Develop Bugs

Stuck on Huawei Logo (TWRP 2.7.1.0 + Omni 4.4.4.))

Hello,
I would like to ask you to give me an advice to solve my problem.
Where I was:
1. Ascend P6 with TWRP 2.7.0.0 and OmniROM 4.4.3. Phone was functional.
What I have done:
1. In TWRP I flashed TWRP 2.7.1.0 zip - it went OK, no errors etc. Reboot. System was OK.
2. Turned off mobile and again booted into TWRP (it showed as I expected 2.7.1.0).
3. Then I tried to install new OmniRom 4.4.4. - I followed the instructions in the thread how to install it (not just update!). Everything seems to be OK. Then wipe cache/dalvik. Tried to reboot, but mobile "told" me, that it is not rooted and asked me, if I want to root it. I confirmed it, but right after I made the confirmation, mobile rebooted.
4. Mobile stuck on Huawei Ascend logo.
What I can I do now:
1. I am able to boot into TWRP 2.7.1.0. I have omni 4.4.4, Gapps 4.4.2 and SuperSu 2.00 on my external SD card. I tried to wipe and install the ROM 2 or 3 times, but everytime the result is the same - instalation is succesfull, reboot and mobile will stuck on Ascend logo.
2. adb shows device offline. When I connect the phone to PC while beeing in TWRP, adb shows "device recovery"
I have no idea what is the cause of this problem - propably I shouldnt update TWRP to 2.7.1.0 version through flashing the .zip file, I dont know ....
Any suggestions?
p.s. sorry for the english

krizko1979 said:
Hello,
I would like to ask you to give me an advice to solve my problem.
Where I was:
1. Ascend P6 with TWRP 2.7.0.0 and OmniROM 4.4.3. Phone was functional.
What I have done:
1. In TWRP I flashed TWRP 2.7.1.0 zip - it went OK, no errors etc. Reboot. System was OK.
2. Turned off mobile and again booted into TWRP (it showed as I expected 2.7.1.0).
3. Then I tried to install new OmniRom 4.4.4. - I followed the instructions in the thread how to install it (not just update!). Everything seems to be OK. Then wipe cache/dalvik. Tried to reboot, but mobile "told" me, that it is not rooted and asked me, if I want to root it. I confirmed it, but right after I made the confirmation, mobile rebooted.
4. Mobile stuck on Huawei Ascend logo.
What I can I do now:
1. I am able to boot into TWRP 2.7.1.0. I have omni 4.4.4, Gapps 4.4.2 and SuperSu 2.00 on my external SD card. I tried to wipe and install the ROM 2 or 3 times, but everytime the result is the same - instalation is succesfull, reboot and mobile will stuck on Ascend logo.
2. adb shows device offline. When I connect the phone to PC while beeing in TWRP, adb shows "device recovery"
I have no idea what is the cause of this problem - propably I shouldnt update TWRP to 2.7.1.0 version through flashing the .zip file, I dont know ....
Any suggestions?
p.s. sorry for the english
Click to expand...
Click to collapse
I'm having the exact same problem... Trying everything as we speak...

Whookid said:
I'm having the exact same problem... Trying everything as we speak...
Click to expand...
Click to collapse
I cant even boot in TWRP.. the logo of TW flashes from time to time but cant go in.. any suggestions?

Here's what I did to fix my issue:
- Restored original B510 recovery (flash recovery.img and boot.img from the original B510 rom, it's inside the TWRP thread...)
- Added the B132 update to my external SD card. (Create a folder /dload/ and add the UPDATE.APP file to it)
- Started the phone in recovery mode by by pressing volume up + volume down + power
- Updated to B510 again via update.zip in the /dload/ folder
After that I did not install TWRP or any other custom rom as B510 is the perfect ROM for me atm anyway...

[Q] How should I go about unbricking my friends phone?

Hello, my friend has a Ace 2 (GT-I8160) and he wanted me to try and install CM 11 on his phone. I managed to root it and install temporary CWM on it, however his version of CWM could not flash CM 11 ROM's because it was outdated. I Googled around and found a TWRP .img file that I decided to flash via ODIN (CWM couldn't flash any TWRP .zip files for some reason). Everything went perfectly fine with ODIN, however my friends phone could not go pass the Samsung logo, it would appear for a few seconds and then the screen would go black. He also couldn't go into recovery but he could go into Download mode. Thinking that it was a recovery problem, I managed to get a .img file of TWRP 2.8.6.0 by Chronomonochrome and flash that via ODIN. Still the same problem - phone won't go pass the logo, however it can go into recovery.
So, now the phone boots perfectly to Download mode and recovery - and it can do everything from the recovery, like making backups, wiping, etc, but it cannot boot to the OS itself. I still haven't flashed a custom ROM on his phone because he didn't have the ROM file on his phone at the time nor could be transfer it to his phone via his PC because of some driver issue.
I'm currently downloading I8160XXBN1 firmware from Samsung Updates to flash via ODIN and try to get his phone back into working state. However, I also planned on placing my SD Card (which has the CM rom and Gapps on it) into his phone and flashing a new, custom ROM instead of flashing the firmware.
Does anyone have any advice on what I should do? Should I flash official firmware via ODIN or just flash the ROM using the recovery?
Thanks in advance.

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?

[SM-P607] TWRP install issue (recovery boot loop)

Hi all, looking for some help here.
I picked up a pair of P607's to install Lineage on.
1. I flashed (via ODIN) the latest Samsung factory build from Sam Mobile (Now running 5.1.1).
2. Grabbed the latest TWRP tar file (twrp-3.1.1-0-lt03ltexx.img.tar)
3. Flashed TWRP via ODIN (AP button, selected the twrp tar, unchecked auto-reboot)
4. Held power button and turned off.
5. Powered back on and Held the [home - vol up - pwr] to boot into recovery to check TWRP.... and..... Recovery Boot Loop.
Odly enough, if I get it back into download mode and just boot it normally, it will boot fine back into the OS (stock rom, not lineage yet)
I can recover back to the factory by re-flashing the stock rom again, so it's recoverable.
I've tried with two different 3.1 TWRP versions now, twrp-3.1.0-0-lt03ltexx.img.tar and twrp-3.1.1-0-lt03ltexx.img.tar, both do the same thing.
Any ideas on this one?

There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?

how did you get out of the boot loop? i cant seem to get back in to download mode

XnoteX said:
how did you get out of the boot loop? i cant seem to get back in to download mode
Click to expand...
Click to collapse
Today I got the same bootloop problem.
Impossible to enter the Download-Mode.
I removed carefully the Backcover and disconnect the battery plug for some seconds.
On the next start I´m holding down Vol- and entered Download Mode.
With Odin I flashed TWRP 3.0.2.0 (same version like before) and its working again without loosing the installed programs.
I think you can also wait until the battery is empty .....
Hope it helps a bit to recover a great tablet.

sillysuliman said:
There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?
Click to expand...
Click to collapse
Most ROMs here install fine with 3.0.2. That's what I am using on my 607T.

S4 Mini Softbrick

First time flashing ROMs, installed resurrection remix tryed to install Gapps which failed, yet RR booted up on its own just fine. Then tried to flash a new recovery on it (TWRP 3.0) yet the phone would just never boot up to complete the recovery install. So now i have a phone which wont enter recovery mode and cannot complete the download of the new recovery.
TLDR: Phone wont boot into recovery as ROM is broken so download cant be fixed?
Previous: recovery TWRP 2.6
Phone: Samsung Galaxy S4 GT-19195
Any help would be really appreciated!
Thanks

Are you sure that you have flashed the right Recovery for your Phone.
Normally the way is.
Boot into Recovery
Install the Recovery .zip file
Reboot into Recovery.
Reboot into System ( ROM )
Can you post a link where you download the Recovery and which file.

bierma32 said:
Are you sure that you have flashed the right Recovery for your Phone.
Normally the way is.
Boot into Recovery
Install the Recovery .zip file
Reboot into Recovery.
Reboot into System ( ROM )
Can you post a link where you download the Recovery and which file.
Click to expand...
Click to collapse
That would only work from TWRP ver 2.8.4, I think you missed he is still on very old TWRP or maybe he edit later , he would have to install with Odin method
@Spec77
If you can boot into download mode you should be able to flash new recovery with Odin method (NOT use zip file).
As Bierma suggests maybe you flashed wrong TWRP does your phone have another letter and after gt-19195 if so it is a different phone & you need different TWRP. Or maybe you just tapped wrong link.

IronRoo said:
That would only work from TWRP ver 2.8.4, I think you missed he is still on very old TWRP or maybe he edit later , he would have to install with Odin method
@Spec77
If you can boot into download mode you should be able to flash new recovery with Odin method (NOT use zip file).
As Bierma suggests maybe you flashed wrong TWRP does your phone have another letter and after gt-19195 if so it is a different phone & you need different TWRP. Or maybe you just tapped wrong link.
Click to expand...
Click to collapse
This way works also if you come from a CWM or PhilzTouch Version.
If you come from TWRP =>2.8.4.0 than you can flash an *.IMG File ,but you can flash on all Versions a *.zip file.

Managed to fix the brick
Thanks for the help, I managed to fix it by installing TRWP 3.0 from ODIN, and now that i have that I'm fine
Thanks!