Related
Unofficial CWM 6.0.2.8 & TWRP 2.6.1.0 for HTC Desire 300 (g3u)
device_htc_g3u v0.77b (05/10/14)
fixed double buffering for twrp
(graphics.c tamed once more, still with 0% overscan involved)
device_htc_g3u v0.77b (25/9/14)
rearranged entries in recovery.fstab
(to speed up manual mounting via recovery menu)
fixed sideload's driver log spam
(errors are only surpressed but it should do the trick)
fixed ext-sd log spam
(blinkfeed-data repurposed as ext-sd)
device_htc_g3u v0.7b (28/8/14)
fixed double buffering
(graphics.c tamed with 0% overscan involved)
fixed stability issues
(cwm's ueventd.rc was evil and a worthy foe)
Full Disclosure
This is my first android project, so go easy on me.
Project Status CWM
Main Features are working.
Backup,Wipe,Restore,Install,ADB,USB-MS,USB-SL
(Tested by factory resetting my device, installing CM10 and reverting back to my backup)
Project Status TWRP
It's still completly untested. So please let me know if everything works as expected.
(Since it's based on the same boardconfig as cwm chances are very high that it'll work fine)
TODO
[CWM] md5 check is slow (by design? missing crypto mods?) [no priority]
Disclaimer
Use at you own risk.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Installation
Your mission, if you choose to accept it, is to infiltrate the bootloader and meet the contact fastboot.
Initiate a conversation by saying fastboot flash recovery recovery.img and wait for his response.
End the conversation with fastboot reboot-bootloader and navigate to the exfiltration point recovery.
Special Thanks
go out to whoever actually fixed the framebuffer issue by teaching minui how to properly align the frames for double buffering.
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(When I think of Maureen I think of two things: asphalt... and trouble.)
Make it flashable throughout CWM? also, is it possible to load backups i made with PhilZ CWM v.6.0.3.7 ?
I have no clue if they work. but knowing that philz is just a variation of cwm and the backups should be just misnamed tar archives.
I guess they could. It's worth a try.
Worst thing that can happen is that it won't boot until you restore a different backup you hopefully made before you started such an attempt
I simply flashed your recovery now and I#M now making a Backup with yours
Your Recovery is already better bc it doesnt have this annoying bug with the jumping screen
Is it possible to upgrade new CWM through old PhilZ CWM v.6.0.3.7 or I have to use ADB?
You have to use adb (fastboot)
luxb said:
You have to use adb (fastboot)
Click to expand...
Click to collapse
Thanks for info.
TWRP is now available but I didn't have the time to fully test it.
Please let me know if everything is working fine.
Also I've yet to find out how to pack recoverys as flashable zips as it was requested, so I guess you'll still need fastboot to get it running.
This shouldn't be that big of a deal since I'm not updating the recoverys that often anyways.
GUYS
I thought this might help you sooner or later.
Due to my expedition into the lands of an unrestorable backup with mismatching md5sums, I conquered this tool
https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=de
it can halp you in mainly 2 ways
regenrating md5sums (just in case something goes wrong like in my case, you'll need it)
Convert TWRP backups into CWM backups and Vice Versa
this is actually really neat, as you dont have to switch between both recoveries anymore
This is a Freemium app, means not all features are free, but the available features in the free version are good enough, the Premium features are Nice to have
hope i can help
Guys, is TWRP tested now, is it working properly?
junk031 said:
Guys, is TWRP tested now, is it working properly?
Click to expand...
Click to collapse
That's exactly what I should be asking, oh wait, I already did in the OP.
Looks like no one has reported any problems so I guess you could say it works without problems.
I have not tested restore so far. But it can install my rom via sideload and it's able to start aromafm, that much is certain.
So, where can i find a stock recovery img? I want to go back full stock before i hand down the mobile.
once again, source?
Crazy good
Installed on my Desire 301s
my reaction is
WHAT?
TWRP has a touch GUI
WHAT?
TWRP does not ANNOYINGLY start when I stick a usb cable into it while it's turned off
unlike what stupid CWM used to do
WHAT?
This is AWESOME
:good:
qwerty123443 said:
once again, source?
Click to expand...
Click to collapse
yeah, we need the source for rebuild our CM...
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
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
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This TWRP Has been Compiled by Myself From Source Using My Rebased Device Tree. Flashing Works Pretty Much Well, No Lags Or Delays.
Download Link: - Click Here To Download
Flashing: - fastboot flash recovery-28032019.img
Internal showing 0 mb ?:
Format data, It Removes Encryption
Credits:
~ TeamWin
~ CM/Lineage/Omni Android
~ SevenMaxs
Kernel: Using Prebuilt Kernel
XDA:DevDB Information
Twrp, Tool/Utility for the Nokia 3
Contributors
RevanthTolety
Source Code: https://github.com/RevanthTolety/device_nokia_heart/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2019-03-28
Created 2019-03-28
Last Updated 2019-03-28
ScreenShot
Reserved
Great! Thanks, but... How do I EXACTLY install this? I mean, with locked bootloader starting from Oreo 8.1 january patch.
Fernandus91 said:
Great! Thanks, but... How do I EXACTLY install this? I mean, with locked bootloader starting from Oreo 8.1 january patch.
Click to expand...
Click to collapse
Hey, If Bootloader is Unlocked Should be Easy to Install. And I havent Tested this Build With Oreo Yet. And i Am Sure this Build Wont Work For Oreo Yet
RevanthTolety said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This TWRP Has been Compiled by Myself From Source Using My Rebased Device Tree. Flashing Works Pretty Much Well, No Lags Or Delays.
Download Link: - Click Here To Download
Flashing: - fastboot flash recovery-28032019.img
Internal showing 0 mb ?:
Format data, It Removes Encryption
Credits:
~ TeamWin
~ CM/Lineage/Omni Android
~ SevenMaxs
Kernel: Using Prebuilt Kernel
XDA:DevDB Information
Twrp, Tool/Utility for the Nokia 3
Contributors
RevanthTolety
Source Code: https://github.com/Revanth/device_nokia_heart/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2019-03-28
Created 2019-03-28
Last Updated 2019-03-28
Click to expand...
Click to collapse
i have installed this recovery its working fine except Mtp not showing on pc,
otg works fine and have flashed rom with.
Does this twrp work on android pie?
link broken
Bug report.
Hello developer of current TWRP for Nokia 3, i am going to report some bugs based on what i have seen and experienced, if you do see this message, please note that i am willing to become a tester for the recovery of this device, i am now going to start stating the problems, please also note that i am using Nokia 3 with Pie ROM, Bootloader unlocked, rooted with Magisk, i am using TWRP 3.2.3 from https://unofficialtwrp.com/nokia-3-root-twrp-3-2-3/, i also believe this is the same with the TWRP that @RevanthTolety made, in other words, you, let me introduce the problems to you.
i have attached the pictures of the bugs, as well as logs, to help you all regarding about this problem, i have messaged all five of you in hopes that some of you are still willing to develop a proper, working recovery for the Pie ROM of this device, or at least team up in making one, anything as long as this project will still continue or something will be done.
Bugs i have found:
1. Decrypting of data, the recovery is asking me for a password and i have no idea what to do, i have never encrypted my device, or anything, and here is what i have done so far:
1a. Formatted data through TWRP, rebooted into recovery and applied root.
1b. Wiped data through TWRP, rebooted into recovery, then applied with root.
1c. All of the above, except this time i flashed no verity opt encrypt, didn't work.
1d. Formatted data through fastboot, rebooted into recovery immediately and applied root.
For the most part, by the time i managed to format or wipe my data/userdata, i am able to gain access on it through TWRP, and the recovery isn't asking me for a password, but once i am able to fully set up my device and it reaches the home screen, not putting any screen locks, just Swipe, rebooting into recovery again, and now it asks me for a password, i tried "default_password" and "password" but it didn't work, at this moment, i can only flash zips through my MicroSD Card, the recovery doesn't have access to my internal storage and i couldn't make a backup with my userdata.
2. TWRP gets replaced with stock recovery if you do not boot into it immediately after flashing, trust me, this is where i got frustrated the most, i was about to smash the phone because of this! I still had to root to ensure that the recovery will stay, or else at next boot the stock recovery will be back.
3. Battery percentage is shown incorrectly, based on the 5 forums i've seen which is all related to porting TWRP for this phone, this error has been very consistent.
4. The recovery keeps showing me a prompt of asking whether to keep System read-only or not, even though i selected the box "Don't show me this screen again.", it still comes back anyway.
5. The recovery complains about '/hidden/emmc_hidden" not being found and all that.
6. I cannot save my language, even though i already toggled it through the settings of the recovery.
7. Touch is very slow during the first screen which is the "Keep System read-only?"
Here are the things i confirmed to be working:
MicroSD Card access
OTG access
Installing .zips
I cannot test the backup and restore option since i can't access data through it, i don't want to lose progress.
The link is broken so i couldn't test the recovery from the true source which is you, hopefully you could still provide me the recovery you actually ported to see if anything is wrong, but if the recovery i obtained from the link i provided is from yours, then please hopefully you could provide a fix for it, you are currently the latest developer for this recovery so i expect you can still do it, the device tree is also still intact and that's the reason why i still have hopes, i want to help not only myself, but also other Nokia 3 users regarding about this, please lets do something so all Nokia 3 phones with Pie ROM can enjoy a fully stable TWRP.
That's all of the bugs i have seen so far, i am going to use my friend's phone who happens to own a Nokia 3 for testing the recovery, if i still haven't received a response within 1 week i will return the cellphone, you could contact me through Telegram, Facebook and other social media sites such as Instagram, i am willing to take the risk, please contact me if you all are still willing to continue with the development of TWRP for this cellphone.
The link doesn't work
I get a 404 error when I click the link
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/
None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the links to my builds anyway. Someone else got OrangeFox working on the forums. Go check it out and use that one instead.
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
TristianX said:
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
Click to expand...
Click to collapse
Crap, I gotta see if there's a way I can get logs then. But you usually can't get logs unless you can boot into a custom recovery...
Gimme a bit to think about this
I tried this image;
https://unofficialtwrp.com/twrp-3-3-1-root-moto-e6/
This process too
https://forum.xda-developers.com/moto-e6/how-to/rooting-e6-surfna-t3965659
and then of course your image from this post.
They all indicate they flash ok from the fastboot status but when it should boot/temp boot/or replace recovery it simply puts me back into normal boot up. I'm using the t-mobile variant with firmware PCB29.73-65-3
Ohhhh I'm excited to see where this can go!
My buddy just sent me a PM and brought up a good point. When dirty porting, I didn't even think to check if the recoveries were both 64 bit. This could be the reason why it's not booting. I'm gonna have another go at this later today and post up another test image for you all if I can figure something out.
Also, just as a heads up, this is for the QUALCOMM MODEL E6. Not sure if there's a MediaTek international model, but this isn't for that.
Well when you post back I'll deff give it a try.
I'm gonna try porting from a different phone, some kind of Aquarius model. It has the same chipset and is 64 bit too.
Also, to those that werent able to flash/boot from it, you unlocked your bootloader right? Forgot to mention that it needs to be unlocked for this to work
I haven't had a chance to give this a go. I'm making sure I understand everything and the risks. More than willing to give it a shot tho
In the process of dirty porting TWRP again to the E6. The only issue is I now have Windows on my PC (for very important personal reasons) and Carliv Image Kitchen is only available on Linux. Here's the steps I need to take to get you guys the 2nd "alpha" of TWRP:
1) Beat Broken Arrow in Payday 2 so I can go back to Linux
2) Download the recoveries/image kitchens for everything again to do the port
3) Do the dirty port and upload it
Currently I'm working on step 1, but it should be done by the end of this night.
NEW RECOVERY IS UP!!! Go download Attempt 2 and see if it gets you any further. If that breaks, try Attempt 3.
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Tim0xff7 said:
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Click to expand...
Click to collapse
Attempt 1 didn't work, waiting on someone to try Attempt 2, and if that doesn't work then 3. If you want to help (I'd really appreciate it) unlock your bootloader and try to boot/flash into one of the images I gave
I'd love to help! Bootloader is already unlocked so I'll try flashing and then get back to you with results
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
FEGuy said:
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
Click to expand...
Click to collapse
PM me. I've got a buddy who's more into kernels and things like that that can probably help us. I'd like to help too, but I can't promise much as I've never done kernel development before
Any headway on this front?
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Daltonyx said:
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Click to expand...
Click to collapse
The TWRP is not working. None of them are. The original poster has said in some recent comments that they plan on buying the E6, so maybe in the future we may get a fully working TWRP. I sure hope so, because my E6 has been collecting dust in my drawer for about a month now. I've been content with my G6 and G7 Power but I can't stand such a nice but unused phone.
Since Visible is pretty much giving away the e6 with any old trade in maybe the op will finally get one.