Develop Bugs

[Q] New OS update bricked my Fire. Any quick fixes?

My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA

What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.

Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.

Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.

Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.

It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.

I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium

The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.

thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM

Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.

Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.

F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.

Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.

Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.

Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!

No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.

Extreme lag...Even in Recovery!!!

Hello,
Something went really serious with my device. I just don't have any idea! Please read on and help...
So, this was my fresh start with customization in my Galaxy Grand Duos (GT-I9082). I wanted cm-11.0 in my phone and I planned to install @pawitp's recovery as he said in his thread. And I installed it using odin 3.09. But after odin said "PASS", the phone rebooted to system (as expected). Then, I switched it off and then tried going to recovery by key combination but the phone rebooted to stock android recovery. I was new to Grand and so I researched on net and found that in few stock roms of Galaxy grand, the odin cannot detect the block where to flash the recovery and so recovery foesn't flash in correct block.
So, I downloaded latest Indian stock ROM from Sammobile (Yes, my device is purchased from India). To be precise, this one: http://www.sammobile.com/firmwares/3/?download=25333
And flashed it. The process was over in 2-3 mins at max. Then, after the first boot, phone was little bit laggy. I thought, it would become smooth after sometime and didn't bother. Then I installed @pawitp's recovery and it flashed and was working fine. Then, I installed v1.51 CF-Root zip, because I had root to use Titanium Backup for few apps. It got installed successfully. Now, I rebooted to system and what I felt was a terrific slow phone (I mean my each and every word). It took 3-4 minutes to open dialer. It was smooth at times for 2-3 seconds but again extreme lag. I thought, I should wipe data and to do that I went to recovery and did a data-wipe/factory-reset. Now, phone took 13-14 mins to boot-up (I know it builds dalvik-cache but it should takke 3-4 minutes at max). After it booted up, I was presented setup wizard and it took me 20-25 minutes to complete this wizard. What I mean is, it was still extreme laggy rather it was more laggy than earlier.
Here comes a very bad thing then:
Now, I thought of going to recovery and flash cm11 zip file. But, when I booted to recovery, I got a black screen with a "clockworkmod recovery 6.0.4.5" text at bottom and the whole recovery layout came after waiting 1-2 minutes! So, it just got me in a very bad tension. It was laggy even in recovery!! Now, I decided to flash stock ROM again and started flash using odin. But, the most dangerous thing happened: It was laggy/extremely slow in download mode even!!!!! It took 53 minutes to complete the flash!
Now, the phone was in same condition. :'(
I just thought of doing a factory reset using this stock recovery and then I did a 'Factory Reset' from inside the system (Settings > Backup & Reset > Factory Reset).
Now, my phone became fast. And I got a BIG relief. It still feels slow at times but is reasonably fast, atleast till now (15-16 hours after factory reset).
What is my question then?
What just happened that made my phone extremely slow in Download Mode, Recovery and ofcourse System?
I need a satisfying answer please...
One more thing: I have habit of pulling out battery to switch the phone off when odin says "Pass" (I'm lazy to wait for it to complete boot), if I have to use recovery.

I restored my phone to previous version.
I had this problem too after update to latest release of Samung Android 4.2.2(febroury release). Screen frequently flickered. Phone slowed down.
I just did a Nandroid Restore to my previous version of the Android (yeah the same 4.2.2 but its old november released 4.2.2).
Everything is back to normal.

Imrankhan92 said:
I had this problem too after update to latest release of Samung Android 4.2.2(febroury release). Screen frequently flickered. Phone slowed down.
I just did a Nandroid Restore to my previous version of the Android (yeah the same 4.2.2 but its old november released 4.2.2).
Everything is back to normal.
Click to expand...
Click to collapse
I was unable to install any recovery as I said, so I don't have a backup but still I may find that release on sammobile.
I'm still on latest N1 (February) and is reasonably fine uptil now but not as fast as K1 (maybe November one). Some glitches still there.
I want someone with good knowledge on Grand to tell me why is this issue occurring!?

I think u messed up with kernel due to which the terrible lag was there...coz u went wrong somewhere which created this problem...Right now u r in B1 firmware right just flash chotu22 recovery using Odin 3.04 or 3.07(S I mean the version) coz if u use other version u will land with weird thinks and then go to recovery that CWM and flash SuperSU.zip to get root access this method worked for me almost 3 out 3 times in every version of the firmware..
Sent from my GT-I9082 using XDA Premium 4 mobile app

I think its bcoz of faulty update by Samsung.. For this
u need to flash 4.1 Android version then flash again with 4.2 version.. Which are released in November month.. Then u gud to go..

@jackeagle,
Thanks for replying. I am on N1 (not B1) and I have enough knowledge about such things and I know that I was right at every step. I'm just new to Grand and so just asked here if there was any device-specific problem.
I think I figured out what was happening.
-This N1 release (February 2014) seems to be a release for the newer/different versions of Galaxy Grand (very minor hardware changes). Because, my device didn't received it via OTA.
-This can work on our devices also. Just format everything using the recovery belonging to that firmware, everything goes straight well. Now, my phone is again flying in the air.

Bhargav97 said:
@jackeagle,
Thanks for replying. I am on N1 (not B1) and I have enough knowledge about such things and I know that I was right at every step. I'm just new to Grand and so just asked here if there was any device-specific problem.
I think I figured out what was happening.
-This N1 release (February 2014) seems to be a release for the newer/different versions of Galaxy Grand (very minor hardware changes). Because, my device didn't received it via OTA.
-This can work on our devices also. Just format everything using the recovery belonging to that firmware, everything goes straight well. Now, my phone is again flying in the air.
Click to expand...
Click to collapse
It must have been very tough 53 minutes while flashing... I guess longest 53 minutes of ur life... good eg. Of patience my friend ...:thumbsup:

Hello everyone,
I'm worried now. What I found after these days is: The write speed on my /boot, /recovery, /system, /data and /cache partition is hellish slow!
Another, the speed becomes slower and slower after it starts to fill up more and more!!!
Supporting Reasons:
-ODIN took 53 minutes for flashing (as mentioned in first post...didn't try after that)
-Restoring a cm11 backup (1.1 GB only) took 19.5 minutes (using PhilZ Touch Recovery). Restoring system starts very fast (250 MB in 20-25 seconds) and then it slows down and it takes 8-9 minutes to restore the left 150-200 MBs! Same kind of thing happened with data partition restore. Also, loading of recovery is slow (black screen for 15-20 secs then comes navigation keys and after 4-5 seconds comes the main UI).
So, is there anyone having the same kind of issue with PhilZ Recovery?
And, what seems to be wrong!? The Feb release?
EDIT:
After flashing older (November release-K3), everything is fine again.

Did I just brick my phone? H815 + Root + trying to FlashFire XPosed

Phone is H815 TWN. Rooted but not unlocked.
Updated the phone to 10e via Download Mode - Check
Tested phone - Check
Xposed wasn't loading - Okay, must re-flash framework
Starting flash with FlashFire and it's been sitting at the LG Lifes Good boot screen for 15 minutes...pulled the battery...same thing.
I did do a system image backup before flashing 10e...is there a way to restore that via Download Mode? Is it the same command just change rootedsystem.img to system.img?
Any help would be appreciated.

IlyaKol said:
Phone is H815 TWN. Rooted but not unlocked.
Updated the phone to 10e via Download Mode - Check
Tested phone - Check
Xposed wasn't loading - Okay, must re-flash framework
Starting flash with FlashFire and it's been sitting at the LG Lifes Good boot screen for 15 minutes...pulled the battery...same thing.
I did do a system image backup before flashing 10e...is there a way to restore that via Download Mode? Is it the same command just change rootedsystem.img to system.img?
Any help would be appreciated.
Click to expand...
Click to collapse
I went ahead and repushed the backup I took via Download Mode and phone is booting now. I guess I'll try my process again.

IlyaKol said:
I went ahead and repushed the backup I took via Download Mode and phone is booting now. I guess I'll try my process again.
Click to expand...
Click to collapse
Maybe you should delete all of the files you have from trying to install xposed and start fresh. Reread each step and make sure you have the proper files in place. Also, xposed took upwards of 15 minutes to install for me. About half way though, the screen turned back on for a quick second and showed some of the installation process, but promptly shut off again. Make sure you have sufficient battery and don't even touch the device, but keep an eye on it. No screen taps, no device rotations. Just let it do it's thing and be patient.

Spudnubs said:
Maybe you should delete all of the files you have from trying to install xposed and start fresh. Reread each step and make sure you have the proper files in place. Also, xposed took upwards of 15 minutes to install for me. About half way though, the screen turned back on for a quick second and showed some of the installation process, but promptly shut off again. Make sure you have sufficient battery and don't even touch the device, but keep an eye on it. No screen taps, no device rotations. Just let it do it's thing and be patient.
Click to expand...
Click to collapse
I've done this before, two times. And I'm a systems engineer for a living. Would like to think I know what I am doing lol.
The Xposed framework (and apk) are both files I've used in the past without issue. I keep them saved for re-use in cases such as these. Perhaps something just went wonky...before the LG logo being stuck for 15 minutes...I was in theory at like minute 20 of the process (it's taken around 15-20 the other two times I flashed Xposed so I knew going in it would take a while). 100% battery (just put a fresh spare in), nothing connected.
For S&G's, I'm going to attempt to do the framework install with the v78-SDK22 version for ARM64. We'll see if that has a different result.

IlyaKol said:
I've done this before, two times. And I'm a systems engineer for a living. Would like to think I know what I am doing lol.
The Xposed framework (and apk) are both files I've used in the past without issue. I keep them saved for re-use in cases such as these. Perhaps something just went wonky...before the LG logo being stuck for 15 minutes...I was in theory at like minute 20 of the process (it's taken around 15-20 the other two times I flashed Xposed so I knew going in it would take a while). 100% battery (just put a fresh spare in), nothing connected.
For S&G's, I'm going to attempt to do the framework install with the v78-SDK22 version for ARM64. We'll see if that has a different result.
Click to expand...
Click to collapse
I've actually just updated to v78 like four or five days ago and I've noticed significant improvements. I also kept my old files around for the xposed installation and when my phone bogged down, I did a factory reset and flashed those same files. They preformed poorly causing me to do another factory reset. I deleted all my old files, updated to the newest version and things have been great ever since.
Best of luck to you.

Good to hear that v78 is working great. Starting that process shortly

Looks like all is well. 2nd times a charm tonight.

[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

An HTC10 out of control - flashed to death?

Hello dear HTC10 community!
My HTC 10 is driving me crazy right now and I'm at the end of my humble Latin and hope for your help.
Facts:
HTC_0034
ROOT (Magisk)
S-OFF
Radio: [email protected]
OS: 3.16.401.2
CustomROM: Viper10 6.0.0
TWRP: twrp-3.5.0_9-0-pme.img (I also used the 4-5 versions before that in between)
About two weeks ago I installed a Magisk update. I think it was Magisk himself and not the manager. After the reboot, the device wanted a decryption key. However, I was only shown a text field, although I had deposited a pattern. Unfortunately, the way via the sample number code translation (point top-left = 1, top-middle = 2, top-right 3, middle-left = 4, middle-middle = 5 ... and so on) did not work. I couldn't get to my data. Regardless, I synchronized all important data with the PC every day via MyPhoneExplorer. So I thought to myself that I would put the smartphone back on. That started the madness ...
Part 1: Restore via TWRP
However, some later installed apps caused problems. Hence the ...
Part 2: ROM flash via TWRP
First I flashed the latest Viper10 6.0.0 ROM.
Since the developers of Viper10 are unfortunately no longer active and the Venom HUB server is down, the setup is no longer fun and my PRO license could no longer be restored - even after the selective restore of the entire Venom Viper- Modules via TitaniumBackup.
A little annoyed, I looked around for more CustomROMs.
Part 3: AICP, crDroid, CarbonROM & XenonHD
The first alternative surprised me with Android 10. WOW - I wouldn't have expected that with the old HTC10. I tried them all one by one. It's cool that some of my favorite functions (e.g. the 1px thick battery bar at the top) have made it into other ROMs.
Now I wanted to flash both candidates crDroid and CarbonROM again and examine them carefully,
From here on, sheer madness followed!
The home button on one of the two ROMs no longer responded. I suspected a hardware defect, but still wanted to test a different ROM. It didn't work either. Okay, back to the beginning.
Stock-3.16.401.2 installed. Both as Flash via TWRP and via 2PS6IMG.zip in download mode. The home button worked again both times. So NO hardware defect. In return, the mobile data no longer worked. WiFi but yes. I hadn't touched the SIM up to now and the smartphone didn't fall down either, which could have explained a wobble on the SIM. SIM removed, cleaned, slot blown out, SIM inserted, reboot: nothing. No funk.
One of the CustomROMs flashed, yeah, radio including LTE works again, home button too, but the GAPPS and the Google setup didn't work. Unfortunately, I need this because of some paid apps. The alternative with MicroG and the fake store unfortunately only worked for a few apps. So I wanted to let Google go directly to my device, because thanks to XPrivacyLua it had been fed with fake data for years and should continue to do so.
So a CustomROM flashed again. This time I couldn't enter a PIN on the first boot. The touchscreen did not respond to any touch. The softkeys responded, however. The hard keys too. With a 1-second press of power, the power menu even came up. But couldn't click anything.
Tried more ROM. Same problem.
With XenonHD the screen went on again. But again no home button.
From here on I just had to look at the device and I got in a bad mood.
Back to the beginning: Stock-3.16.401.2.
Everything worked! Great!
So now my CustomROM favorite carbon flashed clean.
No touch!
After the umpteenth attempt and once more stock ROM in between, the screen went off and was able to enter the PIN. So entered the PIN and bang, black screen. No reaction. 1 minute, 5 minutes, 20 minutes. The device got suspiciously hot. So off and let cool down.
Tried again. Same problem.
Back to the beginning: Stock-3.16.401.2.
Everything goes. But get a slight stomach ache using it without Magisk, XPrivacyLua and AFWall +.
And this has been going on for almost two weeks.
StockROM works (mostly), CustomROMs almost all hang completely in different places.
In the meantime I can hardly get beyond the bootloader (where the red warning is).
When it goes on, I see the boot animation and then a boot loop follows.
I also tried to re-flash the firmware every now and then, because there seems to be some driver problem here.
I found the only ZIP here:
[8.0] HTC 10 OREO FIRMWARE
HTC 10 OREO ~ Firmware Downloads ~ HOW TO FLASH FIRMWARE (Thanks to @Sneakyghost) __________ I had previously provided a few firmware zips for Oreo in the older firmware thread. Some users have/had a difficult time reading and...
forum.xda-developers.com
Post # 2 at the bottom WWE Full_3.16.401.2_NoBootImg_Twrp3.2.1-2_firmware.zip.
However, this always caused problems when flashing. I have no idea what kind of error was displayed. I think it was because of the unpacking. Then left it.
The latest stock ZIP (2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849) contains the latest firmware anyway. So a clean basis should be created for a later CustomROM installation. Or do I have a mistake here?
What is going on here? Is there a limit to the number of flash operations?
Can't be that the device can only be operated with a stick.
In between the installation of the custom ROMs caused problems. But that always looked like errors when unzipping the images. After downloading the ZIP again, at least the installation went.
Basically I installed the ROMS from the external SD and previously deleted Dalvik, System, Cache, Data and Internal memory and formatted the data in order to really remove all remains of the previous installation.
I'm slowly getting fed up with the idea of buying the device new and setting it up based on its original condition.