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.
Related
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
naomile said:
Hello,
After I rooted my ATT galaxy note ICS 4.0.4, downloaded the blackstar6, put it in my sdcard in the phone. Wiped all the data etc...as instructed, when it got to the flashing part, can't open /sdcard/blackstar_VI.zip (bad). I tried 3 times, then restored the back up, then re-do again. still the same problem...any help would be appreciated. Thanks
Click to expand...
Click to collapse
Try redownloading black star and try again.
a3plew said:
Try redownloading black star and try again.
Click to expand...
Click to collapse
I did try, still the same result Thanks for responding.
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
rangercaptain said:
You didn't mention how you are flashing BS6. Are you using CWM or TWRP?
Click to expand...
Click to collapse
sorry, CWM, Thanks
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
rangercaptain said:
Well if you entered CWM recovery, wiped caches, did a factory reset, then flashed BS6, and you are not getting the rom to boot, the file is corrupted. It happens from time to time.
Click to expand...
Click to collapse
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
naomile said:
well, I downloaded bs6 at 2 different links, what should I do next. This is my first android phone sorry for some noobs questions.
Click to expand...
Click to collapse
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
and-on-ROIDS said:
Did you check MD5 and make sure they match? Like Ranger said, its probably a corrupted file.
Click to expand...
Click to collapse
hix I don't know how to do that, and where to check. Show me plizzzzzzzzzzzz
How are you entering recovery?
rangercaptain said:
How are you entering recovery?
Click to expand...
Click to collapse
hold down the volume up and down and power buttons at the same time. I got to the part that installing the bs6, then it said can't open bs6 (bad), so I have to do the restore. I just don't understand what the problem is ?
you didn't unzip the file, right?
rangercaptain said:
you didn't unzip the file, right?
Click to expand...
Click to collapse
ofcourse not sir, I followed instructions step by step.
Well try another rom and see if you get the same error message.
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigfau said:
What's the word? Were you able to flash another rom?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
No sir, I was not able to flash the bs6, it just aborted. would you help? thanks
Try flashing another another rom Its either a recovery issue, rom download issue, operator issue.
hix, CWM ofcourse otherwise how can I flash the ROM? anyway, just tried different ROM ICS IMM76D UCLF6 Base Build #4 samething happended I really don't know what's the problem. REALY need help urgently. Pleaseeeeeeeee help me
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
rangercaptain said:
Either your recovery is broken or you are missing a step/detail. How did you install CWM? Did you use Odin and flash a kernel or did you use Rom Manager app? Because the app doesn't work.
Click to expand...
Click to collapse
I used odin to flash. I had superuser I guess that means my device is rooted. then I downloaded the bsROM and other cooked ROM. I copied the bsROM zip to my sd card, CWM to recovery then wiped out all the data as instructed, then installed the ROM, everything went fine to this part then it couldnot open then aborted. tried 3,4 times with different rom: same results, aborted.
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
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?
Hi guys. I've had a rooted S3 for a while and have flashed loads of roms. Few months ago the phone started acting strangely and the only Ron I could get to work was the German version of the original KK. Now, even though the device is still rooted any attempt to flash another room will give a "signature not verified" error. Anyone else come across this?? Cheers
Hamsterboy2000 said:
Hi guys. I've had a rooted S3 for a while and have flashed loads of roms. Few months ago the phone started acting strangely and the only Ron I could get to work was the German version of the original KK. Now, even though the device is still rooted any attempt to flash another room will give a "signature not verified" error. Anyone else come across this?? Cheers
Click to expand...
Click to collapse
Do you use odin to flash roms or custom recovery??
Custom Recovery... TWRP. Think using Odin might yield some results?
Thanks for the reply btw ?
Hamsterboy2000 said:
Custom Recovery... TWRP. Think using Odin might yield some results?
Thanks for the reply btw
Click to expand...
Click to collapse
You can turn off signature verification in twrp it should do the trick bro hit the tnx button if I helped you
Oh cool. Didn't spot that. Using ROM Manager so will have a look at the options. Cheers
Hamsterboy2000 said:
Custom Recovery... TWRP. Think using Odin might yield some results?
Thanks for the reply btw ?
Click to expand...
Click to collapse
Be sure you haven't a borked version of TWRP. I think official 2.8.7.0 is borked.
Try a more recent unofficial one or use Philz touch 6.48.4 instead for instance.
If your recovery is OK, just check options inside twrp recovery about signature verification... Un-tick zip signature verification.
Btw, about root, AFAIK you can flash custom recovery and custom ROMs without being rooted.
You were right. Switched to CWR and it's all good. Cheers.....
Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Danish78 said:
Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Click to expand...
Click to collapse
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
MyNameIsRage said:
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
Click to expand...
Click to collapse
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Danish78 said:
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Click to expand...
Click to collapse
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
MyNameIsRage said:
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
Click to expand...
Click to collapse
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Danish78 said:
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Click to expand...
Click to collapse
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
MyNameIsRage said:
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
Click to expand...
Click to collapse
Oh man this totally fixed the issue.
Thanks a lot.
I thought I'd have to flash an official firmware and start from scratch.
You saved me a lot of time.
Thank you very much