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 have bootloader 30.04 after using liberty 1.5 I wanted to try out Rubix Focused. Everything was going well till my I tried to flash the watermarkd theme. Went through all the steps rebooted using Koush bootstrapper rocovery and when it restarted stuck at splash screen. After searching around I found out I could get into bootloader menu and reflash. My phone said low batteery cannot program. After cutting a USB in half and jump starting my battery I was able to get it into bootloader and it said battery ok, okay to program. Connect data cable. Make a long story short RSD lite will not recognize my phone I was using 4.9 and was later recommended to use 4.8 as a lot of people had trouble with 4.9 Any advice on this and how I can bring my phone back to life? I can get into boostrap recovery on the Android Recovery system which we all know is kinda useless for the purpose. Am I going to have to SBF Flash my phone? What if it wont recognize the phone after using 4.8 What are my options?! I need to get my phone up and running asap and i've been working on this for like 3 days now. Can anyone give me detailed instructions that could help me restore my phone? I did make a nandroid backup too, I just cant get to the bootstrap recovery for some reason. Only bootloader or Android Recovery. Please Help!!
Make sure you have the latest drivers installed. What OS are you using? If using Windows 7 you have to run as administrator(by holding shift + right click then click run as administrator . Also I had to rename my sbf file to C:/abc.sbf my computer would only recognize the sbf on the root of my C drive.
Hi there!
I tried to update firmwmare with lots of different ROM's (B135,B136,B162,B517,B522) but always getting "Update failed" at Step 2/2 - Installing.
Is this phone bricked?
I cannot access internal card.
Any ideas before i threw it away?
Update: On sdcard i am getting error in file: sd_update.log
notes: (dld_file_ptr != -1) !
dload_sd_file_data_proc-(dld_retry >= DLOAD_RETRY) failed!
Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App
As long as you have a working pink screen, anything is solvable .
I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!
update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App
Maksimitoisto said:
update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.
mesnati said:
I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!
Click to expand...
Click to collapse
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App
mesnati said:
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.
Click to expand...
Click to collapse
Also tried without battery. It is the only way to update. With battery cannot go further from "step 1/2 Unpacking"
julle131 said:
Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App
Click to expand...
Click to collapse
How to find device to mount? dmesg show me nothing.
Any help would be helpful
[email protected]:/home/xxx# lsusb
Bus 002 Device 002: ID 12d1:1035 Huawei Technologies Co., Ltd.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
I can see device with "lsusb" but cannot mount it
Anyone?
julle131 said:
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks julle!
But seems to me that you don't understand the problem.
Here are the steps from blefish:
1 Download update-B518-bootloader.zip from MediaFire.
2 Save it to the root of your SD Card.
3 Start the phone in recovery mode (recommended recovery is 5.5.0.4)
4 Select "install zip from sdcard"
5 Select "chooze zip from sdcard"
6 Select the zip you downloaded before.
7 Select yes.
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.
Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode
mesnati said:
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.
Click to expand...
Click to collapse
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
mesnati said:
Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode
Click to expand...
Click to collapse
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App
julle131 said:
Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You are making me laugh )
I cannot install NOTHING!!! That's the main problem
qwerty12 said:
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
You are right!
So the device should be bricked now? I cannot give back to warranty 'cause i already did it once If i send also this one they will laugh at me and of course they will not give me another phone
But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?
mesnati said:
But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?
Click to expand...
Click to collapse
qwerty12 said:
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
Actually, I haven't tried HyperTerminal on the COM ports/modem - maybe it could, somehow, let you do something? Changing the USB mode would be great...
If you do figure out QPST, you'll need the firmware in a form it can understand - maybe you'd have to get another device to dump its firmware...
Regarding warranty: Couldn't you make the case that it was an official firmware update that caused your phone to brick?
mesnati said:
You are making me laugh )
I cannot install NOTHING!!! That's the main problem
Click to expand...
Click to collapse
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App
julle131 said:
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Your english is ok I tried 100 times after it fails and every time same error appears "Update failed"
Hello!
I'm trying to install clockwork recovery with the fastboot method.
But when i use this method: http://forum.xda-developers.com/showthread.php?t=1319257
The phone just freeze at the ZTE (white background) logo.
And the windows command prompt are telling me: < waiting for device >
I need to remove the battery to start it again.
Have also tried;
z4root + Rom Manager
OneClickRecovery (telling me exploit cannot be used trying su and launch the file explorer)
It's a Gen 2 phone with Android 2.3+
If nothing works cant i use Linux?
Big thanx! for everything.
You need to install drivers for the phone if you use Windows. Link is in the thread.
It'll work on Linux or Mac without any drivers, but you might need to be root if you don't set it up right.
wbaw said:
You need to install drivers for the phone if you use Windows. Link is in the thread.
It'll work on Linux or Mac without any drivers, but you might need to be root if you don't set it up right.
Click to expand...
Click to collapse
Yes, i have done that. I did try the drivers in the thread and those i did get with the phone (autorun). And Windows tells me all drivers work correct.
Thnx for the answer.
When you're in the bootloader, check device manager if it shows Android with a yellow exclamation.
Rapier07 said:
When you're in the bootloader, check device manager if it shows Android with a yellow exclamation.
Click to expand...
Click to collapse
Yes, when i do the
Code:
adb reboot bootloader
and the phone shutsdown and showing ZTE (white background) then device manager starts showing "android" with a yellow "!" behind it.
But it ain't there until i do that? And Win 7 shows a "can't find drive" i did try point it to the ZTE 3G instalation folder with the amd64 drives. But nothing happens.
Now i have tryed on my girlfriends laptop also. It also got the Windows 7 64bit. But it does not work there either. Same problem.
How long should it take until "Android" logo shows on the phone?
Thanx for all the help!
UPDATE
UPDATE!
I think i solved it.
Used: SuperOneClick
And when it started to root and downloaded all drivers i did the original ADB:
[GUIDE] How to root your ZTE Android device
And it started to install Clockwork Recovery. SuperOneClick shutdown (error) and the phone booted. And now i can boot into Clockwork Recovery with VOL-.
But Rom Manager does not find it and can't install it.
So i'm going for the traditional boot with VOL- and hit the ROM from there.
Big thanx for the help!
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!