Develop Bugs

[ROOT][Samsung Galaxy Tab E][sm-t377p/sm-t560nu]

WHATS THIS?
This is my port of CF-AUTOROOT for the Samsung Galaxy TAB E.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE or a TWRP backup in case of problems. This will trip the knox counter.
Flash with ODIN 3.10.7 in the AP slot.
Load the respective file below into the AP slot and hit start.
cfautoroot_sm-t377p.tar
cfautoroot_sm-t560nu.tar
NOTE: ON SOME 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
STOCK TWRP IMAGE FOR SM-T377P
This is a link to the stock system, boot, modem image for the T377P in case anyone needs it. Needs to be restored with twrp.
Thanks to @shawn1976 for providing this.
https://www.dropbox.com/s/skuwsbzm2zigd83/sm-T377PVPU1AOJ5-boot-system-modem-only.zip?dl=0
Credits: Chainfire and my testers - Phrozen99 and nates730
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

FRP lock
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.

Jasn7766 said:
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.
Click to expand...
Click to collapse
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?

ashyx said:
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?
Click to expand...
Click to collapse
That was my plan ...however they do not support this model number yet so its not available to be reflashed. I checked sammobile as well figuring I could download firmware and use Odin to reflash and same situation.

There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.

Okay....will try and find that one.

Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!

Badob said:
Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!
Click to expand...
Click to collapse
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/

ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
Click to expand...
Click to collapse
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!

Badob said:
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!
Click to expand...
Click to collapse
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.

ashyx said:
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.
Click to expand...
Click to collapse
Thanks For the help!

Where do I get TWRP for Tab E T560, and how do I install it?
Thank you.
Edit: Found the answer.

ashyx said:
There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.
Click to expand...
Click to collapse
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.

I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse

Stevenwsmith said:
I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
Click to expand...
Click to collapse
Surprised recovery doesn't work, considering the 2 devices are identical specs.
Try installing Twrp, you'll probably find that works OK.

Jasn7766 said:
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.
Click to expand...
Click to collapse
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.

JohnICon said:
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.
Click to expand...
Click to collapse
What's the issue?

Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.

JohnICon said:
Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.
Click to expand...
Click to collapse
You realise you can't flash a custom rom with odin?
Also when you flash the stock t377r4 firmware what part fails?

The aboot fails every time I try to flash it

I need some help downgrading/rooting my LG G4.

Hello amigos, just to clarify i'm new to XDA so lets get to it then shall we!
So I bought this LG G4 from a guy on eBay, and it basically just arrived today. So the weird thing about the device is, It has a Anti-Rollback Version 4. Ive personally never seen this especially in the UK. Isn't it just the US that's supposed to be effected by these issues???
Is there any way of getting around this or what ever?
Its on Android 6.0 and its the H815 variant, I've tried booting into the boot-loader and that doesn't work (Yes I've used ADB but that didn't work either I also used recovery which for some reason I can access but not the boot-loader ) This is the main issue. There is also something else that doesn't make any sense. The device has an update from LG, It downloads perfectly fine but when it goes to flash the update it just doesn't flash. It comes up with an error. That's all it says in the recovery, error. Yeah that's about it really. The phone works perfectly fine on 6.0 but I just wanted to see if one of the greight minds here could assist me with this issue or just upfront call me stupid for wasting my money on an old phone :laugh:.

Which H815 variant is it?
EU, USA, TR, Int'l?

LPCG7 said:
Which H815 variant is it?
EU, USA, TR, Int'l?
Click to expand...
Click to collapse
It looks to be the EU version to me. I cant be too sure though. Its running on the OPEN EU firmware though. (H81520D)

go to:
settings > about phone > hardware info

LPCG7 said:
go to:
settings > about phone > hardware info
Click to expand...
Click to collapse
Yes the model number is LG-H815. It doesn't say if its EU or INT or what ever.
Is this unusual?

Sileo2056 said:
Yes the model number is LG-H815. It doesn't say if its EU or INT or what ever.
Is this unusual?
Click to expand...
Click to collapse
That's on the page below. There it gives you software version....

mcduffie2010 said:
That's on the page below. There it gives you software version....
Click to expand...
Click to collapse
H81520D is the software version

you need to unlock the bootloader before accessing it first.
this is the only official way for so.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
If I may ask to better assist you, what do you plan on doing exactly?

LPCG7 said:
you need to unlock the bootloader before accessing it first.
this is the only official way for so.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
If I may ask to better assist you, what do you plan on doing exactly?
Click to expand...
Click to collapse
Firstly I plan on rooting and adding TWRP as I did on my old G3. I tried to use LG's method but it did not allow me to fastboot. When I used ADB it just well, restarted the phone. I used the command adb restart bootloader as it states on the unlocking site. I used administrative permissions. Whats unsual is, I can use adb restart recovery perfectly fine to get to the stock recovery.

The confusing thing for me is, the device has the antirollback version 4
Its the EU version of the H815. It makes no sense!!!!
I'm trying to figure out what could have caused this to happen mainly... The only version with antirollback version 4 is the LS991 ZVF... How is this even been done to this thing!? Its running on the H81520D firmware which 0 of them have the antirollback version 4 that i'm aware of. The bootloader is mysteriously inaccessible by anything I do! This is really bugging me now. Could this be a franken device?

Before proceeding further, check whether your device has SN 404 or other. It is found by removing your battery or checking on the box labels.

LPCG7 said:
Before proceeding further, check whether your device has SN 404 or other. It is found by removing your battery or checking on the box labels.
Click to expand...
Click to collapse
Nope it's sn 606....

Sileo2056 said:
Firstly I plan on rooting and adding TWRP as I did on my old G3. I tried to use LG's method but it did not allow me to fastboot. When I used ADB it just well, restarted the phone. I used the command adb restart bootloader as it states on the unlocking site. I used administrative permissions. Whats unsual is, I can use adb restart recovery perfectly fine to get to the stock recovery.
Click to expand...
Click to collapse
To begin with, I rooted mine by downgrading to LP stock rom as rooting MM is not quite easy using this link : https://forum.xda-developers.com/g4/help/how-downgrade-g4-h815-t3264864
Then I had FIsH twrp installed cause I couldn't unlock my BL using : https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
>>ITS RISKY<<
Sileo2056 said:
The confusing thing for me is, the device has the antirollback version 4?
Click to expand...
Click to collapse
Secondly, yours has ARB v4. So there are some hardwork involved in finding a kdz that won't brick your G4 on flashing. As you say it is very much confusing. So do proceed ahead only after properly checking your informations and cross examining carefully.

LPCG7 said:
To begin with, I rooted mine by downgrading to LP stock rom as rooting MM is not quite easy using this link : https://forum.xda-developers.com/g4/help/how-downgrade-g4-h815-t3264864
Then I had FIsH twrp installed cause I couldn't unlock my BL using : https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
>>ITS RISKY<<
Secondly, yours has ARB v4. So there are some hardwork involved in finding a kdz that won't brick your G4 on flashing. As you say it is very much confusing. So do proceed ahead only after properly checking your informations and cross examining carefully.
Click to expand...
Click to collapse
Many people are saying the H81520P KDZ file will work for me, apparently once I install it onto the device downgrading is pretty simple.
As for FIsH, eh... I cant figure it out at all. I was so confused by looking at the page for it, I was like eh...
EDIT: Every time I try to upload the KDZ to the device I get this. https://www.leonf.elhs.co/images/LGUP_05-01-18_11-50AM.png

Sileo2056 said:
Many people are saying the H81520P KDZ file will work for me, apparently once I install it onto the device downgrading is pretty simple.
As for FIsH, eh... I cant figure it out at all. I was so confused by looking at the page for it, I was like eh...
EDIT: Every time I try to upload the KDZ to the device I get this. https://www.leonf.elhs.co/images/LGUP_05-01-18_11-50AM.png
Click to expand...
Click to collapse
Installing FIsH is confusing at first...ask me more about it but with proper reading and carefully executing the steps you should be doing great:good:
This common error may be fixed by updating your LGUP DLL file. follow the first steps on https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803

LPCG7 said:
Installing FIsH is confusing at first...ask me more about it but with proper reading and carefully executing the steps you should be doing great:good:
This common error may be fixed by updating your LGUP DLL file. follow the first steps on https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
Hurah, we are getting somewhere. Im now getting flashing fail and its not restating the device with that DLL!

Sileo2056 said:
Hurah, we are getting somewhere. Im now getting flashing fail and its not restating the device with that DLL!
Click to expand...
Click to collapse
You followed the steps as said to the letter?

LPCG7 said:
Installing FIsH is confusing at first...ask me more about it but with proper reading and carefully executing the steps you should be doing great:good:
This common error may be fixed by updating your LGUP DLL file. follow the first steps on https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
Yes i'm following the instructions to the letter. with LGUP. Still getting the error though.

is your phone restarting?

LPCG7 said:
is your phone restarting?
Click to expand...
Click to collapse
What happens is, follow the instructions on that LGUP thread that you sent me, I put the kdz in and restart lgup and then its on refurbish. I click start and the antirollback error appears on any KDZ I use apart from the H81520p_00_0314 which kicks out a Flash Fail error. Oh and thanks for helping me with this!

dload method stuck at 5%

Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!

lalitkhokhar said:
Hi,
My phone is stuck at boot
error boot.img
keeps rebooting, unable to boot to recovery (can only access erecovery)
bootloader unlocked, frp locked
I tried using dload method to flash stock firmware but each time installation fails at 5% and I am not getting anywhere with it.
MODEL - BND-AL10
How can i recover my phone from this state? Please help!
Click to expand...
Click to collapse
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware

mrmazak said:
They did something different for dload on this phone.
It needs special firmware to dload
We found that service firmware for l21c432 will get the phone working again, then use hwota to restore correct region firmware
Click to expand...
Click to collapse
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download

lalitkhokhar said:
what is hwota?
will i need to keep all files in dload folder or just the update.app?
is service firmware same as the full ota which is found on Firmware finder?
and there are two type of full ota FullOTA-MF and FullOTA-MF-PV which one should i download
Click to expand...
Click to collapse
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.

mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
thank you! I will try this.

@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?

lalitkhokhar said:
@mrmazak Thank you very much! L21 firmware worked and I am running it without any issue.
What difference does it make as now I am using BND-L21 firmware instead of BND-AL10?
Acc. to me this Rom is better as there are very few bloatware installed as compared to AL10 and everything seems to work fine.
In About Phone only things changed are-
Build number
Baseband Version
Model and imei are same as before.
Does i really need to install AL-10 firmware again?
Click to expand...
Click to collapse
As long as the phone is working normally, I think you should be fine . But further updates will , of course, need to be manually done . Like this install was.

mrmazak said:
Service rom is different then fullOTA.
From the screenshot you have . The fullota-mf-pv examples are Oreo and the ones without the pv are nougat.
This separation is not allways Oreo/ nougat, but only in your example.
HWOTA is a method to force install fullOTA files that uses a modified stock recovery that bypasses version verifications.
Here is link.--( there is other hwota too. One that has more batch file script and incorporate bootloader unlock and device rebranding. )
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
And service rom was found on rusian site 4pda.
The file download there has reached a download limit and forces you to sign up for a Yandex account. I copied the service rom to Android file host.
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Click to expand...
Click to collapse
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?

XandeR180 said:
Restored my phone using the service firmware but the "OEM Unlock" option in the Developer Options is completely missing. Is there a fix for this?
Click to expand...
Click to collapse
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?

mrmazak said:
Never saw that before, unless your phone in C00 or C01 (China region)
Try factory reset?
Then skip wifi and Google account, but set a lock screen pin or pattern. See if that helps.
Then share screenshot of "about phone". Block out imei number though.
Also which service ROM did you use. How did you use it. Did you change method from as described, did it flash both parts? The update and hw_update?
Click to expand...
Click to collapse
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.

XandeR180 said:
Actually, my phone is a BND-L34 (Mate SE)
Performed a factory reset 3 times. Third time I set up a pattern but the option still hasn't appeared.
I used the ROM in the link you provided in your previous post (had no idea there were any others, as I haven't been able to find anything else).
Didn't change anything. Extracted the dload folder to my external SD card, powered on while holding all three buttons and the update itself went just fine. Also I'm not sure how to tell whether or not it flashed both parts.
Everything else SEEMS to be working. Haven't poked around or anything, nor have I tried my SIM card. However the only issue I'm coming across (that I actually care about at the moment) is the inability to enable OEM unlocking (not grayed out or anything. It's just completely missing).
Pictures below.
Click to expand...
Click to collapse
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?

mrmazak said:
The system number ending in .046 is clue that the second part of service ROM did not load.
Before worrying about the oem toggle too much. Does the boooader screen show frp locked?
Click to expand...
Click to collapse
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot

XandeR180 said:
Nope. It just says "PHONE locked". Weird, I could've sworn it said frp locked the first time I went into fastboot
Click to expand...
Click to collapse
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,

mrmazak said:
Alright, oem unlock should work.
Then after the reset and boot up , back to fastboot to flash TWRP.
Then use hwota, and best to go with probably b330,
Click to expand...
Click to collapse
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:

XandeR180 said:
WOW it actually worked!! I'm amazed that it was that simple. Thank you so much. I'll follow your HWOTA guide and keep you posted if anything goes wrong :good:
Click to expand...
Click to collapse
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal

mrmazak said:
I did see one time the issue with unknown model and strange build number. And hwota did not help going from emui 8 to emui 8. But downgradeing from emui 8 to emui 5 fixed it. Then update back to 8 went normal
Click to expand...
Click to collapse
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number

XandeR180 said:
Actually, installing the update files for emui 8 while on emui 8 worked perfectly! At least I think. Everything looks normal so far, even the model number and build number
Click to expand...
Click to collapse
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.

mrmazak said:
Sounds good.
So now let me ask what was the issue you had to recover from. And I assume you had the unlock code already?
I ask because yesterday I was helping someone , also with mate se. They are trying to get uock code from DC unlock, but need to downgrade first. I had guided a downgrade this way before to get unlock codes , and it went just fine. But when you had the unknown model number, it makes me wonder what caused it, and of it could be avoided for the guy I'm helping now.
Click to expand...
Click to collapse
As much as I would love to help, I really don't know what caused the unknown model number.
The reason I needed to restore my phone was because I had originally gotten the Oreo update through firmware finder because I never officially got the OTA (even though my IMEI was approved according to FF). The update seemed to have worked alright but one day my camera suddenly stopped functioning completely. Reboot didn't fix it. So I decided to factory reset it but that only ended in a bootloop.
I could have used TWRP to fix it but for some reason it would not boot into TWRP, so I opted for triggering an OTA installation through stock recovery but that didn't work (this was before I knew of the service ROM). So then I tried reflashing TWRP but I couldn't because I forgot to enable USB debugging. I knew I was done for at that point. And stupid me added to the problem by relocking the bootloader (I don't remember why I decided to do that).
So I hadn't touched the thing in months up until today to see if there was any new methods for restoring a bricked device. That's when I found some threads pointing towards a service ROM. And here I am.
Sorry that I couldn't provide any specific details. Some things I just forgot and some things I don't even know the cause of (like the camera malfunctioning and the bootloop after factory resetting).

[ROM] SM-A105F Stock/Combination Firmware

Stock Firmware:
A105FDDU1ASC2
Combination Firmware:
FA90 A105FXXU1ASB6
Extract the firmware with 7zip
Use odin to flash it as per normal

Cool... Thanks man...

what is a combination firmware

How about A105g/ds?

Root/recovery
hello guys, is there any way to root and install custom recovery (TWRP) on galaxy A10 (A105F) or any one working on it ?
i've been searching the web for last two days and i found nothing really work
thank u guys

brahimlagdem said:
hello guys, is there any way to root and install custom recovery (TWRP) on galaxy A10 (A105F) or any one working on it ?
i've been searching the web for last two days and i found nothing really work
thank u guys
Click to expand...
Click to collapse
Did you find a twrp file to flash SM-A105F device ?

Any news about developping/availability of SM-A105F twrp file ? I hope Someone will be able to help with this (growing number of user as noticed on the internet)

Hh

timba123 said:
Hi. I have the metro pcs variant 10e. Our oem unlocking in developer options has been hidden/disabled/missing. Is the a10f the same as far as my metro variant? Also when trying to get into bootloader mode the phone vibrated and a little yellow exclamation ! symbol appeared at bottom of my screen right above the charging port. What was that exactly? This is my 1st A series device
Click to expand...
Click to collapse
even if its the same you cant unlock the bl or root as its a usa variant and its not allowed.
the yellow symbol you see is normal.. its an indicator for the charging i believe to indicate slow charging for example

deadman96385 said:
Stock Firmware:
A105FDDU1ASC2
Combination Firmware:
FA90 A105FXXU1ASB6
Extract the firmware with 7zip
Use odin to flash it as per normal
Click to expand...
Click to collapse
you do know flashing combo firmware now requires factory approval in the form of a token right?

elliwigy said:
you do know flashing combo firmware now requires factory approval in the form of a token right?
Click to expand...
Click to collapse
I don't really follow Samsung much anymore, when this was posted the phone was new and I had access to both and both firmwares weren't available anywhere so I posted it in case it would help someone.

timba123 said:
I have metro ASK4 firmware currently on phone. I found official ASK1 4 file firmware . When trying to downgrade I get SHA256 error. So locked bootloader prevents it? Cant even downgrade. What can I look into as far as changing property values sys.oem_unlock_allowed 1 temporarily if anything? I do apologize if my questions annoy the more experienced members. I used adb shell setprop and it added it but theres 2. One with 0 and one with 1
Click to expand...
Click to collapse
That's because you spelled it wrong bro lol.. it also doesn't do anything unfortunately and reverts after you reboot the device.
You cannot downgrade.. most time even on unlocked bl's downgrading is not allowed.
If you mean you found a lower firmware on same rev that's a different story. You get sha error because you need a modified odin that has the sha checks disabled.. or you can use something like chimera tool

timba123 said:
Lol I see my spelling error now. I think I was really burned out trying to learn and figure out stuff. Is there any decent links on how to patch SHA256? I tried many web searches and little results
Click to expand...
Click to collapse
huh? thats not useful at all lol.. theres already pstched odins all over the internet.. it doesnt patch the firmware, it patches odin software so it ignores the sha256 altogether

timba123 said:
Yes there are many patched Odin's but not a patched 3.14 version. My device will not work with any odin lower than 3.14
Click to expand...
Click to collapse
i forgot lol.. i also have an a10e but i use chimera tool and it works fine and no sha checks if u select that ootion
Sent from my SM-G977P using Tapatalk

timba123 said:
Unfortunately I cant afford any tool like that. I've tried crack versions that dont require box or card but none of them are current cracks.
Click to expand...
Click to collapse
crack talk is also not allowed on xda lol
Sent from my SM-G977P using Tapatalk

timba123 said:
Thanks. I downloaded official version. Pay day I'm going to try a starter license. I'm a little excited lol. Do you know if it flashes combo on a10e?
Click to expand...
Click to collapse
it does/doesnrt.. u cant just flash combo firm to the device, it also has nothing to do with odin or chimera.. samsung implemented security so combo firm cannot b flashed unless you have a token for it.. without it u can only flash stock firmware.. if u got acombo token tho then yes, chimera at that point could flash combo no problem

How To Guide LE2127 OnePlus 9 Pro Custom ROM (T-Mobile)

I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and have accepted all normal OTA updates as of 9/8/22, you should be on C.19 firmware.
Assuming you have already unlocked your bootloader, you can safely upgrade to EU C.62 firmware found at:
OP9PRO_Android12_C62_EU_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
I completed this process while already on Nameless but it should work for others too. No more dodgy modules, hacked MSMDownloadTools or sorta working phones. Note, firmware and local updates are NOT the same. You are not cross-flashing to an entirely new software but ONLY required firmware modules for latest custom ROMs. Hope this helps!
P.S. if you receive any error while sideloading your new firmware, DO NOT unplug or reboot your phone. Repeat the process until it's completed successfully.

So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??

nextbigleap said:
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
Click to expand...
Click to collapse
That's exactly what I am saying, fastboot flash the firmware only and say goodbye to data issues.

My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?

MudaTrucka said:
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
Click to expand...
Click to collapse
No user data removed.

Appreciate this post. Do you plan on keeping this updated as EU gets updates?

SaintZ93 said:
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
Click to expand...
Click to collapse
I will do my best!

Why does this work where the eu msm converter has problems with the modem? After you flash this firmware can you take future ota updates without modem issues as well?

The latest firmware from non-branded OnePlus 9 Pro is now available!
OP9PRO_Android12_C63_NA_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
This finally brings those of us on T-Mobile, especially closer to the bleeding edge.

Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.

rageoner said:
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
Click to expand...
Click to collapse
Of course, it's modified because OnePlus doesn't create firmware packages for our community. However, the files within the package are original dumps.
You can easily sideload this fix through your custom recovery using adb sideload OP9PRO_Android12_C63_NA_Firmware.zip for example.

Ok, one last question, are we able to take ota updates after doing the sideload? I know this is the latest firmware so there won't be any but in the future are we able to take ota?

Question:
1-what room is best for my LE2127 for daily use
2-Hasselblad camera exist a app
3-what TWRP are we using now
thanks in advance

Could someone please post steps to sideload Le2127 to EU / Global C.62EU / C.63NA No data loss ?

can I sideload this from t-mobile c.17? Also what recovery can I use? TWRP is for android 11

I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com

luckylui said:
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
Click to expand...
Click to collapse
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.

MudaTrucka said:
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
Click to expand...
Click to collapse
Do the other option and go from there.

The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !

Bulauski2005 said:
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Click to expand...
Click to collapse
You can't help folks that don't want to help themselves.