Hi there
I installed SlimROM Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344 (mine is mb525, but the ROM changed my 525 to 526) a while ago and everything was working fine until yesterday
I had an 8gb sdcard and I decided to take the SD and put a bigger one inside the device, and when I decided to boot it, it got stuck and Motorola logo and it bricked.
So I tried to use RSD Lite (5.3.1) to flash stock ROM (2.2.1) JORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF
And RSD failed to flash it with error: erasing subscriber unit.
My battery died and I was able to make a McGyver fix with no problem, but RSD does not flash it at all, and I even tried to wipe cache and data from the recovery boot and it also did not work.
Is there a way to revert SlimROM to Stock ? Or even to use RSD to flash another SBF (that works) so I can reinstall SlimROM here ?
It was weird that my phone was working just fine before I tried to replace the SD card and now nothing works.
tks
BUMP
I even tried to flash DFL RSD and still no luck
Again: error about subscriber unit
Any ideas ?
Tks
Related
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
I have the exact same problem you have. Been banging my head against this thing for 3 days without a solution...
You have to install latest 2nd init from here: http://forum.xda-developers.com/showthread.php?t=1032212.
Follow instructions (like reboot twice...). Then flash a Defy+ rom without kernel. The CM7.2 DEFY+ nightly's don't contain the kernel so you won't have a problem. You can find a link in the first post of CM7 threat.
To get everything working, you might want to check the "100% battery and ..." threat in the Dev section.
For CM9, I thing you just need to install the latest nightly on gb kernel, don't know this one. If you search a bit, you'll find everything.
Yeah，I have the same question that drived me to die~！
rjbathgate said:
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1382284
u will have to flash stock sbf file using rsdlite.it worked for me twice
check this link for sbf file of ur build
http://forum.xda-developers.com/showthread.php?t=966537
then download version 2.0 of 2nd init and select install 1.0.7.this should work
Stuck in bootloop with every os in install
rjbathgate said:
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
Click to expand...
Click to collapse
I have the same problem as you .. but in "MOTOROLA DEFY" now to break this bootloop .. i flash this particular SBF > JORDN_U3_97.21.51.rar to work again .. n following the procedure, i tried to upgrade it with os {CM7.1 or CM 9 120416, 120613 / CM10 120904, 201220912, 20924, 20130307} i ended up in Bootloop .. the recovery software i installed is 2ndinit 2.0 and stable version 0.6 .. it works without error. The procedure i use is in recovery mode: first wipe data/ factory reset > wipe cache > wipe delvik cache .. then install the zip file .. but when i restart .. i stuck in the M" Motorola" GoMgle" logo please help me to provide .. stable sbf file and OS GB rom to flash on my defy ?
I have installed the rooted BL7 DFP-231 SBF and everything works fine, but when I install 2ndinit the phone goes into a boot loop and I have to reflash it with RSD Lite again.
try to flashing the stock sbf, then root it from there.
There's no real way to root BL7 that people know of.. the only way is to flash the rooted SBF.
Does anyone have any idea?
Hey
try this Link
It might work
Got it all working and flashed with CM7! v1.4.2 gives permisson errors, 2.0 and 1.9 put my phone in a boot loop.. so I figured it may be because it's actually downloading the recovery you select instead of installing it locally, so I went to 1.7 and it worked like a charm!
Hi.
I have a defy plus .2.3.6 rooted with 2ndinit recovery.
every ROM I've tried to flash makes the phone stuck in bootloader menu, so i had to flash SBF again.
am i do something wrong? I've flashed a lot of roms on defy mb525, and everything worked fine.
thanks and sorry for my terrible english.
Sow now you are stuck in bootloop or you can not flash a custom rom?
I just flash SBF and go back to stock rom.
try wiping data in stock recovery .
(if you access it)
No access to recovery. boot right to the bootloader.
Reply!
Firstly is your defy rooted? If yes, install 2ndint and go to recovery by switching off your phone and press volume+ and power on button.
The problem you are facing is because you are not clearing cache before flashing a custom rom. Happened to me once so i know! Follow this procedure to the line and you should be fine!
http://forum.xda-developers.com/showthread.php?t=1663613
Hmmmmm
What bootloader you have? I think... v7
Teoretically you can use any 2.3.6 ROM
Yup, V7.
The only rom I was able to install it is CM9.
I'd tried this:http://forum.xda-developers.com/showthread.php?t=1667536 with the same results.
Hi all,
its been days I am using CM10 and it started to be choppy and randomly "fast reboot"ing so I decided to go back to CM7.2. The moment I flashed CM7.2 zip via recovery my phone was stuck in bootloops.
So I decided to downgrade to froyo rom (which I have previously used to downgrade my phone as well, http://forum.xda-developers.com/showthread.php?t=1037076)
After successfull flashing through RSD lite my phone is stuck in the motorola bootscreen for ever (not the bootloader but the OS boot screen)
Kindly suggest me if I am doing something wrong here :/ I cant get it resolved anyhow.
Thank you
Resolved: I downloaded the 3.4.2 177-003 UK rom and flashed it, wiped afterwards and it booted.
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Also relevant:
http://forum.xda-developers.com/showthread.php?p=48088388#post48088388
Achiron said:
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Click to expand...
Click to collapse
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
leandrolutz said:
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
Click to expand...
Click to collapse
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Achiron said:
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Click to expand...
Click to collapse
The defy doesn't really brick, because the bootloader is locked.
It may be no charge in the battery...
You need to use an external charger, or McGyver method, because the defy won't charge by the usb or wall charger...
After you make it, try RSD again, and choose the right SBF, from your carrier.
Hope it helps... gogogo defy :victory: