Develop Bugs

[Q] Boot Loop

I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.

Try getting into recovery (CMW or Philz touch) and re-flash a ROM?

thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.

Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.

tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?

Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.

tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....

Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium

Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......

bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.

Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......

bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?

That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium

Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!

How to Root from Stock 4.3?

Just picked up a Note II and was shocked to see how difficult it seems to be to root from stock 4.3. Many posts from users who say the stated methods aren't working for them ...
What is the current status on the best way to root from stock 4.3? The Tmobile bloatware is killing me ...
Forgot to say that I don't care about tripping the counter for knox or ota or any of that. Just want to root, get rid of bloatware, be able to use custom rom, etc.

Just use cf auto root

Haints said:
Just picked up a Note II and was shocked to see how difficult it seems to be to root from stock 4.3. Many posts from users who say the stated methods aren't working for them ...
What is the current status on the best way to root from stock 4.3? The Tmobile bloatware is killing me ...
Forgot to say that I don't care about tripping the counter for knox or ota or any of that. Just want to root, get rid of bloatware, be able to use custom rom, etc.
Click to expand...
Click to collapse
Its not difficult. I put this together today for installing note 3 features on T-Mobile Note 2. It's easiest way to do it. You need to learn basics first. So read about what recovery mode is, download mode and what Odin is and how to use it. It's all very easy and if you have TeamSpeak I wouldn't have a problem helping you with it, but you void your warranty and if you brick your phone - oh well, that's the chance you take. I've been doing it for about a month and its fun. Here's my guide. ezKAT rom is fun as hell! Enjoy!
Simplified procedure for installing ezKat custom rom on T-Mobile Note 2 (SGH-T889) ONLY
WHY THIS GUIDE?
#1 – For first time rooters, this is the easiest way to root your phone, period!
#2 - When I followed the original ezKat instructions, things didn’t go smoothly. After some trial and error and quite a bit of searching, this method worked easier, was repeatable, and also added some additional functionality – primarily stability and the ability to install games etc. to external SD Card.
I just put this together to save people time so they don’t have to go through what I did – namely fumbling around and being frustrated. Most of the solutions to problems turned out to be simple if I’d only known where to look the first time around. Unfortunately, it seems information on T-Mobile stuff is always harder to find compared to AT&T or International Note 2’s.
FILES: See the XDA forums ezKat Developer page for links to files and to acknowledge their awesome work. This is the best rom I’ve ever worked with and was well worth a little extra effort to unleash its full potential on my Note 2.
Problems others have reported that this method either avoids or solved for me:
1) No keyboard working
2) “no Sim card inserted” error after install
3) “code 7” error message during rom flashing that “ezKat 2.0 has error” and failed installation, as well as general instability reported by
others in the XDA forums.
4) Inability to install programs to External Micro SD Card
5) No sleep/coma problems
6) Stock browser is included and fully functional.
Last time I’m going to say this – these instructions pertain to the T-MOBILE NOTE 2 SGH-T889 ONLY!! I assume they probably work on the Canadian version too, but I don’t know. Regardless, whatever you choose to do with your phone is your responsibility. Your warranty is void the first time you root your phone regardless – we’re all adults here. Also, this assumes you know what flashing and Odin are… otherwise run away now!! Go read about download mode, recovery mode, and flashing, then come back if you’re not scared away by the prospect of possibly bricking your phone. Still here? Ok then…
Preparation step ONE OF THREE – freshly format your micro sd card (yep, get over it – this solves two major problems up front*)
Preparation step TWO OF THREE – copy these files linked from the ezKat PAGE to your external micro sd card:
-eZKAT_v2.0_n3feat (rom .zip)
-eZKAT_2.0_S5Keyboard (keyboard fix .zip) (do NOT try the “NEW2.0” keyboard file it does not work)
-T889UVUCMK7_Modem-Dec_9_13 (t-mobile modem fix .zip)
-UPDATE-SuperSU-v1.99
Preparation step THREE of THREE: Make sure these are installed to your PC:
-Odin v1.85
-Samsung USB drivers (duh!)
-**Mr. Robinson’s Pre-Rooted Stock 4.3 Rom “root66_TMO_T889UVUCMK7_2.tar” (for flashing with Odin)
-Philz Touchwiz Recovery “philz_touch_6.00.8-t0ltetmo” (Do Not Use TWRP for these steps – I love TWRP, but for some reason – ezKat doesn’t like it)
OK – here we go! Do these in order and you can’t go wrong. Do not skip any steps!!!
1) FLASH MR. ROBINSON’s PRE-ROOTED 4.3 ROM with Odin 1.85 – phone will auto-reboot.
2) Setup Wifi-Settings and shut off phone.
3) Power on phone in Download Mode
4) Flash Philz Touchwiz 6.00.8 with Odin - phone will auto-reboot.
5) Shut off phone and restart in recovery mode.
6) Flash eZKAT_v2.0_n3feat rom in recovery mode (do not reboot yet)
7) Flash Keyboard fix and Modem fix. Reboot phone.
8) Phone should be working – you’re going to be amazed and want to play around – STOP gawking and shut the
phone down!!
9) Boot back into recovery mode – Flash SuperSU 1.99
10) Clear Cache, Clear Dalvik Cache – Reboot phone
11) Download and install BusyBox from Google Playstore
12) Reboot Phone and ENJOY!!
Congratulations. If you don’t care about installing apps etc. to SD CARD, you’re done!! Enjoy your new Note 3 and S5 features on your Note 2.
Make sure to thank the ezKat team for their amazing work on this rom.
If you do want to install apps to External SD Card, then go to Google Play Store and install “NextApp SD Fix” and “FolderMount Premium” (the free version limits you to a very small number of moveable folders) NextApp SD Fix works automatically with two clicks after installation and there is a simple Youtube video showing how to use FolderMount. Again, it is a VERY simple utility to use. Simple click through – it does everything automatically.
NOTE: Contrary to some posts I’ve seen around stating that you can no longer move programs with FolderMount, I tested it again today while editing this guide and it works perfectly with this ROM. I will not attest to any other roms.
*If you didn’t format your Micro SD Card at the beginning of this process then you may have received the “error 7” code during the flashing of the rom. If so, start over.
**Some experienced rooters will choose not to flash over Mr. Robinson’s rom because they normally prefer to flash over a “clean” install base. If you go this route and experience stability or other issues, then I strongly recommend starting from the top with Mr. Robinson’s as a base. I’ve had a lot less issues since going this route.
Good luck everyone! I hope this helped you out.

Thanks to both of you for responding! I'll check out both of the methods you suggested.

Haints said:
Thanks to both of you for responding! I'll check out both of the methods you suggested.
Click to expand...
Click to collapse
You're well welcome. Good luck.

towelroot works on 4.3 for sgs3 so it should work for note 2 also. no pc required

mattlowry said:
towelroot works on 4.3 for sgs3 so it should work for note 2 also. no pc required
Click to expand...
Click to collapse
I tried won't work

terpin32 said:
I tried won't work
Click to expand...
Click to collapse
What error did you get?

It reboots the phone

Just rooted mine finally. Used the autoroot which didn't work and caused the supersu to just close out with knox errors. Then flashed twrp latest 2.7.2 and used it to fix permissions then flash superuser. Booted and it gave knox error, tried opening supersu and it asked if I wanted to try to disable knox. Choose yes, it said successful and Finally im rooted.

[GUIDE] Root, custom recovery and ROMs for JEM [OCTOBER 2017]

My roommate gave me his Kindle 8.9 to play with and root if possible. I had been successful at rooting, flashing TWRP, but couldn't get a custom ROM to flash. Being stupid, I didn't do a test flash first, so I ended up wiping the system and storage, so I couldn't boot into anything aside from TWRP and ADB was unresponsive. It also caused a power error, causing the device to turn back on immediately when powered down.
I acquired two of these tablets from eBay, for $35.00 a Piece, in like-new condition. I replaced the one I broke and bought one for myself. The problem I had was, there is no single guide which 1) lists the current root method for this tablet 2) The files needed to flash a custom recovery once root is gained 3) the most up to date TWRP recovery available. I read a lot of stuff on XDA. I read a lot of stuff elsewhere. The root methods listed in most every thread, no longer root. It was very hard to find an updated TWRP recovery, but thanks to @ong14, who pointed me to a single post, that was possible. So, I created this guide as a single go to for the current methods to root, TWRP and install a custom ROM.
***THIS GUIDE WILL ROOT YOUR DEVICE AND INSTALL A CUSTOM RECOVERY FOR THE AMAZON HD 8.9 JEM TABLET ONLY***
This method is used with ADB which requires Windows. Please make sure the proper drivers are installed before performing these steps. Required files for rooting and custom recovery installation are available at the bottom of this post. Please see respective links for custom ROMs. I did not create any of this software or the files. I'm not responsible if your device is damaged or bricked.
1. Enable the installation of files from unknown sources in Settings > security.
2. Enable ADB debugging from Settings > device.
3. Using the Silk Browser, go to Kingroot.net and download, install and run the APK. Also from Silk, download and install Total Commander File manager and grant it root access. Once you do that, download FireFlash11.apk at the bottom of this post. Open Total Commander and navigate to /sdcard > Downloads. Install FireFlash, open it and grant it root access to use later. (You can locate FireFlash from Home > Apps.)
5. Download the rest of the files at the bottom of this post and place into a folder of your choice on your desktop. Then go here and download this file and this file and place them in that same folder. Then move the following files to your Kindle: freedom-boot-8.4.6, u-boot-prod-8.1.4, stack and kfhd8-twrp-3.0.2-2-recovery.img.
5. Please follow the steps below from @MeowDude which will tell you how to flash a custom recovery to your Kindle.
now if you moved the files straight to your kindle, then they should be on the sd card, if you downloaded these through silk, they'll be in the downloads folder in your sd card. Now open FlashFire11, and give it root access (if you haven't yet). You should be greeted with a somewhat complicated looking wall of text and checkboxes.
!IMPORTANT!
| | |
\/ \/ \/
1. So, let me now guide you through this app, first of all, there should be red print informing you that you're not on the 8.1.4 bootloader or something like that, so click on the checkbox (at the upper right. The one that says "install kfhd8uboot-prod-8.1.4.img or something like that)
2. Now go down, and you'll see some text that says "Boot Partition Image (boot.img) and a box under it that says "NOT FLASHED" tap it. it should bring up a file manager-like list. scroll down until you see your already downloaded "kfhd8freedom-boot-8.4.6.img" , and tap/select it. (I know it says 8.4.6, IT WORKS ON 8.5.1!).
now go slightly under it and check "apply stack override".
*Next, Go under that to find a line that says "Recover Partition Image (Recovery.img), and slightly under it a box that says "NOT FLASHED" tap that, and again, you'll be greeted with a list-like file manager. scroll down until you see "kfhd8-twrp-3.0.2-2-recovery.img" and tap/select it. last part! go slightly under that and tap the check box next to "disable auto recovery update".
*Now that you have all you options in order, verify that you have them in order, and correctly selected (refer back if needed) and scroll down until you see at the bottom, a box that will install/flash all these things, it will say something like "Execute Flash Script" tap it, and your all set. if you want to boot into recovery (immediately after flashing), go right under that box to find another box that says "reboot into recovery" click it, and wait a sec, your screen will black out, and you will first see the normal kindle fire logo, then a blue one, then some glitchy looking stuff, then it should show a TeamWin logo, and go into recovery.
NOTE: If you don't flash your device with android, the stock Amazon os will erase the recovery, so NEVER REBOOT INTO RECOVERY USING FIREFLASH! Only right after you install/re-install recovery.
Click to expand...
Click to collapse
You should boot back to recovery at this point and do a factory reset. Here is how to do that below:
1. Power off your Kindle.
2. Once off, press first and hold the volume down button, then the power button. Hold them both down until the device boots to the BLUE Kindle logo. Then release the power button then the volume down button.
3. You should see the "Team Win" logo come across the screen. Tap on wipe, advanced, and choose dalvik, data and cache. Ten swipe the wipe button. DO NOT SELECT THE SYSTEM OR INTERNAL STORAGE OPTION. This will do a clean install of FireOS 8.5.1 and get rid of Kingroot.
Installing a custom ROM
You can now use FireOS as you were able to before, but I was unable to get the necessary Gapps to work with each other properly. You can try, but I recommend installing a custom ROM. I've tried two so far and can confirm they both work. I will list the links below where you can get the ROMs and installation instructions.
1. The Candy Rom, based off of Lollipop 5.1.1, works on this tablet. Root is built in so you don't need to install or flash SuperSU, but the post does say you can flash it. I've had a lot of trouble with custom 5.1.1 ROMs when it comes to launchers. Be warned it doesn't play nice with Nova and will cause the SystemUI to crash and restart over and over.
2. Unofficial CyanogenMod (CM 13). I currently use this ROM. Root is also built in. I have had trouble getting used to the permissions for apps. I have to go in and set them myself. If you can't get the Google app to sign you in, go to settings > apps > Google App > permissions > grant all permissions. I cannot get Hangouts to work, but the dialer works perfect. I'm not sure if either of those issues are a fault of mine or just a fluke.
I own 3 Amazon tablets: Amazon Fire 7, rooted with a custom ROM. Amazon Fire HD 8, but unfortunately there's no root for it yet. Amazon Kindle Fire HD 8.9, rooted, custom recovery and ROM. I have had great fun 'hacking' these things. I hate FireOS, but I will give Amazon credit for making some really bad ass tablets.

I didn't really feel too happy with the CM 13 ROM. It was pretty sluggish. Just overall performance was less than it should've been. So I decided to try another CM13 (Marshmallow 6.0.1) build by Temasek . This is by far the best ROM I've ever worked with on Kindle (Sorry Fire Nexus). Performance is off the chart. There's little to no lag. You HAVE to flash SuperSu, but it works really well. You don't see the App icon, just tap settings and SuperSU is listed. You also don't need to flash Viper4Android, already comes installed. Just select it in settings, grant it root access and select yes to download the driver. It will take a minute or two for it to update, but reboot when done and configure your Viper. Just make sure you have BusyBox installed and updated. You can get it from the play store. There are more settings and customization options I can list. Truly an awesome, well built ROM.

First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.

CornellEngineer said:
First off, I'd like to thank you for taking the time to post your very good guide for us new guys. Another superb tutorial can be found here...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
Your and comwiz's guides that summarize MeowDude's excellent work are two of the best ones I've seen to date and they help us novices a lot.
I want to set my elderly father up with Google's new YouTube TV streaming service when I visit him after the holidays and they currently require an Android L device or better to activate the service and control their interface. All he had was a Kindle Fire HD 8.9 a relative gave him that he never uses, so he sent it to me a few days ago so I could modify it. I've read a few of your posts on this and other threads and you seem very impressed with Temasek's CM13 custom ROM, so that's good enough for me and the one I wanna try first. But I'm a little confused by your followup post when you say "you HAVE to flash SuperSu". Does this mean that one should root with that app instead of Kingroot as was described in your original guide? I'm also not totally clear on exactly where in the procedure BusyBox needs to be installed. Here's what I have done so far to date...
*performed factory reset on Kindle Fire HD 8.9 just to clean it up and get it back to stock
*installed ADB on PC and verified it communicates with the Fire HD (detects device and returns serial number)
*downloaded and installed Total Commander (nice looking file explorer at first glance, BTW)
*sideloaded Root Check and verified device is not rooted
*downloaded the following files to PC but have not yet transferred them to the Fire:
---NewKingrootV5.1.0_C176_B415_en_release_2017_05_11_20170511212237_105203.apk
---fireflash11.apk
---kfhd8-u-boot-prod-8.1.4.bin.img
---kfhd8-freedom-boot-8.4.6.img
---kfhd8-twrp-3.0.2-2-recovery.img
---stack
---SR5-SuperSU-v2.82-SR5-20171001224502.zip
---stericson.busybox.apk
---cm-13.0-20160827-V11-temasek-jem.zip
I think this is everything I need but I'm not yet comfortable enough with my current knowledge level to try rooting and flashing a custom ROM. If you or anybody else could tell me what I should do next or at least point me in the right direction that would be much appreciated. I figure it's better to ask some dumb noob questions now before I attempt anything rather than have to come back later and ask how to unbrick my tablet.
Click to expand...
Click to collapse
"Root" is built into the ROM. But, it's not full root. So the ROM maker tells you to Flash SuperSU once the ROM is installed and functioning. You have to do that because you wipe the system (pretty much all of it) before you flash the ROM. That wipes Kingroot, root etc. until you flash the new ROM. You're on the right track exactly. Just make sure your files are placed properly and use FireFlash to install TWRP. Just follow all the steps exactly and it should be successful. The good thing about this method, it doesn't wipe your data to install the recovery.

Okay, DF...thanks. When researching Kingroot & SuperSU I came across a ton of external links about how to get rid of the former if it was used to originally root a device and replace it with the latter. I even found another XDA thread last night where you posted that you yourself spent many hours reading about how to do just that. It seemed like a lot of hoops to jump through so I thought maybe it was better just to use SuperSU to root in the first place and be done with it. But this was all probably before you tried the new ROM you're now using and are apparently liking a lot. It sounds like Temasek's ROM version automatically takes care of most/all of the Kingroot exorcism that gave you such a headache. Apparently on many devices you can install TWRP first and THEN root with SuperSU afterward but I gather the Kindle Fire's funky bootloader unfortunately doesn't permit this.
I'll just keep reading threads over and over again as well as outside reference articles on other sites like I have been so far. Some of it must be finally sinking in because some posts are actually finally starting to make a little sense and in some cases I now understand what a few folks did wrong to cause them problems. When the vast majority of the posts and articles I read make sense and not just some of them then I'll give it a shot. Appreciate the guidance.

Okie dokie, DF...just a quick status report on how we're doing following your new guide. So far, so good...used Kingroot to root the device no problem, verified it was rooted with Root Check, gave Total Commander (which I had installed a few days ago) root access, and downloaded and installed FireFlash. But when I opened the app and clicked on "allow" to have root privilege there was a minor glitch...although I could see the FireFlash menu in the background there was an error message saying it did not have root access and that it was going to close, even though Kingroot verified it as an app that had permission. Tried uninstalling and reinstalling a few times but kept getting the same error message. Finally I simply rebooted the device and it worked fine after that...so if there are any fellow noobs out there who are one step behind me (and heaven help you if you are) you might wanna try a simple reboot during this step if you experience a similar problem to see if that solves it.
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on. You did not mention this in your guide but this was summarized nicely by comwiz in his very similar tutorial...
https://forum.xda-developers.com/showpost.php?p=72395624&postcount=55
He also included many screenshots that one will see while following your guides...I found these visual aids to be very helpful in terms of what one could expect to see as you march through all the steps that you guys so graciously spent the time laying out for us newbies. I'm probably gonna hold off on installing TWRP and Temasek's custom ROM for a few days...I wanna read up more about TWRP and fastboot before I take the next baby steps. BTW, like you I just bought another used KFHD 8.9 in almost new condition on eBay today for about the same price that you paid...how's THAT for the ultimate "backup"???
Man, thank God for this XDA forum...no way I try this on my own without all the info and tools and help that experienced folks have taken the time to post here.

CornellEngineer said:
EDITED BY ME, "compjan"
Before I do anything else I'm gonna use ADB to create some images of several of the now-rooted stock partitions and save them to my PC just in case I eff something up later on.
Click to expand...
Click to collapse
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !

compjan said:
PLEASE upload those images !!! if you are running 8.5.1 on a 32 gig model I NEED THEM !
Click to expand...
Click to collapse
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286

MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
iRoot doesn't work anymore. At least not when I tried. Regardless of the method used to root, the quicker to get rid of them, the better it makes me feel.

MeowDude said:
I wrote a guide on how to flash recovery on 8.5.1 without a computer. Swing around and check it out, its got all the updated files.
https://forum.xda-developers.com/ki...t-install-twrp-android-fire-os-8-5-1-t3278286
Click to expand...
Click to collapse
um, i do not have a working 8.9 tablet. i screwed it up and had a red screen of death for a couple years now. i have been off work due to knee surgery and decided to see if there was a working fix. member sd_shadow has me OFF red screen, now i need to get back to stock BEFORE i start playing with it. that way i can fix it right then if i mess it up again.
SO, i need a copy of the 3 partitions to get back to stock.
UNLESS. . . . i can get the partitions out of the 8.5.1 BIN i grabbed from amazon. that is how sd_shadow ( THANK YOU SIR ! ) got me back to a NOT booting but hung at the fire logo. i flashed the bin to SYSTEM and now i need the other 2 partitions.

UPDATE: GOT IT UP AND RUNNING AS 8.1.4 ! ! !
wife wanted it stock, so i loaded the 8.5.1 update from amazon in the root directory of INTERNAL STORAGE. not i a folder. re-booted and it installed the 8.5.1 update. worked fine . . . EXCEPT . . . .
the built-in amazon app store was buggy as hell. so was the silk browser. gapps worked fine until a re-boot. then crashed as soon as i launched play store.
SO. . . . i'm backing up the 3 partitions and going to load a ROM on this puppy.
EDIT: there is a NEWER 8.5.1 "update" at amazon, it will NOT auto install via the "check for updates" button (afaik. and i tried it on 2 different 8.9's) . download it, copy it to the ROOT of the 8.9, not in a folder. reboot. it will install all by it's self. fixed all my stock problems!! END EDIT

I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.

votinh said:
I got CM13 installed on my 8.9 but then having issue.
a. Can't boot into custom recovery. With volume down hold + power button -> Kindle Fire orange -> Kindle Fire blue -> then it either boots back into CM13 or getting "Fast boot".
b. In CM13, i don't have root access. How so? Weird. I am always under the impression that every custom image will come with root access. I maybe wrong though.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
Well, my bad was I downloaded the wrong gapps, picked 7.1 instead of 6.0, so I wanted to boot back in recovery to install the correct gapps.
Click to expand...
Click to collapse
If using temasek ROM, you'll have to flash SU. Use 2.7X. then update from play store. Root for regular CM is found in developer options. Settings > about device > tap build number 7 times and go back to Maine settings menu, scroll to bottom. For developer options. Enable root in that menu. Select both apps and ADB.

I am using the CM13 ROM by alexander_32, I guess the same one you're using.
Personally, it isn't as snappy as I wish but I'll give it some more time.
Also, the option to boot into recovery on the menu is so much better than using keys combination. Thumb up for that!

what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.

green_reaper said:
what is the optimal gapps to get from open gapps? there are so many options im not sure which works best on jem.
Click to expand...
Click to collapse
I almost always use pico gapps.

DragonFire1024 said:
I almost always use pico gapps.
Click to expand...
Click to collapse
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?

green_reaper said:
so basically for jem im using CM13 (Marshmallow 6.0.1) build by Temasek . and for gapps should I use (platform = ARM , Android 7.0 and pico) ? or is there a better gapps build selection?
Click to expand...
Click to collapse
Go to opengapps website. Always download the gapps for the corresponding Android version. Always choose ARM.

[V2][Update][Root][G955U]PartCyborgRom - SamFail Rooted/Debloated/Audio/More

SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G955U/W, Bootloader Revisions 1, 2, 3​
Updates
NOW Supporting Bootloader V3!
I am happy to announce that BL version 3 phones are now supported by PartCyborgRom!
Just download the Version 3 BL further down in this post (after reading everything in between!) and use it in place of the normal BL Part2 file.
NOTICE: Rooting Process Steps Updated!
Enough people are coming from later bootloader revisions that have some extra protections that I updated the process to use an additional step. Many of you have used this step already at my suggestion when your AP flash was failing with Auth Error without a reboot to Upload.
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G955USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G955UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G955U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G955UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4A) Open Comsy Odin and Reboot into Download mode. Add Only the BL Part2.tar.md5 file. Go to the options tab and remove the checkbox next to "Auto-Reboot". Do not check any additional checkboxes and leave the other ones alone. Connect your phone and Start. Odin will flash the BL file to your device and will say PASS, but will just sit in download mode (because we turned off auto-reboot!). This makes the next part a little easier...
4B) Reset Comsy Odin and use the "three button salute" on your device to Reboot back Download mode. This time only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device stays in Download Mode:
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have likely suffered from the usb3 corruption
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and once again add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Do not change any of the options checkboxes, thus leaving the checkboxes checked for "F Reset Time" and "Auto Reboot". Click "Start" and flash the BL (part 2) to your device.
Note: Flashing BL twice is necessary as some newer stock BLs have patched the Root method we use, but the Combo Factory firmware is still vulnerable. In other words, the SamFail nickname continues to be prolific :good: :good:
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.​
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10

Downloads
BQL1 (G955U and G955W)
AP_PartCyborgRom_G955U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G955U_BQL1.Part2.zip
[Alternate Mirror]
NEW: Bootloader V3 Support!
BL_PartCyborgRom_G955U_U3BQL1_R5.zip
[Alternate Mirror]
Other Downloads
Do Not install any of these unless you are running an older version.
BQL1 has all of these mods already!
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
​

Previous Versions
SM-G955USQU2BQK5
AP and BL Parts 1 & 2
AP_PartCyborgRom-G955USQU2BQK5_Part1.zip
BL_PartCyborgRom-G955USQU2BQK5_Part2.zip
SM-G955USQU1AQK3
AP and BL Parts 1 & 2
AP_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part2.zip
​

One more

@partcyborg , nice work and thank you for posting your PCB ROM for S8+!

Thank you @partcyborg!

You ARE the f'ing man!!!!! THANK YOU!!!
And to the peeps whining, over the past 5+ months that there wasn't a custom ROM available for this phone, I would hope to see you hitting the 'Thanks' button.

You said you would do it, and you did it! Thanks for doing this for us! Very excited to give this a try.

Can't wait to get home and try this out!!!!!!

Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?

ok so i have wiped everything before install and then followed install instructions all the way....
scratch that a reboot fixed the rotation issue

Wow ! I watched you actually say you wouldn't mind doing a rom for us and you did do it. AMAZING. I gotta try this when i get home ! time to back everything up lolol. Do you know if xposed works for this ? and also can we change the font with iFont now since you managed to? Once again thanks for port !

Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Sent from my SM-G955U using Tapatalk

matthewd769 said:
Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?
Click to expand...
Click to collapse
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work

partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
Any ideas?
Sent from my SM-G955U using Tapatalk

partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
thanks dog ... appreciate the hard work and answer .... i might start coughing and leave early

Goddly said:
Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Click to expand...
Click to collapse
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people

Stovall Family said:
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people
Click to expand...
Click to collapse
Factory restore?
Sent from my SM-G955U using Tapatalk

Goddly said:
Factory restore?
Click to expand...
Click to collapse
Factory restore through stock recovery.

Goddly said:
Any ideas?
Click to expand...
Click to collapse
Can you fire up PreConfig and try and set your csc?
Also try flashing 1 more time. If you have a usb2 port absolutely use that. Several people have had major issues with flashing on usb3.0 ports and every one whose had a usb2 port to try it's worked flawless after. This rom will fail when stock doesn't because of its size. In order for samfail to work we have to use a raw image not a sparse one like in the stock AP. This means the image is the full size of the partition despite not being completely full

Newbie rooting/backup thread (groan...)

In my defence, m’lud, I spent about 6 hours yesterday reading through a great many threads before posting this one. It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
I expect it's just the terminology… when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…? Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
My main reason for wanting to root my M8 is to remove all the bloatware HTC put on it. I can read the instructions for rooting here, but I don’t like blindly following anything I don’t understand, for obvious reasons!
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
I’ve read through several tutorials, and they’re easy to follow, but not easy to understand, if you get me… they’ll say things like download this, flash that… but I don’t really know what’s going on when you flash something – what am I over-writing etc.
Is there a thread anywhere which explains what these various things actually ARE?
Oh, and I’ve been playing various King games for years, and have got a long way. I’ve tried to figure out how to back them up – the King website is possibly the most unhelpful I’ve come across. People mention various utilities (I think maybe Titanium etc), but if they only work on a rooted phone, they presumably can’t be used to back the games up prior to rooting…
Sorry about all this guys – not asking you to re-invent the wheel, but f there are specific threads that already answer my questions to get me started, I’d be VERY grateful
Thanks
Roger

Roger465 said:
In my defence, m’lud, I spent about 6 hours yesterday reading through a great many threads before posting this one. It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
Click to expand...
Click to collapse
Aye, it takes a bit of time to learn all the things and understand them.
Me, after being really familiar with a Sony device had to spend XX hours reading about HTC and after few years there are still things that I don't know
Roger465 said:
I expect it's just the terminology… when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…? Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
Click to expand...
Click to collapse
I'd rather say recovery is closer to bios., but bootloader matches too.
Recovery is a partition that all android phones have and it can be accessed in case when the system dies to factory reset and things. Stock recovery is good, but it can't be used to flash things like roms and kernels, so we use TWRP - a custom recovery with many options.
Original recovery is overwritten, but can be restored.
As for bootloader it's kinda like a gate - a locked one prevents booting and flashing of any unauthorized files, like custom recovery for example. Unlocking it removes this restriction. That's one fuction of bootloader, another one is starting up the system - like a bios - and can be accessed by a button combination durning boot up, it's also called hboot. In it you can see some essential info about phone software and boot to recovery.
Roger465 said:
My main reason for wanting to root my M8 is to remove all the bloatware HTC put on it. I can read the instructions for rooting here, but I don’t like blindly following anything I don’t understand, for obvious reasons!
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
Click to expand...
Click to collapse
ROM is the android itself, drivers, kernel and manufacturer's interface, apps, tweaks, settings. and probably something else I've missed. I think it would be somewhat correct to call this operating system. Rooting is gaining superuser access on the phone - it can be used to give extended functionality to apps, like making modifications in system itself. Pretty similiar to "run as administrator" in windows. Rooting itself won't remove the rom.
Roger465 said:
I’ve read through several tutorials, and they’re easy to follow, but not easy to understand, if you get me… they’ll say things like download this, flash that… but I don’t really know what’s going on when you flash something – what am I over-writing etc.
Is there a thread anywhere which explains what these various things actually ARE?
Click to expand...
Click to collapse
Those should give you a basic knowledge:
https://www.androidcentral.com/dictionary
https://android.gadgethacks.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
Roger465 said:
Oh, and I’ve been playing various King games for years, and have got a long way. I’ve tried to figure out how to back them up – the King website is possibly the most unhelpful I’ve come across. People mention various utilities (I think maybe Titanium etc), but if they only work on a rooted phone, they presumably can’t be used to back the games up prior to rooting…
Click to expand...
Click to collapse
Titanium backup is an app used to backup other apps, but it requires root. To get root you need a custom recovery and for it you need an unlocked bootloader.
Unlocking the bootloader will wipe all data from the phone. I'm not aware of many working methods to backup apps and their data.
There's an app called Helium, but there are many complaints that it doesn't fully work. You can try syncing all data to your google account or adb backup.

A lot of the basic terminology is explained here: https://forum.xda-developers.com/showthread.php?p=52484527#post52484527
My responses below in red font:
Roger465 said:
when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…?
I'd say that is a pretty good analogy. It's responsible for loading the OS, same as BIOS does on a PC. And as long as you can get into bootloader, the phone is recoverable almost regardless of what else you did (within some limits).
Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
Recovery is the tool for making or restoring backup (and also flashing ROMs and other mods like root). And not the actually backup itself. So that is one important distinction to remember.
Installing custom recovery (TWRP) will overwrite the stock recovery, that is true. You can only have one recovery at a time.
Stock recovery is easy to restore; and the stock recoveries are available on this forum. But stock recovery is close to useless. The only reason you would need stock recovery, is to install an official OTA (over-the-air) upated. And HTC was done updating this phone a long time ago (with Marshmallow) and there will be no more updates. Therefore, no need for stock recovery.
Since you've decided to do to the dark side and root; custom recovery TWRP as vastly more useful than stock recovery (as also mentioned in the previous response). To be honest, I can't say I've booted to stock recovery on this or any HTC device I've owned (and it's been several) even once. Never used it, and never needed to.
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
Depending on root method (SuperSU or Magisk), root will make changes to the system and/or kernel (which comprise the OS or ROM). It's still the stock ROM, just with some minor changes to allow superuser access. You can and should make a backup or your stock ROM, before rooting, using TWRP custom recovery. This gives you an easy way to restore to stock unrooted ROM, if you ever want to. And also gives you an easy "escape hatch" if anything goes wrong while trying to root. There are other tools on this forum for restoring the stock ROM. But best practice (and just plain common sense) is to make a backup in TWRP.
Click to expand...
Click to collapse
---------- Post added at 10:33 AM ---------- Previous post was at 10:24 AM ----------
Phalangioides said:
There's an app called Helium, but there are many complaints that it doesn't fully work. You can try syncing all data to your google account or adb backup.
Click to expand...
Click to collapse
All backup methods are far from perfect, especially before/without root. I'll agree that Helium is probably the best bet for the OP to backup things like game saves.
---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------
Roger465 said:
It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
Click to expand...
Click to collapse
Stick with it. Every technology has its own lingo and nuances. Even from one Android device to another, there is a learning curve. I've found myself wondering: "WTF is a blob, or Odin" when switching to other Android devices.
With your IT experience, it shouldn't take much to pickup the necessary knowledge.

Thanks guys, kind of you to go to so much trouble to explain for me. Wish I had two phone,s then I could play around messing one up... will read a bit more, then give it a go in a day or two I think. But just to clarify again, can I give myself the rights to remove stock bloatware, while maintaining my familiar Android environment, the apps I use at the moment etc, or do I have to install a custom ROM if I root?
Cheers

Roger465 said:
can I give myself the rights to remove stock bloatware, while maintaining my familiar Android environment, the apps I use at the moment etc, or do I have to install a custom ROM if I root?
Click to expand...
Click to collapse
Yes, the OS will remain the same.
Whether you can remove bloat apps after root is a little complicated to explain. You would normally expect to be able to delete system apps (which bloat apps are) with root. However, for whatever reason, HTC decided to write-protect the system partition, even with root. This means that if you try to delete apps when the phone is booted to OS, (depending on what method you used to delete the apps) you will find they return when the phone is rebooted.
You can flash a kernel mod to disable the write protection, or install a custom kernel. Or you may find the easiest work around (after root) is to use the file manager within TWRP to delete the bloat apps.
---------- Post added at 12:43 PM ---------- Previous post was at 12:11 PM ----------
Vomer's guide is a good one, for unlocking the bootloader, custom recovery and root:
https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
It's a bit outdated, so some words of advice:
- Only follow parts 0 and 1 of the guide. The sections after that aren't needed (s-off and SuperCID) for root, and the s-off method no longer works.
- Use an updated version TWRP from what is in the guide. If you are currently on Marshmallow, the current version TWRP 3.2.1.0 should work. Or basically any version 2.8.7 or later. You can get TWRP here: https://dl.twrp.me/m8/
- Similarly, use current version SuperSU 2.82 (use TWRP flashable zip from here): https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Or alternately, you can use Magisk to root, instead of SuperSU. Honestly, Magisk is really cool, and has lots of features that SuperSU doesn't. So I suggest checking it out: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

redpoint73 said:
Vomer's guide is a good one, for unlocking the bootloader, custom recovery and root
Click to expand...
Click to collapse
Hhmmm, not getting very far with that procedure. Difficulties so far:
- Enable USB debugging in your phone's Developer options - DONE
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
- Install ADB and Fastboot on your computer - DONE
- Make sure to back up all of your app data using either ADB or HTC Sync, because you will be wiping your phone – JUST PLAYING AROUND WITH CONNECTING TO THE PHONE AT THIS STAGE
- Install the HTC One M8 drivers on your computer (if you have HTC Sync installed, then you already have them) - DONE
Enter Fastboot (bootloader) Mode
Place your device into fastboot mode by plugging in your HTC One to your computer,
then powering it down by holding both the Power and Volume Down buttons until you see the screen below – WHEN I DO THAT, IT JUST TAKES A SCREENSHOT

Roger465 said:
Hhmmm, not getting very far with that procedure. Difficulties so far:
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
Click to expand...
Click to collapse
It was only available back on 4.4. It was removed in 5.0 and above, no need to worry about it now.
Roger465 said:
Enter Fastboot (bootloader) Mode
Place your device into fastboot mode by plugging in your HTC One to your computer,
then powering it down by holding both the Power and Volume Down buttons until you see the screen below – WHEN I DO THAT, IT JUST TAKES A SCREENSHOT
Click to expand...
Click to collapse
The guide is a bit inaccurate in this one. Turn off your phone, then press power and vol down - you should get into bootloader. Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
My phone refuses to boot up after I turn it off. Have to help it with a soft reset and then hold vol down so it gets into bootloader, so I can't fully confirm.

Roger465 said:
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
Click to expand...
Click to collapse
As mentioned in the previous response, this doesn't apply anymore. The feature doesn't exist (hasn't since Kitkat) and therefore does not need to be turned off.
Also note, this option is not to be confused with the fastboot/adb interface (virtually the same name, for different things) which is still fully working, and required to unlock the bootloader and flash custom recovery. The power option "Fast boot" was just a feature used by HTC to make the phone turn on faster. It was merely a "deep sleep" trick which was not a true "power down" and would interfere with accessing bootloader/fastboot mode if you tried to it from a "power off" condition (since in fact it wasn't truly powered off).
Again, it's irrelevant now, and you don't need to worry about that step at all.
---------- Post added at 09:14 AM ---------- Previous post was at 09:00 AM ----------
Phalangioides said:
The guide is a bit inaccurate in this one. Turn off your phone, then press power and vol down - you should get into bootloader.
Click to expand...
Click to collapse
Agreed, the guide is a little incorrect on that step, and I hadn't caught that (error in the guide) before. Power+vol down to access bootloader, will only work when the phone is powered off.
To the OP, another method/trick to access bootloader:
1) While the phone is on, reboot the phone by holding down the power button, and select "reboot" (or restart, I forget exactly what it says)
2) Once the screen goes dark to reboot, but before the white HTC logo screen appears, hold down the vol down button. Don't let go until you see the white bootloader screen.
3) If the phone simply restart to OS, you simply got the timing wrong. You either started pressing vol down too late, or let go too early. Just repeat steps 1 and 2 until you get it right.
Another alternative, is to force a reboot by holding power+vol up. Again, once the screen goes dark to reboot, but before the HTC logo screen appears, hold the vol down button only. In this case, you simply let go of the power button, and slide your finger down to the vol down button, and don't let go until the bootloader screen appears. This method is handy to know, since it works in all cases when the phone is powered on, even of the phone is "frozen" or stuck not loading the OS.
Phalangioides said:
Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
Click to expand...
Click to collapse
If the phone is already connected to the PC by USB cable before going to bootloader, it should default to fastboot mode once the bootloader is accessed.
Not sure if it will automatically switch to fastboot mode if you are in bootloader, then plug in the USB cable. But that may well be true (and would make sense).
In either case, if it's not in fastboot mode, simply select "fastboot" by using the vol buttons, and confirm the choice by pressing the power button. You should see "fastboot" highlighted in red near the top of the screen.

Phalangioides said:
Turn off your phone, then press power and vol down - you should get into bootloader. Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
Click to expand...
Click to collapse
Wahay! That worked fine, thanks both. Hope you can appreciate, though, how scary it can be for somebody like me following instructions I don't really understand, when the expected thing doesn't happen – visions of bricks keep coming into my mind
OK, will practice these steps a few times till they’re 2nd nature. I have managed to retrieve my phone identifier thingy though

Roger465 said:
Hope you can appreciate, though, how scary it can be for somebody like me following instructions I don't really understand, when the expected thing doesn't happen – visions of bricks keep coming into my mind
Click to expand...
Click to collapse
Don't worry, you won't brick this device with what you are doing (unlock bootloader, custom recovery & root). In fact, this device is very hard to brick. As long as the screen comes on, it can almost always be recovered.
Worst case, is that something goes wrong, and you can't boot the phone. Maybe you did something wrong, or maybe just some random event that was not fault of yours. And maybe it takes you an (hairpulling) hour to find the answer, and figure out what went wrong (or how to recover from the problem). But that pretty much happens to everyone who mods these devices from time to time. If you work IT, you've been there. Stressful, but hardly ever catastrophic.

Woo hoo! Got my unlock code. Now time for some more studying before I do anything drastic - specifically how to back up.
I think the HTC Sync Manager will handle most of it? My contacts are all on Google anyway... main worry is 2 years' progress on various King games

Roger465 said:
Now time for some more studying before I do anything drastic - specifically how to back up.
I think the HTC Sync Manager will handle most of it? My contacts are all on Google anyway... main worry is 2 years' progress on various King games
Click to expand...
Click to collapse
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).

redpoint73 said:
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).
Click to expand...
Click to collapse
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it

Roger465 said:
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it
Click to expand...
Click to collapse
The first unlock bootloader will restore your phone. Cross your finger if the game data has been backed up. :fingers-crossed:

redpoint73 said:
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).
Click to expand...
Click to collapse
I don't play games so I can't really confirm all games are same.
On my experience transfering games data from one device to another (for nieces & nephews), the data is stored in internal storage android\data\games folder & android\obb\games folder. I copy these two out and transfer them to new device.
(Also check sdcard android folder)

Roger465 said:
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it
Click to expand...
Click to collapse
I agree with the approach, make different backups and hope one or more works properly. Games and other apps don't all save data the same way, so no single approach will work in all cases.

Me again, sorry… shortly after that post, I dropped the thing and broke the screen. For one reason or another, I ended up getting a Samsung S6, which I’m quite happy with.
But I want to use the HTC as a spare/emergency phone – trouble is I can’t remember what I’ve done to it, apart from installing something which was recommended as part of my attempted rooting process.
When I switch it on I get the screen below – but no matter which option I select, it just seems to either switch it off or loop back to this screen.
I didn’t go any further than install whatever software it was that gives me this boot menu screen.
I’m no longer interested in rooting it etc – just went to restore it to factory settings and leave it.
Can anybody tell me how please…?
Thanks

Roger465 said:
I can’t remember what I’ve done to it, apart from installing something which was recommended as part of my attempted rooting process.
Click to expand...
Click to collapse
Obviously, if you don't know what you did, it's hard for us to figure out as well.
The "LOCKED" banner at the top of the bootloader screen means the bootloader was never unlocked. So really, no actual mods were done to the phone by you.
All I can think, the "something" what you installed was possibly the Helium app (recommended by another user back up on this thread) which can be used to backup/restore your app data.
Roger465 said:
I didn’t go any further than install whatever software it was that gives me this boot menu screen.
Click to expand...
Click to collapse
I don't know what you're trying to say here. You'll need to be more specific (at least try) than "whatever software". Did you flash something to the phone? Or only installed something to your PC (drivers, fastboot, etc.).
We need to properly understood what you've done, before we can assist further.

redpoint73 said:
Obviously, if you don't know what you did, it's hard for us to figure out as well.
The "LOCKED" banner at the top of the bootloader screen means the bootloader was never unlocked. So really, no actual mods were done to the phone by you.
All I can think, the "something" what you installed was possibly the Helium app (recommended by another user back up on this thread) which can be used to backup/restore your app data.
I don't know what you're trying to say here. You'll need to be more specific (at least try) than "whatever software". Did you flash something to the phone? Or only installed something to your PC (drivers, fastboot, etc.).
We need to properly understood what you've done, before we can assist further.
Click to expand...
Click to collapse
Yeah… sorry, I’m aware how unhelpful my post is. Unfortunately, it was a while ago now, life went tits up for quite a while, and the phone lay in a drawer, being a very low priority. I used to take it out occasionally and charge it up – it started normally.
The other day, I realised I hadn’t charged it in many months, so took it out, and sure enough it was completely dead – so I plugged it in, and it came up with the screen as posted. I let it charge for a couple of hours, then rebooted, and it came up that way again. No matter which option I select from the menu, it either just shuts down, or reboots to that screen.
I’m virtually certain I didn’t do anything other than enable the mode which lets you get to that boot screen, and that I didn’t get as far as flashing the phone or anything. Don't think I installed Helium - if I did, I didn't actually use it.
So it may just be that the phone has died from being left flat for so long… is that likely do you think?
Thanks and sorry again for the lack of info – I completely understand if you can’t help!

Roger465 said:
I’m virtually certain I didn’t do anything other than enable the mode which lets you get to that boot screen, and that I didn’t get as far as flashing the phone or anything.
Click to expand...
Click to collapse
Okay, so it was somewhat confusing, as you said previously (twice) that you "installed" something. But I think you are just confused, thinking that installing something is necessary to get to the bootloader screen. Which it isn't, that screen is part of the bootloader, without which your device would be a paperweight. It will sometimes default to this screen by virtually no action of yours (except powering it on) in cases when the Android Operating System (OS) is missing or damaged. Or you can simply access the bootloader screen by holding the button combo power+vol down.
Roger465 said:
So it may just be that the phone has died from being left flat for so long… is that likely do you think?
Click to expand...
Click to collapse
We've seen it a number of times, actually. The OS was probably corrupted or damaged by being powered off (battery dead) for so long. This condition is over recoverable, as long as the phone can power on, and you can get to bootloader (which you can).
You can restore the OS with the RUU (ROM Update Utility) tool. You can get the RUU, and instruction how to flash it from here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note: there is no need to lock the bootloader as the first part of the instructions say (your bootloader is still locked).