Hi,
I've got a XT1100 and some strange problems. The os won't boot up and only access to bootloader and TWRP is possible.
My bootloader is locked and looks like this:
And in TWRP I will always get some errors in mounting cache and userdata:
I can't format, mount, erase cache and data partitions.
I can't flash any image because bootloader is locked and I can't flash anything in TWRP because mounting partitions isn't possible. I also tried sideloading zip's.
I think I have some corrupt partitions and I tried to fix them with e2fsck using: e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
But when I do this command in adb shell I get an error: CANNOT LINK EXECUTABLE: could not load library "libext2_quota.so" needed by "e2fsck"; caused by library "libext2_quota.so" not found
Can you please help me? I believe that repairing partitions could help a lot. Then I can wipe again and flash some zip's to activate USB debugging and than finally to open bootloader again.
cheers,
michel
Bolemichel said:
Hi,
I've got a XT1100 and some strange problems. The os won't boot up and only access to bootloader and TWRP is possible.
My bootloader is locked and looks like this:
And in TWRP I will always get some errors in mounting cache and userdata:
I can't format, mount, erase cache and data partitions.
I can't flash any image because bootloader is locked and I can't flash anything in TWRP because mounting partitions isn't possible. I also tried sideloading zip's.
I think I have some corrupt partitions and I tried to fix them with e2fsck using: e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
But when I do this command in adb shell I get an error: CANNOT LINK EXECUTABLE: could not load library "libext2_quota.so" needed by "e2fsck"; caused by library "libext2_quota.so" not found
Can you please help me? I believe that repairing partitions could help a lot. Then I can wipe again and flash some zip's to activate USB debugging and than finally to open bootloader again.
cheers,
michel
Click to expand...
Click to collapse
Try downloading a ROM to your PC, boot your nexus to TWRP, connect to PC. Then drag and drop the ROM into your internal storage, then try to flash the ROM with TWRP.
Ok, I downloaded cm-12.1-20150728-NIGHTLY-shamu.zip for example on my pc and booted into TWRP succesfully.
But how can I drag and drop this file into internal storage? I'm not able to mount anything.
TWRP offers me the following partitions to mount:
System, data, Cache, firmware and USB-OTG. But it isn't possible to mount it with my PC (of course, device drivers already installed)
command line says "no valid storage partitions found for MTP" and afterwards "unable to mount /data"
Bolemichel said:
Ok, I downloaded cm-12.1-20150728-NIGHTLY-shamu.zip for example on my pc and booted into TWRP succesfully.
But how can I drag and drop this file into internal storage? I'm not able to mount anything.
TWRP offers me the following partitions to mount:
System, data, Cache, firmware and USB-OTG. But it isn't possible to mount it with my PC (of course, device drivers already installed)
command line says "no valid storage partitions found for MTP" and afterwards "unable to mount /data"
Click to expand...
Click to collapse
Do you see " internal storage " on your PC?
If so, just drag and drop there. No need to mount anything other than MTP which should by default.
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
Edit: reread your post.
You said you can not issue fastboot format userdata from bootloader, then follow that with fastboot format cache?
Yeeehaa, I finally fixed it by myself.
No I wasn't able to mount the device with my PC due to faulty partitions. Solution:
I formatted cache and data with vfat and afterwards back to ext4. It won't work to format it with ext3/ext2 and back to ext4! (may be some dev could give me an answer why!?)
Then, I have seen the device connected to my PC, no more unable to mount /data again!
And now I'm on CM and activated usb debugging and now I will look for unlocking bootloader again. Hope this works as well.
Edit: I ticked usb debugging in CM but in bootloader with "fastboot oem unlock" there is the message:
Check "Allow OEM Unlock" in Developer Options FAILED (remote failure)
Edit2: Hmm, I can't get the bootloader unlocked. Is there anything I could do? USB debugging is definitly activated and pc is authorizised
Bolemichel said:
Yeeehaa, I finally fixed it by myself.
No I wasn't able to mount the device with my PC due to faulty partitions. Solution:
I formatted cache and data with vfat and afterwards back to ext4. It won't work to format it with ext3/ext2 and back to ext4! (may be some dev could give me an answer why!?)
Then, I have seen the device connected to my PC, no more unable to mount /data again!
And now I'm on CM and activated usb debugging and now I will look for unlocking bootloader again. Hope this works as well.
Edit: I ticked usb debugging in CM but in bootloader with "fastboot oem unlock" there is the message:
Check "Allow OEM Unlock" in Developer Options FAILED (remote failure)
Click to expand...
Click to collapse
Yes, you need to enable that option. If it's not available in CM, flash a stock or AOSP based ROM.
Evolution_Tech said:
Yes, you need to enable that option. If it's not available in CM, flash a stock or AOSP based ROM.
Click to expand...
Click to collapse
Yes USB debugging is definitly enabled in CM. I'm really sure. I activated dev options by ticking build number (I think) 7 times and than I could activate usb debugging in dev options itself.
Bolemichel said:
Yes USB debugging is definitly enabled in CM. I'm really sure. I activated dev options by ticking build number (I think) 7 times and than I could activate usb debugging in dev options itself.
Click to expand...
Click to collapse
No, you need to enable "allow OEM unlock" in developer options. If that option isn't there in CM (I don't use CM), then follow my previous instructions.
Evolution_Tech said:
No, you need to enable "allow OEM unlock" in developer options. If that option isn't there in CM (I don't use CM), then follow my previous instructions.
Click to expand...
Click to collapse
Ah sorry, my fault! Forgot that little thing Thank you!
I'm now full stock. The only thing is that I can't access stock recovery.
There's just a littel android with a red triangle. How can I fix this?
edit: ok fixed
Bolemichel said:
I'm now full stock. The only thing is that I can't access stock recovery.
There's just a littel android with a red triangle. How can I fix this?
edit: ok fixed
Click to expand...
Click to collapse
Try this
http://www.android.gs/how-to-enter-nexus-6-recovery-mode/
Thanks, I see that I have that little android lying on the back every time... is this normal?
May be I should not go fully stock and keep TWRP recovery...
Bolemichel said:
Thanks, I see that I have that little android lying on the back every time... is this normal?
May be I should not go fully stock and keep TWRP recovery...
Click to expand...
Click to collapse
No, this is normal for stock recovery. When dead android appears, hold power and press volume up once.
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
VineelKumar said:
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
Click to expand...
Click to collapse
You have to format data using the type "yes" to continue method. Then use twrp's menus to reboot back into recovery. Mount /system and /vendor in twrp then flash it. If you still have a problem, then try the 5/21/19 release of the disabler.
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
It doesn't show data as mounted. It shows the external sdcard as being mounted. And there is an error, twrp is giving error 1, and the disabler is also showing an error saying it can't find the boot block location. This means twrp isn't able to modify block devices or mount them properly. What I told him to do will fix the problem. The script doesn't mount anything correctly if twrp is not able to run the script... I know what I'm talking about. I wouldn't steer the guy wrong.
Edit: I'm definitely correct. What I said is actually mentioned in the official twrp thread for this device. It says; "If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again." - direct quote from the instructions, under notes.
I flashed the same .zip with /data, /system and /vendor mounted properly and ran into the same error... (see screenshot)
To mount a device block it's not neccessary to have /data mounted.
The .zip is incompatible with Moto g6 - that's all!
WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
Thanks it worked fine. But for some reason the mobile was struck in boot loop(just warning message on screen saying, you have unlocked bootloader for couple of seconds and then same thing appears again), any idea how to fix it ?
VineelKumar said:
...any idea how to fix it ?
Click to expand...
Click to collapse
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
The magisk.zip also removes dm-verity within the installation process. So you don't need the disabler.zip for this.
To remove forceencryption you have to follow a few simple steps which are given in my instruction below:
preparation:
You have to be on the latest stock firmware with TWRP installed and nothing else.
Boot into TWRP and format /data (do not wipe it! you must use format). Then reboot directly into TWRP!!
Now let's start to remove forceencryption.
1.) place the attached .tar.gz file in your internal storage (/sdcard)
2.) mount /vendor in the options menu and open TWRP's terminal command under advanced settings
3.) type in (or copy it from here)
Code:
tar -xvzf /sdcard/fstab.tar.gz
4.) at next boot your device will be unencrypted
Now don't reboot your device and stay in TWRP to install the magisk.zip v19.3!! That's important to flash v19.3 instead of the latest v20.3 otherwise it causes a bootloop!! I don't know why it does but you can later update Magisk without any problems through the Magisk Manager.
Magisk will now remove the dm-verity during the installation process. That's a part of the installation script of Magisk.
When the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
WoKoschekk said:
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
...
the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
Click to expand...
Click to collapse
I appreciate your patience, WoKoschekk. I for one appreciate the guide and insight into the reason root must be achieved this way. I was using 20.3 and 18 the whole time. I was successful with your instructions the first time. It became stuck on boot after the initia reboot, so I pushed fstab and magisk again and it was fine. I remember that on one phone, encryption wasn't a problem if you had your pin or password. Could it be the same here provided there was no fingerprint assigned (might be the original pixel)? I'm guessing this TWRP can't decrypt? Just curious, because N/A balogna.
I'm glad to hear that!
TWRP for Moto g6 can't decrypt your data. That's the reason why you must disable forceencryption to use TWRP.
WoKoschekk said:
Code:
tar -xvzf /sdcard/fstab.tar.gz
Click to expand...
Click to collapse
I don't have a SD card, so I put the file into the TWRP folder. I then used,
Code:
tar -xvzf data/media/TWRP/fstab.tar.gz
Was that the right location?
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
WoKoschekk said:
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
Click to expand...
Click to collapse
Ok, I see now. Anyway all updated and rooted with your instructions, thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 by Blue Dogerino
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
FEATURES:
built from Pie kernel source
built in full 64bit mode
updated TWRP source to 3.3.1 (9.0 version)
Full F2FS Support
fully compatible with all Oreo and Pie roms
WORKING:
Boots
Backup
Restore
All Wipes
Supports unconditional flashing
File manager
Brightness Slider
Flashing
chmod
MTP
Broken:
Nothing for the moment, but if you notice anything please do let me know
Downloads:
Get IMG
Get TAR
Installation:
1. If you have TWRP already:
Boot into TWRP recovery
Select Install, Install IMG
Select TWRP-3.3.1-j5y17lte-26052020.img
Swipe to flash
Restart your phone to recovery and you have new recovery.
Alternative method
Boot into download mode.
Get ODIN
select AP in Odin and select TWRP-3.3.1-j5y17lte-26052020.tar and click start.
To use stock rom, you need to wipe data partition, otherwise the phone will bootloop.
Kernel Source : https://github.com/Doge-Jxy17lte/kernel-exynos7870
XDA:DevDB Information
[RECOVERY][TWRP 3.3.1][9.0] Galaxy J5 (2017) [26.05.2020] , Tool/Utility for the Samsung Galaxy J5
Contributors
bluedogerino, ananjaser1211, corsicanu
Source Code: https://github.com/bluedogerino/twrp-j5y17lte
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2020-05-26
Created 2020-05-26
Last Updated 2020-05-29
Very good to have an updated version that supposedly takes into account the newer security updates!
Thank you a lot for your efforts!
Any trick needed after downloading from Odin?
RMM-state bypass, no-verity, some cache to wipe?...
Or does it simply need plain Odin download?
I'd like just to know before embarking against Pie security...
Every time I try something, it's popping out a new nightmare...
Some other known problem while then flashing Magisk?
I'm aiming at LOS17.1 and letting Google crap behind me...
Well...
I take the lack of replies as an affirmation that there aren't neither installation problems nor ancillary programs to install.
Let's hope there are no bad surprises, and go on.
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
/snip/
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
At last I succeeded in installing this TWRP, but as an upgrade of the former TWRP-3.3.0-j5y17lte-20190417.tar.
I had to before install it with Odin, then followed the procedure indicated at this old post of mine:
https://forum.xda-developers.com/showpost.php?p=80223502&postcount=82
then, from that recovery, installed TWRP-3.3.1-j5y17lte-26052020.img, that I previously loaded into my external SD, selecting to flash recovery.:victory:
I didn't reinstall RMM and no-verity after having them installed with the first TWRP.
At a first sight all appears to be well.:highfive::highfive:
But I stress that it appears to be impossible to directly install it from Odin. I'm presently too stressed to keep up with testing, but it would be interesting re-tarring this image and then re-trying direct install by Odin.:fingers-crossed:
Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:
bluedogerino said:
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:
Click to expand...
Click to collapse
I did it in the first trials, and it didn't work, while it worked for the former TWRP version 3.3.0 I then used to update to your 3.3.1. I presently dislike to repeat the trial as it took me a lot of useless time. Maybe I try again in the future.
Anyway thank you for your work again.
Kind regards
Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards
jaggedN said:
Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards
Click to expand...
Click to collapse
Works fine for me with magisk installed
Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader
axross said:
Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader
Click to expand...
Click to collapse
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards
Alvin50 said:
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards
Click to expand...
Click to collapse
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
Click to expand...
Click to collapse
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...
axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
axross said:
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...
Click to expand...
Click to collapse
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards
Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards
Click to expand...
Click to collapse
Thanks for the idea, but Android device manager and Samsung find my device were not previously configured for the phone
HELP!!!
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
Please detail better...
1) Have you yet installed TWRP? Which version?
2) Can you go to Odin download screen and report the status messages in the first rows of that page?
3) How did you try to have root?
My first suggestion is that you revert to your stock ROM by Odin, and regain your phone control.
Then restart the rooting process, caring of details: "The Devil hiddens himself into details"...
Kind regards
Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
You should reflash stock using odin, install TWRP again, format data, install a new ROM and root that using magisk.
Hey, I hope this thread is not dead, but I can't get out of the bootloop after flashing TWRP. I install it normally with Odin (as AP), then I immediatly enter recovery and it seems fine. When I try to wipe Data it gives me errors, that i can't wipe, the only option is to format data. After this i can wipe Data, but when rebooting it's stuck in a bootloop. I can still access TWRP and Download mode though. I'm running stock Android Pie, but I'm going to try it with stock 8.1 too.
Spoiler: Error
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage.
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount 'data' (Invalid argument)
unable to wipe /data.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
EDIT: Well I guess I 'fixed' it on my own. I tried what happens if I try to root it with the magisk.zip et voilá it booted just fine