I was attempting to flash the sbf last night and when rsd was finishing up I received a pass on rsd but my phone came up with the error" failed to boot 4 starting RSD mode" . I have reinstalled drivers ,reinstalled rsd lite , tried it on two different computers and used two different cables all with the same result. I also cannot get into any screen other than this on my phone as holding the buttons does nothing but stay on this screen. Anyone know what to do with this error?
gkeller16 said:
I was attempting to flash the sbf last night and when rsd was finishing up I received a pass on rsd but my phone came up with the error" failed to boot 4 starting RSD mode" . I have reinstalled drivers ,reinstalled rsd lite , tried it on two different computers and used two different cables all with the same result. I also cannot get into any screen other than this on my phone as holding the buttons does nothing but stay on this screen. Anyone know what to do with this error?
Click to expand...
Click to collapse
Did you receive the update, then attempt to SBF back to froyo?
I was attempting to sbf to install gingerbread hoping I would catch the ota last night . I was running the Affinity Rom at the time of flashing .Here is the process RSD is going through :
1. Phone (0000) Creating Image File
2. Reboot
3. Phone (0000) Interface AP-OS Flashing code group (group numbers ascending till it gets to group 65
4. Reboot
5. Switching device to BP pass through mode while rebooting
6. Interface BP Flashing Code group 5
7. Reboot
8. Phone is being rebooted (at which point always says Executed 26% then immediate 100 and PASS is on screen, phone still has Failed to Boot 4 Starting RSD mode
I had the same problem all day yesterday and fixed it by uninstalling the moto drivers and rsd lite then reinstalling them. make sure you have the newest version and reboot your computer after they are installed
I did try that several times and still was getting the same error . I posted in another forum and someone had walked me through going the linux route and ended up with still the same error .This is from the command:
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG02: 100.0%
-- OK
>> uploading CG03: 100.0%
-- OK
>> uploading CG39: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> uploading CG56: 100.0%
-- OK
>> uploading CG58: 100.0%
-- OK
>> uploading CG59: 100.0%
-- OK
>> uploading CG60: 100.0%
-- OK
>> uploading CG62: 100.0%
-- OK
>> uploading CG65: 100.0%
-- OK
>> rebooting
[email protected]:~/Desktop$ sudo ./sbf_flash VRZ_MB870_DTN-14.8_1FF_01.sbf
SBF FLASH 1.23 (mbm)
Perhaps your SBF file is corrupt? Try re-downloading a fresh SBF.
I tried three sbf files from different sources and still no dice. Ive tried pulling sd card , with it in, two different charged batteries, 3 different cables ,2 different computers , linux and rsd , reinstalled drivers and rsd 5 or 6 times .Nothing is working ,this is so frustrating ,especially since this thing isnt even a month old yet. Im at a loss as to what is wrong .
Still have been trying to flash with all kinds of different methods, anyone have a idea or seen this before?
I'm having the same problem on my Droid X2. I backed up all my media onto sd card and removed before I began any of the sbf flashing process. The phone was running 2.3.4 and i accordingly downloaded the latest 2.3.4 sbf and flashed it. Now I'm where you are, the phone does nothing for 15 - 20 seconds then reads Failed to Boot 4 and Starting RSD mode. I haven't been able to try anything else yet, because my battery is too low, with 3 batteries and a desktop charger en route. Have you had any luck yet?
Quote from OP on anther forum "Just wanted to update this post. I received my new one from Verizon today . However I saw the new sbf that was posted and thought what the hell I will see what happens before I send this other one off and of course it worked . So now I guess ill have to call verizon and act dumb and tell them my old one magically works." So I would say try a different SBF file. Maybe go back to 2.3.3 and then update?
Just a quick question on the occurrence of real bricks with the x2? Anyone ever hear of one or experience one?
Have never seen real bricked x2
I think ur problem was ur battery not charged enough.
This error seems to come up time to time and I've seen it remedied by getting new battery or charging the one u have somehow.
ashclepdia said:
Have never seen real bricked x2
I think ur problem was ur battery not charged enough.
This error seems to come up time to time and I've seen it remedied by getting new battery or charging the one u have somehow.
Click to expand...
Click to collapse
Had the same issue. Battery was fully charged. I can't pinpoint what the cause was.
Sent from my DROID X2 using Tapatalk
Just in case someone has this issue and comes up here like I did, here's what finally worked for me.
I was coming off of 2.3.5 Eclipse 2.2.1, and tried to sbf to 2.3.4. I was stuck through multiple boots, unable to enter any kind of recovery. I finally decided to try a different 2.3 version (went with the 2.3.5 sbf) and it knocked it loose. The world is good again.
Related
Just got my workphone, Droid 2 Global. No stranger to flashing droid phones (my personal phone is a Captivate) I just had to flash it. I mucked it up once or twice flashing Droid 2 Roms on it and needed to get it back to stock. I know a few people have asked about recovering the Droid 2 Global but I haven't seen any instructions to that effect, so here goes:
Droid 2 Global Return to Stock
1. Download RSD Lite 4.9 - http://www.mediafire.com/?ufxs9lft9q2xwnu
2. Download DROID2WE_X6_2.4.29_FULL SBF - http://www.megaupload.com/?d=MD5K1YY8
3. Download Motorla Drivers - http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
4. Install RSD Lite 4.9 and the Motorla Driver software. Unzip DROID2WE_X6_2.4.29_FULL to a convenient location, i.e. Desktop.
5. Shut off your Droid 2 Global, unhook it from USB or the AC adapter charger.
6. With the phone off, slide open the keyboard, hold the UP ARROW key on the keyboard and hold the power button. This puts the phone in Recovery mode. The screen will display white text and say something to this effect: "Bootloader D0.11, Battery OK, OK to Program, Connect USB Data Cable."
7. Start RSD Lite by clicking on the desktop icon, this brings up the GUI. Click the ellipse (...) next to the Filename dialogue box. If you put the DROID2WE_X6_2.4.29_FULL SBF file on the desktop, scroll down and select it and click Open. The File Properties box should populate with information about the SBF file.
8. Hook your USB cable to your phone, the text on the display will change. Click the Start button and have patience, this takes a while. RSD Lite will extract files to your desktop and begin flashing your phone. Do not interrupt the flash at any point or you will most likely have as nice paperweight.It takes roughly 5 minutes to flash the default rom and RSD Lite will reboot your phone.
9. If the Reboot fails and your phone loops through the starting animation. Pull the battery and put it back in.
10. Slide open the keyboard on the phone, hold down X on the keyboard and push the power button. This puts the phone in Recovery mode. You know you're in recovery mode when you see a triangle with a yellow exclamation and the green android logo.
11. Hit the Search magnifying glass key, this brings you in to the actual menu. You use the Volume Up and Down to navigate here and the Camera button for enter. Power button exits. Use Volume down until you get to the entry which reads Wipe Data/Factory Reset, push the Camera button. This will wipe your data and cache, I had to tap the OK button (The four little square button on the touchscreen) While it was running because the progress bar would stop. Your milage may vary. After it finishes, select the first menu option to reboot and push the Camera button.
That's it in a nutshell pretty much, let me know if I missed anything.
I've been trying to do this all day. My husband installed Liberty on my phone last night and forgot that it was a D2G, so of course it's all kinds of buggy. I'm trying to revert back to stock to try to properly install Liberty on the phone, but I can't get past the RSD Lite section. It keeps telling me "Failed Flashing Process 0x7100."
I've read a few forums about this issue and tried everything I could find. I'm running Windows 7, have run RSD lite as administrator, changed compatibility to Windows XP, moved the sbf file to every folder mentioned, moved RSD lite to the desktop, etc etc. I've also rebooted, uninstalled, reinstalled, in every fashion I could think of.
This is what I get when I check the error log:
17:01:30, May 03, 2011
Line: 868
ERROR: \\?\c:\users\user\downloads\droid2we_x6_2.4.29_full.sbfuèá contains an invalid path.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
17:01:30, May 03, 2011
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
I'm not sure what it means because most of the errors I've seen for RSD lite have been "was not found."
Any suggestions?
Also, I don't know if this is connected (I think it probably is), but for some reason when I plug in the phone it tells me MTP USB driver installation has failed. Each and every time.
Should I try to flash Fission over top of Liberty?
Thanks.
At first glance, i'd say to check the filename. There looks to be a space in what you copied from the errorlog, in the word full. Secondly, i'd redownload the SBF file, it's possible your download is corrupt. You can also try uninstalling and reinstalling the Moto software, it should install the drivers properly in recovery mode. I have windows 7 64bit and did not have to do anything other than what's in my directions.
Shorten the name of the SBF. Like - d2g.sbf for example. Put the SBF in c:\ and let RSDLite look for it there. It is known not handle well long paths or spaces in file name.
Is this supposed to put the phone back at original stock settings with no apps and everything? I can't find any videos of this, but the Droid X sbf guid it leads you back to the touch the android new out of the box screen. I followed this guide and when my phone rebooted, it had all my apps and widgets and stuff still, the only thing that was different was the firmware version had gone back down.
Nevermind, I somehow skipped the last few steps, I must be really out of it, ignore me.
i flashed it twice now and updated it. both times while flashing it told me to restart the device manually and when i did no change, so i closed the rsd and hit ok when it warns me of damaging my phone. phone was already on and running at the time.
Now i cant get my wifi to connect, it authenticates, then goes straight ot disconnected and then trys again.....any ideas of why this is happenning?
Did you follow steps 9-11?
What terrigan said. If you didn't do the last steps, then your phone will maintain all of its settings, but it will revert to the old firmware, 2.4.29 which is what I initially did. I believe that firmware has buggy wifi to say the least which might be the cause of your problem. You should do steps 9-11 and then after that go to settings, about phone, and system updates, and update to 2.4.330
Awesome!
Thank you for the post! You are awesome. Like a noob, I messed up my phone wile rooting/bootstrapping it and couldn't download from the marketplace, get updates installed etc. This fixed it all and I'm back up and running!
No prob, Wish there were more ROMs for the D2G though.
Worked like a champ, thanks!
Thanks muchly! Now that D2G Gingerbread is available, I'm reverting in the hopes to get the OTA update. Just waiting for the stock SBF to finish atm, will let you know how it goes..
Were not going to get the update until a couple more weeks...
Sent from my DROID2 GLOBAL using XDA App
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Chenoaem said:
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Click to expand...
Click to collapse
The steps and the RSDLite software will, you will need to find an SBF for your phone.
Droid 2 (Non Global) SBF: http://www.multiupload.com/R6VS5FFISB
I take no responsibility if this bricks your phone.
failed flashing process?
Hey, I was trying to revert my phone back, and while running RSD Lite, it got to 100% then it said that the flashing process failed?
the status came out as:
"Failed flashing process: Failed flashing process: Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected"
help please?
Is there a reason why this would work on one phone but not another? I keep getting a failed on one phone with RSD lite I get code error FEBE 0047. I search and says not compatible software, doesn't make sense. Phone stays in boot loop.
thanks for any help.
Hey guys,
Here's my story:
Just bought a brand new D2G from a friend who likes to waste money...he tried to root it using a D2 rom, and gets the bootloader error. I bought it off of him for $50.
Flashed back to the SBF file in the first post, and then I got a message saying a new update was available. It downloaded on the phone, installs, the phone reboots and I saw the android green robot logo with a box, and a status bar. Once it hit 100%, the phone rebooted again, and to the bootload error said "code corrupt, insert data cable"
Tried holding X and power button to go into recovery mode like I did before, but it just boots to this screen....
Battery just died too, so I had to take it to a verizon store where they are awfully kind to recharge it for free.
Any help is appreciated, otherwise I'm just re flashing back to the rom in the first post again, and never updating the phone!
Jon
Find the .330 D2G SBF file and that should solve your problem I think....
Sounds like the update corrupted during install or download.. theres a .330 sbf try it like the above post stated make sure its fully charged low battery can cause major issues
So...I welcome all the NOOB comments but in reality I'm hoping to learn from the wise ones in this field. I bought a Dell streak for learning purposes (own an MotoAtrix) so that I can really get behind the weels of learning android the meant it was meant to be FREE so here's my problem so far with with the dell streak. Since it got updated to the ATT 2.2 build 353 it has been restarting on it's own any time after 4-6 mins of real usage. I can leave it on it's own charging or just on standby and no issues but it freezes and resets itself to then hang on the Dell Logo before the colorful Dell Logo. Now here's the steps I've tried to resolve. like i said I want to learn not a solution to my problems.
I tried first the simple get in and reset from the Settings screens. reset still issues.
Then I tried a hard reset and still issue.
3.) I tried uploading the "Update.pkg" and then it tells me Update.pkg.dec out of date error 7....resets back to 2.2
after 5 mins of usage resets on own and hangs on dell black and white logo.
keep in mind sometimes the hang is so big I have to do a battery pull for at least half hour to get it back (makes me think that there's something going on with flash memories sort of like bios on a main computer)
replace battery restart and back to 2.2 reset okay tried to root with superoneclick 1.7 and it gives me this as I tried to root...and keep in mind I've tried both way trying to get the password first and then doing the super rage root.
GET UNLOCKED CODE SCRIPT
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Preparing to copy nv_data.bin to sd...
OK
Copying nv_data.bin to sd...
/efs/nv_data.bin: No such file or directory
OK
Pulling nv_data.bin...
OK
Reading nv_data.bin...
Unlock Code: OK
then I went ahead and tried to root.....and got this message...
so no luck still having issues reseting..so I went on to the next step...MULTIFLASHER RECOVERY TOOL v.08 wich by the way is super sweet for someone to come up with this....but I do this still (SR #11) option and still once it resets it hangs in the Dell black and white logo screen. I guess another half to an hour battery pull. Hopefully I've given enough info or detail for someone to guide me in the right direction. as the next step from this is getting more android devices to root and modify to learn the process better before I start hopefully someday writing my own rom. Thanks Everyone!
Read this post all the way through:
http://forum.xda-developers.com/showthread.php?t=1292859
Basically, flash the recovery for a stock rom, i.e. 354
upgrade from update.pkg
See if this fixes your issue.
Going to try this as it has been sitting on standby with out a battery for about an hour now so hopefully it will start no probs will post results from there. Thank You Much will reply once I have results in the AM
UPdate...
SO I tried your suggestion and I'm stuck at the point of adding the Drivers manually, (which may be the reason why flash and the rooting didn't work to begin with since it's not recognizing the device in the port that is connecting to. I've tried all 4 ports on this toshiba but guessing that I'm running a 64 OS also may be the reason for the issues. but I've tried adding the Qualcom HS USB Diagnostic device 9002 and I get the following error.
Driver is not intended for this platform and for some reason it always wants to assign driver for Qualcomm Diagnostic device 1937, if you know the manf of your device please contact ... yeah right like DELL will know how to fix this issue. So once I hit close it just gives it a Com14 or Com# depending on what port is plugged in.
64-bit OS has nothing to do with it, since I can successfully run Fastboot commands on my 64-bit Windows 7 laptop without issues.
I believe your best approach is to intall Dell's sync software from Dell.com if you haven't already done so. That has the proper drivers for the Streak as well as creating the registry entries for the drivers. Once installed you actually can uninstall the sync software if you wish and the drivers will remain.
After that, do NOT run SuperOneClick or ANY one click rooting solutions. The recommended procedure is to copy Superuser.zip to the external SD, then flash Streakmod Recovery. Complete instructions and the Superuser.zip file can be downloaded here. Too many issues have been caused by one-click solutions, while the Superuser.zip/Streakmod Recovery method works flawlessly.
reinstalling the sync method...
I had already installed the sync software from dell and it was not connecting before I tried all the other methods I even tried reinstalling and have the program try to self fix install errors. So I'm going to uninstall completely and then reinstall see if that works. off tomorrow so i'm going to be burning the midnight oil to get this fixed am i crazy to think this is fun...? or is it the nerdiness in me that finds the challenge of restoring a hanging on a dell logo unstable 2.2 on a dell streak fun?
If I read correctly on the link that you posted, in order for me to do the streakmod recovery, I must have the streak rooted, now here's a problem with that since the computer hasn't been able to install the drivers I haven't been able to root the streak, and it keeps reflashing itself at boot to stock recovery so I don't get custom recovery boot. I will keep trying and post any updates or resolved issues in the hope that this can also help anyone out there. Thanks for all the imput I appreciate it!
Chamo4u2 said:
If I read correctly on the link that you posted, in order for me to do the streakmod recovery, I must have the streak rooted, now here's a problem with that since the computer hasn't been able to install the drivers I haven't been able to root the streak, and it keeps reflashing itself at boot to stock recovery so I don't get custom recovery boot. I will keep trying and post any updates or resolved issues in the hope that this can also help anyone out there. Thanks for all the imput I appreciate it!
Click to expand...
Click to collapse
Rooting and custom recovery are two separate things. You need a custom recovery to root using superuser.zip. You said it keeps rewriting the recovery when you reboot. I take it you have been able to flash recovery on it? If so, flash StreakMod again and instead of rebooting, pull the battery when finished. Put the battery back in and hold the volume keys (both) while powering on the device. Choose option 2 and you'll boot into streakmod. From there you should be able to flash superuser.zip and/or a custom rom. Note: Nearly all, if not all, custom roms are prerooted.
If you have flashed a custom recovery, what makes you think you have driver problems?
well...I tried the Multirecovery tool to try to get the Streakmod recovery on but when I tried to retry to load the streakmod.zip I couldn't get the other files on the sd but only the option to load from .pkg so I was under the assumption since I couldn't get the custom flash tool to read the zip i wanted to load that it didn't work. but here I go again. another thing I'm trying to start fresh I just formatted the sd card and I'm going to start fresh. will update once I try the next step. Going to load the right files onto sd then streakmod with multirecovery tool and then try to boot into streadroid by pulling the battery out and not letting it self reboot.
Under the advanced option in streakmod is an option to mount your sd card. Choose it and your sd card will appear in windows explorer.
You do not have to have root to flash and use StreakMod - you do have to flash it and then either reboot using the fastboot command and go right into recovery mode or do a battery pull and restart.
some reading:
Using StreakMod
Prevent overwriting of custom recovery
So...update...I tried to multirecovery tool option 11 Streakmod recovery in fastboot mode it kept giving me this message cant upload/admin user/... then it would proceed to succesful... so thinking that it successceded so I figure lets try this one more time load from sd update.pkg
message given was...
Assert failed: !less_than_int(1297160324. getprop("ro.build.date.utc"))
E:Error in /sdcard/update.pkg.dec
(Status 7)
E:Can't mount CACHE:recovery/log
E:can't open: recovery/log
it restarted gave me the good ol white and black dell then the multicolor flash and then hanged on the white dell logo for 10 mins before i decided to pull the battery and see what now.
UPDATE: i did a battery pull for 20 mins restarted and it finally booted into froyo 2.2 (att rom) hmmm...? now to finally root to a more stable and better rom let the rooting and modding begin! hopefully this wont be an issue still wondering why it said error on this and status 7 anyone?
here's the problem with doing that. Something is putting such a drain on the phone that by the tim i have to boot if I don't give it a good five to ten mins to reset when I do reset it hangs on the dell screen or when I try to boot into a flash recovery mode it only gives me the stock recovery screen....? confused at this point where to go from this point. but if I have to brick I have to brick and rebuild again here's the current numbes.
android version 2.2
baseband version GAUSB 135331-US
Kernel 2.6.32.9 perf
OEM version GAUSB 135331
Build 15697
without touching it or using any features that would use the GPS it hasn't reset for over an hour 1:45 time on to streak mod preferably something more stable than the ATT Rom
I tip my hat to you. I am happy to see someone wanting to genuinely learn how to mod their streak without being spoon fed every answer. I have been getting sick of seeing all the incompetencies on the Streak forums. Thank you for brightening my evening with your desire to learn.
Good luck in your Streaking endeavours.
Sent from my Dell Streak using XDA App
Only way to learn is to actually do something...you can't learn to fly if you don't jump, but I'm pretty sure that when people slam into the ground I'm sure they had more imput on how to stay in the air longer or eventually to not slam back into the ground...Question if I change the rom that I put in the sd card and relabel it as update.pkg with the stock recovery will that give us bad results aka as BRICKING the phone my question really is the rom more like the OS on a pc system and the recovery more like a bios?? reason why I'm asking is this streak is so unstable at times that I have to do battery pulls for hours before I can get a full restart. So I wanted to load a rom in there and restore from update.pkg but start with a rom that doesn't use as much system such as 1.6 to see if the reset comes from having a 2.2 that from what I've read ATT never tested enough to send out. to see if I could actually use it or if it's hardware causing all the restarts (guessing a bad internal sim) from what I've read. And thank you to everyone's imput that has made me learn a ton about this device. hopefully someday I can use it as my main device but working in a market where I'm required to have a working cell for straight 9 hours means I'm pushed to the awesome atrix wich I have to say it's a tough lil phone. Again thank you and to streaking I go!
so the Streak has gone streaking...
Apparently is not what we were doing wrong but we really had a bad streak The cpu was overheating anytime it had real heavy load on it and it will shutdown and reset over and over and over as it kept restarting everytime it needed to cool down so DELL AMAZINGLY HAS STEPPED UP and sent me a replacement device! since the STREAK is no longer being replaced they are sending me a Venue HEY I could complaint but the fact that it was out of warranty and they are doing everything in power to replace the unit wich should arrive soon is the only reason why I'm not continuing on working on the streak but!!! streak and Venue look like they are carrying the same software so ON TO A MORE RELIABLE PHONE AND MORE LEARNING THANK YOU FOR EVERYONE AND THEIR IMPUT! I can't wait till I have a flashed Rom at work and people say WAIT MY ANDROID DOESN'T DO THAT! SO ON TO LEARNING OTHER THINGS BY READING! ANY GOOD GUIDES TO READ OVER ALL PLEASE PLACE YOUR " YOU SHOULD READ THIS TO LEARN MORE ABOUT THE WORLD OF ANDROID DEVELOPING"
Hello,
I'm a little bit at a dead end after trying so much things.
My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).
After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.
Then I send it in for the third time and now I have the third mainboard in my phone.
Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.
Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.
So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold
So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.
GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...
Then I discovered the next problem...
Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...
I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.
Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.
RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.
RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".
I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf
Then I found hints, that others were in the same boat and were able to recover from this error flashing this image
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf
But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.
Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.
Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...
After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...
I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?
I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...
Best Regards
Mario
Exactly whats ur problem?????can u be more specific !!!
Sent from my MB860 using Tapatalk
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Mario1976 said:
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Click to expand...
Click to collapse
Mario1976,
I am encountering a similar problem with my AT&T Atrix 4G running Fruit Cake 4.5.141 with BL unlocked.
I cannot get the Data Encryption to work with CWM Recovery 5.8.1.8.
I'm beginning to think that I'll need to restore the stock Android Recovery to be able to get the Data Encrytion to work.
So far, my previous attempts at flashing the stock 4.5.141 SBF using RSDLite has met with the sec_exception: febe, 35, 35 error.
I also tried to use another set of instruction for restoring stock recovery onto another device on my Atrix but to no avail:adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1Konker
Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.
Hello,
I am posting this question after searching and trying different things for about a month on my phone, and I am still standing where I started. I also ordered one of these active power cables from TeamBlackHat and atleast it brought me where I started after the battery died. Let me put things in a simple way
1. A morning, I found it sleeping (turned off) after I forgot charging it on 10% the last night. Charged it, but it stopped detecting my sim card on turning on and started rebooting every 2 min 10 seconds.
2. I am an android noob and have been reluctant of trying stuff with my phones previously. I got hold of MATT Utility 1.6 and 1.8 and RSD Lite package (the latest one)
3. Tried both, first flashed with RSD Lite. Flashes fine with the latest Spyder file, but the same issue. Reboot loop and IMEI not found.
4. Then tried MATT Utility. It restores with some errors and then it only gets till M logo on rebooting.
5. Also tried recovering from external flash from a file named Blur_Version.98.72.8.XT912.Verizon.en.US.zip but in vain.
6. Now the phone is turning on, but reboots every 2 min 10 sec and IMEI and ESN can not be found.
I tried asking this on droid razr forum, but I think people are not much active there. I really hope that I find help here. Thank you guys in advance.
trsiddiqui1989 said:
Hello,
I am posting this question after searching and trying different things for about a month on my phone, and I am still standing where I started. I also ordered one of these active power cables from TeamBlackHat and atleast it brought me where I started after the battery died. Let me put things in a simple way
1. A morning, I found it sleeping (turned off) after I forgot charging it on 10% the last night. Charged it, but it stopped detecting my sim card on turning on and started rebooting every 2 min 10 seconds.
2. I am an android noob and have been reluctant of trying stuff with my phones previously. I got hold of MATT Utility 1.6 and 1.8 and RSD Lite package (the latest one)
3. Tried both, first flashed with RSD Lite. Flashes fine with the latest Spyder file, but the same issue. Reboot loop and IMEI not found.
4. Then tried MATT Utility. It restores with some errors and then it only gets till M logo on rebooting.
5. Also tried recovering from external flash from a file named Blur_Version.98.72.8.XT912.Verizon.en.US.zip but in vain.
6. Now the phone is turning on, but reboots every 2 min 10 sec and IMEI and ESN can not be found.
I tried asking this on droid razr forum, but I think people are not much active there. I really hope that I find help here. Thank you guys in advance.
Click to expand...
Click to collapse
I have the same problem anybody know to fix it??? Help with this please!!!
Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih