Develop Bugs

Recovery Fail!

So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?

kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!

Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?

Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.

[Q] CWM recovery bootloop and can't get out

The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!

re: boot loop/recovery/rom manager
Jakman85 said:
The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!
Click to expand...
Click to collapse
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
Odin flash the cf-autoroot first.
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Once you are done doing the above you will no longer have bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Also philz touch recovery is not fully compatible with these newer firmwares and roms.
Good luck!

Misterjunky said:
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Odin flash the cf-autoroot first.
Once you are done you will no longer have any bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Good luck!
Click to expand...
Click to collapse
Here is the problem: I cannot get into download mode. I have held volume up+home+power and any combination of buttons and it just keeps trying to boot into a broken recovery. I have also plugged it into my computer and it doesnt communicate to it at all (makes sense, since it never boots into anything). I need to be able to reset my bootloader or force the bootloader into download mode.

Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.

PanchoPlanet said:
Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.
Click to expand...
Click to collapse
I have been trying that all evening! I have been looking up JTAG services and JIGs. I read your comment and said "It can't hurt to give it another go"... and BAM!!! Download Mode! After the 50th time!!! WOOT! Thanks guys!

This is what the Android community is all about.
Your welcome.
Pp.

Stuck on HTC logo(help)

Hello guys,
Just got my m9 a few hours ago, decided to root,s-off etc
Anyway, I did something stupid and Im stuck on the android logo.
Here is what I did.
-I updated the device through the stock recovery, there was another update but I didnt install i.
- unlocked the bootloader, phone rebooted and was working fine
-installed costume recovery(TWRP), I didnt boot into it because there wasnt and option like in the m8 to boot in recovery from bootloader.
-I reset the device and installed the update(stupid move I knew the stock recovery is not there)
- I got into TWRP and the updated failed so I had the SUbinary.zip so I plashed it and decided to reboot
-Here I got a note that theres no OS installed so I installed android Revolution, I placed it in the sdcard prior
- after flashing it I pressed on reboot yet I get no OS installed and now im stuck on the HTC logo.
BTW I can boot into boot loader but it says sd card not mounted (64GB)
Edit:
I entered into recovery, flashed AR again,its installs everything normally but I realized on the installation log last line : set_metadata_recursive: some changes failed
still I get no OS installed
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?

mr.dj26 said:
Hello guys,
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
Click to expand...
Click to collapse
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.

x51 said:
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
Click to expand...
Click to collapse
hey there, thanks for the reply.
I think ill do the s-off first then ill download the RUU like this guy http://forum.xda-developers.com/one-m9/help/tut-ota-successfully-1-32-401-15-to-1-t3091911
i wish i updated before

I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.

thunderwolf333 said:
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
Click to expand...
Click to collapse
Thats good to hear, sometimes TWRP will say that there isn't any OS installed but actually there is just reboot the device.
After updating through the OTA I installed ARHD and I got the same error again with the latest recovery. I think its because when I did wipe the data there root directory is changing make the phone unable to boot or there is a problem with the rom although it flashed before the update.
Here is a fix http://forum.xda-developers.com/one...h-recovery-t3066720/post59934542#post59934542
If it didn't work try to format data in the recovery and reboot. Make sure you have a ROM or back up on an SD card.
Since your phone is running I would suggest you to S-off because from what I understand is RUU (for Europe) will only work with S-off
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
hope this helps others

Messed up the Second version of Pre-Rooted 5.2.1.0 ROM install and need some help

so I decided to install second version of Pre-Rooted 5.2.1.0 ROM and only had a partial boot unlock. I managed to full boot unlock and install clockwork but then I tried to install the prerooted rom but missed the step about not imstalling a prerooted without busybox and bootmenu
Anyway I bricked the device and managed to recover to version 51.1.4.0.
I still have the full boot unlock and it boots into clockwork on startup but I can't root version 51.1.4.0 and can't seem to install a lower firmware version through clock work. I always get "error in update.zip Status 7 installation aborted"
I've tried these guides to put me back to lower stock firmware but no luck.
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
I know you can't root 51.1.4.0. but is there any options if I already have the bootunlock and clockwork still installed.
I'm at my wits end at the moment. Any advice would be appreciated

It sounds like you tried flashing the 5.2.1.0 pre-rooted ROM using ClockworkMod, right? You can't do that. You must first replace ClockworkMod with TWRP and then use TWRP to install the Fire OS 5 per-rooted ROMs (like 5.2.1.0).
I'm not quite sure the damage you've done, so best to see if @rbox will reply.

Yep, I was trying to get to TWRP. I can still sideload apps and have kodi all working again but running off a SMB share now. No Usb access without the root.. So not all lost I guess. SMB share seems to work well on a wifi network

Unable to recover OxygenOS on Oneplus3

Hello everyone,
This morning, I wanted to recover OxygenOS on my Oneplus3. I'm currently running Cyanogenmod 13.
I used the following guide: "[GUIDE] How to Unroot your OnePlus 3 / 3T and go back completely to stock" (Since I'm a newb, I can't post the link. But Google will get you there)
I booted into fastboot, issued the fastboot flash recovery recovery_op3.img and fastboot oem lock commands from my Linux termina, and rebooted in recovery mode.
In recovery mode, I then erased the cache and all that, selected the "Upgrade android from USB" and issued the adb sideload ota.zip command. This is where my problems began.
After running the command, I got the error "error: protocol fault (no status)". I tried to look this error up, but couldn't find useful information.
I started to panic a bit, fearing that my phone would be bricked. However, after booting back into fastboot mode, unlocking OEM, and rebooting, my phone would boot back into Cyanogenmod 13 (A clean install).
So now I don't have a bricked phone. However, I really would like to go back to OxygenOS, so my question is whether anyone knows how to solve my problem.
Summary:
Running Linux (Debian 8) on my PC;
Running Cyanogenmod13 on my Phone;
Want to recover OxygenOS, but adb sideload gave me "error: protocol fault (no status)";
Tried running the adb sideload command as root, however that did not work;
Can still use the Cyanogenmod13.

I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs

Tybalt said:
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for responding.
I forgot to mention that I also tried killing the adb process several times, using the adb kill-server command and by killing the process sending SIGKILL.
Another thing I tried was using another Debian machine, which is my laptop. Still, those things did not solve my issue.

Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.

Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.

null0seven said:
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
Click to expand...
Click to collapse
Thanks for responding.
Since I don't understand everything yet, I will spend this evening looking up everything in detail, before I start giving it another try. Do you perhaps know of a tutorial about this specific situation? I don't want to bother you by questioning everything you stated in your instructions. They seem clear enough to be able to be looked up on Google :laugh:
drmuruga said:
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Click to expand...
Click to collapse
Thanks for responding.
By the steps after "if you want complete stock", do you mean that I should keep the bootloader unlocked, and then perform the same steps as in the tutorial that I used?
EDIT:
@ null0seven: I found these steps online as I was looking up some things you said (I don't have much time since I will celebrate eastern with my family today)
Rooted Users or users with ROMs other than OxygenOS having new bootloader (Official CM 13,CM 13 Based ROMs dated later than 04 June 2016,H2OS Marshmallow)​
Step 1 :- Download the OxygenOS 3.0.2 full zip from the top of the post.
Step 2 :- Boot into TWRP.Wipe Dalvik,System,Data and Cache.After that,flash OxygenOS 3.0.2.
Step 3 :- [OPTIONAL] Flash SuperSU from here :- https://www.androidfilehost.com/?fid=24459283995297946
Step 4 -> Reboot System.
Of course, this is about an old version of OxygenOS. But it looks the same as you said.
I think this, combined with your instructions, will make it a bit clearer. Still one question: What do you mean exactly by flashing?

dvbeck
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733