Develop Bugs

[Q] Messed up somewhere along the line...

Tried to flash my AT&T Samsung Galaxy SIII to CM10.1.3-RC2-d2att.zip
(along with gapps-jb-20130813-signed.zip) using TWRP v2.6.1.0
Messed up when I... deleted everything of my phone while wiping.
No more restore points, no rom to load, no gapps. Nothing.
Used a friends SD card and moved the files over to try on the TWRP left on my phone & end up with
set_perm: some changes failed
E: Error executing updater binary in zip '/extern
Error flashing zip '/external_sd/New folder/cm1
Updating partition details
Failed
tl;dr had everything ready to flash my rom, ended up wiping everything. Left with a useless hunk of a phone doing nothing but TWRP :crying:

I would suggest you install stock ROM through Odin.
Here is the link with everything needed
http://forum.xda-developers.com/showthread.php?p=39152518
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[T311] Unable to install stock firmware after installing cm12

I install cm12 on my tab but before I had taken the nandorid backup
And I have done this so many time "installed cm12" again revert back to "stock 4.4.2 using backup" again and again in last 2 months like(~ 20 times)
But now dont now what happend whenever I restore in twrp it it gives an error
(20mb) <some path >recovery.Img.win size is larger than <some path>mpblock(8mb)
(something like this error)
Then I try with Odin its also giving me error when it trying to flash recovery.IMG and am getting fail msg every time
Someone please help me out

hardythaker said:
I install cm12 on my tab but before I had taken the nandorid backup
And I have done this so many time "installed cm12" again revert back to "stock 4.4.2 using backup" again and again in last 2 months like(~ 20 times)
But now dont now what happend whenever I restore in twrp it it gives an error
(20mb) <some path >recovery.Img.win size is larger than <some path>mpblock(8mb)
(something like this error)
Then I try with Odin its also giving me error when it trying to flash recovery.IMG and am getting fail msg every time
Someone please help me out
Click to expand...
Click to collapse
There is no reason to ever include recovery in your backup. Do a restore and uncheck the recovery option.

Need help recovering from bad flash

I was attempting to change my Galaxy Nexus from Cyanogenmod 10.2.1 to cm 11 (current stable release). So, I did the following:
Created a Nandroid backup, saved it to my laptop, and deleted it from my phone as after creating the backup I had almost no free space. Before deleting it, I did test it and confirm that it worked.
Downloaded the CM ROM and gapps from the CM website
Verified their hashes.
Copied them to /sdcard. I didn't think to verify their hashes again. This may well have been a mistake.
Used TWRP v2.6.3.0 to wipe the phone and attempt to install CM. A message appears: "Failed." Here's a sample output (note that the output falls off the right-hand edge of the screen and there seems to be no way to scroll it to make it readable):
Code:
Updating partition details...
Installing '/sdcard/cm-11-20150626-SNAPSHOT-XNG3
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Updating partition details...
At this point, the phone won't boot. It goes directly to recovery.
To recover, I thought I'd just copy over my Nandroid backup. But, I can't use adb in recovery. I tried to use fastboot to flash my nandroid backup, but the format seems to be different, and I wound up with a phone that, when attempting normal boot, gets stuck on the Google logo until I remove the battery. I do have access to recovery still.
How can I get something bootable on my phone? I just want to restore my Nandroid backup. (And maybe see if I can figure out why CM-11 didn't work.) I can't find any way to copy arbitrary files to my phone.

Solved
This guide enabled me to resolve my issue. The steps I took:
Downloaded the latest stock ROM for my phone
used fastboot to flash it following the instructions on the linked post (which involved unzipping things and whatnot)
Booted into the new system and restored /sdcard from backup
Copied the latest Nandroid backup to /sdcard
Restored the Nandroid backup
Tried to install CM 11 again (this time without deleting the backup from my phone). It failed, so I restored again and am giving up for now.

Bootloop after OTA Update

I have an ASUS ZenFone 2 (550 model), and I got a Push Notification about an OS Update, so I went ahead and installed it. After the phone installed the Update and rebooted, I got in a Bootloop. I can get into the Bootloader, the Stock Recovery, and the Temporary ClockworkMod Recovery mentioned here:
Code:
http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063
ADB also works, thankfully.
My phone is rooted, and I'd like to unlock my Bootloader, and install CyanogenMod, after I get out of this Bootloop.
Could someone please help?
EDIT:
Silly me, I forgot to mention the problems I actually had while trying t solve the bootloop.
So,
Problem #1: If I try to flash Firmware, the stock Recovery stops at 25% (It continues going until 50% in ADB), and then i get this error:
"E: failed to verify whole-file signature
E: signature vertification failed"
Problem #2: CWM cannot use my MicroSD. If I go to "Install zip from sd card", it doesn't show the actual SD card, jus three empty folders. I tried to mount "ext-sd" in the mounting options, but it fails to mount. (My MicroSD is 32GBs and formatted in Fat32, so it should work. :/ )

Tab310 8" stuck at Samsung splash screen

I can get into custom recovery and wipe data and install custom rom, have tried different roms, all of them get to "verifying update package" then gets error something about signature failed, then it tries to start and just gets to the splash screen. I have tried it several times with 3 different roms. Running latest TWRP, and wiped data multiple times each time.

dh419 said:
I can get into custom recovery and wipe data and install custom rom, have tried different roms, all of them get to "verifying update package" then gets error something about signature failed, then it tries to start and just gets to the splash screen. I have tried it several times with 3 different roms. Running latest TWRP, and wiped data multiple times each time.
Click to expand...
Click to collapse
It sounds like either your twrp or the ROM, could be for a different device. Another possibility is that the ROM might have a getvar line at the top of the updater script. This calls on the build.prop to check to see if the device is correct for the ROM. However, if you have accidentally wiped your system partition, the build.prop won't be there to check and will automatically fail.
Sent from my KYOCERA-C6745 using Tapatalk

I think all files are correct for my tab, maybe I did wipe system partition, how would I tell or fix that?

I downloaded TWRP again and installed with Odin and when I start it in TWRP, and hit install, try to select SD card, it will not let me. The same thing the first time. The first time i tried Odin to install Rom, then after that each time I got into TWRP it looked different and I could install from SD card, but got the error. Not sure what to do this time.

I got it, had to use my SD card as an external drive, and TWRP read it, and installed the rom with no problem. My problem was for some reason, when I went into TWRP it would not read the SD card for the install, it showed 0 mb and would not let me select it, but did using USB drive.