Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
This happened to me a few days ago the way you should do it is download the 2.51 uk sbf file and flash it over using rsd lite and it should boot straight back Into the operating system and by the way how come that version did that to your phone I've installed recovery on 2 defys and they both worked
One more question did it boot up into recovery or not ?
No it didnt boot into recovery, just the boot loop. Any idea where i can get the uk sbf ? the link here seems to be dead
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
so.. is the usb debugging on?
when tap install recovery button, you should turn off usb debugging.
memz180 said:
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
Click to expand...
Click to collapse
mannn you save my life, i was looking for a stock rom from Latin America, and i got it from that link.
Thanks for the link memz180. Downloaded sbf and flashed sbf and phone is now working. Next question is what is the idiot proof way to install recovery ?
You installed the correct recovery just make sure you click into the program and install the system recovery within the program and then click on boot to recovery make sure i would make sure superuser is allowing it so check that out to and also as stated above turn off your debugging in development and then click on recovery see if it works.
Goodluck
Rerooted phone and reinstalled recovery, no problems this time. Thanks all for your help.
Sam
No problem here at xda we do our best to help our fellow android mates lol
Another Noob with an almost bricked Defy!
sammitch said:
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
Click to expand...
Click to collapse
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
SOLVED!
NrikeCalderon said:
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
Click to expand...
Click to collapse
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
I'm in the same boat, my phone is in a reboot loop, and I can't seem to flash it...
RSD Lite 4.9 on win7
Error:
Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected
/me bangs head against the wall...
read somewhere else it has to do with where RSD Lite is installed, on my win 7 32bit that was c:\Program Files\Motorola\RSD Lite...
uninstalled, reinstalled in c:\Motorola\RSD Lite and copied the sbf to that dir too... seems to be working... hope this helps someone else!
NrikeCalderon said:
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
Click to expand...
Click to collapse
Yer cm7 comes with it pre installed it would flash blue at bootup you should of seen it I think on the installation instruction it's written dont install 2ndinit
just rename the .sbf file to smaller name and try again
This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.
I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.
Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?
Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.
Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance
The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.
Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters
Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.
Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk
It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.
Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.
Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?
Is there any A6000 plus driver for windows 10? Because I can't find any on google.
I need it because I've just wipe data, system, etc via TWRP and unfortunately my TWRP won't read any SD Cards. The only way is flash it via PC but ya, there's no A6000 plus driver for windows 10.
Please anyone help me, thanks!
vokkus kreatif said:
Is there any A6000 plus driver for windows 10? Because I can't find any on google.
I need it because I've just wipe data, system, etc via TWRP and unfortunately my TWRP won't read any SD Cards. The only way is flash it via PC but ya, there's no A6000 plus driver for windows 10.
Please anyone help me, thanks!
Click to expand...
Click to collapse
Try installing the drivers you have using "troubleshoot compatability" and choose the option that "it worked on earlier version of windows" and select win 7
Hope this helps
Just install any driver for Lenovo A6000 Plus....... it doesn't matter which version of Windows you're on. I have a laptop with Windows 10 & Lenovo A6000 Plus drivers from various sites works just fine with Windows 10. Run the driver installer pack as administrator whenever possible.
If the driver won't install, you might need to disable driver signature enforcement at boot by following this guide.
Hey guys,
I hope someone can come to the rescue with this matter. I did an OTA update on my LG G2 (D803) and it booted to twrp option menu. I downloaded the stock firmware (which is a ".kdz" file) for the phone but can't find a way to install it on the phone since the PC is not connecting to it neither does it have external memory. I played around the options like restore, advanced but it seems empty. I can't even turn off the device with the power button. What can I do? Please help
rosh88 said:
Hey guys,
I hope someone can come to the rescue with this matter. I did an OTA update on my LG G2 (D803) and it booted to twrp option menu. I downloaded the stock firmware (which is a ".kdz" file) for the phone but can't find a way to install it on the phone since the PC is not connecting to it neither does it have external memory. I played around the options like restore, advanced but it seems empty. I can't even turn off the device with the power button. What can I do? Please help
Click to expand...
Click to collapse
OTA updates don't work when custom recoveries are installed. The device would be bricked. Sorry you found out the hard way. If you can boot into TWRP, you can download a ROM and Gapps. Buy the usb flash drive that has both USB point and Android 3.0 point. Copy the downloaded ROM unto it, slot into the charging port of the phone, boot into recovery. It should detect the usb flash, navigate to downloaded ROM and flash. This would work if you can boot into TWRP. Hope it works. Give feedback. Good luck
Sent from my Motorola Droid Turbo
abbykay said:
OTA updates don't work when custom recoveries are installed. The device would be bricked. Sorry you found out the hard way. If you can boot into TWRP, you can download a ROM and Gapps. Buy the usb flash drive that has both USB point and Android 3.0 point. Copy the downloaded ROM unto it, slot into the charging port of the phone, boot into recovery. It should detect the usb flash, navigate to downloaded ROM and flash. This would work if you can boot into TWRP. Hope it works. Give feedback. Good luck
Sent from my Motorola Droid Turbo
Click to expand...
Click to collapse
What about ADB or terminal command? I see it under the "Advanced" Menu in TWRP?
If you can do into download mode and allready have KDZ file just use flash tool 2014 to go back to stock (search here for "going back to stock:" post)
Also.. if you can send data over usb cable, try to use sideload to upload custom rom, or like stated before, use USB stick with OTG
You can also try this one: https://forum.xda-developers.com/showpost.php?p=71044359&postcount=2
or this as a last case scenario: https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
sakej said:
If you can do into download mode and allready have KDZ file just use flash tool 2014 to go back to stock (search here for "going back to stock:" post)
Also.. if you can send data over usb cable, try to use sideload to upload custom rom, or like stated before, use USB stick with OTG
You can also try this one: https://forum.xda-developers.com/showpost.php?p=71044359&postcount=2
or this as a last case scenario: https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
I have moved the kdz file to a usb stick and attached a usb stick to an OTG. But where in TWRP do I go to read the usb stick and how can I complete the process? Also I did try the SRK tool from on the links you provided. The phone is not detecting the computer while plugging in the usb while the phone is on TWRP and the computer makes a noise when the usb is connected but srk tool is not reading the phone.
You can't flash kdz with twrp or other recovery! Download custom Rom and gapps or a debloated stock rom and flash it with twrp. The custom Roms are zip files. Do you have twrp installed?
Gesendet von meinem LG-D802 mit Tapatalk
Yes you CANNOT flash KDZ with TWRP you need FLASH TOOL 2014. Download flash tool 2014 (search it on xda) than, in your G2 go into download mode, connect your phone to pc with usb cable and than run flash tool to flash kdz