Seeing how this phone just recently came out in January I haven't really found too much info out there so maybe this can be a start.
I've tried to unlock the bootloader but couldn't get fastboot to work and I tried kingroot and that failed. iIt has 12 requests for this phone so far.
So I'm pretty stuck right now on what to do I'm kinda a noob so maybe y'all can help me out a lil on what to do if anymore info is needed please let me know.
Thanks in advance
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
diorthotis said:
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
Click to expand...
Click to collapse
You can use this guide for your phone:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
No, it does not work. I am having several issues. First, I cannot get adb windows drivers to recognize this device, I have installed every qualcomm driver I could find, also tried the universal adb drivers and even the drivers that come with the phone. Nothing works.
However, I have a rooted tablet with an otc cable that does connect via adb. However, adb reboot bootloader simply reboots the phone. There is a download mode, but I do not have fastboot installed on the tablet, so I cannot check if download mode = fastboot.
I am able to adb push files to /data/local/tmp and running adb shell chmod 755, I have succesfully unstalled busybox and can execute commands such as vi. The user is still not root, but I feel I am close.
I tried to download the emmc internal memory using backup qualcomm tool, but I seem to not have the correct drivers for my phone. My plan was to edit ro.debuggable to 1 and reflash, so I can adb root and remount as rw.
Best I can do so far
So far cracking it is still undone...but I can offer up some advice...download 3c, advanced tools and dev tools. A notepad++ would help too so you can re-create rom commands to make your own. Use advanced tools to look for vendor. Once there you should see a few files that make you question Google's business practices. Go into them to make alterations using dev toolds. The rest of the files can be re-made from scratch using notepad and 3c's rom manager.
This phone is complete garbage, I ended up giving it away because the touch screen would go to random spots on the phone randomly. It appears to be a cheap phone I do not like. Got an LG that as far superior.
I may have a Root method for the 5044R and the 5044C, I need someone with the 5044R and 5044C to get in contact with me. Best way to do that is Telegram. Here is the Link: https://t.me/Android_General_Chat
I'm currently Testing Root on the 5044C
---------- Post added at 12:56 AM ---------- Previous post was at 12:42 AM ----------
Alcatel 5044C and Alcatel 5044R PWND and Rooted. Doing 5044C TWRP Recovery now.
UPDATE: TWRP Ported and WORKING. Now somebody make some custom Roms.
I'll have a Custom Stock Rom out for this soonishly if anyone is interested
Alcatel Verso Root Solution
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and the solution from PizzaG works well. The bootloader is unlocked and the phone is rooted. It works better now than when it was new. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports and unplug any other USB cables / devices. You will need MS Windows, the .mbn file and Sugar_QCT (from PizzaG).
Where is the root method?
I am just curious of the method used, I do not have this phone.
mrhealthpatriot said:
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and yes, the solution from PizzaG actually works. The phone boots properly, has Magisk, etc. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports, unplug any other USB drives and be persistent.
You will need MS Windows and Sugar_QCT (from PizzaG). The phone is rooted, working and more responsive.
Click to expand...
Click to collapse
Of course it works, otherwise I wouldn't have posted it along with modified boot and TWRP. Unsure if I released the modified stock rom or not?
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
diorthotis said:
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
Click to expand...
Click to collapse
I use the Alcatel Internal flashing software. It grabs the firmware files from their servers. I then swap their boot image for my modified image and then use the software to flash the device. It's then rooted and you can install TWRP or swap recovery files in the Flasher software and it will flash for you. Device must be bootloader unlocked from the factory but they disabled fastboot.
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
diorthotis said:
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
Click to expand...
Click to collapse
Once the program downloads the firmware, I was able to get some good info from the flashing logs that told me what every file is. So I just grabbed the B file which is boot and ran it through magisk manager to patch it. Pretty easy peasy. TWRP I just ported from another msm8909 device. The TWRP for 5044C also woks for 5044R models as well as the whole rooting procedure. I would build some more recoveries for it from source but I don't have the device so I can't be bothered with that unless someone wants to donate towards the cause.
Verso Unlocking
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
mrhealthpatriot said:
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
Click to expand...
Click to collapse
oh, did I really do it with SuperSU? My bad on that. Seems weird I'd use that. But yep, nice job of explaining the procedure. You should be nice and post your magisk patched version of boot.img or pass it to me to further modify it and i'll post it on here. I'd like to make it selinux permissive and remove the line of code that reflashes stock recovery on reboot. If you used my original SuperSu patched image and then repatched it with Magisk, then it wouldn't need to be repatched for selinux and such.
Flashing Files
Actually, I didn't patch the boot image or modify any files. I used the 5044C_TWRP.img and BVT4H1H0CL10.mbn that you posted. I have an Alcatel rom from Needrom, but I didn't use that either. I flashed Magjsk.zip with flashify, but I could have flashed it via adb. SuperSu was already installed..
Related
Hey Guys,
So I just bought a brand new ZTE V5 Max and upon receiving found out that it didn't have GAPPS installed which I heaily use those apps so I went down the route of figuring out what was needed to install GAPPS. Please keep in mind I'm writing this to help fellow users of this phone so they don't have to go through the teadious research and chinese translations, I will not be held accountable for anything that goes wrong with your device when doing the below process, I just know it worked perfectly fine for me:
Step 1: Enable Debugging Mode
Head to Settings > About Phone > tap Build Number 8 times or something > Now go Back to settings and tap More > Developer Options > Enable USB Debugging.
Step 2: Install Drivers
Plug in your phone and install the AutoRun.exe that appears in the virtual CD drive (shows up when youplug the phone in)
Once you have installed the drivers verify in Device manager that all devices relating to the phone are installed and there's no unknow devices.
Step 3: Root the Phone and install CWM (Chinese Version sorry but the bits that are needed have english written )
Download the Rooting and Custom Recovery tool here -- drive.google.com/file/d/0B8qJPucQA8GkQy1uTk93dUNuMkE/view?usp=sharing
Unzip and double click on the ZTE-V5-MAX-TOOL.exe
It should come up and ask for a password enter the following (no spaces in the password had too due to XDA posting rules) - www . ydss . cn
Now select Option 2 which is the Root option
Now the tool will detect the phone and press any key and it'll reboot (my computer installed more drivers at this point and I had to close the rooting tool window, reboot the phone and start again, once again selecting option 2)
Now it should proceed through the rooting process.
At the end it'll try and install a chinese verison of the Root Checker tool mine failed which is ok.
It then display Sucess.
Now at this point I rebooted the phone and installed a Root Checker to validate that I did have Root acess and I did, you can proberly skip this step.
I then fired up the Rooting tool again but this time selected option 3 which will install the Custom Recover CWM
Once again press any key and it will begin installing the custom recovery
Once complete you should see sucess.
Reboot the Phone and go to Settings > About Phone > System Updates > Recovery and it should boot to Recovery CWM if it does yay.
Step 4: Installing Gapps
Reboot the phone
Install ES File Explore and give it Superuser Access
Now go to the uper directoy and tap and hold on the System folder then view the details.
You'll need around 150mb free space in there to be able to install GAPPS, I had to install an app called "Uninstall" (red coloured trash can). I then uninstalled the following : Easy Mode, Handbook (as it's chinese), neoshare, nubia Niudun, Nubia PlatLogo, Nubia Poster and Video Sample.
I then had enough room.
Now download Micro Gapps (Go to drive.google.com/folderview?id=0B1T7tp6tJ_3kQkZSWjNsazJZbGc&usp=sharing
Then click on "1.10 update_gapps" then "pa_gapps-modular-m" and download it. Then put it in the root directory of you Phone Storage.
Now reboot into recovery (Settings > About Phone > System Updates > Recovery)
Go to the second Option in Recovery called "***** Zip**) and browse to the phones storae and install the Zip.
If sucessfull go back to the main menu of Recovery and go down to the (****Cache**) option and select, then select it again to confirm.
Once complete go back to the Main menu again and choose the top option to reboot.
Walla your done.
Website I for info: shuajizhijia.com/jiaocheng/9170.html&prev=search then use translate in Google.
Have fun guys.
Have fun guys, and keep in mind I probaly wont reply if you ask for help as I have a day job
Now select Option 2 which is the Root option
Now the tool will detect the phone and press any key and it'll reboot (my computer installed more drivers at this point and I had to close the rooting tool window, reboot the phone and start again, once again selecting option 2)
Now it should proceed through the rooting process.
At the end it'll try and install a chinese verison of the Root Checker tool mine failed which is ok.
It then display Sucess.
Now at this point I rebooted the phone and installed a Root Checker to validate that I did have Root acess and I did, you can proberly skip this step.
I then fired up the Rooting tool again but this time selected option 2 which will install the Custom Recover CWM
Click to expand...
Click to collapse
Hi m8, I'm still waiting for my phone, seems it will take a wile, as I don't have confirmation yet of shipping.
Now, I was reading what you posted above and I have to thank you for the mini tut, but I marked in red two lines that I'm quite confuse... Can you confirm that please?
Hey Mate,
I've fixed that up now good pickup
Cheers Eric
i got my phone with root without cwm
and found that playstore didnt worked, it has 4.4.4 version
any suggest?
Simply Skip these steps:
Now select Option 2 which is the Root option
Now the tool will detect the phone and press any key and it'll reboot (my computer installed more drivers at this point and I had to close the rooting tool window, reboot the phone and start again, once again selecting option 2)
Now it should proceed through the rooting process.
At the end it'll try and install a chinese verison of the Root Checker tool mine failed which is ok.
It then display Sucess.
Now at this point I rebooted the phone and installed a Root Checker to validate that I did have Root acess and I did, you can proberly skip this step.
very very useful
Dear Frenchie
I would like to express my sincere thanks for your magnificent manual
It has been very very extremely truly helpful for me
I can't express how much I feel grateful for you, this solved a problem that ruined my life
The manual is very accurate and detailed
Thanks very much
unable to add google account
Hi, I have just received my new ZTE Max 5 and I've spent all evening trying to set up my google account. The phone has google play store installed but I cannot install any apps because I cannot establish my google account. Every time I try to set up the account it says "there was a problem communicating with google servers". Any ideas? (I have disabled 2 google 2 step verification).
Can't turn on my phone
Hi, so I was trying to root my ZTE V5 Pro and when i reached the step where it was suposed to root itself, it reeboted and the computer stopped recognizing it. I tried rebooting it several times and restoring its fabric data but it doesnt pass the first screen. It can't open /dev/tty0 because there is no such file or directory. Can anyone please help me?
patseho said:
Hi, so I was trying to root my ZTE V5 Pro and when i reached the step where it was suposed to root itself, it reeboted and the computer stopped recognizing it. I tried rebooting it several times and restoring its fabric data but it doesnt pass the first screen. It can't open /dev/tty0 because there is no such file or directory. Can anyone please help me?
Click to expand...
Click to collapse
You said you have the "ZTE V5 Pro". Maybe that is just a typo, but this thread is about the "ZTE V5 Max", so be careful about what you do.
You can try looking at this post and see if it is helpful to you: http://forum.xda-developers.com/and...alcom-2-gb-t2965623/post63005167#post63005167
But you must make your own assessment and take responsibility for the outcome if it is not the right thing to do for your phone.
I just want the GAPPS zip File.
So, I was sort of thinking that at least rooting and OTA blocking with the handy hdx toolkit would be easy but I don't get the impression that it is working. My Firmware is 13.3.2.3.2 and I used towelroot via the toolkit. This is what I see when I root. (aren't allowed to post links/images yet so it's only a non-clickable link to the image, sorry)
i.imgur.com/GLtVd1R.jpg
As you can see, there are some error messages. It also asks me to select 'make it rain' but there is nothing on my device to actually select and it continues on without my input. It then says 'please wait until device reboots' but my device continues to be entirely unimpressed and doesn't reboot, not even a bit. In short, while the root *appears* to be doing something, I don't think it actually does because it can't find the stuff it needs. On the next screen it checks if the rooting worked but it only gets me another error message saying /system/bin/sh: su: not found
help, please?
You can download and install towelroot manually.
As for OTA updates, you can rename /system/etc/security/otacerts.zip to anything else (i.e. otacerts.zip.bak); that should block them.
I couldn't leave well enough alone despite @EncryptedCurse excellent advice and managed to troubleshoot it and get it working in the toolkit after all. In case someone has similar troubles (Error 2 and Error 3 are what I got at different times) here's how I got it working (in Windows 7):
-In the device manager I uninstalled the adb driver (with adb enabled the kindle is listed twice in the device manager, you should unistall the drivers of the one that *isn't* listed under portable devices) and restarted the computer. Edit: On second thought: I'm not sure if that uninstall worked. I think I needed to use uninstaller.exe in C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers to really remove the driver.
-Then I disabled ADB in the kindle. I also shut down my antivirus (not sure if it made a difference but some people have reported interference). Then I used the toolkit to install adb drivers again (in the instructions there it says to have adb enabled while doing this but if you get error messages while rooting try it this way.).
-Now I rebooted the computer again (this is important), checked that antivirus was still activated, checked that Bluestacks was *also* still shut down (having it or another emulator open leads to a complete different error message, I have learned ) and tried rooting with the toolkit again. It worked with no troubles.
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Works like a charm on J320FN.
I signed up just to say, after hours of trying different guides, accidentally factory resetting once or twice, and getting my phone stuck in a boot loop, this method worked. BUT it did factory reset my phone, but that's fine I've everything backed up and it wont take long to get it back. Maybe I pressed something I shouldn't have.
Some info on my phone in case it helps anyone in a similar position to how I was:
At one point I installed stock firmware from to get my phone out of the boot loop, I can't link it but if you google "J320FNXXU0APB4_J320FNO2C0APC1_O2C" (WITH quotes) you should find the page.
After doing that:
Android version: 5.1.1
Model number: SM-J320FN
Kernel version: 3.10.65-7225942 (Sun Feb 14 2016)
Build no: LMY47V.J320FNXXU0APB4
Baseband version: J320FNXXU0APB5
I hope I typed all that right. Thank you so much!!
have anyone tried on j320v?
kekambas18 said:
have anyone tried on j320v?
Click to expand...
Click to collapse
Going to attempt that right now wish me luck.
---------- Post added at 08:06 PM ---------- Previous post was at 07:09 PM ----------
And it didn't work. Not suprised, but I at least tried.
GN9166 said:
4. Add twrp.zip to AP tab
10. Copy SuperSU into internal memory from your PC
Click to expand...
Click to collapse
Hey, why this guide doesn't mention that I have to download something. It's definitely NOT definitive! What is twrp.zip? Where do I take it from? What is AP tab? Where exactly do I copy SuperSU? What will happen in the download mode?
Problems in Root J320AZ
My name is Dario Lobos. I am working as a gardener and I am making a little application in my phone. I don't have computer so I did it in Java n-ide. I started with a Samsung core prime but the screen was broken and I did change it and the technicians broke it and gave me an Samsung s320. Android 6 (api23) and after that the java n-ide don't compiles the permits that I am requesting in the manifest so I can't grant permissions to my apk. Parallel of it the phone always show a notice unauthorized actions have been made please restart the phone to undo the unauthorized actions. And the lookout said message root access detected. I wrote Samsung without any positive answer. No technical assistance at all. But the roots checkers says that I have no root in my phone. Now I am trying to do a root. But I don't know if someone have a hidden root access in my phone. A page suggest Framaroot and you suggest kingroot. I don't want to store all my phone in their server to root it. Does any program that don't access to all the data to root the phone?. I am writing you since you have more experience to request you if it is in your possibilities. Also to ask you about prompt root commands. Where I can find info about that. A suggestion to solve my problem. My simple all is here
....github.com/DarioLobos/sistemariego
....github.com/tranleduy2000/javaide/issues/163
....1drv.ms/u/s!Asr3Ewn45KOLtGOqDkoMq20A-hbc?e=24Wwx3
The system don't let me put url since I am new add please http...
Well thank you in advance and any help is wellcome
Regards,
Dario Lobos
Adding more information to what I did to try to find a an answer. I tried to root with Frama root 1.9.3 and the installation only request me access to the camera and after installed the programs showed a banner that said can't root your device.
Today I downloaded from firmware.mobi some zip and img files but I already I couldn't learn how to use them properly.
I am trying to avoid the exploids system because maybe is a hacker in the middle. Always I am trying to root w/o SIM card and with Wi-Fi off. So I think that kingroot and kingoroot are not useful for my.
I am trying to buy an old desktop computer as an alternative.
Well any suggestion is usefull and wellcome.
Before of all of that I did two factory reset in recovery mode.
Then I installed an apk Dev Tools (trinea) and one menu request me developer permit in accesibility setting. The phone started to change the color of the screen and the outside padding start to flashing red. Then was open a setting menu and the language was changed suddenly to Japanese or Korean while the screen was lighting like receiving knoks. I turned of the phone and restarted and hopefully I remembered the position in settings to change the language.
After that I had to use an apk repair system and fix Android and the screen get better but the padding outside still flashing in red ones in a while.
Also where added plenty sha certificates (settings user certificates) like system certificates
Go daddy
VeriSign
Some governments (Turkish, Spain, Japan, Germany, Holland, and more)
The Catholic religion with 6 certificates called
Quo Basis
And much more.
So I did another factory reset recovery mode. And the screen problem disappeared and the certificates that I turned off manually firt too (All) but the root alert in the look out and the security notice didn't disappeared.
Today I wanted to print your forum page and the phone put error. Only put error in your forum page.
Other thing that I had to to just after the unpackage the restored Android is disable the setup and transfer. Because I think that is this apk that were using to access and modify my files and grants permissions.
I installed the TWRP application but said the phone have no root.
Today I opened the developer option in settings and turned to on the OEM option to unlock the boot loader but instead of put a banner saying that all data will be erased put a banner saying that the device protection will be not work and didn't do the reboot or nothing more that put this dialog.
Dario Lobos
great, unlocken/rooten worked here. But after that, the mobile became unusable. All google apps complain no connection is available. I cannot update google play store, cannot update other google apps like youtube, or install any app now.
And perhaps it does not have anything to do with the mentioned process, but before I started the process, I made sure all nessacary file were on the sd card. But now I have finished wiping the data / cache from the recovery and all files on the sd card are gone.
I cannot login to google photos to see if the apps are backupped because every google app complains no internet connection is available.
So yes, rooting/unlocking worked, but that's the only thing that worked here. I now got a useless Samsung J3 2016...
I need assistant trying to root my J320FN, which I mistakenly wipe some backed up recovery file now, I can not get through with the rooting and I can get back to forma phone setting am locked up , samsung phone not coming up again please what can I do ?
GN9166 said:
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Click to expand...
Click to collapse
The link says "the key is invalid"
Hello guys,
I have come many times here to root my phone and I did success, thanks to you.
But now there is a new problem and I did not find any solution, then I will try to explain with my bad english what I did :
At first I tried to flash TWRP (an unofficial one many said it was working) on the phone after unlocking the bootloader, SP flash tool said it was successful.
But it was not, after reboot former recovery was still there, not TWRP (does anyone knows why it did not work ?).
I tried to install Lineage, which bricked my phone. After the debrick, I installed Android 10 GSI, and it worked but impossible to use MTP, Bluetooth or to download with the HTMLViewer (in other words, the system was unusable).
Then I reinstalled the ROM provided by Blackview, and installed Magisk, rooted the phone, also suppressing all the Google stuff it was possible.
And there is the main problem : I think I erased the NVRAM while unbricking the phone and then I have got an overlay of red chinese caracters on the corner of the screen. I tried to replace the original IMEI and MEID successfully with MAUI Meta, but chinese caracters are remaining here.
A screenshot of the ugly writings : https ://ibb.co/bWWp1wr
My phone is a Blackview BV9500 Plus.
Any suggestion about how to remove them ?
Thanks in advance !
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
John Manjiro said:
I have just tried to replace the BT/Wifi adresses with SN Writer.
The soft said it was a success, but in the system parameters of the phone these adresses were not modified. I wonder why...
I guess these adresses (and/or the serial number, in others words all the parameters of the NVRAM) are the causes of the message. What do you think about that ?
Also, in the official firmware, there are some files for only one choice for the AP and MD databases (what are the correct ones ?).
I think I almost tried everything I am able to do...
Any suggestion or solution ?
Thanks
Click to expand...
Click to collapse
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
@John Manjiro
It seem's Trusted Execution Environment (TEE) for Android is installed on your phone. It's a secure Operating System (OS) what runs in parallel to Android OS. TEE protects phone from malicious apps installed by the user and potential vulnerabilities that may be discovered in Android.
Did you ever find a solution to this?
huafu said:
Hi John, same issue here, but not same process. Phone won't boot so I've restored which made IMEIs being 111111 and 22222. Used MetaModem (successor of AMUI Meta or whatever you used is called) to restore correct IMEIs. But got those red "TEE" and "Google" followed by Chinese chars. Will keep you updated here if I can find a solution.
Click to expand...
Click to collapse
I'm having the same issues with a BV9800 Pro.
cnorman27 said:
I'm having the same issues with a BV9800 Pro.
Click to expand...
Click to collapse
Still same issue, got a long email thread with BlackView team which tried to help even tho they seem to not get well my Enlgish. They keep giving me a version of SNWritter where I had to modify some ini file in some tee subfolder. But the exe couldn't launch and was complaining about MVC100.dll missing. I could fix that by downloading from the web a SNWritter tool with working exe. Now I need to find some special screwdriver so that I can remove the battery from the phone. Doing so will keep the phone appearing as MT65XX Preloader in the devices manager and not for only one second...
Just FYI, I gave up and was using it with this **** red overlay.
Last week I was really bored of this overlay so I've installed AOSP 10 GSI. Tho it doesn't pass safety net, and believe me I've tried many way to make it pass. So I cannot use most of my banking apps + no google pay :-(
I even tried with AOSP 9, 10 and 11, as well as LineageOS 15, 17 and 18... unable to pass safety net even with universal safety net fix, magiskhidepropsconf, ...
Hahaha, looks like I just needed to write the previous post and finally got it wokring on PixelExperience Android 10 rooted and passing SafetyNet!!!!
Quick howto if someone is interested:
with SPFlashTools, restore the original ROM
Activate developer mode + USB debug
on the computer, adb reboot bootloader
Download PixelExperience system image and extract it (on linux with unxz) - I've tried many other ROMs with no success. Also while the device is not an A/B, you must download A/B images else they do not work.
fastboot -w && sleep 1 && fastboot flash system path/to/downloaded/system.img && fastboot reboot
Skip everything you can skip at first boot (you can restore later from an online backup or another android phone)
Download MagiskManager apk
adb push path/to/MagiskManager.apk /sdcard/download/
On the phone go in the file manager in download folder and install MagiskManager
copy the boot-signed.img from stock ROM on the device adb push path/to/boot-signed.img /sdcard/download
Open Magisk Manager, install, uncheck the first checkbox (to disable encryption, I forgot the exact label) but keep "recovery mode" checked, then click on next, then second option (patch boot image) and select the boot-signed.img you uploaded on step 10
download on your computed the patched image using adb pull
adb reboot bootloader
fastboot flash boot path/to/downloaded/patched-boot-magisk.img
You need to reboot in recovery mode, this is important: press power and volume up until you see the Blackview logo (can take up to 40 seconds)
select "reboot" (first option) in the recovery mode
once rebooted, open magisk manager, activate magisk hide and go in plugins.
install MagiskHideProps Config but do not reboot yet
install SafetyNet fix (download from here, it's not in online modules)
click on reboot
It'll reboot in recovery, that is normal and you MUST boot your device into recovery each time you need to boot/reboot it. Once in recovery, as before select reboot
Once it has rebooted, go in magisk and change in the settings so that the default method is not "prompt" but "grant".
from your computer:
adb shell
su
props
Select device fingerprint, then choose from certified, google, pixel 2, android 10
confirm but do not reboot when asked, simply exit
adb reboot recovery
again, select "reboot system"
Once booted, open Magisk Manager, click SafetyNet, it should pass SafetyNet.
Scroll down notification, and choose "continue device setup"
continue as normal the setup of the bv9500 plus!