Database Info

[Q] a little help

ive been rooted for a long time now, i have a Moto Attrix 2. recently i did the updated to the 2.3.6 but before i did, i went ahead and did the perminent root method. this helped me keep root. now i want to jump into Roms. i'm not new to this. i had a Droid X proir to the Attrix. so i kinda know my way around. sorta..aha, ive read the process of the rom i want to install on to my phone which is supercharge Rom

So do you have a question, I couldn't tell from your post

awe man, i'm sorry about that.
my question...actually the question is about the process needed to be taken. i read thru the steps to flash supercharge rom V5 but, i have no clue to where start from since i have not flash a rom on this device.? so i'm startin off from scretch i'm sorry about that, i shoulda proof read that..lol, before i posted.

Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.

eL_MeXiCaNo said:
Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.
Click to expand...
Click to collapse
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.

Droid_Boi86 said:
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.
Click to expand...
Click to collapse
Dont worry about ever doing the forever root there's a root method for 2.3.6
Before flashing any rom I suggest you flash the 2.3.5 FXZ and update to 2.3.6 and then root it. This way you start from a fresh base and don't have any random bugs that would take a long time to hunt down and fix due to coming from a non-stock rom.

Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.

rob219 said:
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.
Click to expand...
Click to collapse
Because if you dont deny bootstrap SU after FLASHING CWM ON STARTUP zip then you will not get CWM everytime you boot up, it's a bug. So if you want CWM everytime you boot your phone you have to deny bootstrap SU. Other than that IDK the exact technical details on why it does this, it just does.

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.

Droid_Boi86 said:
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.
Click to expand...
Click to collapse
Sorry KEB - not to step on your toes or anything, but...
Get and install the A2 Bootstrap from here.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!

alteredlikeness said:
Sorry KEB - not to step on your toes or anything, but...
Get the A2 Bootstrap from here.
Get ROM Manager from the Google Play Store.
Install both.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!
Click to expand...
Click to collapse
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/

Droid_Boi86 said:
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/
Click to expand...
Click to collapse
Make sure you have the drivers downloaded for the Atrix 2.

thethird84 said:
Make sure you have the drivers downloaded for the Atrix 2.
Click to expand...
Click to collapse
By "seeing your phone," do you mean ADB-wise? Settings -> Applications -> Development -> USB Debugging (enable)

PM me if you need any help. I have Supercharged V5 update 2 running and I love it. there are some things you need to do to make sure it works right though.

thanks alot! i will do..

[RECOVERY] TWRP 2.1.1 for Motorola Milestone 2

I have ported this recovery from Motorola Defy.
Big thanks to Epsylon3 and TWRP team.
WARNING: Use it at your own risk !!!
It has been tested on my MIUI v4 (ICS) ROM.
BUGs:
- restoring system from nandroid doesn't work
- not working with GB ROMS
Download
Only recovery.
Recovery and ICS bootmenu.
You can use Only recovery package if you don't have ICS ROM installed.
This recovery only replaces recovery in bootmenu.

Anyone tested the bootmenu version with CM9?

It should be working, because I have used bootmenu in MIUI v4 from CM9.
You can also flash only recovery package. It won't delete your bootmenu, it will only replace recovery. Only recovery package won't work, if you don't have bootmenu already.
With bootmenu package replace the whole bootmenu also with recovery.

doubt: why change to this recovery?

Look into Defy thread about it or on the official site: www.teamw.in/project/twrp2

---UFO--- said:
Look into Defy thread about it or on the official site: www.teamw.in/project/twrp2
Click to expand...
Click to collapse
yeah, now I can see the reason...
but I think you should explain how to install it. Can we install via CWM (?), before or later install the ICS ROM (?), can we install it with a GB ROM (?), etc

I installed the recovery only version as i already have bootmenu and i dont have ics. It says it is conpleted and i just need to reboot recovery but i dont see the option from my recovery menu so i just rebooted the phone. I reentered recovery but i still have the same recovery. Choosing latest, stable or stock does not show me the twrp recovery. I then tried to install again but the same thing happens no twrp. Did i miss something?

lucasdeeiroz said:
yeah, now I can see the reason...
but I think you should explain how to install it. Can we install via CWM (?), before or later install the ICS ROM (?), can we install it with a GB ROM (?), etc
Click to expand...
Click to collapse
Yeah, will both the recovery and bootmenu work with GB ROMS? I'd like it on will5's MIUI 2.5.25 GB 2.3.7. Thanks in advance!

evilmtv said:
Yeah, will both the recovery and bootmenu work with GB ROMS? I'd like it on will5's MIUI 2.5.25 GB 2.3.7. Thanks in advance!
Click to expand...
Click to collapse
I have only tried it with ICS. When I will have some spare time, I will try it with GB roms.

I agree that some more detailed description and "how-to" guide would be useful.
To be honest, I'm not sure what exactly is better on TWRP recovery and why would I prefer it over CWM (what's its functions?), what can it do? How it looks (some screens would be nice)?
How to install it?
I appreciate all your work, so don't take it as (rude) criticism, but as an idea for an improvement of this topic
I bet, it would be way more interesting and more people would use it, if there will be informations, I mentioned above.

Anonymous_ said:
I agree that some more detailed description and "how-to" guide would be useful.
To be honest, I'm not sure what exactly is better on TWRP recovery and why would I prefer it over CWM (what's its functions?), what can it do? How it looks (some screens would be nice)?
How to install it?
I appreciate all your work, so don't take it as (rude) criticism, but as an idea for an improvement of this topic
I bet, it would be way more interesting and more people would use it, if there will be informations, I mentioned above.
Click to expand...
Click to collapse
Since it doesn't have specified the requirements I pushed the files with right permissions over bootmenu 0.8.6(yes old, but i didn't know about requirements), so adding missing files, patching one script I got it running, touch UI, everything nice, but but but, I fixed the backup, backed up system, then tried to restore and oh surprise, rm -rf /system and then nothing happened. The result? the recovery deleted the whole system folder. so, my progress is on a .tar nandroid that i can't restore(the usual way)...So be CAREFUL.

Sorry about that, I have tested it only with MIUIv4 (ICS) with lastest bootmenu from CM9.
I have never try to restore system from nandroid, I'm always using update.zip for restoring system.
Thanks for your feedback.

Hello,
Does anyone experienced problems to mount sdcard ?
Kind reagrds,

Help with Kexec for SGS3

To whoever can help me -- I'm trying to use kexec to install CM10 on my SGS3, but i've been hearing that when you hard-reboot your phone, AKA battery pull/death, or using the power button, you go right back to the recovery. This isn't a problem, as long as I don't have to re-flash CM10 every time I boot, or I have no choice but to go to the stock ROM. I'd like to be able to either boot to the CM10 or go to my currently flashed version of CM10 from the recovery.
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!

Bumping... could really use help here.

Just reboot from recovery and it will bootloop a couple times then boot up.

DonSagiv said:
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Click to expand...
Click to collapse
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.

lazarus2405 said:
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
Click to expand...
Click to collapse
In which cases would someone lose kexec and need to reinstall it?

Zalithian said:
In which cases would someone lose kexec and need to reinstall it?
Click to expand...
Click to collapse
When u flash back to stock.

droidstyle said:
When u flash back to stock.
Click to expand...
Click to collapse
Or any rom.

jaymattt said:
Or any rom.
Click to expand...
Click to collapse
not necessarily...if your flashing a custom rom/kernel like beans custom stock, cm10, paranoidandroid, aokp, or imosyeons Touchwiz leankernel, kexec is always there...kexec is built into the kernel, cwm 6.0.1 is compatible with kexec.

Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app

Vorfidus said:
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...

droidstyle said:
Just reboot from recovery and it will bootloop a couple times then boot up.
Click to expand...
Click to collapse
Thanks! CM10 works beautifully on here.

droidstyle said:
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
Click to expand...
Click to collapse
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link. There is also a kexec twrp 2.2 recovery but it didn't work for me.

piiman said:
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link.
Click to expand...
Click to collapse
yea i know, thats what I used in reference to my previous post.

droidstyle said:
yea i know, thats what I used in reference to my previous post.
Click to expand...
Click to collapse
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514

Triskite said:
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Click to expand...
Click to collapse
let this thread die....there is no need to use anything kexec. stick to cwm 6.0.1.0 or 6.0.1.2

Unlocked, now can't install kexec roms?

I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\

confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems

Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.

lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?

confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?

PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)

confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.

lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?

confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.

confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.

droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?

PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.

newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.

If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question

synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?

[Q] Can I use BMM after Bootstrap?

Now I am currently running on Leak 2 with Bootstrap, but I want to FXZ Leak 3 and then install BMM so I can also install Mokee. Is there any risk of bricking my device if I install BMM after Bootstrap even if i FXZ inbetween ?

Kraix said:
Now I am currently running on Leak 2 with Bootstrap, but I want to FXZ Leak 3 and then install BMM so I can also install Mokee. Is there any risk of bricking my device if I install BMM after Bootstrap even if i FXZ inbetween ?
Click to expand...
Click to collapse
This question has been answered multiple times so it is completely unnecessary to start a whole new thread to ask it yet again. Also, questions belong in q&a.
Brought to you by time and relative dimensions in space.