I have the Motorola Pro, original firmware 2.2.2, and I have found that most SBF files dont seem to work on it. I can flash back to the stock 2.2.2 sbf I downloaded with no problem, but if I try any other sbf I get an error as it tries to reboot, then I get a Code Corrupt error on bootloader :/
I am able to still flash roms, so I have CM7, but my installs are always buggy, not starting on the recommended firmwares.
I was just wondering if anyone had a similar issue/fix for this that I am just missing, done tons of searching and had way too many near brick experiences for my liking xD
Related
My Droid X was endlessly rebooting at the red eye. I didn't have a backup or anything so I found a 2.3.13 SBF file and used RSD Lite to restore.
I got the file from a post about TBH on my droid world.
My question is, will I ever be able to get OTA updates now? The version on my phone before this problem was 2.3.15, I've tried to get updates by going to the settings / etc, but it says none are available.
My baseband & kernel numbers are the same between the two files, the only difference is the system version, ie 2.3.15 vs 2.3.13
If I can't get any OTA updates, I guess I'll try to get back to endless booting and get another phone from Verizon. Thanks for the help.
I don't completely understand the whole SBF version / baseband / kernel thing here.
But I think the issue with the above SBF from mydroidworld is that it DID NOT include updates to the kernal & baseband, it was only the 2.3.13 system files. However that works?
http://www.mydroidworld.com/forums/...mental-upgrade-2-3-15-droidx-8.html#post33274
(This leak is safe to sbf from, as it does not include baseband, kernel or bootlodear update.)
Click to expand...
Click to collapse
So my kernel & baseband were originally the ones that came with 2.3.15. But I used the SBF and put the system version at 2.3.13
I'm still very confused though, because Flash 10.1 and a few other updates were supposed to come with the 2.3.15 update. However after flashing to 2.3.13, it appears my phone has flash 10.1 and the updates intact.
You will be able to recieve updates.
Sent from my DROIDX using XDA App
Okay, so here is what happened:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fussion rom, but some how ended up with two rom managers. Anyways, I tried to reset my phone to complete stock, because I want a clean start to install a rom from.
I read the tutorial, but when I got to the part when I am supposed to flash "BL_D235...HSPart.sbf", the Start button is grayed out.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .spb I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
My phone is currently stuck at the default bootloader I believe. Black screen that says:
Bootloader
D2.37
Err:A6,70,70,00,1F
MEM_MAP Blank
Service Req'd
...
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Any help is greatly appreciated, my phone is just an over priced paper weight right now. Thanks a lot.
rhannahs19 said:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fission rom, but some how ended up with two rom managers.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .sbf I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Click to expand...
Click to collapse
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0 because the bootloader changed and won't accept the old SBF.
If you are having trouble flashing the SBF in windows then try it with THIS method. Make sure you download the SBF I provided in the tutorial because the one you have might be corrupt or not complete.
It's not a good idea to use ROM manager's for the D2 just yet afaik. If you don't have koush's bootstrap for the D2 than you are missing a vital piece of software for backing up and restoring your phone. If you came from the D1 forget (almost) everything you know. The D2 doesn't have an unlocked bootloader and thus has to be bootstrapped in order to work around this fact.
ROM managers might be useful for downloading but if you are going to install a ROM on the D2 I'd stick with Koush's bootstrapped clockwork recovery. I've never downloaded or even seen a ROM manager so if my info on them is completely wrong please correct me. But I have flashed plenty of ROMs on my D2 via koush's bootstrap and I have SBF'd about twice using linux and it's been easy sailing and I've never had any big problems.
Sorry if I'm rambling it's almost 2 in the morning and I have to be up for class at 8.
thanks, maybe its not a rom manager, but i installed clockworkmod, i guess maybe thats another bootstrap loader? i was very good at flashing winmo roms, this is a whole new game
newk8600 said:
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0
Click to expand...
Click to collapse
You mean you cant flash 2.2.0 over 2.3.2 right?
burkechrs1 said:
You mean you cant flash 2.2.0 over 2.3.2 right?
Click to expand...
Click to collapse
Yes sorry I reread my post but I didn't catch that. You can't flash 2.2.0 after flashing 2.3.20 correct.
I'll keep this short so I can get straight to the point. Was running Apex ROM on 2.3.15, and a new version is out for the OTA update that just came out, 2.3.40. Reverted back to stock everything, tried to apply the update.zip, and got an error that said "status 7." Did some reading, saw a suggestion to apply the clean Droid X image from 928droid.com. I did that, tried to update.zip, and it still wouldn't do it. I've cleared everything a couple times and keep getting the error.
So unless there's another route I can go to get the update applied (which I'd love to hear so I can avoid SBF'ing), it looks like I'll need to just SBF. Problem is, in the SBF guides I've seen, it says that the current SBF (the ~450MB one) will only work for the 30.03 bootloader, not 30.04... Well I have 30.04. So I really don't know what to do.
ANY help would be appreciated.
If you already have the 30.04 bootloader (refurb phone on 2.3.151?), you can use the system only SBF for 2.3.340.
It is a refurb that I just got with the 30.04 on 2.3.151. So I should just follow the instructions here as though I'm running the 2.3.20 leak even though I'm not?
Crap crap crap!
You can't use just the system only SBF for 340! No kernel means problems for you! Get your 2.3.151 back to bone stock and try Verizon's over the air update now that it's out. If that doesn't work I'm not sure where you go from where you are.
The OTA update doesn't work, it downloads it, goes to install it, then after getting about 1/4 of the way in it says it failed.
Try the 320 update.zip or the 320 full SBF from Team Black Hat, then do the system only SBF to 340. That should get you back to the right path.
Can you tell me where to get the 320 update.zip?
Right before the Status 7 error it says "Error in /cache/Blur_Version.2.3.15.MB810.Verizon.en.US.zip", if that matters to anyone reading.
You can look around the forums here or over at MDW, but I'm guessing all the links are long gone by now. The Team Black Hat app is a few bucks on the Market and has all the files you want, and to be honest it's worth it. Those guys do a lot for the community!
Wiped data and cache, then restored the backup from here - http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
After that I was able to update, no SBF's anywhere in the process.
Just thought I'd post because I've seen a handful of people having similar problems today.
got an error while flashing atrix 2.3.4 stock to 2.3.6 using RSD lite, can anyone help me getting out of this? will be much appericiated tnx in advance
error is:
failed to boot 4
starting rsd mode
soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.
gnahc79 said:
soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.
Click to expand...
Click to collapse
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
sunny1119 said:
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
Click to expand...
Click to collapse
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.
TravisAntonio said:
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.
Click to expand...
Click to collapse
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!
DJHile said:
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!
Click to expand...
Click to collapse
Flashing SBF's only bricks devices when people dont research what they're doing and they flash the wrong SBF or downgrade from 2.3.4 gingerbread to froyo etc etc... I flashed the 2.3.6 sbf from 2.3.4 just fine.... People just tend to want to run and dive into this stuff without getting the proper information first.
i almost did the same mistake as you ... But i read more and ask users beffore doing something . Try to use Search button and ask don't do any thing on your own .
Hello.
I'm quite new to the CyanogenMod-stuff in general, though I'm not a complete beginner when it comes to Cellphone flashing.
I have tried several CM-versions on my Milestone 2 (UK model), CM7 even bricked my phone, but I was able to revive it using RSD and an SBF file.
Ok, just as a background.
My question or problem is: NO version of CM works properly on my MS2. Mostly the google keyboard AOSP keeps crashing, the OTA updater, too and the browser won't open in any version. White screen flash, then closes.
There is a thread about all the versions (http://forum.xda-developers.com/showthread.php?t=1827801), but I can't be bothered to read 101 pages, my apologies. So, if anyone just KNOWS the answer, because it's a known bug or whatever, please let me know.
I intend to use the latest CM10.2.1 build date 28-12-2012, nightly. Are all those builds simply buggy? Is there any stable? Should I try one of the new CM11 ROMs instead? Recommendations on THE best ROM for the MS2 welcome
To run CM7 you have to do firmware downgrade with a special sbf (look for so called "Chinese kernel").
Concerning other problems you describe, I have none of these. Maybe you don't do a full phone wipe after flash (wipe everything besides system). Or you install some broken apps? Or maybe ROM zip file is broken?
rabinhood said:
To run CM7 you have to do firmware downgrade with a special sbf (look for so called "Chinese kernel").
Concerning other problems you describe, I have none of these. Maybe you don't do a full phone wipe after flash (wipe everything besides system). Or you install some broken apps? Or maybe ROM zip file is broken?
Click to expand...
Click to collapse
Thanks for your reply. Downgrade doesn't sound that good. Do we have any disadvantages by downgrading? I was hoping to be able to run the 3.x kernel on that phone...
I will look for that special SBF, if I dislike it, I flash the stock SBF again, that always includes the kernel, right?
About the crashing apps: It happens instantly after the flashing (and wiping data+cache partition) when the phone has booted. Google keyboard and browser are preinstalled. No broken apps. plus I tried several ROMs, they can't all be broken the same way. I'm pretty out of ideas, apart from that kernel thing...
As far as I know there's no working 3.x kernel for MS2.
Yes, after you flash a modified kernel, you can simply restore default one by flashing an original sbf.
MS2 bootloader is locked, that means if you want to flash another bootloader, it has to be signed with a secret Motorola key (it hasn't been released/leaked). Also you cannot downgrade bootloader. If you flashed European GB, you won't be able to flash Froyo (that can be bypassed with Chinese kernel, which is said to be signed with both Froyo and GB keys). If you flash Latin America GB, you won't be able to flash Euro GB nor Froyo. Only LATAM ROMs will be bootable.