I tried already some topics here and I rooted my older Samsung phones before
But,
My J5 2016 510JN doesn't seem to be installing TWRP 3.0.2/3 by odin.
FRP lock is off and I got a succes with a reboot, but with up/home/power I still have stock recovery.
And after that offcource the supersu verification fail
Can someone tell me what i do wrong or need to check?
usb debugging is on
installing apk from unkown sources is on
OEM is onn (frp lock)
thanks in advance
For other people's search results:
untick the autoboot in odin, that seemed to be the problem...
thnx treat may be closed
This does not belong in the 2016 ROMS section. Please, for future posts, post in the Questions section.
Please, delete this TRASH anyone!
@Vatsal
Please move this thread to question and answer
?????
Related
Q&A for [Dev][Recovery] TWRP 2.8.7.1 for G928C | first compile !!!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Dev][Recovery] TWRP 2.8.7.1 for G928C | first compile !!!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello,
I did install it on a S6 edge+ (G928C).
The install went fine (do not forget to uncheck Auto Reboot in Odin).
I then installed SuperSU 2.46. After that, I tried to reboot, but then got stuck at "Samsung Galaxy S6 edge+" black&white screen
I am currently downloading the stock firmware to start over with a fresh device.
Currently I wouldn't advise anyone to install this recovery, seeing my experience.
I'll try again with the fresh device, to check if the bootloop problem is consistent.
RonanT said:
Hello,
I did install it on a S6 edge+ (G928C).
The install went fine (do not forget to uncheck Auto Reboot in Odin).
I then installed SuperSU 2.46. After that, I tried to reboot, but then got stuck at "Samsung Galaxy S6 edge+" black&white screen
I am currently downloading the stock firmware to start over with a fresh device.
Currently I wouldn't advise anyone to install this recovery, seeing my experience.
I'll try again with the fresh device, to check if the bootloop problem is consistent.
Click to expand...
Click to collapse
You can not "root" Now, the device will bootloop if without a custom kernel supports the "Root". Similar to "UniKernel" for S6 / S6 egde
Well, I confirm the bootloop as well.
I reinstalled the stock firmware.
I installed the recovery.
==> Bootloop is happening.
As it happened twice to me and once to another poster, I suggest this first compile is not the good one.
I might try a go at compiling one myself if I have the time.
its crazy why they post the recovery all over the net without checking it
but i dont understant the mod here if he see its not good he need to erase the thread cause the recovery not good end of line
with root without root
it can boot normally but the moment you get in recovery then you cant boot up !!!!!!!!!!
Manh_IT said:
You can not "root" Now, the device will bootloop if without a custom kernel supports the "Root". Similar to "UniKernel" for S6 / S6 egde
Click to expand...
Click to collapse
Thanks!
Please answers my questionS cause this will help all the "noobs" here cause they don't ask right questions and thus remain unhelped...
Im on MARSHMALLOW stock and i am planning to use this
http://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
Its a backup of stock de-bloated rooted
There are many tutorials for k3 note on how to root
And then there are some rom and a backup threads
The methods given are different in each one of them (not totally different)
My questionS ARE
1.Don't we need to unlock bootloader? Askin this cause some rooting tutorial here don't mention it and some does.
2.If so how to unlock bootloader in MARSHMALLOW
Settings -> Developer options -> Enable OEM Unlock Right ???
2.2.What happened if i just flick this 'Enable OEM Unlock' button ? Does the Phone Factory resets ?
2.3. What exactly is the purpose of unlocking bootloader?
3.Whats the correct order of doing it?
Like what we have to do first
Unlock bootloader -> flash custom recovery -> flash rooting/rom zip . Am i right ?
On my old device that was Sam Galaxy fit therr was no matter of bootloader and stuff
What i usually did with this snapdragon device was flash stock firmware/recoveries via odin and anf flash roms via cwm thats it . But im new to this processor and unfamiliar with bootloader..
RANT: (don't read below from here if u don't have time)
Nearly none of the threads clarify the instructions they just redirect to other threads and if questions are asked then they say "don't spam thread" like my one post will make the site look dirty and don't answer in straightforward way AND they say "follow the instructions and its not my responsibility of u brick yo fone"...
Rockstar.garvit said:
Please answers my questionS cause this will help all the "noobs" here cause they don't ask right questions and thus remain unhelped...
Im on MARSHMALLOW stock and i am planning to use this
http://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
Its a backup of stock de-bloated rooted
There are many tutorials for k3 note on how to root
And then there are some rom and a backup threads
The methods given are different in each one of them (not totally different)
My questionS ARE
1.Don't we need to unlock bootloader? Askin this cause some rooting tutorial here don't mention it and some does.
2.If so how to unlock bootloader in MARSHMALLOW
Settings -> Developer options -> Enable OEM Unlock Right ???
2.2.What happened if i just flick this 'Enable OEM Unlock' button ? Does the Phone Factory resets ?
2.3. What exactly is the purpose of unlocking bootloader?
3.Whats the correct order of doing it?
Like what we have to do first
Unlock bootloader -> flash custom recovery -> flash rooting/rom zip . Am i right ?
On my old device that was Sam Galaxy fit therr was no matter of bootloader and stuff
What i usually did with this snapdragon device was flash stock firmware/recoveries via odin and anf flash roms via cwm thats it . But im new to this processor and unfamiliar with bootloader..
RANT: (don't read below from here if u don't have time)
Nearly none of the threads clarify the instructions they just redirect to other threads and if questions are asked then they say "don't spam thread" like my one post will make the site look dirty and don't answer in straightforward way AND they say "follow the instructions and its not my responsibility of u brick yo fone"...
Click to expand...
Click to collapse
2.2 if you click oem then still nothing happenes..
It personally tested..
adikri said:
2.2 if you click oem then still nothing happenes..
It personally tested..
Click to expand...
Click to collapse
Did you did this on stock rom ??
Yes, Nothing happens because of it
This is because it is made for prevention of clearing data. If you will use command "fastboot oem unlock" using fastboot it will allow you unlock bootloader
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
Personally tested on stock marshmallow Indian ROM
Rockstar.garvit said:
Did you did this on stock rom ??
Click to expand...
Click to collapse
Nope... always on custom rom...
adikri said:
Nope... always on custom rom...
Click to expand...
Click to collapse
Hey dude can u help me a little plz
I want to install twrp on and root the stock firmware
Plz tell me do i need to unlock bootloader before flashing recovery via spf tool
One other thing i want to ask is do i need to flash the patched boot img to b able to boot stock with custom recovery ??
Basically i neee to install this and i need to know steps from Start to end plz help
http://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
There is no need to unlock the bootloader if you are using SPF tools Because MTK devices use the MTK preloader which turns on for 5 seconds on boot if you flash anything that time it will be directly written.
Actually OEM is android device default security service.
If you turn it off you will turn off the protection of your Android, though nothing happens if you turn it off.
You don't need to unlock bootloader while flashing custom recovery.
Important point always clear caches before and after flashing of roms and always be sure you know how to recover from bootloops.
First of all perform a nandroid backup. There are some cases when recoveries show unable to mount system, and then you literally can't do anything except repairment of the device partitions.
While installing custom roms, steps are:–
1. Rooting the device
2. Installation of custom recovery.(Remember to backup your stock recovery)
3. Clearing of cache and dalvik–cache.
4. Flashing of rom.
5. Clearing of cache.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
Rockstar.garvit said:
Hey dude can u help me a little plz
I want to install twrp on and root the stock firmware
Plz tell me do i need to unlock bootloader before flashing recovery via spf tool
One other thing i want to ask is do i need to flash the patched boot img to b able to boot stock with custom recovery ??
Basically i neee to install this and i need to know steps from Start to end plz help
http://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
Click to expand...
Click to collapse
You don't need to unlock your bootloader to install recoveries (always backup your stock one).
Boot.img is a patch file for some devices that use super su.zip to root their device, basically it is not needed, but some devices exploits are very rare. So if it is mentioned to flash that boot.img you should flash it otherwise it will cause your device to go in bootloop and if it happens the only way to recover would be unrooting your device.
So my conclusion would be it depends, but if it is said you should flash it too.
Dear Experts,
as I have already complained in several topics, my N9005 didn't boot after encryption.
Now I'm on the way to try other ROMs. But now I'm starting to thing, how to even test it with other ROMs. I have a backup of the original ROM made with TWRP. BUT, if I encrypt the device and something goes wrong - then how will I restore ? Will TWRP be somehow able to read the encrypted device ? Please suggest on how to proceed ?
I'm afraid, that if I put a ROM and encrypt the phone with it, I'll be stuck with that ROM... Or if not - what to choose in TWRP in order to get rid of the encryption then ?
Many thanks in advance!
Did you use the phone with stock recovery to encrypt?
Duplicate.
Please follow your existing thread: http://forum.xda-developers.com/gal...encryption-t3478539/post69084515#post69084515
Closed
I had connectivity issues with the Samsung A3 (2015) SM-A300FU I bought from a friend so I decided to flash a Custom ROM to see if the problem persists.
I flashed my Sony Xperia U Kumquat some years ago so I am not completely new to the topic.
I decided which ROM to use (LineAgeOS14.1) and went ahead and try to root my phone.
I found this page: https://androidmtk.com/root-samsung-galaxy-a3-sm-a300fu
via google and followed the instructions. After I followed them my Phone did not boot (stuck at the Samsung Galaxy A3 screen).
I read afterwards in the warnings that I should have only used these instructions with Android 4.4.
I tried flashing my device with a CF-Auto-Root from https://desktop.firmware.mobi/ which did not work.
Then I downloaded the recovery.img and boot.img from the firmware.mobi site converted them to odin flashable files with the script from this forum, which did not help the problem.
So I went to write this post but saw in the "Similar Threads" part a link to this post: "Is there a CF Root for Samsung A3 SM-A300FU ?"
Reading that thread brought me to this one: [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M
I was able to boot into Team Win Recovery Project but I am unsure where to go from here.
Any help would be much appreciated.
Thanks in advance!
Quick Update before I got to leave for a few hours: I managed to follow the rest of the instructions in: [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M
And after a long wait my phone booted. It even has the SuperSU App installed, but when I try to start it, a message pops up telling me
There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums to your device!
Click to expand...
Click to collapse
I am unsure as to what exactly I should be doing here. I am on Android Version 6.0.1 IF you need any further information to help I will gladly provide it.
I found a SuperSU zip that worked: BETA-SuperSU-v2.74-2-20160519174328
After installing that I had root access and could install LineageOS and Gapps which solved my W-Lan Problem.
@Moderators you can close this
Mod edit: Thread closed as duplicate of
samsung galaxy j5 J510fQ twrp problem
greetings, after processing the twrp file in odin, when I want to open the twrp menu of the device, first the system update is installed, then it says there is no command and then the old recovery menu comes, any idea? (device samsung galaxy j5...
forum.xda-developers.com
@sheeesh13 Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
greetings, after processing the twrp file in odin, when I want to open the twrp menu of the device, first the system update is installed, then it says there is no command and then the old recovery menu comes, any idea?
Disable 'auto-reboot' in Odin first.
Then flash twrp.
When the flash in Odin is complete do not reboot your device, instead take the battery out (yes this sounds a bit weird but it's okay) and then reboot to recovery. Do not boot to system first or else the system will overwrite the custom recovery for stock recovery which happened to you and you will have to start again