Was running 3.4.11 tmobile uk, upgraded from 2.51 via sbf.
Just restored the new offical korean nandroid and too my surprise did not need to touch the bootloader, it just booted
You mean u didnt had to flash de sbf?
Just restored the backup?
Yes, thats correct I have done it 3 more times to be sure. However carfeul over the version of recovery you install, ensure it is the one for froyo
interesting.
and everything runs normally?
if so we could assume that they got things in common.
but i wouldnt assume that any froyo version can do that.
My thoughts are the bootloader is backwards compatible, I haven't tried yet but I would expect that and nandroid of froyo will work on same bootloader, just wipe cache to resolve data clashes
Flashed Chinese 1.11 ROM with uk_bootonly, it's actually recommended by someone who says they're compatible.
Related
Does anyone have a link to the original firmware for the US T-mobile firmware? I went through an odyssey last night trying to install jboogie's froyo rom and after applying the camera fix .sbf my phone started losing it's mind. I couldn't even enter recovery boot from clockworkmod and eventually had to flash the 2.34 central european rom, but had no cellular data. From there I could enter recovery boot and nandroid restore and am now back to rooted 2.21. I'd like to try to get working froyo again, but in case the same problems arise I don't want to flash the 2.34 rom if it doesn't have cell data. Is there just a plain old tmobile .sbf that I can use to restore if I can't get into recovery to nandroid restore? Thanks.
Why not just perform 3G fix mentioned in this thread.
http://forum.xda-developers.com/showthread.php?t=897445
gottabekin said:
Why not just perform 3G fix mentioned in this thread.
http://forum.xda-developers.com/showthread.php?t=897445
Click to expand...
Click to collapse
I searched for that but couldn't find anything. Thanks a ton. I've got froyo working again except for a flash but I'll get that data fix just in case. Thanks again.
No problem.
hello!
i now have 3.4.3-11. the phone is rooted!
what is the safest way to flash a new rom when it will be available.
i've heard that if i wipe from recovery before installing new rom with rsd lite, the phone could get in bootloop because of the root. but if i install directly and wipe at the end, will the phone remain rooted?
what is the safest way?
No it's not true.
You always have to wipe before flash a new sbf with RSDlite. Flashing a new ROM will "unroot" your phone, so you have to root again after flashing.
mihik said:
No it's not true.
You always have to wipe before flash a new sbf with RSDlite.
Click to expand...
Click to collapse
Does that not depend upon what version sbf you are flashing?
When I went from eclair 2.1 up to froyo 2.2 I wiped before flashing (also wiped after just in case) but when I recently went from the UK froyo to a newer leaked UK froyo sbf I didn't wipe at all & everything worked fine
There are a lot of comments in dev part where users have FCs and app errors and most of the cases they didn't wipe before flash.
So may be you were lucky.
It's up to you,but he asked the safest way.
I was only asking the question as I wasn't sure myself as i'm not fully clued up yet.
The first time I did wipe when going from éclair.
Maybe I was lucky the second time but I would have wiped if there was an issue - just didn't want to have to input all my settings again if I didn't need to. But it all went OK so no worries.
Sent from my MotoDefy.
I recently installed the nordic 2.2.2 fixed sbf and afterwards the custom rom S.Froyo NORDIC edition. Thing is that the market wasn't working so I tried flashing gapps from CWM. When I started the phone I could enter pin but all sort of google apps kept FC'ing so I couldn't do anything. That's why I wanted to reflash Nandroid and fixed SBF but I couldn't get into CWM anymore. Now I can only acces stock Android recovery.
I came from Android 2.1.1 (2.51.1), can I just reflash a full SBF of that version again and will my phone be alright then? (I already wiped everything but that didn't work out.)
Yes just flash the 2.51 full sbf i did that. The reason a wipe doesn't work is you have modified apps on the system partition and wiping doesn't touch the system partition. It's protected for a reason lol.
Thank you very much it worked.
I recently moved to CM7 and S-OFF. I used the alpha-rev method and flashed the CM7 hboot
Seeing the new Leedroid GB rom, I figured I'd give it a try. So I did a full backup, wiped everything, flashed the stock Hboot from Alpha-rev website, then flashed the Leedroid rom and... BOOTLOOP.
I then tried version 2.4, and same thing.
Following this I flashed Redux, which was nice but slow and I was able to confirm that I had 148 Mb of internal memory...
I then redownloaded Leedroid 3.0.5, thinking my file was perhaps corrupt, and still nothing...
I even tried restoring an my old CoolSenseHD 9 nandroid, which passed the splash screen, but looped at the boot screen.
Any ideas??
I had a similar problem. Go into CWM and format system, data and cache.
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
i think your recovery is outdated, this can cause bootloops, something to do with your recovery version not able to handle new updater-script.
so update your recovery, you dont have to remove current one, just get the fake-flash.zip of any new recovery (clockworkmod 3.0.2.7) put it on ur sdcard, then in AmonRa select to flash the fake-flash.zip file and it should boot up CWM. then wipe all and flash the ROM.
other than that make sure you have correct partiton layout on ur sd (ext needed ofc) and obviously, correct hboot table.
I tried flashing the latest CWM, then wiping everything and flashing leedroid, but no luck. Then I tried putting AmonRA recovery back, and I tried once more, but still no luck. Then I tried flashing the latest Gingerbread MIUI, and that worked like a charm....
So that rules out my recovery being outdated, and I did flash the latest Radio, so that's good too... I really can't pinpoint the issue, but regardless, I'm really liking MIUI, so that's good I guess.
And as for partitioning, my SD card had a 500MB EXT3 partition for Leedroid, as specified on his page, and my partition table was set to Stock Bravo. I reflashed that Hboot about 4 times just to make sure...
TheSobadef said:
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
Click to expand...
Click to collapse
As I said, I had this exact problem and solved it by formatting system in CWM. I could flash certain Roms like redux but not leedroid.
AmonRA does not have an option to format system, just wipe which is different.
But even with CWM, I couldn't do it...
I'm guessing it's because the boot.img is too big in the leedroid GB rom, and you have corrupted blocks which limit the allowable size or something. I have that problem with my Desire with certain roms.. which really sucks. Maybe it's because we have Telus branded Desire's lol....
Well I don't believe the Telus Desire is branded (no telus bloatware like other phones, no logo or anything)... I mean I never had to make a gold card, and I haven't been on stock since december...
I just find it wierd that I used to be able to run Froyo leedroid (version 2.3d), but now that I try and flash 2.4 (also froyo) or 3.0 (GB) I have no luck
Have you tried using the RUU to get stock ROM, use Unrevoked and then get the LeeDroid version you wanted?
Are you trying to load htc sense roms on cw7 hboot? Of course it won't work, there is not enough space for the rom.
^If you read my posts, you would know that I have not been using the CM7 HBoot, but the stock Hboot, which is why I was able to load a stock rooted sense rom.
The thing is, I'm afraid to use and RUU because Telus didn't modify their roms in anyway, so carrier RUUs don't exist, yet the phone is locked to Telus... I haven't created a gold-card yet because I haven't had to, yet I feel as though an RUU can jeopardize all of this.
Hi guys,
New to xda.. I own a defy with 2.2.2 official SEA. I want to update to CM7 RC0, without losing the downgrade ability. After reading a lot in xda, I've got a fair amount of knowledge to flash my phone. Just have a couple of queries..
6) Can I restore my phone to send it to warranty after flashing CM7?
- You can in these two situations
1 - You have a full SBF of your original ROM (for carriers that already released 2.2 is very easy to find one)
2 - You have a nandroid backup AND a fixed SBF of the version you need.
Click to expand...
Click to collapse
Quick question:
Considering option 1, I have the official ROM (full sbf, 2.2.2 for India) downloaded here. If I flash to CM7, can I re-flash it with the official full sbf to claim warranty? Considering the scenario that I only have contacts and sms to restore and I don't want to restore settings, apps and all. I like to do them anew (even if it takes time).
Technically, that would be like formatting the drive which has the operating system, instead of restoring an image.. Is that possible? Is Nandroid Backup + fixed sbf is the only way to go back to the stock OS to claim warranty?
P.S. - I still don't get what fixed sbf is. Can anyone help?
Just create a backup of your current OS if anything happens restore it.
Sent from my MB525 using XDA Premium App
ATXiceman512 said:
Just create a backup of your current OS if anything happens restore it.
Click to expand...
Click to collapse
You mean Nandroid backup? Can i restore just that file (and not the sbf) in case anything goes wrong?
If your device is rooted download the 1.4.2 version of 2ndinit go into custom recovery and create a backup, then boot back up normally and connect device to the computer and copy the backup to a safe place on your computer, so if you ever need to back it up, you will have the file.
Sent from my MB525 using XDA Premium App
I mean do I always need an sbf file to restore an image?
No you only need sbf. file to flash a image, to restore and image all you need is a copy of a backup.
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
WolVish said:
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Click to expand...
Click to collapse
Yes 2ndinit is a custom recovery program as long as you have that you wont need sbf. Files. Sbf. Files are used with RSD lite in order to install custom roms. You can use any recovery program you want, best I have found to use on the defy is 1.4.2 version of 2ndinit.
Sent from my MB525 using XDA Premium App
Mem check your message please
Sent from my MB525 using XDA Premium App
memz180 said:
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Click to expand...
Click to collapse
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
Click to expand...
Click to collapse
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
WolVish said:
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
I just restored my old nandroid and flashed with the fixed sbf but i believe if you do a full sbf it will result in the same thing both ways should work
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
Click to expand...
Click to collapse
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
memz180 said:
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
Click to expand...
Click to collapse
What i found in the Official SEA 2.2.2 ROM's thread
ok make sure you do not install CM7 directly on this rom, else boot looping.
Please follow the cyanogenmod7 FAQ point 7. http://forum.xda-developers.com/show....php?t=1065798
i tried and was stuck on boot loop.
Again FLASHED this sea15 sbf via rsd lite back to square1 now need to start the process all again.
Click to expand...
Click to collapse
Nordic is the way to go it seems..
Nice find because i just got my sea15 back i listened to someone from here like a idiot they said they were running SEA15 with cm7 which is a lie because it when i installed cm7 i got a never ending boot loop so id like to say it does not work with sea15 it took me an 1hr to restore all my stuff back to the way it was so yes NORDIC I or II is the way to go thanks for the info
You're welcome mate.. Heard review that RC0 is way better than Beta6..
Finnaly the thread i've been looking for.
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (wich is not available at this moment) of my version if I want to downgrade again.
So just to be sure:
Having a sbf is not an absolute must?
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
ShiroHouseki said:
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (which is not available at this moment) of my version if I want to downgrade again.
Click to expand...
Click to collapse
That's correct. Even if you can't find a full sbf (carrier released version of your OS, usually a large file, 200-300 MB), make sure you have one nandroid backup of your data/settings and a fixed sbf (usually stripped down version, less size <50 MB) of your current OS. This would enable you to re-flash in case you have to claim warranty.
So just to be sure:
Having a sbf is not an absolute must?
Click to expand...
Click to collapse
I don't think so. You MUST have one if you want to claim warranty. Even if you don't need warranty, still you need either Nordic ROM or UK ROM (sbf files, mind you )to be flashed first to install CM7.. Other ROMs are not recommended.
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
Click to expand...
Click to collapse
This only works If you flashed with nandroid + fixed sbf of the Nordic/UK ROM.
OR
You have the full sbf of your current ROM, which you can flash from RSD lite.
Hope this helps...
P.S. - Can anyone confirm these answers?
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
I am also confused. I thought a nandroid was a complete image of the phone and didn't require an SBF?
Putting it in PC terms I considered a nandroid the equivilent to a ghost image of a HDD? So if I had a PC with XP on it and took a ghost image of that it would be a complete copy of the drive. I could then install Vista on that drive and when / if I wanted to restore the ghost image and it would restore XP onto that system?
I understood an SBF to be a system image as such, but not including the very base level stuff that a nandroid backup would have and hence why you can flash a 2.2.2 rom but need a 2.2 SBF flashed on the phone?
Or am i getting confused?
ShiroHouseki said:
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
Click to expand...
Click to collapse
I think your German 2.2.2 ROM has been added only yesterday. Go to www.motorola.com/update, select your region - Select MOTODEFY - Follow instructions.. (Don't forget to do a hard reset after updating )
Full sbf s are released by the Manufacturers/Carriers. It's like untouched windows XP cd. You can directly update via MSU or use RSDlite to flash it..
Fixed sbf s can be made by anyone, maybe you or me, by making some tweaks, just like we do to Windows XP using nlite (which i'm still not that familiar with )