So I posted about 2 months ago with no reply hopefully I get a response this time. When I originally posted I was having trouble sbfing my D2G. I have the correct sbf file for it. I was on ICS sbfing the GB firmware back so I could install CM7. But after I finished flashing I still had the ics boot anim. And I was stuck in boot loop. I've tried using all different versions of RSD lite aswell. So today I had a R2D2 that I was doing the same thing on. This time when I sbfed the boot anim. was changeing based on the different sbf files I used (r2d2 and d2). (Yes I'm aware the d2g and d2 have different files.) I've tried them all though from froyo to GB and the A9557 R2D2 sbf. They all put me in boot loop and now both of my d2's are bricked. RSD Gets done and wants me to manually power up the phone while its looping. I boot back to boot loader and it gives me a pass. Even though it loops. I've also tried it on XP and win. 7. How in the world can I get my phones back to working order. Help help help
Sent from my NookColor using xda app-developers app
Did you try google? You tube? Moto forum? ACS ?
Pp.
Sent from my ginger infused Mayan calculator.
Related
If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo
hi is this only for US people or will it work in UK as well?
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Does it supports 720p video recording!!
vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?
Anyone can upload nandroid and sbf ?
It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App
Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!
I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz
On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.
i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.
you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.
Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk
i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.
I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk
It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App
Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.
i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Some notes:
I was the the newest CWM Recovery Version
I checked all the MD5 and they all aligned perfectly
Thanks for any help I receive, if you want to know something else about my phone data during this procedure, just let me know.
so you flashed back to.33 or .608 before you flash cm9?
Sent from my DROID2 GLOBAL using xda premium
odnanreh12 said:
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Click to expand...
Click to collapse
Hexen was made for 2.4.x stock firmware (Android 2.2 and the corresponding Motorola kernel).
All newer ROMs (CM7, CM9, Gummy, Apex, etc.) are based on 4.5.x. Update to 4.5.608 (preferably via SBF; do NOT accept any OTA updates once you're on 4.5.608) and proceed from there.
Ah thanks so much, I forgot that Android Firmware numbers had to match up, I will try again later tonight
forgot that Android Firmware numbers had to match up,
Click to expand...
Click to collapse
just fyi, not android firmware, moto's system version/firmware
Firmware must be watched
Sent from my GT-I9001 using xda premium
ok so i rooted a few weeks ago and downloaded the usual apps. super user titanium back up and clock work mod. tried to flash a rom with clock work mod and got the e:signature verification failure message. found a post for a kernal that made clock work mod actually work so i tried to flash a rom. zSimplyAOKPV5_Dark to be exact. now it sticks on boot screen. i have searched for hours and cannot find a way to fix my problem. its my first rooted android and first attempted rom flash and i botched it right off the rip. please help?
Depending on what you did beforehand, you have some options.
If you have backed everything up previously, just flash back to stock with one of the one-click stock roms in the Development section (they're in a sticky).
If you haven't backed everything up, try holding V+/V-/power until it reboots. If it doesn't take you to recovery, you can try to flash a kernel (most likely one that would match the version of android/rom you were running prior to this flash) and see if it lets you into recovery. You'll have to flash it with either Odin or Heimdall, after rebooting into download mode (power off, hold V+/V-, insert USB).
If that doesn't work, though, the stock flashing would probably be your best and/or only bet.
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
phoenixfriend said:
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
Click to expand...
Click to collapse
Flash corn kernel if you have stock gingerbread
Sent from my SGH-I897
The utility in my signature can help you flash the Corn Kernel so that you will have CWM.
I have corn kernal and odin 3 on the computer at home. Ill do that tonight. Any suggestions on a good stable rom for a noob? Preferably ics. I hated posting for fear of being flamed as a noob. My wife keeps making fun of me for it so I kinda have to get it done. I want to fix hers also. Its a great little phone it just seem a bit buggy to me. Very laggy. Thanks for all the help.
Sent from my SAMSUNG-SGH-I897 using XDA
Maybe start with a KK4 based rom such as Legend and then move up to ICS after that. I only say that because there is a bug in ICS that could render your internal SD unusable. It's rare, but when it happens you will not be happy.
Still unable to get corn kernal to flash. I've tried a few of your guys fixes but I'm gonna have to get some other updates to my computer first.
Sent from my SAMSUNG-SGH-I897 using XDA
Hi all,
As the title says I am currently unable to boot past (red) CWM recovery on my Infuse. I figure it might be easier to get help if I explain everything I've done:
The other day I tried to flash Uniporn build 37 only to soft-brick my phone because I didn't have the GB bootloaders installed (I had previously been on CM7). I managed to nandroid back to CM7 and decided I'd give it another go today.
Since I was told that flashing bootloaders is very risky I decided to flash something easier first with Heimdall to make sure everything was working right. I ended up flashing the ICS kernel in qkster's thread (one-click)... mistake #1. That bricked my phone once again and gave me rainbows in recovery.
So then I decided to try a Heimdall flash to stock 2.3.6 UCLB3 (once again, the one-click Heimdall from qkster's thread), which did give me a bootable OS despite some rainbows while booting up. However, here I made mistake #2 and tried to recover from the CM7 backup I made earlier today with the Infuse Toolkit. This completely soft-bricked my phone; I couldn't even get into recovery at this point.
So, I tried to reflash the stock 2.3.6 with bootloaders this time, only (and this may be important, not sure) it tried and failed to flash a PIT. At this point I flipped because I thought I had hard-bricked the phone. After I calmed down and came back a while later, I discovered the phone wasn't hard-bricked at all and I was able to get it into download mode after all!
I then flashed stock Froyo (I'd had enough of that rainbow ****) and it seemed to go fine... only now it wouldn't boot past 3e recovery, despite me wiping data and cache multiple times. So I flashed the community kernel... same problem, only now with red CWM instead of 3e.
So... what can I do now? I'm relieved I don't have a hard-brick on my hands, but this isn't that much better... could that PIT be the problem? I hope the info I gave is enough to help (and isn't too much either!)
Screw ICS, now I just want my CM7 back
EDIT: I should also probably note that after I managed to get CWM back I tried to flash the UCLB3 ROM in the Infuse toolkit; it said it installed but when I rebooted the phone still went straight to CWM.
EDIT 2: Another weird thing I just noticed: the phone apparently refuses to stay turned off while it's plugged into the wall to charge. If I plug it in, it turns on and goes into recovery mode. This also can't be good, since IIRC the battery won't charge while in recovery.
Just heimdall or Odin again...I've had this happen soo many time when I had my infuse...I just simply run heimdall again and its good...if you ever get recovery after heimdal or Odin...do not hit reboot...wipe everything then hit reboot...
And gingerbread bootloaders are not required for ics...I keep hearing people say they brick there phones because they don't have gb bootloaders...that is not the reason...yes with out the bootloaders you get rainbow recovery and boot up but that is it!!!
Remember if you are going to ics from gingerbread...YOU HAVE TO double flash...the first flash will not work...just three finger back to recovery and flash again from.blue/rainbow recovery depending whether or not you have.bootloaders...
Look at my infinitum port thread...it has great instructions on how to flash ics roms...as well as how I flashed gingerbread bootloaders when I had my infuse
Sent from my HTC PH39100 using XDA
Nah, I've tried that, it's more broken than that. I think I need to reflash the PIT, which Heimdall doesn't like for some reason. I followed qkster's advice in another thread but still no dice. I might have to try using a different computer.
All fixed now, I used the Heimdall one-click on a Windows machine; the PIT and everything else flashed without a hitch and I'm up and running again.
just keep trying flash different stable stock roms thru odin until u can boot..i had it happen twice nd even couldn't get computer recognize my phone for a bit thru odin but it finaly workd now I'm back on cm9
Samsung Infuse ICS 4.0.1(cm9)
I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!
Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!
Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...
Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium
I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app