Related
Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.
Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users
FBis251 said:
Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users
Click to expand...
Click to collapse
Soon as Heimdall can flash the modem properly, I will. lol. It fails, git issue opened on it, gave Heimdall dude all my logs, so we'll see. Also, since most people get bootlooped and mess up the param, and other files trying to flash everything under the sun, this package was the best way to do everything in 1 step.
The package though will work for linux/osx, etc, just use that Heimdall version. I just have Windows directions as I assume most people will be on Windows. You can load the gz though into any Heimdall and flash it.
getochkn said:
Welcome T959W users.
*********
Great Job man.
That was just awesome and a single click did the trick.
As instructed , i installed an ICS and that took care of the modem & signal as well.
Thank you so much.
Click to expand...
Click to collapse
Was it necessary to quote the entire post?
Hi getochkn,
Thanks for this very informative guide.I seriously thought my son's phone was bricked, but after following your instructions, everything was restored perfectly.The only hiccup I had was, at step #6 Heimdall showed the device as detected, but when I went to flash it, it said that it couldn't detect the device.So I installed the drivers manually through Zdiag and it was smooth sailing from there.
I then flashed CM9 and noticed in your sig that you are running RemICS Rom so I flashed that and everything is looking great so far.
Thanks for taking the time to make this guide for those on the T959W
Glad it worked for you and you saved the phone.
getochkn said:
Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.
Click to expand...
Click to collapse
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.
kdkd008 said:
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.
Click to expand...
Click to collapse
You flashed this on a t959v? With bootloaders? And it works?
TwitchyEye said:
You flashed this on a t959v? With bootloaders? And it works?
Click to expand...
Click to collapse
No bootloaders in my package. For some reason the "W" model, it's impossible to flash the bootloader, the modem and EFS partition (I think it's that, been a while since I played with it) from Heimdall or Odin, so it's sort of impossible to brick them as you can never flash those items. Worst you can do is flash the param from the "V" to the "W" and it corrupts the bootup image but works fine otherwise.
Oh I see. Thanks for clearing that up, I've been wondering for a while what would happen.
Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.
noobishuser said:
Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.
Click to expand...
Click to collapse
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.
getochkn said:
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.
Click to expand...
Click to collapse
Thank you very much, I thought I broke my phone.
Do you have instruction on how to flash a modem?
The link you provided only gives a file, I'm not sure how to flash it.
I also looked for instruction here:
http://forum.xda-developers.com/showthread.php?t=1001759
but got stuck on step 7 as the file provided does not have a .tar file.
That is a very old thread. FBis251 has a thread with all the modems and you just have to flash them via recovery. Ill look for the thread link and post it back.
This is it here.
http://forum.xda-developers.com/showthread.php?t=1192436
Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.
noobishuser said:
Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.
Click to expand...
Click to collapse
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.
getochkn said:
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.
Click to expand...
Click to collapse
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...
noobishuser said:
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...
Click to expand...
Click to collapse
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.
getochkn said:
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.
Click to expand...
Click to collapse
Q here, does this modem support the 850mhz frequency and can I flash it to a T959V
Forgot to say it's the wcdma band
I'm new to this phone, exchange an IPhone 3GS for this one.......
Sent from my XT925 using xda app-developers app
Out of curiosity, is there way to brick this device to stage that for example warranty service can`t find out that it is self-inflicted?
Surely, flashing a bootloader not intended for the device is the best way to brick it?
i will do in that way :
flash engeniereng bootloader
flash a rom not suitable for your device ( ex. rom for 9200hk )
if still works, flash wrong pit file or modified wrong one )
Why would someone do that anyway???
XxM4tzexX said:
Why would someone do that anyway???
Click to expand...
Click to collapse
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
PeK_m said:
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
Click to expand...
Click to collapse
Dark ideas! I like it!
I bricked my G920F trying to get back to stock-rom. Nothing would work, Odin failed time after time (cm.bin). I could flash TWRP and used ADB to get back to stock-recovery, connected to smart-switch and performed emergency restore. Failed again.
I took it to a Samsung servicepoint (talking about Holland) and they immediatly found the custom flag. Phone wil be send over to Samsung now and, according to the lady at the servicepoint, Samsung does not even check. They just reflash it and send it back under full waranty. All I can do now is hoping she is right....
Still figuring out why everybody but me can restore a bricked phone through ODIN.
Team Win Recovery Project
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.
What is TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How to flash and setup it completely?
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and RMM Bypass v3 zip.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Power, Vol + and Vol - buttons together)
- Connect your phone in your PC, open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now copy the no-verity-opt-encrypt and RMM Bypass zip you downloaded before and flash them (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.
Download:
Galaxy A8 2018 (jackpotlte):
https://twrp.me/samsung/samsunggalaxya82018.html
Galaxy A8+ 2018 (jackpot2lte):
https://twrp.me/samsung/samsunggalaxya8plus2018.html
Sources:
Kernel Source Code: https://github.com/devkingsteam/android_kernel_samsung_universal7885/
Device Tree (jackpotlte): https://github.com/TeamWin/android_device_samsung_jackpotlte
Device Tree (jackpot2lte): https://github.com/TeamWin/android_device_samsung_jackpot2lte
Changelog:
Check Post #2.
A8 2018 Community Telegram Group:
Invite Link
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ananjaser1211 and @McFy for their help and support
- @SaboorTheCool for testing out the recovery
XDA:DevDB Information
TWRP for Galaxy A8+ 2018, Tool/Utility for the Samsung Galaxy A8+ (2018)
Contributors
BlackMesa123
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-20
Created 2018-07-18
Last Updated 2019-06-17
Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
20180921 (3.2.3-0)
- Updated kernel source code
- Fixed USB OTG
- Enabled FBE support (general AOSP only, Samsung method is still not supported)
20180730 (3.2.3-0)
- Removed /preload from partitions table
- Added /system_image (raw system partition backup)
- Enabled software encryption support (general AOSP only, Samsung method is still not supported)
20180718 (3.2.2-0)
- First release
Reserved
Plan to do nightlies for TWRP?
SRIHARI_GUY said:
Plan to do nightlies for TWRP?
Click to expand...
Click to collapse
Nope, gonna update it just if omni/A8 sources gets updated
TWRP 3.2.3 released. Enjoy!
Will this work with A8+ oreo?
Bad.Server said:
Will this work with A8+ oreo?
Click to expand...
Click to collapse
TWRP isn't built for a specific OS since it's totally separated from OS, so it works on all of them if there aren't significately changes in bootloader/kernel. Even if it was, mine is compiled with latest Oreo kernel source code and based on omniROM 8.1, so...
I lost mobile network?
Hi all. I have an unlocked A8+. I rooted when I had Nougat. I installed the oreo firmware from Columbia and the phone works great. I like the enhancements. I followed the instructions to install the new twrp. Took a bit but got magisk working and root explorer but had issues with busy box and titanium bkup. No biggie. The issue I had is the when I went to send a text I got an error and then I noticed I had no signal. So I checked and low and behold I had no mobile networks in the connections list. Does anyone have a clue as to why it disappeared? Did I miss something? I tried it 2 times with the same result. And help would be greatly appreciated.
P.S. OEM unlock is enabled as well as USB debugging enabled also.
Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.
BlackMesa123 said:
Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.
Click to expand...
Click to collapse
Good work
Help Flash odin erro
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Please read and follow the RMM State guide linked in OP.
Congrats on getting Official xD
vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Same thing happened to me.
had to download and install the whole firmware.
downloaded from this
https://forum.xda-developers.com/galaxy-a8-plus/how-to/pie-a8-pie-a730fxxu4csb9-t3908703
probably happened because I still have RMM lock (can't do anything to unlock) in oreo. Bootloader got unlocked in Pie so I thought i can now flash custom binaries. Turns out, you still can't
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its worst than frp locked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, system app we only need without those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies our needs but it comes with risk. Even we have same device model flashing custom rom in other but same device can experience bugs and some are not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and if something went wrong you're the one responsible and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
If you really want to start rooting your phone just like me, all you need to do is read, study and understand every aspect, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time of visiting xda, I have a positive feeling and also I'm completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing suddenly stop me to proceed.
(Read more)
To fully understand the procedure, it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need privilege access to these "four letters" R O O T.
We all know that with a stock os, accessing root surely not possible, it need the superuser (su) to grant permission to access the root and installing su ofcourse is not just like the ordinary apk that can easily be installed, it needs to be flash manually but not in odin. It will be flash in recovery mode but flashing it there still be impossible because that su.zip file cannot be flashed with the stock recovery, you need to modify the recovery mode... Do you how to mdofy it? Well, if you can, that's good and you will have a unique version of it, but me? No way I can modified it...
So, to those people like me who cannot make a customized recovery, NO WORRIES! good news for us because xda geniuses made us for free, custom recovery like twrp, hurray!
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
Next step to do is yet very simple and easy up to the last step of the procedure...
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its wosrt than frp lovked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, our only and always be our favorite to do... which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, having an app that we need and removes those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies your needs but it comes with risk. Even we have same device model flashing custom rom some device can face bugs some is not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
Like me, if you really want to make it happen, all you need to do is read, study and understand, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time visiting xda, I have a positive feeling and completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing stops me to proceed.
(Read more)
To fully understand the procedure and , it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need access to these "four letters" R O O T.
Accessing it is not possible, I need the superuser to grant me permission to access the root and su ofcourse is not just like the ordinary apk that can easily be installed, it will be flash, not in odin but recovery but flashing it will not be possible because that su.zip file cannot be flashed with the stock recovery, but custom recovery can like twrp.
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
***Next step to do is very simple and easy up to the last step of the procedure...
Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
Can do it with a couple of swipes to wipe (format data), reboot to recovery again flash su, flash no-verity and also RMM bypass zip just for sure... after that fun stuff can now be available, flash custom roms, blah.. blah.. etc. Boot normally without worries.
About the:
" ***Next step to do is very simple and easy "(above)
Yet very simple and very easy, that's the actual problem dive-in...
As I've mentioned above about having this device from such time and putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS"
The next step was about formatting and it's a must thing to do to make it work and using unrooted device is impossible to make NANdroid backup, the 64Gb internal storage were almost full and because of that it makes much harder backing-up...
Any advise?
Please help...
@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte
mark0021 said:
bla bla bla...
Click to expand...
Click to collapse
Well the answer is no of course, if you don't wipe your /data partition it will be unreadable from TWRP, equals you can't flash anything that needs to write data in that partition, like Magisk itself. Was it necessary to write that whole post when all you're asking is just a way to avoid /data partition wiping? You basically blamed the "master XDA devs" (which I feel like I'm part of it, sort-of) because "they made the steps for root so hard". I imagine you know "we" aren't the "bad guys that wanna make you lose your precious time" and if I wrote all those steps to follow in the main post (that you copy-pasted twice in your post, without any sense I'd add since users can read the steps from there instead of reading a 1500 lines post) are there because... they are needed? You even noticed and wrote yourself that if you miss one you break something in the way and you get no TWRP if you don't follow all the steps correctly... Wanna blame someone? Then blame the OEMs that add all those security features instead of blaming people that dedicated their time to bypass those and bring you custom softwares for your phone.
inunxelex said:
@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte
Click to expand...
Click to collapse
Sorry but I'm not interested on that phone (since I don't even own it), ask the device tree maintainer to do that.
pls someone help me. Everytime I install TWRP through odin my entire system wipes, and in TWRP it recognizes as 0mb. How can I install TWRP without wiping the entire phone?
WARNINGS:
1.) THIS IS FROM blinoff82's Guide:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
2.) I'm explaining how I got EVOLUTION X to work. However, this applies to other ROMS I have mentioned below. Just without the GAPPS step. I might include guides on those in the future and videos.
Hello,
This is a quick prequel to what I am actually posting about.
PREQUEL:
I tried to install these ROMS: Lineage 16, Lineage 17, SyberiaOS, and ElementalX.
None of them would work with any of the INSTALLATION instructions provided.
I researched a lot of different guides, I read about Slots, etc. I have been a Computer Science Undergraduate for almost a year now(I know this has nothing to do with this. All it shows is that I know how to follow simple rules of Logic).
I decided I was going to figure it out myself. This is what worked for my device. IF anyone can tell me why this is the only way it works for me, please inform me(Just for the first time installation. Not for updates). Thank you.
Guide:
1.) Wipe everything(check all the options in the WIPE category in TWRP) and format data after that.
2.) switch to the other slot(slot you currently aren't in) without rebooting through the settings menu
3.) Repeat step 1
4.) USE the MSM tool to get to 9.0.8
4a.) How I get this to work is, connect the phone to USB, open MSM tool with admin, Click Start, try to power off the phone. Eventually, the MSM tool will start, leave the phone alone.
5.) After the reboot, go through settings skipping everything and agreeing to everything. SET UP A PIN OR A PATTERN .
6.) Go to settings, spam the build number in About Device until Developer Mode is given.
7.) uncheck update system, check advanced reboot and debug, and switch the USB connection mode from CHARGE to FILE TRANSFER.
7a.) PUT OOS 9.09 INTO INTERNAL
8.) Go to Fastboot through the phone's power menu. Unlock Bootloader.
8a.) Boot into the OFFICIAL TWRP MENU by following the steps in the Bootloader guide.
9.) Factory Reset. Wipe system
10.) Install Full ROM (9.09), Wipe Dalvik, Install Twrp and Wipe Dalvik
11.) Reboot Recovery, Repeat Step 10
12.) Factory Reset, and FORMAT(NOT WIPE) Data
13.) Reboot into Recovery
14.) Put 9.09, TWRP, EVO X ROM, and MAGISK 20.1 (OR Most Up-To-Date Version 20.1+) on Internal
15.) Factory Reset
16.) Repeat Step 10, Reboot Recovery, Repeat Step 10
17.) Flash Evo and TWRP
18.) Factory Reset, Wipe Data and Cache
19.) Reboot System
20.) Set the phone up and Set up a pin
21.) Reboot into Recovery after making sure you have Dev Mode and Debugging enabled
22.) Flash Magisk
23.) Reboot
24.) BE HAPPY!
I hope you guys take the time to appreciate my Guide and Let me know of any way I can make this guide better.
Thank you.
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
J0nhy said:
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
Click to expand...
Click to collapse
Thanks for that worthy contribution to this thread.
I appreciate OP's guide. I've had nothing but problems installing a custom ROM on my 6. I've been installing custom ROMs since my Galaxy S2, so I'm familiar with the process. Nothing has worked so far though. I'll give this a shot.
J0nhy said:
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
Click to expand...
Click to collapse
I'm not trying to be mean, however, I have been rooting and putting ROMs on my phones for nine years now.
I kept up with the whole Slot A/Slot B update. However, after a while of running stock OOS, I ran into the issue of NOT A SINGLE GUIDE or A SINGLE ROM working on my phone.
I am just sharing what I thought people would find helpful. Every once in a while I see people posting, "This Guide/ROM didn't work for me. I have followed all the steps to the LETTER".
I figured it out for myself, and I am sharing it with our community on XDA. I really hope this helps. It's my first post.
Thank you for your comment.
Yippee38 said:
Thanks for that worthy contribution to this thread.
I appreciate OP's guide. I've had nothing but problems installing a custom ROM on my 6. I've been installing custom ROMs since my Galaxy S2, so I'm familiar with the process. Nothing has worked so far though. I'll give this a shot.
Click to expand...
Click to collapse
Thank you for your comment, what you are describing is my exact issue with what I have been dealing with. I really hope this helps.
If it doesn't, I will try and upload a video for this too. Good luck!
I'm pretty sure your issue has to do with firmware mismatch, (also maybe not factory resetting), nothing more. The steps you have provided are really for beginners who have no idea what is wrong with their installation procedure. Also, some ROMs are still on 9.0.9 fw where other ROMs are on 10.0.x, so for ROMs that require OOS 10 fw, you should upgrade to OOS 10 instead of 9.0.9.
EDIT: I'm pretty sure the part where you need to set up a PIN or pattern is only required for older builds of Syberia (and maybe current builds also).
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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-nairo.img
drive.google.com
Source code:
Device Tree
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G 5G Plus
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-27
Created 2020-08-27
Last Updated 2020-08-27
Excellent, can't wait to get a modding community for this device.
Looking forward to see how long I can get this to be used, I hope 3-4+ years.
after i booted into recovery using
fastboot boot twrp.img
i recieved the decryption message with one letter already written inside if i try it it says decryption fail ... and i cannot use sd card also because it cannot be accessed as well
what should i do to bypass encryption ? i tried format data and ended up reflashing stock rom via rescue and smart backup application ... i only want to root via magisk
Everytime you want to boot into TWRP you have to boot using fastboot flash recovery. Is there anyway around this as flashing doesn't seem to work.
What is working and what isn't.?Also, did anyone try to use GSIs on this device? Cheers
shanere51 said:
Everytime you want to boot into TWRP you have to boot using fastboot flash recovery. Is there anyway around this as flashing doesn't seem to work.
Click to expand...
Click to collapse
I've a feeling it's because there are two recovery partitions (A/B) and the flashing tools expect to see one:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-04-21 02:32 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-04-21 02:32 recovery_b -> /dev/block/sdf20
nairo:/ $
@vache: Does twrp-3.4.0-0-nairo-test1.img work for Moto G 5g Plus XT2075-3?
New build :
-Updated to TWRP 3.5
-Fix slot switching
-Added fastbootd support
-Fix boot when flashed
-Fix sideload feature
Download : https://drive.google.com/file/d/1soSNdeYuvU0-P-QAJPuAoVnmWSQS8JmD/view?usp=sharing
vache 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-nairo.img
drive.google.com
Source code:
Device Tree
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G 5G Plus
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-27
Created 2020-08-27
Last Updated 2020-08-27
Click to expand...
Click to collapse
Would it work for motog 5g indian varient
Yangasto said:
Would it work for motog 5g indian varient
Click to expand...
Click to collapse
No, they're completely different. This is for moto g power, g8 power, g fast, g8 and g stylus. If not more. Lol.
Edit lol nevermind I'm just a complete idiot. I got distracted by the vache qui rit smoking weed profile picture, it's perfect
vache said:
New build :
-Updated to TWRP 3.5
-Fix slot switching
-Added fastbootd support
-Fix boot when flashed
-Fix sideload feature
Download : https://drive.google.com/file/d/1soSNdeYuvU0-P-QAJPuAoVnmWSQS8JmD/view?usp=sharing
Click to expand...
Click to collapse
Can this TWRP work on the Moto 5G Ace. We need a lot of help over on our side. From the specs it looks like the exact same phone branded differently. We have root but we're on the A/B system with Super Sparschunks. Thanks.
Articul8Madness said:
Can this TWRP work on the Moto 5G Ace. We need a lot of help over on our side. From the specs it looks like the exact same phone branded differently. We have root but we're on the A/B system with Super Sparschunks. Thanks.
Click to expand...
Click to collapse
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
dagey said:
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
Click to expand...
Click to collapse
I think we are going to have to be hands on. Step one is creating the device tree. I don't have my linux live usb with me but I found this. https://github.com/SebaUbuntu/TWRP-device-tree-generator
Once we get our device tree maybe we can get a more experienced DEV to build the TWRP.
dagey said:
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
Click to expand...
Click to collapse
Flashing it did not work. Flashing it did not work. Been trying everything to get this POS to R/W.
We need a delete post button around here.
Articul8Madness said:
I think we are going to have to be hands on. Step one is creating the device tree. I don't have my linux live usb with me but I found this. https://github.com/SebaUbuntu/TWRP-device-tree-generator
Once we get our device tree maybe we can get a more experienced DEV to build the TWRP.
Click to expand...
Click to collapse
Nice way to encourage Vache. It's not like he's getting paid to do this, or owes us anything.
I'm considering buying this phone, and appreciate any and all work people are doing on it.
Pheckphul said:
Nice way to encourage Vache. It's not like he's getting paid to do this, or owes us anything.
I'm considering buying this phone, and appreciate any and all work people are doing on it.
Click to expand...
Click to collapse
What are you speaking of? Vache doesn't even HAVE my variant. And FYI I'm not getting paid either for all the work I've done on the variant, so you can dial that back.
If you get the phone just know TWRP isn't working on it right now (that I happened to have built). It is rootable and I do have R/W access finally.
Articul8Madness said:
What are you speaking of?
Click to expand...
Click to collapse
Perhaps it's a language issue, but I thought you were being very harsh on him without reason.
Thank you for the info on rooting. I've decided to buy this phone, and will be picking it up later today.
Pheckphul said:
Perhaps it's a language issue, but I thought you were being very harsh on him without reason.
Thank you for the info on rooting. I've decided to buy this phone, and will be picking it up later today.
Click to expand...
Click to collapse
Nah, not being harsh. Welcome to the Moto brave new 5G world.