Hi Guys,
I generally make do with all of the older threads (and google), but for this I just
had to make an account and ask if there is some saving possible.
I reinstalled (Flashed) the stock rom for the J5 (with ODIN), rooted the phone using j5nlte Auto Root.
flashed TWRP and then MOAB & SuperSu. This is where something seemed to go wrong
as TWRP asked me again if I wanted to install SuperSu when exiting. Stupidly I swiped
instead of choosing no. This is where my phone ended up in a bootloop to TWRP.
Now my first reaction was, okay no biggie i'll just wipe the phone and start over again. All of a sudden
Odin can't recognize the phone when I reboot into bootloader, because it doesn't go into the normal
Samsung DOWNLOAD MODE anymore, I get the following if I choose to reboot into bootloader
ODIN MODE
Product name: SM-J500FN
Current Binary: Custom
System Status: Custom
FRP Lock: Off
Knox warranty void: 0x1 (4)
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
the pc doesn't recognize it in this state.
In TWRP it adb does recognize it. It seems to recognize adb commands.
tried the following
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
but it gives me an error message: failed to allocate 910 blocks, out of space?
anymore options?
I generally make do with all of the older threads (and google), but for this I just
had to make an account and ask if there is some saving possible.
I reinstalled (Flashed) the stock rom for the J5 (with ODIN), rooted the phone using j5nlte Auto Root.
flashed TWRP and then MOAB & SuperSu. This is where something seemed to go wrong
as TWRP asked me again if I wanted to install SuperSu when exiting. Stupidly I swiped
instead of choosing no. This is where my phone ended up in a bootloop to TWRP.
Now my first reaction was, okay no biggie i'll just wipe the phone and start over again. All of a sudden
Odin can't recognize the phone when I reboot into bootloader, because it doesn't go into the normal
Samsung DOWNLOAD MODE anymore, I get the following if I choose to reboot into bootloader
ODIN MODE
Product name: SM-J500FN
Current Binary: Custom
System Status: Custom
FRP Lock: Off
Knox warranty void: 0x1 (4)
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
the pc doesn't recognize it in this state.
In TWRP it adb does recognize it. It seems to recognize adb commands.
tried the following
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
but it gives me an error message: failed to allocate 910 blocks, out of space?
anymore options?
from xda-developers http://ift.tt/2bg9GmS
via IFTTT

Aucun commentaire:
Enregistrer un commentaire