OK, so i SBF'ed to 2.1, pulled the battery when it was done, then applied the OTA update to 2.2. Worked fine, then i rooted, but was having problems with the market. All apps showed up, but i had this huge list of items waiting to be downloaded and it didnt budge for hours. So i manually downloaded DX Bootstrapper from the market and tried to install the Tranquility rom. I didnt mount the system the first time i tried to install the Tranquility rom so i went back to do it, but this time i did a factory reset, and wiped the cache, then mounted the system and installed the zip. Then i was stuck on an Endless loop of the Tranquility logo. Attempted an SBF restore back to 2.1, and this time it just failed. Now the phone only turns on to the programming screen and i get this message:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
Should i just go back to Verizon, not sure if they have this in stock, and not sure what questions they will raise when they see this screen.
Well according to a birdman twitter post:
_mrbirdman_
do not flash back to 2.1 sbf after 2.2 0ta, keys/signature check has changed, if you go to 2.2OTA say goodbye to 2.1 forever....
and then he proceeded to say...
_mrbirdman_
Please retweet, everyones about to wake up! DO NOT DOWNGRADE TO 2.1 SBF FROM THE 2.2 OTA, YOU WILL BE BRICKED! UNTILL WE GET A 2.2 SBF LEAK
So until they leak a 2.2 SBF I don't think anything you can do. =(
They've got a thread over at droidforums with a number of people w/ the same problems too.
I got the same problem Now waiting for leaked 2.2 SBF :|
wow, im screwed.
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
GoldenCyn said:
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
Click to expand...
Click to collapse
i would tell them you were doing the ota it failed then just play dumb. It almost always works.
now the problem is that there are none in stock so im either gonna have to wait for a 2.2 SBF, or a replacement from verizon (and only god knows how long that will take).
I can't believe Motorola. For a company that is just barely getting their feet back on the ground after years of crappy phones - they sure not how to stick it to the consumer. I know we are just small percentage, BUT THAT'S THE POINT. Leaving it unlocked (aka no eFuse, etc.) would not really effect them much.
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Even worse...p3droid warned that tranquility was meant to be applied over deodexed systems and the ota is not deodexed...yet.
Sent from my DROIDX using XDA App
GoldenCyn said:
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Click to expand...
Click to collapse
That's kind of crazy when you think about it....intentionally brick your phone = get a new (though probably refurbished) phone.
I suppose it would be just about impossible for verizon to determine if the phone was bricked from their update or someone that tried to sbf but gone wrong.
Sent from my DROIDX using XDA App
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
denpad2010 said:
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
Click to expand...
Click to collapse
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
As always, modder beware
Personally, I think Motorola will drop the anal attitude of locking down hardware in due time. Probably getting significant downplay from it. The number of people bricking the phones might be higher than other types? I don't know. Of course, only time will tell.
As for the OTAU. It's nice and buttery for an official release imo.
meshdub said:
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
Click to expand...
Click to collapse
Ok thanks I think I stay with my leaked froyo
You are the reason Motorola has chosen to lock these devices down. It's awful that you bricked your phone through impatience, carelessness, or imprudence, but you shouldn't expect a free replacement because you couldn't follow directions or misunderstood them. These are probably low on stock because of all the consumers like you who did this. When you think about it, you take the one you initially bought out of circulation and then the replacement which you feel that you are owed. Maybe Motorola made enough, but since you bricked yours, another customer has to wait a week longer to get their first one. Thanks for that. If you are going to attempt these modifications you need to make sure you can handle it or have deep pockets.
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
iDroidNow said:
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
Click to expand...
Click to collapse
This not true, all I'm hearing is fanboyism. What about the Backflip or the Cliq? If you root the Backflip or the Cliq you will lose your manufacturer's warranty not the carrier's warranty. It Motorola's fault not anyone else. Even on the Motorola website they call it illegal when talking about rooting the Cliq, and rooting Android in general. You will your manufacturer's warranty if you root a Motorola Android even if it's on, Verizon, At&t, and or T-Mobile. The carrier's have nothing to do with this.
Related
Figured I'd start a thread for all of us suckers that went with Unrevoked and want to back down or switch methods.
Has anyone that did the Unrevoked 2 / ClockWorkMod method of root successfully backed down to stock and / or converted to Toast?
What method did you use.
Thanks
Smac61 said:
Figured I'd start a thread for all of us suckers that went with Unrevoked and want to back down or switch methods.
Has anyone that did the Unrevoked 2 / ClockWorkMod method of root successfully backed down to stock and / or converted to Toast?
What method did you use.
Thanks
Click to expand...
Click to collapse
*raises hand*
4G still hosed. I was on Unrevoked v1 which hosed my 4G.
Did the dummy's guide to rooting found on this forum.
Still no 4G, but my MAC is now correct.
If you still have partial root try this
http://forum.xda-developers.com/showthread.php?t=715915
Might not fit your situation but might help somebody out
just use Toasts ruu to get back to stock then reroot using his guide.
p.s. whats wrong with unrevoked2, does 4g not work with it or something?
Im in a no 4g zone so.................
ifly4vamerica said:
If you still have partial root try this
http://forum.xda-developers.com/showthread.php?t=715915
Might not fit your situation but might help somebody out
Click to expand...
Click to collapse
Just did that. No go.
I have tried a lot of things to restore my 4g. I reset my MAC to original using:
http://forum.xda-developers.com/showthread.php?t=715525
I have converted to Damage Control: Still no working 4g.
I have tried basically everything I can think of including going back to stock.
At this point I think I am going to flash the original hardware and do the OTA update....then take it in and show that my 4g isn't working.
This has been bugging me for a while, and this seems like the right thread to ask this question in. If a lot of roms require Toast's root method, and Unrevoked has given issues, is there a reason that people are still using Unrevoked's root method over Toast's? Not to hate on the Unrevoked guys, but this has been bugging me.
i have tried everything, i dont know what to do!!
jonathaflores said:
i have tried everything, i dont know what to do!!
Click to expand...
Click to collapse
What EXACTLY are you trying to do?
restore 4G after using the Unrevoked 1 to update to the new firmware, but it just busted my 4g i have gonne back to stock, i am bout to take it to sprint and act dumb!!
jonathaflores said:
restore 4G after using the Unrevoked 1 to update to the new firmware, but it just busted my 4g i have gonne back to stock, i am bout to take it to sprint and act dumb!!
Click to expand...
Click to collapse
This may be the only option. I have the same issue.
As far as using unrevoked over toast, it was just the first one I used to get root when I got the phone. I went with it because it was easy. I have since used toast to install other items in an attempt to restore 4g. I will use toast in the future now that I am familiar with it.
okay, so i used unrevoked.apk to root then used unrevoked2 to flash recovery. are you saying that 4g is now completely gone from my phone?
yep sir, Unrevoked its busting 4g!!
I was using unrevoked.apk at first, as I didn't want to wipe my EVO. I had to wipe it anyway to move from the I/O account to my personal one, so I though "might as well root now." I like having ENG SPLs, and unrevoked2 wasn't out yet, so it wasn't a difficult decision.
I was terribly disappointed in every custom ROM I tried. They would run hot, the battery sucked, and they'd randomly reboot when I wasn't even touching them. I finally had enough and went back to a stock system.img with unrevoked.apk installed, and everything worked fine. I only use root to have full access in adb anyway - I don't really mess with task killers or the like. I'm not interested in a custom ROM until FroYo AOSP.
I applied the unrevoked version of the latest OTA patch last night. Let's see how that goes…
im confused. why is this just now being brought up. unrevoked has been around for awhile. I haven't heard anyone complain until now. Is it something Unrevoked has done recently, or are we just now realizing the issue?
It is a known issue. Unrevoked released a response to the OTA for users to update without breaking root. The initial release broke 4g for almost everyone who applied it (maybe everyone). They pulled the release and a day later put up a new one that works (as far as i know). Those who used the first release still have no 4g. To the best of my knowledge, no one has been able to fix the 4g issues caused by the initial unrevoked2
Edit:
Read the second bullet under FAQs: http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Why the f*** is there ANOTHER thread on this...
There's already 3 threads relating to this, one of which I made that goes into detail and another which talks about changing MAC and it still doesn't work.
There is no solution, stop making new threads hoping to find one.
If you want a solution, wait for unrevoked to announce one.
bandagraph said:
It is a known issue. Unrevoked released a response to the OTA for users to update without breaking root. The initial release broke 4g for almost everyone who applied it (maybe everyone). They pulled the release and a day later put up a new one that works (as far as i know). Those who used the first release still have no 4g. To the best of my knowledge, no one has been able to fix the 4g issues caused by the initial unrevoked2
Edit:
Read the second bullet under FAQs: http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Click to expand...
Click to collapse
ok, so this just pertains to the OTA?
cause I haven't dont the OTA.
it doesnt matter, we jut got screw, taking my phone to sprint on monday, two days to find a solution, or i am taking my phone back to sprint!!
jonathaflores said:
it doesnt matter, we jut got screw, taking my phone to sprint on monday, two days to find a solution, or i am taking my phone back to sprint!!
Click to expand...
Click to collapse
LMAO - you really think the people at your "local sprint" store are smarter than these guys at XDA?
-= User Error =-
Atrix died help me .. to upgrade 2.3 my screen freezes Atrix did not respond so I decided to reposition the rsd lite 2.2 and is no longer there and I get caught "fail boot" and I can not enter rsd support
if you upgraded to the ota and decided to rsd lite / sbf flash back to 2.2 then you are hardbricked. try to see if you can boot into fastboot by turning the power on while holding volume down.
okay do not see it immediately turns off the phone menu
Sorry to say I and into this issue last night, you hard bricked your phone and to my knowledge and a few hours of trying last night are pardon my french but your screwed. I had to get another Atrix since mine wouldn't boot into a fast boot mode.
REDFOCZ said:
Sorry to say I and into this issue last night, you hard bricked your phone and to my knowledge and a few hours of trying last night are pardon my french but your screwed. I had to get another Atrix since mine wouldn't boot into a fast boot mode.
Click to expand...
Click to collapse
how to solved it any 1 can tell me abt tht
bivrat said:
how to solved it any 1 can tell me abt tht
Click to expand...
Click to collapse
So far the only known way is to play a fool and call warranty telling a lovely story that u were updating ur phone (OTA of course) then something went wrong in the middle of the process then... BOOM... ask for a replacement.
PPL must read mainly the RED lines... there are tons of ppl bricking their phone trying to use RSD to downgrade... RSD MUST BE UNINSTALLED from your machine so you will not put ur phone in dungerous situations....
RSD should be never used... it is a tool from Motorola and regular users shoudnt mess with it.
That, my dear comrade, would be known as a Hard Brick.
A thoroughly baked brick.
i dont understand why the situation would even arise where so many people are wanting to downgrade. once upgraded to 2.3.4, wouldnt you want to stay there at all costs? i thought the update was a pretty good one from moto this time.
why are so many people going back to froyo in the first place?
RogerPodacter said:
i dont understand why the situation would even arise where so many people are wanting to downgrade. once upgraded to 2.3.4, wouldnt you want to stay there at all costs? i thought the update was a pretty good one from moto this time.
why are so many people going back to froyo in the first place?
Click to expand...
Click to collapse
People like to have paper weights... who knows
RogerPodacter said:
i dont understand why the situation would even arise where so many people are wanting to downgrade. once upgraded to 2.3.4, wouldnt you want to stay there at all costs? i thought the update was a pretty good one from moto this time.
why are so many people going back to froyo in the first place?
Click to expand...
Click to collapse
I think so many people have become used to flashing back on 4.1.26/4.1.57/4.1.83 that they maybe think they need to go back and do a clean install or something. The OTA shouldn't work on a modded phone, but maybe some people just think it's normal. We have been spoiled with what the devs have given us previously, and lots of people don't read I guess. Too excited to upgrade and flash and update and flash.......
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
floridatank said:
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
Click to expand...
Click to collapse
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
bigshotrob22 said:
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
floridatank said:
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
Click to expand...
Click to collapse
Nope! Like I said its unrootable
Sent from my DROIDX using XDA App
Unrootable...
But that doesn't mean you can't root.
SBF to froyo.
Flash the 2-part gingerbread .zips.
Flash a custom rom (Liberty?)
Or stay on the froyo kernel...
and try MIUI or Cyanogen.
Be careful and read as much as you possibly can before starting. Myself and at least one other on here with the latest iteration of the X have ended up with boot looping or totally non-responsive devices.
I have started a thread with my findings. I am by no means an expert but I do have much experience with rooting devices going all the way back to the PPC6700.
Good luck.
getting stuck in a bootloop is part of the exploration process IMHO.
At least once per new ROM I'll flash something 'just to see what happens' and end up SBF'ing back. Just make backups between steps if you aren't sure about what will happen next.
it would be nice if one of the devs or people who work on rooting or someone in the know would at least comment if we are going to get a real root with the OTA
i mean im running froyo with CM7 but i sure would like the new firmwares for all the radios flashed and then be running CM7
so if someone could give us some kind of update at least saying no one is even remotely working on trying to gain root on 4.5.596 Official OTA or that yea we are working on it but it is a ***** and taken longer then we expected
that lil bit of info goes a long ways
thanks
I am not aware of any dev working on this ATM.
I don't think rooting 596 ota is critical 2nd unit has opened up alot of new doors and the attention has shifted. However I have flashed all of drew gardens latest and ran cm4dx until nightly 47. Now I'm daily MIUI and loving it, despite locked bootloader the cdma_shadow still has alot of options.
Sent from my DROIDX using XDA Premium App
to my understanding .596 has better battery life and signals are better for wifi and cellular (at least more stable and less drops)
i do not know if this is true but i have read/heard alot of ppl saying the battery life is better on .596
after all there is a .596 for some reason and its not a lil bump from 2.2.340 its pretty big
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
m16-maniac said:
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
Click to expand...
Click to collapse
the big deal is that there isn't a readily found exploit for the ota, the pre-rooted was done with a diff. method (brute force? recompiled?) but the versions are the same regardless
no ones holding back a secret root method, there just isn't a dev interested in spending huge amounts of time to recreate what already exists
i think it would be interesting to create a batch script that sbf's a phone and installs the pre-rooted .596 but all hidden behind a random animation so the user doesn't see what's happening. if i call it a 'one click' root method lots of people who don't seem to want to take the readily available pre-rooted gb for whatever reason would likely be happy. yeah i understand that if it includes a sbf then data may get lost, but if i said in the instructions of my 'app' that it would happen and they should have backups, people would still likely use it
sorry, but i just don't understand why so many people who want root are seemingly against using the pre-rooted option, as most of them don't have the knowledge to find an exploit or a root method from scratch themselves, so they are still using the work of someone else...
<Disclaimer>I'm going out on a limb here with limited knowledge of the X. <End disclaimer>
From what I read and I don't remember where, the rooting of an X involves a 2nd init method by which it takes control of the initial init. I believe I read the original init isn't able to be exploited and this is the basis of some of the more complicated methods of rooting the X.
If someone knows more about this please correct me or chime in.
I had an Incredible prior. The rooting was more comprehensive and simple. I believe that is because the bootstrap and recovery were not as difficult to get into. That being said, personally, I may be going back to another HTC device if the folks light years smarter than me aren't interested in developing a root method like the other devices out there.
I bricked my phone by using the wrong SBF. Like a DA, I didn't pay attn and used a SBF for verizon. However, my carrier is C Spire.
I am stuck at this:
Bootloader
30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Can anyone point me to the correct SBF for C Spire to resolve this? Any help is much appreciated.
You're going to have to take it back to c spire and do a warranty return or you can send it to Motorola and they'll send you a new one back unless you're phone came with android version 2.2. If it came with 2.3.5 there's nothing you can do. Try this sbf file if it came with 2.2 http://www.filesonic.com/file/1301534444/SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks
jamcnew said:
Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks
Click to expand...
Click to collapse
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?
ngholson said:
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?
Click to expand...
Click to collapse
No, I can't get beyond the Boot loader screen.
jamcnew said:
No, I can't get beyond the Boot loader screen.
Click to expand...
Click to collapse
my advice, before admitting defeat and taking it in for warranty, i would try every damn sbf i could find and use every method you can find. whats the worst that will happen? you brick it? too late. if you can get it to boot again somehow there is hope. try the same method over and over again. keep trying everything you can. THEN report back here and let the rest of us know =D
I've been working on this since Friday. The only sbf I've come across for C Spire is SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
I've yanked the battery, tried every imaginable button combo but that damned thing is stubborn. I'll probably go and do a warranty exchange later in the afternoon today. But if anyone here can point me to another sbf for C Spire, I'll try it out before I take it in. The one above is the only one I've been able to find.
I guess being on a small regional carrier makes it a little harder to get these things.
Thanks for the responses. I've warranty exchanged it now.
The replacement is on 2.2.2. Should I leave it alone or get the OTA update? I would like to put Cyanogenmod 7.1 on it.
Leave it alone. You can't run cyanogenmod nightlys on 2.3 because the nightlys are using froyo. If you do update you'll have to find the RC of cyanogenmod to put on it because it uses 2.3.7
Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
****SOLUTION POSTED AT THE END*****
The sbf has been leaked, and is available:
Here:
http://sbf.droid-developers.org/
and Here:
goo.gl/9SdIy
JerrytheGreat said:
Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
Click to expand...
Click to collapse
I think I'm in the same boat.
Hey guys I can upload a .sbf later tonight.
Sent from my DROID2 using xda premium
Where did you get it?
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg
JerrytheGreat said:
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg
Click to expand...
Click to collapse
I have the gingerbread sbf for the droid2
Gingerbread 2.3.3 will not work-MUST be 2.3.4
Thanks for the offer, but the Gingerbread 2.3.3 floating around the Internet will not work- the SBF MUST be 2.3.4, what was just realeased as an OTA 1 week or so ago.
Now, if someone stumbles across this thread, please note you CANNOT "downgrade" the R2D2 after the 2.3.4 OTA, as Verizon also updated the bootloader. If you try to downgrade to 2.3.3, you will brick the phone until the 2.3.4 sbf gets leaked.
From what I have seen, I am one of 3 people to create bricked R2D2s trying this, now waiting for a 2.3.4 leak to bring his/her phone back from the dead.
If you are indeed looking for the VZW 2.3.3 sbf, stockroms.net has it.
-jtg
same, identical problem!!!!
Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481
MissionImprobable said:
Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481
Click to expand...
Click to collapse
Thats 2.3.3
Not 2.3.4
So it's actually not amazing.
Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...
JerrytheGreat said:
Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...
Click to expand...
Click to collapse
sadly i do believe my r2d2 has suffered the same fate as yours.. ive tried updatubg with both of the available from
stockroms . net/ file/ Droid2/ Droid2R2D2
Bootloader
D2.37
Err:A5,70,70,00,1F thou ive had several variations
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB Data Cable
this is what i get when i connect it.. it acts like its flashing but never does.... when it reboots it goes right back to the loader with same mem_map blank error
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00D237
Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.
chasehammer said:
Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.
Click to expand...
Click to collapse
Thank you, Captain Obvious, for restating the subject of this thread..
Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.
MissionImprobable said:
Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.
Click to expand...
Click to collapse
A. My batt life and stability tanked after the update, and I was fed up
B. Didn't think it through
C. I thought I could easily download the most recent sbf and reflash-but didnt check first to see its wasn't available.
D. I have a spare phone, so knew if I bricked it, I would be OK
E. I'm not shocked or mad, I'm already married, so enough told-you-so's
Same problem
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!
korydak1lla said:
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!
Click to expand...
Click to collapse
Ummmmm they dont want people to be able to root their phones.
Don't expect the sbf anytime soon as the Droid 2 is dead and pretty much nobody cares about it. :/
That's why I love me some MIUI. Also why Moto is on the bottom of my list for future upgrades. Sony is looking dead sexy about now.
Please Keep an Eye Peeled--Lots of People need this
Well this thread and about 4 others all drill down to the same issue.
We are all looking for a leaked 2.3.4 sbf for Verizon Droid2 or R2D2. Please all you people in the know keep your eyes peeled for a leak, and post the second it appears (if ever).
jtg