Related
Hallo,
I've been trying to install the updated to update-cm-4.2.7.1-signed.zip.
I've been able to install first the signed-dream_devphone_userdebug-ota-14721.zip and imediatly after that, without reboot, the update-cm-4.2.7.1-signed.zip. Only I was unable to sign in to google right after that so I rebooted and then I was unable to boot it any longer...
Ok so then I retried the whole process but now after flashing the first signed-dream_devphone_userdebug-ota-14721.zip, wich goes ok, the second update-cm-4.2.7.1-signed.zip aborts the installation...
Next to it the installation of signed-dream_devphone_userdebug-ota-14721.zip isn't stable at all... after max one minute the phone crashes, so I'm unable to do anything....
I'm feeling extremely NOOOOOOBY!!!...
Which is probably how I'm supposed to feel...
Uuuugh....
Anyways is there anyone with hints about what I'm doing wrong here?
Thanks!
Greetings,
Geert
did u do a full wipe from CM recovery before putting on the google updates then cyanogen??? i had this issue and it fixes it?
Sorry for the late reply...
I tried to flash the recovery image of cyanogen but itś not possible anymore....
There is no flash_image tool on signed-dream_devphone_userdebug-ota-14721.zip...
Also using fastboot, it says < waiting for device > till eternity...
my advice would be to start from scratch, get dreaming.nbh on ur sdcard. follow the instructions @ cyanogens wiki
i was having a world of **** on my G1 and just went back to RC29/RC7 and started again. if you have the files already on the SD card (CM recovery, official google, latest cyanogen mod) its simply a case of a few key presses.
dont forget to do the telnetd stage. i did and then wondered why i didnt have root access lol
ive never bothered with fastboot, usually just use ADB!
r|ktk|ng
re: 2.3.6 Upgrade issue.
I may have made a mistake.
I recently updated my atrix to 2.3.6. It installed successfully but I decided to flash it back to 2.3.4, which I'm currently regretting.
When I turn my Atrix 4G on, It says 'failed to boot 1'.
If I hold the Volume up and power buttong it says:
'Failed to boot 1, PwrReason: Power_cut, Starting fastboot protocol support'.
Im tried to flash the roms using RSDLite:
att-2.3.4_pudding_preroot and also the
official 2.3.6
The error is:
Failed flashing process. Unable to retrieve interface handle.
I tried to unlock bootloader cmd, but wasn't successful.
Any ideas guys?
As an update, i tried to use fastboot to load images.
Instructions to root Atrix 4G running Gingerbread:
-----------------
Download and Extract Fastboot Files to your C: drive (Download Link)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
---------------
it says:
sending preinstall OK
writing preinstall... Failed remote 00180004.
I can't see to write to boot, system or any component?
Do I need to unlock the bootloader? Sorry this stuff is all new to me, and trying to piece it together.
Please use the search, I faced the same issue, you will have to create a factory cable and using RSDLite, flash the 2.3.6, you cannot flash the 2.3.4
Sent from my MB860 using Tapatalk
Hi Tommy,
I saw you're thread but it wasn't clear what steps you took.
Did you modify the Atrix USB Cable in order to install a 2.3.6 sbf file using rsdlite?
I'm wondering if there is another way.
OP - Flash the 2.3.6 sbf file with RSD lite 5.6 - should get you back up and running just fine...
I tried flashing the:
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012
and got this error in rsdlite
internal error while programming phone.
Then after that if I try it again, or try the pudding 2.3.4 one the error changes to:
Failed flashing process. Unable to retrieve interface ahndle 0x7027.
re: 2.3.6 Upgrade issue
First off let me say I know absolutely nothing of development but I figured I'd be brave enough to experiment any way. So I tried upgrading yesterday with partial success, there was no separate .img files at the time though . I'm rooted and have an unlocked bootloader; what I did was extract the zip file from the cache folder onto my PC then removed ap20bl.img seeing that I read all the horrors of possibly re-locking bootloader and bricking I then zipped the file and named it update.zip and booted the phone to CWM Recovery and tried installing that way. I realized after failing the install since it prompted that it couldn't find the ap20bl.img that there must me a script. Knowing that there'd probably be a size check I did this any way....used a bl.img from the 2.3.4 fruitcake and renamed it to ap20bl.img still failing therefore I assume that it really did check the file size. I then located the updater script and removed references to the ap20bl.img file. I tried install again this time saying something about E:\ unfortunately I don't recall exactly what.....so to take care of that I deleted the cache (probably a bad idea). That got rid of that error but from that point I got an error 6 ever since. I decided to reboot the phone which booted fine. Checked "About Phone" and it said the current version was 4.5.141, I was very happy about that; checked that the phone was still rooted and it was. Calls worked, bluetooth worked.....BUT ....it came time to check the wireless....."ERROR". Yip, no more WiFi. I rebooted to CWM and did a factory reset...rebooted again checked WiFi...now said "Turning on, Turning off, Error". So.......I rebooted to fastboot and sent the 2.3.4 radio (.91), rebooted and still got the error. I decided even though I read not to, to go back to 2.3.4 so I rebooted CWM, did the necessary wipes and reinstalled the 2.3.4 fruitcake then checked WiFi which now worked (or so I thought)....the connection dropped after a while then said error when I checked its status so I rebooted and it worked fine only to have the same issue again. I then did necessary wipes and tried Neutrino 2.1 EE seeing that it was the only ROM I had with me at work still having the same WiFi issue. At this time I haven't done anything else with the phone but hopefully this information will help developers or anyone else
Your only hope is the Motorola Factory Cable, yes it is configured differently, in it the red and brown cable are joined, please see my thread for reference, also you will find lot of articles on the internet, you will not be able to flash without it, been there, done that
Sent from my MB860 using Tapatalk
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2471370
The program get's stuck at analyzing device and doesn't flash or download anything. It would be nice if I can perform at least a factory reset in case something wants to blow up in my face. If anyone has some ideas (ridiculous or not), feel free to let me know.
slicknessessity said:
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
Click to expand...
Click to collapse
Hey man you could try just using Flashify to flash a recovery...its a app...then boot to recovery
I tried using that method. It gives me the same thing. Maybe somewhere in the recovery location (or associated locations) seem to may have gotten damaged somehow during the bad flash? Flashing the phone completely I'm sure would do the trick. I came from the droid 4, so sbf/fastboot flash would solve all my problems. Searching around landed me to a kdz, which seemed to be an equivalent, but isn't working or maybe I'm doing something wrong? Any advice on this would be greatly appreciated.
I went and did a full flash using this method: http://forum.xda-developers.com/showthread.php?t=2448960. Since I couldn't find a recovery fix per se, I decided to flash the whole thing and start fresh (oh well).
It downgraded to 11A in the process, so the same can probably be said for 10B for compatible custom builds.
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
How did you tried connecting phone to odin? Did you went into download mode then connected the phone to pc ?
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
The rom you mentioned is a banned rom
You have 2 options
Option 1
If you can get into recovery mode (Vol up home button power button)
Download any stock based custom rom
Go into cwm
Format system data cache
Mount system data cache
Flash rom zip
Assuming that you are using a stock based kernel it will boot
Option 2
Flash stock rom via odin
See my firmware thread link in my signature
Note you can use standard 5360 firmware instead of the b variant which may be better
Posting to say I didn't get the phone to work still, but I got home without too much trouble. needless to say this thread is no longer an emergency.
I want to express my gratitude to you guys for helping me out, thank you so very much.
Unfortunately as I say the phone does still not work -
With multiple attempts using ODIN I keep getting the hangup at 'setup connection' - I tried on mac via parallels (windows 7) and a windows 8 machine.
I can successfully install a ROM via CWM but the phone gets stuck in a boot loop (samsung galaxy y splash screen) so I'm guessing I have a kernel problem? When I try flashing a new kernel I get the "error mounting /sd-ext!" message, and the same when I try to format it via CWM. I found this: http://forum.xda-developers.com/showthread.php?t=1750888, but I cannot boot the phone so I guess I'm stuck.
My last install attempt was these
http://forum.xda-developers.com/showthread.php?t=2462914 - V3LenoxEvolution ---- SUCCESSFUL INSTALL.
http://forum.xda-developers.com/showthread.php?t=2644262 - Blackheart kernel ---- FAILED, error mounting /sd-ext
Got any other ideas guys? Or do you know where I'm going wrong?
I think I'm in way over my head :s
Many thanks once again!
EDIT: some additional information, I cannot reboot to bootloader, and as far as I can tell I can't replace the custom recovery CWM v6 (I find a different version, boot into CWM v6, click install .zip from sd card and say CWM v5 launches, but when I reboot it's back to v6)
Flash stock rom via odin....
Flashing other diffrent ROM packages won't help until you have right bootable kernel...
So put your efforts towards making it to boot up on a stock firmware....
By ODIN mode
Try installing drivers and checking that no other device is connected to pc via USB.
Also make sure you follow the guide properly....
Then post errors ...or try google...
We'll help...
Sent from my GT-S5360 using XDA Free mobile app
Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!
Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!
Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)