Related
I have been looking through all of the ROMs by all of our fantastic developers and have been paying attention to the developments as they've been happening, and now it seems that everyone is adding in the CWM-on-boot mod.
I'm just wondering, is there a huge bonus from it that I'm missing? Or is it just useful from a dev's standpoint to be able to flash on every boot? Since most ROMs just come with it now, is there a way to remove it and restore the Atrix Bootstrapper app for the occasional CWM run (I heard of the J.Y.Daddy's something or other but does that put everything back to normal?)?
I'm running SuperCharged V5 Update 2, btw, so I still am used to the Bootstrapper app.
iarejohnsmith said:
I have been looking through all of the ROMs by all of our fantastic developers and have been paying attention to the developments as they've been happening, and now it seems that everyone is adding in the CWM-on-boot mod.
I'm just wondering, is there a huge bonus from it that I'm missing? Or is it just useful from a dev's standpoint to be able to flash on every boot? Since most ROMs just come with it now, is there a way to remove it and restore the Atrix Bootstrapper app for the occasional CWM run (I heard of the J.Y.Daddy's something or other but does that put everything back to normal?)?
I'm running SuperCharged V5 Update 2, btw, so I still am used to the Bootstrapper app.
Click to expand...
Click to collapse
To my understanding there is a way to remove it however I would recommend against it.
It's put in there as a safe-guard IMO, and it has saved me from many a nasty soft-brick.
I would leave it mate. It's there for safety's sake!
iarejohnsmith said:
I have been looking through all of the ROMs by all of our fantastic developers and have been paying attention to the developments as they've been happening, and now it seems that everyone is adding in the CWM-on-boot mod.
I'm just wondering, is there a huge bonus from it that I'm missing? Or is it just useful from a dev's standpoint to be able to flash on every boot? Since most ROMs just come with it now, is there a way to remove it and restore the Atrix Bootstrapper app for the occasional CWM run (I heard of the J.Y.Daddy's something or other but does that put everything back to normal?)?
I'm running SuperCharged V5 Update 2, btw, so I still am used to the Bootstrapper app.
Click to expand...
Click to collapse
CWM on boot is nice because if you bootloop, you can just pull the battery to get back into it, meaning you will not have to flash the fxz to get out of softbricks. you can get rid of it by reallowing bootstrap in superuser then running it once.
lkrasner said:
CWM on boot is nice because if you bootloop, you can just pull the battery to get back into it, meaning you will not have to flash the fxz to get out of softbricks. you can get rid of it by reallowing bootstrap in superuser then running it once.
Click to expand...
Click to collapse
oh, okay I guess it's a must have then for all devs
but wait, a couple of days ago I was running Bullet and I couldn't even find the Bootstrapper app; if I reallow it does it just show back up?
iarejohnsmith said:
I have been looking through all of the ROMs by all of our fantastic developers and have been paying attention to the developments as they've been happening, and now it seems that everyone is adding in the CWM-on-boot mod.
I'm just wondering, is there a huge bonus from it that I'm missing?
Click to expand...
Click to collapse
CWM on boot is a handy tool to have as a safety net when flashing things to your phone. Basically it's like this:
Let's say you flash something to your phone and it didn't take right and sent your phone into a bootloop, with CWM on boot if that were to happen your phone would boot into CWM Recovery and at that point you could do a restore to get your phone back to it's previous state. And should you not flash anything for a while, you can go into the SuperUser app and allow the A2 Bootstrap permission and it would override CWM on boot, that way you wouldn't have to click "reboot system now" in CWM Recovery every time you reboot your phone.
Okay so this thread really died off already but...
Is it possible to temporarily disable the CWM on boot if it's already baked into the ROM? I am running SCv6 right now, and since there is no Bootstrapper app, there is no way I can simply enable it in SuperUser.
iarejohnsmith said:
Okay so this thread really died off already but...
Is it possible to temporarily disable the CWM on boot if it's already baked into the ROM? I am running SCv6 right now, and since there is no Bootstrapper app, there is no way I can simply enable it in SuperUser.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1385283, and download the "remove" zip. Reboot and install from sdcard...
Sent from my phone's mind
iarejohnsmith said:
Okay so this thread really died off already but...
Is it possible to temporarily disable the CWM on boot if it's already baked into the ROM? I am running SCv6 right now, and since there is no Bootstrapper app, there is no way I can simply enable it in SuperUser.
Click to expand...
Click to collapse
download the bootsrap app, hit the first button and allow. bam, disabled, block it with supeuser to get cwm on boot back
alteredlikeness said:
Go here: http://forum.xda-developers.com/showthread.php?t=1385283, and download the "remove" zip. Reboot and install from sdcard...
Click to expand...
Click to collapse
Yeah I read about this somewhere, but then I heard that it messes with overclock, so I never tried it.
lkrasner said:
download the bootsrap app, hit the first button and allow. bam, disabled, block it with supeuser to get cwm on boot back
Click to expand...
Click to collapse
So will downloading and installing the app again do something weird? Will that merge together with the CWM already there, so that they can both be disabled with one fell swoop?
iarejohnsmith said:
Yeah I read about this somewhere, but then I heard that it messes with overclock, so I never tried it.
So will downloading and installing the app again do something weird? Will that merge together with the CWM already there, so that they can both be disabled with one fell swoop?
Click to expand...
Click to collapse
installing the bootstrap will no hurt anything. just enable it in SU to disable it on boot (it just kind of takes over, but doesn't hurt anything.) Keep in mind it may take 2 reboots before the change kicks in either way. (1 to set up and the next you actually see it.)
I goofed up. :cyclops:
I was on a nice custom 2.3.6 ROM, and now I'm just on needles.
I was ...um, let's just say,.. barely conscious. So, anyhow I'm not 100% positive what I did -- but this is my best guess.
I am fairly sure I was fiddling with system settings (just looking around, no changes), and probably because of the apps I had installed, things became unstable.
What's strange now, is that I don't recall pausing on CWM recovery, which is VERY odd indeed, because I WAS really happy to have installed JW Daddy's CWM on every boot installed, and I've still got several full CWM backups that should work fine.
This much is 100% certain, after several failed attempts to stabilize (even long enough to uninstall the most recent apps), I decided to just restore a CWM backup. But I had forgotten that I had the CWM on every boot mod installed (because it wasn't working anymore, for some reason), and still didn't remember, even after I failed to find the Bootstrap app (which I had uninstalled, just after installing the CWM on every boot mod).
I must have just figured it was probably some ROM or backup of a ROM that I had put on that was clean I guess. Of course, on the next cycle up, it stayed up just long enough, so that I finally got the BootStrap installed again, but before I could hit the button to reboot into CWM, the phone crashed back down into a loop again, and this time, never came back up at all, not even for a second. Factory reset, & clearing Dalvik cache didn't help either.
The problem is that I didn't have a chance to reboot into CWM Recovery after installing the bootstrap and now that it won't boot at all, I'm just stuck looping without an easy way to get into CWM recovery. I am able to get into the useless stock recovery and/or fastboot, but I'm not sure what to do, now that I've got (I think) 2 additional goof-ball mods potentially in there --- one for the old faithful A2 Bootstrap, that is used to reboot into CWM recovery, and of course, the CWM on every boot mod, which was for whatever reason, broken by some other cause (possibly the apps I was fiddling with?) even before I 'worsened' things up.
I'd rather not go all the way back to stock 2.3.5 via RSD but I may have to? What say thee?
===================================================
SPECS PRIOR TO SCREW-UP:
AT&T Best Buy
Model Number: MB8656
Android version : 2.3.6
Display : SuperCharged_V_5_Update_2
Yeah, it sounds like a goof up to me.
You're probably going to have to FXZ the 2.3.5 and then upgrade to the 2.3.6 and use the FXZ fix to get your phone back to where it was. The problem that probably occurred was that you had both the bootstrap and the cwm on boot at the same time. You shouldn't use both of them, only 1 or the other.
If you read the posts, it tells you to un-allow the bootstrap app after installing the cwm on every boot. In fact, the roms that come with the cwm on boot on them don't even have the bootstrap app.
DusThis said:
If you read the posts, it tells you to un-allow the bootstrap app after installing the cwm on every boot. In fact, the roms that come with the cwm on boot on them don't even have the bootstrap app.
Click to expand...
Click to collapse
Oh well. I was hoping to at least only FXZ to 2.3.6 and maybe skip a step, since I was already there. ugh.
Thanks DusThis (hitting the Thanks Button now ;-)
Is there a single criteria that defines when we can FXZ back to 2.3.6 versus 2.3.5?
Yeah I would FXZ back to 2.3.5 and do the OTA, then restore your CWM backup using the bootstrap.
There is not currently a way to FXZ back to 2.3.6. Our 2.3.5 was something a very nice XDA member went and got off of a moto server for us. Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.
jimbridgman said:
Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.
Click to expand...
Click to collapse
<-- ahh, this makes sense now. There is more to an FXZ than just what comes OTA (I had forgotten that ;-)
Once you FXZ back to 2.3.5 you can just simply reroot, install A2 bootstrap and then perform a backup. I have done this several times and have never had any ill effects. Just make sure your backup is GOOD
To get rid of your errors now you must have to restore FXZ then update to 2.3.6 and restore CWM backup after that
To restore FXZ follow:
http://forum.xda-developers.com/showthread.php?t=1721218
jimbridgman said:
Yeah I would FXZ back to 2.3.5 and do the OTA, then restore your CWM backup using the bootstrap.
There is not currently a way to FXZ back to 2.3.6. Our 2.3.5 was something a very nice XDA member went and got off of a moto server for us. Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.
Click to expand...
Click to collapse
people seem to want it though. I will make it. I just have to pull all the images from the updated phone then write the XML with the same format right.
Sent from my MB865 using xda premium
lkrasner said:
people seem to want it though. I will make it. I just have to pull all the images from the updated phone then write the XML with the same format right.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yes, but getting the boot image will be a challenge, I think. Let me know if you run into an issue and I might be able to point you in the right direction.
The rest are east but, you HAVE to cat the device for each image, you can't dd it.
I would use the SAME xml file, just update the md5 sums.
The rest of the changes you already know.
I'm no expert at that kind of stuff by any means, but wouldn't it be easier to do if you FXZ your phone to 2.3.5 and then download the OTA. Don't install it right away and pull the update.zip and use that to make the 2.3.6 FXZ??
DusThis said:
I'm no expert at that kind of stuff by any means, but wouldn't it be easier to do if you FXZ your phone to 2.3.5 and then download the OTA. Don't install it right away and pull the update.zip and use that to make the 2.3.6 FXZ??
Click to expand...
Click to collapse
Nope, an ota is just basically linux patch files that are then applied to the apks and kernel and os files on your phone, it is not a whole new firmware that writes over the one on your phone.
Linux/UNIX patch:
http://en.m.wikipedia.org/wiki/Patch_(Unix)
Oh ok. That makes sense. I'm pretty much self teaching myself on this kind of stuff and I know that for instance the cheesecake stuff can be looked at and checked so I didn't know if an OTA update could be done the same way. Thanks for the link Jim.
DusThis said:
Oh ok. That makes sense. I'm pretty much self teaching myself on this kind of stuff and I know that for instance the cheesecake stuff can be looked at and checked so I didn't know if an OTA update could be done the same way. Thanks for the link Jim.
Click to expand...
Click to collapse
the cheesecake stuff and otas are the same thing. you can tell some stuff by looking inside the zips. for example they often contain a build.prop, which lets us see if it is ics, or what has changed.
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
DX2Trip said:
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
Click to expand...
Click to collapse
Hey, and sort of welcome back...
But I hate to be the bearer of bad, bad news... you have a softbrick, and there is NOTHING you can do.
Next time, read everything in an OP... LOL, look who I am telling this to....
The CM10 installs come with their own CWM built in, and flashing bootstrap is what bootlooped you, so after you get another warranty replacement (yes, you HAVE to do this), I would install leak #1 ONLY, then flash cm10 with bootstrap, then do not reinstall any boot hijacks or CWM "like" recovery (bootmenu), because all you have to do it hit the vol down button right as you see the blue led flash during the M dual core logo.
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
tcf38012 said:
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
Click to expand...
Click to collapse
he can't, he installed bootstrap while on cm10m, so he can't get to cwm anymore.
Scratch that ----- Deleted
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
DX2Trip said:
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
Click to expand...
Click to collapse
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
jimbridgman said:
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
Click to expand...
Click to collapse
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
lkrasner said:
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know, I was seeing in recovery how youbcan flash an update through sd AND system which has a lost and found folder and recovery folder. Dont know if this is of any info but either way because I wouldnt know how to put anything in system since I cant seem to get adb to recognize or moto-fastboot...I'm in a very confused state of mind and almost came to the point of hard brick but I refuse. I'll leave it up to ya devs. Thanks againg everyone.
Sent from my MB870 using xda premium
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
justdrew said:
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
First Softbrick it seems In Trouble
jimbridgman said:
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
Click to expand...
Click to collapse
Guys need your urgent help i am into a trouble what is it called technically may be a Soft brick but this is what has happened.
I was trying the Magic mod the installation went superb booted the phone it worked properly and then i used the bootstrap :silly: and tried starting the phone in recovery after which my phone is now stuck at magic mod boot animation. PLEASE HELP.
I am upto a point where have installed drivers latest rsd lite 6.0 ready with the extracted fxz 6.7.2_EDEM-18-SEARET_cfc.xml but phone is not showing up in rsd lite so that i can flash my phone. Phone says USB connected in AP Fastboot mode have a look at the attachment of my desktop. Please HELP guys....
Thanks & Regards,
Beginner Android (Ravi D)
havent you just posted this in the any question answered here thread and getting help there ??
Wow, almost forgot I made this thread lol. But sounds like your drivers need a good updating. Reboot PC after updating and try again is all I can say. Hope this helps.
Sent from my MB865 using xda premium
Ok so I have a rooted infuse 4G and am a complete noob when it comes to flashin roms and mods... I am still on the froyo 2.2.1and hate it lol. Which brings me to my first query, I know its possible to upgrade my android version to the GB and JB with multiple methods but I'm extremely scared that I'm going to brick my phone. It was some forums on here that helped me decide to root my phone so now I'm hoping that you guys can help me take the next step. So whats the safest, easiest way to upgrade my os.. Odin didnt work and I no longer have a computer, so heimdall is out as well. Oh not sure if this is important but I'm not registered on any network nor have I unlocked my phone's sim. Well that's a start. I really hate froyo 2.2.1 so please if anyone can help I definitely could use it.
treyserits said:
Ok so I have a rooted infuse 4G and am a complete noob when it comes to flashin roms and mods... I am still on the froyo 2.2.1and hate it lol. Which brings me to my first query, I know its possible to upgrade my android version to the GB and JB with multiple methods but I'm extremely scared that I'm going to brick my phone. It was some forums on here that helped me decide to root my phone so now I'm hoping that you guys can help me take the next step. So whats the safest, easiest way to upgrade my os.. Odin didnt work and I no longer have a computer, so heimdall is out as well. Oh not sure if this is important but I'm not registered on any network nor have I unlocked my phone's sim. Well that's a start. I really hate froyo 2.2.1 so please if anyone can help I definitely could use it.
Click to expand...
Click to collapse
From Froyo 2.2.1, there is an official build GB 2.3.6 UCLB3 out for the Infuse.
You will need a computer though. Without a computer to restore your phone to stock from soft bricking, you should not be flashing anything. It may be possible for you to bring your phone to an AT&T store and have them update you if you don't have a PC. You will need a computer to root the GB UCLB3.
Where to start? Read the Q/A as much as you can. Then move into the Development section.
http://forum.xda-developers.com/showthread.php?t=1437548 - read it all
thanks
qkster said:
From Froyo 2.2.1, there is an official build GB 2.3.6 UCLB3 out for the Infuse.
You will need a computer though. Without a computer to restore your phone to stock from soft bricking, you should not be flashing anything. It may be possible for you to bring your phone to an AT&T store and have them update you if you don't have a PC. You will need a computer to root the GB UCLB3.
Where to start? Read the Q/A as much as you can. Then move into the Development section.
http://forum.xda-developers.com/showthread.php?t=1437548 - read it all
Click to expand...
Click to collapse
Thanks qkster.. I really appreciate your help. I follow alot of your threads and am so hapoy thst there are infuse users that actually are willing to take the device to the next lvl. Now for another question.
Will it be easier to flash the jellybean 4.1.1 from the froyo or the gb? Or would it be possible to just flash a higher kernel? I'm not syre if that would help me or not, I really want to speed up my infuse and stop it from rebooting so much.
treyserits said:
Thanks qkster.. I really appreciate your help. I follow alot of your threads and am so hapoy thst there are infuse users that actually are willing to take the device to the next lvl. Now for another question.
Will it be easier to flash the jellybean 4.1.1 from the froyo or the gb? Or would it be possible to just flash a higher kernel? I'm not syre if that would help me or not, I really want to speed up my infuse and stop it from rebooting so much.
Click to expand...
Click to collapse
You cannot flash JB from Froyo and need to go to Gingerbread, then ICS then JB.
http://forum.xda-developers.com/showthread.php?t=1878458
Kies?
psal217050 said:
You cannot flash JB from Froyo and need to go to Gingerbread, then ICS then JB.
http://forum.xda-developers.com/showthread.php?t=1878458
Click to expand...
Click to collapse
Would it be best to use kies to update to GB? I'm a little concerned as to what would happen to my Infuse all around.. What will need backed up?
I have titanium backup but if the app gets wiped wont i lose all my back-ups? For some reason it wont sync to my dropbox app force closes every time I try. Sorry about all the questions I'm just short on the amount of time I am able to browse threads at the moment but I do have use of a computer for awhile so that kinda helps.
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Ok well here goes nothing.
andros11 said:
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Well I'm going to install and give it a try with Heimdall. I'll let you know how it goes. Thanks everyone for all your help. I'm sure I'll have more questions before long. XD
andros11 said:
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Will this even work if i'm not registered to a network with the phone still locked? And I see that it will also unroot my phone which isnt a problem I'm just curious whether or not I can still root with super one click or if i need a different root tool?
treyserits said:
Will this even work if i'm not registered to a network with the phone still locked? And I see that it will also unroot my phone which isnt a problem I'm just curious whether or not I can still root with super one click or if i need a different root tool?
Click to expand...
Click to collapse
It doesn't matter if your phone is unregistered and locked. You cannot use SuperOneClick on Gingerbread. What you should do is (this is the Heimdall version):
Flash this rooted version of stock GB:
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
You do that and you already have root.
If you want to then graduate on to Jelly Bean you must:
Flash ICS (follow directions carefully!):
http://forum.xda-developers.com/showpost.php?p=24901014&postcount=1
Once you've done that, flash any of the JB ROMs you like, but make sure to read the directions carefully. I strongly recommend that you consult the Super Everything Thread for links to the ROMs and tweaks you need, particularly if you are interested in unlocking your phone.
http://forum.xda-developers.com/showthread.php?t=1610374
I'm feeling kinda stupid..
Can somebody give me the right link for downloading Heimdall One-click w/root? For some reason I'm not able to get any to work on this computer.. I downloaded the ink provided labeled UCLB3 -DEBLOATED-ODEX - ROOTED - BUSYBOX- STOCK KERNEL on
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
but am unsure if that actually is the one containing Heimdall or just the rom i'm flashing or both.. I'm extremely sorry about my noobishness of just posting all these already answered questions. I've gone and confused myself and have like ten tabs with different threads open please don't hate me. I have a bad habit of asking questions..
Oh and what apps do i need on my phone in order to flash? And I mean absolutely need. I've also noticed that most threads say to format my mounted sd card But i really dont want to do that if i dont need to.
It should all be bundled together. Heimdall is a java based interface so it should just open up. Sorry, it's been a long time and I'm an Odin person!
You don't need any apps on your phone. When you flash, everything on the small partition will be wiped (apps, app data, etc). Flashing will not usually wipe your pictures, videos etc. but it's always a good idea to back up. For now, don't worry about formatting anything. When you get to ICS, you'll need to format as it says in the instructions. Otherwise, if it works, don't fix it!
When you flash ICS and JB, all you need to do is to put the zip files on to your internal SD card (not the one you can take out). You can then flash from CWM (which will already be on your phone - don't download Rom Manager).
Once again thank you all. I'm running GB and loving it. My fiance is shocked at how much help I needed though usually I'm the person everyone comes to with their tech issues LOL. But I absolutely did not want to mess my infuse up. I thought I did but the issue was such a noob mistake that I had to smack myself in the face at my stupidity. Forgot to unzip the cwm ect folder I downloaded. XD not sure I'm ready to try ICS or JB yet though.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
The odd thing is you could have updated to GB through AT&T and used mini kies. But at least you are now rooted and able to go to ICS and JB.
Read the instructions on the next step before moving on.
Sent from my SGH-I997 using xda premium
Kinda wish I would have done it that way... I wanted to get some practice flashing roms tho. And now my phone is bootlooping, computer says the device is incompatible I can only get into the samsung recovery even tho the rom i flashed had cwm packaged in. I tried to change my boot animation following the steps provided in my boot animation thread then again with the steps in tsqers rom thread I apologise if thats mispelled. I tried updating from sd but get a sign error Can get into download mode but same issue with it being incompatible usb device. I tried holding down the power button for 1 minute and then rebooting no luck there. I tried wiping data/fact. reset,... nothing. I tried wipe cache partition,...still looping.
The loop samsung screen two seconds, black screen 1 1/2 seconds,... over and over and over...
My battery is full. Any advice???
treyserits said:
Kinda wish I would have done it that way... I wanted to get some practice flashing roms tho. And now my phone is bootlooping, computer says the device is incompatible I can only get into the samsung recovery even tho the rom i flashed had cwm packaged in. I tried to change my boot animation following the steps provided in my boot animation thread then again with the steps in tsqers rom thread I apologise if thats mispelled. I tried updating from sd but get a sign error Can get into download mode but same issue with it being incompatible usb device. I tried holding down the power button for 1 minute and then rebooting no luck there. I tried wiping data/fact. reset,... nothing. I tried wipe cache partition,...still looping.
The loop samsung screen two seconds, black screen 1 1/2 seconds,... over and over and over...
My battery is full. Any advice???
Click to expand...
Click to collapse
Which ROM did you flash and which CWM recovery can you see (which version)?
I used the http://forum.xda-developers.com/show...43&postcount=2 thread to get the rooted rom UCLB3 -DEBLOATED-ODEX - ROOTED - BUSYBOX- STOCK KERNEL.
Saved I think.
So I finally Got it to connect to my comp and re-flashed the rom can i get a link to an ICS heimdall one click package to flash before restoring anything and this happening again?
You should be able to find it on the ISET page.
http://forum.xda-developers.com/showthread.php?p=32876425
Sent from my SGH-I997 using xda premium
This is the bootstrap recovery for atrix 2 based on clockworkmod recovery 6 [CWM 6] to be used with MIUI v5
Steps to use bootstrap cwm6:
1. Install the Atrix2Bootstrap.apk in the rooted leaked jellybean #3
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions. Give access to it
4. Select "Reboot Recovery"
5. Then flash latest MIUI v5
6. With this recovery ie CWM6, Direct OTA update will work, the phone will flash the OTA and automatically reboot. Earlier Bootstrap based on CWM5 threw an error if we tried to auto update from system updates. This is the recommended recovery to be used with MIUI v5. Now you wont get any error messages while OTA update.
If you find the post useful...plz hit thanks.
arnab said:
This is the bootstrap recovery for atrix 2 based on clockworkmod recovery 6 [CWM 6]
Steps to use bootstrap cwm6:
1. Install the Atrix2Bootstrap.apk in a rooted stock rom
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions. Give access to it
4. Select "Reboot Recovery"
If you find the post useful...plz hit thanks.
Click to expand...
Click to collapse
Is this useful since 98-99% of our latest ROM's are based on BMM? No disrespect just stating the facts. I'd personally like to try it out since Multi-booting is not my thing really anymore... Nice find either way. Thanks for the share. I'll give a thanks when I try it out
Sent from my MB865 using XDA Premium 4 mobile app
A2Trip said:
Is this useful since 98-99% of our latest ROM's are based on BMM? No disrespect just stating the facts. I'd personally like to try it out since Multi-booting is not my thing really anymore... Nice find either way. Thanks for the share. I'll give a thanks when I try it out
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm wondering the same thing since I don't care much about multi-booting. My guess would be that you would have to flash the ROM first, then uninstall BMM, then install this but don't take my word for it yet. I'm going to play around with it once I get home and charge up my A2.
@arnab, thanks for this.:thumbup:
If I had a dollar for every time I said that, I'd be making money in a very weird way.
It works perfectly...U don't have to worry a thing...Personally I like non kexec based custom ROMs...But be sure to remove BMM before installing it.
Are we able to cwm at boot?
No
atrix2man said:
Are we able to cwm at boot?
Click to expand...
Click to collapse
Good point out that IS one thing I like with BMM. Forgot CWM doesn't really work that way without an extra mod probably.
Sent from my MB865 using XDA Premium 4 mobile app
Wish we could boot kexec with this
seems like alot of extra work required to get a recovery that you cant boot directly into, and that no still worked on ROM actually support this anymore.
So from a BMM ROM, must remove BMM recovery by using the BMM application, then remove the app, then install this and then use it to install the recovery that we cant get into at boot.
Is that correct?
Not purposely coming off as an ass, can just see alot of problems coming from it.
You will not be able to boot any kexec/2nd init based roms using this.. @OP, I recommend you to take a look at the cmdefy recovery in altered's github or wang's.. If you want to get them working..
In short your recovery must start on every boot (look into Cwm on every boot) and then run a script that loads kexec or 2nd init..
Sent from my MB865 using Tapatalk 2
Yea i checked it out and will only use this if i want to stay on ics. Pretty kool tho! :good:
I am not sure of how relevant this is but out of my personal experience, if you have already installed BMM make sure to search for the logwrapper.bin file being altered (or was it deleted, don't recall) issue in the forum before uninstalling BMM, else it may cause you grief.
EDIT
Just looked it up, the issue was :
Quote
DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.
I want to thank all those who replied. As you all gave me a clear & concise understanding of the issue being discussed. And I will be staying with BMM for all the reasons that were very easy to understand.
RAD7 said:
I am not sure of how relevant this is but out of my personal experience, if you have already installed BMM make sure to search for the logwrapper.bin file being altered (or was it deleted, don't recall) issue in the forum before uninstalling BMM, else it may cause you grief.
EDIT
Just looked it up, the issue was :
Quote
DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.
Click to expand...
Click to collapse
If I am not mistaken you can uninstall BMM from within the app itself and it will automatically clean all of that up for you. It's been a while since I've had the time to experiment with my A2, but I'm almost positive of that at least.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
1BadWolf said:
If I am not mistaken you can uninstall BMM from within the app itself and it will automatically clean all of that up for you. It's been a while since I've had the time to experiment with my A2, but I'm almost positive of that at least.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
Yeah you are right in what you have stated but what I wanted the guys to be wary was installing BMM after previously having installed and uninstalled A2 bootstrap in which case the logwrapper.bin issue crops up causing boot loop and battery cannot be charged until fresh fxz via rsd is done. Even I have not been experimenting for long but strongly contemplating getting aboard jbx :fingers-crossed:
I updated the thread. Its made for MIUI v5 enthusiasts (santajin)
arnab said:
I updated the thread. Its made for MIUI v5 enthusiasts (santajin)
Click to expand...
Click to collapse
with this recovery you can apply any OTA update of the miui rom?
Yup...earlier it used to crash giving sm sd card error...nw it will work like a charm...actually this is the official recovery for santajin's miui v5 at miui.com
guys atleast press the thanx button
MIUI is not for ATT .... right ?? :silly: :silly: