Database Develop

[Q] Flashing stock before flashing a new ROM - risks & benefits?

Hi all,
I'll start by apologising if this should be posted in Q&A, but my question relates to recommended practice when flashing ROMs, and I think the people with the necessary knowledge are mostly in here. But please do move this topic to Q&A if that's where it needs to be.
Also, I want to stress that I'm not trying to start any flaming, and I don't even expect to end up with a single "right answer".
My own experience...
I'm pretty new to this - maybe 5 flashes so far. I read everything I could before my first flash (you guys have been a huge help and I salute the community here). It seemed nearly everyone was recommending flashing back to stock first (and Master Clear). The reason seemed to be that it gives you (more or less) a clean slate, and therefore the best chance of a trouble-free flash.
I have no development background, so I thought "Well, that sounds sensible. That's what I'll do." Four flashes with no problems.
In the last few days over in the Phoenix thread, there's been some discussion about the wisdom of flashing to stock before flashing a new ROM. (In summary, every flash is risky, so why do flash to stock when it's not needed? It's another opportunity for the fickle hand of fate to brick your phone. sbl.bin has been identified as a particular risk)
So this morning I decided to try the other approach. I flashed Phoenix 2 over 1.5 and everything is working fine.
So I've had 5 successful flashes.
The first 4 I started by flashing to stock.
The last one I flashed straight over the previous ROM (same kernel, same lagfix etc).
Both approaches have worked for me, so I still have a genuinely open mind on this.
So let me try to phrase this right...
1. What are the risks involved in flashing back to stock, and how easy is it to recover if something goes wrong?
2. What are the risks of not flashing back to stock first, and how easy is it to recover if something goes wrong?
3. Are there any rules that can help us decide whether the risk of first flashing to stock is greater than the risk of flashing straight from Cool ROM A to Cool ROM B?
4. Are there any good dev practices that could reduce the risks either way?
Like I said, I'm not looking to start a war.
It's just that I haven't really seen much said at this level of detail (especially question 3), and my brain likes to understand stuff.

Personally, I just do a factory reset in CWM recovery before I flash anything new. I only flash back to stock when I want to get rid of voodoo and use something thats not compatible. I know you can disable voodoo but that takes forever compared to odin. I'm not that experienced but I've flashed over 100 times and the only thing that has ever broken my phone was the over the air update from att. I will never do one of those again. I agree with the consensus that flashing back to stock is unnecessary. Oh, and get ready for the this is in the wrong thread replies ;-).
Edit: I also use regular Odin and not the one click. I don't know why everyone uses it when there are so many complaints about it. Regular Odin is maybe 3 clicks.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mikey you should make that your new wall paper
Sent from my liberated Captivate via XDA App.

Original, and totally agree.

majinzen said:
Oh, and get ready for the this is in the wrong thread replies ;-).
Click to expand...
Click to collapse
Uh oh. Thanks for the warning
I wonder if I can get it moved before I'm the one that gets all the flames.
Mods - please can someone move this for me before I get wedgied?

Yeah totally kinda here with ya. It would be "preferable" to be able to flash on the go. Just looking at the Vibrant Thread most ROM's are just flashed through CWM, no ODIN, no Master Clear. I know every device is different, but if it is indeed unnecessary that would be great. As well as it would be very nice to know if you can upgrade a particular ROM without a computer. Nero and Axura VE can... Well the Dev's do great and I more importantly think it is for the protection of our device and not having to deal with people complain about "how to fix it..." and "whats wrong..."

I had the same questions myself even read some of the same sort of posts recently in the perception thread. Its been about six months since this phone has been out and maybe it's time to reevaluate what should be common practice. What was true in the beginning might not be true now.
Sent via Santa Clause thru the gingerbread cookies

Looks like I didn't need to worry about a flame war. We've got a group hug going on.
I'm still hoping for some more information though, especially question 3.
When is it ok to flash straight from A to B, and what risks are we accepting when we do that?
Likewise, when is it better to go from A to Stock to B, and what are the extra risks? If flashing to stock is necessary, is 1-click more risky than n-click?
Sent from my SGH-I897 using XDA App

So can I flash perception...then a couple days later disable voodoo lagfix go into clockworkmod and clear data and factory reset. Then flash to another rom like pheonix...I know that's how I would flash on hatch aria...but I want to check and see if that's possible on the captivate
Sent from my SGH-I897 using XDA App

When will you people stop disabling the lag fix...
Sent from my Captivate.

I had problems flashing to a new ROM without disabling the lagfix, so I always disable.
I never do a master clear, or Odin back to stock. I just CWM to the new ROM, but have always had horrible battery.

It will be awesome if we can install roms without losing all of our apps, settings, contacts, email, ect.. I just hate reinstalling all of my apps and reconfiguring all of my email accounts.

wpb2 said:
I had problems flashing to a new ROM without disabling the lagfix, so I always disable.
I never do a master clear, or Odin back to stock. I just CWM to the new ROM, but have always had horrible battery.
Click to expand...
Click to collapse
When you CWM to new ROM, do you lose all of your data, settings, apps ect...?

Ok, so here's a good example of where we might get a better understanding of one part of the flashing process...
MikeyMike01 said:
When will you people stop disabling the lag fix...
Sent from my Captivate.
Click to expand...
Click to collapse
So this sounds like disabling the lagfix is unnecessary. But on the other hand...
wpb2 said:
I had problems flashing to a new ROM without disabling the lagfix, so I always disable.
I never do a master clear, or Odin back to stock. I just CWM to the new ROM, but have always had horrible battery.
Click to expand...
Click to collapse
Wpb2, can you remember which old & new ROM(s) you were flashing when you got the problems? Maybe there are features of those ROMs that (in hindsight) we can understand why the flash didn't play nice without a lagfix.
Maybe it tells us "when flashing between ROMs that differ in feature X, we should always disable lagfix".
Or maybe it identities something that the flash scripts could do, to take the guesswork out of it.
Or mybe time has moved on, and the same problems wouldn't happen today - maybe the "disable lagfix" days are behind us, but we're continuing to do it when we don't need to?
I don't have OCD or anything. It just seems like each procedure (disable lagfix / flash to stock / other procedure) carries a risk. So if we can figure out when the procedures are necessary / redundant, it will help us reduce the risk of trying to flash a cool new ROM and ending up with an expensive brick?
BTW, I appreciate the replies so far, and I apologise for my delayed reply - I'm in New Zealand (and also I've gone for a few days mountain biking but left my charger cable at home, so I'm nursing my battery a little).

The only time i disable lagfix before I flash a new rom is if, say i have all partitions formatted as JFS and the rom im flashing is using a kernel I want and it only supports ext4, for example voodoo, then I disable it, cause the new kernel wont support my old file system and that leads to something bad...but say I have Hardcores kernel already flashed, and all my partitions are ext4 and the rom im going to uses the same kernel or something similar (say Glitterballs, or Setirons kernel (something else that supports ext4) then there shouldnt be any reason to disable it.. Ive flashed probley, atleast 15-20 times from voodoo to either Setirons kernel or Hardcores kernel WITHOUT disabling voodoo for the simple fact of having /system ext4 instead of RFS...and ive never had a problem..thats just personal preference though, I just prefer my /system partition ext4

No offense to anybody at all but this thread is like a "should I format my hard drive before reinstalling Windows" thread. Sure it may work if you don't but why risk it? Especially if you're installing a ROM for testing purposes. Why not start clean and eliminate any bad/old files that could eventually cause problems? Just my $0.02.
I personally always Odin to stock, master clear and flash new ROM. Never an issue.

Escape311 said:
No offense to anybody at all but this thread is like a "should I format my hard drive before reinstalling Windows" thread. Sure it may work if you don't but why risk it? Especially if you're installing a ROM for testing purposes. Why not start clean and eliminate any bad/old files that could eventually cause problems?
Click to expand...
Click to collapse
No offence taken at all. Thanks for replying.
You're kind of right about the "should I format my hard hard drive" thing, and I wouldn't want to waste anyone's time just asking that kind of question. I'm actually asking for information that will help me know which approach to take, in which circumstances.
existz's post was exactly the kind of education I'm looking for...
existz said:
The only time i disable lagfix before I flash a new rom is if, say i have all partitions formatted as JFS and the rom im flashing is using a kernel I want and it only supports ext4, for example voodoo, then I disable it, cause the new kernel wont support my old file system and that leads to something bad...but say I have Hardcores kernel already flashed, and all my partitions are ext4 and the rom im going to uses the same kernel or something similar (say Glitterballs, or Setirons kernel (something else that supports ext4) then there shouldnt be any reason to disable it.
Click to expand...
Click to collapse
So now I know how to decide whether to disable lagfix...
Do the old ROM & new ROM (kernels?) support the same file system?
If YES: I don't need to disable lagfix.
If NO: I do need to disable lagfix
This is probably obvious to you guys (thanks for not flaming me & my noob questions that might be in the wrong forum). But it's good education for folks like me. Now that I've learned that flashing to stock / disabling lagfix carry their own risks, so I don't want to do them if I don't have to.
Not much education so far about the risks of flashing to stock, but I should probably just let this thread die. It's a shame though. There are plenty of opinions for & against flashing to stock, and there seem to be smart & respected people on both sides. I just can't find any information.
Thanks everyone for your replies, and particularly to existz. I'm just a little bit smarter now than I was when I posted the topic.
As for flashing to stock - given that it carries the risk of serious brickery (and the risks of not flashing to stock seem minor by comparison), I reckon I'll be following the flowchart on page 1 from now on.
Unless someone posts some more education to explain why that's a dumb ass move.

The response is going to vary based on both people's experience and their phones. I never flash to stock before installing a new ROM, I simply wipe data and cache using CWM before installing, then restore my apps and contacts with Titanium Backup. I've never had a problem with this method.
But here is where things get a bit complicated. Why don't I flash back to stock? It's not because I'm lazy or because I like taking risks. It's because (in my case, as well as with many others) my Captivate can't be flashed to stock JF6. The closest I can get is JH7, which requires flashing to JH2 first, a much riskier and less simple process.
For me (and supposedly others), attempting to 'one-click' my phone (or use another version of Odin, including the 3-button fix version) is a 'success' message in Odin, followed by a bricked phone, no ADB connection and no button combos. Time to break out the jig again...
I can't agree that it's generally less risky to flash back to stock first, as you still use a non-official method of writing to your phone's ROM, which is just an additional chance for a full-brick (corrupted sbl.bin means you need RIFF JTAG to fix). For custom ROM's that don't include this file (and no-wipe ROM's), there is a significantly reduced chance of really messing things up. At worst, you might not get past the boot screen, or you might get some FC's, and then you can either wipe and try again, or move onto flashing stock if nothing else works.

I spent a lot of time reading threads again today serendipity and phoenix and noticed at least once someone had issues understanding how clockwork actually works. They didn't understand that the update zip that rom manager puts on the root of the sd card is what loads clockwork, and that reapplying the update zip loads it compared to applying a zip from sd_card is a different operation all together.they can be used the same, but they are missing the small diffences of the operation. Something that more experienced users are missing is just how much clockwork has changed in six months. Now it's in the kernal and has many more features. The problem is the stock answer for fixing problems flash to stock instead of learn to use clockwork better. As of yet I haven't seen any good guides for clockwork, and all the lag options, at least not the pages and pages of how to flash stock which really could use a good rehashing.
Sent via Santa Clause thru the gingerbread cookies

[Q] MCR script missing

hey guys, just rooted my Samsung Captivate. Everything has been going great till now. i Downloaded a lagfix, which is honestly the main reason i rooted my phone. however after everything (yes, i did everyting right) i didnt have the app that was included in the .zip file iput in my phone. the app is called MCR scripts.
i did some reseach and i found this key line
"*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******"
in this thread:
http://forum.xda-developers.com/showthread.php?t=750869
so how do i just get the MCR scripts? i downloaded tayutama's zip file and i found the folder named "scripts" with the 3 files in there but they are .sh files.
so what do i do here? do i need to convert then to apk or something? please help!!!

forgot to mention...because i have a captivate i can not just go to setting/applications/ and choose for any app to be allowed or what not. i simply do not have that option. i use android central to get my apk files working on my phone. I have tried to run a zip file that will just let me install the apk file on my phone with no need for a computer. But that was to no avail.

bumping this.....this forum moves fast haha

thats an old thread and deprecated now im sure. why not flash a kernel with voodoo enabled? That would be a much safer and logical approach

woooah what?
i would like to get all technical and hardcore with this rooting thing but step by step lol. I'm still in my beginning stage i have a lot of experience to be earned ahead of me. is there no way to just get the mcr scripts as an apk?

nismoasfuh said:
woooah what?
i would like to get all technical and hardcore with this rooting thing but step by step lol. I'm still in my beginning stage i have a lot of experience to be earned ahead of me. is there no way to just get the mcr scripts as an apk?
Click to expand...
Click to collapse
have a look at the date on that thread, and the FIRST LINE in the thread asking to be deleted....

right, i didn't notice that...wow. either way that new thread the link is dead. and for me to run that packaged zip file i would need to completely set my phone to stock, nor do i know how to do that. Im simply asking for just the MCR files in apk format if that is possible at all. If not then can you please point me in the right direction? Thank you for all the help so far, i truly do appreciate it.

i guess the real question here is what is your ultimate goal?
you want froyo? install a rom (most everything on the dev forum will install a lagfix for you, click on the link in my sig)
you just want a 'lagfix' on stock eclair? install a 2.1 kernel with voodoo

rom would be customizing the android correct? like a new home layout and what not? That would be cool but im happy with what i have...i would just like to be able to download any app for free. and get the lag fix. i got the first part down (apps for free) by rooting the phone, all i have to do is get the apk downloaded on my comp then run android central to install it on my phone.
so i download kernel with voodoo, is it just a drop into internal sd...same as when i rooted my phone? then go into recovery and choose reinstall packages?
ok found this thread:
http://forum.xda-developers.com/showthread.php?t=784170
sooo i would definitely be installing the one WITHOUT the back light notification, as...my hpone doesnt have leds. Hopefully it works for all galaxy s phones because this seems to be for only the 19000 captivate? while i have the sgh captivate from AT&T.

3rd page in less than 24 hours...wow lol

so at this thread
http://project-voodoo.org/download
i downloaded the lag fix for my phone which is like near the bottom of the page. i renamed it to lag fix zip file tp "update" but since i have the other files that are also renamed to "update" like for my rooting and stuff the file ended up being update(3) idk if that makes a difference but when i booted my phone from recovery mode after choosing resinstall pacakges, the phone boots up normally no long pause durgin the at&t screen or anything so i know the lag fix didnt work...also because the phone is still...slow. helllp! please.

you need to remove ANY other update.zip files from your phone and rename THAT file to update.zip
then reinstall packages
once you have installed an update.zip it is no longer required on your sdcard

thats what i was thinking, just wanted to make sure. Ill check back once its done thankyou.

YES!!! i knew it was going to work when i heard the freaky computer lady's voice haha. Even still, i didnt notice a HUGE improvement, my quadrant score is a bit dissapointing only 1400...

yea, so do you guys think i should maybe overclock? its still laggy/slow to me. Im sure becuase of the preious iphone usage lol. whats the best way to o/c? i heard that the overclock app isnt very reliable...i know , i know, overclocking itself isnt relable but are there other ways about doing it?

off your original topic ...

understood. making a new thread.

[Q] Help With Old Partially Rooted G1

So I have a G1. I rooted it and then tried flashing CM5 (Or 6, I don't remember) but something went wrong so I just dropped this project. I picked it up again because my girlfriend has a dumbphone, so I want to give her this smartphone until I can buy her a better one. When I boot up the G1 normally, it just stays at the boot screen. I am able to get into recovery. However, when I trying to flash CM6 I had to go through a few steps. I flashed CWM Recovery, created a backup, updated radios and such, then flashed Danger SPL. After that (I think that's all I did, it was about a year ago so I don't exactly remember) it reverted to JesusFreke's Recovery(the default recovery installed using the rooting method that I used). The phone is in S-OFF and I believe the H-BOOT Version indicates that Danger SPL was flashed successfully as well, but I'm kind of stuck now. Any help would be appreciated.
Boot Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery:
H-BOOT:

looks like you just about there, i would recommend getting the latest amon_ra recovery for it has more options and will make other tasks easier.
http://forum.xda-developers.com/showthread.php?t=566669
also you should definitely get the latest radio/spl found here
http://forum.xda-developers.com/showthread.php?t=831139
to make things easy start by flashing the rom found here
http://forum.xda-developers.com/showthread.php?t=613809
you have everything almost done, so try to get amon_ra, the 2708 + radio/spl, and flash an awesome new rom --- maybe ezgingerbread or froyobylazslo?
keep at it, it worth it in the end

demkantor said:
looks like you just about there, i would recommend getting the latest amon_ra recovery for it has more options and will make other tasks easier.
http://forum.xda-developers.com/showthread.php?t=566669
also you should definitely get the latest radio/spl found here
http://forum.xda-developers.com/showthread.php?t=831139
to make things easy start by flashing the rom found here
http://forum.xda-developers.com/showthread.php?t=613809
you have everything almost done, so try to get amon_ra, the 2708 + radio/spl, and flash an awesome new rom --- maybe ezgingerbread or froyobylazslo?
keep at it, it worth it in the end
Click to expand...
Click to collapse
Thanks for the response
I'm having a problem. I tried flashing the custom recovery multiple ways but it didn't work. The farthest I got was through fastboot. I installed fastboot on my computer and I have the recovery file in the root of the SD. I put the G1 into fastboot and checked to see if it was detected:
Code:
fastboot devices
HT841GZ06125 fastboot
I assume that means it's detected. Then I ran this:
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0.img
error: cannot load 'recovery-RA-dream-v1.7.0.img'
What's wrong?

The recovery.img you want to flash needs to be in your current working directory our you need to give the full path as a parameter, i.e.
Code:
fastboot flash recovery recovery.img
if the recovery image is in your working directory or
Code:
fastboot flash recocery /home/xyz/work/recovery.img
if the recovery image is located in the directory /home/xyz/work

Wow, I feel so dumb. For some reason I thought fastboot worked through the sdcard, although now I realize that is impossible because the SD wasn't mounted. Happily running CM6.1 now =]

Vulf said:
Wow, I feel so dumb. For some reason I thought fastboot worked through the sdcard, although now I realize that is impossible because the SD wasn't mounted. Happily running CM6.1 now =]
Click to expand...
Click to collapse
Meh I find CM6 gets really slow after a while
You should try Froyobylaszlo
Froyobylaszlo for speed and stability and usability...oh and it looks good
EzGingerbread...if you for some reason really like Gingerbread

I'm a bit at the same stage as Vulf,and just grabbed my G1 out of the dust again, whilst my Sensation XE is being repaired.
I have been struggling for three days now to get a ROM flashed, but I obviously must be doing something wrong. I know there's a whole lot of information available. I been through a lot of topics, and tried different things. I am now kinda frustrated and wondering what I'm doing wrong, and hope someone can help me out.
Take for instance FrankDrey's ROM, I'd love to try it, and just followed your steps perhaps 10 times. But, just like many other ROM's I try to install (i.e CM7.2, ezGingerBread), I end up in the 'hanging G1' screen. I tried using different kernels (perhaps the wrong one?), tried the swipes using 'fastboot', the superswipe and all kinds of things, but I never got anything to work. But... for some reason, there's 1 ROM that did work for me, just not 100%. I tried Froyo DreamTeam ROM, which installed (like most other roms did, except some gave Status 7 boot write error), but this one actually booted up. I could not work with it, because I did not get the 'install wizard', did not see the 'Market', my phone has no lock screen anymore (pressing any button activates the phone), and I could not use my 'Phone' and 'Home' key anymore. (these still work in recovery mode though) I tried different 'gapps' apart from the one being suggested, and been looking at some 'custom ATMD' or so which might be a cause for the 'home' and 'phone' key, but I did not recognize anything in there that I have been doing.
I really hope someone can please help me out, so I can finally get this phone to work again properly (and give it to my sister in a few weeks )
Here's the information fastboot gives me, which seems to be what it should be, I think:
DREAM PVT 32B SHIP S-ON
HBOOT 1.33.0013D (DREA11000)
CPLD-4
RADIO-2.22.28.25
Oct 21 2009:22:33:27
I believe that the Kernel I used was one of EzTerry (excuse me if I misspelled that), the 1.5.1 Froyo based.
Thanks in advance to anyone who's taking time to read and help me out.

With that radio/SPL you should be able to run ezGingerbread without problems. To be sure, do a
fastboot erase system -w
then boot into recovery and flash latest version of Terry's ROM http://sandbox.devnull.name/android/gingerbread/GINGERBREAD-DS-Stable-v1.0-20111204.zip and gapps http://www.multiupload.com/7B0LCBTREB, then boot the ROM. The first boot might take some time ... (>= 5 min)

anddisa should also mention to look at his signature. he has a version of ezgingerbread that is almost the same as ezterrys but has a few nice tweaks to it. if you tap his sig it will link you to a page explaining his version and a dropbox for the files.
oh and anddisa i love your work and all the help you give on xda so in case i never thanked you ill do it in the post above!

Hello AndSisa and demkantor. First I'd just like to say thank you for the help! .
Is the erase system -w better, or is it the same as the 'wipe' from the recovery menu? I tried both just to make sure . Also, I had the feeling that installing another kernel was sort of required for the ROM to work.
Anyway, I followed your steps, but instead, I flashed the ROM from your signature. As demkantor mentioned, for some reason my preference goes to the ADS_Magpie ROM. I also tried that ROM earlier, without any luck I have to add, and I'm afraid I'm facing the same again as I speak . I downloaded the Signed-v1.0 by the way.
I think I'll wait another 10 minutes and try the ezGingerbread rom soon which you posted in your reply (which I tried as well a few times), trying it the way you suggest me. I'll keep my fingers crossed, and will post my result in a reply if no one else has replied after my post, and otherwise I'll edit this post .
Thanks in advance, and when I got my ROM running, I'll make sure to properly thank you using the 'Thank you' button.

Yes with that radio and spl you should be able to flash Frayo, froyobylaszlo, EzGingerbread, and a few other ROMs.
Are you sure you're waiting long enough?
It may take a few minutes...
If you are waiting that long, then hmm...sounds odd...
When you flashed frayo was it the ONLY thing you flashed? Make sure it is.
You don't need to flash any kernels or anything.
Just frayo-signed.zip and that's all...
Btw, my theory is confirmed
Google apps controls the Home/Phone keys, Lockscreen and other stuff!

My 2nd attempt in flashing ezGingerBread turns out to fail as well I'm afraid. I've waited for nearly 10 minutes now (and counting), yet no sign of life.
For some reason, I got a feeling that it just skips to install something or so. For instance, when I install this DreamTeam Froyo, and install the Google Apps they provide (or any other cause none worked for me), it does say "Google Apps installed", or something like that after I flashed the .zip file. However, in the menu, I don't see any Google app at all. Should I try another SD card, or can't it be the SD card? As for the SD card, I partitioned it as some topic advises, I guess yours. (512MB Ext4, 96swap, other GB's FAT32).
As for your ROM, Frankdrey, I tried 4 different methods to be honest. I tried the straight-forward, flash it + gapps. I tried flashing + kernel + gapps, I tried flashing kernel, your rom, and then gapps, and even once without gapps, but without any result .
Also, can it be possible that the kernel I installed is not compatible with the ROM? I flashed the 1.5.2f_S one from Terry, been switching between the Froyo / GIngerbread one depending on the android version.

Nonono...for my ROM you don't need to flash Gapps
Just flash the ROM and thats it!
No kernel, no Gapps
Everything is included!
Both EzGingerBread and Frayo/Froyobylaszlo include the kernel in them!
So you don't need to flash any kernels, just make sure you have the correct SPL/Radio and you're all set!

I feel there is something missing from the equation here. What was the last working rom you had on your g1? Have you ever had a custom mtd? According to what your telling us your radio/spl are ideal, you seem to have the latest recovery and understand fastboot.
Try this mount your sd sd card to make sure it works, take everything off except superwipe and frayo (ease of use) thats all you should need. From recovery flash superwipe.zip then teboot to recovery. Flash frayo.zip the reboot. Wait. Wait. Even as long as 20 min. After that i would sugest just starting over with dreaming.nbh
Sent from my NXM726HN using XDA App

frankdrey said:
Yes with that radio and spl you should be able to flash Frayo, froyobylaszlo, EzGingerbread, and a few other ROMs.
Are you sure you're waiting long enough?
It may take a few minutes...
If you are waiting that long, then hmm...sounds odd...
When you flashed frayo was it the ONLY thing you flashed? Make sure it is.
You don't need to flash any kernels or anything.
Just frayo-signed.zip and that's all...
Btw, my theory is confirmed
Google apps controls the Home/Phone keys, Lockscreen and other stuff!
Click to expand...
Click to collapse
Hey frankdrey, how did you confirm the gapps could be causing the home keys etc problems. What google app(s) is the source?
Sent from my NXM726HN using XDA App

There is another possibillity at least to see what is happening: While booting your phone keep it connected to usb and type
adb logcat
on the console of your PC. At least after one/two minutes you should see something there. On a Linux system you could also do a
adb logcat | tee boot.log
so the output is written into the boot.log file, too.
If you provide later that log, probably we can see what's happening.
Sent from my Gingerbread on Dream using XDA App

I unfortunately can't put a catlog here anymore, but I can say that it's working now! Good start of a working day/week .
What the exact problem is a mystery, and I think it will stay that way.
What I've done is putting the old dreamimg.nbh back on the phone, and started the whole rooting thing all over. The only difference, in actions that I've been doing, is that I did not pick the *cyan* coloured RA Recovery this time.
As for the question if I ran any custom ROM before on this phone, I only used the 'default' rooted ROM so far. On my other G1, things worked like a charm.
Anyway, I just got the 'setup wizard' from Frayo on my screen, so I think I'll start working with it and enjoying it!
I feel a bit silly that I never thought of doing the whole thing over earlier
Thanks for the help and input, and I hope that anyone else facing this issue will get things worked out too.
demkantor said:
Hey frankdrey, how did you confirm the gapps could be causing the home keys etc problems. What google app(s) is the source?
Click to expand...
Click to collapse
I think it's probably based on his previous experience, and the fact that I said something in my previous post like "I did get one ROM to work, but just not 100%. The market wasn't in the apps list, I had no lockscreen (every button activates the phone instantly), my dial (phone) key is not working, nor was my home-button." must have given him the last bit of confirmation he needed .

I think it was that you were flashing a kernel after the ROMs...
You're not supposed to do that for most ROM
And yes about google apps
I think it is the entire google services framework
Ill try look into the code (if there is code for gapps)
And ill see what's up

[Q] - Simple route to GB bootloaders from ICS w/Froyo BL

The title pretty much says it all. I've been reading for days and my eyes are burning yet I still haven't found anything exactly like what I'm asking...and I don't want to keep asking stupid questions in the dev section.....
I was on a custom Froyo ROM for a long time and finally got around to trying out SlimICS 4.2 a couple of weeks ago. The instructions called for a CM9 flash first, then SlimICS. It all worked perfectly and I love the ROM.
I've never tried GB and am still on Froyo bootloaders. I would like to switch to GB bootloaders, maybe for no good reason at all. I figure in the long run it will be a good idea. (different rom, kernel, JB, whatever)
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
I'm looking for a simple, logical sequence to get me back exactly where I am (ICS) but with GB bootloaders. Perhaps back to a custom Froyo rom/kernel then flash GB bootloaders then back to ICS? I'm guessing that cwm will be able to restore the state of my current rom after all that. I'm so sick of setting up everything from scratch and Titanium can only do so much....
Thanks

Here ya go...
U cannot flash the GB Bootloaders while you are running a Rom that has the mtd/yaffs or yaffs2 partition, that is, a CM, MIUI, ICS, JellyBean and such like. U will need to be on a bml/rfs partition, that is, a Stock Rom or at least a Dev Rom based from a stock firmware.
Do an Nandroid Backup on what you are running currently.
Backup everything you do want to save...apps, contacts, messages, emails, pics, efs folder, etc.
Then you will need to flash back to Stock GB Firmware with Bootloaders included. The i897ucKK4 is the latest official. Here is Stock I897UCKK4 Android 2.3.5 One Clicks. Use the Odin or Heimdall version that includes the GB Bootloaders. If you have a newer Captivate that does not like using the One Clicks, then see this thread for the .tar package of the i897ucKK4... [ROM] I897UCKK4 [17.11.2011][Android 2.3.5]. With this you will probably have to wipedata/factory reset first. Then use regular Odinv3 1.83 or similar to flash it. **Note: Flashing Bootloaders is risky. So be sure you have a trust worthy micro usb/usb cable, constant power source, etc. You don't want to loose power or connection during the few seconds that the bootloaders are being flashed. Bad bootloader flash = hard brick.
Once you are successfully back on Stock KK4, then go to this thread... [KERNEL][KK4][1/28/11] Corn Kernel and use the regular Odin to flash the .tar 7.0A version of this kernel. This will give you the CWM Recovery that you need.
Then reboot into CWM and reinstall the ICS Rom you were on before per that Rom's install instructions.
Once you are booted up on that ICS Rom, reboot into the Recovery of that Rom and then you can Restore your backup that you did at the beginning of this process.
You should be good now.
For issues along the way with connections to the pc, download mode, etc. please see this thread... Captivate Connection Issues and Download Mode Help

The most direct route would be to flash a Gingerbread-based Stock rom with bootloaders from your current setup. This will put you back at stock (including your partitioning), so you'll have to flash as if you're going to CM-based roms for the first time when you go back to ICS/JB.
Obviously, there's all the normal cautions of backing up, bootloader dangers, etc.

@ jmtheiss... I Ninja'd ya by a few minutes. Lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

They both said it better than I could have but what it comes down to is there is no "simple" way to go about what you are wanting to do...
Sent from my SGH-I897 using xda app-developers app

I don't think a lousy "thanks" even begins to cover it. I really appreciate when someone puts that much effort into helping somebody out. Cheers!
And that definitely qualifies as "simple" enough...better than something requiring rooting again and getting a functional recovery, etc. A couple of Odin sessions and a couple of cwm flashes are fine.
Thanks again guys.

bcflyfisher said:
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
Thanks
Click to expand...
Click to collapse
I have done it successfully a couple of times without any issues. I have only done it when absolutely necessary since they do say there's some risk there.
What I don't understand is how you *could* run ICS without GB bootloaders? I didn't think that was possible.

I'm living proof. I was hesitant but their instructions said if coming from Froyo flash CM9 first then SlimICS. I flipped a coin and it worked fine. The developer of Slim (krarvind) knows I'm on Froyo bootloaders and didn't seem too phased by it. Whether or not I'd be able to jump to JB with whatever kernel is unknown so I'm going to backtrack a little and do what I probably should have in the first place.

Here's an update of what I did just in case it's helpful to someone else down the road.......
I did my best to follow the suggestions given by 4-2ndtwin in the 2nd post. I generally have pretty good backups of everything done but I did new ones just for kicks. Nandroid, Titanium Backup, efs, SMS, call log, APN, and a few other things. I downloaded all the necessary files, and laid them all out sequentially on my screen so I wouldn't get distracted and screw up. In the end I'm pretty much exactly where I wanted to be but of course there were a few unexpected issues.
- The Heimdall One-Click of stock GB with bootloaders was very easy. I had Samsung drivers on the computer already but Heimdall insisted on installing new ones. After that it did its thing and I was on official KK4 with GB bootloaders.
- Next up was regular Odin flash of the Corn Kernel. When I connected the phone in download mode Odin didn't give me a yellow light. If I connected the phone while it was NOT in download mode Odin recognized it. I wasted at least an hour to discover that it was just a driver issue. The drivers that Heimdall wanted weren't "good enough" for Odin. Interestingly, neither was the original package I had on the computer. The one that worked was called "Samsung_USB_Driver_for_Mobile_Phones.zip" from the Samsung website. After installing that Odin saw my phone in download mode and I was able to install the Corn Kernel. Rebooting into recovery gave an option to root the phone.
- At this point everyone in the world decided they needed something from me so between work and phone calls/texts I ended up using the phone on GB for a while.
- My boot screens had been a total mess since my first custom rom so I decided to do the boot screen fix next - http://forum.xda-developers.com/showthread.php?t=1065743 - TRusselo added a bunch of good info to the thread and there's a good post on page 10 from irishvandal that explains the whole sequence of boot screens and what you can and cannot change.
- So the next step should have been to flash CM9 on my way back to SlimICS just like I did a month ago. I figured since I had been using the phone for a couple of hours I should wipe everything ... so I did the cache, data, format system, dalvik cache, and then I went to flash CM9 and noticed that for some reason I didn't have the zip file on the phone any more. I must have deleted it myself because nothing else spontaneously disappeared. When I rebooted normally to plug the phone in and transfer files I discovered that in wiping/formatting I messed something up and I kept getting stuck on the Corn Kernel boot screen. I could get into recovery or download mode just fine, just no normal boot. I was able to mount storage in recovery but when I tried to copy over the CM9 zip it kept hanging. After numerous attempts I decided to just go right back to the beginning.....
- Heimdall once again wanted its own drivers. No problem, I did that, then uninstalled them and reinstalled the drivers Odin likes, then got Corn again, did the boot screen fix again just to try a different image, then downloaded a new CM9 Nightly and copied it to the SD, flashed it with no issues, then flashed SlimICS (which actually has 2 zips plus addon packages) and I was back to ICS with GB bootloaders. It's amazing how fast things can be done when there are no more surprises!
- When the phone was rebooting into Slim ICS I got a message I don't remember seeing before - "Android is upgrading" or something similar. Weird. The next time I booted to recovery to try to restore the nandroid backup I ended up in CWMR Touch v5.5.0.4, which is weird looking and makes me feel strange. When I tried to do a full restore it encountered a few issues such as not being able to restore data normally. I don't recall the details but when I reinstalled Titanium Backup it would just FC so I couldn't restore any of my other apps. The "solution" was to reflash the Slim zips and do a restore of the system only. This set up all the tedious stuff for me. I got TiBu again and restored apps+data and that worked. Chose my launcher and it was back almost the way I wanted it. Interestingly, I had to replace the widgets but the shortcuts were all there in the right places.
- Voice search force closed. Slim doesn't include it in the base rom but it's available as an add-on and I had the zip on the sd from last time but flashing it didn't fix the problem (it had worked the first time I installed Slim). Some random sequence of freezing the Voice Search app, wiping its data, reflashing the Voice zip, unfreezing the app and it worked. In the process I noticed that in TiBu it was originally listed as Voice Search 2.x.x but then it was suddenly 3.x.x with a different icon. Then an hour later after all kinds of restoring (SMS, call log, etc) voice was force closing again. It was also listed as 2.x.x. This time it took me twice as long to randomly do things until it started working again (and at the same time it turned back into 3.x.x. It's been fine since...
So again a huge thanks for the advice! I got to spend the better part of a day fighting my way through minor issues but I learned a lot about my phone and got over my aversion to Odin for the last time. Hopefully someone else can benefit from something I've gone through. If nothing else, I feel a renewed sense of accomplishment.

^
If all ur ics and jb roms have run well...then i see no need to flash the bootloaders.
Sent from my SAMSUNG-SGH-I897 using xda premium

[Q] [HELP !] Bricked my GT-P1000 ?

Hello right here,
Got an big issue on my GT-P1000 :crying:, hope i'll find help and answers around :angel:.
First of all, i'm french, so please apologize my english if it's not as good as i'd like to (and feel free to correct me if necessary, it'll help !)
So, i bought a few years ago a GT-P1000.
Trying to change the rom, the official one was too slow .
First of all, rooting, yet some problems : all the processes i followed told me it was OK, and when i ran Root Checker, it told me the opposite (not root access). After a few tries, i thought Root Checker was the probleme, so news step : CWM installation.
Nickel, all good.
Last step : download and install Cyanogen Mod 10.2 (Android 4.3) following this tuto : computechips (can post a link )
And the result is : the tab won't boot any more. I restored it, and same thing, stays sticked on the "samsung" welcome screen, no more movements.
I still can go to the Recovery Mode, but there are messages telling that no drive can be mounted :
Code:
E: unknown volume for path [/system]
E: Unable process volume ! skipping ..
Checking /data..
E: unknown volume for path [/data]
E: unknown volume for path [/data]
E: Unable process volume ! skipping ..
Checking /cache..
E: unknown volume for path [/cache]
E: unknown volume for path [/cache]
E: Unable process volume ! skipping ..
Done !
And so on ..
Any idea on this issue ?
Thx !
Oliv.

Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252

Ichijoe said:
Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252
Click to expand...
Click to collapse
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?

Olif5978 said:
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?
Click to expand...
Click to collapse
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.

Thx !
Ichijoe said:
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.
Click to expand...
Click to collapse
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif

Olif5978 said:
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif
Click to expand...
Click to collapse
My advice is to just stick to the lastest CM10 Release 20130203
for now as this ROM if not, working @ 100%! then most certainly @ 99.9% as far as both the Camera and Bluetooth are concerned!
At this point we're better off waiting for KitKat ROMs then updated Jelly Baean Ones. AFAIK (And, TBH I'm just as new to this "Game"!), these Problems have been around as long as CM10.1, and CM10.2. i.e. for almost a whole Year now!
So I for One am not, holding my breath that this will be fixed soon-ish, at least not for CM's 10 .1 & .2...

CM11 KitKat
Ichijoe said:
My advice is to just stick to the lastest CM10 Release 20130203
Click to expand...
Click to collapse
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!

ha5x said:
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!
Click to expand...
Click to collapse
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.

Cannot remember how I did it
Olif5978 said:
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.
Click to expand...
Click to collapse
Hi Olivier,
I do not volunteer to write a how-to. In fact, I cannot remember how I did it. I myself had LOTS of such difficulties, errors, missing files, there were even several hours while I thought I had bricked the device which was responding to anything... It took me nearly three days flashing, cursing and flashing, cursing and flashing and cursing.
But what I have found is that you need to go step by step, flashing one ROM after another until you find one which comes with a recovery compatible with CM... I vaguely remember that a key step was flashing the "Overcome ROM", which then let me great step further.
Sorry.

You have to flash CM 7, then CM9, and finally CM 10 or 11. Your choice. Just make sure you have the right recovery installed and CWM version. I would skip the gapps til the last version you flash. Follow the directions for each CM version on xda.
Sent from my SCH-I800 using xda app-developers app

This is how i flash CM11..
Go to download mode
1) Restock using Overcome method..(via Odin) http://forum.xda-developers.com/showthread.php?t=1881981
-just the stock safe with my support modem..which is JPZ modem..no need to flash the Overcome Rom
-let it boot
Go to download mode again
2) Flash the Overcome Kernel..for root access and custom recovery..(via Odin)
-let it boot
(Step 1 and 2 is not necessary if you already using custom rom..but i like to do a clean flash..and if you still using the official firmware..step 1 and 2 is necessary..)
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
3) Flash CM10.2 for Kernel 3.0.x...(via custom recovery) Any CM10.2 With Kernel 3.0.X
-3x flash (first for CMW recovery..second for partition layout..third for CM10.2 Rom)
-let it boot
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
4) Flash the CM11..
5) Flash gapps..
6) Reboot
done..my p1 is running CM11..
and i did it without any problem..no crash or anything..
and i'm using storm31 CM1120131203..
with a few bug like front camera ect.(newer build already fix some of the bug)
or you can always go to the CM11 thread and read the OP for their instruction..
but always remember..
CREATE BACKUP
READ THE OP..and maybe a few comment first before you try to flash any rom..
just to make sure what are you going to experience..
i even read the whole thread before i start to flash any rom..
with that being said..
DO AT YOUR OWN RISK.. and Good Luck..:good: