Related
so i got an update for cwm to 2.5.1.1 and i did a backup of rr1.7, went back to recovery did my usual wipes tried to reinstall and now i cant restore anything at all!! wtf now i cant use my phone what can i do?
i just resolved it, ACD168 helped me. i just downloaded the older version from unrevoked.com and installed it from hboot...everything works now but will not be updating to this version again
What error are you getting?
i saw a message before about a backup failing after updating to the latest clockwork. thats why i didnt install it yet
mine has been doing that too. all mine says is md5 mismatch i think. and onces that happens i can't flash any roms. I will have to wipe my Sd card and start from scratch. my worst fear is that and i get bootloop IM SCREWED cause none of my backups will work.
and yes i have tried backing up in rom manager and in clockwork. and then trying to restore in clock work and in rom manager and they always say mismatch.
and i am trying to restore right after i back up.
Well, I'm doing a backup now. Will let you know how it goes. So far so good, with no errors. Worst case, there's always adb.
error while formatting system, i didnt see nything bad about it b4 i updated so i didnt think thered be a problem but now there is
pete_kowalski83 said:
so i got an update for cwm to 2.5.1.1 and i did a backup of rr1.7, went back to recovery did my usual wipes tried to reinstall and now i cant restore anything at all!! wtf now i cant use my phone what can i do?
Click to expand...
Click to collapse
The only thing I know to try is manually revert back to 2.5.0.5 then recover a previous backup. I imagine you'll have to push it in ADB but I'm no expert.
Sent from my ADR6300 using XDA App
bensl84 said:
mine has been doing that too. all mine says is md5 mismatch i think. and onces that happens i can't flash any roms. I will have to wipe my Sd card and start from scratch. my worst fear is that and i get bootloop IM SCREWED cause none of my backups will work.
and yes i have tried backing up in rom manager and in clockwork. and then trying to restore in clock work and in rom manager and they always say mismatch.
and i am trying to restore right after i back up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=714114
E:failure at line 6
Backed up with no errors. Formatted and cleared everything with no errors. Now it's installing the ROM. At "copying files." Again, no errors so far. Heading to bed, will report back tomorrow morning.
well what the hell? ive never had any problems before i need some help people! im s-off just took an update from rom manager and now im screwed. im not a dev or anykind of programmer. i can get to recovery and everything but wen i do a restore it says cannot format system, now it says md5 mismatch, and now im trying it again and it gets to restoring system but then just hangs
Ok... so is the update i installed today gonna screw up my phone. I haven't done anything with it yet. Should I hold off doing any backups? Is anyone having luck with 2.5.1.1?
Sent from my ADR6300 using XDA App
I'm not getting the mismatch error, it's just freezing at MD5
I installed it and updated kernels with it, worked fine.
Upon entering clockwork recovery I was immediately getting errors that said:
E:Can't mount /dev/block/mmcbld0p2 (file exists)
and if I tried to restore a backup I would get stuck at MD5
I downgraded my clockwork to 2.5.0.1 and am now trying another restore. It looked like it was working since it got past MD5 and seemed to restore a few files but then the phone rebooted and not is stuck on the unrevoked splash screen.
This just goes in loops.
Hope someone figures this out because my phone is toast as of now.
This must be a hit and.miss sort of thing because im having no issues
Sent from my ADR6300 using XDA App
I was getting errors, so I downgraded. Then, I reupgraded after going into recovery and all is good. This version is sweet!
Sent from my personal space
I had downgraded to 2.5.0.1 and after a couple of battery pulls due to freezing up and unrevoked screen I finally got into recovery and now it says v2.5.1.1 - Not really sure how it got back to this version on its own.
Anyway I thought the restore was working but now it's been sitting at htc_wallpaper_small for 5 minutes and hasn't progressed.
Guess I'll downgrade my version again and then do an upgrade.
ncwildcat said:
I was getting errors, so I downgraded. Then, I reupgraded after going into recovery and all is good. This version is sweet!
Sent from my personal space
Click to expand...
Click to collapse
Do you mean you downgraded your version of recovery? If so how exactly did you do it.
I installed the zip for a lower version and it appears to take but as soon as I reboot back into recovery its back at 2.5.1.1
So it wasn't just me.. I downloaded update, tried installing zip through rm, stopped at "writing boot".
Sent from my ADR6300 using XDA App
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
So I installed the 12/09 Nightly of CM10 and ever since I cannot Restore or Install any ROMs. My Recovery is TWRP 2.3.1.1. It seems as though I cannot Wipe Cache, Dalvik, Factory Reset or System Wipe either. When I am using the latest installed ROM after a couple hours all of my apps force close, including Trebuchet leaving me to reset my phone.
When I reset and go into Recovery, I can restore backed up ROMs or new ones and when I reboot I am still on 12/09 CM10 with no errors until after a couple hours go by. I have tried installing CMW with no luck and re-installing TWRP with no luck. I have also tried the unrooting/unbricking method using Odin with no luck.
I am stuck on CM10 12/09 Nightly and my TWRP isn't helping in any way. I don't know if anyone else has ever run into this problem. Please help if you can.
Did you somehow loose super user? It sounds like a permission thing. When you install a new rom watch closely to what it says. You have to be getting some kind of error.
Hope this helps, good luck
Have you tried re rooting then re flashing twrp?
Sent from my liquid smooth t989
onlychevys said:
Did you somehow loose super user? It sounds like a permission thing. When you install a new rom watch closely to what it says. You have to be getting some kind of error.
Hope this helps, good luck
Click to expand...
Click to collapse
It still asks for super user when I go into a root application. I have tried installing supersu and it fails when trying to update the binary files. It has to be an error. Is it possible that my recovery could have become corrupt? I can't even download a new version of CM10. Every time I tried installing clockwork through rom manger is force closes all my apps and I am still on twrp. I have even tried installing with terminal emulator as well with no luck.
skaroger867 said:
Have you tried re rooting then re flashing twrp?
Sent from my liquid smooth t989
Click to expand...
Click to collapse
Yeah I tried re rooting using odin back to ICS with no luck. I tried unrooting using odin as well that would put me back to gingerbread. I have tried just about everything I can think of. My next option to try is pushing files through adb.
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Luthien1 said:
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Click to expand...
Click to collapse
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
lordcheeto03 said:
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
Click to expand...
Click to collapse
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Luthien1 said:
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Click to expand...
Click to collapse
It says E: error when you try to make a backup as well?
lordcheeto03 said:
It says E: error when you try to make a backup as well?
Click to expand...
Click to collapse
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
this is so strange, i didnt do anytihng out of the ordinary, i got root by chainfire, then installed goo manager, and then a custom kernel...the most viewed one right now, so i thought it was legit which im sure it is, then a rom..... to end the madness, then i keep getting errors, its so frustrating
Luthien1 said:
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
Click to expand...
Click to collapse
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
lordcheeto03 said:
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
Click to expand...
Click to collapse
i did i tried flashing jedi rom and that failed too, soo this is just weird
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Luthien1 said:
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Click to expand...
Click to collapse
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
now it says E cant open/sdcard/o/download/jedi(bad)
Luthien1 said:
now it says E cant open/sdcard/o/download/jedi(bad)
Click to expand...
Click to collapse
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
lordcheeto03 said:
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
Click to expand...
Click to collapse
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Luthien1 said:
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Click to expand...
Click to collapse
Slow down, re-group, you are NOT going to brick...
First off, lets try some things, my first would be try a different recovery, copy a rom you want to the internal sdcard, then try. Bet it works.
I had a issue like this also, day 2 of my g4, pull the battery for 5-10 min, it seems the recovery gets confused and it will error.
another item to try...check to make sure the md5 file size is correct. common mistake, people for get to do a check.
try these, if you have the same issues, odin back to stock and start over.
Good luck. Your welcome.
lordcheeto03 said:
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
Click to expand...
Click to collapse
Probably this...and a formatting of the internal storage couldn't hurt either to make sure everything is cleared out.
Hey I had same problem. Download through Firefox not reg browser. And for infamous use the last download link
Goomanger gave me 3 bad downloads. To test this theory try and open the zip through a file manager, it probably won't let you because of bad download.. Happened to me 4 times but stopped using stock browser to download those files and has been working ever since
Sent from my SGH-M919 using XDA Premium HD app
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
Also if you can't flash most things from more than 1 recovery still(happened to me when first got my gs4) I did Odin again but used 2.5.0.2 twrp and everything fixed as well. I recently was having the problem you have now and my first suggestion fixed it
Sent from my SGH-M919 using XDA Premium HD app
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Luthien1 said:
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Click to expand...
Click to collapse
Might want to thank people for the effort...there is a thanks button
get into recovery now, and do a factory reset, flash the correct kernel for your device, it will boot.
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium