Related
I pulled this from my phone when it was released yesterday. I'm in OE2 rooted, so this file is from OE2 to OI2
THIS IS NOT AN ODIN FILE!
Build is G925AUCU3BOI2
http://www.mediafire.com/?xksb71307dofox8
designgears said:
*** UNCONFIRMED *** This hasn't been tested.
This is for upgrading from G925AUCU1AOE2 to G925AUCU3BOI2 while retaining root.
Flash with FlashFire
2400258_s6_edge.zip
https://mega.nz/#!S1BnHSSJ!emk9y52XQIaVE0KFyRBwzYmXav0MByBOPtVeZwRCUmw
Flash With Odin
boot.tar.md5
https://mega.nz/#!T05xiaDR!3SVrDVONPGfRU898PSwQ52e631ubArsSNKV4mHPqMXM
modem.tar.md5
https://mega.nz/#!D8gxkA6J!riyZ69REc0DoSBO0O43Ykfa4sI9Pl5gRVSljWTqS2lc
-----------------------------------
In Flashfire select "Flash ZIP or OTA"
Select 2400258_s6_edge.zip from your sdcard
Leave all of the settings default and flash.
After it has flashed, reboot to download mode and use Odin to flash the updated kernel and modem.
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Once the phone has rebooted you should be on G925AUCU3BOI2.
Click to expand...
Click to collapse
how to use this..i am in stock 5.0.2
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Did you retain root?
Yes. I was prepared to lose it imo, but still have it so that's kind off weird. But I won't be complaining. Now I'll wait for deodoexed rom then I can go xposed with flashfire..
Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Can you please post pic to confirm you have root still on 5.1.1 and please provide instructions on how you sideloaded this with adb?
I unlocked my phone and i still didn't get the update yet is that a problem?
Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
How did you do this? I get a DM-Verification error in recovery.
Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!
tronghienk32 said:
Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!
Click to expand...
Click to collapse
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.
teamfresno said:
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.
Click to expand...
Click to collapse
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.
Rodman101 said:
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.
Click to expand...
Click to collapse
The computer. I put the phone into recovery mode, then I scroll down to install from ADB, but I always get an "ADB is disabled". I thought you have to get into there and then ADB sideload xxxx.cfg from the command prompt.
Am I doing it wrong?
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
It worked and you remained rooted?
krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?
srideep said:
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?
Click to expand...
Click to collapse
same problem!
krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
AT&T? Seems like you have a custom recovery. We don't have "ADB sideload", it comes up as "install from ADB".
Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Rodman101 said:
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Click to expand...
Click to collapse
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip
Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
mrRobinson said:
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip
Click to expand...
Click to collapse
ADB sideload right?
Hi there!
I have a TX1085, it is already unlocked and rooted and has the CM Recovery installed. But before the CM Recovery I had the TWRP Recovery installed and tried to use it to flash CM12, which I had put on the SD-Card. It kept on telling me that mounting the system failed. Unfortunately I wiped everything via TWRP Recovery without creating a backup. Then I installed the CM Recovery to try again. Now, if I try to flash via CM Recovery (apply update) it doesn't show anything in my internal storage and I can't connect via adb using Ubuntu (Terminal tells me either "device not found" or "device offline".)
Any suggestions?
Greets
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
psssss said:
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
Click to expand...
Click to collapse
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
pyq said:
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
Click to expand...
Click to collapse
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
josuearisty said:
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
pyq said:
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
Click to expand...
Click to collapse
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
Click to expand...
Click to collapse
I am using Linux without Android SDK, but I have working fastboot and adb installed.
josuearisty said:
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
try to flash stock firmware
kaktusmaier125 said:
try to flash stock firmware
Click to expand...
Click to collapse
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Click to expand...
Click to collapse
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
josuearisty said:
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
pyq said:
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
Click to expand...
Click to collapse
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
josuearisty said:
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
If I use the "fastboot boot CM_recovery.img" command the phone installs it and then starts into TWRP. Except for that nothing changes. How can I continue?
rotorbudd said:
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
Click to expand...
Click to collapse
If I try to make a tick (as to mount) system the phone vibrates but doesn't tick system, so I can't mount it this way.
pyq said:
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
Click to expand...
Click to collapse
Yes you can
It's been a long time since I got back into the root game, so I was just wondering if there is a root guide for the OnePlus3T on Mac, or is the root guide compatible on both Windows and Mac through the terminal? If there is can you please link it to me. Thank you.
-Galaxys3world
Yes adb fastboot.
It is pretty much same. You need ADB tools (these are different than Windows, just download correct ones), recovery image and SuperSU zip file. Process is same - adb commands, then go to recovery on phone, flash zip file.
Someguyfromhell said:
It is pretty much same. You need ADB tools (these are different than Windows, just download correct ones), recovery image and SuperSU zip file. Process is same - adb commands, then go to recovery on phone, flash zip file.
Click to expand...
Click to collapse
Is there a link for a the guide on XDA?
galaxys3world said:
Is there a link for a the guide on XDA?
Click to expand...
Click to collapse
Just follow any existing root guide here in the 3T Guides section.
Someguyfromhell said:
Just follow any existing root guide here in the 3T Guides section.
Click to expand...
Click to collapse
Can't find any in the section for some reason.
Bad luck then. Found a couple.
dreinulldrei said:
Bad luck then. Found a couple.
Click to expand...
Click to collapse
Does it matter which ADB & Fastboot version I have installed on my Mac for root? Does it have to be the latest version?
galaxys3world said:
Does it matter which ADB & Fastboot version I have installed on my Mac for root? Does it have to be the latest version?
Click to expand...
Click to collapse
Use this zip for adb and fastboot on Mac. From a Google worker, without the need for Android studio.
https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
And don't forget it's ./adb and ./fastboot on Mac. Otherwise it's just like the guides. And, to transfer files from Mac, you need some app like Android file transfer. Google it. Or use ADB push...
/Söder
soder said:
Use this zip for adb and fastboot on Mac. From a Google worker, without the need for Android studio.
https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
And don't forget it's ./adb and ./fastboot on Mac. Otherwise it's just like the guides. And, to transfer files from Mac, you need some app like Android file transfer. Google it. Or use ADB push...
/Söder
Click to expand...
Click to collapse
Would this guide work better an easier on Mac?
https://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Don't know. Use my file for ADB and fastboot. Then normal guides here..
EDIT: Just unzip the file I linked to, and in terminal go to folder and typ ./adb devices when booted in to system, and ./fastboot devices when in bootloader.
Then you can follow this guide to get TWRP and root with SuperSU.
I don't use SuperSU, but Magisk and phh's root superuser instead. I then flash dm zip and then Magisk. If you're gonna use SuperSU I think dm zip shouldn't be used.
Also, use the beta1 of TWRP in post 550.
GLHF!
/Söder
soder said:
Don't know. Use my file for ADB and fastboot. Then normal guides here..
EDIT: Just unzip the file I linked to, and in terminal go to folder and typ ./adb devices when booted in to system, and ./fastboot devices when in bootloader.
Then you can follow this guide to get TWRP and root with SuperSU.
I don't use SuperSU, but Magisk and phh's root superuser instead. I then flash dm zip and then Magisk. If you're gonna use SuperSU I think dm zip shouldn't be used.
Also, use the beta1 of TWRP in post 550.
GLHF!
/Söder
Click to expand...
Click to collapse
OMG, I forgot the link.
https://forum.xda-developers.com/showthread.php?p=69795572
/Söder
I am stuck. I tried to update to OREO and the update wouldnt take. I kept saying that update is for "oneplus 3t" and you have " ". I wiped device and have been trying to get an OS back on my device. I tried using ADB with ADB sideload through TWRP and the Command Prompt but I get an error "you need adb 1.0.32 or newer to sideload to this. My ADB is version 1.1.3 and TWRP is 3.1.1-2
I dont know what else to do........
Try a slightly older version of ADB. Also make sure you kill the old adb.exe in taskmanager since it runs on the background.
Read the OP in the official Open Beta 16 forum. All answers are there.
zdaddi said:
I am stuck. I tried to update to OREO and the update wouldnt take. I kept saying that update is for "oneplus 3t" and you have " ". I wiped device and have been trying to get an OS back on my device. I tried using ADB with ADB sideload through TWRP and the Command Prompt but I get an error "you need adb 1.0.32 or newer to sideload to this. My ADB is version 1.1.3 and TWRP is 3.1.1-2
I dont know what else to do........
Click to expand...
Click to collapse
Did you follow all the steps correctly? I think this occurs when one doesn't flash the right firmware beforehand. I also believe that you require an oreo compatible recovery such as blu spark.
All the flashing instructions are in the 2nd post of this thread: https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240
Here is the Zip file containing edited xml files to stop unbrick tool to erase your internal data.
Link to edited script : https://drive.google.com/open?id=0Byn304jb_hlqZ29XM1oxUUZwbzg
(Personally I made , Tested and used these files and successfully recovered device without data loss)
Link to the unbrick tool download : https://mega.nz/#!Q1YnTTAT!gnLf6NEkSRy7W-WY8J0H2SmJJLzO91-vReKx7B1VVpI
Thread : https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306.
Steps to be followed :
1. Download the unbrick tool
2. Extract the Zip File.
3. Download my edited script zip file.
4. Extract the zip and copy and replace the extracted files in the unbrick tool.
5. Follow the steps in the unbrick thread .
Dont forget to hit Thanks Button ............
Sent from my OnePlus3T using XDA Labs
Push the ROM to your phone using the adb push command and flash from your phone
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
I was talking about the Miui 12.5 update but it's good to know it
ZeroNoTime said:
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
Click to expand...
Click to collapse
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
4. Have you tried simply formatting data from TWRP before attempting to boot?
Dobsgw said:
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
Click to expand...
Click to collapse
Yep, i tried everything but doesn't work
I only have access to twrp and fastboot but the usb connection doesn't work
Dobsgw said:
4. Have you tried simply formatting data from TWRP before attempting to boot?
Click to expand...
Click to collapse
Yep but shows the message e: Unable to decrypt FBE device