Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
Related
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
jfigura said:
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
Click to expand...
Click to collapse
You cant flash clockwork recovery from the phone it has to be pushed in odin then you can flash it in rom manager
The thread is in the development section
Do a little searching around and you ll find all the info you need
Yet another reason not to use z4 root as you learn nothing about your phone
And really it aint hard to do things the" right" way
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Soba - Once I repushed from Odin it came back. Scratching my head a little but hey it's back. I used Z4 on this phone because I got caught by Verizon when I manually rooted the first model which went bellyup after having it for a week. I wanted to make sure I could quickly get rid of the root if I needed to go back into the store.
To the other responder, sorry for not being specifically "clear".
I've been tinkering with 6 different phones from this one to two Motos and 3 different HTC's. All the methods are beginning to run together sometimes.
I appreciate the assist and I thank you both.
soba49 said:
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Click to expand...
Click to collapse
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
woodaresick said:
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
Click to expand...
Click to collapse
Here's Update.Zip file for CWM
Direct Link, I uploaded it by myself, couldn't find decent one
http://www.4shared.com/file/ReRrCtwV/update.html
Make Sure to thank me if it works
If it doesn't let me know.
THIS THREAD IS NO LONGER RELEVANT AS IT IS FOR A DIFFERENT ISSUE FROM THE PAST... IT GOT BROUGHT BACK TO THE TOP. DONT CONFUSE THIS WITH THE 3E RECOVERY "ISSUE"
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Update from koush:
@clockworkmod Hey all, flashing recoveries through ROM Manager is busted. We hit a bandwidth/CPU quota on Google App engine.
If you are trying to flash Clockwork Recovery for the first time, it appears that a lot of users are having issues over the past 24 hours.
Normally, you would:
download Rom Manager
Click Flash Clockwork Recovery
it will ask for root privelages
you would select the Vibrant as your phone
after it downloaded CWR you would get a successful pop-up....
you could then click on reboot into recovery (and since it was the first time you would go to the stock recovery, click reinstall packages, and THEN you would go to Clockwork Recovery)....
well.... people can't seem to get there now. I am NOT having issues as I already have CWR. However, if you are, please download this file on your phones browser (just so you dont have to mount your phone to your pc.... which you can do if you prefer)
FILE DOWNLOAD HERE: View attachment update.zip
Move this file to the root of your internal memory. If you have any other update.zip file you can just overwrite it, or delete it prior to moving this file over, your choice....
NOW, go back to your stock recovery and press reintall packages.... you should go to CWR, if not, press to reinstall again... still no luck? blasphemy.
With all of that said, I need someone to post that this successfully works (it should, and you really can't lose anything)
I am contacting koush for an explanation of what's wrong....
i will check this out
everytime i boot into recovery and press reinstall packages my just restarts phone and i can't get into clockwork.
You generally have to tell it to reinstall packages twice.
^ that has not been the case for me.. but try it twice if if doesn't work the first time!
Yeah, it may depend on the ROM being run or something, but I've noticed it quite a bit.
yeah, something happened when rom manager updated in the last day where flashing recovery isnt compatable with galaxy s devices anymore. drove me freakin crazy cuz i just dl'ed nero and went to install and couldnt.
thank you again. +10 internets to u.
I started having an issue after flashing eugenes super kernel. I did a.clean install of axura and problem went away.
Powered by Axura
^ the rom would have nothing to do with it.
Koush has fixed this, it was server related.
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW (NORMAL STEPS STILL INCLUDED BELOW). I KNEW THIS WOULD BE A QUICK FIX FOR KOUSH!
As of 10mins ago i was having this problem.
But thanks to this post and installing the downloaded update I'm back up!
Rom manager gave me errors when flashing the clockwork recovery
so had to go to the update.zip and i'm now back!
Dont think rom manager in the market has been updated
[i was coming from a odin[ed] JFD stock.
hope this helps someone else!
Thanks... this works for me :\
I flashed to JL4 and had a freaking wifi boot loop and gotta go back to Eugene's does not brick ROM and found out can't install CWM via ROM manager
I don't know if its supposed to fix it, but even after flashing this Im still having issues with ROM manager. Get an error every time I try to update the recovery. Also, I can't remember the last time fix permissions actually worked (eclair maybe?).
Anyone else feel my pain?
This is a fix, and you trying to update the recovery is no different than those who have issues not even using my .zip....
I updated the op with a tweet from koush. He has a fix on his site too (might as well download it from here though?
I downloaded the new update, still can't get into clock work. When I hit reinstall packages it says ... E: error /cache/update.zip
(bad)
Installation aborted
Sent from my SGH-T959 using XDA App
^^^ I'm having the same problem as well right now.
reinstall off market and it works
I thought I was sunk until an hour of searching found this post. Thank you all so much!
I have after upgrade to K6 the error messeage:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I've try the update.zip from the 1st post,
reinstalled via market
update und select the Vibrant modell
everytime the same...
the phone is rooted via SuperOneClickv1.5.5-ShortFuse
Any help ?
None of this works because none of it addresses the real problem ,3E signature. Way to much trouble to go thru.
^ This thread was created when the Clockwork servers were down... it has absolutely nothing to do with 3e recovery... as that didnt even exist when this thread was created... hopefully others are not confused now that it was brought back to the top.
I didn't update it yet, because the thread was dead.
And to be fair the OP did have this:
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Click to expand...
Click to collapse
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Manneman32 said:
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Click to expand...
Click to collapse
You didn't mention the version of Philz you were using. Anyway, the error 7 can be caused from 2 main reasons:
1- Older recovery version. Flash the lastest recovery available (6.15.4) and try again: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
2- Corrupted rom download.
To your 2nd question- if it doesn't work with Philz, it will not work with any other recovery.
Well... when I asked about how to go about rooting just a week ago I got links to what I needed. And with that I got a link to Philz Recovery. But now I see that it was an old version (6.07.9)
I´ll try with the latest one and see where that takes me.
Edit:
Flashed the latest Philz and took a new backup just in case. It didn´t work. Still Status 7. So I re-downloaded the ROM just in case it was corrupted but still the same... aborted Status 7.
So... now what? Am I screwed?
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Manneman32 said:
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Click to expand...
Click to collapse
Worth the try
Here 2 relevant threads I found:
http://en.miui.com/thread-6429-1-1.html
Follow galnet post (page 7):
http://forum.xda-developers.com/showthread.php?t=1749392&page=7
Sent from my GT-I9300 using Tapatalk
So... the links refer to downgrading to a really old recovery used for rooting with CF or unticking the "disable signature check" ... feels strange.
Is there anyway to explain why this error occurs?
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Manneman32 said:
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Click to expand...
Click to collapse
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221