Database Info

[Q] Can't update ClockworkMod for Mesmerize

I have a samsung mesmerize and i jsut updated it into froyo, im new to doing this kind of stuff and I haev tried to update Clockworkmod using ODIN. But everytime i do it and start my phone up again i'm stuck in airplane mode and cant get out of it. Is there another step i'm supposed to do after using ODIN that i'm missing? Any help would be greatly appreciated.

Blier2488 said:
I have a samsung mesmerize and i jsut updated it into froyo, im new to doing this kind of stuff and I haev tried to update Clockworkmod using ODIN. But everytime i do it and start my phone up again i'm stuck in airplane mode and cant get out of it. Is there another step i'm supposed to do after using ODIN that i'm missing? Any help would be greatly appreciated.
Click to expand...
Click to collapse
never heard of odin (im still kinda new), but have you tried rom manager from the market? thats how i updated my clockwork recovery to 3.0.0.7, the newest one. it upgrades clockworkrecovery, flashes roms, and backups roms, and theres a paid and free version (with ads). thats what i used. tell me if this works.

CODISDABOMB said:
never heard of odin (im still kinda new), but have you tried rom manager from the market? thats how i updated my clockwork recovery to 3.0.0.7, the newest one. it upgrades clockworkrecovery, flashes roms, and backups roms, and theres a paid and free version (with ads). thats what i used. tell me if this works.
Click to expand...
Click to collapse
Yes i have rom manager but still not 100% on how it works. Would i save the update i downloaded to my sdcard and then use rom manager to open it and update clockworkrecovery?

Blier2488 said:
Yes i have rom manager but still not 100% on how it works. Would i save the update i downloaded to my sdcard and then use rom manager to open it and update clockworkrecovery?
Click to expand...
Click to collapse
to fix anything clockwork scroll to the very bottom of the app, then click flash alternate recovery. Then when its done then click all clockworkmod recoveries right below it, then select 3.0.0.5, and that should fix most/all problems with clockwork anyone has, and give you the newest update. and to get to recovery easier just use mikfroyo v4.4 like i am. when you hold the power button just click options under power off, and click recovery, and it'll open clockworkmod.
note: i did this while i wrote it to double check it still works after i updated it.
and this is all done on my htc evo.

ROM Manager

ROM Manager has an option to "Backup Current ROM" and "Manage and Restore Backups". Can all that be used on stock (odexed), rooted ROM?
The End.

I noticed this feature as well. I personally never tried but i am not sure how it would work. It might create a file in the the clockwork mod folder. But i doubt it works. You could always try it out. the worst it could do it bootloop your phone and you can just fxz? haha.

I don't have a method yet for flashing a fxz file. I'm on linux. Ive never been forced to learn how to do it. You try. ;-)
The End.

Haha. That is a great challenge. My phone is charging right now. We need to find another "victim" to do it. I don't think ROM toolbox is very reliable though. Or at least not as reliable as CWM

I use this app to backup and restore apps.
Don't know for sure to backup and restore rom.
Need someone who has warranty to try this though LOL
Sent from my MB865 using Tapatalk 2

kindacrazyazn said:
Haha. That is a great challenge. My phone is charging right now. We need to find another "victim" to do it. I don't think ROM toolbox is very reliable though. Or at least not as reliable as CWM
Click to expand...
Click to collapse
We're talking about ROM Manager by Koushik Dutta. Not "ROM Toolbox". Right?
The End.

As far as backing up and restoring a stock rom, I fairly certain that it will. However, it depends on a CWM mod recovery and at the moment all we have is a frankinmod recovery and Rom Manager doesn't even acknowledge it.
So, if we had CWM in better shape, or a way for Rom Manager to see it, then everything else would fall into place.
On a random note, Rom Manager will boot into recovery with our frankinmod, but that's about it.

@41rw4lk
These are exactly the concerns i have.
The End.

I was referring to ROM Toolbox but i personally never trusted ROM Toolbox or ROM manager. But that is just me personally.

ROM Manager makes things a whole lot easier for flashing ROMs and backing up/restoring. It's developed by koushikdutta, the same person that develops CWM, so everything should be seamlessly integrated. But as 41rw4lk stated, ROM Manager only partially detects our modified, bootstrapped recovery (it can boot into it but no automation). However, you can get it to work on the A2 . Apply the A2 bootstrap, then flash the Bionic recovery from ROM Manager, then re-apply the A2 bootstrap.
---------- Post added at 12:26 AM ---------- Previous post was at 12:24 AM ----------
kindacrazyazn said:
I was referring to ROM Toolbox but i personally never trusted ROM Toolbox or ROM manager. But that is just me personally.
Click to expand...
Click to collapse
Using ROM Toolbox for flashing/restoring/backing up/etc only works if you have the premium ROM Manager. It uses methods from the premium ROM Manager to do just what ROM Manager does. So ROM Toolbox works although there isn't really a reason to use it.

I did away with the bootstrapper and use the cwm on every boot method, which is built into the Sonya rom now I believe. Can I flash the Bionic recovery still without messing everything up?

41rw4lk said:
I did away with the bootstrapper and use the cwm on every boot method, which is built into the Sonya rom now I believe. Can I flash the Bionic recovery still without messing everything up?
Click to expand...
Click to collapse
yes it will work finr as i have done so. Also, the options in rom manager that alow you to backup or restore a rom do work as i have used both mutiple times with out a problem. I just flashed the new lithium rom today right after i backed up my atrix sonya rom using the backup option.

@cogeary
Is there a method to remove the Bionic Recovery? When the Atrix 2 Recovery becomes available would we install that over the Bionic?
The End.

rob219 said:
yes it will work finr as i have done so. Also, the options in rom manager that alow you to backup or restore a rom do work as i have used both mutiple times with out a problem. I just flashed the new lithium rom today right after i backed up my atrix sonya rom using the backup option.
Click to expand...
Click to collapse
I just flashed the Bionic recovery and it works perfectly with Rom Manager. One click backup. Thanks for the tip.

KEB64 said:
@cogeary
Is there a method to remove the Bionic Recovery? When the Atrix 2 Recovery becomes available would we install that over the Bionic?
The End.
Click to expand...
Click to collapse
im not sure about removing it from out phone, but i do know if we ever get an officail or unofficial recovery made just for the atrix 2 you would just either flash it using rom manager (if its in the list of devices) or flash the zip in recovery and reboot into your rom or reboot recovery to check it out.

Technically, the recoveries we're flashing now aren't replacing the system recovery, they're just put in the system and loaded like any other script. If you try to get to recovery manually with buttons, you hit the default system recovery. If we ever get an unlocked bootloader and an official CWM then we're golden and can overwrite the system recovery. So uninstalling everything else should be a matter of deleting scripts, or just not build them into roms anymore since we won't need to.
It's late, so if I'm talking out my ass I apologize. I will say, I appreciate all the work and help from everyone here.

Alright guys I'm stuck :( (soft brick? ) please help

I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?

j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709

psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium

volume up/home/power button is recovery try that
and you used rom manger to flash rom?

j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.

PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.

not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.

If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?

j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.

j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.

[Q] First Time Root Help Please?

Hello everyone,
I just bought a Verizon Galaxy S3 and I am in the process of rooting it. Im kinda freaking out because things really arent going that well for me. So far what I've done is root and unlock bootloader. Here is where the problem starts. When I try to reboot into CWM recovery it just boots me into the normal android recovery. Is this normal? every video I have watched shows people manually rebooting straight into CWM. The only way I can get it to work is if I go into EZ recovery and press "Flash" then "Reboot Into Recovery" buttons.
My second area of confusion is regarding the IMEI backup. Is this something everyone does when flashing roms on this phone? I am very confused as to what I'm supposed to do. Do I use the adb or download a terminal app from the play store? If someone could clarify that would be great !
Sorry if these questions are pathetic but this is my first time doing this and it's a learning experience I geuss. Here are the links to the guides I used for what I have done so far.
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1852255
Thanks

I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.

apacseven said:
I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.
Click to expand...
Click to collapse
Alright thanks, so for most people once they flash it once it should stay every time they reboot into recovery? I have probably the noobiest question of all time, what does flashing CWM recovery even do? is it like flashing a rom where it just gets baked in to the OS permanently? Or does it actually provide a backup of data because I thought thats what nandroids were for.

Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.

apacseven said:
Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.
Click to expand...
Click to collapse
Yes you did, thank you so much. In the tutorial I used it was saying that the newer versions of EZ unlock were having problems so I downloaded version 1.2. How do I proceed if my bootloader was unlocked improperly? Also, I went in to EZ recovery and flashed CWM and made a nandroid backup if this matters.
Thanks so much for your help.

If you used version 1.2 then my point was moot. So you can only get into CWM if you install CWM from ez recovery and then hit reboot into recovery? If you do the hold vol up + home button while powering on it always takes you to stock recovery?

Yep its very weird. Not sure what to do.

Someone else will likely be able to chime in on how to correct this, unfortunately (or fortunately? lol) it hasnt happened to me so I havent had to deal with it. Its not a huge deal so I wouldnt worry about it.
Personally I use TWRP recovery. You can try that and see if it will stick, you can always go back to CWM later. Try it in ez recovery, or Goo manager from the play store (I use goo manager). If you want to try installing it from goo manager, install the app, hit menu, then select install open recovery script.

K cool. So would it hurt me if I just used ez recovery to flash and reboot everytime I need to get into CWM? Also for goo manager does that install the one you were talking about or CWM?
Sent from my SCH-I535 using xda app-developers app

Goo manager is only for TWRP recovery. And as long as the backups are being stored and you can access them the next time you get into CWM, it doesnt matter. Like I said, hopefully someone will be able to tell you how to correct this issue and we will both learn a thing or two from it.

Did you follow Step 12 in Section 2 in the first link you posted?
You have to make sure to go to CWM v6.0.1 in the drop down and install that version of Clockwork Mod Recovery.
I'm not sure if that's the cause of your issue, but you may want to check into that

Yep i did that
Sent from my SCH-I535 using xda app-developers app

Can someone please help D:
Sent from my SCH-I535 using xda app-developers app

[Q] Confused as to what to do next: un-bricked, but recovery is still a garbled mess

So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.

It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.

Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk

I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker

One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium

UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it

MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app

UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info

MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.

UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us