Hey
I tried to get my phone faster and found the [ROM][Minimal] Nothing But Speed 1.0 Thread.
I downloaded the rom that says Recommended SBF for Defy+: DEFYPLUS_U3_4.5.1-134_DFP-132 (I use it too)
Flashed it with RSD lite all went well it said now rebooting left it 5 mins nothing.
So I hit the power button wait few minutes nothing, Pull battery out for a few minutes put it back in hold the power button for like 30 secs wait few mins, no lights, no screen, no vibration, not a damn thing.
Battery was at 80% when I started and I have tried to hook up a USB wire with red and black hooked onto positive and negative as had trouble flashing last time and it said battery was low so had to do that. It wont show anything!
I should of left it as I am not sure how to fix this if you cannot even get it to start booting.
No one have any idea whats going on?
Was your previous rom a higher version than 132?
I tried to flash a 1321 rom to my defy plus which was OTA updated to 231 and it seemed to kill it. No response. Plugging in the USB cable would light the led and rsdlite would show connected. So i just flashed my 231 ROM again and it worked.
If you plug in your phone to usb and run rsdlite, see if it shows connected. If so, just flash the correct rom and it will work again.
I did try to flash the new rom 4.0.1 I think it was but got a error at boot (tried this before but used different steps this time hoping it would work) But before I was able to flash it back to 2.3.5 and it updated to 2.3.6 no problems at all.
This time it wont boot. It shows a white light if I hit the power when the USB is connected but not the charger and RSD lite did not show it was connected. Might try it a few times with different ways like connecting phone then starting it or starting it then connecting the phone see if any will read it.
Apart from that only other thing I can think of is take it back and hope they cant get it working and send me a new one. Or they will get it working and not sure what they do if its had custom roms flashed, I guess I will have to pay for the repair?
Ok got it to flash in RSD lite. I tried to flash the rom that worked last time but it still wont boot at all.
I think I may need a CM9 SBF file as I flashed the CM9 kernel and gapps or something. I did not do this last time I tried.
Would this be why I cannot flash back to the ROM that was working before?? and if so how can I get the kernel back or a ROM that will work with the one I have?
Being that the defy is virtually unbrickable, all you need to do is flash a stock 2.3.6 rom, but make sure that the CG/BL version is the same as the version you were running previously. Most probably try 132/1321 since these are the latest rootable roms. If there's a chance that you were running 231, then these roms will leave your defy dead, and you will have to flash a 231 rom. Kernel doesn't really matter, because a full stock SBF will have everything needed to bring the phone back to life.
Edit: i just realised: i hope you're not trying to flash rom zips through rsdlite. only sbfs. thought of this since you said you flashed a 4.0.1 rom which should NOT be an sbf. if you meant that you flashed the ICS rom through the clockworkmod, then ignore this whole para.
ok not sure what the version is how can I tell??
I followed the instructions on this page
forum.xda-developers.com/showthread.php?t=1432100
I think I downloaded the one that says:
NEW Latest build by Epsylon3: 16 Apr 2012
Edit:
Oh sorry I am a bit of a NOOB but where is the best place to fine SBF files for the versions I have I seen there are heaps on here but not sure what ones are right to use.
Ok I have it going again thanks. I think I must of had the 231 rom as all the rest but that didnt work.
Can I flash any rom with the 231 version??? as this is a german one not sure if that will matter but if I come into problems I might need to flash a new one.
Since you want to install ICS, doesn't really matter.
Follow the steps here to root 231: http://forum.xda-developers.com/showthread.php?t=1542956 These are full SBFs so your earlier 231 download would be wasted i guess.
Then install ICS from here: http://forum.xda-developers.com/showthread.php?t=1432100
Or some other rom if you like.
Yeah thanks, I already found that thread before had as I found out in about 30mins of installing it that it wont root.
I think I am going to keep it 2.3.6. Do you run ICS?? I tried to install it twice and got problems both times using 2 different ways and the link you posted was one of them.
What is the fastest rom?? will I be able to do the nothing but speed 1 rom now or have I upgraded to high?
I just wanted to get alot of crap off and get it a little faster but I dont want to overclock it.
I actually own an xperia play (previously used a blade), i'm helping a friend with his defy+.
Originally the plan was to root and debloat because the stock phone was painfully and surprisingly slow and laggy. In the meantime he decided to upgrade OTA to 231 (came with 1321 stock) in the hopes that the update would speed it up. Since 231 has a painful root procedure of downloading two SBFs, we then decided to go the whole hog and upgrade to ICS.
First tried Quarx's Apr 20th, but the buttons backlight stayed on. I know there's a fix for that, but then decided to try Epsylon's Apr 17th. Working fine so far. Only gripes are the lack of HWA means opera mobile etc. won't run, but making do with mini/next.
Since there is now a root method for 231, you can run any rom that uses a GB kernel. Just install 2nd init first, then boot into CWM and install a rom. Note that for the defy+, if you install the CM9 kernel, the system seems to die, so only install the CM9 rom.
99% after you switch to ICS you wouldn't wanna go back to 2.3.
Related
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Mmy defy infos are:
Firmware: 2.2.2
Model: MB525
Build: JEM_3.4.3-36-1.1
Am I able to install CM7 ? and what are the steps/tips to install it ? I also want to be able to revert back to my stock in case i needed the warranty. thanks.
hey,man hmm, here what i did works for me so give it a try,btw there are lots of topic around this on xda you could easily look around!
1:download RSD LITE
2:download the SBF (stock one,i used stock froyo)
3.open rsd lite and find your sbf
4:hold volume key + or up and power on the phone
5:now it should be the first device on the list click that and push start
6: now you are done,go to reroot your device and install Clockwork MOD recovery can find it here (http://forum.xda-developers.com/showthread.php?t=875233)
7.download the cm7.1 and put it in root of your sd card
8.boot into recovery mode using clockworkmod then wipe/factory
9.select zip to be install,select the cm7
10. now your done after flashed!
this worked for me but if you have any problem you could ask,i will try my best xD
steps 1 & 2 confused me, why i should flash froyo if i already have it ?
then skip step 1 or 2 if you firmware is already stock
ok, but what about if i wanted to re-flash for warranty ?
Flashing from cm7 to stock froyo via sbf is a non-issue
i didnt find the sbf for my build version at the sbf list here
took me 10 seconds to find it! Seriously!
http://forum.xda-developers.com/showthread.php?t=1122210
read the build#.... it is JEM_3.4.3-36-1.1
iam still a newbie, sorry!
LOL... I hope my post didn't sound rude! I promise it wasn't my intent. I try to help as much as my knowledge allows! Sometimes we all just wish peeps would browse around a little. But I understand it can be overwhelming at times! and HEY we all start out as noobs right!
nah, np
I'm trying to get to the latest version from the old RC1v2.
I believe i need to install 7.1.1.1 stable, as it has all the kernel etc, then jump to the latest nightly from there?
I installed 7.1.1.1 stable, got the dreaded boot loop, removed battery, rebooted, then installed 111121 hopefully thats right, seems ok at the moment.
picked up the dreaded overnight abttery drain again, so trying out 111123 now
7.1 stable is fine
a
.................................
Hey folks,
before I start describing my fu*k-up let me thank you for all your great work and support in this forum! It makes tinkering with your phone so much fun
Unless you achieve what I have..
Last Rom was the JB buil from Quarx. I was running the build 31.12. and wantend to update to 07.01. This is where I got stuck in a bootloop and started freaking out. I did a lot of random stuff and finally tried reverting to stock to start all over again. I tried doing this via this method here: http://forum.xda-developers.com/showthread.php?t=1807899
Now my phone does not respond at all. When I try to power it up with the Vol+ pressed, nothing happens, same with Vol-
Only response I get is when I plug it in to my PC and start RSD Lite, it shows up as a device, but without any information on the device.
What the hell am I supposed to do now?
Thanks in advance for your help (If there is any hope at all..)
I think this might have to do with the fact that I used the wrong sbf. Which one do I have to use? The last one I flashed was JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTDACH_P025_A008_HWp3_WIG144847_Service1FF
Is there a sbf that will work for sure? I don't need to downgrade afterwards..
I think you need to go MacGyver.
Your battery level is too low so you need to take a usb cord, cut it, expose the wires and connect them directly to the battery.
There are detailed guides with pictures around (I know I had to this once).
Apart from battery which seems to go dead try BL6 sbf. The one you used doesn't allow to flash CM10 2ndboot builds (BL5 Chinese eclair, which caused a lot of troubles).
Regarding battery my proposal would be an external charger or other defy. Doing McGyver you shall do it with caution.
My proposal is 4.5.1-134_DFP-137 retail Nordic from this site - defy+ fROM which causes no problems for most of custom ROMs. Anyway even after the ROM you've flashed there is no way back to froyo.
Try This
http://forum.xda-developers.com/showthread.php?t=1820282
Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??
Spersico said:
Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??
Click to expand...
Click to collapse
Try the retail Taiwanese DFP-231.
Thanks!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
Thanks dude, i've made that, but i still have problems, it helped me a lot though, since that in a moment not even one rom of the defy plus worked, except this one.
I keep dealing with the issue, but using this guide, i think i might get to the point that i want (that is... everything except the stock rom).
http://forum.xda-developers.com/showthread.php?t=1889325
Thanks!
I made it!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.
Spersico said:
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.
Click to expand...
Click to collapse
You can use framaroot instead of using the double flash method. See the new CM7.2 by maniac in the dev thread. Try it.
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.