Related
hello i just wanted to see if i still could get help with my useless device
Ok so yesterday ive rooted the phone and today i tried to install cyanogen mod 7 rom
i used rom utility which i ve downlaoded from android marketplace
now sometimes my phone boots and gets to the logo loop
ive heard that clearing cache and settings would work but i cant access these menus as my hboot is not reacting to my key presses , i tried to reflash the phone but nothing came with success.
I used android sdk and RUU but nothing with success .
maybe anyone would teamview me or give me step by step tutorial how to get this phone alive again would be appreciated
You will be rewarded
You rooted the Phone with a App from the Market?
You need if your HBoot is lower then 1.* the unrEVOked Tool.
If its 1.* there is no way to flash it.
Okay, maybe it worked with yout root app from the market, dunno, but i dont think so.
So you cant access while pressing volume down (keep holding) and switching on the phone the bootmanager? oO thats no good.
The Logo will stay up to "15minutes (<-?)" after flashing a new Rom. In this time its possible, that you Phone restarts automaticly. its normal. Switch it on an wait up to an half hour. If it keep staying in the boot sequence while showing the logo you got a problem .
I think there isnt a more unsave way than a "Flash by teamviewer". You have also pay attention to the phone while flashing. on TV you cant keep an eye on it.
But how can you reflash your phone without getting access to the bootmanager/ HBoot? I think you habe to access the clockwork to flash cm7 *thinking*.
If u nowhow to use adb try n get a adb logcat if possible
Sent from my HTC Wildfire using XDA App
Hi borris and daddyspud thanks for your reply ,i cant move around in hboot ,my hboot version i 0.80.0003
Ive rooted it using unrevoked with clockwork mod on it.
now even when i get it to boot it just loops in cyanogen animation,should i leave it for 15 minutes to do its thing?
also im new to this so i dont know anything about sdk and adb,all i did is saw the tutorials using it ,so i thought i would use it just to give it a go
HBoot 0.8 is rootable, so its okay.
If there is still an animation while you see the CM Logo everything is fine.
If it freeze for some minutes is there a problem. The Animation shows you "i am working / installing".
Yes, let him do his thing for some Minutes.
I think everting should be okay and after some minutes it will work like normal.
It reboots sometimes it self, but this is also okay.
I dont know... does the new CM7 also install a new HBoot? So its possible why you cant move around in it.
Do you wait about 10 seconds before you try to move around in it? Because in the first seconds it looks like it freezed an then it start a test or something. this takes about 10seconds then you can use it.
Its not bricked if its turning on.
Can you get into recovery? If you can try flashing the 4.1 kernel.
If that doesnt help, go into recovery and do a full wipe. Clear cache and dalvik, and under partitions menu format everything except SD card. Then flash CM7, then the 4.1 kernel
Remember first boot will take 10-15 minutes. Be patient. If youve done everything right you shouldnt have any problems
Hi and thanks for cooperation ,i left my phone on cyanogen animation for an hour and nothing is happening just animation loop constantly.
I've just tried hboot and it searches for the PC 49 DIAG and says not found after that it freezes and i cant use any menu navigation buttons . in hbot and fastboot.
I dont even know what to do next
Much help appreciated guys
oO
thats weird.
the PC49DIAG is a part of the rom it self. So i think you have to try to re-flash it. Did you try it with or without a goldcard?
before you flash your phone whipe ALL datas on it!!!
If i start in bootloader mode i get also all the "missing" errors but i can still use the vol up/down buttons to navigate around.
That should help.
I think you did something wrong while flashing.
the root failed?
you got an error while flashing?
goldcard?
Try to flash a RUU from shipped roms. DONT flash a Froyo rom, you will get the HBoot 1.* if you do this.
Recoverymode doesnt work in the hboot?
If you try recoverymode you will get a blackscreen with an triangle.
most say "press the power button" to enter the recovery mode. if this doesnt work press the "volum up button (hold it) then the power button" this should enter recovery mode.
**EDIT**
http://shipped-roms.com/index.php?category=android&model=Buzz use a www-rom its without a branding. and use a RUU rom.. and pls dont use a froyo rom. after flashing this your root is gone i think but your phone will be alive again.
dont try the cm7 this time. use a stock rom.
is it alive again?
i talked today to someone who hat exactly the same problem like you.
it was simple to fix the problem... he (you also?) didnt
whipe the phone before he flashed the cm7. thats why it wont stop looping
in the cm7 animation.
after whiping and reflashing everything was fine.
... did you whipe it b4 flashing?
I have Acer Iconia Tab A500 running on Honeycomb 3.1. I needed to replace its software. So what I did was:
1) Rooted my device with that - http://forum.xda-developers.com/showthread.php?t=1138228
2) downloaded and installed AcerRecoveryInstaller - https://market.android.com/details?id=com.interphaze.AcerRecoveryInstaller
3) downloaded DextersGalaxyA500-p1 and DextersGalaxyA500-p1-avi-patch from http://dext3r.komodin.org/
4) Copyed them to my internal memory, the downloaded app which allowed me to copy to SDCard and copyed to SD card.
5) started AcerRecoveryInstaller and clicked boot into recovery.
6) selected install from SD card
7) selected DextersGalaxyA500-p1.zip
8) install started
9) intall ended and boots (samsung logo) wohooo happy!
10) what the hell is this? Some noise coming from speaker, apps are not responding, device ultra slow - unusable.
11) somehow manage to open AcerRecoveryInstaller click boot into recovery - BOOM! android logo with warning sign, waits about 5 mins then reboots to OS. Thats it.
+ also when I turn of the device, hold power button+sound til the text comes to the corner i get an android logo + warning sign icon, this time its bit different icon. Waits about 5 mins then reboots to OS.
What have I done wrong and how to fix it?
Did you wipe everything, like (dalvik)cache, before installing the new ROM?
Did you check the MD5 checksum on the downloaded ROM?
Can you get into recovery and try to install a different ROM?
Try putting a stock Acer update.zip in the root folder of your micro sd card and then use standard Acer upgrade procedures to get back to stock. (i.e hold the power and vol+ button while booting).
Should that not work, I'd try to do a complete factory reset / wipe using the rotation lock method described elsewhere in this forums. (sorry I cant recall the exact order of things well enough to quote them but a quick search will find them... ).
pattiman said:
Did you wipe everything, like (dalvik)cache, before installing the new ROM?
Did you check the MD5 checksum on the downloaded ROM?
Can you get into recovery and try to install a different ROM?
Click to expand...
Click to collapse
1) No
2) No. With what should I compare it (dext3r.komodin.org didn't give out MD5 hash codes)
3) Luckyly, I found out that I can (had to hold start+volume up little bit longer)
What should I do now? Select: "wipe data/factory reset" + "wipe cache partition" + and then install from SD card again?
TheDroidProject said:
1) No
2) No. With what should I compare it (dext3r.komodin.org didn't give out MD5 hash codes)
3) Luckyly, I found out that I can (had to hold start+volume up little bit longer)
What should I do now? Select: "wipe data/factory reset" + "wipe cache partition" + and then install from SD card again?
Click to expand...
Click to collapse
Pretty much, yes.. You should always do this when installing a different ROM. It's often OK for new versions of the same ROM, but between different ROMs you must wipe your device or you risk problems.
Thank you guys!
Everything working after cleanup and new install, really appreciate it!
This is why these boards are great, you got your problem solved in a matter of a couple of hours from experienced members. XDA is the greatest!
See that's what these forums are for. Thanks for helping this person out guys. Keep it up
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
hi there...
just installed CM7 this weekend. worked fine for 2 days
After restarting the ms2, it got stuck in a bootloop.
I can flash a sbf with rsd lite from, finishes OK, but when it says, rebooting, well...
it still stuck in a bootloop.
In recovery mode, i can do a cache wipe and factory reset. But there is a error message at the bottom, telling:
E: Can't open /cache/recovery/command
E: Can't open /cache/recovery/caller
Could I successfully flash with RSDlite from Linux? which version?
Is there a way to restore the ms2 from dev console?
Thanks a lot
Do you test to Wipe Data with stock moto recovery ?
Here step 7 to 11
I think your request must be on "General" section
I suspected it might be related the CyanogenMod intstall. But move to "general" if necessary
Have done steps 7 - 11
but still ms2 bootloops
OMG - if broke it - my wife kills me
I hope your wife don't kill you LOL
See this thread and particulary this with r2beta0 tips:
EVEALEX62 said:
I have do this (all step 1 to 11 because "boot up the phone manually" ) with the sbf 2.2.2 officiel but modify whith this post :
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I did exactly the same, as in the other thread.
And thank god, my ms2 booted up
So everything seems fine for now und no one should get killed
Many Thanks!
Nice for you
Moved to proper forum.
Hi all, Emiliano from Italy. I firstly wanted to thank you all for your support.
Even being my first post here, I've been following you since some time.
My problem looks exactly the same: bootloop... bootloop... bootloop.
No matter how many I tried flashing back the original ROM for my M2 (SBF file always worked before!!! so I'm sure is the correct one for my smartphone).
I tried also the procedure with depacking described above with no progresses.
Anyway I already had noticed that after renaming cg66 to cg37, depacker wasn't able to see it in the list of cgs before repacking, so that final fbs was 300MB less.
Something wrong I made? (tried on 2 pcs with Vista Home and Business)
Unluckily I cannot even try to wipe data because I cannot enter in recovery mode (On + X -> Android robot with mark -> but nothing happens after pressing magnifying lens or any other key).
Could someone, please, help me before using my bricked M2 for building a new house?
Devilsball said:
Hi all, Emiliano from Italy. I firstly wanted to thank you all for your support.
Even being my first post here, I've been following you since some time.
My problem looks exactly the same: bootloop... bootloop... bootloop.
No matter how many I tried flashing back the original ROM for my M2 (SBF file always worked before!!! so I'm sure is the correct one for my smartphone).
I tried also the procedure with depacking described above with no progresses.
Anyway I already had noticed that after renaming cg66 to cg37, depacker wasn't able to see it in the list of cgs before repacking, so that final fbs was 300MB less.
Something wrong I made? (tried on 2 pcs with Vista Home and Business)
Unluckily I cannot even try to wipe data because I cannot enter in recovery mode (On + X -> Android robot with mark -> but nothing happens after pressing magnifying lens or any other key).
Could someone, please, help me before using my bricked M2 for building a new house?
Click to expand...
Click to collapse
Hi
Have the same problem here since 6 months now,
Just to see if it s the same thing as me, try this please:
In my case i can t acces recovery, only way is to hold X and plug the phone to the wall, did not resolve nthing for me, but maybe you re luckier...
post results...
C ya
Hi Amir4Life,
thanks for reply and for your suggestion.
Unluckily I cannot access recovery mode.
All I get when pressing X is the green robot with Exclamation mark, but no matter which key I press after, it gets stuck at that point (so that I'm bound to take away battery to turn smartphone off) and cannot access or see any menu to operate wipe.
Tried also reflashing other roms through rds lite (bootloader works efficiently) or through ubuntu live cd "sbf_flash system", but the only fsb that always worked for me turns out to be a bootloop when rebooting.
Unluckily nothing seems to help me in this situation, so far.
It's still a bootlpop and no access to recovery mode.
Thanks anyway for your help and happy and special new year to you all!
At the 'exclamation sign + green android guy' screen, you have to press 'vol up + vol down' together.
Now you will get the options like 'wipe data' etc. etc. Scroll through options using vol up or vol down and select using power button.
sahilarora911 said:
At the 'exclamation sign + green android guy' screen, you have to press 'vol up + vol down' together.
Now you will get the options like 'wipe data' etc. etc. Scroll through options using vol up or vol down and select using power button.
Click to expand...
Click to collapse
Thanks Sahilarora,
If I had read you before I would have saved a lot of time trying all possibile combinations of keys on the keboards (since magnifying glasses didn't work)!!
Then just by chance I discovered myself volume up + down while pressing chaotically all buttons and it worked to my best suprise, showing me finally the belated list of options, together with blessed wipe data factory
Since yesterday evening my Milestone 2 is wonderfully working again, as fresh as a daisy!
Thank you so much for your contribution, hoping it could help also Amir4Life and oll pthers in a similar situation.
Happy new year (started in the best way).
Glad for you, I was about to tell to do what sahilarora911 told ya,
I expect i m the only one who stays with brick'd phone... my luck.
C ya
Amir4Life said:
Glad for you, I was about to tell to do what sahilarora911 told ya,
I expect i m the only one who stays with brick'd phone... my luck.
C ya
Click to expand...
Click to collapse
Could explain in details which is your problem, and which methods have you already tried to solve it?
If not me, maybe someone else could help you.
Hi Emiliano! It seems to be that we share the same problem. Did you found a fix to it? Thanks!
Devilsball said:
Hi Amir4Life,
thanks for reply and for your suggestion.
Unluckily I cannot access recovery mode.
All I get when pressing X is the green robot with Exclamation mark, but no matter which key I press after, it gets stuck at that point (so that I'm bound to take away battery to turn smartphone off) and cannot access or see any menu to operate wipe.
Tried also reflashing other roms through rds lite (bootloader works efficiently) or through ubuntu live cd "sbf_flash system", but the only fsb that always worked for me turns out to be a bootloop when rebooting.
Unluckily nothing seems to help me in this situation, so far.
It's still a bootlpop and no access to recovery mode.
Thanks anyway for your help and happy and special new year to you all!
Click to expand...
Click to collapse
thank you ...................
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.