Database Info

Am I the only one....

Who has not got the update yet? I ran a backup and SBF'd as soon as I saw the update was being pushed and now I feel like the fat kid on the playground who always gets picked last.

Brenardo said:
Who has not got the update yet? I ran a backup and SBF'd as soon as I saw the update was being pushed and now I feel like the fat kid on the playground who always gets picked last.
Click to expand...
Click to collapse
hi there, this is out of the update question
can u tell me how can i backup the whole android (stock) system?
thanks alot ^^""

Rom manager. Flash Clockwork recovery then boot into recovery. Use volume buttons to select backup and restore choose backup and let CwR do its work.

Brenardo said:
Rom manager. Flash Clockwork recovery then boot into recovery. Use volume buttons to select backup and restore choose backup and let CwR do its work.
Click to expand...
Click to collapse
hi there, thanks for the reply,
do u mean i have to download the Rom Manager, install it, and then go into CWM?

Me either
I have NOT received anything for an update. 100% stock, never rooted or unlocked wi-fi only........

I haven't received it yet either, I"m on stock, rooted, but still, trying to manually update now, having some issues though.
And for the wifi xoom I'm pretty sure they said it would be a few weeks before that was pushed out however they plan on doing that.
There's instructions to do that manually too though if needed on here.

[Q] Attempted to root my i727r

Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.

Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613

Me[kk]A said:
Have a rogers S2LTE, running ICS 4.04.
I ran Odin and used cwm recovery, and used what I found to be the most recent TAR file for the i727r.
during the download procedure to put superuzer on the phone, I had one error aborted installation, but success the second time.
Everything seemed normal, albeit aside from a slightly slower speed in the operation of the phone.
The only reason I noticed something was wrong was the fact that superuzer didnt really do anything, I couldnt add any apps or get past the initial screen.
Also, titanium back up didnt work, stating it couldn't get root permissions.
At this point, I installed root checker and got a negative response on my phone being rooted.
I'm posting here as I'm not sure how to progress, and as the phone is running normally, and im not sure if any real damage is done.
Do I simply try to flash the phone with Odin once more? Or do I flash it back to stock, and factory reset, and then try to root again?
Thanks in advance.
Click to expand...
Click to collapse
download procedure?
just put superuser on sd and install from cwm.
no root access means no su binary's installed. su binary's will not install from the superuser in the market that's just a front end.

wouldn't you also require busy box and then fix permissions using rom manager?

SeraldoBabalu said:
wouldn't you also require busy box and then fix permissions using rom manager?
Click to expand...
Click to collapse
no. busy box has nothing to do with su. and rom manager sucks and you will have nothing but trouble if you use it. just download odin and cwm and superuser thats all you need to root that expensive phone.

Try the super user file located here: http://forum.xda-developers.com/showthread.php?t=1565126
I had a similar issue as you and the su in the link worked fine. If it fails keep trying, took me like 3 tries.
Sent from my SAMSUNG-SGH-I727 using xda premium

vincom said:
which cwm did u use
wich su file did u use
read this on rooting http://forum.xda-developers.com/showthread.php?t=1340526
but use this cwm http://forum.xda-developers.com/showthread.php?t=1566613
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/showthread.php?t=1340526
but used the newest tar file provided on one of the rogers ics rooting threads.
As nothing is visibly wrong at this point, could I simply retry to root? Or should I wipe everything first?

So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?

Me[kk]A said:
So i tried to reflash again and use the new hercules file in odin.
All went well until I went into cwm recovery to make a back up, it said the it couldn't mount and aborted.
I backed up onto the SD card and it proceeded, however, when trying to load the superuser file from the external sd, it also said it couldn't mount, and aborted there.
any way around this?
Click to expand...
Click to collapse
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).

popcorn900 said:
dont use a touch recovery, flash a non touch recovery then install superuser. or put the superuser zip on the emm(internal sd).
Click to expand...
Click to collapse
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig

vincom said:
use this touch from tpmullan http://forum.xda-developers.com/showthread.php?t=1566613
u used this one from sk8erwitskil, u have to mount the sdcard first, but he has fixed it now(in testing) http://forum.xda-developers.com/showthread.php?t=1472954&highlight=sk8erwitskils
dont read my sig
Click to expand...
Click to collapse
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.

Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
weird, which method did u use to flash cwm
where is backup located, int or ext sdcard, which cwm version did u make backup
what do u mean it wouldnt read superuser, maybe redownload su and check the md5, running su in cwm has to b done a few times until it states that it has completed sucessfully
edit:try to mount sdcard from within cwm in "mounts and storage/mount sdcard" also mount emmc, i never had to do that but it might b that u have to do it once

Me[kk]A said:
That's the one I used, the one from tpmullan. Couldn't mount a back up, and wouldn't read superuser either.
Click to expand...
Click to collapse
well if you would just try a non touch recovery you might be surprised.
http://forum.xda-developers.com/showthread.php?t=1725221
this recovery works and this is all the help i can muster up. so now if you cant figure it out then i guess you shouldn't be flashing phones.

I have the same phone this is what I did
Flash phone with CWM use this one
Clockworkmod Touch 5.8.1.3 Odin tar http://forum.xda-developers.com/show....php?t=1566613
Then wipe data/factory reset, format- system, data and cache, and clear the partition and dalvik caches, do that to all of them 3 times each, using touch cwm.
Then odin ICS download it from here http://www.sammobile.com/firmware/
(make sure only Auto Reboot is checked nothing else)
Once the phone loads go through the setup then leave it alone, let it sit for about 20min then flash back the CWM. Then download Superuser from here and put it on the root of your SD card then flash it in CWM if it fails just keep doing it until it works, it worked the second time for me.
Once superuser is installed install busybox from the market and everything will work.
This method worked perfect for me I was having the same problem like you. The key is to wait about 20min after you flashed ICS before you do anything else.
Hope this helps you.

Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.

Me[kk]A said:
Well, the final superuser file worked, everything backed up perfectly.
Wanted to thank you all for you assistance. Vincom, if I knew who you were in Bolton, id buy you a beer, as I'm in your town 3 times a week.
lol Cheers everyone.
Click to expand...
Click to collapse
cool, what was the solution? bad download

vincom said:
cool, what was the solution? bad download
Click to expand...
Click to collapse
I'm not entirely sure. After not being able to back up, I grabbed an external sd, put superuser on that.
The back up went through with no problems. Also, superuser installed on the 2nd try and all went well with permissions from there.
Friend of mine had picked a zip file labelled "root" to use with Odin, and I'm suspecting the tar files I had attempted with in the past weren't correct and this file was.
Either way, I have lots more reading to do to fully understand what is available to me now. Busybox, nandroid, ROM toolbox installed.

iv flashed my phone so many times that flashing stock and rooting seem tedious to me. glad you got it rooted, now make a nand backup so you don't have to do it again.
my 32 gig sd is filled with nand dumps lol i don't even have a game on it to play.

[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

CWM Can't see my backup

I fragged up Android by applying an update, so I can't boot into Android.
I can get into CWM, but it doesn't see my backup... The backup is in /clockwordmod/backup/2013-03-17-14.09.00 . I can see it when I put my SD card in the PC.
However, CWM isn't finding it when it's in the device, and there's no option to direct CWM to where it is....
Solution anyone?

Bump....

damian5000 said:
I fragged up Android by applying an update, so I can't boot into Android.
I can get into CWM, but it doesn't see my backup... The backup is in /clockwordmod/backup/2013-03-17-14.09.00 . I can see it when I put my SD card in the PC.
However, CWM isn't finding it when it's in the device, and there's no option to direct CWM to where it is....
Solution anyone?
Click to expand...
Click to collapse
Hi there!
What I can think of is first of all save your CWM backup to your PC.
Then you'd really have to flash a ROM to at least a version that will enable you to use the version of your backup: say if the ROM requirement that you had installed when you made the backup was 4.0.4 then install any ROM of that. You won't have to install any apps then.
You can then install X-parts from Google Play and with that CWM but that will not be a "stuck-on" CWM as any ROM upgrade will remove it BUT the beauty of it is that in your backup [which you'll then copy from your PC to the same folder you describe above make a Restore] you have the CWM that will stick and from there on won't have to worry.
Sounds like a bit of work but personally I don´t see a way around it...this is what I would do to get things as before.
Hope this works for you and do let me know.
Oh and don't forget to click THANKS.

ac3ofS2 said:
Hi there!
What I can think of is first of all save your CWM backup to your PC.
Then you'd really have to flash a ROM to at least a version that will enable you to use the version of your backup: say if the ROM requirement that you had installed when you made the backup was 4.0.4 then install any ROM of that. You won't have to install any apps then.
You can then install X-parts from Google Play and with that CWM but that will not be a "stuck-on" CWM as any ROM upgrade will remove it BUT the beauty of it is that in your backup [which you'll then copy from your PC to the same folder you describe above make a Restore] you have the CWM that will stick and from there on won't have to worry.
Sounds like a bit of work but personally I don´t see a way around it...this is what I would do to get things as before.
Hope this works for you and do let me know.
Oh and don't forget to click THANKS.
Click to expand...
Click to collapse
Yea, what I ended up doing was installing a stock ROM, then installing Rom Manager. From ROM manager the backup installs no problem... But if booting directly to recovery, it can't find it, even though it's in the standard spot... It seems halfway pointless to me to have a backup that can't be restored from recovery... but who am I to judge :silly:

damian5000 said:
Yea, what I ended up doing was installing a stock ROM, then installing Rom Manager. From ROM manager the backup installs no problem... But if booting directly to recovery, it can find it, even though it's in the standard spot... It seems halfway pointless to me to have a backup that can't be restored from recovery... but who am I to judge :silly:
Click to expand...
Click to collapse
Okay... I think I found what the problem was. From within CWM App, I changed storage to external as opposed to internal, now the backups are found from recovery. Not 100% sure that's what the issue was, because I've wiped and installed a couple different ROMs since having the issue.

damian5000 said:
Okay... I think I found what the problem was. From within CWM App, I changed storage to external as opposed to internal, now the backups are found from recovery. Not 100% sure that's what the issue was, because I've wiped and installed a couple different ROMs since having the issue.
Click to expand...
Click to collapse
Hi there mate!
Thanks for sharing what the prob was at the end of it all...I surely learned something and my THANKS to you is given.
See ya around the Forum...

Clockworkmod not working anymore.

Well I have been a CWM(and sometimes also TWRP) user for years. But I am stumped. I recently started having issues staying connected to AIO/Cricket(voice not even staying connected). As I am running a custom ROM I decided to try Stock and see if the problem persists, thus it may be a hardware issue with the radio or something. So I did a current backup, and restored one from a few weeks back. It's the same ROM but I thought it was worth a shot. It restored fine but the problem persisted. Then I decided to restore my new backup from the hour before. It failed. Gave me an MD5 Mismatch error(I think I have that right). So I made another new backup, same thing. I am unable to restore any backups made right now. I can still restore the one from a few weeks ago. I am running the very latest CWM touch. I tried flashing TWRP to see if that might help(using Rom Manager to do so). This has always worked before. It said that it works, and even tells me it's rebooting into TWRP when I reboot to Recovery. But the broken version of CWM is still what is loading. I am at a loss here.

your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).

simms22 said:
your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).
Click to expand...
Click to collapse
Thank you! Gonna try flashing TWRP that way now!

Landara said:
Thank you! Gonna try flashing TWRP that way now!
Click to expand...
Click to collapse
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.

simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
First thing I did. I was able to backup with TWRP. Since I am currently running the restore from that NANDROID from a few weeks ago, it's all good! I am restoring the TWRP i just made, just to be sure. Seems to be restoring fine though. With my NANDRIOD problem solved, I can work on getting this radio issue fixed. I am really hoping it's just ROM related and I can salve it by flashing something else. I'm going to flash STOCK and see if it persists now.

simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?

Landara said:
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?
Click to expand...
Click to collapse
no problem, in stock or custom roms the radios are the same

simms22 said:
no problem, in stock or custom roms the radios are the same
Click to expand...
Click to collapse
Thanks!