Related
SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.
Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct
Can I install viper and su along with this?
MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.
TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.
firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this
Hi!
My Oneplus 6 is rooted and since I updated it to Pie I have a problem. When I plug my (off) phone in order to charge it, it will start but get stuck on the "bootloader is unlocked..." message, never moving on. However if not plugged the message will appear for a few seconds and the phone will start normally. Also, if I plug it while on, there won't be any problem, the phone will charge. On other aspects the phone is doing great and the root is working well.
Any thought?
Thanks a lot,
Corto
Hi, how did you root?
CoffeeMachineSwitch said:
Hi, how did you root?
Click to expand...
Click to collapse
Hi! Thanks for your answer. I used the oneplus.gadgethacks's guide to root (unlocked the bootloader, installed TWRP, Magisk Manager App, then booted into TWRP to install Magisk).
When Pie was released, I booted into TWRP to install the official Pie ROM (9.0.1 cause I have a French phone) then installed the last TWRP Installer, changed the slot (A to B) before rebooting, and booted again in TWRP to install Magisk, before wiping the cache.
I did it two days ago and except for the problem I raised everything is working great and the root it still working!
Up!
Its a normal bug since OB4, mostly happening on custom kernels
byReqz said:
Its a normal bug since OB4, mostly happening on custom kernels
Click to expand...
Click to collapse
Thanks for the answer! So I'm just waiting for a new firmware update?
CortoMaItese said:
Thanks for the answer! So I'm just waiting for a new firmware update?
Click to expand...
Click to collapse
Today i updated to last OOS 9.0.2 using twrp, after i flashed twrp and magisk. All works fine, but i have the same issue, stuck at bootloader and no charging. To charge it, i have to power on and after plug the cable.
Inviato dal mio ONEPLUS A6000 utilizzando Tapatalk
Same here
Same. 9.0.2.
Anyone tried a custom Kernel?
Since 9.0.2 same Problem
I tried Blu Spark Kernel r51. No change.
Yes it is kernel related. Because without kernel it charges. I already tried with 3 different kernel and it happens with all of them
I had this issue as well but not anymore..am not sure what's I changed...am on Open beta 6. Try making sure frimware is up-to-date on both slots.in recovery Flash oos then twrp...reboot into twrp then flash oos then twrp again then boot.
Yes. What magisk version are you using.. version 17.3 or 17.1 cause this issue.. try magisk cannary build 17.4 .I am also in pie stable 9.02 and I did fix it with this version
Iwas on Magisk 17.1 and tried your uploaded Magisk Version.
Issue still present.
I'm on 9.0.2 with blu spark Kernel.
Later i will reflash my Rom an try it with the original kernel.
---------- Post added at 05:22 PM ---------- Previous post was at 04:54 PM ----------
I reflashed the Rom with the actual TWRP and used the original kernel from 9.0.2 with Magisk 17.4.
Nothing changed. Issue is still there.
TheMAD1980 said:
Iwas on Magisk 17.1 and tried your uploaded Magisk Version.
Issue still present.
I'm on 9.0.2 with blu spark Kernel.
Later i will reflash my Rom an try it with the original kernel.
---------- Post added at 05:22 PM ---------- Previous post was at 04:54 PM ----------
I reflashed the Rom with the actual TWRP and used the original kernel from 9.0.2 with Magisk 17.4.
Nothing changed. Issue is still there.
Click to expand...
Click to collapse
Strange. I am on 9.02 ROm, stock kernel , and flash This MAgisk version 17.4 and I can charge my phone normally. I know is a magisk issue, because if you go to the Magisk cannary build section , the developer is aware of this issue. Also happens in Pixel Phones
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Rogue8o8 said:
I had this issue as well but not anymore..am not sure what's I changed...am on Open beta 6. Try making sure frimware is up-to-date on both slots.in recovery Flash oos then twrp...reboot into twrp then flash oos then twrp again then boot.
Click to expand...
Click to collapse
Are you root ???.. Or only TWRP..?? MAgisk is causing this issue
Am rooted...magisk 17.3
You are right, it is a Magisk problem. I uninstalled Magisk and now i can charge my phone switched off.
I will try to reinstall 17.4
---------- Post added at 07:10 PM ---------- Previous post was at 06:49 PM ----------
After reinstalling Magisk 17.4 the issue is present again.
Perhaps there is a difference from which slot you are booting.
Just guessing.
TheMAD1980 said:
You are right, it is a Magisk problem. I uninstalled Magisk and now i can charge my phone switched off.
I will try to reinstall 17.4
---------- Post added at 07:10 PM ---------- Previous post was at 06:49 PM ----------
After reinstalling Magisk 17.4 the issue is present again.
Perhaps there is a difference from which slot you are booting.
Just guessing.
Click to expand...
Click to collapse
MAybe i should wipe everything and install Beta 6 and try with 17.4, But the developer of magisk is already aware of this issue and is working on a solution
Just interested to know many of you have rooted & had any issues. Twice I've been rooted myself & had to use msm recovery program to get me up & running again!
First time it worked well for a few weeks but then I had a charging issue that eventually got me stuck in fastboot. Second time the phone simply gave up after using titanium to remove bloatware
I love my OP7P but never had issues like this on any Samsung device. TWRP backups cause major issues as well!
Had no issues with Root like those. I'm not using TWRP.
No issues with my phone i'm rooted since 1st day and i use twrp
c3drik 67 said:
No issues with my phone i'm rooted since 1st day and i use twrp
Click to expand...
Click to collapse
Whatever you do don't attempt a recovery backup, it won't work
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
mike710_0 said:
Whatever you do don't attempt a recovery backup, it won't work
Click to expand...
Click to collapse
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
No issues, rooted, love it.
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
No I haven't but I'll certain give it a try. Usually when I backup I select everything
Zero issues
Root w/ Magisk 19.3
TWRP unofficial installed
Handful of Magisk Mods
Renovate ROM
Kirisakura custom kernel
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Same. You hit the nail on the head.....backup and restores fine.... But you have to follow these rules....running twrp, magisk, bunch of modules..... everything is kosher
Make sure you're only using stable magisk
The others cause charge issues
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ??
mike710_0 said:
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ?
Click to expand...
Click to collapse
No problem, you are welcome. Enjoy ?
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(
Hi everyone, my dad has been using the oneplus one since it came out. he has been mentioning lately the phone is really slow, so i decided to try and root the phone and get a newer OS for him in hope it runs more smooth.
here where the trouble began, so i had to root the phone in order to get a new OS, so i got as far as installing supersu, which came up with a binary error so i went back out to TWRP and flashed a newer version, when i rebooted phone when in to a loop at the cyonegenmod, it just wont load. so i rebooted back in to TWRP and thats when i went stupid and deleted everything ( with out making a backup ).
So I am now stuck with no OS installed, with out an OS i have been able to adb push files to the internal storage for the roms i have down loaded, i try using sideload to install the roms i have downloaded, which has always failed, with the sideload error executing updater zip / xxxxx/ xxxx/ etc.
questions i have
-the error is due to the wrong ROM i have sideloaded? ( what is the stock version? some say 4.4.2 kitkat? some say cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot )
-if i am using adb sideload, which file should i be using? cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot or cm-13.1.2-ZNH2KAS3P0-bacon-signed ?
- to my understanding ( whihc isnt much ) i just need to find the right stock ROM zip file and sideload it in and it should run again right?
or am i totally wrong and the phone is pretty much dead?
any help would be great
Thanks in advance
I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.
risay07 said:
I'm replying since no one is. I'm not sure about the error but did you factory reset prior to flashing?
You can restore stock rom using the method in this thread https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541.
Other than sideloading, you can use an OTG adapter + thumbdrive. Even in recovery, OTG storage is still detected.
Hopefully you are able to solve your issue.
---------- Post added 10-08-2020 at 12:07 AM ---------- Previous post was 09-08-2020 at 11:59 PM ----------
Also, supersu/superuser is outdated. Magisk is the current way to root now.
Click to expand...
Click to collapse
Thanks for your reply
yeah i did do a factory reset, i then wiped everything including the system
so i am now stuck with NO OS i believe, i did read that post you linked, but i cant access fastboot mode
all i can access is TWRP, so i can push files in the storage, but when ever i sideload or install the Stock roms and reboot the phone nothing is happening just stuck at the one plus logo
any suggestions from this point??
Thanks in advance
Did you try to boot to fastboot by plugging the usb cable while volume up button is pressed? What android version are you on before you wiped? And what is your current TWRP version.
---------- Post added at 03:16 AM ---------- Previous post was at 02:51 AM ----------
IMO, since fastboot and adb sideload not working for you, try going the thumbdrive+OTG cable method. Download any Pie or Q rom and open gapps pico and copy them to the thumbdrive. Connect the thumbdrive to your phone using the OTG cable and flashed it in TWRP.