Related
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)
Hello you gods and godesses of xda.
Cant anyone of you pleas share a nand backup thats been done after you've flashed the finnish 'leak'. I don't mind it there is apps or custom roms included or not. Anything will do.
Ill make a donation to who ever u suggest... provider (of the backup) or preferd developer or just a foundation of your choice!
im in a bit of a crisis..
What backup you need?
Sent from my MB525 using Tapatalk
jboogie3 said:
What backup you need?
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
a full nandroid backup. UK or preferably the finnish one. -non branded
4305ms said:
a full nandroid backup. UK or preferably the finnish one. -non branded
Click to expand...
Click to collapse
jboogie3 's rom is released as an nandroid backup. it has uk version, and it's great!
http://forum.xda-developers.com/showthread.php?t=877058
jakiej said:
jboogie3 's rom is released as an nandroid backup. it has uk version, and it's great!
http://forum.xda-developers.com/showthread.php?t=877058
Click to expand...
Click to collapse
Alright! Ill try that.. but don't you need to flash the chineese .sbf first?
The problem is that RSD cant find my phone so thats why i whant a nandroid backup to use instead..
4305ms said:
Alright! Ill try that.. but don't you need to flash the chineese .sbf first?
The problem is that RSD cant find my phone so thats why i whant a nandroid backup to use instead..
Click to expand...
Click to collapse
You are using RSDLite 4.9 and latest drivers?
Make sure you follow this steps to your RSDLite connection be successful
http://forum.xda-developers.com/showthread.php?t=853674
edition- said:
You are using RSDLite 4.9 and latest drivers?
Make sure you follow this steps to your RSDLite connection be successful
http://forum.xda-developers.com/showthread.php?t=853674
Click to expand...
Click to collapse
Yeah. Ive tried reinstalling everything and doing the steps over again and i just dont whant to work.
And just for fun ive tried flashing a 2.1 T-mobile nandroid backup that is listet in the FAQ and it worked so i thought that ive can use that method..
But thinking about it.. it might not work, right?
Ive had a Defy just a couple of weeks ago and I had no problem at all to flashing anything with RSDlite 4.9- but with this phone...
It doesn't appear.. and yes- ive been searching for an answer.
well you will have to flash with rsd lite to use any 2.2 backups, what are you running right now? if you are on 2.2 already then you dont HAVE to flash with china 2.2, you can just use the nandroid backup
jboogie3 said:
well you will have to flash with rsd lite to use any 2.2 backups, what are you running right now? if you are on 2.2 already then you dont HAVE to flash with china 2.2, you can just use the nandroid backup
Click to expand...
Click to collapse
Seems logic. But im still not getting past the problem with RSDlite. It did work on my first Defy so I thought it might had to do with a new update or somthing like that (that it could'nt be found by RSD)..
I can't see any suggestions or somthing like a check list of (other) things to do.
Can it be the W7 x64 OSystem that makes the problem?
Or is there any late firmware that wont mate with RSDlite?
God.. ive been spoiled with Hero, HD2, Galaxy S and Desire-.- This is hard work!
Problem solved. It seems somthing were wrong with the usb cabel. It did not stay connected all the time i should.. Turned on the sound and you could hear it. Sorry for desturbing with a new thread.
Mod can delete it if he/she wish.
Thanks for the support anyway and I will proceed with a donation.
Thx
glad you got it working.. let me know if you need any other help on my thread or PM
I have that problem when I plug in certain USB devices with my Win7x64 machine. It will sometimes only connect and disconnect constantly. Also, glad you were able to get it working!
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?
First poster here.
Hi I flashed a kernel from this link here
http://forum.xda-developers.com/archive/index.php/t-1513287.html
At first boot it had some of my apps, so I tried to reboot to get back the other apps, and it looked like a factory reset for my apps and home screen. So I did a nandroid restore for the backup I had right when I flashed the kernel. Now the screen is stuck at the boot, and it won't go into recovery. Any help please?
What kernel where you on before? If it was CWM 3.0 then 5.0 won't be able to restore.
How are you trying to get into recovery? What ROM?
Uhh I was on the stock kernel and gingerbread, i was on cwm 5 pretty sure, I got cwm from flashing that kernel
I'm trying to get into recovery by holding the volume buttons and the power button
How did you flash the kernel? It's a CWM flash which stock does not have. Did you heimdell it?
Not to interrupt hecheon - but follow the guide in the second link in my signature to restore your phone. And read it all for your benefit. Don't restore a backup. We can talk about that after you fix your phone.
lumin
No interruption here. Just trying to figure out what this guy did and how he did it. Could be a really simple fix. And I was gonna toss a coin to decide whether to link him your guide or juls.
Anytime time I read nandroid restore - better to start fresh. Link him to Juls' guide. He may find an easier read. I'm on the app.
hechoen said:
How did you flash the kernel? It's a CWM flash which stock does not have. Did you heimdell it?
Click to expand...
Click to collapse
I flashed it with sgs kernel flasher, I'm not home at the moment, I'll try the links asap
mtran1516 said:
I flashed it with sgs kernel flasher, I'm not home at the moment, I'll try the links asap
Click to expand...
Click to collapse
OK. Brainfart on my end. I forgot about that little tool. Follow lumins guide and you should be golden. Good luck.
lumin30 said:
Anytime time I read nandroid restore - better to start fresh. Link him to Juls' guide. He may find an easier read. I'm on the app.
Click to expand...
Click to collapse
Hey, I tried the second guide in your signature, I did everything right up to where I use Heimdall to flash. However, when I use Zadig to select my driver, and then flash, it prompts me to install my driver and open Zadig again. When I close it to try and just skip it, it just makes me wait, without any changes. I've been waiting for at least 30 minutes, how long am I supposed to wait for it to flash?
Let me know if you were able to get One-Click going. If not - try a fresh USB port that you have not plugged your phone in to yet if possible and start over.
lumin30 said:
Let me know if you were able to get One-Click going. If not - try a fresh USB port that you have not plugged your phone in to yet if possible and start over.
Click to expand...
Click to collapse
Nvm, I worked my way with Zadig, it worked
Thanks a lot man, and thanks to all the posters in this thread. You guys are great!
mtran1516 said:
Nvm, I worked my way with Zadig, it worked
Thanks a lot man, and thanks to all the posters in this thread. You guys are great!
Click to expand...
Click to collapse
What did you have to do? It might help other people that have a similar issue.
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
http://forum.xda-developers.com/showthread.php?t=1357157
This root method works wonders nothing is more better then to learn to manually root your device. Of course you can use the tool provided in the, the development forums, but I personally enjoy learning to do things without the use of developed tools.
If you need help feel free to ask we are here to help ^_^
Good luck don't turn your device into a brick READ READ AND READ FOLLOW INSTRUCTIONS EXACTLY HOW THEY ARE YOU WILL BE A OK.
Sent from my PG06100 using xda app-developers app
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Use the manual method by Indirect if you want to have more control over what you're doing (also does not void your warranty) and definitely read read read
I would recommend at least going through the whole "user" section of xda-university before even touching your phone, it has tons of useful information
turkbot said:
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
Click to expand...
Click to collapse
Definitely, also just FYI but when you do a factory restore that simply wipes all app data (both user and system apps)
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Best advice I can give you is to Read, Read, Read, and Read some more. Use the search function a ton, as it will help you to get used to resolving issues in the future. Because sometimes even when people are willing to help, answers are hard to come by. Also there are a few links you can check out in my Signature. The Shift community is one of the Best anywhere, so you picked the right device to learn Android with . Welcome to a great forum.
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
x2phrack said:
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
Click to expand...
Click to collapse
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
CNexus said:
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
Click to expand...
Click to collapse
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE or HERE.
Click to expand...
Click to collapse
Points to dead files / links
x2phrack said:
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
Points to dead files / links
Click to expand...
Click to collapse
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
CNexus said:
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
Click to expand...
Click to collapse
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
x2phrack said:
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
Click to expand...
Click to collapse
It doesn't matter, you can do it anytime after you have rooted (make sure you flash it in bootloader and not through recovery though)