Hi, everyone. I've successfully rooted several Android phones in the past, but this one's got me stumped. Has anyone successfully rooted this specific model, and if so, how?
I have a J1 mini prime, specifically a J106M. It is running Marshmallow 6.0.1 with a pending update that I've paused. I was under the impression the bootloader would be unlocked since it's not tied to a carrier. I now assume it isn't because I've tried:
kingoroot, kingroot, iRoot, towelroot (doesn't work with modstring codes either), latest framaroot (device not vulnerable to exploits error), framaroot 1.5.3 (same error), chainfire (causes soft brick bootloop, but has since been restored).
I can't even figure out how to verify if the bootloader is unlocked for sure. I tried using ADB. cd fastboot command simplay restarts the phone, and fastboot oem unlock command my phone or just sits there saying "waiting for device."
When I boot the phone holding down the volume, home, and power buttons, it brings me to a blue screen that I believe is Odin mode. Others seem to get a different screen that has the bootloader info right there.
It's been a few weeks since I've had time to mess with this. I'm pretty sure that's everything I attempted.
To verify, I have developer mode on, OEM unlocking on, debugging on, allow unknown sources on.
Other specs:
Baseband version : J106MUBU0AQF1
Kernel: 3.10.65-11653963
Build: MMB29Q_J106MUBU0AQF2
Thanks in advance to anyone who can assist a semi-noob. I've never posted on a forum before, and I'm not usually one to ask for help, but I'm out of ideas here lol.
Hello Bahamut,
Are you familar with the Odin tool flashing Samsung firmware? If yes, there is a universal root method Magisk root. There are two ways to root using Magisk:
1. install a TWRP recovery (flash by Odin) & install Magisk Root using TWRP recovery
2. Extract boot.img from the firmware; modify it by Magisk apk; flash the modified img by Odin.
Both ways successfully rooted my Samsung J3 Pro. I've google search for a while & see firmware/TWRP are available for your device J106M.
You should study Odin, Magisk before you go ahead.
Thanks. Somewhat familiar, I was saving that as a last resort out of apprehension that I completely brick the device lol I used Odin when attempting the chainfire files.
I forgot I had downloaded TWRP at one point, but I must be missing something because it appears to be a catch 22 as TWRP was asking for root access in the first place to perform this function. Is there a work around such as using a PC version instead of the app or am I just way off base here?
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
chankk0101 said:
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
Click to expand...
Click to collapse
Unfortunately, the Odin flashing is how I wound up soft-bricking it twice and decided I'd need assistance on this model. I was hoping someone could walk me through it with the specifics, but I guess this isn't a very popular phone.:
Related
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
First off, I have an Samsung Galaxy S4 ATT SGH-1337. I have lurked around these forums and have come to understand the rooting / recovery flash processes. Getting root on the phone is no problem using the following method: http://forum.xda-developers.com/showthread.php?t=2387577
Where my issue lies is within the recovery mode. I have tried GooManager / RomManager / CASUAL /ODIN and nothing I try seems to work. It short when I use CWM or GooManager or CASUAL everything works correctly and I receive no errors. When I first tried this i used GooManager and when it went to reboot into recovery mode It said COULD NOT DO NORMAL BOOT and put me in download mode - in short my stock recovery mode is gone/corrupted.
No matter what I try via (STOCK FW load for example) ODIN i always get a FAIL and can not get it to work. It should be noted that I have the correct USB driver installed also official USB cable and I've tried many versions of ODIN with the same result. It looks like it always fails on write. When I re-try the other methods to install a custom recovery they seem to work but I end up with the same COULD NOT DO NORMAL BOOT.
I thought I was stuck in this download mode until I rebooted the phone manually put in download mode and smashed VOL-DOWN. When I did this the phone booted up.
The strange part is that I have root, and can get into the OS, but all the recovery methods seem to fail. I have even tried the DD method via TWRP page with no luck.
I do not understand why this is the case, or why when I first did this with Goomanager it hosed my recovery mode. I am literally out of ideas, and have tired everything I can think of to get a recovery mode installed.
It should be noted that all the "gotya's" are enabled such as USB Debugging, and version verification. I do notice that when download mode appears, and i see COULD NOT DO NORMAL BOOT it does say "WRITE PROTECTION ENABLED". From my Googleing it would appear this is ok.
I have also made sure I was using the LOKI exploit; but it simply seems that my bootloader is locked no matter what I try.
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Ya5e said:
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Click to expand...
Click to collapse
One thing I could think of trying is taking a look at this video here on how to install CWM Recovery on the ATT Galaxy S4. As you watch the video make sure you've done everything exactly as he has done in the video, this way you can determine if you have overlooked or missed any steps.
Thanks for the video link. However it looks like this won't work due to the MF3 firmware.
Q6: I have a AT&T S 4 (OTA MF3) and I have rooted my device can I install a custom rom or a custom recovery?
The answer is "NO" you can not install a custom recovery or a rom at this moment.
Click to expand...
Click to collapse
I found the above in this thread http://forum.xda-developers.com/showthread.php?t=2413746&nocache=1
My phone came with MF3; I would assume this is the issue.
=(
Hey guys... So I'm REALLY new at this whole rooting thing, so please forgive me if I am not aware of any terms related to rooting and such.
So basically what happened was this:
I decided to root my Galaxy S4 (sgh-i337 --- AT&T) using the towelroot method. I had to use this method because my phone is currently running Android 4.4.4 KitKat (TouchWiz) and it worked fine. SuperSU was installed, Root Checker said my phone was rooted, it was good. I tried to install CWM using Odin, and I got the "RESET" or "PASS" from Odin, which I thought that it meant that it worked. However, when I tried to go into Recovery Mode, it went into Stock Recovery Mode. I started to look at other tutorials, and I came across another one that involved flashing your phone's respective CWM .img file from your phone itself (transfer the .img to your phone's SD, and then flash it from your phone using the app, Flashify). But when I tried to go into Recovery mode to see if it worked, it gave me the yellow triangle with an error message, "System software is unauthorized by AT&T" or something like that. I tried to look at other posts, and there was a general idea that I needed to flash the stock Kernel. Now, the way I rooted the phone in the first place, I already had two different ones downloaded. One was flashed, towelroot was used, and then the second kernel (which was the one that originally on my phone before rooting) was flashed. After that, it was rooted. So me, being the complete noob I am at rooting, decided to re-flash both, in order, to see if that cleared up the error message when trying to get into Recovery Mode. This did not solve the problem either.
Again, I would like to apologize for my lack of knowledge on rooting and such, so please forgive me for my incompetence. And yes, I know that there are other threads on topics like this, but I have tried several things and it has not worked. Any help on how to fix this problem (and how to install CWM properly on my phone - since it is updated to 4.4.4 TouchWiz - or if I should use TWRP instead, because I intend on downloading the Kangapop GPE ROM(and how to install that for my specific model/software version)) is greatly appreciated, thanks!
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
Kogan agora 6 plus.
android 6.0
i tried, kingoroot, towelroot and kingroot.
All failed, i am now asking around the community on a way to root it for various reasons.
will provide more info about it when it charges.
edit:
Model number: Kogan Agora 6Plus
android version: 6.9
baseband version: MOLY.LR11.W1539.MD.MP.V10.P6, 2016/07/29 14:46
kernal version: 3.18.22
Build number: M1_PLUS_N_AU_KG_M_MT6755_65U_V1.8
custom build version: alps-mp-m0-mp7-v1.5_mlt6755.65u.m_p11
In the developer options, there is a toggle called OEM unlocking. Try toggling it and try rooting again.
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
I can confirm they device looks identical, I am not very familiar with repacking TWRP, but would be appreciative if you were happy to share.
Jimmy Mossiba Floyd said:
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
Click to expand...
Click to collapse
ok then: what you'll need to download is:
1. adb minimal drivers (you can find it here on xda)
2. supersu latest systemless zip (2.79 I think it's the latest version) after you've downloaded it, put it in the device's internal memory (yeah just right-click the zip file, chose "send-to" then chose your device)
3. the recovery file which is compressed in zip (unzip it and put the img file in the folder where you've installed adb - c:\adb\ )
after that, when you've got everything set, restart your device in fastboot mode: shut down the phone then put it on by hitting the power button and volume up button.. you're gonna have a three-choices menu that you're gonna scroll with the volume up button, when you've got the cursor on "fastboot" press the volume down button... the device will be put on fastboot mode.
Now back to your pc, open a command prompt, then brows to c:\adb. When you have your command prompt on adb, write this (including the quotes):
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Hit enter... wait a little (while the recovery boots) and then... voila!! all you've got to do is to flash the supersu zip through the recovery and reboot: congratulations your device is now rooted
p.s: I suggest you make a full backup for all the partitions from TWRP before you do anything... you'll thank me for that
Thanks for the elaborate explanation,but I am stuck on:
Jimmy Mossiba Floyd said:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Click to expand...
Click to collapse
Cmd says that it successfully pushed and booted the image
Code:
downloading 'boot.img'...
OKAY [ 0.717s]
booting...
OKAY [ 0.070s]
finished. total time: 0.799s
...but after a couple of seconds, it reboots to system.
Any Ideas what is happening?
Long time no see hhhhh
ummm really have no idea since it works flawlessly for me but ummmm tell me: do you care if you lose the stock recovery?
I would like to try to flash it but there is a chance that it would not work , therefore having no recovery. I have unlocked my bootloader though.
Ok so instead of:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Try:
fastboot flash boot "TWRP 3.0.2 by Jemmini.img"
This is only if you're gonna take the risk... If not, just give me time maybe I'm gonna find something for you
Sorry, but I don't want to take the risk. I think the problem is that I am running Android 7.0 which differs from other versions. I have contacted Kogan to see if I can access the source code, but judging by previous threads on Kogan, it is not going to be easy.
Ah ok then I must be wrong! Because my device runs on Marshmallow 6.0 and ther must be a difference between the two (software-side)
I don't know if you can do it but, can I have a system dump so that I can bring you a fix for rooting the device?
P.S: I can assist you to make one if you want!
I am not quite sure how to dump the system (Is it "adb pull /system <whatever path>"). I have run the command, and it seems that adb can't access the /system/bin folder. Is it required for recovery porting? If not I will upload the system.
Sorry for being late, I have no DSL where I live and my data plan came to an end!! I will look for a method to dump the whole system for you. Stay tuned
Kogan has replied back and the kernel is released to the public.
https://assets.kogan.com/files/support_files/KAPHN4G6PA_Kernel/kernel-3.18.tar.gz
I am not very experienced with compiling from the kernel so some help would be nice.
I'm not really into compiling kernels... I wish I could... Gonna see with some developers in the samsung forums may be they'll be willing to help
P.S: I'm really really sorry for being late to help you with rooting the phone.. my only pc is bricked and I need it to send you the files I used to pull and push recovery to the phone
In case it's not much asking, is there a possibility to have the link for the stock firmware from kogan?
Unfortunately, Kogan did not release the stock firmware, just the kernel. I'll too go to the other forums and see if they can help.
Thank you very much for your help, and I hope that you can un-brick your pc.
Installed TWRP but it can't read internal storage.
Also wanting to root my agora 6 plus BUMP
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Cryptic Bore said:
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Click to expand...
Click to collapse
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Hey thanks for the reply im thinking of teaching myself to build my own port of trwp.
0. It is my daily driver but i only just got it the other day ie. nothing important on there besides two factor authentication which even that i can reset up fairly easily. or just take the sim card out and use sms for that.
I also like to live on the edge a bit place austinpowers.jpg here(my first smart phone i got for my birthday from my rents: i got into a boot loop through flashing with in a week of receiving it and fixed on the fly at uni using the libary computers without my rents knowing my phone was broken xD)
1. Is the boot loader unlocked not sure how to check it on this phone, I do however have dev options unlocked with usb debuging etc turned on aswell as tickbox for "OEM Unlocking" with the description: allow the bootloader to be unlocked which i just have turned on .
2. Yes i do but im a bit out of practice its been years since ive messed around with root on android. Ive got logcat dumps through adb and have got fast boot working (as far as i can tell with the "fastboot" devices query) Got some help from a FB friend who is also going to try helping me make this happen. My previous experience was a HTC pico (the first smart phone i referenced earlier) and a Sony z2 which recently died dropping it which had a duel boot setup with carbon rom being the daily driver/rom.
Jimmy Mossiba Floyd said:
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Click to expand...
Click to collapse
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Morky001 said:
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Click to expand...
Click to collapse
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
x.ak**** said:
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
Click to expand...
Click to collapse
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Nivead said:
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Click to expand...
Click to collapse
Nivead, I did unlocked the OEM before downloading that though, but still didn't work. The phone is an unlocked phone.
And, thank you for your help.
Morky001 said:
Kumar, I did unlocked the OEM before downloading that though, but still didn't work.
Click to expand...
Click to collapse
And.. thank you.
Morky001 said:
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
Click to expand...
Click to collapse
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Nivead said:
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Click to expand...
Click to collapse
Deae Nivead,
..Oy! That sounds painful!! Guess, I have no business be doing this lock/unlock/rooting thing, huh?! Not a techie at all, this is very foreign to me! And those guys on YouTube... they lied then, said I could do all these without PC... Yeah, right! Turned out, it wasn't as easy as they were showing on videos. (((sigh))) Would be easier if I just send my phone to you?!?!!!
Thank yoooouuu soooo much for taking the time to write/tell me all this, truly appreciate your help and replies.
<Morky>
x.ak**** said:
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
Click to expand...
Click to collapse
Kumar,
I guess those YouTube tutorials omitted left out a lot of steps and not as easy nor simple as they made it to be.... "without PC" as they claimed. How would someone with no background in computer programing, nor a "techie" like you here at xda... like me would know that?! If you "don't understand how....." I wouldn't understand either!! More so than you. One thing I've learnt now, all those tutorials about rooting and TWRP. on YouTube... are crap.