To those professionals, any help would be greatly appreciated....
Nobody is working on this model?
@ashyx After flashing an SBOOT ENG from Halabtech, on the top right hand corner of the boot screen, i am getting in pink:
NAD : Passed
RPMB Provisioned
Have i gotten anywhere?
DeviceManagent said:
@ashyx After flashing an SBOOT ENG from Halabtech, on the top right hand corner of the boot screen, i am getting in pink:
NAD : Passed
RPMB Provisioned
Have i gotten anywhere?
Click to expand...
Click to collapse
I don't think the Sboot is really of any use for anything. Not from what I've gathered.
RPMB is a special part of the EMMC, it's part of secure boot.
I think provisioning is done by the manufacturer before it's released and ties the Soc to the emmc, obviously for security purposes.
This means the emmc cannot be removed and placed in another device preventing anyone getting to the data on the emmc.
No idea what NAD is?
ashyx said:
I don't think the Sboot is really of any use for anything. Not from what I've gathered.
RPMB is a special part of the EMMC, it's part of secure boot.
I think provisioning is done by the manufacturer before it's released and ties the Soc to the emmc, obviously for security purposes.
This means the emmc cannot be removed and placed in another device preventing anyone getting to the data on the emmc.
No idea what NAD is?
Click to expand...
Click to collapse
I paid for files from Halabtech if you want me to put them in Drive for you to check out
DeviceManagent said:
I paid for files from Halabtech if you want me to put them in Drive for you to check out
Click to expand...
Click to collapse
What did you buy?
ashyx said:
What did you buy?
Click to expand...
Click to collapse
Eng Boot
Sboot
Eng Modem
combination files
root files
stock firmware
*edit*
for J327t and J727T
DeviceManagent said:
Eng Boot
Sboot
End Modem
combination files
root files
stock firmware
Click to expand...
Click to collapse
Wouldn't mind taking a peak at the eng boot and root file.
ashyx said:
Wouldn't mind taking a peak at the eng boot and root file.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0BxPUZKcTuwZ1bk1kTFctLXJGZkk
Eng boot boot looped
Sboot booted
Root files did nothing
DeviceManagent said:
https://drive.google.com/open?id=0BxPUZKcTuwZ1bk1kTFctLXJGZkk
Eng boot boot looped
Sboot booted
Root files did nothing
Click to expand...
Click to collapse
Had a quick look at Eng root which is worthless. Doesn't even have a ramdisk, it's empty? It's also been modified so not surprising it didnt do anything. Did it even flash?
Eng boot looks like it's the binary from combination firmware. No good for root as it's ro.secure=1
ashyx said:
Had a quick look at Eng root which is worthless. Doesn't even have a ramdisk, it's empty? It's also been modified so not surprising it didnt do anything. Did it even flash?
Eng boot looks like it's the binary from combination firmware. No good for root as it's ro.secure=1
Click to expand...
Click to collapse
Eng boot and Sboot passed without issue. Eng boot looped and Sboot gave me the message on the boot screen i mentioned in other post
DeviceManagent said:
Eng boot and Sboot passed without issue. Eng boot looped and Sboot gave me the message on the boot screen i mentioned in other post
Click to expand...
Click to collapse
Did the Eng root flash with odin? I'd be surprised if it did.
ashyx said:
Did the Eng root flash with odin? I'd be surprised if it did.
Click to expand...
Click to collapse
yea, it just boot-looped
*edit*
As did my J327
DeviceManagent said:
yea, it just boot-looped
*edit*
As did my J327
Click to expand...
Click to collapse
Combination file booted fine
*edit*
sorry J327 booted on sboot and gave the message on start up screen... again sorry, juggling 4 devices at the moment.
DeviceManagent said:
yea, it just boot-looped
*edit*
As did my J327
Click to expand...
Click to collapse
J727TUVU1AQD7_Root_Halabtech_2
Are you sure this actually flashed with ODIN? It's a modified binary and as such has no Samsung signature. I wouldn't expect it to flash at all and just be rejected.
.
ashyx said:
J727TUVU1AQD7_Root_Halabtech_2
Are you sure this actually flashed with ODIN? It's a modified binary and as such has no Samsung signature. I wouldn't expect it to flash at all and just be rejected.
.
Click to expand...
Click to collapse
Thats all i use is Odin
DeviceManagent said:
Thats all i use is Odin
Click to expand...
Click to collapse
So we're saying unsigned binaries can be flashed on the J727T?
There is no failure in Odin or 'secure check fail' warning on the device itself?
ashyx said:
So we're saying unsigned binaries can be flashed on the J727T?
There is no failure in Odin or 'secure check fail' warning on the device itself?
Click to expand...
Click to collapse
i get secure check fails (recovery) when flashing CF-auto-root
DeviceManagent said:
i get secure check fails (recovery) when flashing CF-auto-root
Click to expand...
Click to collapse
But not when flashing the root file from Halibtech?
ashyx said:
But not when flashing the root file from Halibtech?
Click to expand...
Click to collapse
odin wouldnt even read the file
Related
was anyone able to root the new a5 2016?
if so how?
Sent from my SM-A510F using Tapatalk
wildalan said:
was anyone able to root the new a5 2016?
if so how?
Sent from my SM-A510F using Tapatalk
Click to expand...
Click to collapse
Latest TWRP v3.0.0-0 for the Samsung Galaxy SM-A510F
NOTE:
This is a test build and requires a tester who knows how to flash with Odin and recover if required.
It may boot it may not, it sometimes takes a few tries to get the configuration right as I don't own this device.
If it doesn't boot take close note of what happens and describe in detail.
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Flash with Odin 3.10.7 using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
twrp_3.0.0-0_sm-a510f
NOTE: ON SOME ANDROID 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.
Device Tree: Coming soon
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
ashyx said:
Latest TWRP v3.0.0-0 for the Samsung Galaxy SM-A510F
NOTE:
This is a test build and requires a tester who knows how to flash with Odin and recover if required.
It may boot it may not, it sometimes takes a few tries to get the configuration right as I don't own this device.
If it doesn't boot take close note of what happens and describe in detail.
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Flash with Odin 3.10.7 using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
twrp_3.0.0-0_sm-a510f
Device Tree: Coming soon
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Click to expand...
Click to collapse
What about A7 A710F and A710FD ?
iNTER5LOve said:
What about A7 A710F and A710FD ?
Click to expand...
Click to collapse
Post up your recovery.img
ashyx said:
Post up your recovery.img
Click to expand...
Click to collapse
how to extract it from my device ?
iNTER5LOve said:
how to extract it from my device ?
Click to expand...
Click to collapse
It's ok I got it. Watch this space, compiling now.
ashyx said:
It's ok I got it. Watch this space, compiling now.
Click to expand...
Click to collapse
ooh many thanks bro
I’am waiting
iNTER5LOve said:
ooh many thanks bro
I’am waiting
Click to expand...
Click to collapse
Follow the instructions above and flash this: twrp_3.0.0-0_sm-a710f
Stock recovery should you need it: https://www.androidfilehost.com/?fid=24415232478675519
ashyx said:
Follow the instructions above and flash this: twrp_3.0.0-0_sm-a710f
Stock recovery should you need it: https://www.androidfilehost.com/?fid=24415232478675519
Click to expand...
Click to collapse
thanks bro at first
but its bootloop on samsung logo even revert back to stock recovery
my model number is A710FD
I dont know if its different
iNTER5LOve said:
thanks bro at first
but its bootloop on samsung logo even revert back to stock recovery
my model number is A710FD
I dont know if its different
Click to expand...
Click to collapse
Thought you had the A710F?
Ok will have to recompile for the A710FD.
Will upload stock recovery for your device, but no more development for today. Time for bed and early to work tomorrow.
Which build of firmware is your device running?
ashyx said:
Thought you had the A710F?
Ok will have to recompile for the A710FD.
Will upload stock recovery for your device, but no more development for today. Time for bed and early to work tomorrow.
Click to expand...
Click to collapse
go to sleep and have a nice drean D:
its okay I will waiting till tomorrow
iNTER5LOve said:
go to sleep and have a nice drean D:
its okay I will waiting till tomorrow
Click to expand...
Click to collapse
Which build of firmware is your device running?
i need root for Sm-A510FD
ashyx said:
which build of firmware is your device running?
Click to expand...
Click to collapse
a710fxxu1aolg
Then the stock recovery should have worked. Are you certain it flashed without any errors?
ashyx said:
Which build of firmware is your device running?
Click to expand...
Click to collapse
this one is work fine with me
http://www.mediafire.com/download/224avarqg63mmvy/recovery.tar.md5
ashyx said:
Then the stock recovery should have worked. Are you certain it flashed without an errors?
Click to expand...
Click to collapse
ok this is what I did again
I flashed your twrp file
and phone boot normally with twrp recovery but without root
reboot to recovery and I let recovery install supersu and system R/W
after this my phone got bootloop again
what should I do to get twrp and root ?
. .
ashyx said:
Can you tell from which firmware you obtained this recovery?
Click to expand...
Click to collapse
I flashed your TWRP file and this supersu from recovery
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
and now everythings worked
root and twrp recovery
thanks a lot bro
your file works for A710F and A710FD
iNTER5LOve said:
ok this is what I did again
I flashed your twrp file
and phone boot normally with twrp recovery but without root
reboot to recovery and I let recovery install supersu and system R/W
after this my phone got bootloop again
what should I do to get twrp and root ?
Click to expand...
Click to collapse
Ah ok, so it did work.
OK do not let twrp root your device as it will bootloop devices running 5.1.1 roms.
So I take it you have the stock firmware to flash? Flash that then install the file below and you will have root.
https://download.chainfire.eu/921/SuperSU
IF TWRP ASKS TO ROOT DO NOT LET IT ROOT.
---------- Post added at 09:53 AM ---------- Previous post was at 09:48 AM ----------
iNTER5LOve said:
I flashed your TWRP file and this supersu from recovery
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
and now everythings worked
root and twrp recovery
thanks a lot bro
your file works for A710F and A710FD
Click to expand...
Click to collapse
OK can you test everything?
Backup, restore, adb, mtp(probably won't work), all partitions mount etc.
Also could you go to advanced and send me the recovery.log.
If you want to hit my THANKS button be my guest.
Thanks.
So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.
polepoe said:
So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.
Click to expand...
Click to collapse
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).
hgoldner said:
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).
Click to expand...
Click to collapse
I think the boot loader is unlocked because I can access the boot loader screen. It said:
*** Software status: Offcial ***
*** LOCKED ***
*** S-OFF ***
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
DDR TEST
DDT TEST (LOOPING)
POWER DOWN
Click to expand...
Click to collapse
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
hTC download mode
*** LOCKED ***
htc_pmewl XC S-OFF
CID-VZW__01
MID-2PS650000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.605.20
Jun 8 2017, 11:30:46(857212)
Click to expand...
Click to collapse
Wondering whether you have a firmware/ROM mismatch.
polepoe said:
I think the boot loader is unlocked because I can access the boot loader screen. It said:
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
Click to expand...
Click to collapse
what rom are you trying to flash?
aer0zer0 said:
what rom are you trying to flash?
Click to expand...
Click to collapse
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums
polepoe said:
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums
Click to expand...
Click to collapse
And they all do the same thing?
aer0zer0 said:
And they all do the same thing?
Click to expand...
Click to collapse
Yes, it stuck in boot loader after done flashing and restart.
polepoe said:
Yes, it stuck in boot loader after done flashing and restart.
Click to expand...
Click to collapse
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.
aer0zer0 said:
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.
Click to expand...
Click to collapse
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
hgoldner said:
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
Click to expand...
Click to collapse
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?
polepoe said:
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?
Click to expand...
Click to collapse
Reread post #9 of this thread.
hgoldner said:
Reread post #9 of this thread.
Click to expand...
Click to collapse
TWRP flashing is done and it freeze at REBOOT phase so I have to hard restart the phone (with volume down + power for 11 seconds)
It still stuck in the boot loader.
This error message show up with the boot loader:
Code:
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368
polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there
aer0zer0 said:
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there
Click to expand...
Click to collapse
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
What error message?
polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk
aer0zer0 said:
What error message?
Click to expand...
Click to collapse
This
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368
Click to expand...
Click to collapse
santod040 said:
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html
polepoe said:
This
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html
Click to expand...
Click to collapse
And you've made sure to allow system modifications via Twrp swipe option when you first loaded it?
Check under Advanced > Mount and make sure system is not selected as Read Only.
Sent from my HTC6545LVW using Tapatalk
I'm trying to root my Sprint LTE Samsung Galaxy TAB A 10.1. The current firmware is MM which is on the February 1st, 2017 security patch. I'm really trying to adopt my 128GB SD card as internal storage. I tried the ADB methods, but it didn't work. Maybe it has something to do with the newer security patches? If so, where might I be able to download the earlier firmwares and downgrade? I'm really swamped here... If someone could help me out with this I'd be extremely grateful!
Thanks!
Khotum7 said:
I'm trying to root my Sprint LTE Samsung Galaxy TAB A 10.1. The current firmware is MM which is on the February 1st, 2017 security patch. I'm really trying to adopt my 128GB SD card as internal storage. I tried the ADB methods, but it didn't work. Maybe it has something to do with the newer security patches? If so, where might I be able to download the earlier firmwares and downgrade? I'm really swamped here... If someone could help me out with this I'd be extremely grateful!
Thanks!
Click to expand...
Click to collapse
You don't need to downgrade, you just need my patch in my sig below.
ashyx said:
You don't need to downgrade, you just need my patch in my sig below.
Click to expand...
Click to collapse
Just the second one? Do I install it from the recovery? I'm on the stock.
ashyx said:
You don't need to downgrade, you just need my patch in my sig below.
Click to expand...
Click to collapse
Khotum7 said:
Just the second one? Do I install it from the recovery? I'm on the stock.
Click to expand...
Click to collapse
The thing is idk if I can root my T587P. To install it from recovery, I need TWRP, right? To Get TWRP, I need root?
Khotum7 said:
The thing is idk if I can root my T587P. To install it from recovery, I need TWRP, right? To Get TWRP, I need root?
Click to expand...
Click to collapse
Root not required at all just custom recovery to install the zip.
ashyx said:
Root not required at all just custom recovery to install the zip.
Click to expand...
Click to collapse
I'm having trouble finding any custom recovery for the T587P though... Could you help me?
Khotum7 said:
I'm having trouble finding any custom recovery for the T587P though... Could you help me?
Click to expand...
Click to collapse
Maybe I could flash it with Odin? Is there a way to do that? I tried changing the file extension to ".img.tar" but when I hit start it's not doing anything, lol. When I tried changing the extension to ".tar.md5" it gives me an error. I really need to flash this without root or recovery, because I can't find neither for my device, which is the T587P.
Thanks for your help.
Khotum7 said:
Maybe I could flash it with Odin? Is there a way to do that? I tried changing the file extension to ".img.tar" but when I hit start it's not doing anything, lol. When I tried changing the extension to ".tar.md5" it gives me an error. I really need to flash this without root or recovery, because I can't find neither for my device, which is the T587P.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash it with odin, it has to be custom recovery.
The T580/T585 twrp recovery should work for your device.
ashyx said:
You can't flash it with odin, it has to be custom recovery.
The T580/T585 twrp recovery should work for your device.
Click to expand...
Click to collapse
Could you please find me one and give me a link? I've this deadline to meet regarding the tablet, in a couple of hours and I'm really stressed about it. It would mean so much. I'll quickly try and flash anything you can find for me.
Thank you so much!
Khotum7 said:
Could you please find me one and give me a link? I've this deadline to meet regarding the tablet, in a couple of hours and I'm really stressed about it. It would mean so much. I'll quickly try and flash anything you can find for me.
Thank you so much!
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...overy-official-twrp-gtaxlwifi-galaxy-t3437666
ashyx said:
https://forum.xda-developers.com/ga...overy-official-twrp-gtaxlwifi-galaxy-t3437666
Click to expand...
Click to collapse
Ah I tried that, but whenever I booted into recovery mode, it had the blue text at the top left, along with text that you would see on the bootloader mode, with the android 6.0 boot logo in the background. It just freezes there and doesn't do anything :^)
Khotum7 said:
Ah I tried that, but whenever I booted into recovery mode, it had the blue text at the top left, along with text that you would see on the bootloader mode, with the android 6.0 boot logo in the background. It just freezes there and doesn't do anything :^)
Click to expand...
Click to collapse
Seems like the kernel is incompatible with the firmware you are running.
ashyx said:
You can't flash it with odin, it has to be custom recovery.
The T580/T585 twrp recovery should work for your device.
Click to expand...
Click to collapse
i can confirm that it does not work for the sprint version(sm-t587p) , gets stuck on recovery booting- bootloop.
Has anyone had any luck figuring this out? I'm trying to use SD card for internal storage as well. Sprint SM-T587P
zobriant said:
Has anyone had any luck figuring this out? I'm trying to use SD card for internal storage as well. Sprint SM-T587P
Click to expand...
Click to collapse
There is a version of twrp for the T587p posted in the development forum.
Hey buddy. Sorry for all the bad advice you have gotten here. Custom recoveries for other tab a variants do not work on the sm-t587p, and neither do the roots.
The current firmware is not Marshmallow as you said. Nougat 7.0 came out for the SM-T587P last September. (August 1, 2017 Security Patch)
I can help you further from this thread, but everything you need is here https://forum.xda-developers.com/ga...overy-sprint-samsung-galaxy-tab-10-1-t3669559
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
ANFOR7 said:
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
Click to expand...
Click to collapse
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
bmwdroid said:
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
Click to expand...
Click to collapse
Did you change the file system of the system and did it help you avoid error 1?
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
ANFOR7 said:
Did you change the file system of the system and did it help you avoid error 1?
Click to expand...
Click to collapse
Yes. To f2fs and back to ext4.
ANFOR7 said:
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
Click to expand...
Click to collapse
bmwdroid said:
Yes. To f2fs and back to ext4.
Click to expand...
Click to collapse
Did you reboot?
ANFOR7 said:
Did you reboot?
Click to expand...
Click to collapse
Yes to TWRP
bmwdroid said:
Yes to TWRP
Click to expand...
Click to collapse
Did not help(
ANFOR7 said:
Did not help(
Click to expand...
Click to collapse
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
This is what I do before every attempt to install a custom ROM.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
Should I try to lock and then unlock the bootloader back? I heard it clears partitions completely. By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
ANFOR7 said:
Should I try to lock and then unlock the bootloader back?
Click to expand...
Click to collapse
can't give you any advice here. I'd search other threads before to learn more what happens then.
ANFOR7 said:
I heard it clears partitions completely.
Click to expand...
Click to collapse
afaik it's only doing a factory reset.
ANFOR7 said:
By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
Click to expand...
Click to collapse
Probably but I'm not sure
Edit: just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
bmwdroid said:
just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
Click to expand...
Click to collapse
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
ANFOR7 said:
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
Click to expand...
Click to collapse
I c
bmwdroid said:
I c
Click to expand...
Click to collapse
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
ANFOR7 said:
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
Click to expand...
Click to collapse
I c = I see