Let me just start off by saying this is my first post, as I am the type to scour every thread available to figure this stuff out myself but alas, I am finally at a loss. I have found plenty of posts from people who cant flash any sbf other than JORDN_U3_97.21.51, but I am not even able to flash that at this point. I have tried just about every sbf available on and-developers/sbf:defy. At first I had an issue with CM7 so I attempted to flash the original sbf I flashed when I first got the phone (the sbf that allowed me to OTA update to Froyo and then root and flash CM7) which was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF. However after flashing to that it gave me black screens. After trying everything, I finally got it to boot flashing the JORDN_U3_97.21.51. I then flashed a nandroid backup, then a fixed SBF, and finally flashed Defy_Amoled_Green ROM after several unsuccessful attempts to re-flash CM7. I figured out I was able to flash CM7 after flashing the Defy_Amoled_Green ROM as the Amoled was giving me battery issues. Again, black screens. No matter what fixed SBF I cooked or what versions the SMG files were, nothing. I discovered after just flashing random SBF's every now and again I could get it to boot after flashing the JORDN_U3_97.21.51, but when I would unroot using SuperOneClick and reboot (because when I went to root it it would say it was already rooted, but no SuperUser on phone) it would just stick on the Motorola screen. Now, I have flashed every sbf at my disposal, attempting to re-flash the JORDN_U3_97.21.51 after every one, and I am completely stuck. The closest I can get is getting stuck at the red M logo when I flash the 2.3.6 Chinese sbf (which I know is a non-no, but Im out of ideas). Anyone else got any?
Edit* Issue most likely resolved folks. I had to cook a custom version of the 2.3.6 Chinese sbf (which had default language as German for some reason) removing the CG32 and CG45 files (radio) which got me to the default recovery screen, wiped data-cache, then flashed the same file but with CG32 added. Will try to go back to CM7 and let you guys know what happens. Hopefully this helps anyone stuck in the same spot im in.
Related
Hi,
I have a strange problem here:
My Desire keeps bootlooping with every ROM I flash, even if I flash the ROM thats currently running stable on my device for weeks now.
Its a T-MOB (debranded) wit HBOOT 0.80.0000 and AMOLED display.
I'm not using A2SD ROMs.
I can only recover the phone if I use my last nandroid backup.
I tried factory-reset from phone - bootloop. Wiping from recovery - bootloop.
Tried flashing some ROMs (including exactly the one I currently run) - bootloop.
The loop starts on the 2nd bootscreen (the animated one).
Any ideas would be helpful. I thought about applying a RUU - but if that causes a bootloop afterwards... there would be no way to recover from that I fear.
as stated in many posts, this is a sdcard problem.
formatt your card to fat32 and flash the rom. don't forget to backup important data.
Regards
Marios
Thanks for your reply mariosraptor - I did read several posts explaining that bootlooping is a sdcard issue - I reformatted the card but still get bootloops.
So I tried some different stuff - and successfully flashed several 2.1 images without getting bootloops.
Flashing any 2.2 ROM afterwards got me bootloops again, so I'm still not sure if my loops are caused by the corrupt sd.
Now I took my goldcard and flashed the stock 1.21.405.2 image (lost root during the process but thats no issue).
Do you think its safe to apply the 2.09.405.8 OTA my phone is offering now?
If its really the other sd that was causing the issues it should be safe...
Will I still be able to flash back to an old version with the goldcard (via PB99IMG.zip)?
I know that the OTA comes with a new HBOOT but I still can root it with Unrevoked afterwards. But I'm not sure if I can recover the phone if its looping after the OTA
Solved: replaced sdcard, rooted with Unrevoked, flashed 2.2 ROM - no more bootloops
Old sdcard -> trash (have been using it for almost 2 years, still from my HTC Magic)
happy you solved your prob.
Hi,
I'd like to find out why my ME525 Motorola OTA update now fails...it worked from 2.2 to 2.2.1 before, but I might have rooted and/or installed clockworm recovery and a ton of apks since then...
So here's what I get:
the OTA udate is downloaded, I get a notification that my phone will restart for installation, I press OK and after about 1/3rd into the unzipping/installation I get the picture of the Android robot and an exclamation point inside a triangle.
What do I do wrong?
I use TB to freeze the bloatware on my phone (some 40-some apks the last I've checked) so I was suspecting that it was the problem so I 'unfroze' everything in TB, rebooted and tried OTA again: same result.
Should I (or do I HAVE to?) wipe everything i.e: uninstall CWM recovery and TB before OTA? And if I do so, would re-rooting, and recover from a (TB and/or CWM) recovery backup undo the OTA update?
thanks for any help.
Rooting will stop the updates I believe and I am not sure if the recovery mod does.
It might be worth reflashing the firmware (make a backup of sms, settingst, etc)
Then with the moto bootloader format it to standard, clear cache, log back into Blur once rebooted and try the OTA again if available.
i had a similar problem with my htc wildfire. what you need to do is take off all the custom beta roms and put on the original rom. hope this helps
Thanks guys for the replies.
I've tried doing a factory reset and that didn't do it.
So I bit the bullet and finally did reflash my original sbf and as expected, the OTA update then worked.
Quite a job to bring everything on my phone back to the state it was though..
But on the bright side, I've done my first ever Defy RSD flashing and I've learned a thing or two...
And I finally have the v 2.2.2 Frozen Yogurt installed
Hi, yesterday i've installed an clockworkmod for defy from this site, but from the second installation the phone just keep restarting on the motorola logo, i didn't applyed any rom so far, i can use the phone's recovery menu, but it wont install any rom because it fails on sign check, wipe data/cache wont work too, my phone has an official froyo 2.2 from Claro Argentina D:
Thank you.
htcmania.com/showthread.php?t=161717
What are you trying to do? CWM doesn't replace the stock recovery on the defy so you can't use this to install a rom.
You will have to flash an sbf and then follow a guide on how to install the rom you want. Just check beginners guide, where you will find what you look for. The wiki page is also up to date on (almost) every rom.
yeah, but so far i know to flash an sbf, you should do it with an custom recovery thing, that's installed from an working android system, and mine wont boot D:
http://forum.xda-developers.com/showthread.php?t=966537
the first thread in dev
Read this post first http://forum.xda-developers.com/showthread.php?t=1216982
hey :3 i could get it working flashing it from USB, then installing an bootloader from the last link and installing, i just noticed i can't catch my operator's signal, but google told me that i should change the baseband, so, i did with "Defy baseband" app, everything works, thank you to you two =)
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
How to fix it:
1.Download this SBF and Flash it
2.Root your Phone
3.Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
4.Download and install this Nandroid Backup
5.Enter Recovery, Wipe Data/Cache
6.After wiping, turn off your phone
7.Turn it on and get immediately into Bootloader mode
8.Flash this Fixed SBF
9.Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
Click to expand...
Click to collapse
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
miguelco01 said:
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
Click to expand...
Click to collapse
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
root_toor said:
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
Click to expand...
Click to collapse
root_toor Thanks a lot for your response but the problem that I'm having is not that the phone is dead, the phone is in working condition right now after flashing JORDN_U3_97.21.51.rar in step 1.
I'm trying to get my phone back to stock, and while trying this fix: http://forum.xda-developers.com/showthread.php?t=1216982 I got stuck in step 4. which is to install 2011-06-11.14.14.27.zip nandroid backup. I still don't know if this is relevant to my main problem anyway.
So if I install deblur 3.4.2_177-005_nordic and follow your steps is it going to help me revert back to stock? if so in step 5) which nandroid do I need to install?
Or I should just try to install other sbf
Thanks!
Have you tried to use the Froyo 2.2 CEE sbf?
I always use this sbf when I got myself in trouble lol..
WHOA WHOA WHOA! I hate to burst your bubble dude but you just screwed up by flashing JORDN_U3_97.21.51 This is a chinese eclair with CG39.smg and CG31.smg ver=5... Not cool considering stock US Tmobile has ver=4. They will be able to tell you have blown an efuse and brought it up to level=5.
For everyone who says you cannot downgrade back to stock US Tmobile Eclair after flashing any Froyo sbf are misinformed. This is not true, stock US Tmo Eclair contains ver=4 just like all Froyo sbf's and can easily be flashed back to ( I have done it a thousand times trust me!! ) US Tmo is actually on official froyo now but there is no sbf for it. The only US Froyo sbf is the leaked 3.4.2.107-4 and is not the official Froyo which is 3.4.2.107-9. Flashing JORDN_U3_97.21.51 was the absolute worst thing you could have done! You can still get to official US 3.4.2.107-9 (34.4.9) by restoring a nandroid of 3.4.2.107-9 and then creating a fixed sbf yourself from leaked US froyo 3.4.2.107-4 by depacking the sbf, removing CG39.smg and replacing CG31.smg with CG31.smg that is ver=5 and repack it and flash. I'm actually not sure what CG31.smg you should use in this case?? Either the one from JORDN_U3_97.21.51 or the one from the full 2.3.4 sbf??? these are the only CG31.smg's that are ver=5.
The problem is that now that you have flashed JORDN_U3_97.21.51 Your CG31.smg MUST ALWAYS now be at ver=5 or above or your phone will never boot! This creates a problem for warranty because your US defy should contain one at ver=4......IF THEY ACTUALLY CHECK INTO IT THAT IS!! I would imagine that it is pretty easy for them to identify if they do look to see which level of Code Groups have been flashed. Good luck dude and let us know how it goes! While I'm thinking about it I should also mention that not only is your CG31 at level=5 but so is your CG39.smg, this is why you MUST restore a NANDROID of froyo because all froyo sbf's have CG39.smg at level=4. CG39.smg is the Code Group of the actual system. JORDN_U3_97.21.51 is the ONLY known Eclair which has CG levels=5. Once you flash a higher level of Code Groups it is PERMANENTLY burned and CAN NOT be reversed. When you tried going from CM7 back to stock you should have WIPED DATA/CACHE in STOCK recovery and then flashed JORDN_U3_6.36.0 and you would have been good to go. JORDN_U3_6.19.0 was a very early build of eclair for US defy with CG=3 and when they released an Eclair update (2.1 update 1) they changed to CG=4. You must ALWAYS wipe in stock recovery prior to flashing ANY sbf or there is a very high chance you will boot loop or black screen. I know it's too late now but I'm simply trying to help you understand what went wrong. Who knows if they will even check to see if you have flashed a higher Code Group or not????? Hopefully not
Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested
Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw
Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...
Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.
Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !
hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160