Related
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.
Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch
This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.
Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.
I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
bricked, verizon is overnighting one, should have a good clean one tomorrow.
SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!
Its really really really hard to brick these things. With motorola devices, you just need to get RSD Lite running (a PC program), get into RSD mode on the device and then connect to the computer. You can then flash a stock sbf file and that will bring you back to stock firmware.
I can't provide links right now but if you look around/wait for someone, you'll be just fine. The fact that you can get into CWM, fastboot and **** is a good sign. The key is to not panic and do plenty of reading on how to troubleshoot this.
Thanks for the reply. I have done a ton of reading and became a bit overwhelmed so I knew posting would be the good thing to do. I just need some guidance here. I went and snagged RSDLite 5.6 from: http://forum.xda-developers.com/showthread.php?t=1348587
I believe that is the latest version. My question is where do I find a stock sbf file for my 3G/WiFi motorola xoom?
Edit: I got my xoom connected to RSD Lite and get the following in device properties if it helps any:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x001050
DRM Version: N / A
Phone Type: Engineering (0288504140C00557000000000000)
Click to expand...
Click to collapse
What region is your device from?
My Xoom is US.
Ok, in order to have your xoom seen in RSD you need to be in RSD mode on the Xoom. In order to get there, turn it off. Then hold power and volume up and it'll get you into rsd mode. Once it says something like "starting RSD support protocol" you can plug it in and RSD lite should recognize it.
Now you need the sbf file. I'll have a look around but I swear the file was posted on these boards somewhere before.
Edit: Found a thread with a ton of different SBF files for various regions. There is a VZW 3.2.2 sbf file toward the bottom of the OP. Make sure to charge up before you flash and as per usual, I am not responsible for anything that happens from flashing. Best of luck to you!
Thanks again for the help...unfortunately the filesharing sites linked no longer allow downloads.
I will keep an eye out for the file but if anyone knows a place then please let me know !
oh damn
I'm sorry
I found this. I don't know about legitimacy but perhaps its worth testing.
Hacktually said:
I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!
Click to expand...
Click to collapse
Are you locked or not? I don't know if your stock restoration project was successful since you say you can boot into CWM recovery (stock would overwrite the recovery). Just make sure that you have a flashable rom zip file on your sdcard and then boot into CWM recovery and flash it. You're rooted so you know how to do that. FYI, you should probably do a complete data wipe/factory reset, cache wipe and dalvik cache wipe.
Why did you want to revert to stock/re-lock? Are you selling your Xoom or sending it to be fixed? If you wanted to upgrade to ICS, there a CWM flashable stock ICS rom available in the Development section.
I figured out that I was using the wrong stock img's from motorola dev. Used the right ones and now running Ice Cream!!!!!
ty for all the answers and help
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2
Hello,
i know there has been a lot of Bricked Defy posts and i've read them all. I think my Defy is really Dead.
I had my stock Defy and wanted to instal Kit Kat on it. So i followed some you tube instructions and made it work., the only problem is that i did not have Data working any more, i could make calls but no Data., So, i decided to restore my previously created nanobackup (is that how it's called) anyway, it failed, gave me some errors and my phone was then stuck on the M screen.
As i previously made it work, i grabbed the SBF i had and flashed it using RSDLite and now my phone is dead :crying:
I first thought that my battery was dead, but i have performed the MacGiver method and i can see the phone on RSDlite and i can re-flash it, but nothing happens, when the flash finishes, it reports "PASSED" and the phone remains dead.
as i read in other posts the phone is not booting because my SBF is older or something, but i cannot find any newer SBF, i have the following:
JRDNEM_U3_3.4.3-33-INESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P001_A013_HWp3_Service1FF.sbf.gz
JRDNEM_U3_3.4.2_145-012_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B5TEL03B.0R_PDS03C_USAJRDNFRYOTELSTRA_P013_A007_M003_HWp3_Service1FF
and
DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
Since had kitkat working for a while, do i have to find a much newer SBF, some newer than Kitkat or what should i do.
Any help would be greatly appretiate it.
thank you
I will follow this thread.
I think i may have the same problem
http://forum.xda-developers.com/showpost.php?p=58344502&postcount=464