So, I received this phone as an award in a competition, and when I wanted to root it... nope. No root for this phone. Only for 4.4.4, but I hate ****Kat and I don't want it. So, I updated to 5.1.1 and I was looking for root.. didn't find anything. And those "universal" roots such as KingRoot, Kingo Root, TowelRoot didn't work. I also tried installing TWRP, but after installing it and rebooting into it, the phone got stuck on "recovery is not seandroid enforcing". After booting the phone and than entering the recovery, the "recovery is not seandroid enforcing" appeared again, but instead of getting stuck, the stock recovery booted. So I flashed the stock rom with stock recovery just to remove that annoying error via odin.
Any ideas how to root this f*****g knox device?
Thanks
Please..
i have the same probleme. Nothing work for root.
Hi together, i am mucho interested, too.
Also slightly skilled linux user, so if anyone has a clue where to start rooting this thing i can give it a try.
Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.
_Beni_ said:
Mhh I also need a way to root this device because I need a full Image of my /data Partition.
My first idea was to flash the Kitkat bootloader and TWRP. However it will not but a L /system.
So we need a custom L system image which has the already installed SuperSU.
I really like to try it but however my task is to restore photos and not to hardbrick this phone.
Can anybody try a custom /sytem image which is Prerooted? Heimdall should be able to flash it.
Click to expand...
Click to collapse
If you have a clue where to find such images i can try. Without root this phone is useless to me, so i wouldn't mind bricking it
Tried to flash SBOOT, SBOOT2, Loke_Primary, Loke_Recovery ... it is now hard broken
Yeah maybe i forgot it has no Qualcomm processor where you even can flash a image even you dd if=/dev/zero of=/dev/mmc.
Now giving my old OnePlus Two to her.
You need to register at SAMMobile there you can the latest 5.1.1 for xcover3, you need to extract the image with 7zip then unpack the system.img with sparsed, then mount it via loop-back device. Now umount it, repack the image with sparse and flash the result into SYSTEM with heimdall.
Good luck, I ****ed it up
Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?
todomade said:
Oh sh*t, sorry to hear dude! Okay, this evening i can give it a try. Am i guessing right that i want to put the SuperSU binary into the /system/app? Or what's the best way to root this?
Click to expand...
Click to collapse
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
if ($SAMSUNG); then
# Prevent "KERNEL IS NOT SEANDROID ENFORCING"
SAMSUNG_CHECK=$(cat /sutmp/boot.img | grep SEANDROIDENFORCE)
if [ $? -ne 0 ]; then
echo -n "SEANDROIDENFORCE" >> /sutmp/boot.img
fi
fi
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
Click to expand...
Click to collapse
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.
Okay, looks like i should dig some deeper into that matter. I guess i can try your suggestion within the next week. I'll post an update if i make any progress.
_Beni_ said:
Yeah, however I'm not sure how su exactly works.
I know took a look at UPDATE-SuperSU.zip.
This lines are interesting:
[...]
It seems its just appends SEANDROIDENFORCE at the end of the boot.img and then flashes it.
Maybe it is the same for the recovery.
You could just try to "echo -n "SEANDROIDENFORCE" >> twrp-3.0.2-*.img"
and then flash this image via heimdall.
Click to expand...
Click to collapse
Okay i tried it, sadly no success.
Still getting "Recovery is not Seandroid Enforcing" and default recovery
Will now try to pack a boot.img myself and flash it.
Other approaches or tips are highly appreciated!
Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device?? I want some confirmation before deciding to flash twrp and then supersu into my phone running lollipop?
Newest twrp link: https://dl.twrp.me/xcover3ltexx/
Matt07211 said:
Is the "Recovery is not seandroid enforcing" showing up on the most recent build of twrp, 3.0.2.0. For the lollipop build of the device??
Click to expand...
Click to collapse
Affirmative.
VolterPL said:
Affirmative.
Click to expand...
Click to collapse
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
I geuss a fix could be compiling the kernel with the flag disabled on the flag that stops you from switching between enforcing and permissive modes. As done on this guide, http://graemehill.ca/compiling-permissive-android-kernel/ . This would allow the recovery to set itself to be running in permissive mode, when it runs "setenforce 0" as seen
https://github.com/TeamWin/android_device_samsung_xcover3ltexx/blob/android-4.4/init.rc
The source code for the Samsung phone, http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g388f
I am willing to build/compile the kernel, but due to this phone being my main phone, I am not in a position to test it out, would anyone here be willing to try?
The modified kernel will also allow you to run the OS in permissive mode if done through the terminal.
Matt07211 said:
So do you mean that the "recovery is not seandroid enforcing" shows up with the newest twrp build (3.0.2-0) for our device while running lollipop? Are you able to use the twrp recovery and phone as normal even though that message flashes on boot.
Click to expand...
Click to collapse
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.
VolterPL said:
Yes, I can confirm it's true. The phone works fine. When I try to go to the recovery mode, it shows said message and boots to the stock recovery.
Click to expand...
Click to collapse
I got a few questions to ask
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
I am willing to work, read up and compile anything necessary to get the recovery working on the device, but due to it being my only phone I cant afford to mess around with it much, so are you willing to try out stuff for me e.g. flashing a custom kernel with the ability to toggle selinux modes?
I believe a fix for the "recovery is not seandroid enforcing" can be fixed if I recompile the kernel with a flag set to false (It a custom flag from samsung that disallows the changing of selinux modes, "EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false") allowing for the twrp recovery to change "setenforce 1" to a "0" allowing the recovery to run in permissive mode. http://graemehill.ca/compiling-permissive-android-kernel/ , https://su.chainfire.eu/#selinux , https://source.android.com/security/selinux/
If you are willing to help test for me I would really appreciate it And once I get the recovery working I am gonna root my phone by flashing the SuperSu.zip.
Matt07211 said:
How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)
Click to expand...
Click to collapse
Yes, I am using the newest Odin and the newest TWRP, downloaded from TWRP site.
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.
VolterPL said:
I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.
Click to expand...
Click to collapse
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given
Matt07211 said:
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem
But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.
Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.
I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)
So if you are willing, i would appreciate the help if given
Click to expand...
Click to collapse
@ Matt07211 If you need a tester. here i am. But what i need is, a step by step for flashing with heimdall on linux mint 18 in easy english. mx phone is sm-g388f with 5.1.1
@VolterPL @yy1
So but this is gonna be an onslaught of questions and information, I would appreciate if you are able to work through this (READ EVERYTHING AT LEAST ONCE) and test/answer my questions.
Some info: When I was searching for info for how to use heimdall for yy1 because I never used it before, I happened to stumble upon a bit of info that I found interesting, and which may solve one of our problems.
In one of the comment sections a user mentioned that their recovery gets replaced each time with stock, a user replied mentioning that their is a script that runs at boot that replaces the recovery if its been tampered with e.g. TWRP, with a stock recovery. So with a bit of digging (ES File Explorer FTW!!) I happened to find the script mentioned in "/system/bin/install-recovery.sh" and the fix is to rename the file, therefore being unable to run at boot and therfore not replacing the custom recovery.
So I believe one (maybe all) of our problems with the recovery being unable to boot can be fixed as follows, would appreciate help/testing here.
Sidenote: I still plan to build a custom kernel, as I would like the ability to run in permissive mode if needed (also including running recovery in permissive mode as well) and adding custom governors as time progress.
Now time for the fix/instructions:
NOTE: I am not responsible for any damage to the phone, system, tripping KNOX, warranty or your insanity
1. Download Odin, I am using version v3.12.3 (sorry yy1, won't have a guide for Haimdell yet as on phone typing this out) and make sure to have ADB, Fastboot and Samsung drivers installed and backup any important files
2. Download newest SuperSu (yep we are gonna try rooting the phone) from this link: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1
and then put it on the root of the phones internal memory
3. Download the newest TWRP image for our device, which should be 3.0.2-0, link: https://dl.twrp.me/xcover3ltexx/ which should be in the .img.tar format
4. Would probably be best to enable USB Debugging and make sure you have everything backed up and have all files downloaded and Samsung drivers working before preceding any further. If you don't then you should fix that.
5. Launch Odin and boot device into download mode (Power, Volume Down and Home buttons at the same time, for a few seconds.), ensure that the phone is connected to the computer USB port
6. Check Odin and make sure the "added" message is displayed; also, the ID:COM field should now be turned yellow or blue â?? if not, reinstall USB drivers and retry the steps from above.
7. Click on the AP button and then load the TWRP recovery file from desktop. Then, make sure Re Partition and Auto Reboot fields are not checked. Make sure especially that the auto reboot is un-ticked, or this wont work properly as the install-recovery.sh would be able to work before we could get into the recovery at least once.
8. Click "Start" and once finished the â??passâ? message will be displayed; also the ID:COM field will be turned green â?? then you should unplug the USB cord and reboot your device into recovery mode (Reboot straight into recovery or you are gonna have to flash it all over again, due to the install-recovery.sh script)
9. Once in recovery, do a nandroid backup and then flash the SuperSu.zip and reboot
10. Verify that you have root and then download and install a file manager that allows you to modify the /system area, I suggest ES File Explorer and then navigate to "/system/bin/install-recovery.sh" and rename the "install-recovery.sh" to "install-recovery.sh.bak". On a side note, according to the TWRP page, if you boot into TWRP at least once it will patch the stock ROM to prevent this happening. So if TWRP has acctually done this then you probably wont need to modify this file, but try rebooting into recovery at least once after booting to the android OS to see if TWRP is their before modifying the file. If TWRP is their then you can skip the last step.
11. Now due to the "install-recovery.sh" script running at the most recent boot, we will have to re-flash the TWRP recovery once more as the current recovery has been reverted back to stock due to the script. So repeat the steps to flash TWRP one more time and verify that the recovery is persistent across reboots etc.
Outcomes:
- Should have a persistent recovery due to the disabling of "install-recovery.sh" script
- Should have Root on the phone
Stuff wanted to be completed in the future:
- IF this has actually worked, I would like feedback once completed the above steps stating if recovery is persistent across boots and can verify root access. If this worked I will write up a separate thread for rooting this phone and see if we can then get a section on XDA for this phone
- Recompiling the kernel to allow the changing of selinux modes between "enforcing" and "permissive", and as time progresses adding more CPU governors. I will be working to develop this myself so any help would be appreciated.
NOTES/Questions:
- Appreciate your input if this is successful
- If it still flashes the "recovery is not seandroid enforcing" and if the recovery still works in spite of that fact
- If you achieved root, please mention this
- Thank you for taking the time to read and test this if you do
- @yy1 I will write a tutorial for using Heimdall depending on this success of rooting and twrp this phone
Sorry for the wall of text and good luck
Related
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
N101BL said:
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
Click to expand...
Click to collapse
A 504 error is a network error and has nothing to do with your phone or it's backup. http://pcsupport.about.com/od/findbyerrormessage/a/504error.htm You should research these error's or post a question before doing things that end up making the situation worse. At this point you need to restore your backup and don't do anything till you read the tutorials on how to install TWRP (which has it's own built in way to root the device) or read a supersu tutorial on how to root the device after twrp is up and running correctly THEN if you have issues ask your question in the proper thread...you say you are "booting" twrp...booting twrp means it's not installed and you are running the fastboot boot command. If you meant "booting INTO twrp" by using the vol up key while the phone is booting then you should clarify. You should also be verifying your supersu zip file has the proper size/md5sum. If your backup is not valid (or you didn't bother to make one) then go to the stock image thread and download the most recent image for your model and flash that via twrp.
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
famewolf said:
go to the stock image thread and download the most recent image for your model and flash that via twrp.
Click to expand...
Click to collapse
N101BL said:
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
Click to expand...
Click to collapse
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
famewolf said:
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Click to expand...
Click to collapse
N101BL said:
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
Click to expand...
Click to collapse
While your thought is appreciated we currently have all the versions of stock that we need for the 6045i. The next time start by flashing twrp (not just booting it) following the tutorial in the twrp thread step by step...after twrp is installed boot into it and make a full backup for your OWN use before trying to root. I can't emphasize this enough...follow the tutorials..don't just jump out and start running whatevr. Your system was fine when you had the 504 network error...it was also STILL fine when you restored your backup and "continued to get the 504 error". It was after that you went off on a tangent somewhere. If you cause Alcatel enough grief they can check your returns for the presence of modifications such as attempting to root and opt to void your warranty especially after multiple returns.
I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
DJBTB said:
I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
Click to expand...
Click to collapse
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I've tried doing a factory reset if I get lucky and it takes me into the main screen but immediately it gives me the "seandroid" error message the same as if I press volume up, menu, and power. I am able to boot onto download mode ive tried this to flash firmware but Odin gives me a Fail (Auth) message each time. I'm not even sure if TWRP has a version for my phone yet I'm not sure much about TWRP. If there's a way I can break this chain I'll try anything.
TWRP working so far
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
DJBTB said:
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
Click to expand...
Click to collapse
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
DJBTB said:
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
Click to expand...
Click to collapse
By the way, when flashing stock firmware via Odin, root is not required. The only time root is required to flash stock ROM is when flashing a stock firmware that has been converted into a custom recovery stock flashable.zip. It is not uncommon for someone in this community to convert stock firmware into a recovery flashable .zip. This is used so that the device doesn't lose root or custom recovery. When flashing stock the normal way via PC, it removes root and reverts the device back to stock recovery. Then the device has to be rooted and flash recovery again. The stock flashable .zip avoids all of that because it gets flashed in custom recovery, this way, recovery is not lost and root is not lost.
This only applies "IF" someone converts the firmware to flashable .zip. Not all devices have a stock flashable .zip available though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
spent the last 3 weeks ( NO LIE ) trying every method under the sun to get my device rooted
easy recowvery
Hard Recowvery
manual ADB and flashing img
tot updates
kdz downgrades
basically everything
im not sure what else to do if its even possible at this point
Device details
tmobile locked LG G5 (h830)
OEM unlocked
its on 20a firmware ( coming from 20i )
ive rooted and installed twrp on may phones so i have a vast knowledge of these things
a few observations are
phone seems like its rewriting stock recovery on each reboot
fastboot won't accept any commands, i get "writing 'recovery'...FAILED (remote: unknown command)"
both hard recowvery and easy recowvery work up to the part of twrp install then it reboots to nothing
FINAL NOTE
im wondering if t-mobile is blocking the fastboot commands since im on temp unlock via device unlock app
if thats not a thing idk whats wrong im hoping one of you great minds can help this poor soul
Anyone?
Did you check oem unlock in developer options
rflores said:
Did you check oem unlock in developer options
Click to expand...
Click to collapse
thanks for replying ,
yes i did
its greyed out now but its been off
the fastboot commands says its unlocked as well
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
thanks for this reply
i will try this as soon as i get home
thanks in advance
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
providing an update
Ive just tried everything listed in you post specifically and failed , so i tried like 2 more time ,
it reboots into stock recovery so still no TWRP ,
boot loader is unlocked , cause i just checked again , and its still not accepting any commands
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
speters04 said:
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
Click to expand...
Click to collapse
thanks for reply;
none of those work for me either, I've been trying all this time
it says its successful in deploying commands, but when it restarts I see the LG logo two times, then it boots back up
( i assume its rewriting recovery there )
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
I had the same issue after returning from 20k to 20a. I didn't have this problem doing the same from 20f. T-Mobile might've introduced some security kink at 20i that sticks across updates. I was only able to flash twrp after flashing 20a with UPPERCUT to enter LGUP, booting into 20a, allowing debug in developer options, then running easyrecowvery with verification disabled (press 5 for advanced options, then 7 I think, then 0 to return to main menu, then 1 or 2). With verification enabled, easyrecowvery will just take you to the non-existent Android recovery screen and leave you there. I think that's where you're stuck??
speters04 said:
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
Click to expand...
Click to collapse
well lets use Autorecowvery for example
ive exhausted all options there and Ive gotten the success messages , does its fancy restarts and success messages all around , but when it restarts to install the "no-verity-opt-encrypt" it reboots and comes right back to android . ( note it reboots 2 times at this point , so i know its rewriting stock recovery )
see below
https://ibb.co/eq5ctR
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
speters04 said:
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
Click to expand...
Click to collapse
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
dtgo said:
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
Click to expand...
Click to collapse
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
poog said:
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
Click to expand...
Click to collapse
well ive been working to get to this screen it NEVER happens , i already know im set when im there
the phone isnt encrypted so i know i wont have to format data , since , format data removes encryption
speters04 said:
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
Click to expand...
Click to collapse
ive tried both your suggestions plus more
copied to the phone and renamed
downloaded on the phone then renamed
dowloaded on pc and renamed then copied to phone
used adb to push and rename to phone
still having challenges with this
do you think its a dead case guys
OP isn't the only one with this hair-pulling problem...I too downgraded a new H830 from 20M (? I can't remember which one exactly since I've LG-Uppercutted 20A and troubleshooted this constant problem so many times now)---I get the exact same error as OP, also with the highly suspicious 'greyed-out OEM Unlock' (in the Developer Options of the Settings).
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
shane_c said:
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
Click to expand...
Click to collapse
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
MikasuX14 said:
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Click to expand...
Click to collapse
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
shane_c said:
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
Click to expand...
Click to collapse
Maybe a factory reset would be a good idea to try. If you want to try my twrp recovery build, you'll be wiping your data anyway. I highly suggest you to get the full stock rom since even just getting back the stock recovery could end up with a weird sort of corruption (like duplicated or unknown options inside the Settings app, or at least I experienced that). I am not responsible if it breaks anything, you were warned to get your precautions such as getting the stock rom.
MikasuX14 said:
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Click to expand...
Click to collapse
hi if your still looking. i looked into it and the j327u twrp does work on j327w. i had the same problem trying to gain SU access with the other image files for j327w i had to use magisk zip and install it from twrp menu. had to format data and mount system in twrp.
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
bytwigorlimerick said:
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
Click to expand...
Click to collapse
heres what i did. i soft bricked, bootlooped and had to flash firmware from sfirmware a few times to get it to work
i used a twrp for j327u i found on a another similar thread on this topic. i flashed it with odin.
once inside twrp menu i went to wipe menu, i hit format, then back to mount menu, checked boxes data/system (previously data or system wouldnt check off before formatting data).once data and system were mounted i then
plugged phone back into computer while in twrp menu. the phone showed up as J327u cut/paste the latest magisk .exe into the internal storage of j327u (on computer) . i then on twrp menu found and installed magisk exe finally got it to properly install magisk i then in reboot menu hit system and reboot.
the phone restarted after awhile like it was factory reset but once i set up the phone magisk apk was already installed and root access was available. hope this helps.
so i've been busy for a long while before looking back into this. I will try again with the J327U rom. Right now, i struggle to find stock roms of the J327W because i flashed a not working twrp apparently and it locks my boot.
The J327U TWRP didn't work for me. Though, twrp itself works but i cannot get the system to boot and i cannot get to root it, no matter what i tried, i ended up in boot loop.
I managed to root this phone without TWRP. I used Linux tools to do this so I'm not sure if it could work on Windows.
Requirements:
Stock ROM for your phone (I used samfirm.js to pull it from the Samsung servers but downloading from sammobile.com works too)
A way to extract zip files
A way to extract tar files
Heimdall flasher (https://www.glassechidna.com.au/heimdall/)
Magisk Manager APK
An Internet connection on your phone
A compatible USB connector for your phone
Of course, a SM-J327W running the stock Android firmware
Obligatory warning: This WILL void the warranty of your phone and permanently trigger the warranty void flag. It also WILL cause a factory reset, so back up all your data first.
Bear with me, because there are a lot of steps. This will take around 15 to 30 minutes.
You will need to download and extract a stock ROM for your phone. Make sure that you download a ROM for the SM-J327W and not another model. Also make sure to download the latest version available.
Stock ROMs usually come in a zip file containing a few tar.md5 files. You will only need to extract the one that starts with "AP" for this procedure.
Step 1: Extract the tar.md5 file that starts with "AP" from your stock rom.
Step 2: Open the tar.md5 file in an archive manager. You may need to remove ".md5" from the end of the file.
Step 3: Extract the boot image (boot.img) from the AP file.
Step 4: Upload the boot image and the Magisk Manager APK to your phone. You can use ADB to transfer the files. For example:
adb push boot.img /storage/emulated/0
adb push Magisk-v22.0.apk /storage/emulated/0
Step 5: Open the files app on your phone. Navigate to the internal storage and tap on the Magisk APK file to install it. You may be prompted to allow installation from unknown sources.
Step 6: Open the Magisk app. It should say that Magisk isn't installed and it shoulld say "Yes" beside "Ramdisk". Tap the cogwheel icon in the top-right corner.
Step 7: Due to a bug in Magisk, you need to install version 21 instead of the latest version (v22). Set the update channel to "Custom Channel".
Step 8: When prompted, enter the following URL: "https://raw.githubusercontent.com/t...d863d3a15c6a2276b1061a280ece80ed7/stable.json" (Without the quotes.)
Step 9: Now it's time to patch the boot.img file. Tap the button to install Magisk and select the option to patch a file. When prompted, navigate to the internal storage and select the boot.img file that you transferred previously.
Step 10: Magisk will patch the file and tell you where it saved the patched file. Transfer the patched file to your computer. You can use ADB for this, for example:
adb pull /storage/emulated/0/Download/magisk_patched_XXXXX.img
Remember to replace the Xs with the the random characters that Magisk added to the file name.
Step 11: Reboot your phone into Download mode. You can shut it down and then hold the power, home, and volume down buttons at the same time to enter Download mode or use ADB: "adb reboot bootloader"
Step 12: A warning may show about the dangers of installing a custom OS. Press the volume up key to continue.
Step 13: The screen should now show "Downloading... Do not turn off target." If your phone isn't already plugged into your computer, plug it in now.
Step 14: Use Heimdall flasher to flash the patched boot image. For example:
heimdall flash --BOOT magisk_patched_XXXXX.img
Again, replace the Xs with the random characters that Magisk added to the file name.
Step 15: After a few seconds, Heimdall should report that the flash succeeded and your phone will reboot. It may take longer than usual. Leave it to do its thing and DO NOT pull out the battery.
Step 16: Your phone will show a notice that unauthorized changes have been detected and will prompt you to factory reset it. Press the button to perform the factory reset.
Step 17: Set up your phone as if it was new. It's not rooted yet, but you're really close if you got so far.
Step 18: Once you reach the home screen, upload the Magisk Manager APK to your phone again and install it like before.
Step 19: Open Magisk Manager. It will show that Magisk is installed and may prompt you to reboot to complete installation. Do not update Magisk to v22 or you will lose root access and you will have to flash the patched image again.
In the (very unlikely) case that your phone doesn't boot after flashing the patched boot.img, you can simply flash the original boot image and it should be fixed.
CONGRATULATIONS! You just rooted your SM-J327W successfully.
I also managed to port TWRP to this phone with the touchscreen working using the kernel from a recovery image for the SM-J327P found here: https://forum.xda-developers.com/t/...-1-samsung-galaxy-j3-emerge-sm-j327p.3573607/. All the partitions are mapped correctly. Due to a bug (presumably with the kernel), the data partition can unfortunately only be mounted read-only. However, this shouldn't affect being able to flash zips on your phone and you can insert an SD card to write backups onto. In the future, I may port CWM recovery to this phone using the stock kernel to be able to mount the data partition read-write.
You can find my custom recovery attached to this reply.
Follow up: It seems that the bug that causes Magisk to fail is fixed in the latest version (v22.1.) As a result, steps 6-8 in my previous post are unnecessary.
MikasuX14 said:
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
Click to expand...
Click to collapse
link is dead do you have twrp for j327w?
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.