Hi Folks,
I have just installed CWM recovery V 6.0.4.6 using ROM Manager app in my Galaxy S3 I9300 running on stock android 4.3 . I rebooted the device to check it and it was successfully installed. While I tried to reboot device through an option in the recovery, it showed up two messages as follows,
Message 1:
ROM may flash stock recovery on boot. Fix? THIS CAN'T BE UNDONE
1.No
2.Yes - Disable recovery flash
Message 2:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. No
2. Yes - Fix root (/system/xbin/su)
I selected option "2.Yes - Disable recovery flash" from Message 1 and again option "2. YES fix root (/system/xbin/su)" from Message 2.
Why these messages are getting displayed? Is there any problem now?
Also please let me know whether it will revert to Stock Android Recovery by selecting Option "1.No" from Message 1. If so again I have to flash CWM recovery?
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks. So shall I revert back to stock recovery by selecting 1.No from message 1 and then flash cwm using odin?. Will it be fine?
I have also read that many folks facing same kinda issue even they flashed CWM recovery using odin.
Please advice that will there be any issues if I flash Cynogenmod 10.2 now?.
Any help on this? Please.
mpadhu said:
Any help on this? Please.
Click to expand...
Click to collapse
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
boomboomer said:
Don't use rom manager on the s3.
Click to expand...
Click to collapse
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
Click to expand...
Click to collapse
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
dxppxd said:
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
Click to expand...
Click to collapse
Hence the statement:
"As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. "
dxppxd said:
It's better to install cwm recovery through means other than rom manager to avoid problems.
Click to expand...
Click to collapse
My point is that of the two, Rom Manager is the one that works. I have never had issues using Rom Manager to install recoveries. Although, I always install the first time using fastboot... So my anecdotal impressions may not apply here.
Care to explain your statement? (Which is the intent of my original message. Why the Koushik XDA witchhunt?)
I would search, but XDA search is borderline unusable.
Thanks!
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
None of the stock roms I've used have ever tried to restore stock recovery, it's just left there from other devices that do it.
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
Click to expand...
Click to collapse
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
When asked those i always select "no" to both. Never had an issue.
mpadhu said:
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
Click to expand...
Click to collapse
Looks like a successful backup to me.
t1n0m3n said:
Looks like a successful backup to me.
Click to expand...
Click to collapse
Thank you. I have successfully flashed Cynogenmod 10.2.
I can see my old android files still present in the internal memory. I did wipe data/factory reset, wipe cache partition and wipe dalvik cache but still the files are present. Will it cause any problem if I remove those files? If No will a factory reset work to remove those files?
Related
Hi guys,
I used this method to root my phone:
http://forum.xda-developers.com/showthread.php?t=1103399
Everything seems to work fine, and i just installed my first rom (ginger mod), i would like to ask you:
1. Every time i install a new rom, i'll do a wipe for secerity reasons, but by doing this, how come everything i had on the phone doesn't dissapear, like pictures? Doesn't wipe mean factory reset = remove everything on the phone?
2. Every time i install a new rom, does the older one get removed automatic or do they stay left on the phone, if so how do i remove the old stuff?
3. I know this may sound stupid, but do i have the same root every time i install new rom? Because i noticed when i install new rom and i went i to recovery mode i see new color on the Meny, that's normal?
4. Which app is good for beginners to start with, like Rom's and doing backup, which of these should i purchase: titanium backup, rom manager P, rom toolbox P.
thanks guys,
1. Internal SD card data remains. Can't tell you why it just does.
2. Old Rom is replaced. No need to remove it.
3. Each Rom has its own kernel. That kernel may or may not be rooted.
4. Titanium backup. Also do backup via CWM.
Sent from my GT-I9100 using XDA App
aceofclubs said:
1. Internal SD card data remains. Can't tell you why it just does.
2. Old Rom is replaced. No need to remove it.
3. Each Rom has its own kernel. That kernel may or may not be rooted.
4. Titanium backup. Also do backup via CWM.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Thank you for the quic answers,
1. when you're talking about the CWN, do you mean the one in the Rom manager?
2. So each rome, has their own root theme if i understood this correctly, so i don't need to worrie about re-rooting the device or something like that, because each rom has their own theme and meny?
3. which rom do you use and why, do you think that ginger-mod is good?
thanks again.
Darwichee said:
Thank you for the quic answers,
1. when you're talking about the CWN, do you mean the one in the Rom manager?
CWM not rom manager CWM is the modified recovery menu or CWM app .
2. So each rome, has their own root theme
No not all custom roms are rooted
jje
Click to expand...
Click to collapse
Darwichee said:
3. which rom do you use and why, do you think that ginger-mod is good?
thanks again.
Click to expand...
Click to collapse
One you did a backup with your ClockWorkMod recovery, you can experiment as much as you wish. You can go with various TouchWiz-based roms. You can try CyanogenMod or MIUI, which are completely different. And if you don't like them, just restore the backup.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
One you did a backup with your ClockWorkMod recovery, you can experiment as much as you wish. You can go with various TouchWiz-based roms. You can try CyanogenMod or MIUI, which are completely different. And if you don't like them, just restore the backup.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
1.Ok guys, i soon understand everything. I never did a backup on any roms. Here's the deal. When i first rooted the device, i used this method:
http://forum.xda-developers.com/showthread.php?t=1103399
2.I also got the CWM app with this root, and superuser( which i dont know what this do), but now when i installed Ginger-mod, suddenly i don't have the CWM app anymore, which i guess is normal?
3.So please can you explain this for me. Lets say i have ginger-mod now, but i decide i want to install CM7 now, but before i do this, i'll have to do a backup of the ginger-mod if something goes wrong with the CM7, am i right so far?
So i'll have to install this CWM app (where i find it?) and make a backup, and then try a new rom. But if i make a wipe before installing new rom, wont the CWM app dissapear or something like that? Or if i install new rom again, will the CWM app be gone again?
I know my English grammer isn't that great, but i'll hope you understood me anyway.
thanks again
Darwichee said:
2.I also got the CWM app with this root, and superuser( which i dont know what this do), but now when i installed Ginger-mod, suddenly i don't have the CWM app anymore, which i guess is normal?
Click to expand...
Click to collapse
The CWM app is a manager for the ClockWorkMod-recovery. The ClockWorkMod-recovery is a replacement for the stock Android-recovery. You enter the recovery by shutting your device down, holding volume-up and home and then pressing the power-button until you see the galaxy s2 logo. The CWM-app does not give you root-rights, in fact, it requires root-rights to work properly.
The SuperUser app gives you the root-rights. On OS' like Linux (and of course Android) there is one user called "root" (or superuser). He is basically what the Administrator was for Windows before Vista, having full access to everything.
The superuser-app manages what apps get root-permissions. You'll notice when it happens, because whenever an app wants to gain root-permissions, you'll see the superuser-app popping up and asking you if this is OK.
The fact that you don't have the CWM-App is no problem, as it just manages the recovery. The recovery itself does not need additional apps to be installed.
Darwichee said:
3.So please can you explain this for me. Lets say i have ginger-mod now, but i decide i want to install CM7 now, but before i do this, i'll have to do a backup of the ginger-mod if something goes wrong with the CM7, am i right so far?
Click to expand...
Click to collapse
Enter the cwm-recovery (already said how you do this). You'll find various menus. One of them is the "Backup and Restore"-menu. You'll just create a backup to your internal or external sdcard (as you wish). When it is completed (without errors), you can safely flash any other rom. If you want to come back, you just enter cwm again and restore the backup.
You don't have to create a backup, but it's always good to have one of a working system.
Darwichee said:
So i'll have to install this CWM app (where i find it?) and make a backup, and then try a new rom. But if i make a wipe before installing new rom, wont the CWM app dissapear or something like that? Or if i install new rom again, will the CWM app be gone again?
Click to expand...
Click to collapse
As I already said, you don't need the app. If your kernel does not provide it (it's just not there from the start), live with it. Everything you do in this app will just start the cwm-recovery anyway.
The ClockWorkMod-recovery is the "standard" for custom-roms. You can be sure that, if you flash another rom, it will have it too. And if your Rom does not come with CWM (like a stock-rom), you can just flash a kernel with cwm again (like Siyah).
Hope this clears things up for you. If you have any more questions (even if you think they're stupid) ask us here. It's better to ask twice, than to break something.
Happy new year!
TheSniperFan said:
The CWM app is a manager for the ClockWorkMod-recovery. The ClockWorkMod-recovery is a replacement for the stock Android-recovery. You enter the recovery by shutting your device down, holding volume-up and home and then pressing the power-button until you see the galaxy s2 logo. The CWM-app does not give you root-rights, in fact, it requires root-rights to work properly.
The SuperUser app gives you the root-rights. On OS' like Linux (and of course Android) there is one user called "root" (or superuser). He is basically what the Administrator was for Windows before Vista, having full access to everything.
The superuser-app manages what apps get root-permissions. You'll notice when it happens, because whenever an app wants to gain root-permissions, you'll see the superuser-app popping up and asking you if this is OK.
The fact that you don't have the CWM-App is no problem, as it just manages the recovery. The recovery itself does not need additional apps to be installed.
Enter the cwm-recovery (already said how you do this). You'll find various menus. One of them is the "Backup and Restore"-menu. You'll just create a backup to your internal or external sdcard (as you wish). When it is completed (without errors), you can safely flash any other rom. If you want to come back, you just enter cwm again and restore the backup.
You don't have to create a backup, but it's always good to have one of a working system.
As I already said, you don't need the app. If your kernel does not provide it (it's just not there from the start), live with it. Everything you do in this app will just start the cwm-recovery anyway.
The ClockWorkMod-recovery is the "standard" for custom-roms. You can be sure that, if you flash another rom, it will have it too. And if your Rom does not come with CWM (like a stock-rom), you can just flash a kernel with cwm again (like Siyah).
Hope this clears things up for you. If you have any more questions (even if you think they're stupid) ask us here. It's better to ask twice, than to break something.
Happy new year!
Click to expand...
Click to collapse
thank you, you explained everything perfect. I think i can manage figure out the rest by my self. Just one last question:
I noticed to good programs, and where you also could do a backup for your rom's and much more:
# Rom manager (Premium)
# Root toolbox (Pro)
Which one of these would you suggest for a beginner friendly UI and settings, do you use one of these?
thanks, and happy new year.
You don't need them. The ROM-manager is just an app like the cwm-app. It handles your ClockWorkMod-recovery. It does nothing itself. Once you click create backup, your phone will reboot into the ClockWorkMod-recovery, which will do the job.
However for the ROM-manager to work, you need to install the ClockWorkMod-recovery that shops with it. Just stick with the version of your kernel. This avoids confusion.
Besides that the ClockWorkMod-recovery is beginner-friendly. Just don't touch any options, you don't know what they do.
I recommend you to get a kernel with the latest recovery. The Siyah-kernel. It is compatible to practically every ROM out there. Just reflash the kernel after you flash a ROM.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
You don't need them. The ROM-manager is just an app like the cwm-app. It handles your ClockWorkMod-recovery. It does nothing itself. Once you click create backup, your phone will reboot into the ClockWorkMod-recovery, which will do the job.
However for the ROM-manager to work, you need to install the ClockWorkMod-recovery that shops with it. Just stick with the version of your kernel. This avoids confusion.
Besides that the ClockWorkMod-recovery is beginner-friendly. Just don't touch any options, you don't know what they do.
I recommend you to get a kernel with the latest recovery. The Siyah-kernel. It is compatible to practically every ROM out there. Just reflash the kernel after you flash a ROM.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You have been veryhelpful, i've learned a few things now thanks to you. Just some last questions then i'm fine.
1. I've downloaded Siyahkernal from his website http://www.gokhanmoral.com/ and as you see, i can choose between TAR, and Zip (download), which one of them is it that i put under the PDA in Odin? Or it doesn't matter which i download?
2. So after every Rom install i make, i install Siyah-kernal, let's say i installed Ginger-Mod, and this mod has Darkknight kernal, and now i install Siyah, will Siyah replace the other kernal, or will those 2 stick with eachother?
3. Just so i don't make any misstakes, installing kernal, is like installing root for the first time right? Meaning = 1, Put phone into download mode. 2.Put the kernal file in PDA 3. Press start?
4. I've noticed that there's a new version av Siyah 2.6.4, is this stable, and have he released it for download yet, because i couldn't find it?
Thanks for every answer you giving me. I feel much safer allready =).
Darwichee said:
You have been veryhelpful, i've learned a few things now thanks to you. Just some last questions then i'm fine.
1. I've downloaded Siyahkernal from his website http://www.gokhanmoral.com/ and as you see, i can choose between TAR, and Zip (download), which one of them is it that i put under the PDA in Odin? Or it doesn't matter which i download?
ODIN is TAR CWM is ZIP .
2. So after every Rom install i make, i install Siyah-kernal, let's say i installed Ginger-Mod, and this mod has Darkknight kernal, and now i install Siyah, will Siyah replace the other kernal, or will those 2 stick with eachother?
REPLACE
3. Just so i don't make any misstakes, installing kernal, is like installing root for the first time right? Meaning = 1, Put phone into download mode. 2.Put the kernal file in PDA 3. Press start?
YES
4. I've noticed that there's a new version av Siyah 2.6.4, is this stable, and have he released it for download yet, because i couldn't find it?
No idea read the siyah thread .
No point asking is anything stable its development forum and as 2.6.3 was only released two days ago i guess not .
Stable = stock .
Once you start you have to be prepared for problems though 90% do not have a problem some do .
Rooting or Custom rom voids warranty .
jje
Click to expand...
Click to collapse
As JJEgan said.
4. You can see what the developer is working on while he is doing it. Therefore the changelog for the latest release is what to expect for the next version.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
As JJEgan said.
4. You can see what the developer is working on while he is doing it. Therefore the changelog for the latest release is what to expect for the next version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Ah ok, i see. But do you think i should use the 2.6.3 version( since it's new), or is there any older version that's more stable?
Answer to Jjegan:
Yes i know, but there's allways something els you can say to the store, because they can't proof my phone got destroyed by rootinng,or can they?
Thanks guys.
Go with the latest one and, if you experience any problems, look for an update or downgrade, if there is none available yet.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
Go with the latest one and, if you experience any problems, look for an update or downgrade, if there is none available yet.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I started to notice another problem.
Sometimes CWM wont recognize my external SD, example: I have put kernal, and roms in it, and when i want to flash these, i only get "no files found". And sometimes it work, but often it wont.
What can i do about this?
Sometimes cwm mistakes the internal for the external. Just take the other option.
Besides that, better update to Siyah 2.6.4. The ClockWorkMod there is more reliable.
Sent from my GT-I9100 using XDA App
Hi, I have been trying to figure this out for hours.
I flashed cyanogen mod 9 using rom manager from my stock rooted 19300. All went smoothly but now with cyanogenmod 9 Rom manager is really temperamental and keeps not responding when I try to use it.
Anyone any help? Please go easy with the tech terms I am a total beginner.
I also noted cyanogen mod 9 has no file explorer but I found root manager seems to do the trick. Took me a while to figure that out aswell.
Cool ROM though!:good:
Hope someone can help me out.
don't use rom manager, allegedly it's buggy. also, why ICS? we now live in a JB world
Glebun said:
don't use rom manager, allegedly it's buggy. also, why ICS? we now live in a JB world
Click to expand...
Click to collapse
It was my first flash. I thought it was fairly new? How do I get JB? Where can I find the ROM file?
Thanks for the reply
So clockwork rom Manager seems to be ok now.
But another issue thats really bugging me is that CW rom manager won't recognise my ext sd card.!
Anyone any ideas
same answer, don't use it. find roms in the roms section
Glebun said:
same answer, don't use it. find roms in the roms section
Click to expand...
Click to collapse
Ok cheers, So what would you recommend I use instead for backing up ROM's etc. CWM just makes things so easy for installing ROM's from the phone. Is there another app that will do this.
On cyanogemod 9 CWM seems to be a system app also. So cant really go delete it.
schooner said:
Ok cheers, So what would you recommend I use instead for backing up ROM's etc. CWM just makes things so easy for installing ROM's from the phone. Is there another app that will do this.
On cyanogemod 9 CWM seems to be a system app also. So cant really go delete it.
Click to expand...
Click to collapse
Use the recovery menu. What you are doing is not ment to be easy. You have to understand what you are doing or you will end up in an unhappy place now that your warranty is voided.
zelendel said:
Use the recovery menu. What you are doing is not ment to be easy. You have to understand what you are doing or you will end up in an unhappy place now that your warranty is voided.
Click to expand...
Click to collapse
Never had warranty in the first place. Have to learn somehow so no point being afraid of it. So what your saying is use cwm manually so to speak instead of backing up roms and flashing new rom through the app?
schooner said:
Never had warranty in the first place. Have to learn somehow so no point being afraid of it. So what your saying is use cwm manually so to speak instead of backing up roms and flashing new rom through the app?
Click to expand...
Click to collapse
Yes. Rom manager has caused issues as long as i can remember, to the point that even some devs advice not to use it at all.
schooner said:
Never had warranty in the first place. Have to learn somehow so no point being afraid of it. So what your saying is use cwm manually so to speak instead of backing up roms and flashing new rom through the app?
Click to expand...
Click to collapse
Yep CWM recovery as it states on the tin CWM Manager is no longer updated or supported .
jje
Im kind of confused. Is cwm recovery not rom manager? Do i have rom manager or cwm recovery
Im going to attach screen shots.
So is this what i should use? Or is it recommended to use something else.
If i shouldnt use it, what will happen if i delete it seen as it's a system app and what's a good replacement?
schooner said:
Im kind of confused. Is cwm recovery not rom manager? Do i have rom manager or cwm recovery
Im going to attach screen shots.
So is this what i should use? Or is it recommended to use something else.
If i shouldnt use it, what will happen if i delete it seen as it's a system app and what's a good replacement?
Click to expand...
Click to collapse
No Rom manager is not CWM recovery. It is an app that is supposed to work with the cwm recovery.
All the options you need are in recovery when you boot directly to recovery from the reboot menu.
zelendel said:
No Rom manager is not CWM recovery. It is an app that is supposed to work with the cwm recovery.
All the options you need are in recovery when you boot directly to recovery from the reboot menu.
Click to expand...
Click to collapse
Got it:good: Thanks
I've just rooted my device....first time ever, and just going through many of the lists of things to install and do. ROM Manager seems to be mentioned on every site. I installed it, was going to try and make a nandroid backup before I venture into flashing a custom ROM. First off, when I try to put in my Recovery Setup, I dont see the Galaxy S4 in the list of phones. Right now it just says Current Recovery: ClockworkMod 5.x.x.x
I thought this was correct, but when I go to "Reboot into Recovery" and try to make a backup....there is no option to make a backup on the startup list.
I've never used ROM manager before....have no idea what I need to change as I cant even find any GS4 listed. I was assuming I set it up incorrectly and thats why I couldnt backup. Anyone know what might be going on here?
Any help here? I'm confused, to get ClockworkMod Recovery to install....you install ROM Manager correct? I've uninstalled ClockworkMod ROM Manager and reinstalled it, still dont have the option to select a GS4 and no option to make a backup when in recovery mode. I do need to use this to make a recovery of my phone if I flash a new ROM and want to go back correct?
Every video I've seen of people setting this up on their GS4, find a GS4 on the phone list....why dont I see one? Is there another component needed to use this properly?
stringboi said:
Any help here? I'm confused, to get ClockworkMod Recovery to install....you install ROM Manager correct? I've uninstalled ClockworkMod ROM Manager and reinstalled it, still dont have the option to select a GS4 and no option to make a backup when in recovery mode. I do need to use this to make a recovery of my phone if I flash a new ROM and want to go back correct?
Every video I've seen of people setting this up on their GS4, find a GS4 on the phone list....why dont I see one? Is there another component needed to use this properly?
Click to expand...
Click to collapse
The current build of cwm recovery for this phone is not supported through rom manager. This phones recoverys are loki patched to bybass bootloader. Easiest way to install cwm is via my all in one tool in yhe development section. If you are already rooted choose preo for recovery step then install cwm steo. Full instructions and things to watch for are in the 1st post
bhp090808 said:
The current build of cwm recovery for this phone is not supported through rom manager. This phones recoverys are loki patched to bybass bootloader. Easiest way to install cwm is via my all in one tool in yhe development section. If you are already rooted choose preo for recovery step then install cwm steo. Full instructions and things to watch for are in the 1st post
Click to expand...
Click to collapse
Ok so its not me...I thought I was going crazy here. Thank you so much!
BTW, does ROM Manager need to stay on the phone to do this? (sorry noob here)
I did as you said, everything went fine....but when I reboot in recovery, I still have no option to make a backup. This is the proper procedure to make a backup of your phone before flashing a custom ROM right, or am I going about this the wrong way? I want to make sure I cover my butt if I dont like one or screw it up.
stringboi said:
I did as you said, everything went fine....but when I reboot in recovery, I still have no option to make a backup. This is the proper procedure to make a backup of your phone before flashing a custom ROM right, or am I going about this the wrong way? I want to make sure I cover my butt if I dont like one or screw it up.
Click to expand...
Click to collapse
Did you install a recovery? If so which one?
bkhorn said:
Did you install a recovery? If so which one?
Click to expand...
Click to collapse
I got it to work, I had uninstalled ROM Manager before doing this install method because I thought it was useless....didnt realize that it was needed to load the proper recovery. I'm all good now.....so far =)
I got it to work and am able to backup to the internal SD, but I cant seem to get it to backup to my extSD. Every time I choose external, I get "Cant mount /external_sd" "Cant mount backup path" Using a 64gb Samsung card if it helps....
Thanks again!
Lol. It won't back up ext sd because you don't have that partition..you're all good
Sent from my SCH-I545 using Tapatalk 4 Beta
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.
[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker