Develop Bugs

[Q] Locked out of my G2

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

[Q] BIG Error installing new JB rom, please HELP

I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.

Did you re download and check md5?

PonsAsinorem said:
Did you re download and check md5?
Click to expand...
Click to collapse
I re downloaded twice. And I thought it always checked md5, it's at least never had a problem when it did..

Hypherism said:
I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.
Click to expand...
Click to collapse
Install from twrp cwm is a broken recovery
Sent from my ADR6300 using Xparent Red Tapatalk 2

Status 7 usually means there is a problem with the updater script in the rom file. What recovery are you using? Try TWRP if thats not what your using. Either the rom developer made an error in the rom zip, or the file is getting corrupted during download.
Also the md5 is not automaticly checked, you must check it your self.

Thanks very much for your assistance fellas. Unfortunately, I have an entirely new problem on mis manos.
So, after the most recent failure of the rom to install, I restored my backup of my RC2 rom.
It wouldn't get past the nexus boot animation. (I waited for 15+ minutes, I don't know why) So I
went back to recovery, and attempted to install RC3 again.
No problems installing. When I booted up however, after it had notified me that it was "Finishing installation" and that Android was "upgrading"
I was met with a plethora of errors. android.process.acore has stopped etc.
So, I ended up doing a factory reset/wiped user data.
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:

cmlusco said:
Also the md5 is not automaticly checked, you must check it your self.
Click to expand...
Click to collapse
Depends on how you get it. If downloaded from the Goo Manager app, the app auto checks md5.
Hypherism said:
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:
Click to expand...
Click to collapse
Good to hear it worked out for you.

Stock Nandroid

I tried to flash to Intergalactic Rom and it failed, so I tried to flash it again, but when I was wiping the files I accidentally wiped my SD card with my nandroid. So does anyone have one they can upload or another idea? Thanks.

CipherC233 said:
I tried to flash to Intergalactic Rom and it failed, so I tried to flash it again, but when I was wiping the files I accidentally wiped my SD card with my nandroid. So does anyone have one they can upload or another idea? Thanks.
Click to expand...
Click to collapse
what was the error message?
if we find your problem is not fixable via flashing a different rom, etc, you could consider downloading and flashing stock firmware in odin and starting over

Reason for most failed installs is outdated recovery or bad download. Just download a ROM again and put it on your ext ad card. Flash an updated recovery in Odinand then flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda premium

Alright, sorry I was in a rush to get back to work.
"assert failed: getprop( … ) == "d2att" E: Error in /emmc/Intergalactic_v2.8.zip "
That is the error that I am getting when I try to flash it. I searched the page and found that the error is because my CWM is out-of-date.
It flashed the second time I tried which is what bricked the phone, so now I can't upgrade my CWM via the two ways that I have found online which both require a working ROM.
If I can flash another ROM with CWM 5.5 that would be great. If anyone knows of a ROM that is compatible please let me know.

CipherC233 said:
Alright, sorry I was in a rush to get back to work.
"assert failed: getprop( … ) == "d2att" E: Error in /emmc/Intergalactic_v2.8.zip "
That is the error that I am getting when I try to flash it. I searched the page and found that the error is because my CWM is out-of-date.
It flashed the second time I tried which is what bricked the phone, so now I can't upgrade my CWM via the two ways that I have found online which both require a working ROM.
If I can flash another ROM with CWM 5.5 that would be great. If anyone knows of a ROM that is compatible please let me know.
Click to expand...
Click to collapse
here's a link to a cwm recovery flashable update. this is cwm 6.0.2.3. should work. flash it in cwm then "reboot recovery"
http://d-h.st/8qP
and if you want to make sure it's done right, here's a compilation of the best way to root/flash/backup your device. stick with these methods and you'll have far fewer problems
http://forum.xda-developers.com/showthread.php?t=2179330

Thanks, but the update was a No-Go. It's giving me the getprop error again. I'll just suck it up and start over.

CipherC233 said:
Thanks, but the update was a No-Go. It's giving me the getprop error again. I'll just suck it up and start over.
Click to expand...
Click to collapse
odin back to stock. here is a link to stock firmware with root already injected. download the correct carrier version and flash in odin. http://forum.xda-developers.com/showthread.php?t=1739426
install rom manager (http://download.clockworkmod.com/recoveries/RomManager.apk). flash recovery via rom manager. i think latest release is 6.0.3.0. make sure rom is still on your phone.
boot into recovery and make a backup before you do anything else.
then wipe data
wipe cache and dalvik
install rom
after successful boot, wait 10 minutes and reboot.
---------- Post added at 11:41 PM ---------- Previous post was at 11:29 PM ----------
While you're back at the beginning, I would take the time to backup your imei/efs stuff. Better safe than sorry. This is a step that many skip.
This is a beginning to end guide
http://forum.xda-developers.com/showthread.php?t=2179330
Cheers

[Q] Cannot flash anything

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

Unable to Install new roms in TWRP

Hello everyone. I tried to wipe my kindle and replace the rom last night but its not letting me install anything. I have been running a version of Smoothrom for months now without any issues. I am giving the kindle to my gf so I wiped it and tried to upgrade to a kitkat rom first. I did a complete wipe of everything then loaded the roms on via usb. Now, when I try to install a new rom I get an error which Ill post below. I am using TWRP 2.5.0.0. I tried loading several different 4.4 roms and they all get the same error:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/AmazonHfk2.8-20131220-Stable-otter.zip
Error flashing zip '/sdcard/AmazonHfk2.8-20131220-Stable-otter.zip
Updating partition details.......
It stays like that. If I try to reset it I get a message saying "Root permissions appear to be lost, fix root permissions now?"
Any ideas would be really appreciated.

SOLVED: I tried a few different Roms and it seems like its just the 4.4 roms that are failing. Im assuming its just my version of TWRP so ill try to update it. Feel free to delete this thread. Sorry for clogging up the forum.