(Q) Atrix 2 BMM Error - Motorola Atrix 2

Hey guys , so I just got an atrix , was on stock ICS , installed bmm , I have an razr and I have bmm for umts_spyder so i installed it
Long story short , I wiped and restore ics and bmm but I'm getting an error from bmm saying busybox error
I already tried installing a new busybox on playstore but no luck :silly:

XbzakdX said:
Hey guys , so I just got an atrix , was on stock ICS , installed bmm , I have an razr and I have bmm for umts_spyder so i installed it
Long story short , I wiped and restore ics and bmm but I'm getting an error from bmm saying busybox error
I already tried installing a new busybox on playstore but no luck :silly:
Click to expand...
Click to collapse
Are you getting the error in recovery or in the app itself? Every time I've seen that error was in the app and it boot looped on the next reboot requiring an FXZ flash to get it back up and going.

1BadWolf said:
Are you getting the error in recovery or in the app itself? Every time I've seen that error was in the app and it boot looped on the next reboot requiring an FXZ flash to get it back up and going.
Click to expand...
Click to collapse
In the app itself , I already tried updating busybox but I guess thats not the case now , is it ?
Later I'm going to try restoring it with firmware SEARET because I restored it with "fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-220-EDS-3-65-release-keys-Retail-05_hktwn.tar"
Is there hardly any difference between the one I restored and this both ? " 6.7.2_EDEM-18-SEARET_cfc.xml " and " 6.7.2_EDEM-18-ASIAOPS_cfc.xml "

Related

[Q] Updating to 4.1.1 OTA

I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )

[Q] Clockworkmod recovery for spice mi410

Hi all i tried to use Rom manager to flash my Spice mi 410 for the first time. I wanted to install ice cream sandwhich, jelly bean etc on my phhone by using various custom roms available here. I was very excited and watched youtube videos about how to do it and followed each step like clearing cache, dalvik etc. When i started Rom manager it said i needed clockwork mod , i then saw its list but my phone wasn't listed , then i searched google endlessly and found a version 4 for the phone , i copied it and made backup and then flashed my phone, the update ended with success message but when i restarted it it got stuck in boot loop, then again i searched internet ; someone said it could be because of wrong version of clckwork mod so then i fond a version 5 for my phone when i copied it , it still showd a version 4 in rom manager but whwn i go to recovery mode there a version 5 is written. So now also whichever rom i install it installs perfectly but gets stuck in a boot loop. i have no idea where i might be wrong!
Sorry for being verbose but i am frustrated here as its my first time flashing but even after following all iinstructions i get no result. (And why the hell Rom manager couldn't automatically found a clockworkmod for a phone or use a single file for every model!! ) Please if you can five link to a valid clockworkmod recovery file for spice mi410 then i would really appreciate it or if you have any advice or suggestion please do tell thanks a lot.
I don't know when i will be able to taste ice cream sandwhich
Hi,
Might I suggest this link:http://forum.xda-developers.com/showthread.php?t=1278027
Hope It helps
Daniel120201 said:
Hi,
Might I suggest this link:http://forum.xda-developers.com/showthread.php?t=1278027
Hope It helps
Click to expand...
Click to collapse
thanks i installed it, but it says current recovery: clockworkmod 4.0.1.5 though its version 5. is this ok??
cwm
I don't know how to install CWM too
Maybe it is an error or something.
I didnt install it so I dont know anything about it.
Anyway you can try to install ICS
Hope it works.
Oh and btw you should flash it via fastboot.With fastboot you are sure that it installed ok because you flash it manually.
Hope this helps .
Daniel120201 said:
Maybe it is an error or something.
I didnt install it so I dont know anything about it.
Anyway you can try to install ICS
Hope it works.
Oh and btw you should flash it via fastboot.With fastboot you are sure that it installed ok because you flash it manually.
Hope this helps .
Click to expand...
Click to collapse
Sorry for a noob question...but what happens if something wrong happens with fastboot? will i still be able to restore it with CWM?
Well if the fastboot flash doesnt work your phone will boot into fast boot mode so that means you can flash your old version of cwm back .

Rooted device doesn't show "Tampered device" screen on boot

Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Click to expand...
Click to collapse
Hi, are you using a custom ROM or the stock ROM? The apps reappearing issue is on the stock ROM and happens on the 4.1 Jelly Bean ROM because HTC in their infinite wisdom (lmao who did I copy) introduced a write-protect feature in the Jelly Bean kernel. So installing stuff will work, but only in recovery when the kernel isn't active. I assume this is how you installed Superuser - through recovery. To overcome this issue you can flash a custom ROM like ViperOneS or if you don't want a custom ROM you can flash a zip in recovery which I will provide the link to shortly
Edit: page 212 of the official jelly bean thread in the general forum
Sent from my One S using Tapatalk 2
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
tominozh said:
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
Jeeza said:
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Click to expand...
Click to collapse
nightlys are stable enough to be daily drivers.
real187 said:
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
Click to expand...
Click to collapse
Thank you all for your replies! I'll try and flash this zip with twrp..the phone was used, but the previous owner did nothing like flashing stuff, or rooting..
Does flashing this package allows me to permanently delete system apps?
And are there real benefits with flashing a non-stock kernel?
Meanwhile, bought flash image gui, flashed the kernel with it, and again with recovery. Now I can uninstall system apps permanently!
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
mr_verystock said:
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
Click to expand...
Click to collapse
On the Hboot screen it says clearly S-on...and i'm sorry but i didn't understand your "Kernal reboot would force it to reinstall"

problem flashing roms on moto g xt1032

Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now
Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great
hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)
A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?
will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.

[Q] Moto RAZR XT910 - Not able to Flash

Hello Guys,
I installed JB leak in my Moto RAZR xt910 and was using till now,
And i didnt have any CWM Recovery installed in mine, so to install that , i tried a thread from xda ( cant remember which one )
It was "RazerTouchBlack.apk" . after installing that and trying to install CWM, my phone showed error " Encryption Unsuccessful" and was not able to proceed further.
Then i decided to Flash it with stock ROM, tried several ROM's with RSD Lite.
For every ROM , It fails at "cdt.bin_signed" -> PHONE returned FAIL
What am i supposed to do ?
I just want my phone back alive.
- John
JohnTUH said:
Hello Guys,
I installed JB leak in my Moto RAZR xt910 and was using till now,
And i didnt have any CWM Recovery installed in mine, so to install that , i tried a thread from xda ( cant remember which one )
It was "RazerTouchBlack.apk" . after installing that and trying to install CWM, my phone showed error " Encryption Unsuccessful" and was not able to proceed further.
Then i decided to Flash it with stock ROM, tried several ROM's with RSD Lite.
For every ROM , It fails at "cdt.bin_signed" -> PHONE returned FAIL
What am i supposed to do ?
I just want my phone back alive.
- John
Click to expand...
Click to collapse
Your bootloader is locked. Flash your phone back to stock LINK and install THIS as a working recovery system (Its Safestrap including TWRP 2.7)
Can't Flash
LS.xD said:
Your bootloader is locked. Flash your phone back to stock LINK and install THIS as a working recovery system (Its Safestrap including TWRP 2.7)
Click to expand...
Click to collapse
Hi,
I tried the Stock ROM which you mentioned and it gives me an error
"E: Signature verification failed"
Installation Aborted
??
:/
And is there any was i can install CWM recovery by flashing ?? or safestrap or any recovery ??
Thanks guys ... I installed latest ROM and it worked... Thanks a ton !
JohnTUH said:
Hi,
I tried the Stock ROM which you mentioned and it gives me an error
"E: Signature verification failed"
Installation Aborted
??
:/
And is there any was i can install CWM recovery by flashing ?? or safestrap or any recovery ??
Thanks guys ... I installed latest ROM and it worked... Thanks a ton !
Click to expand...
Click to collapse
Problem solved?

Categories

Resources