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 had problems with myphone and someonehere advised me to flash the radio again, i did it and now it wont boot ican enter the bootloader options but no recovery or android booting ijust flashed the radio and everything was good no error iused the fastboot method icopied the radio.img(isearched after the one that i already haved on) copied it into the android sd foolder and fastboot flash radio etc ...... now i dont know why it dosent work and franklyim s eriosly thinkyng about flashing it backat its normal state please help me
You have no recovery? After flashing a radio it shouldn't wipe recovery but I have seen roms messed up. So via fastboot flash recovery than flash rom either through fastboot or your recovery
Sent from my HTC Vision using xda premium
i just flashed a ruu again still on italia and now i have to root it again a and no improveents on service anyway i talked to the developer of the rom and he toled me that its stilll on italian cuz i didnt do a full wipe before flashing the ruu personaly wiped the data/factory reset the cache and dalvik is something else i can wipe ?
So my problem is that only froyo 2.2.2 works and I cant find whats the problem.. I had already aurora ICS, oxygen and other costum roms but now no other rom than 2.2.2 works I have instaled costum partition, stock partition tried different CWM s but nothing works. It just shows huiwai logo and that's all.. Official 2.3.5 works only if I format data and cache but later on after a few days everything crashes and I need to erase data and cache again or else it's infinite boot loading. Please help !
try to flash stock partition and than install stock 2.3.5 from DLOAD folder...
and than put a recovery... and flash a custom ROM
Hello,
I have a very strange problem with my phone.
After installing the new ubuntu-touch release on the 17th October and reflashing paranoid android, I can't get any signals on pa (no imei, no baseband). The strange part is, if i install the stock rom, cyanogenmod, aokp, I can get these signals and it will display my imei.
The other thing is, in bootloader it displays the correct baseband and bootloader. (i have installed the one from date I have bought my phone and the one from the thread about paranoid android 3.99 RC2). I also have tried PA 3.99 RC 1 the last version worked with signals.
The first time I have installed ubuntu-touch I had signals and in the recovery i got two new mountpoints firmware and persist. I reinstalled ubuntu-touch and now there are also no signals. I can remember I also have formated firmware and persist. So may this could be the problem. At least I have decided to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2347060 ([GUIDE]99% working unbrick method aslong you can get into download mode )
The problem persist, but the two mountpoints disapeared. (FYI: I have a Nexus 4 16 GB Model)
May one of the mountpoints were not restored correctly by this guide. May someone can backup his firmware mountpoint and can tell me where i have to restore it, because i think the whole /dev/block/mmcblk0 will be restored by this guide, if not so may the persist partition could be the problem and the firmware partition was created by ubuntu-touch and is not needed by android roms. (But I'am not into any android specific partition layouts)
I have backuped the efs "m9kefs1" and "m9kefs2" now. And the Phone runs now on the newest build of cm.
May someone could help me or have an usefull idea. But I can live without ubuntu-touch and paranoid android, but I really like the features of paranoid android.
Best regards
Richard
I assume you tried it with both recoveries just for trouble shooting. Also I know this doe not effect IMEI but did you try flashing radio after PA? Also did you have a backup of PA on your phone and did you try to restore from backup
Ubuntu-touch recovery, its still the same as clockworkmod (if you mean that with both recoveries). I only used cwm to wipe data and install roms.
I also have tested to install radio and boot after pa, without success. In recovery I can see persist and firmware, may it is something pa specific.
I had a backup, but I wiped it. I never thought a backup is a cleaner solution than a fresh rom installation. I thought its only for saving data.
[Solution] [Solved]
The Problem is the newest CWM as mentioned in this thread ([EXPERIMENTAL] Semi-official builds of Omni):
http://forum.xda-developers.com/showpost.php?p=46511999&postcount=4
The solution is to downgrade CWM, you could do this by:
Code:
http://clockworkmod.com/rommanager
Chose Nexus 4 and copy the link of the version you want to download:
Code:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-[B]6.0.4.3[/B]-mako.img
Than change the version number to a lower version, like this:
Code:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-[B][U]6.0.3.1[/U][/B]-mako.img
Go to fastboot mode and erase userdata: (This will delete your private data)
Code:
fastboot erase userdata
Than lets write it again:
Code:
fastboot -w
Go to recovery mode, wipe and format all partitions, at least install paranoid android and reboot to system. Now the services should be back.
May you could skip the fastboot steps, but I stuck at a very long boot (I interpreted this as a bootloop and decided do format all partitions with cwm, install pa and reboot again. That worked for me)
Glad you fixed it but thats why I asked you if you tried both recoveries... I also know some versions of TWRP had that issue but its since been resolved in the latest version. Most have more success and less issues with TWRP not CWM...
Hello People! so here is my case.. i followed this specific Guide to the letter http://forum.xda-developers.com/showthread.php?t=2792022 from a stock Hc Rom/recovery to kit kat used blackthund3rs Flash tool to flash Skrilax_CZ's bootloader and everything went smooth i managed to flash Cwm 6.0.4.5 on secboot without problems too but after i installed the Omnirom i forgot to do a factory reset i just cleared cache and dalvik cache after that the tablet wont boot to the rom it just shows the android logo and then resets by it self problem is that i cant even do a wipe/factory reset through cwm in secboot it just freezes and restarts again tried to install the omnirom again from the zip is gone from sdcard!!! oO along with everything else i guess i can see only 3 folders 0 the clockworkmod one and obb thing is i got the cpuid and sbk number also stock recovery is there. so what happens next? any help will be really appreciated!
ps. Sorry for my long and painfull to the eye post!
Devilhanzo said:
Hello People! so here is my case.. i followed this specific Guide to the letter http://forum.xda-developers.com/showthread.php?t=2792022 from a stock Hc Rom/recovery to kit kat used blackthund3rs Flash tool to flash Skrilax_CZ's bootloader and everything went smooth i managed to flash Cwm 6.0.4.5 on secboot without problems too but after i installed the Omnirom i forgot to do a factory reset i just cleared cache and dalvik cache after that the tablet wont boot to the rom it just shows the android logo and then resets by it self problem is that i cant even do a wipe/factory reset through cwm in secboot it just freezes and restarts again tried to install the omnirom again from the zip is gone from sdcard!!! oO along with everything else i guess i can see only 3 folders 0 the clockworkmod one and obb thing is i got the cpuid and sbk number also stock recovery is there. so what happens next? any help will be really appreciated!
ps. Sorry for my long and painfull to the eye post!
Click to expand...
Click to collapse
We have similar problems man!
http://forum.xda-developers.com/iconia-a500/help/help-a500-brickedi-t3080673