Related
Just a quick question to double check.. I rooted my atrix 2 and installed CWM and took backup of my phone thru it. So two questions:
1.} Now to install custom rom, what should i do? directly now download and install thru cwm or need to flash any other thing?
2.} I accedently changed my stock battery icon thru rom toolbox pro and when i restore my stock rom thru cwm it says md5 check failed.. What should i do?
To install a Custom Rom only need access to CWM Recovery, and follow the installation steps of the Rom you choose, as there are two forms, one is restored and the other is flashing, so you should read the instructions.
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Sedariya11 said:
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Click to expand...
Click to collapse
No rsd and fastboot files are for flashing back to stock in the case of u messing up your phone (soft brick or bootloop)
Sedariya11 said:
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Click to expand...
Click to collapse
for restoring. do a few things. first, make a backup right now and try to restore it right away. If that works, something went wrong with your old one. you can open up the nandroid.md5 file within the backup folder and delete everything, that will make it restore, but it could cause some issues if it really was broken. Or it could not even boot, but that is what the fxz is for.
If it also fails, most likely there is something wrong with your sdcard. that happened to me. try formatting it WITH THE PHONE (backup anything that you need to since it will be wiped). if it fails both times the backups are most likely fine, so just delete everything in the nandroid.md5 file and do it. Keep in mind it may still have issues so be familiar with the stock restoring process just in case.
As always, i don't take responsibility for anything that happens.
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
None of the 130 viewers have any advice on this one?
HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck
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
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update? Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
tylerlawhon said:
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update?
Click to expand...
Click to collapse
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
Click to expand...
Click to collapse
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
I'll check my wife's phone tonight. If she gets the ota I will pull it from the cache and extract the boot loader and recovery and rezip it and see if it will flash via twrp
SlimSnoopOS said:
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
Click to expand...
Click to collapse
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
tylerlawhon said:
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
Click to expand...
Click to collapse
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
SlimSnoopOS said:
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
Click to expand...
Click to collapse
Hmmm sounds interesting. I doubt I'd be able to use EZ unlock like I did on ICS... I guess I'll wait for a recovery flashable file.
What OTA?
cammykool said:
What OTA?
Click to expand...
Click to collapse
4.1.2 ota being pushed starting today. According to Google+
Is this basically the same thing as the VRBMA2 leak?
pettigrew95 said:
Is this basically the same thing as the VRBMA2 leak?
Click to expand...
Click to collapse
Yes, it's a final version of VRBMA2 leak which is VRBMB1
Damn.... on the day i root... oh well glad i did!
vzw probably blocked our current methods.
The OTA de-odexed is already posted courtesy of beanstown over here:
http://forum.xda-developers.com/showthread.php?t=2177798
I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.
lexluthor said:
I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.
Click to expand...
Click to collapse
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798
pettigrew95 said:
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798
Click to expand...
Click to collapse
I'd rather have the odex version though. You think someone will post that?
OK I took it from cache. Does anyone remember what all I need to delete after I extract it so it doesn't update boot loader. Recovery for sure...here's where I am before i rezip
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!