Develop Bugs

Phone stuck on htc screen =[

hey everyone,
So i just rooted my phone using the wiki cyanogen mod, and everything worked great... afterwards I downloaded rom manager and used this method here
http://wiki.cyanogenmod.com/wiki/HTC_Vision:_Radio_and_CyanogenMod
Method via ROM Manager
Launch RomManager.
Optional: Choose the first option in the app, Flash ClockworkMod Recovery to update to the latest version.
Select the Download ROM option from the main menu in the ROM Manager.
Select the CyanogenMod option, and then choose the latest version of CyanogenMod from the menu.
Optional: When you select the latest version of CyanogenMod, check the Google Apps* option.
Once the ROM is finished downloading, it asks if you would like to Backup Existing ROM and Wipe Data and Cache.
If Superuser prompts for root permissions check to Remember and then Allow.
The HTC Vision will now reboot into the recovery, wipe data and cache, and then install CyanogenMod. When it's finished installing it will reboot into CyanogenMod.
----------
After this the phone rebooted and now it's been stuck on the white htc screen... I'm completely clueless on what to do now.. any help would be great thank you guys

So did you flash a 5.x.x.x recovery from ROM manager? People are having issues with this.
Pull the battery and try booting up again. If this happened on your first attempt (aka it hasnt actually wiped or anything) just go back to your ROM, and flash a previous CWM recovery. 3.0.2.4 works. THEN try to do the process.
All ROM manager is doing here is automating a process you can do yourself. I'm assuming what happened is you're having a problem with the new recovery when it reboots to go to the recovery, it hangs on HTC screen. ROM manager and CWM haven't even had a chance to do anything yet.
Another option is to pull the battery and boot with vol. down + power, then enter recovery. See if it enters. If it does, then you can reboot and run the install from ROM manager and it should work this time. You could also do it manually at that point if you wanted.
For me (and many others) when using a 5.x.x.x CWM recovery, the first boot always hangs at the HTC logo, and after a battery pull and a 2nd attempt to boot into recovery, it works.

if i was at your position and cwm is installed, by look at your post it is installed.
i pull battery out and put it back in. turn on your phone whilst holding volume down.
it will scan for pc10img if there's any dont install it...
then there should be an option for recovery, use the volume rocker to navigate gate and your on button to select.
your phone will restart and hopefully load cwm manager.
if you've got there then you can wipe data and cache then install a different ROM or another cyanmod rom.

thank you guys for all the help! it was much needed, I have successfully rooted my phone and I have cyanmod 7, i'm so glad i didn't brick my phone hahah

Gratulations

[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

Stuck at boot loop. White Amazon Logo

Hi guys,
I was in the final step (7) of this gude: http://www.aftvnews.com/start/
Which is installing the latest pre-rooted stock software, (version 51.1.4.1_514013920) After pushing the rom to /sdcard, I rebooted the device so that I could flash it via clockworkmod recovery, but I was not able to select the recovery option with my keyboard. So I decided to re-do the installation of Rbox's kernel boot menu. Now, I'm stuck at a boot loop with just the white Amazon logo showing up. Is my device bricked and is there a way to fix it?

FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?

Newbie_from_NJ said:
FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?
Click to expand...
Click to collapse
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!

KLit75 said:
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!
Click to expand...
Click to collapse
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.

In hindsight, now that I've reviewed each step, what I should have done was flashed Pre-Rooted Stock ROM version 51.1.4.0_514006420 AGAIN via Clockworkmod recovery in order to properly uninstall the kernel boot menu. Then I should have tried re-installing the kernel boot loader again. Lesson learned.

Newbie_from_NJ said:
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.
Click to expand...
Click to collapse
Then I don't know...I always double or triple check to make sure but your steps seem correct. Was this a new box? I only say that because I remember that super tedious process and at one point I think I needed to root again. At that point it maybe possible an update could sneak through but that would probably result in losing root--worst case. Not a brick.
It's concerning because you seem to know what you're doing and were cautious during the process.
Hopefully someone else can confirm where you went wrong. If you didn't go wrong then that might be a bigger problem. Everything went smoothly up until it hung at boot?

As they always say, if your in a jam and get "failed" messages when writing to boot or recovery or flashing, do not reboot. keep trying till you get no errors. that said, I thought I was stuck in a boot loop cause I insalled the llama and xbmc launcher and removed the launcher app. I was still able to get through adb but it took like 5 or 6 reboot tries. good luck.

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?

flashed supersu in twrp, but phone doesnot boot.

i flashed supersu in twrp and now the phone gets stuck at "your android has been unlocked" screen.
my android is 7.1.1

You mean the system will boot in 5 seconds screen?
Here are a few things you can do, try them one by one and in order.
- Reboot and immediately press power to let it boot in system.
- Go to recovery. Wipe > Format data (like you did after installing recovery) try to reboot and see if you can boot in the system.
- If you are or want to install a custom ROM then at recovery wipe data and flash a custom ROM and install from recovery.
If above doesn't make sense or doesn't work at all then Flash Stock, which is very very easy.
Download factory image and follow instructions here https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
https://forum.xda-developers.com/nextbit-robin/help/unbrick-tool-mac-windows-t3400860
P.S. : I personally use and prefer Magisk over SuperSu and it works fine.