Develop Bugs

Need HELP with CM10 installation!

so whenever i download the "nightly builds" for d2tmo, i go into clockworkmod recovery.
after i clear the data,cache,etc, i get a error 7 installation aborted.
anyone help with that ?

Boot into your ROM again, download ROM manager, select the T-Mobile Galaxy S3 recovery, let it flash and install from the ROM Mananger app, select reboot into recovery from app the, should boot into recovery, flash CM10, enjoy.

hey its a recover-clockwork.img
how do i flash that ?

What exactly is an image file, the new recovery your flashing, or the version of cmx your trying to install. Have you changed any build.prop files. This could be telling your recovery that your ROM doesn't match the phone.

HazyJMac said:
What exactly is an image file, the new recovery your flashing, or the version of cmx your trying to install. Have you changed any build.prop files. This could be telling your recovery that your ROM doesn't match the phone.
Click to expand...
Click to collapse
i got it haha thanks !

[Q] TWRP not available in recovery

Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock

hefilump said:
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
Click to expand...
Click to collapse
You will see E: Footer errors at stock recovery mode because stock recovery allows only samsung signed archive to sideload.
Or did you mean something different with E: Footer? You sentence is inaccurate.
For stock recovery image, I prepared a patched[/] stock recovery image, which will allow unsigned archives to sideload.

I was actually trying to find out why TWRP recovery is no longer available on my tablet. It was working but since loading a stock rom I no longer get the TWRP recovery only the stock one.
I have tried lots of combinations to try and get TWRP recovery working but nothing appears to work - I just get stock recovery.
I am using:
T700XXU1ANF9_T700BTU1ANG1_BTU stock rom
CF_AutoRoot_Port_T700_BeansTown106.tar.md5 to get root access with Super SU
TWRP 2.7
TWRP Manager from Play store with the recommended Busy Box installed
I am sure I am missing something but cannot see what it is - I obviously got it right before as I had it working but I have missed a step somewhere.

Try using Flashify from the playstore and flash the TWRP .img or .zip
The "dd" method is the most flawless method if your familiar with using terminal
http://teamw.in/project/twrp2/238
Nexus 5 via Tapatalk

Finally got things working. It would appear that it is all about the sequence you do things in.
1. Use odin to load stock rom
2. Set up tablet and let everything download and update
3. Use odin to get root
4. Ensure that root is working and up to date
5. Use odin to add TWRP
6. Install TWRP manager from play store
7. Install Busybox from play store and run installation in busybox
If you deviate from this sequence TWRP does not appear to work in recovery. Have now made successful backup and can start playing with custom roms again.
Thanks for all the advice.

Not to much excitement I hope. Limited to a couple Roms
Nexus 5 via Tapatalk

Just FYI twrp IS recovery, when u restore to stock twrp is overwritten by the stock recovery. Twrp is not overwritten when you flash custom roms because recovery is not packaged in the zip file. But remember stock firmwares overwrite your recovery. Also please remember not to take ota's if you are using a custom recovery like twrp

Cannot install CM11 no matter what

Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.

TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?

Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood

TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?

I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.

[Q] SGH-i747 Installing CustomROM Issues

NOOB ALERT!
I have a samsung sgh-i747 that is still tied to the AT&T network, although, I do not have a SIM or service anymore. (is not being unlocked my issue?) I have been trying install Cyanogen 11 and 10.1. I currently have TWRP recovery, and the phone is definitely rooted. I have followed multiple guides to install a custom OS and nothing has worked. When trying the first time, I get the status 7 error, then I remove the assert check from the script and it still fails. It will sometimes just fail right after it skips the md5 check and not even return an error. What could I be doing wrong?
Possibly relevant info:
- I have CWM recovery that I installed TWRP over(may not be an issue, idk)
- I have tried installing .zip from sdcard and sideloading.
- phone is on stock 4.4.2
- I factory reset and wipe cache and dalvik cache before trying to install ROM.
- I have tried installing on TWRP and CWM.
Any suggestions would be great. I am new to the whole rooting and flashing thing, so I wanna get this done because I am slowly becoming obsessed.
Thanks guys!

Download the latest tar.md5 version of Philz Touch recovery from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download the latest cm11 for the d2lte from here: https://download.cyanogenmod.org/?device=d2lte. Save cm11 to an external SD card.
Download the Gapps from here: http://wiki.cyanogenmod.org/w/Google_Apps. Save the Gapps file to the external SD card. Place the SD card into the phone.
Boot the phone into download mode, uncheck everything in Odin except f.reset time. Connect the phone and flash Philz. When you see the word "reset" in the status window, remove the USB cable, remove the battery, replace the battery, boot into recovery, wipe data, cache, system, and Dalvik. Flash CM11, flash Gapps, boot phone.

Thank you so much. That worked first try. so was it just that I did not have updated recovery?

Yes, status 7 errors are often due to an outdated recovery.
Glad it worked.

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3

@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.

noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.

I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?