A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.
Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!
More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11
Related
Hiya all, I am quite desperate for help, I consider myself intermediate when it comes to dealing with android devices but I am well and truly stumped on this one.
I received a second hand streak from eBay yesterday, turned on first time and booted fine, running Steakdroid 1.9.0 by DJ Steve. I had a few issues with it reboot randomly or crashing, as it had Streakmod Recovery installed I did a full wipe all areas, reinstalled the Rom 1.9.0 and bit a factory reset on reboot from the Dell recovery menu.
All the device does now is reboot in bootloop on the dell logo it stall when it goes as far as booting or trying to load the Rom.
I ran the test in fastboot to test the internal drive as this is known to fail and both that and my SD memory passed the test.
I used fastboot and CMD to flash 4399 recovery image the OEM recovery image for the Rom Streak_104_4399_21.pkg I renamed this to update.pkg and rebooted the device into recovery where I then went to restore the original firmware (1.6) but as soon as I pressed the camera button to proceed I was greeted with a lovely black screen.
I left the device for about 2 minutes where it reset itself and just keep rebooting on the dell logo the restore did not seem to work, just to check fastboot and CMD was working as it should I went to reinstall the Streakmod Recovery image and sure enough it worked I managed to boot the device back into streakmod.
Unfortunately every time I try to install a custom rom they just do not seem to load the device simply stalls on the Dell logo because I cant seem to restore the original recovery image for the stock rom I cannot factory restore and nor will any custom rom boot.
All I have is access to fastboot and Streakmod recovery aaaah!!
If anyone can help me in the slightest I would well very, very, very much appreciate it!
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
(InsertNameHere) said:
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
Click to expand...
Click to collapse
Thanks for the reply here's my progress so far:
Flashed recovery image and loaded rom to SD card..... Booted into dell recovery and this is what happened
Finding update package
Opening update package
Verifying update package
Yellow bar 25%ish at this point
flashing lights
Installing Update
33%ish lights flash again
Yellow bar jumps 3/4 then fills screen, streaks screen goes blank/ off
Doesn't reboot/ cant turn on so I remove battery and switch back on and I am back to Dell logo then I get a picture of an android and another small progress bar that slowly fills and the device and it again reboots
Streak reboots again about 3 times like it is stuck in bootloop, I leave it and keep my fingers crossed I then get an animation of the Dell logo and glowing lights behind it.
Keep fingers crossed and sure enough it boots into the lock screen, I go to unlock it but it freezes and I get the flashing lights syndrome and the screen goes blank
Remove battery and switch on again, dell logo bootloop after about 8 or 9 bootloops it boots back up into the ROM above but then crashes once again...
Is it fair to say this streak has given up the ghost?
Flashing lights could mean baseband mismatch.
Try again, but be certain to use the correct recovery.img for the rom you are flashing, get the 351, 354 or 360 recovery.img that matches your choice of rom.
Make sure there is only 1 update.pkg on your microsd card, the one you want to flash, move all others, rename them or delete them. The Dell recovery always looks for update.pkg, nothing else.
Flashing lights could be something more major, but i still think its a baseband mismatch.
(InsertNameHere) said:
Flashing lights could mean baseband mismatch.
Click to expand...
Click to collapse
Honestly thats what I wanted to hear but what worries me is I downloaded the recovery and image from Wiki both relating to 360 will try flashing again I really do hope it can be fixed! Seems today is not a good day for me today many things going up the creek!
I am 75% certain if you flash it with the right update.pkg, that is a renamed 360 pkg you downloaded, you will have success.
When you flashed Streak_104_4399_21.pkg you were trying to revert to Android 1.6.
You may have to use the QDLTool to fix the Streak. I am not sure what problems trying an 1.6 build over an Android 2.2 build can cause. You may want to wait for some more feedback.
Start here for more info and try the links in my signature.
I dont believe you can downgrade directly from 2.2.x -> 1.6.
2.2.x -> 2.1 -> 1.6 might work but why are you doing this in the first place?
Just directly install 360 or the like
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
marvin02 said:
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
Click to expand...
Click to collapse
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
teaganravetta said:
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
Click to expand...
Click to collapse
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
many thanks for all the help, so far I have downloaded "QDLTool3rd_20101022_GAUSB1A130500" turned off driver signing as I am x64 all ADB drivers fine and COM ports okay have restored via this tool according to the log successfully.
Phone rebooted a few times it has paused on the Dell logo for a moment but the guide did say anything up to 10minutes for first boot so I am holding for the moment to see if this has cured it otherwise I will report back and re download the above files and try that!
It takes me a while because I am out in the sticks I only have a 60kbps download speed (yikes) I know!!
Because your first attempt at flashing a stock ROM was the Android 1.6 version I am not sure you can just flash 360 at this point. I think you have to use the QDLTool (repairtool), but I am not sure. Try searching for the procedures that were used to upgrade from 1.6.
Edit to use the QDLTool:
In this post DL under commonly downloaded tools get Fastboot/ADB utils + drivers for Streak 5/7 and Venue and QDL Tool.
Then download qdltool-tutorial.zip from this page. unzip the tutorial and open it with a browser that supports flash or other flash viewer.
After using the QDLTool let the Streak boot and then flash the 360 recovery file and the 360 ROM. You must not let the phone boot completely after flashing a different recovery or the phone will restore the one that came with the ROM currently on the phone. Read this.
You can find more info about QDLTool by searching. As I said I think that is what you need to do.
lordmorphous said:
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
Click to expand...
Click to collapse
Thanks, this got my problem solved (endless boot logo issue with Simple Droid rom), however I am left with a no cell tower reception ?
I flashed the official stock unlocked retail rom ? still no tower reception ?
Try Simple Streak 1.2 , as i had this problem yestrday , but for simple streak 1.2 everything Worked Fine , just goto its thread and follow its instructions and u wll hve 2.2.2 in 15minutes , hit thnx if this helps
Hi I am a noob, so please be gentle.
I tried to install the cyanogen for ZTE blade 7.02 (gingerbread) on my android which was running a froyo by cyanogen.
First I unzipped the gen1-gen2 on my PC and moved the image folder to my phone, then copied the cyanogen zip and the Google apps (gapps)zip to the phone
I used clockwork to install the cyanogen and google apps, wiped the data and cache and rebooted.
Found no google apps and no market on the phone.
Tried reinstalling gapps - no difference.
tried reinstalling cyanogen and got the following message:
Installing://sdcard/(the cyanogen).zip
finding update package
opening update package
E:can't open / (the cyanogen) public.zip
(bad)
Installation aborted(I had the ss3 rom name in there so have changed it.)
I tried installing 3 other gen 2 roms, and they all give the same message, but the gapps zip will install.
I also notice that though I have repeatedly wiped everything (including the davix) I still see (in clockwork and through the PC ) all my old data on the sd card
I wondered if
The reason it won't install is because it is still gen 1
Can you answer this, please?
Thing is I dare not install a gen 1 rom because it might brick it.
I can't use mr pigfish to find out if it is still gen 1, because I can't download it as market on my PC won't send it. I cannot install market or any other google apps on my rather functionless phone. I have no contacts, and my email is set up by imap.
Not only that but the Home key won't work except in clockwork mode.
I am due to go away in two days and need my phone by then.
I have searched the forums, and have trie solutions, but am stumped. Any ideas.
Oh, I haven't tried using TPT before apart from the gen 1-gen2, and understand that it is non-recoverable. should I try that?
When you put the gen2 image on the root of your SD card did to press power, vol + and menu at the same time?, you should see some green writing.
sent using tapatalk
Thank you for your help.
I didn't do that at the time, though I have tried doing that since but I get the green android even though I hold it for ages, and when I let go it still stays on the green man.
someone else suggested holding just the volume up and power, but that does exactly the same.
Should I copy it over again and try again, do you think?
I tried it again, again only the green android, nothing more.
Your phone is still gen1 then, this is why you are stuck at the android picture.
You probably will need to restore your nandroid first.
Try this:
Download gen1 to gen2 (there is a download link in this section) http://forum.xda-developers.com/showthread.php?t=1258855
Unzip the file and place the image ( the image is called image, not gen1 to gen2) on the root of your sd card (ideally it is best to do this on a pc)
Also download and place the Rom you wish to use on the root of your SD card (cyanogenMod 7.1.0 stable release works well) http://forum.xda-developers.com/showthread.php?t=1297776
DO NOT UNZIP THE ROM at this stage.
Put the SD card back into the phone.
Power off the phone, hold menu & vol + (up) & power at the same time, you should see some green writing, wait until it is finished (well done your phone is now gen2)
You should now arrive at the clockwork recovery screen, if not power off the phone, then hold vol - (down) and power (together), clockwork will boot.
Now using clockwork recovery, clear data/factory reset, then install your rom from the zip, that is all there is to it, obviously you'll have to enter your login details to use the market and sync your contacts etc, but your phone should now be working.
Don't forget to make a nandroid backup.
Goodluck 
sent using tapatalk
sent using tapatalk
Thank you.
Firstly I cannot copy the files on my PC as my cardreader will not read the sdcard (it is limited to 4gb,) and I have the same problem with my laptop.
Having transferred (by usb) the appropriate files (image, mod zip and gapps zip) I tried to do exactly as you said, but when it gets to the holding home, power and volume up I am still stuck at the green robot.
In fact I realised as I started to type that I had been holding the menu key rather than the home key, so I tried again, this time doing as you advised and holding the home key(as well as the power and volume up) I am still stuck at the green robot.
So I assume that the phone is still gen 1?
Do you think I should just give up and try a gen 1 rom. Or is that to make assumptions and risk bricking it?
Caddi
Aef 101, Many thanks - you linked upthread to a thread about gen1 and gen2 and later in the thread, there is a reply which I had missed reading, which states:
"Some sd cards seem incompatible & wont perform a tpt flash."
I wonder if that is the problem here with mine?
Considering that initially I didn't do a tpt, and then when I did it didn't work, I might still have the gen1.
I won't hold anyone responsible, but I would love an opinion on whether you or anyone would risk trying a gen 1 mod.
It may be an idea to try a different SD card, I use the cyanogenmod 7.1.0 Rom, if you want to try a gen1 Rom you'll be happy with the last ginger stir fry rom also found on this site.
As I have said, I think you are trying to run a gen2 Rom on a gen1 phone, just boot into recovery and reinstall your old backup.
sent using tapatalk
Place the image on the root of your sd card.
Press menu, vol up, and power at the same time, if you see green writing then you are doing it correctly, then use recovery to install the Rom.
sent using tapatalk
Thanks I think I am going to try the stir fry rom. Your help has been much appreciated
(PS I really fancy ginger stir fry for tea too!)
I am delighted!
Thanks everyone. I am now running Ginger stirfry, and quite importantly I have learned a lot about installing Roms in the process.
caddi
Original message
:I need some serious help.
I tryed to flash custom 2.3.6 fixed sbf.
which didnt end well, after powerup i would go straight to bootloader with err codes.
so tryed to flash another stock SBF, that ended me in inifinte bootloop with android logo. after 20 minutes in bootloop i gave up and flashed another stock SBF this time it was cellcom israel sbf, it finished the flashing succesfully but now the phone wont powerup at all. not bootloader not recovey.
nada...
I really need your help here, any kind of insights will help. please this is urgent.
BTW: this is a red lense defy, last rom was JB 4.1.1 quarx 30.07 build.
the sbf was supposed to have the same rom.
update 1: managed to finally flash stock, cant enable 3g. phone is still rooted, installing superuser is succesfuly but doesnt control attributes. so 2ndinit currently does not work,
issue solved
Click to expand...
Click to collapse
UPDATE 16/11/2012: links check and updated everything should work.
Solution:
1. first get these files as we'll need all of them: Rsd lite (download and install that),
Motorola drivers (download and install: Here)
JORDN_U3_97.21.51.rar(contains sbf file): http://www.4shared.com/get/xzT3dMXv/JORDN_U3_972151.html
firmware.rar(contains another sbf file): http://www.4shared.com/rar/Ytt5O6--/firmware.html
2ndinit 1.4.2, and 2ndinit 2.3 (can be found here: http://forum.xda-developers.com/showthread.php?t=1032212).
also need the nandroid backup: http://www.4shared.com/file/pVQfB4bF/2011-06-11141427.html
[Optional]
superuser.zip file installing from recovery: http://downloads.androidsu.com/superuser/Superuser-3.2-arm-signed.zip
2. [Optional] I didn't have a router at my house and no signal at my phone and i needed internet for 2ndinit, so i installed a program that turns my wifi on the computer into a hotspot, it can be found here: http://www.connectify.me/
3.First shutdown your phone, hold the Vol down and boot the phone up keeping the volume down pressed. you should come up to a triangle android logo, press the vol up and down key and then tap the screen ( this is a touch screen gui), choose the wipe data/cache and press ok, this should take up to 5 minutes.
4. Now, shut down the phone (pull the battery out and return it back in), Hold the Vol Up button and power up your phone.
you will enter the Bootloader (or BL as its called in the forums) and you should see the phone stating that (usually 9.10 version)
5. after installing Rsd lite, launch it, extract the JORDN_U3_97.21.51.rar and firmware.rar files into root directory (C:\ or D:\ or whatever).
in rsdlite press the
...
Click to expand...
Click to collapse
button and choose the JORDN_U3_97.21.51.sbf file.
connect your phone via a usb cable to your computer, the phone should state its connected. and you should see on the rsdlite window that a device is connected, click on it and press the button :"start".
let it finish and boot on itself (it should do that).
6. [Optional] if you started with low battery now is a good time to charge your phone.
7. transfer the 2ndinit 1.4.2 apk and the 2ndinit 2.3 apk into a folder in your sd card (name it "A" for ease of use).
also extract the 2011-06-11.14.14.27.zip into this folder on your sd card "/clockworkmod/backup/"
8. extract the superoneclick on your computer and launch it, while the phone is connected (should also be in usb debugging mode), press the root button in the superoneclick window and watch the magic, make sure you also install busybox (should be installed automatically when pressing the ROOT button).
9. disconnect your phone, use the file explorer provided with this rom and make sure you check with a "V" to "allow 3rd party apps" in the settings. install the 2ndinit1.4.2.apk file.
open the app after installation and make sure you have internet connectivity, press the install bootmenu option.(now pop-ups should appear regarding permissions, choose "allow" for all of them).
after the green led has turned on, go to settings menu under application/development and turn off the "usb debugging mode".
10. restart your phone and make sure you press the vol down button when the led turns blue during the bootup.
when in bootmenu, choose recovery-> custom recovery.
when in recovery, choose "wipe data/factory reset", "wipe cache", "advanced-> wipe dalvik".
now return to recovery menu and choose "backup/restore"->"restore->2011-06-11.14.14.27".
this should take a couple of minutes.
when its done, go back again to recovery menu, and choose again "wipe cache", "advanced-> wipe dalvik".
power off the phone.
11. hold the vol up button once again and power up the phone to go into bootloader screen.
connect your phone once again to your computer and on the rsdlite window choose the "firmware.sbf" file.
press start and flash it.
12. let the phone boot up, congrats you just revived your phone, root it once again using super one click (if needed), install the 2ndinit2.3.apk.
transfer whatever rom you like (dont try sbf's cause that's how I first got in this mess), reboot phone, go into stock recovery and install that zip after wiping data/factory reset. and ohh well you know the rest.
Good luck.
P.S if you can't or dont know where to find the files take a quick search in the forums and youll find most of them.
Reserved
reserved
when i flash firmware.sbs it takes me back to Android Bootmenu when it reboots please help. thanks
Shouldnt happen, make sure you Wipe Data, and cache, before the nandroid backup and after the nandroid backup.
only then u can flash the firmware.sbf
if the bootmenu still comes up simply choose "Boot-> set default-> normal". and reboot.
if still comes back to bootmenu (and i hope you are talking about bootmenu and not bootloader). install through custom recovery your favorite ROM and don't forget the corresponding Kernel.
good luck!
Is that work with bl7 ???
I've been trying to restore my phone for weeks, up until this thread, I started to think the internet couldn't help me. You are a god amongst men.
OK, banging my head against a wall here; I have 2 defy's. Mine has been to a war zone 4 times, I've replaced the screen (and the waterproof gasket) once, It's broken (the case) but still works except for the fact that the last time I had to flash an sbf I messed up the charging ability with the "macguyver" method.
Now I recently got a pristine looking red lens defy from a friend who said it wasn't booting...It "tried" but never stayed booted long. I tried immediately flashing one of the fixed sbf's with CM10 on it, and ever since I get the bootloader 09.10 code corrupt message.
I've tried the method listed here (by the way the first firmware in OP won't download for me, something about violating some terms of agreement?) the one labeled simply "firmware" downloaded.
Still no joy. Every flash I get all the way through code group 32 checksums match. Everything after that fails. Have tried multiple CEE, Nordic, Chinese, even Defy+ sbf (the new defy has red lens) with no luck.
Likewise when I tried flashing via linux (sbf_flash). The other night after battery out for quite awhile it led me to believe it had started working, and allowed me to get into recovery and wipe everything, but it was all false hope. It still did not boot (motorola M boot loop) and likewise, it still did not flash.
Anyone have any ideas how I can proceed to fix this thing?
I thought I had this thing figured out but obviously I was mistaken.
thanks in advance
I just unbricked my phone again yesterday after trying the latest cm10 sbf with no luck, so i can guarantee this method still works, however the firmware.sbf file is really needed and also the nandroid backup, so here's what i'll do:
1. i'll check what links are broken and reupload the necassery files.
2. I'll clean the the first message and update the links
so check back in about an hour
Thanks a lot for posting this. Tried to restore my phone using lot of other posts since the last 3 to 4 days days, but all in vain.
Was anybody able to install CM10 over this? After the installation, the phone is going into boot loop.
Thanks rtk217 for starting this guide very useful for noobs...
I've made some video tutorials using a few of the guides in the forums here...
hope it helps someone...
Its a complete step by step.
Part 1 of 4. This part deals with preparation of all the required files to successfully complete the custom rom installation.
http://youtu.be/jMAlys2_KG4
Part 2 of 4. How to restore Defy to default
http://youtu.be/6SUysKZ2E5Y
Part 3 of 4. How to root using SuperOneClick and install clockworkmod.
http://youtu.be/hd3_SRbkUWw
Part 4 of 4. How to install 2ndinit recovery and install CyanogenMod 10 Jelly Bean 4.1.2
http://youtu.be/gNPacGesWOI
I am still not able to install CM10. I had bricked my phone a week ago, so I followed this post using the below steps:
1. Flashed with JORDN_U3_97.21.51.sbf.
2. Installed 1.4.2 Sndinit..
3. restored the nandroid backup 2011-06-11.14.14.27
I am able to restore Froyo...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?
k.manojraja said:
I am still not able to install CM10. I had bricked my phone a week ago, so I followed this post using the below steps:
1. Flashed with JORDN_U3_97.21.51.sbf.
2. Installed 1.4.2 Sndinit..
3. restored the nandroid backup 2011-06-11.14.14.27
I am able to restore Froyo...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?
Click to expand...
Click to collapse
Have you got a Defy or Defy+ as you are trying to install the cm10 zip for MB526 (Defy+)
I have a defy mb525.. The one i tried to install is a 2nd boot build that is common for both mb525 and mb526
k.manojraja said:
...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?
Click to expand...
Click to collapse
Why are you using 2ndInit 2.3???
All the guides and FAQs will tell you to use 2ndInit 1.4.2
hey i have the same problem did you fix it?
k.manojraja said:
I have a defy mb525.. The one i tried to install is a 2nd boot build that is common for both mb525 and mb526
Click to expand...
Click to collapse
hey i have the same problem did you fix it?
Thanks ...
Hay, Ur are a genie to me.. I tried so many mods after my imei no is gone. Wifi not working, issues with signal catching.. Now with your step by step guide i was able to overcome all of those... Thank you very much.
cmcooper123 said:
hey i have the same problem did you fix it?
Click to expand...
Click to collapse
Yep... Please see the thread http://forum.xda-developers.com/showthread.php?t=1618718&page=32
Look at pages 31 and 32...
k.manojraja said:
Yep... Please see the thread http://forum.xda-developers.com/showthread.php?t=1618718&page=32
Look at pages 31 and 32...
Click to expand...
Click to collapse
but if i flash defy plus firmware on a defy mb525 wont that brick it?
---------- Post added at 12:05 PM ---------- Previous post was at 11:24 AM ----------
cmcooper123 said:
but if i flash defy plus firmware on a defy mb525 wont that brick it?
Click to expand...
Click to collapse
lol my bad it did brick it kind of
flashed DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
then JORDN_U3_97.21.51.sbf
now it has a black screen but in boot loader mode sigh
any way this is were i am at:
http://forum.xda-developers.com/showthread.php?t=2032711
SIGH
cmcooper123 said:
bwithut if i flash defy plus firmware on a defy mb525 wont that brick it?
---------- Post added at 12:05 PM ---------- Previous post was at 11:24 AM ----------
lol my bad it did brick it kind of
flashed DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
then JORDN_U3_97.21.51.sbf
now it has a black screen but in boot loader mode sigh
any way this is were i am at:
http://forum.xda-developers.com/showthread.php?t=2032711
SIGH
Click to expand...
Click to collapse
I am really not sure if you have read the posts properly. I had no problems in flashing the defy plus sbf. The defy plus sbf that I gave you was a bl6 version and you can never downgrade to froyo.
97.21.51 is a Chinese éclair with bl5. 2nd boot builds were not working on bl5.
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
stickplayer said:
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
Click to expand...
Click to collapse
So you've tried using fastboot to flash a custom recovery image? The command fastboot is a part of the Android SDK.
fastboot flash recovery <name of recovery .img>
There's plenty of stickies and information in this forum, which I won't re-hash here.
The stock recovery WILL show the android with the red triangle. To get into recovery from there, I believe you need to hold the up volume key. Other recoveries shouldn't do this though. Perhaps you should try using ROM Manager or Goomanager to flash a recovery from within android.
It took several attempts - flashing stock, then cwm, from the toolkit, before cwm finally "took". It's all working now.
So I got this Defy+ (story here if anyone cares).
I formatted the SD card, put a compatible *** ROM on it, restarted.
When the blue led flashed, I pressed power + vol. down, so I was able to start recovery. Then I cleaned up, wanted to install the ROM. I got an error message something like 'it did not succeed' then also prompted if I want to restore root access with which there was a problem with, I clicked yes.
Now if I start the device the red Motorola logo turns up then nothing, no blue LED to boot into recovery. So what's next?
Sorry. Anyone has any idea? Or am I supposed to be without phone?
Pls. help!
looks like u bricked ur phone
So here is what you should do:
1) Get RSD Lite
2) Download a compatible SBF
3) Flash it and get the phone up and running
Go through the DEFY Forum for instructions flashing and stuff
this might help
http://forum.xda-developers.com/showthread.php?t=966537
shashank3131 said:
So here is what you should do:
1) Get RSD Lite
2) Download a compatible SBF
3) Flash it and get the phone up and running
Go through the DEFY Forum for instructions flashing and stuff
this might help
http://forum.xda-developers.com/showthread.php?t=966537
Click to expand...
Click to collapse
Thanks for your feedback.
1. Your descriptions are too advanced for me. I can understand straightforward step by step instructions starting from square one
2. The current situation:
http://forum.xda-developers.com/showpost.php?p=52092537&postcount=738
3. Most of the 1st post here: http://forum.xda-developers.com/showthread.php?t=1216982
is also written in a too advanced language for me.
I am not an expert in hacking phones, I haven't done it on dozens of other devices, this is my first.
Now what's next? I truly appreciate you.
magicphone said:
Thanks for your feedback.
1. Your descriptions are too advanced for me. I can understand straightforward step by step instructions starting from square one
2. The current situation:
http://forum.xda-developers.com/showpost.php?p=52092537&postcount=738
3. Most of the 1st post here: http://forum.xda-developers.com/showthread.php?t=1216982
is also written in a too advanced language for me.
I am not an expert in hacking phones, I haven't done it on dozens of other devices, this is my first.
Now what's next? I truly appreciate you.
Click to expand...
Click to collapse
Looks like you'll need to start over from scratch. I'll try:
0. Make sure your battery is charged, if possible. Power loss while flashing will brick your phone. I think the Defy refuses to flash if it's low on power, but i'm not sure on that.
1. Get RSD Lite. There's a link in the Beginner's Guide under How To Flash. Make sure your Motorola USB Drivers are installed.
2. Download a SBF from here. I only have a regular Defy, so i can't recommend a + one, just try one that fits your country.
3. Open RSD Lite, click the three dots [...] and choose your SBF.
4. Boot up the Defy in Bootloader mode (VolUp+Power) and connect via USB.
5. Wait until RSDLite identifies your Defy (can take a few seconds) and the Start button becomes available. Click it and wait, flashing takes a while. When done, it should say "finished" under "status" and "pass" under "result", so disconnect and power up the phone. After a looong boot (can take 10+min), you should end up in a stock Android.
6. Charge your battery. You really don't want your phone dying in the middle of a flash.
7. Meanwhile, download some stuff and put it on your SD card:
The latest Framaroot
2ndInit 2.3
defy_twrp_recovery_2.6.3.0.zip
The CM11 nightly of your choice
BaNkS Minimal GApps for 4.4.2 (If needed)
8. Now root the phone: First allow installing apps from unsafe sources in the phone settings, then install Framaroot using a file explorer. Run the app and root (Gimli).
9. Install and run 2ndInit, Click Install 2ndInit Recovery, reboot. Wait for the LED to turn blue, then press Volume Down and you should end up in the custom recovery (CWM).
10. In CWM, navigate to "install zip from sdcard", choose defy_twrp_recovery_2.6.3.0.zip and flash it. Reboot into recovery again, which should now be TWRP.
11. In TWRP, first wipe data/factory reset, then install your CM11 nightly. Reboot into system. That will again take a while.
12. If you need GApps, then reboot again, wait for the splash screen and choose recovery, then install the GApps file.
And that should be it, i hope i haven't forgotten anything. In any case, you should be aware that CM11 on the Defy is pretty much beta at the moment, so you shouldn't expect a totally stable system with everything working like it's supposed to.