Related
New official version stock English rom for UK v2.51.1 released.
DOWNLOAD: Defy Rom v2.51.1
thanks, but where can we find the changelog of this new rom ?
Great! Will give it a try.
might try this tomorrow, although I can't see it being anything major, at the end of the day its not been push OTA as an update yet. I just tried the supposedly "no blur" firmware too and there was still loads of blur on it!
it is unrootable for the moiment.
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
TPGamer said:
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
Click to expand...
Click to collapse
i don´t know, but i have the "deblured" 2.34.1 firm rooted with z4root and with the clockwork recovery working
Thanks, have installed and its a nice improvement.
Not a giant leep but more of a polish. I must be one of the few people that likes the email client in motoblur.
i aint going anywhere near this it its not rootable then - there nothing wrong with 2.21 imo. And I like the blur email app too lol
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
the problem is that you can not flash any older than this and without root you can not flash custom recovery and can not restore nand backup.
if you flash older the phone wont boot.
Yep now unable get root access. Oh well
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
TPGamer said:
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
Click to expand...
Click to collapse
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
andyirons said:
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
Click to expand...
Click to collapse
we need another exploit for this rom atleast
jboogie3 said:
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
Click to expand...
Click to collapse
I´ve just flashed back from 2.34.1 to 2.21.0 with no major problem.
Looks like 2.51.1 UK comes with a secret within.
jboogie3 said:
we need another exploit for this rom atleast
Click to expand...
Click to collapse
yes, indeed
ya... moto patched it.. my devices goes offline after doing the - ./rageagainstthecage-arm5.bin using the droid2root method... if only it could stay online then we could have root
what the fnck....I just flash the 2.51 two hours ago. i've try atleast 3 method to root this ...all failure....Fnck moto.....
see what they did is baited you in with "noblur" and now your stuck without root!
Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
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
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• 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)
• Once restored 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.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!
I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.
sorry to bother, but as 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?
and thank you for your work....
conradlyn said:
sorry to bother, but as 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?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.
As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?
Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf
Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?
Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as 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?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149
Thanks mate, my DEFY is perfect now.
Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!
Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy
Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?
Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?
Hi,
I have a stock rooted tf currently running 9.2.1.17. I would like to update it but it wont do ota. I tried using ota rootkeeper to unroot first but didnt work.
from what I have read it is because of the CWM recovery I am running. I used to use files from Daoist here
http://forum.xda-developers.com/showthread.php?t=1334673&highlight=updating+my+root+tf
to keep my TF up to date but he hasn't made an update for a while.
I would like to know how he made those files update-able
or
how to put stock recovery back on my TF
or any other way to update my TF while it is rooted.
Please if anyone can help me I am not having luck finding any info on this that I understand.
thanks
John
I should do use this tool then
http://forum.xda-developers.com/showthread.php?t=1689193
It is an solution for a lott of things together but you can use them apart from what i can see to
batjuh said:
I should do use this tool then
http://forum.xda-developers.com/showthread.php?t=1689193
It is an solution for a lott of things together but you can use them apart from what i can see to
Click to expand...
Click to collapse
Hi,
Thank you, I saw that thread and thought it was just for getting root. I see it is for more, looks good. I will try it as soon as I can and let you know if it works.
thank you for the reply.
John
Hi all
Sorry to bother you. I upgraded my UK Note to the German JB 4.1.1. a few weeks ago and it's been flying since. I noticed today though, that SamMobile had the German 4.1.2. version available for download (N8010XXUCMA5 / N8010OXACMA5), so I'm now in the process of downloading it.
What I need to know is, is it simply a case of me doing what I did to upgrade to JB before? I used Odin if I remember right, and pointed it toward the ROM I wanted to flash with. Is that all that's needed?
Also, do I need to backup my present setup or won't it affect my present apps when I flash with 4.1.2.?
Many thanks guys
Naith32 said:
Hi all
Sorry to bother you. I upgraded my UK Note to the German JB 4.1.1. a few weeks ago and it's been flying since. I noticed today though, that SamMobile had the German 4.1.2. version available for download (N8010XXUCMA5 / N8010OXACMA5), so I'm now in the process of downloading it.
What I need to know is, is it simply a case of me doing what I did to upgrade to JB before? I used Odin if I remember right, and pointed it toward the ROM I wanted to flash with. Is that all that's needed?
Also, do I need to backup my present setup or won't it affect my present apps when I flash with 4.1.2.?
Many thanks guys
Click to expand...
Click to collapse
Odin flash --> User Data/Apps is not deleted --> reroot (if you want)
Backup is always a good idea
Backing up your current setup is always a good idea, but I had no issue when I flashed it.
Assuming that your not rooted, use Odin or use Exynos Abuse to root and then...
If you are rooted then get a copy of Mobile Odin and select everroot.
Thanks guys
I'm not rooted at the moment. Do I need to root? I haven't felt the need to do so until now, so I'm not really bothered about rooting...
Naith32 said:
Thanks guys
I'm not rooted at the moment. Do I need to root? I haven't felt the need to do so until now, so I'm not really bothered about rooting...
Click to expand...
Click to collapse
No pressing need to root so if you don't want to, then just use Odin to flash it.
You do not need to root to flash using odin just go on the link on my signature to get the tutorial
Bulbous said:
No pressing need to root so if you don't want to, then just use Odin to flash it.
Click to expand...
Click to collapse
Great.
One more question. I swapped from a UK ROM to the German JB one. Is it an easy procedure to go back to the official UK ROM if and when ver. 4.1.2. is available in the UK?
Cheers
Yes it should not be a problem the same procedure but make sure you take a back up
Thanks all
11 minutes and counting before the new ROM is d/loaded...
Just had a look at the rooting guide (thanks Samir) and the first option looks very easy (ExynosAbuse app). If I was to use this method would I lose any functionality of the Note at all? Also, if I have to send my Note back, would Samsung object to the note having been rooted?
Cheers
I dont think mobile odin will flash the hidden or bootloaders, odin or heimdall is a better option
the exynos abuse patch doesn't work on the MA (4.1.2) builds, if you want root use cfautoroot through odin on those.
Rooting will cause issues with samsungs warranty. If you need to return a device to samsung then you need to restore it to stock rom, with no root, they are using a binary counter though that you can get rid of by using triangleaway.
don't forget to use the search on the forum for these topics, there's been quite a bit about them
Well I've followed the instructions like last time, but it won't update - it keeps saying the process has 'FAILED'
Can anyone shed any light on why I can't update???
Confirm that Kies is not running
Sent from my GT-N8000 using XDA Premium HD app
Can you post a screenshot ??
What version of odin are you using
Hi guys
Thanks for the quick replies. I must admit to being a plonker of the highest order - I never put the tablet in d/l mode did I
It's doing its business now. Roll on 4.1.2. goodness!!!
Thanks to all of you for your help
fards said:
I dont think mobile odin will flash the hidden or bootloaders, odin or heimdall is a better option
Click to expand...
Click to collapse
Does.... Less hassle with Mobile ODIN....