Alright, so last night I saw that the CM nightly build had been working for others so I decided to try it. I wiped and flashed but got a boot loop. I went back to recovery to try to wipe and reflash but the flash failed halfway through. I go to hboot and see that I'm back to S-ON... So now I'm stuck with a phone that won't boot, won't let me flash a rom in recovery, and won't even let me install the stock rom with hboot. I spent about 4 hours on it last night messing around with fastboot and trying apache14's OTA rollback method but was never able to get it to work. The adb shell won't recognize that I have the edited misc.img on my sd, even with a newly formatted card with no other data. Before anyone states the obvious, I was using the first version of the G2 clockwork mod, and if there was an option for a backup in there, I didn't see it anywhere. Any help is appreciated. Thanks in advance.
man i've been trying to help someone in a similar spot for 2 days now. so do u still have a custom recovery on there now?
so hboot recognizes the stock rom? what exactly happens when you try to flash it?
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
thenpaxtongoes said:
Yeah I managed to get a newer clockwork on here. Turns out a friend of mine just bought a G2 so I'm going to attempt to make a nandroid backup of his and apply it to mine. Think that will work?
It recognizes it, but just says "Main version is older! Update fail!" after it scans the image. I assume that's because I had the ota applied before I flashed the cm rom.
Click to expand...
Click to collapse
you should be able to just flash a rom in recovery. do full wipe then apply one of these roms:
mine: http://forum.xda-developers.com/showthread.php?t=836042
pauls: http://forum.xda-developers.com/showthread.php?t=836784
btw-your alot better off then the guy im trying to help
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
thenpaxtongoes said:
Alright, I'm downloading it. I don't see why this would work when the desire rom and CM roms didn't but it's definitely worth a try. Thank you for the help. I'll post my results in a minute.
Edit: Nope
It starts to install and then:
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
E:
"system" wipe failed!
E: can't format system:
E: Failure at line 6
format System:
installation aborted
Click to expand...
Click to collapse
hmm thats a little more info then u gave last time. which rom did u try?
Your odex rom. And I actually tried Paul's rom last night with the same results. I have to go to work right now so there's not much else I can do but I appreciate the help. I'm really banking on the nandroid restore of my friend's g2 backup working but we'll see what happens.
I had this happen to me also. Since you have clockwork recovery installed, you should be able to use the instructions in this post using adb while in recovery mode:
forum.xda-developers.com/showthread.php?t=831398
The only change you'll have to make is you need to mount the sdcard in order to follow the instructions.
mount -o rw -t vfat /dev/block/mmcblk1p1 /sdcard
/cache also has available space so you might be able to use that without mounting /sdcard.
Hope this helps!
remember that in his first post he said that the phone has reverted to s-on. you've tried the original unrooted stock ROM? because with s-on I don't think you'll be able to flash any of pre-rooted ROM.
Mine had clockwork installed when I tried to install the signed ship rom in order to revert back to stock so I was s-on also. It appears that mmcblk0p17 was not WP in clockwork recover in my case, so I was able to dd the modified image to that partition through adb and then the shipped rom was able to flash normally.
Thank you again for all your help guys, but the nandroid backup worked. Though I am stuck on baconbits and my wifi card is not working at the moment all I need to do is follow the unroot instructions and i'll be fine. I hope...
Sent from my T-Mobile G2 using XDA App
Related
Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel
N_Jones said:
Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel
Click to expand...
Click to collapse
After flashing rom. Reboot. It will then install the RADIO. Radio installation requires one more extra step after flashing. Once thats done. Load into Android. Then go back in recovery then flash the WIMAX.
+1 the above I use Ra and flashed both just fine.
My Evo starts to boot then hangs on the white htc EVO 4G screen for all eternity! I nandroid restored all the way to day one of my root, I get an error and it aborts restoring or flashing. What do I do? The last Thing I did was flash a kernal that this rooting method put in my SD card, now all I can do is stare at a white screen or play around in recovery
Specific Errors:
When flashing a Rom/Kernal
Code:
Writing BOOT:...
E: No space left on device
E: Writing BOOT:
E: FAilre at line 7:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
or
Code:
Copying files..
E: Can't symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
When restoring a nandroid backup:
Code:
Restoring boot image...
Error while flashing boot image!
I've tried flashing a few kernals and plenty of roms, same errors EVERY time! I really want to know why restoring a nandorid backup doesnt even help
::::::::HIGH PRIORITY:::::
I also saw something about another guy who had problems on his moto droid then flashed an update.zip and was fine, any evo update.zip's out there you can give me a link to? If tis will fix it then at least I'll be able to use my phone!
Googled for update.zips for the Evo, the only one I found was on geekfor.me and it got removed
you will have to restore your evo back to stock and then re root....this is how you do it:
download the 3.30 release from this site and put in root of sd card http://shipped-roms.com/index.php?ca...del=Supersonic
in order for your phone to see this ..boot into bootloader..when phone is off, hold the volume button down and then hold the power button...the phone will see it and flash and update it...you will be back to stock and not rooted...you will have to re root the phone and then create a nandroid...
read this for more info on nandroid backup http://www.simplemobilereview.com/an...ndroid-backup/
once you are back to stock, check to see what hboot version you have...this will determine the root method you have to use to re root it...i would not use the root method you did in the first post...there are other methods that are more reliable...if you are hboot 2.02 or 2.10, follow this method... http://forum.xda-developers.com/showthread.php?t=829045
if you are a different hboot like .76 or something else..you can use the unrevoked 3.2.1 method
good luck
whoa whoa whoa ... put a exe in the root of my sd card? I did that, held the vol (down) button, and it booted into bootloader and did nothing special. Just sat there idle. I rebooted the phone and it still hung on the white screen
And my phone cant fully boot so running that wont help at all...
U need to click the up volume to flash image once the check runs....this works, I walked one other person through it and have done it to my brothers phone
Sent from my PC36100 using XDA App
I put
RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed (1)
in my sd card, booted into the bootloader with volup+power, and it did nothing. Rebooted phone and it just hung on the evo screen
Try running the ruu using htc sync
Sent from my PC36100 using XDA App
When you put the ruu on the zip card, did u rename the file to pc36100 ? U need to do that bc that is what the evo reads to get it to flash
Sent from my PC36100 using XDA App
Rename a .exe to pc36100? How does android use a .exe?! I"m afradi this will jsut 100% bork my phone
http://forum.xda-developers.com/showthread.php?t=888481
read that thread please...i explained the same thing to a different member and he did it and it worked...I am not a newb and am not trying to screw your phone.
here is a different link to the newest 3.70 update....flash that and you will be good to go
http://www.megaupload.com/?d=D454VSVN
weaselp1 said:
http://forum.xda-developers.com/showthread.php?t=888481
read that thread please...i explained the same thing to a different member and he did it and it worked...I am not a newb and am not trying to screw your phone.
here is a different link to the newest 3.70 update....flash that and you will be good to go
http://www.megaupload.com/?d=D454VSVN[/QUdo you have a link for 3.30 cause 3.70 doesnt work for me
Click to expand...
Click to collapse
3.30... http://forum.xda-developers.com/showthread.php?t=819771
The kernel you flashed was the stock htc #17 as noted in the post. This is a kernel custom made for our phones so it will not work with google android builds.
You will need to wipe data/cache/dalvik and then restore to a nandroid that you made after you finished rooting. The only real purpose for that initial nandroid is to save your wimax partition since your phone was not usable when that was made.
Sent from my PC36100 using XDA App
I'm fairly new to rooting and flashing, but I can figure things out usually after a bit of research. This has me completely stumped though because I have no idea what to attribute my problem to:
I rooted my Evo a few weeks ago and flashed CM7. The problems I had after flashing CM7 was my GPS and I had 1x instead of 3G. Note: I have also updated my CM7 with the recent updates.
I researched some fixes for the GPS/1x issue, which meant I needed to flash to a sense-based rom. I tried flashing a sense-based rom (several different ones) on several occasions via Clockwork/Rom Manager and I had no luck- it would just reboot to the white screen over and over.
The problem I'd like to resolve in this thread is how to figure out why I am unable to flash to *any* rom. I just attempted flashing KingsRom (via Rom Manager) and everything seemed to be going quite well until the very end where it scrolled so fast I could barely catch what the error was- and it seemed to be something with the "boot image."
Side note: During one of my previous attempts at flashing a different rom, which of course was unsuccessful, I was unable to flash a restore of my CM7 backup and I received this error: "error while flashing to boot image." However after just going at it over and over again I managed to flash a fresh CM7
I'd really appreciate any help as it seems a simple flash is giving me a lot of trouble. If any details about my phone are needed to help resolve this please let me know (I don't know what would be necessary to post).
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
plainjane said:
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
+1 on what Jane said. You can use rom manager to flash RA recovery (alternate recovery) but don't use it for flashing roms. Just wipe like she said and flash the zip manually through RA.
Sent from "The EVO" using XDA Premium
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
subjectdelta said:
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
Click to expand...
Click to collapse
Are you wiping fully between installs? It seems like your boot partition may be corrupt... or getting there, if that's possible. Try wiping everything, boot included, and flashing again. The only other thing I can think to do is unroot & go back to stock, then reroot & try again...?
Hi everyone... I have been doing a bit of searching with no luck so far. And I searched a lot but no luck in finding my stituation and don't want to screw up the phone completely...
I bought a D-Z used, Bell Rom. It showed to be S-Off, but when i checked to see if it was rooted with RootCheck, it said it wasn't. So I started the process of applying Visionary for Temprooting and then on terminal emulator, I got the error: exec format error...and, stupid me, decided to keep going. I followed the rest of the process, up to step 10 on http://theunlockr.com/2010/11/30/how...g2-htc-vision/.
But when i turned phone back on, it got stuck on the white screen with the green htc logo....
If I vol-down/turn on, i see:
Vision PVT ENG S-OFF
HBOOT-076.2000 (PC1012000)
MICROP-0425
RADIO-26.03.20.26_M
eMMC-boot
Aug 20 2010,16:51:01
HBOOT and the options:
FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK, SYSTEM INFO, IMAGE CRC
On system info it says
OS Ver.-1.34.666.5
When I put the battery in it, plugged into charger, it goes into ClockworkMod Recovery v3.0.0.5 and below the menu it says:
ClockworkRecovery v3.0.0.5
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
the phone says S-off: should I just copy some rom and launch the flashing? If so, a zip to the SD card is the way to go, right?
Or is something bad and should I attempt first loading a stock rom? (I guess not, because it says S-Off!).
It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App
heybobitsme said:
It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
lucky you! - someone before you S-OFFed the phone!
read the stikies next time. http://forum.xda-developers.com/showthread.php?t=1025135
santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
first, download any untouched flashable sense rom (make sure it's not a full rom with hboot, radio etc, just /system)
place the rom.zip on your sd card
reboot with vol down
choose recovery
wipe cache and wipe data/factory reset
choose install zip form sd (not update), then select the zip and press trackpad
hopefully this is all you will have to do to make the phone functional again
here is a flashable rooted /system from a stock sense rom: http://forum.xda-developers.com/showthread.php?t=1012763
hope this will help
petarpLab said:
lucky you! - someone before you S-OFFed the phone!
Click to expand...
Click to collapse
thanks for you help. I'm trying it now.
I had tried the other method... but it didn't work out. I should have read more before going for what looked simpler - visionary.
I will report soon. Hopefully, i will have a phone and not a piece of wall...
THANK YOU!!!!! IT WORKED PERFECTLY. I GUESS I CAN NOW GO TO Cyanogen, right?
santiargy said:
at this point, I don't want to screw up anymore...
wipe cache, ok
wipe system? Not an option... got wipe data/factory reset. is that the option? you refer to?
Click to expand...
Click to collapse
yes, do this one.
p.s. sorry for the rant earlier.
Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..
Mkarin said:
Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..
Click to expand...
Click to collapse
this is a G2 rom, not DZ. it's dangerous to mix them if we are talking about full stock roms. bricks happen from such mixes.
santiargy, any success?
ah, i mised a post.
I am really glad to hear it worked.
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