Hi,
Newbie here and I realize that this might have been discussed before somewhere but I hope that some of you experience users will be kind enough to guide me anyway.
OK, I've done quite some reading here and recently decided to go ahead and root my ME525 [came stock with Chinese Froyo firmware build: JDGC_1.11.0 Kernel: 2.6.32.9] and that went well. I also installed Titanium backup (TB) and did full and user app only backups. Yesterday, I installed ClockWorkMod (CWM) recovery and I did a full backup (without factory reset).
So, before I factory reset and do another recovery backup [and then try other ROMs] , I would like to know these one or two things:
- Whenever I will need to restore my stuff, is it preferable to recover to a bare backup (i.e.: the backup I will do after factory reset)? or is it jus fine to recover my backup including my apps/settings?
- If the second option of the first question is fine, then what is (or is there) any point of also restoring a full Titanium backup (or user files only - please specify) since everything should have been restored from CWM right?
- What is the deal with with having to flash a "boot_only.sbf" after a change of ROM? Is this (always?) needed after (RSD) flashing a stock sbf file? and would this be needed after just doing a CWM recovery?
I'm asking all this because I don't know where to find the exact sbf files for my Chinese phone...the Chinese Froyo 'stock' file I found had CPU set at 1GHz and that is clearly a sign that this is not 'stock' since mine came in at 800MHz... Others, have already altered the sbf to match US carriers or what not..
So last question: if things go wrong, can I flash that slightly different 'stock' [droid2.2.zip] sbf file anyway, flash the boot_only (needed?) and then just use clockworkmod (and/or TB??) to get back to my stock state or current state?
I know, this is basic stuff and had been covered many times. But not having an official (and exactly same) stock sbf file worries me a little... I don't want to lose my wifi, camera flash or who knows what... and there are all those issues with firmwares incompatibilities or undowngradability...
I just want to cover my butt in case I have to get Motorola service one day (warranty repair...) since I beleive that unroot is (a bit complicated) but possible...
Anyway, sorry for long post and thanks in advance for your help on all this.
http://u.115.com/file/f38db7bb8a
0.26.0 CN froyo
http://u.115.com/file/t355594b48
1.11.0 CN froyo
Related
hi all,
Sorry I have to return my handset as its faulty I think, it crackles from the speaker all the time on the handset only, presume this is not a normal fault, i havent found it anyway .so i need a replacement.
I installed nandroid and rooted the phone when I got it, but have forgotten it all lol, I did take a backup of the original os, and i kept it on the standard sd card (2gb) .
I then took that out and did the update with a new card, kept the old one separate. So I am thinking to return to the orange rom, I would put the old card back in (sd) and then just use nandroid to reflash the rom, but then how do i remove the nandroid rooting??
also i have used backup for root users to backup everything, and will re root the new phone hopefully this will restore everything or more things, I am using modaco 2.2
thanks
another thought would chooosing the option
wipe data/factory reset restore the phone to how it came? or restore to fresh install 2.2?
also would backing up the current install using the option nandroid 2.2backup also backup all the data/apps and stuff?
thx
jason4656 said:
hi all,
Sorry I have to return my handset as its faulty I think, it crackles from the speaker all the time on the handset only, presume this is not a normal fault, i havent found it anyway .so i need a replacement.
I installed nandroid and rooted the phone when I got it, but have forgotten it all lol, I did take a backup of the original os, and i kept it on the standard sd card (2gb) .
I then took that out and did the update with a new card, kept the old one separate. So I am thinking to return to the orange rom, I would put the old card back in (sd) and then just use nandroid to reflash the rom, but then how do i remove the nandroid rooting??
also i have used backup for root users to backup everything, and will re root the new phone hopefully this will restore everything or more things, I am using modaco 2.2
thanks
Click to expand...
Click to collapse
there is a way to unroot your phone, but because you are stuck with the modified recovery img you installed you wont have a standard orange hero
my suggestion is to flash a rom with
stock recovery
stock radio
stock rom
I would suggest try using the updates HTC.com has provided for us, that should return you back to stock firmware!
"Make sure you flash correct update, I am not responsible for any bricks or damages to your phone!"
how do you mean since i am stuck with modded rom? I said I backed up my orange rom before i used the update feature of the nandroid root, so my question is about 1 restoring it, and then 2 removing the root feature?
thanks for ur advice
ok i have managed to restore to factory orange rom so never mind that, how do i remove the ability to boot to the nandroid backup/loader feature?
to "unroot" and get back to Orange stock you will need to do a full flash, use the HTC Orange Update as its Orange verified, a normall restore wont remove the Custom recovery image you have installed
ok how do i do that? thx
dont worry, have done it, but thanks
glad to hear it
job done
all sorted
thread closed
Hello,
I plan to upgrade my Australian (Telstra) Motorola Defy to an Android 2.2 (Froyo) ROM that is ideally without Motoblur.
I have comprehensively read hundblues of the Defy modding threads through Search, Browsing and Cross-Links on XDA, however there are still a few areas I am still unsure about and feel the need to ask.
I absolutely require downgrade-ability back to the Telstra stock firmware (A variant of 2.21), Because if I become affected by the Speaker issue, then I will need to restore to stock for Warranty.
I am also conscious of using the Chinese 2.2 ROM due to risk of blowing the Camera Flash LED.
Maintaining Downgrade-ability
Higgsy has made a thread how to upgrade to 2.2 (Froyo) without losing downgrade-ability, but I am not clear on a few points, my comments are in blue
Instructions in the thread:
"Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here [http://www.sorensiim.dk/higgsy/.sbf/2.2CN_SBF.zip] Is this the unmodified Chinese 2.2 ROM?
Need the system.img nandroid and boot/devtree.sbf – Download here [http://www.sorensiim.dk/higgsy/TMOB_US_3.42_Files.rar] This must be the "Tmob 3.42 system image(pre rooted)"
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear [http://www.sorensiim.dk/higgsy/GB_3.4.2_system.img.rar]
• Flash the Chinese .sbf by RSD lite OK I understand that the Chinese 2.2 ROM is downgrade-able, makes sense so far
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder) What makes this 3.4.2 ROM different from the others in that it is still downgrade-able?
• Once restoblue pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done. See below about Camera Flash LED issue
If you want to use the GB release then just restore the system.img from the GB release. Similar to the T-Mobile 3.4.2 ROM, what makes this UK 3.4.2 ROM downgrade-able?
"
If there has been a modification done to the T-Mobile / UK 3.4.2 images provided which makes them downgrade-able, what is it?
Can it can be applied to other 3.4.2 ROMs too (eg: Finland 3.4.2 155-002 which is Blurless).
Based on Which SBF code group prevents downgrade, I am guessing that the CDT(CG31) has been removed from the image (to keep CDT on version 2), but I'm also guessing that this would also screw up SYSTEM (CG39) because that would also need to stay on version 2, when 3.4.2 uses (and needs to be?) version 4 (or else it will screw up the signature?).
Preventing the Camera Flash LED from blowing when the Chinese 2.2 ROM has been used
I seem to have found two theories on this one:
1. Higgsy's 'Devtree' theory (see thread above) that the Devtree in the Chinese 2.2 ROM is causing the issue, and a Devtree copied out of a different ROM should be used. (This leads to more questions: What is the Devtree? Where is it located? How is the Devtree copied out of a ROM? I can't find any information about Devtrees)
There is a followup post in this thread in reference to the Devtree theory which says "I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?"
I am not sure if this users's reference to the "flash fix" is referring to the 'Devtree' fix or if it was another "flash fix" that they tried. Nor do I know if the user followed the instructions for this "flash fix" correctly, but it is casting some doubt if the Devtree fix is correct or not?
Also in the instructions above, if the T-Mobile or UK 3.4.2 image is flashed after the Chinese 2.2 ROM was installed, wouldn't the non-Chinese Devtree already have been installed?
2. 'build.prop' theory
The post reads:
"I was going through build.prop for some thing else and noticed these settings on my 3.4.2-145 build.
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
What are these set to for the Chinese ROM?"
There are no followup posts to this to confirm the values of the Chinese ROM, to confirm that this prevents Camera Flash LED burnout, or to confirm that this doesn't work.
Or use the downgradable method I list in my post (http://forum.xda-developers.com/showthread.php?t=977989).
That way you dont have to flash any chinese firmware and worry about camera/flash issues.
Your ROM seems to be just what I am looking for. I want to be as close to the Stock Android Experience as possible (I've tried Motoblur and it's not for me) and without the bloat.
I have a few questions about the process that Barebones uses, because I think that it's important to learn what I'm actually doing.
"2. Restore your Froyo Nandroid of choice.
Barebones: CEE3.4.2_155-002_DEBLUR.Nandroid.zip"
I guessing that this contains ONLY the SYSTEM partition, which has been taken from the unmodified CEE 3.4.2-155-002 Deblur ROM, as the SBF method would change the version making it un-downgradeable?
"Flash the fixed sbf.
Barebones: Fixed.CEE.3.4.2_155-002_DEBLUR.zip"
I guessing that this "fixed" version contains unmodified CEE 3.4.2-155-002 Deblur partitions PDS, LBL, MISC, BOOT, CACHE, USERDATA & KPANIC, but not CDT (To allow downgrade), SYSTEM (To allow downgrade, it has already been installed at Step 2 instead?) and RECOVERY (To retain Clockwork Recovery)?
"5. Reboot into Froyo; install Clockwork Recovery; copy Barbones to sdcard.
Barebones: Barebones_12-signed.zip"This must be the bit where all the modifications of Barebones itself are made? And hasn't Clockwork Recovery already been installed to the RECOVERY partition from Step 1 or does Clockwork have elements that need to be reinstalled? (eg: in the BOOT/SYSTEM/USERDATA partitions)
"Swype, Gtalk, Voice Commands, GreekIME, CarDock, Recovery, and Easy Installer -> Download update.zip"With the Extras package, can these components be installed separately or are they all installed together? Some of these extras may not be applicable like GreekIME (If the user is not Greek).
Is the Swype in the package the same as the latest Beta from beta.swype.com and isn't Clockwork Recovery supposed to be already installed?
Also, is there a way to reinstall some of the 'Removed' APKs like BlurAlarmClock, Calculator, ClockWidget, DLNA, Quickoffice, WeatherWidget (assuming that these APKs will still work on their own) or will I need to copy them before installing Barebones_12-signed.zip
Finally, you have done a great job so far and it is far better than anything else out there for the Defy at the moment, thank you.
My only bit of [constructive] criticism (and I am by no means ungrateful) is that I think that some of the Added & Value Added features of Barebones (especially the Wallpapers and Sounds) would be more suited to the Extras package (as optionals) to keep in line with the goal rather than being bundled in the Barebones package.
Barebones faqs. . .
Why its downgradable ?
This works is because the fixed sbf has partitions taken out; specifically CG31 (CDT) and CG39 (System). Reason being these are the parts of the sbf that prevent you from downgrading. So, this lets you make up the rest of a 'whole' rom using the nandroid; and bingo Froyo with downgrade.
Barebones.zip ?
Unlike some of the other roms posted here, which are nandroids, this one is based on an update-script. Meaning it just changes a stock rom into Barebones; does not restore a complete system. So a factory reset is not enough.
Why install clockwork a few times ?
Nandroid doesnt come with the app, my rom doesnt come with it; yes clockwork is installed just not the apk, so you need that to boot into recovery. Reason why, defy bootloader is locked - so recovery has to be initiated from within the android os, hence bootstrap.
Update.zip ?
If you read the build info it states that it copies all the extras to the sdcard. While Easy Installer is the only program in that update that get installed automatically. Point being you use it to install whatever you feel is missing and delete the rest.
Other apk's not in update.zip ?
Not my problem, I cant please everyone; and I'm not going to make update.zip's with every apk under the sun. The update.zip is already half the size of my rom, so . . . Barebones ? Maybe use adb to pull /system/app after you restore the nandroid and before Barebones. You could then copy them back to the /system/app folder after Barebones is installed. If you try to install the apk's before Barebones they will be erased by my update-script. To be honest I probably didnt include most of these apk's because they must be installed to the /system/app folder (eg: MediaGallery, BlurAlarmClock). They just wont install to /data/app.
But its not Barebones . . . .*tear
OK I get it guys, my 380kb of extra noise's offends, so wait for v1.3 if its too much. This is my first android phone, I got it in December; I learned to cook this rom in that time (so google and read). So lets face it, I make this rom for my phone; just sometimes other people like it too.
Hope this clears up a few things . . . and enjoy the rom.
What is nandroid and how to use it............is it a modification of the android and is there any risks in it???.............
It is a backup image of android phone system, like a ghost image of pc. You need clockworkmod aka recovery to restore a nandroid backup. There are several recovery for defy, all working essentially the same.
Just read more before you do anything. You don't want to get stuck in something or a heart attack when the phone has apparently "bricked"
A bit OT but I need the stock Nandroid to flash my Defy since I got a terrible acoustic ear speaker and need to send it in for repair.
Sorry for jumping in like this but I am quite desperate, I cant sem to find an stock blured nandroid backup anywere and .sbf doesn´t seem to work if CM7 is installed...
Again, sorry.
I recently updated by Defy (UK) to Froyo using the full sbf – JRDNEM_U3_3.4.2_177-005_NORDIC. Foolishly I didn't do my research regards down grading. My Defy original had Eclair JRDNEM_U3_2.21.0. The phone then developed a common hardware fault (ear piece failed) so I now need to restore the original version of Android otherwise the warranty will be invalid. I've search the web for several days and tried several method to restore it (I do have a nandroid backup of my original installation).
Reading several forum posts it's unclear but I don't think it is possible. Could somebody with a little (it won't take much) more knowledge verify that once you have flashed using a full SBF for Froyo it is not possible to return to Eclair (Build 2.21).
Any help would be much appreciated.
Restore nandroid, wipe, reboot while holding volume key up flash fixed sbf, unroot and wipe again
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
How to fix it:
1.Download this SBF and Flash it
2.Root your Phone
3.Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
4.Download and install this Nandroid Backup
5.Enter Recovery, Wipe Data/Cache
6.After wiping, turn off your phone
7.Turn it on and get immediately into Bootloader mode
8.Flash this Fixed SBF
9.Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
Click to expand...
Click to collapse
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
miguelco01 said:
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
Click to expand...
Click to collapse
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
root_toor said:
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
Click to expand...
Click to collapse
root_toor Thanks a lot for your response but the problem that I'm having is not that the phone is dead, the phone is in working condition right now after flashing JORDN_U3_97.21.51.rar in step 1.
I'm trying to get my phone back to stock, and while trying this fix: http://forum.xda-developers.com/showthread.php?t=1216982 I got stuck in step 4. which is to install 2011-06-11.14.14.27.zip nandroid backup. I still don't know if this is relevant to my main problem anyway.
So if I install deblur 3.4.2_177-005_nordic and follow your steps is it going to help me revert back to stock? if so in step 5) which nandroid do I need to install?
Or I should just try to install other sbf
Thanks!
Have you tried to use the Froyo 2.2 CEE sbf?
I always use this sbf when I got myself in trouble lol..
WHOA WHOA WHOA! I hate to burst your bubble dude but you just screwed up by flashing JORDN_U3_97.21.51 This is a chinese eclair with CG39.smg and CG31.smg ver=5... Not cool considering stock US Tmobile has ver=4. They will be able to tell you have blown an efuse and brought it up to level=5.
For everyone who says you cannot downgrade back to stock US Tmobile Eclair after flashing any Froyo sbf are misinformed. This is not true, stock US Tmo Eclair contains ver=4 just like all Froyo sbf's and can easily be flashed back to ( I have done it a thousand times trust me!! ) US Tmo is actually on official froyo now but there is no sbf for it. The only US Froyo sbf is the leaked 3.4.2.107-4 and is not the official Froyo which is 3.4.2.107-9. Flashing JORDN_U3_97.21.51 was the absolute worst thing you could have done! You can still get to official US 3.4.2.107-9 (34.4.9) by restoring a nandroid of 3.4.2.107-9 and then creating a fixed sbf yourself from leaked US froyo 3.4.2.107-4 by depacking the sbf, removing CG39.smg and replacing CG31.smg with CG31.smg that is ver=5 and repack it and flash. I'm actually not sure what CG31.smg you should use in this case?? Either the one from JORDN_U3_97.21.51 or the one from the full 2.3.4 sbf??? these are the only CG31.smg's that are ver=5.
The problem is that now that you have flashed JORDN_U3_97.21.51 Your CG31.smg MUST ALWAYS now be at ver=5 or above or your phone will never boot! This creates a problem for warranty because your US defy should contain one at ver=4......IF THEY ACTUALLY CHECK INTO IT THAT IS!! I would imagine that it is pretty easy for them to identify if they do look to see which level of Code Groups have been flashed. Good luck dude and let us know how it goes! While I'm thinking about it I should also mention that not only is your CG31 at level=5 but so is your CG39.smg, this is why you MUST restore a NANDROID of froyo because all froyo sbf's have CG39.smg at level=4. CG39.smg is the Code Group of the actual system. JORDN_U3_97.21.51 is the ONLY known Eclair which has CG levels=5. Once you flash a higher level of Code Groups it is PERMANENTLY burned and CAN NOT be reversed. When you tried going from CM7 back to stock you should have WIPED DATA/CACHE in STOCK recovery and then flashed JORDN_U3_6.36.0 and you would have been good to go. JORDN_U3_6.19.0 was a very early build of eclair for US defy with CG=3 and when they released an Eclair update (2.1 update 1) they changed to CG=4. You must ALWAYS wipe in stock recovery prior to flashing ANY sbf or there is a very high chance you will boot loop or black screen. I know it's too late now but I'm simply trying to help you understand what went wrong. Who knows if they will even check to see if you have flashed a higher Code Group or not????? Hopefully not