Related
Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
slowcurve said:
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
Click to expand...
Click to collapse
I just replied to your email, you efused!
This is exactly what happened to me when I bricked my gf's first bravo.
Good news is sbf and its fixed. You wont even lose any data.
IDK how this happens, seems it has happened twice now, there must be a specific change made before bootstraping that causes the check.
Either way the code group that is problematic is in the sbf, flash it and your good.
you will need to reroot, rerun nonmarket apps enabler, and re-bootstrap recovery, then reboto recovery and flash rc2 and you will be fine.
sorry for the spam... i panic'd..
i have the rsd lite i searched for sbf's and a whole bunch came up mind pointing which one i should use.
Edit: Its fixed thank you bando, you own half of my soul
I tried to flash my MS2, but now I have no boot and no access to the phone.
Story:
- root via paxChristos' Linux Port of DooMLoRD's Easy Rooting Toolkit
- backup via Titanium Backup
- backup via Bootstrap
- installed CyanogenMod and the nightly build cm_droid2_full-139.zip
- realized ... it is the wrong Mod, because for Druid2 and I have a Milestone2 = not the same
- sudo ./sbf_flash MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf
And now, I have a dead phone ... even could not start it. It is just a black screen and nothing more!
The only thing that show "life" is the LED on the side of the USB-Cable plug!
I also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable!
Is there a way to flash the phone anyway?
Would be nice to have a little help!
A little more info:
Plug in USB cable and lsusb:
Bus 002 Device 013: ID 22b8:4280 Motorola PCS
Long press on the power button and lsusb:
no Motorola
Keep USB cabel in the phone, unplug the batterie and plug in back ... lsusb:
Bus 002 Device 015: ID 22b8:4280 Motorola PCS
And more info:
udev-rule1 (worked to flash the phone)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
udev-rule2 (tried after reboot of phone showed lsusb shown before)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
Also ... not worked:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ./adb shell
error: device not found
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
First of all ... thanks for helping me!
Anonymous_ said:
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
Click to expand...
Click to collapse
Nothing happend ... screen is black, LEDs are off!
DreadPirateDan said:
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
Click to expand...
Click to collapse
Battery should be ok, it also don't work with Charger on!
If it is impossible to remove the locked bootloader, why can I still not boot?!
If the device bricked only a black screen shows up. This is bootloader mode. RSDLite will recognise your phone and flash an SBF.
Sent from my MotoA953 using XDA App
Damn ... just bought a used one on eBay and now I have my old one fixed! *lol*
Thanks to you all ..
I used my laptop with Windows7 and RDS light from Chip Online
Then I used the SBF Version 2.3.4!
reboot ...DONE ... Milestone2 worked again!
But ...
root via zergRush_automated_Linux_root
Installed bootstrap-1.0.0.5-droid2.apk from SD-Card because:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
I think the message is very clear. The bootstrapper never installed to begin with. Second of all, why are installing the bootstrapper like that? Instead of copying it to your SD-Card and execute it from the file browser on your phone. It will be installed, after which you should execute it. It will ask for root access when you press the bootstrap button. You give it and then you press the button Reboot Recovery. Then you'll be in CWM. You can't install CM7 from Motorola's recovery, which is what you've been doing all the time.
Further: Endless7 has written a guide here: http://forum.xda-developers.com/showthread.php?t=1310641
I'd suggest you follow it, and if you don't understand something ask it.
HAPPY NEW YEAR!!!
Okay, actual I have my MS2 with the original sbf and I wait until my second MS2 is here.
Then I try to install CM!
Never the less I have questions, just to be sure.
When I install the droid2bootstrap, I just copy the file to the sdcard and then install it at the phone?! Is this correct?
Then the HowTo says: 3.open droid2bootstrap and select install recovery
But there is nothing like "install recovery" to select. There is just a screen with two buttons (Bootstrap Recovery and Reboot Recovery) ... I think "Bootstrap Recovery" first, then reboot?
If I do the steps above, I have an bootloader installed on my phone?! Which I can start with the volume buttons at bootup?
Wow, I have to learn a lot about Android phones! I read the wiki, but asking questions will help me more!
Thanks to you all!
What you described is correct except the startup with volume buttons.
You have to use the Reboot Recovery button to get in CWM, where you can flash CM7.
And just for the record: every phone has a bootloader installed, otherwise it wouldn't be able to boot an OS. Fact is that you can't replace it on the Milestone 2.
Don't mix up Recovery and Bootloader. They're different things.
sasch42 said:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
Click to expand...
Click to collapse
bootstrap is not copied to /system/app , adb said "failed to copy...".
maybe copy it do /data/app ?
You wiped data and cache.. how about dalvik?
Because the copy failed, I installed the app from the sdcard (/data/app was also read only).
But as described here (http://forum.xda-developers.com/showthread.php?t=1310641) I used the wrong app!
IMHO it is the same to copy the app via adb or install it from sdcard?!
What the shizzle, you are making it so hard for yourself.
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
EDIT: on a side note, it would seem you flashed the official gingerbread sbf, so now you will only be able to use the gingerbread kernel roms. Which is pretty much the cm9 alpha version, endless 7's cm7 defy port. Not really sure about the other gb rom (argen2stone, blurless etc). So make sure you read up on what you need and what will work
DreadPirateDan said:
...
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
...
Click to expand...
Click to collapse
Have you read all the posts?
My mistake was ti follow this guide.
And my way to install the app was, to copy it tio the sdcard because the method in the guid didn't work!
Milestone 2 Bricked
Hello friend, i am having the same problem then you...
It only show black screen and the led on the side of the usb cable and i also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable, as you and nothing...
Can you help me? please!
Do you have RSDLite? If yes, then RSDLite should detect your phone as it is already in bootloader mode (the black screen). You can flash an SBF at this point.
Download an appropriate one, if you were on Froyo then Froyo and in case you had upgraded to Gingerbread then download a GB SBF.
Flash the SBF. You would probably end up in a bootloop. Go to moto recovery, wipe data and boot. You should be good to go.
Edit: I believe that only GB sbf is gonna work for you as I suspect that you were somehow on GB and then tried to flash Froyo which led you to the black screen.
Hi everyone,
today I've solved my problem (http://forum.xda-developers.com/showthread.php?t=1567301), but my recovery...is brake! When I boot into recovery, there is an exclamation point...I can wipe data/cache and use zip file from sd. Stop...nothing else!
Like this....I can flash with another rom? Or maybe my recovery is "damaged"?
Sorry for my poor english...
kaiserxol said:
Hi everyone,
today I've solved my problem (http://forum.xda-developers.com/showthread.php?t=1567301), but my recovery...is brake! When I boot into recovery, there is an exclamation point...I can wipe data/cache and use zip file from sd. Stop...nothing else!
Like this....I can flash with another rom? Or maybe my recovery is "damaged"?
Sorry for my poor english...
Click to expand...
Click to collapse
I think you're in stock recovery. What you need is install 2nd-init for the custom recovery and all it's features onboard...
Thanks for your reply!
I've tried to install 2nd-init (the stable, not the latest) and all it's ok...if I restarted my phone e try to enter to recovery mod, I see an Android BootMenu ( ) and I can choose stock recovery and custom recovery. If i start the custom it retunr this message:
Code:
Start Custom Recovery...
E:Can't run /system/bootmenu/script/recovery.sh (No such file or directory)
So confused....
Something braked with che CM9 kernel? If I start the stock recovery...I see the imaged attached in this post.
Boot normally into CM9. Open 2nd init and uninstall Bootmenu, then re-install bootmenu but chose "Latest - 1.0.7", not "Stable - 0.6.7"
Boot menu 1.0.7 is available with latest Sndinit2.0 version, get that sol from dev section and then install boot menu.
Sent from my MB526 using XDA App
Thanks to everyone!
Now I'n with the 1.0.7...I have the same image on the recovery this is strange!
I've tried to flash with che CM9, but the install aborted with this message:
Code:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
EDIT: the same error with my CM7.2
I'm coming from a 7.2 NIGHTLY (cm72-120127.0846-NIGHTLY-Defy+). I've tried to install the CM9 from this link http://forum.xda-developers.com/showthread.php?t=1432100 (I've used the Quarx rom). After this my Defy+ wan unable to boot (black screen). After a few of stock rom I'm back to the default rom (the spanish version, not the italian...it doesn't work ). I would like to flash the CM9, but first I think there is a problem with the recovery...why it displayed the image with the alert? Another question...with the CM7 my recovery have got a lot of option...now I've: reboot/apply update from sd/wipe data/factory reset/wipe cache. Is it normal?
What the hell I've done?
Most likely you're trying to flash unsigned ZIPs and the recovery wants signed ones, or trying to flash what should be extracted as "backup" and restored. You can turn off signature checking in recovery, if you know that you're flashing correct ZIPs and they're unsigned.
The stock recovery ALWAYS displays an image with the alert, because you can NEVER change it, until Defy bootloader will be unlocked (if it'll ever happen). Nothing strange about it.
I was able to use recovery and I tried to reinstall the CM9, but now my phone looks dead! No boot, no boot error, no recovery...nothing! Black screen. If I plug the phone to my pc...RDS Lite does't recognized the Defy. I would try to flash the sbf and come back to the 7.2 NIGHTLY...but how?
Damn...I'm so sad for this I'm hope there is a workaround...
kaiserxol said:
I was able to use recovery and I tried to reinstall the CM9, but now my phone looks dead! No boot, no boot error, no recovery...nothing! Black screen. If I plug the phone to my pc...RDS Lite does't recognized the Defy. I would try to flash the sbf and come back to the 7.2 NIGHTLY...but how?
Damn...I'm so sad for this I'm hope there is a workaround...
Click to expand...
Click to collapse
Did you press vol up and power??! You need to go to program mode for RSD lite to recognise your phone! It may have been that you flashed CM9 for Defy instead of CM9 for Defy+!! By no recovery do you mean you can't go even to stock recovery?!(Sounds almost impossible!)
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
You need to go to program mode for RSD lite to recognise your phone!
Click to expand...
Click to collapse
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
kaiserxol said:
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
Click to expand...
Click to collapse
Normally these steps are followed to flash SBF:
1.) go to bootloader mode (Vol up + power button. That's the program mode I was talking about)
2.) Now RSD lite will recognise your phone.
3.) Flash from RSD lite.
Are you saying that Vol up + power button = nothing happening in your phone? Not even black screen with
Bootloader .... blah blah
USB
Battery OK
Ready to program
????
If that's the case:
1.) Battery not charged.
2.) Go claim warranty!
Yes...this case! I know the bootloader screen
Code:
Bootloader .... blah blah
USB
Battery OK
Ready to program
but this time nothing...
Mhh...maybe the battery is near the 0% and the usb from a pc doesn't charge the phone? The led is white...but nothing. Maybe with the AC power?
kaiserxol said:
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
Click to expand...
Click to collapse
Charge your battery... In another Defy phone, NOT McGyver method as many have already fried their batteries, using this trick!
I don't have another Defy for try this! I will try tonight at home, with the other cable connected directly to AC, and not to my pc. I hope it's work
No matter what cable you will try. At the moment your phone is not charging the battery. In order to start charging, you need to reflash it. And in order to reflash it, you need to get your battery charged... Sweet, ha? Get a buddy with a Defy to charge your battery and then reflash the phone.
Wow...this is a problem for me. Nobody have this phone and in Italy is not so much widespread...nobody know it :-(
kaiserxol said:
Wow...this is a problem for me. Nobody have this phone and in Italy is not so much widespread...nobody know it :-(
Click to expand...
Click to collapse
Then get to Amazon.com and buy a docking station with external battery charger if you dont want to use mc guyver, thats was my backupplan if I'm too stupid to use it... well mac guyver worked for me, 5 min charging and everything was fine xD
Here is an example
http://www.amazon.com/Fosmon®-Premi...9TVM/ref=sr_1_1?ie=UTF8&qid=1333017207&sr=8-1
It's hard to use the McGyver method? I'm a little bit scared to do this...but if it works to you...i will try
kaiserxol said:
It's hard to use the McGyver method? I'm a little bit scared to do this...but if it works to you...i will try
Click to expand...
Click to collapse
It worked like charm, battery is fine, i was able to flash a new rom...
One Usb-Cable "broken" but well who cares.
But if you try it, you need to be very very veeery careful.
Friend of mine is Hifi-Electrician and i had a little help from him, for testing which wires are the right ones to connect.
You have to be aware, that this could kill your battery and you need to buy a new one.
But once, everything is connected the right way, you also need to know that there is no safety or fuse or whatever, that safes your battery, so dont put it on too long, in my case, it took about 5 to ten minutes for 50-70% of battery, so dont let it be connected too long.
And one last thing, make sure, that there is no possibility for the cables to hit any other connector(?) on the battery, use some kind of tape, to make them stay in there position.
If your still willing to try this, good luck to you, as I say, this works. I dont know which MC Guyver you like to try, but i would recommend the batterycharge only, so not connected to the phone, version.
But think about this docking station too, its way more comfortable, easier, less dangerous, and amazon is really fast in shipping, so it would probaply just take 1-2 days.
I fuound this in the forum
http://forum.xda-developers.com/showthread.php?t=892026
I think it's the best way...or not?
Thanks
EDIT: can I use the usb cable from a pc? Or I need to plug the cable directly into the AC power?
Hi all,
I have a bit of a problem.
I had an old Oxygen (?) 2.3.? but wish to upgrade to ICS so after installing the 'official' 2.3.5 was following steps in http://forum.xda-developers.com/showthread.php?t=1420728.
I got up to the bit about installing Clockworkmod. When I tried to go into recovery mode for some reason (I must have screwed something up) it went back into the Firmware update (presumably because I still had the sd card with the 2.3.5 updated on it). It gets through the first step of the update but when it goes to start step 2 it comes up with 'Update failed'.
If I remove the sd card and try to start up normally I get the blue screen.
I can get to the pink screen but I'm not sure what to do from there.
Thanks for any help.
Cheers,
H.
horrendo said:
Hi all,
I have a bit of a problem.
I had an old Oxygen (?) 2.3.? but wish to upgrade to ICS so after installing the 'official' 2.3.5 was following steps in http://forum.xda-developers.com/showthread.php?t=1420728.
I got up to the bit about installing Clockworkmod. When I tried to go into recovery mode for some reason (I must have screwed something up) it went back into the Firmware update (presumably because I still had the sd card with the 2.3.5 updated on it). It gets through the first step of the update but when it goes to start step 2 it comes up with 'Update failed'.
If I remove the sd card and try to start up normally I get the blue screen.
I can get to the pink screen but I'm not sure what to do from there.
Thanks for any help.
Cheers,
H.
Click to expand...
Click to collapse
IS it the pro or regular?
conect to computer in blue screen mode and watch what is missing.
Sent from not my ragelis
bronxitas said:
conect to computer in blue screen mode and watch what is missing.
Click to expand...
Click to collapse
Thanks for the suggestion. How do I see what is missing? I have tried various USB drivers but so far haven't found one that will mount the device. Do I need to use logcat with adb?
Any idea why it will no longer allow me to simply reflash the stock rom?
By the way, the device is the standard u8800 - not the -pro.
Cheers,
H.
Not in blue screen, you must go to pink screen mode(by pressing vol+/- end power when the device is turned off). There you'll be able to see the folder with the system files on pc.
dancer_69 said:
Not in blue screen, you must go to pink screen mode
Click to expand...
Click to collapse
bronxitas said:
conect to computer in blue screen mode and watch what is missing.
Click to expand...
Click to collapse
Now I'm confused.
When I connect the phone to my Windows computer (tried XP and 7 in both pink and blue modes), the device does not register. Windows detects the new device and asks for drivers. I have tried different ones but none that I've tried so far will see the device. If someone could give me a link to drivers that definitely work I would be most grateful.
Like I said in my original post, if I leave the SD card in it tries to do the firmware upgrade but fails. Is there no way to 'reset' the phone somehow so that the firmware upgrade will go through? Perhaps downgrade to an older version first??
Thanks,
H.
There is not blue screen mode. Blue screen just shows that the system files don't exist. If recovery image doesn't exist you get a blue screen when you try to reboot to recovery mode. If you cannot boot normally, probably boot.img is erased(or maybe all system files which are on Image folder are erased).
Also if you had flashe an official rom version higher of B518, you probably have a locked pink screen, so it doesn' t matter if you have or not drivers because you cannot access the special partition which has the Image folder with all system files anyway.
Now, if the update proccess of official rom stops or second step(after unpacking proccess), probably a partition on the device is corrupted and the update cannot write to it. There is a special update, which you can flash with the same way as the official rom(put it on dload folder), and maybe can solve the problem. I' ve posted it on another thread here before some time. The filename is: update-160up
try to search the forum and hopefully you will find the thread(which has some isntructions and comments also).
You can try to flash a 2.2 official rom also. Maybe the update will succeed then.
horrendo said:
Hi all,
I have a bit of a problem.
I had an old Oxygen (?) 2.3.? but wish to upgrade to ICS so after installing the 'official' 2.3.5 was following steps in http://forum.xda-developers.com/showthread.php?t=1420728.
I got up to the bit about installing Clockworkmod. When I tried to go into recovery mode for some reason (I must have screwed something up) it went back into the Firmware update (presumably because I still had the sd card with the 2.3.5 updated on it). It gets through the first step of the update but when it goes to start step 2 it comes up with 'Update failed'.
If I remove the sd card and try to start up normally I get the blue screen.
I can get to the pink screen but I'm not sure what to do from there.
Thanks for any help.
Cheers,
H.
Click to expand...
Click to collapse
Depending on your model you need to restore its pinkscreen stock files. The boot.img will fix the bluescreen. Heres oxygen's boot.img. Mount via usb to computer*
Somcom3X said:
Depending on your model you need to restore its pinkscreen stock files. The boot.img will fix the bluescreen. Heres oxygen's boot.img. Mount via usb to computer*
Click to expand...
Click to collapse
I have same problem and can not mount phone via computer seems the only way is via external sd card. will the phone boot off the sd card if the above boot.img is loaded on to it and where would i put this file. and should i take the 2.3 gingerbread update (dload/update.app)off the sd card and just have the boot.img file?
fookedit said:
I have same problem and can not mount phone via computer seems the only way is via external sd card. will the phone boot off the sd card if the above boot.img is loaded on to it and where would i put this file. and should i take the 2.3 gingerbread update (dload/update.app)off the sd card and just have the boot.img file?
Click to expand...
Click to collapse
you should flash the update again maybe?
Sent from my u8800-51 running popura ICS.
is it game over?
Somcom3X said:
you should flash the update again maybe?
Sent from my u8800-51 running popura ICS.
Click to expand...
Click to collapse
flashed normal gingerbread with update.app and update_custom.app in the dload folder. no luck, update failed. the phone does go into boot loop with huawei logo when power vol+- and plugged into external power. Help! I should say that i have recently upgraded it to official 2.3.5 firmware from 2.2 using and wanted to install dzo's aurora so i like others
"2. rooted with superoneclick
3. replaced .cust_backup/image/recovery.img with recovery.img (cwm5.0.2.7), by remount and es file explorer'
restarted, bang! blue screen restarted again with power vol-+ got pink screen but computer wont detect any storage on phone so i cant access the phone with the computer only via external sd card and the updates dont seem to work, i would like to try booting with froyo but cant find it anywhere....
so yeah, help, seems like game over to me!