Hello,
I'm trying to install TWRP recovery mode on my Samsung Galaxy note 4 ( version N910FFXXU1DPE3) running under android 6.0.1 Marshmallow
I have rooted my phone (installed the CF_Autoroot stuff with Odin) , but it doesn't seem to be enough, because when i install TWRP and try to boot in recovery mode, my phone show a message "unable to do normal boot" and switch in "download mode" and get stuck in it.
I Fixed it to work normal again, and try to find what i did wrong :
And It seems I missed to "unlock" my "bootloader".
I try to find on internet how to do it, but i can't find anything
Either the file links are missing,
Either it's only for Android 5
Either its for another version of Galaxy note, and not for mine : N910F
I can't find any good tutorial to do it, can you help me with this ?
Thank you !
You're most likely using the wrong version of TWRP or the incorrect way to load it. Please link to which version you are trying to confirm.
es0tericcha0s said:
You're most likely using the wrong version of TWRP or the incorrect way to load it. Please link to which version you are trying to confirm.
Click to expand...
Click to collapse
Well i downloaded TWRP on android store.
Then he ask me the model of my phone, i choose Samsung galaxy s4 international
Then he hask me wich version of TWRP i want, I take the latest.
Then he ask me if it should install, and just before that it launch a popup saying "Warning : You have to be sure that your phone bootloader is unlocked, are you sure you want to proceed" ?
First time, i pressed Yes, and the phone was not starting anymore.
When starting normally or in recovery .it was saying "cannot boot normally" and it switch automatically in "download mode"
I understood after that it was because I only rooted my phone, but I never unlocked the bootloader in order to install a custom recovery.
Maybe it was a typo, but you said you choose S4 international, whereas in the title you mentioned having a Note 4. That would certainly cause this...
Other than that, just reflash the original firmware in Download Mode and then boot back to Download Mode and install TWRP that way.
Sorry I meant galaxy note 4 international. not s4.
You say its possible to install a TWRP with odin ? how ?
and without unlocking the bootloader ?
Because the bootloader is supposed to be here to prevent you from installing other Custommode, other OS... replacing the basic boot files..
That's what I don't understand.
I did it with odin.
Actually i kept reading that it wasnt possible to install TWRP on a locked bootloader...
But what i didn't know that was my bootloader wasn't lock in the first place!
sorry
Related
I Unlocked the bootloader 3 days ago and flashed Cyanogenmod 12.1 with exact gapps and was able to use the phone perfectly ,today I searched for xposed and found that it could be only installed by manual flashing for android lollipop , so I downloaded the zip file and rebooted my phone in Recovery Mode [ TWRP ] and flashed the zip file just after that the phone stuck at bootloop. Restarted the phone 3 time's but no luck so finally I got into bootloader by pressing the volume down button and the power button and opened recovery mode to factory reset the phone and reflashed the CM 12.1 with gapps , now the problem begin's when I restarted the phone it is stuck at "Warning Bootloader Unlocked" and even the recovery mode is stuck at beginning screen of twrp , Im only able to use the bootloader . Even tried to reflash TWRP Recovery from computer but thier's no change it is still stuck at the recovery screen .
Any help would be really appreciated
try reflashing and then wiping cache's before rebooting ?
like the regular cache and dalvik cache.
also don't expect the first boot to work quick.. leave it for a long time...
good luck.
Actully the problem is , when i try to open recovery mode it stucks at teamwin logo (twrp)
"I searched for xposed and found that it could be only installed by manual flashing for android lollipop"
Click to expand...
Click to collapse
that quote is confusing.. what did you mean exactly.
What TWRP ? From Where + what version # ?
If i were you i would re-download it then MD5 hash it.. verify it !
I always check the md5 hashes on any phone roms or firmware etc.
I have had tons of incomplete downloads and there is nothing wrong with my internet connection either.
The more detailed you can be the more likely someone can help.
Once you are positive your TWRP is downloaded properly if i were you
i would re-flash it with fastboot. (if you can)
Can you power off the phone and put it in bootloader mode then connect to pc ?
power it off then hold volume down + power then plug in USB
then right click the empty space in the windows folder (assuming no Linux)
select open command prompt here then type:
adb devices
Is it listed ?
I also assumed you have "Minimal ADB and Fastboot" installed.
Sounds like you flashed a 5.1 firmware package ?
yes ? which one ?
And watch out many sites have cut off my download on me while downloading them.
and if you then flashed a half completed download you could prob damage the phone.
for checking hashes on windows i use HashSlash.. it's clean / free and has a GUI ..google it
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
sabungolfer0011 said:
Basically , first I flashed Android 5.1.1 AOSP for my device and then Cyanogenmod 12.1 Nightly Surnia . and yes I tried to reflash TWRP Recovery but it is stuck at the same Teamwin Logo screen , and i flashed the latest version of twrp which was available on xda . Can you provide me worth some kind of image file which I can flash to Factory reset my device from computer or anything else which can help.
And by the way Thanks for the quick reply
Click to expand...
Click to collapse
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
i used that.. but didn't flash my phone yet.
that is all firmware packages stock for Moto-2015
You still have not mentioned a lot like where did you get TWRP and what version ?
What carrier is your phone ?
I take it you unlocked the bootloader or did you get it like that ?
I'm guessing the bootloader loads TWRP
so either of those is probably damaged i bet.
I would try and get it stock then work from there getting TWRP back on and rooting etc.
What i was trying to ask you is..
Was your phone on 5.02 and you tried to update it to v5.1 ?
Because i have seen other people here who had problems with that.
Relocking the bootloader can cause problems and so can reverting to an old ver from 5.1 to 5.02
I used a custom kernel and TWRP from Squid here on the forum and rooted
and his kernel is only good for me up to version 5 but he has way newer versions out..
but they are only for users who updated to 5.1
So you have to be VERY careful what your doing.
I might have screwed up my phone if i didn't notice the fine print.
Also just search the forum for some guides on flashing firmware
and verify the downloads
My Bootloader is unlocked , TWRP Recovery Version 2.8.6.0 . My phone was on Android 5.0.2 [ Official Non Rooted ] , so I thought of updating it to 5.1.1 which was available as custom rom So I unlocked the bootloader flashed TWRP version 2.8.6.0 by copying Recovery.img in minimal adb folder and oped CMD and flashed the custom recory and it was no problem , then 2 days ago I flashed Cyanogenmod.12.1.Surnia.20150829.zip and it worked fine no issues then I flashed Xposed Modular in recovery mode , now when I tried to restart the system it stuck at bootloop so I entered Bootloader and again restarted 2, 3 times but no luck so I again entered bootloader and entered Recovery Mode ( TWRP 2.8.6.0) and wiped all my data , But unfortunately I was outside so I dint had the firmware and gapps so I switched the phone off in hope that ill flash the firmware and gapps when i reach back home . So when I vame back home and pasted the firmware and gapps in memory card and inserted it baxk in the phone and tried to enter recovery mode , that was the first time when I experied That teamwork logo stuck at recover mode and the further story you laready know
Hey guys,
I've just recently brought a Galaxy S7 (SM-G930F) - I've tried rooting it with "CF-Auto-Root-herolte-heroltexx-smg930f" on a stock rom downloaded from sammobile.
Nothing has been working. It successfully loads with Odin, reboots and says "Recovery Is Not Seandroid Enforcing" then reboots again and will not startup.
I'm not sure what is wrong. I've followed about 10 different sets of instructions and I've had no success with having any of it work.
The serial number of the device is: R58H729E0GM
The baseband version is: G930FXXU1DQEF
The build number is: NRD90M.G930FXXS1DQG5
I've enabled developer mode and enabled OEM unlocking.
If anyone has any experience I would very much appreciate it. I have no idea why it will not work.
Thank You so much in advance. (I've been searching for 2 days for a solution!)
I believe u need TWRP for that model, then flash CF-Auto with TWRP
Hey i have the same device rooted with twrp and herolte.img - install twrp and load the Image for your device ! Then you have to use odin and flash the herolte.img (in odin AP-Slot) to your device.
Then Boot up the device to twrp and Flash cf-image !
Hope this helps ....
If you need more Information ask here again...
Greetz & happy flashing
Hello,
I'm new to all this so forgive me my noobish questions. I've allready searched the internet for tutorials and how-to's but nothing seems to work.
Can someone help me on how to unlock the bootloader?
I would like to install a custom rom but need to root the phone first, in order to do that it has to be unlocked ...
Iv'e tried with adb & fastboot but nothing seems to work.
The phone (samsung S3 GT-I9300 android 4.3) remains locked.
Thanks in advance for your help
dodger1 said:
Hello,
I'm new to all this so forgive me my noobish questions. I've allready searched the internet for tutorials and how-to's but nothing seems to work.
Can someone help me on how to unlock the bootloader?
I would like to install a custom rom but need to root the phone first, in order to do that it has to be unlocked ...
Iv'e tried with adb & fastboot but nothing seems to work.
The phone (samsung S3 GT-I9300 android 4.3) remains locked.
Thanks in advance for your help
Click to expand...
Click to collapse
Are you sure that the BL is locked? Normaly it is unlocked ? so you can fash twrp to flash custom Roms
Sent from my Xiaomi Redmi Note 7 using XDA Labs
Snuk265 said:
Are you sure that the BL is locked? Normaly it is unlocked ? so you can fash twrp to flash custom Roms
Sent from my Xiaomi Redmi Note 7 using XDA Labs
Click to expand...
Click to collapse
I think it's locked ... if i try with adb & fastboot ... (several commands to check if the phone is locked i don't get an answer) ... only <waiting for device> message.
Is there any other way to check if it's locked?
I'm afraid that if i try to install TWRP it will block the phone and all i have left is a useless paper weight.
dodger1 said:
I think it's locked ... if i try with adb & fastboot ... (several commands to check if the phone is locked i don't get an answer) ... only <waiting for device> message.
Is there any other way to check if it's locked?
I'm afraid that if i try to install TWRP it will block the phone and all i have left is a useless paper weight.
Click to expand...
Click to collapse
The bootloader is not locked. Samsung phones don't have a fastboot mode, they have a download mode. You have two options for flashing twrp: odin or heimdall.
theandroid02 said:
The bootloader is not locked. Samsung phones don't have a fastboot mode, they have a download mode. You have two options for flashing twrp: odin or heimdall.
Click to expand...
Click to collapse
Hello,
I installed Odin307 and downloaded CF-root-sgs3-v6.4.tar, after connecting odin to my S3 and selecting the CF root file ... after the phone rebooted and went back to android i got the message "PASS" in odin.
So if i am correct, the phone should be rooted by now.
Now i guess: installing TWRP via odin and the google apps ... what version of Lineage Os would you recommend?
If i check on the website of lineage os, the samsung s3 i9300 is no longer available ...
Hi, you could follow this entire tutorial : https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
If anyone can help that'll be great!
Phone Info:
Android Version: 10
Baseband Version: J600GDXSACVB1
Knox version: Knox 3.5 (idk if this is needed)
"OEM Unlocking" option in developer setting is enabled
"USB Debugging" is also enabled
ThatUnknownDude said:
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
Click to expand...
Click to collapse
TWRP =/= root. Root means you have SU access in Android system. Recovery mode is a separate environment; the difference between TWRP and stock recovery is that TWRP allows you to flash unsigned images.
If you just want to root your phone with Magisk, you can follow these instructions.
Otherwise, if you want to be able to flash custom ROMs, you can use this to patch your stock recovery to enable Fastbootd which will allow you to flash partitions directly instead of using Odin.
ThatUnknownDude said:
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
Click to expand...
Click to collapse
Yes, see the Magisk instructions I linked. Samsung likes to make things complicated, so when you've unlocked the bootloader, it still won't let you flash custom images until Vaultkeeper has been disabled.
Hmm ok thanks.. I saw the Magisk installation help page and I am getting stuck in this part:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Click to expand...
Click to collapse
I am long pressing volume up button in download mode however nothing is happening...
(Edit) Oh and KG State (which I assume is another word for RMM Lock) is just showing 'checking' and not 'prenormal' or anything...
I think TWRP may be the cause of the bootloop. I flashed a stock firmware of J600G to completely reset it (factory reset of sorts) and then flashed TWRP, and entered the recovery screen. After that the bootlooping issue started... is there any other good custom recoveries?
Hi TUD, fellow J600G user here, I'd recommend you to start off easy by installing TWRP 3.2.3.
Requirements -
Odin installed on your computer.
USB cable
TWRP tar file
To install TWRP -
1. Switch your phone off and hold volume up and down buttons at the same time while connecting your phone to the computer by cable.
2. Open Odin and go to options, switch off auto reboot, now click on AP and select your TWRP tar file.
3. Now after Odin says PASS disconnect the cable from your phone and hold Volume down + power button for 7 seconds and as soon as the screen goes black hold Volume up + power button. This will boot you into your newly installed TWRP.
When it comes to custom roms J6 has some limitations for a few good ones. In my opinion you can install EvolutionX 4.0 (made by @adi_ss) that is based on android 10 as its the easiest rom to install. All you have to do is follow the instructions given by the developer.
Happy Flashing.