Hi,
Today I installed the latest CM11 version and everything went fine. The room booted correctly. Then I tried to reinstall bmm but the installed gave me a busybox error and uninstalled bmm completly. After that I rebooted the phone but it is bootlooping on the M logo and a black screen.
Is there any way I can fix the bootloop without having to fxz with rsd lite and lose all my data?
Thank you.
norkitt said:
Hi,
Today I installed the latest CM11 version and everything went fine. The room booted correctly. Then I tried to reinstall bmm but the installed gave me a busybox error and uninstalled bmm completly. After that I rebooted the phone but it is bootlooping on the M logo and a black screen.
Is there any way I can fix the bootloop without having to fxz with rsd lite and lose all my data?
Thank you.
Click to expand...
Click to collapse
Sorry, but no. Bootloop without BMM = FXZ time.
norkitt said:
Hi,
Today I installed the latest CM11 version and everything went fine. The room booted correctly. Then I tried to reinstall bmm but the installed gave me a busybox error and uninstalled bmm completly. After that I rebooted the phone but it is bootlooping on the M logo and a black screen.
Is there any way I can fix the bootloop without having to fxz with rsd lite and lose all my data?
Thank you.
Click to expand...
Click to collapse
Fxz the universal antidote..in your case the only antidote
Sent from my MB865 using XDA Premium 4 mobile app
norkitt said:
Hi,
Today I installed the latest CM11 version and everything went fine. The room booted correctly. Then I tried to reinstall bmm but the installed gave me a busybox error and uninstalled bmm completly. After that I rebooted the phone but it is bootlooping on the M logo and a black screen.
Is there any way I can fix the bootloop without having to fxz with rsd lite and lose all my data?
Thank you.
Click to expand...
Click to collapse
U shouldn't have reinstalled BMM there's no need to. Unfortunately u will have to FXZ no other way. Did u make a backup by any chance?
I think it is possible to flash just the system.img using fastboot command..just now thought of that..
Sent from my MB865 using XDA Premium 4 mobile app
Related
PLEASE HELP!! I have successfully rooted the device and was doing ok after flashing CWmod recovery 6.0.1 through E-Z recovery app and running Liquid Rom. I managed to be dumb enough to flash CWMod version 5.8.4.9 through Rom manager and when I rebooted my phone it got stuck in boot loop. I am able to get into CWMod 5.8.4.9 but I cannot restore my backup anymore. I can also data wipe and install a new rom, but it all just keeps going into bootloop and I cannot get past the samsung custom unlock screen. It first flashed that, then the android man pops up on the next screen like its loading something and then just keeps looping through the process. I did not use ODIN for any of this process and I dont know how to get myself back tothe point where I can reboot. Any help would be tremendously appreciated, because I'm dead stuck and in a panic. Thanks in advance for any assistance.
Happend to me last night...
I made the same mistake... DO NOT download any recoveries from ROM manager. I found out the hard way... So the problem now is your phone is stuck using the recovery you downloaded. I am not sure of a quick way using that recovery if you can revert back but... My solution got me where I needed to be in order to get going again.
I had to use Odin to root to stock ROM. Yes when you wipe it will destroy your data but not your pictures, downloaded files, and other files you put on there. When I re-rooted with stock all my stuff for CM10, gapps, and the kexec CWM was there.
So use this guide...
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Section 1!!!!! And follow the steps EXACTLY the way it says to.
This is why i have never liked rom manager...
The best solution for us to flash recoveries is ez recovery free from the market. I would use this going forward once you Odin back to stock
Sent from my SCH-I535 using xda premium
Same **** happened to me.
Odin. I lost my pics and internal memory though...
Sent from my SCH-I535 using Tapatalk 2
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
slegger04 said:
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
Click to expand...
Click to collapse
I had the same problem with 2.1 and 2.5 on my phone. For some reason, the flash does not work on my phone the first time. both times I had to pull the battery when I got stuck on the boot screen then boot into recovery, re-wipe, fix permissions and reinstall. It always worked for me on the second try.
Good luck.
slegger04 said:
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
Click to expand...
Click to collapse
This happened to me once. Try to re-root the phone again then flash it.
Did you do a dalvick cache wipe too? Also were you flashing a kernel with 2.5? Are you coming from stock or a custom rom too? And if you are coming from a custom rom does it use a custom kernel? You should also check the md5 of the rom and verify it didnt get corrupt on download/transfer.
Sent from my SCH-I535 using xda app-developers app
RE
x714x said:
Did you do a dalvick cache wipe too? Also were you flashing a kernel with 2.5? Are you coming from stock or a custom rom too? And if you are coming from a custom rom does it use a custom kernel? You should also check the md5 of the rom and verify it didnt get corrupt on download/transfer.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes i wiped the dalvick, fixed permissions, formatted just about everything and factory reset, when that did not work I formatted and wiped everything before and after the flash. still no luck. I was not flashing a kernel, (to be honest im not even sure how to do that) and im coming from a stock rooted rom that i got when i first rooted with odin. I checked the md5 and everything matched up too.
How!?
rpuleo said:
This happened to me once. Try to re-root the phone again then flash it.
Click to expand...
Click to collapse
How do you re root? would i have to use odin to flash the rooted rom again?
The process of how you flashed sounds right.
When you say it's stuck forever, how much time did you give the phone to reboot. Sometimes with a new rom, it may take 5 min or longer for reboot to finish. If you haven't already, just walk away for 5-10 min before checking it.
Sent from a SYNERGIZED GalaxySIII
Clean rom wouldn't install for me on my phone... Weird stuff happened on the screen during boot animation and then would vibrate like crazy and go into boot loop... I came to realize that it was the kernel and I flashed lean kernel and it worked perfectly... I think these roms act differently on everyone's phones and sometimes there's no rhyme or reason to why things work for some people and not others... Just my. 02 cents
Sent from my SCH-I535 using xda app-developers app
Ok so i FXZ back to stock, and i uninstalled A2Bootstrap, installed Busybox and updated to latest version it installed to system/xbin. Now i installed BMM and try to install and i get a error 'Wrong BMM busybox" what did i do wrong?
Darell3 said:
Ok so i FXZ back to stock, and i uninstalled A2Bootstrap, installed Busybox and updated to latest version it installed to system/xbin. Now i installed BMM and try to install and i get a error 'Wrong BMM busybox" what did i do wrong?
Click to expand...
Click to collapse
Did you have a2 bootstrap installed previously... And did you do the edits required for the boot menu manager to work??
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Did you have a2 bootstrap installed previously... And did you do the edits required for the boot menu manager to work??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, just fix it i guess, all i wanted was stock 4.0.4 so i flashed AT&T version for my stock my original is TNZ.
Darell3 said:
Yeah, just fix it i guess, all i wanted was stock 4.0.4 so i flashed AT&T version for my stock my original is TNZ.
Click to expand...
Click to collapse
How did you fix the issue? I keep getting the busy box error when i try to install to system 1.
ins5736 said:
How did you fix the issue? I keep getting the busy box error when i try to install to system 1.
Click to expand...
Click to collapse
I just flashed AT&T ICS and install BMM from there.
wrong bmm busy box
samsung nexus s 4 g .I seen on the play store description it say it was only for 2 motorola devices so that may be my issue.If not does anyone know how I could fix this to work .I installed latest busybox .I am running slimrom if that matters.
I face the same issue as well. I have a Huawei G700-U00 running ColorOS 4.2.2... please help
androKP said:
I face the same issue as well. I have a Huawei G700-U00 running ColorOS 4.2.2... please help
Click to expand...
Click to collapse
Boot Menu Manager is only for Motorola's OMAP4 device, so on any other device except tegra it wont work.
Sent from my Atrix 2 using Tapatalk.
Yeah Ive been getting this as well. Just dont install busybox from the Play Store. Killed BMM on the install I had and needed to reflash.
I just ignore it and it seems to work alright for the most part. Only noticed this on a custom Roms. Stock rooted doesnt seem to have the problem even when using the busybox installer from play store.
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.