I have found a way to root the Samsung Galaxy J1 (SM-J100VPP, Verizon) without needing to flash modified, rooted firmware using ODIN. I do not know if this unlocks the bootloader. Maybe someone can reply with an answer.
1. Make sure ADB/USB debugging is turned on. Settings > about phone > tap on 'build number' seven times to enable developer options.
2. Tap back button once and tap developer options. Make sure the box next to 'USB Debugging' has a check mark.
3. Plug your phone into your PC and open up an ADB window.
4. Download and install the Hidden Menus APK attached to this post, located at the bottom of the thread. (If using ADB to install, place the APK in your ADB folder and open an ADB command window and type: adb install HiddenMenus.apk)
5. Open the Hidden Menus app and scroll until you see 'Rlz Debug UI' and tap on it.
6. Where it says 'OEM Mode', make sure 'on' is selected (tap the circle next to OEM Mode to turn it on).
7. Go to my Google Drive, download and install 'android_root.exe'. This will install an older version of KingoRoot onto your PC.
8. Open KingoRoot for PC and connect your phone to the PC.
9. At the very bottom, left corner of the KingoRoot for PC window, make sure to UNCHECK the box that says 'install recommended app'.
10. Click on root and let KingoRoot root your phone.
Replace KingoRoot with SuperSU
I don't like one-click-root apps. I don't trust them. So whenever possible, I try to find methods to install SuperSU. Below is a guide to replace KingoRoot with SuperSU. The method in this thread works and only consists of a few steps. First you'll need to go to the KingoRoot homepage and download the APK for Android and install it. Then follow the steps below:
1. Delete/Uninstall Kingouser, but keep Kingoroot. DON'T reboot your device
3. Install SuperSU apk from flashable zip v2.79 (APK provided by me, attached at the bottom of this thread).
4. Launch it, press "continue" and "normal" wait until the update is successful. (You might have to close the SuperSU app and reopen it to complete this step).
5. Reboot and uninstall Kingoroot.
Thanks everyone. I really love this little phone!
ok, so all that has happened here IS. you happened to have a samsung galaxy j1 sm-j100vpp verizon prepaid phone that happened to NEVER be updated to the unpatchable 5.1.1 and you rooted the existing firmware that we all have to downgrade to, to be able to root. And to answer your question about the boot loader.... NO, flashing or MODIFYING the firmware has nothing to do with the boot partition.
BUT. the super su replacement has caught my eye and is how i found this post. I will check the work and report back. this would be a huge step forward in creating a 32 bit custom twrp as the chipset in this phone only supports 32 bit and is why twrp (cwm similar etc....) does not work on this device. i have noticed another samsung device that has "alot" of the same chipsets but still supports 64 bit and has a promising twrp I may be able to compile as a 32 bit only recovery img. after that. its smooth sailing.
Related
YOUR PHONE WILL BE RESET!! BACKUP ANY DATA YOU WANT TO KEEP BEFORE PROCEEDING!!
download this
follow these steps:
1. go to settings/about/software information/more and click a few times on build number until "your a devoloper"
2. go to settings/developer options and activate usb debugging
3. unzip htc tool
4. open htconetoolkit.exe
5. install drivers (step 1 on toolkit)
6. regester at htcdev.com (step 2 on toolkit)
7. plug phone into computer
8. follow steps 3-5 in toolkit or htcdev website to unlock (toolkit will use website but opens pages you need, easy!)
9. run twrp recovery on right side of toolkit
10. click on "perm root" on bottom right of toolkit (last option) and run
11. donate to hasoon2000 and jzm
12. profit!
VIDEO GUIDE HERE, BY phonetechkid!! Good job on it!
my favorite root apps:
es file explorer
airstream
sixaxis controller
there is many other reasons to root though...
Moved to General.
orangekid said:
Moved to General.
Click to expand...
Click to collapse
thanks
Anyone know if this is compatible with Windows 8.1? Not working for me so far, but maybe its just my setup.
NVM - Updated adb version, and then the phone asked to accept the connection, and voila
For some reason the toolkit won't flash the recovery to my device. it tries to, but it gets stuck. i let it for for 22 minutes and it's still not finished. i don't want to unplug it but i don't think it's going to finish at this point. I'm also getting my stock recovery is busted at this point, no?
Hello all,
I have a Z2 on MM with 23.5.A.1.291 firmware. I want to root and install a custom recovery and have looked at the threads on here about it but I'm pretty confused! None of the various options seem to be up to date, or stable, or understandable.
This thread seems to be the most up-to-date, but the instructions are pretty vague, files seem to be missing, and quite a few people seem to have had problems with it.
Can anyone explain the simplest, safest way to root the Z2 on the latest firware? Or at least help me make head-nor-tail of the existing instructions...
Many thanks
tooplanx said:
Hello all,
I have a Z2 on MM with 23.5.A.1.291 firmware. I want to root and install a custom recovery and have looked at the threads on here about it but I'm pretty confused! None of the various options seem to be up to date, or stable, or understandable.
This thread seems to be the most up-to-date, but the instructions are pretty vague, files seem to be missing, and quite a few people seem to have had problems with it.
Can anyone explain the simplest, safest way to root the Z2 on the latest firware? Or at least help me make head-nor-tail of the existing instructions...
Many thanks
Click to expand...
Click to collapse
Download .314 ftf (or any rootable ftf for z2)
Then search for dual recovery for Xperia z2 and download the last version
And download Xperia root kit
1. Flash the ftf file that you have downloaded
2. Root it using Xperia rootkit(usb debugging must be on)
3. Install dual recovery using your pc
Thats it now you have root and recovery
I followed the guide you linked to and everything worked perfectly! As long as all files are available, I would do this again. Be sure to follow the directions exactly and you'll be fine.
Whatever you do, DON'T try to flash Nut's Dual Recovery on MM, because you'll then be in a continuous bootloop at the Sony logo; don't ask me how I know this! ;>)
wicozani said:
I followed the guide you linked to and everything worked perfectly! As long as all files are available, I would do this again. Be sure to follow the directions exactly and you'll be fine.
Whatever you do, DON'T try to flash Nut's Dual Recovery on MM, because you'll then be in a continuous bootloop at the Sony logo; don't ask me how I know this! ;>)
Click to expand...
Click to collapse
I've read through that entire thread pretty much and still haven't found clear step by step instructions :/
I've downloaded the flashtool but don't know what to do now: there is no option to 'flash' or select a file..
Surely someone out there is able to write a clear, full, step-by-step guide to root this very popular phone..?
I've rooted many different phones and installed plenty of ROMs but never found so much confusing information before!
IDIOTS GUIDE Root and TWRP
Okay, may as well do it my self...
IDIOT'S GUIDE: (for Z2 Marshmallow .291)
1. Firstly go to https://drive.google.com/file/d/0B6aEcBP7FwsWUGpQdHdvaVRCQlk/view and download the .291 kernel.
2. Then download SuperSU from here.
3. Put both these files on your phone's SD card.
4. Next download the .575 kernel here.
5. Before this can be used, you need to change it from a .zip file to a .ftf file.
- Go to the file location in the file browser.
- Click on the 'View' section in the top ribbon (Win 10).
- Check 'file name extensions' in the 'show/hide' section.
- Rename the kernel file, deleting the .zip and replacing it with .ftf instead at the end.
6. Download the Recovery for MM from here.
Extract the zip file.
7. Download the correct drivers for your phone: simplest way seems to be by installing Sony PC Companion and connecting your device.
8. Download and install 'Flashtool' from here. (The 0.9.18.6 version seems to have better compatibility).
9. Install the drivers for the flash- if you are on windows 10 or 8 you will need to turn off driver signing first:
A) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
- This will take you to the advanced boot menu.
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machineTo install the drivers you need to go to the Flashtool install folder (e.g. C:\Flashtool) and go in to the 'drivers' folder and run the 'flashtool-drivers.exe'.
- From the menu select Flashmode drivers, Fastboot drivers, and then scroll down and select Xperia Z2 device drivers (not sure if this last one is necessary if you've done step 7 previously, but I did it and everything worked.)
- Click install, and click okay on the warning messages.
10. Enable developer options on your phone (repeatedly tap on build number in 'About phone' in settings.)
Then make sure that USB Debugging is enabled, and in 'Security' that 'Allow Unknown Sources' is enabled.
11. Back up vital data (though you shouldn't loose anything), then power your phone off with it not connected to the computer.
12. Startup Flashtool and let it update etc.
13. While holding the volume down button on your phone, connect it to your PC.
Flashtool should respond and spew out a few lines of text ending with something like 'Phone ready for flashmode operations'.
14. Click on the lightning bolt, select 'Flashmode', and then in the next window browse to the location of the .575 .ftf kernel file you made. Select it, then click 'flash' at the bottom right. There should be more lines of text hopefully showing that this is completed successfully.
15. Close Flashtool, disconnect your phone, then turn on your phone.
16. Flash the recovery: Reconnect your phone to the PC and select MSC mode.
Go to the unzipped recovery and run 'install.bat' as administrator (if that doesn't work try not as administrator).
If the window that opens up stays on 'starting daemon...' for a while check on your phone as you may need to authorize the 'unknown source' connection from the PC.
The installation should complete with a 'press any key to continue'. Your phone should then automatically reboot in to TWRP recovery.
17. Install SuperSU: Once in TWRP go to 'Install' and select the SuperSU zip (you may need to select 'storage' and choose your SD card first). Swipe to install!
18. Reinstall the .291 kernel: still in TWRP do basically the same as for SuperSU but this time with the MM .291 zip.
19. Cross your fingers and reboot!
20. All being well you are now rooted, you can check root by installing 'Root Checker' form the play store.
21. Open a beer and relax!
(22. Install Cyberian camera!)
Please give me some thanks if I have helped you!
I will post this as a new thread as well so it's easier to find.
Credits:
Rocker00
Xperia Blog
Dr. Death
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Sorry to bump this, but any chance someone has time for a response?
Bllur said:
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Click to expand...
Click to collapse
OK. I don't know about those steps, as I took a different route to get to the Nseven rom. Make sure you have the ADB/Odin 3.09 or 3.10 and Samsung drivers already installed on your PC. You might want to get/DL Kingroot.apk aswell.
Step 1.
Download the 5.1.1 BPA1 full firmware, this should be a all in one file. None of these separate files eg.BL AP CSC..
"I downloaded this from Sammobile"
Step 2.
Open Odin and add the firmware file to the AP tab by clicking on it and navigating to where file is located. This takes a little while to show as Odin checks the file before adding it( Make sure Auto reboot and F.Reset Time are ticked)
Step 3.
Make sure you have unlocked "DEVELOPER MODE" and "USB DEBUGGING" is ticked before powering down your phone and putting it into download mode by holding the 3 keys Vol Down,Power,Home then Vol Up to continue, once your in DL mode connect to PC. There may be a little pause as your PC may install further driver files before Odin recognizes you phone and adds it under "ID;COM". Once your phone has been added into the ID:COM you can go ahead and press START. Allow Odin to do its stuff and once your phone reboots you can unplug from the PC.
Now you should be on the 5.1.1 BPA1 firmware.
Allow your phone to boot completely, you can skip the whole setup process but you'll need to be connected to WiFi for the next process.
GAINING TEMP ROOT.
Step 1.
Transfer the "KINGROOT.APK" to your phone and install but don't open it yet.
Step 2.
Unlock Developer Mode again and tick USB DEBUGGING. * This is necessary for ADB.
Step 3.
Open Kingroot and allow it to check for root this can take awhile just be patient. Once it throws up the results it'll ask if you want to try "TRY TO ROOT". click on the tab and watch the process. " Your phone will reboot a few times during the process" I just reopened Kingroot each time it did until the process was done. ******You'll have to repeat this process again***** as your Phone reboots while your pushing the command file through ADB. Losing root in the process.
Now that you've repeated the process again and you have gained TEMP root. You can confirm this with "ROOT Checker" you can reconnect your phone to your PC.
Step 4.
Make sure you have the "Samsung_unlock_n4-fix script file in your FASTBOOT folder located in the extracted files of ADB.
Now open a ADB command window *Open this in the same folder where you exacted ADB. to do this hold Shift and click Right mouse button on any clear area of the ADB folder and scroll down to "Open command window here"
Step 5.
Within the command window type "CD Fastboot"
To confirm your device is added type" ADB devices"
You should see a random number listed under "List of devices"
If you do your set to go.
For this next step its best you have the Notepad open with these commands to make it easier. ****COPY & PASTE*****
The commands are.....* without the numbers in front of it
#1. adb push samsung_unlock_n4-fix
#2. adb shell
#3. su
#4. cd/data/tmp/
#5. chmod 777 samsung_unlock_n4-fix
#6. chown root. root samsung_unlock_n4-fix
#7. . / samsung_unlock_n4-fix
OK time to push the file. Start with the 1st command and press enter. Then the 2nd and press enter. Then the 3rd and press enter. Then the 4th, then the 5th and 6th then the 7th.
Now once you've enter the 7th command you'll be presented with a warning just type YES ****USING THE SHIFT KEY WHILE DO SO****** and wait while the process completes. Your phone will reboot to confirm the process is complete.
******NOTE*******
Your phone will reboot but reboot into a Bootloop, don't worry just pull the battery and memory card. Replace the battery but not the memory card. Reboot into DL mode to confirm that you are now in/a Developer Mode.
**********CONGRATULATIONS YOU JUST UNLOCKED THE BOOTLOADER********
*****NOW HERE COMES THE STINK PART*******
You'll need to flash the N910VVRU2BPA1_N910VVRU2CPD1 full firmware with Odin this will update the Bootloader to CPD1 required for Nseven to boot. But in doing so will LOCK the bootloader again. ARRRGGGGG!!!!!!
So.....
Step 1.
Put your newly unlocked phone into DL mode again and reconnect to Odin.
Step 2.
Place the BPA1/CPD1 firmware into the AP slot and press start
Disconnect when the phone reboots. Allow it to fully boot/skip the setup process. ******Note you will need Mobile Data as WiFi is non usable due to the updated firmware.
Step 3.
Reformat your memory card using your PC and place back into your phone, reconnect your phone to PC and transfer ROOTKING.APK over again.
Step 4.
Turn on Mobile data. Install KINGROOT and open, follow the same process you did to unlock 5.1.1. This time it may take a little longer and there's a chance Kingroot will fail to root just try again.
*It did it to me.
*There's a chance your phone will reboot when it comes to pushing the command file, unfortunately that's just the way it is. Just repeat the Kingroot process again.
Step 5.
Now that you've gained TEMP ROOT again, You'll need to run ADB and push the scripts again. Just follow the same process you did for 5.1.1 BPA1.
Even down to pulling the Batt & Memory card.
Step 6.
Now that the bootloader is unlocked, place phone into DL mode and reconnect to PC and Odin. Now again AP slot navigate to where you placed your Custom recovery.
****NOTE. I used TWRP 2.8.7.0 trltevzv.img as TWRP 3.0.2.0 Didn't work for me. And flash disconnecting when phone reboots.
********Congrats you now have a UNLOCKED BOOTLOADER and a CUSTOM RECOVERY on 5.1.1 with a CPD1 bootloader.
Time to flash Nseven. *don't forget to reformat your memory card.
To flash Nseven, just copy over the Nseven zip file to your memory card and flash using TWRP.......ENJOY.
* Note. I didn't flash anything else apart from the CPL1 Nseven
Even though I had all the files DL. Just follow the Nseven forum if you experience any problems.
Hope this helps getting you into/onto Nseven.
Hi all,
I'm not an expert with flashing ROMs/recovery and stuff, but I think I know the basics. So, if I was missing something, please forgive me in advance
I'm trying to install TWRP on my Oukitel K6000 Pro, but can't do it for some reason. The things I tried:
1. Rooting my phone w/ kingroot to install flashify. Kingroot failed to root my phone.
2. Via linux machine, using fastboot command. Fastboot failed installing the recovery (USB debugning was turn on. OEM unlocking was turn on, but I wasn't sure I even needed it). Error message I got: "FAILED (remote: download for partition 'recovery' is not allowed"
3. Using windows 7 and windows 10 machines to install it via SP-flash-tool (USB debuging and OEM unlocking was turned on). The SP-flash-tool did not recognized my phone.
4. Using SP-flash-tool with FWUL live-CD. It did not recognize my phone.
5. Using SP-flash-tool with linux machine. It did not recognize my phone.
As for #3 above, I was trying to install MTK drivers before performing the flash process. I think I got it right (for the win10 machine, I rebooted to a mode without signature check as required), but I'm not sure though.
If anyone can step in and help with that - I would much appreciate it.
Thanks in advance,
Tamir
you need the right drivers and the right adb tool.
Download adb tools of android sdk, google it.
Then download the oukitel drivers-> Driver_Auto_Installer_v5.1453.03, search for those., install them.
Try again, good luck.
Rooting and unlocking your phone will format your phone, beware of losing everything on it.
Btw, never use kingroot. Use latest SP Flashtool Version 1728,
Guide:
Download Magisk V16 or SuperSu to your micro sd on your phone.
--(Download your desired firmware, if you want to upgrade as well. (if you want, not needed, since you only want to root or install twrp)--
Download SPFlashTool compatible TWRP from a site that i can't mention here.
Turn off your phone.
Open Splflashtool, select the Android Scatter file that was downloaded with your twrp.
A little bit under that, select Download Only, and NOT firmware ugprade etc.
Now click Download, connect your turned off phone to your pc.
You should hear a windows sound, look at the tool and DO NOT Disconnect your phone. until a popup with Success and a green Symbol appears.
be patient and let it run. (shouldn't actually take longer than 3-5seconds)
After it is done, press simultaneously the Power and Volume+ Keys until a really small menu on the left side screen appears.
Now you can navigate with the Volume+ Key, from the top to the bottom, in an endless loop.
With the Volume- Key you can select on of the three options:
Recovery <-this is what we want, select it!
Fastboot (not really needed for us)
Normal (normal Reboot - Start of the phone)
You will now see the bootlogo, then the twrp menu will show up.
Now you can Flash Magisk or SuperSu for Root. Wipe Dalvik and cache, Reboot, Enjoy.
Hello.
This post describes how to reboot the Alcatel OneTouch Pop Icon A564C Yaris5NA into EDL mode. This can be achieved without root. It can happen on both Windows and Linux computers. It requires ADB to work.
1. Go into settings and "About phone" and tap the build number "01001" for about seven times.
2. Go into "Developer options" and enable "USB Debugging".
3. To install ADB drivers on Windows Vista, look for "Minimal ADB and Fastboot" on XDA and download extract and run the exe file. Do not forget to install Google drivers. On Linux, just install adb through terminal.
4. On Windows, go into "Device Manager" in Windows and look for "Android device" with a yellow triangle with an exclamation point. You may have two of these on your computer, so be sure to install drivers to both devices to avoid any error.
5. Right click on these devices and the menu appears hit "Update driver", than select browse my computer for drivers and eventually show all devices. Find the Google Inc. drivers and install one of three drivers; the "Android ADB interface" should work, but you may have to use the "Android Composite interface".
6. Go open CMD or Terminal and type adb devices. You will receive "Enable USB Debugging?" on your A564C phone so be sure to check the box and press Enable.
7. Now check adb connection by typing "adb devices", and the device should appear in the terminal; there should be letters and numbers on the left and authorized on the right.
8. Now type "adb reboot edl" to send the device into Emergency DownLoad mode. When you look on Windows a box appearing with QualComm HS-Loader 9000 (COM4) drivers will have installed. Look into Device Manager under ports (the serial cable icon)
Well, if you have this phone A564C and would like to develop on it, this guide may have motivated you to do make custom software. I think the only way to flash firmware is through QFIL program on Windows. Now we are looking for a FireHose programmer for the device in an attempt to unlock the bootloader the way the new ZTE method is described. My goal is to find the right FireHose programmer and to examine the partition manager and edit the bootloader to unlock it, or perhaps a way to somehow put the su binary in the /system/bin folder, or put a custom recovery on the device. That is my goal.
Here is my background on my device:
I have owned the Alcatel OneTouch Pop Icon A564C for over a year. I have read the posts describing many users who do not have enough space on their internal storage and that is why they need root. I have also read KingRoot can root but for me it is the opposite. I had tried rooting many times with the KingRoot. When the metre reaches a certain point, usually 18% or 70%, the phone crashes and reboots automatically or freezes and requires holding the power button to reboot. The phone is seemingly unable to root. Last week I acheived a true temp root that was lost upon reboot; the way I did it I installed KingRoot apks I downloaded from AndroidFileHost in order from oldest to newest, ran them once for reboot, then proceeded to uninstall each one and reinstall the newer KingRoot. I had noticed a phenomenon when using a newer KingRoot than going to KingRoot 4.1 I received root failed and it went back to 70% and I achieved temp root that way. I than restarted the phone in order to restart the method after a data wipe.
I then thought if there were other ways to root a phone other than using one-click rooting methods such as KingRoot. The phone was manufactured about six years ago, so it is old enough that exploits could potentially root it. I had tried Framaroot and Towelroot; both did not work. I installed a DirtyCow checker apk and it said the phone was patched, so I assume an exploit based on DirtyCow would not work. There may be one more method to finally allow root; it is called QuickRoot a Proof-of-Concept root for Android devices. It may work on older devices, but I do not know how to compile for Android 4.4.2.