Related
Can anyone help me out with rooting galaxy core prime sm-g360h model phone with kit kat 4.4.4 android version.
rooting samsung core prime?
can anybody plz suggest how to root samsung core prime? i'm gonna buy it within next 7 days & i've seen everywhere, but can't find a post which'll help to root this phone. kindly help me.
Same problem. I cannot root Samsung Galaxy Core Prime (SM-G360F)!!
try this one
bluebeetle2332 said:
Can anyone help me out with rooting galaxy core prime sm-g360h model phone with kit kat 4.4.4 android version.
Click to expand...
Click to collapse
try this link
http://www.4shared.com/rar/2MMnMoaAba/G360H_XXU0ANK6_root_kernel.html
flash it, but to be honest i didn't try it so try it on your own risk
http://www.srsroot.com/supported
Please use find in page and search G360, Srs root supports its very few firmwares. So you might need to downgrade your firmware.
But i have yet to check if its true or not.
I tried SRSRoot. It says that SU was installed (see messages below) but nothing was installed indeed. I tried several times. While all the times it reports that SU was installed the device is not rooted. HELP!!
---= SRS One-Click-Root v4.7 =---
7:30:42 ìì - Starting ADB Server..
7:30:47 ìì - Manufacturer: samsung
7:30:47 ìì - Model: SM-G360F
7:30:47 ìì - Android Version: 4.4.4
7:30:48 ìì - Build ID: KTU84P.G360FXXU1ANL3
7:30:48 ìì - Board ID: MSM8916
7:30:48 ìì - Chipset Platform: msm8916
7:30:48 ìì - Getting OffSets.. : 0x8003 0x8005 (False)
7:30:48 ìì - Query Server for Best Method.. Found Rootkit: 4
----= Start Rooting Process.. Please Wait =----
7:30:50 ìì [+] Testing exploit: root4 (please wait..)
7:30:53 ìì [+] Device Reboot #1 (Wait till it's started)
7:32:43 ìì [+] Device Reboot #2 (Wait till it's started)
7:34:12 ìì [+] Remounting /system Filesystem as R/W..
7:34:12 ìì [+] Installing SU Binary...
7:34:12 ìì [+] Installing SuperUser APK...
7:34:12 ìì [+] Remounting /system Filesystem as R/O..
7:34:19 ìì [+] Rooting Complete !
iakovosmavro said:
I tried SRSRoot. It says that SU was installed (see messages below) but nothing was installed indeed. I tried several times. While all the times it reports that SU was installed the device is not rooted. HELP!!
---= SRS One-Click-Root v4.7 =---
7:30:42 ìì - Starting ADB Server..
7:30:47 ìì - Manufacturer: samsung
7:30:47 ìì - Model: SM-G360F
7:30:47 ìì - Android Version: 4.4.4
7:30:48 ìì - Build ID: KTU84P.G360FXXU1ANL3
7:30:48 ìì - Board ID: MSM8916
7:30:48 ìì - Chipset Platform: msm8916
7:30:48 ìì - Getting OffSets.. : 0x8003 0x8005 (False)
7:30:48 ìì - Query Server for Best Method.. Found Rootkit: 4
----= Start Rooting Process.. Please Wait =----
7:30:50 ìì [+] Testing exploit: root4 (please wait..)
7:30:53 ìì [+] Device Reboot #1 (Wait till it's started)
7:32:43 ìì [+] Device Reboot #2 (Wait till it's started)
7:34:12 ìì [+] Remounting /system Filesystem as R/W..
7:34:12 ìì [+] Installing SU Binary...
7:34:12 ìì [+] Installing SuperUser APK...
7:34:12 ìì [+] Remounting /system Filesystem as R/O..
7:34:19 ìì [+] Rooting Complete !
Click to expand...
Click to collapse
Which firmware did you try?. The same one mentioned in supported in the list?.
Where can I find the firmware of my cell? Do you mean the "Build ID"? It is KTU84P.G360FXXU1ANL3. This is exactly the same as the one in the supported list.
My cell phone also provides several other parameters:
Baseband version : G360FXXU1ANL3
Kernel versoin: 3.10.28-294663, [email protected] #1, Fri Dec 5
Build number: KTU84P.G360FXXU1ANL3
KNOX version : KNOX 2.2, Standard SDK 5.2.0, Premium SDK 2.2.0, Customization SDK 1.0.0, Conetiner 2.2.0, IM 2.0.0, CEP 2.0.0 ...
http://forum.xda-developers.com/showthread.php?t=3032893
Samsung galaxy core lte sm-g360f
Hello,
This method for get root Will Work and for g360f version ?
Thanks in advance
Still I can't root the device!! :crying:
The instructions say to get the G360H root kernel (step 2 on youtube video). Where do you find this file? I have G360F. Is there a root file for G360F?
Also what do you mean when you say "Step 2: Install iroot for pc. " in your instructions? Should we use iroot or Odin ?? I used iroot and it couldn't root my device (BTW I got several virus pop-ups from mcafee but my PC and cell are still alive )
Root file link is given in youtube video description.
Flash root kernel via odin.
Then insatall iroot in your pc
Then root your device.
Help get CWM for SM-G360H.
Same here....I am unable to root my Samsung Galaxy Core Prime. Somebody help please!!
I guess nobody in xda is interested in developing a guide to root smg core prime.
Personally i would buy that person a beer who so ever comes with a valid method to root the fort knox solid... Samsung Galaxy Core prime
Sent from my GT-I8262 using XDA Free mobile app
Thanks shrey rocker for sharing.
Guys try and share if this works for you all..
As far as i know it sure does work well for rooting Samsung Galaxy Core prime
Root Samsung galaxy core Prime G360H.
I am not a developer.
Credits to mahmoud djelailia for his guide.
Step 1 : Do the process shown in this video.
ht tp://m.youtube.com/watch?v=o3CGGXkO7nU
Step 2: Install iroot for pc. Google it. u will find it easily.
step 3: If u want engilsh supersu then download it from playstore and update su binary.
And u have a rooted galaxy core prime in ur hands.
good luck.,.
Sent from my GT-I8262 using XDA Free mobile app
Friends i tried the steps shared by shrey and it finally let me have a rooted Samsung Galaxy Core prime.
This method works 100%.
Checked and verified.
Sent from my GT-I8262 using XDA Free mobile app
Hey buddy i have rooted my galaxy core prime as per the above method. It works fine bro.
I have also tried to root my Core Prime (G360G) with SRS root, it says I'm rooted but there are no SU binaries and thus can't install any root programs. The SRS website even listed me as rooted!
@bmcosier did u follow the exact same process?
If yes. Then most probably iroot has installed the Chinese version of superuser(the one with the lion or horse icon... Whatever). The binaries have already been installed onto by this chinese superuser app. Thats y u r not able to update ur binaries with supersu.(There can be only one binary using app at a time)
This app will be in chinese hopefully. But once u open it. It will check for online update and you will get the English version. Now all u got to do is navigate to
Settings>grant root access to app
and mark the option which is turned off by default.
There after u would be able to have full root access.
Try this and share your views.
Thanks
Just another party by Keen Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting increased queries and replies in this post/PM recently, so I'll try to make this clear (hopefully) for 99% of people. Short version of OP which you must read:
1. Don't install 5.1.1 for now if you ever want to root without tripping Knox warranty.
2. No new ROM can be supported as bug has been fixed.
3. If you don't know how to check a kernel's build date, DO NOT submit FPTAG.
Full story:
New bootloader blocks downgrading, be careful installing 5.1.1 OTA! More details: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
Kernel built after May 15th (including some 5.0.2 and all 5.1.1) have this bug fixed. Be cautious when installing OTA these days and FlashFire might be your best shot of upgrading systems. Use Odin to unroot and receive OTA if you want.
Current version: Beta 6 (HTC One (M9) SUPERSU VERSION! Check updated Usage section!)
Since Beta 5.2: Should be more "stable" on devices with more application installed, but I'm not 100% sure. If it doesn't work, roll back to beta 5.1
I'm getting too many queries about Note 4. Two things to clarify: 1) No device data needed to root Note 4, try KingRoot 4.0. 2) Unless you have KNOX warranty bit tripped already, there is no perm-root for Note 4 yet.
If you have decent bandwidth and experience with ROM files, please see this: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639. Volunteers needed to speed up adding new ROMs.
Big THANK YOU to all helped collecting ROMs. Now we have 91+2 ROM versions supported!
Everyone please do me a favor. If you want a ROM (S6 or S6E) get supported, please confirm it is not yet supported and post a reply in this thread like:
FPTAG fingerprint here
So I can quickly filter FP out of the replys by using search. Thanks.Only submit if you know what a kernel build date is.
Supported devices
Samsung Galaxy S6 with following ROM versions:
G9200ZCU1AOD5
G9200ZHU1AOD3
G9200ZHU1AOD9
G920R4TYU1AOD3
G920IDVU1AOD1
G920FXXU1AOCV
G920PVPU1AOCF
G920TUVU1AOCG
G920VVRU1AOC3
G920FXXU1AOBN
G920FXXU1AODG
G9209KEU1AOCI
G9209KEU1AODA
G9208ZMU1AOD5
G9208ZMU1AOCI
G920FXXU1AOD9
G920AUCU1AOCE
G920FXXU1AODE
G9200ZCU1AOD9
G920W8VLU1AOCG
G920FXXU1AOD4
G920R4TYU1AOCB
***new*** Use Download Data!
G920FXXU1AOCY
G920IDVU1AOC4
G920FXXU1AODI
G9209KEU1AOD5
G920IDVU1AOBQ
G9208ZTU1AOD9
G920FXXU1AOE3
G920IDVU1AOE3
G920FXXU1AOD8
G920FXXU1AOE4
G920AUCU1AOE2
G920T1UVU1AOCH
G9208ZTU1AOCI
G920IDVU1AOC6
G920IDVU1AOD3
G920FXXU1AOCZ
G920AZTUU1AOD1
G9200ZHU1AOE4
G9200ZCU1AOE4
G920KKKU1AODC
G920IDVU1AOE4
G920LKLU1AODC
G920SKSU1AODC
G920IDVU1BOE2
G9208ZTU1AOE4
G920PVPU1AOE2
G920W8VLU1AOE1
G920VVRU1AOE2
SC04GOMU1AOE1
Samsung Galaxy S6 Edge with following ROM versions:
G9250ZCU1AODC
G925VVRU1AOC3
G925FXXU1AOD9
G925PVPU1AOCF
G925FXXU1AOCV
G925AUCU1AOCE
G925TUVU1AOCG
G925W8VLU1AOCG
G925IDVU1AOD1
G925SKSU1AOD5
***new*** Use Download Data!
G925FXXU1AOD4
G925R4TYU1AOD3
G925FXXU1AODG
G925FXXU1AOCZ
G925IDVU1AOD3
G925LKLU1AOD8
G925SKSU1AOD8
G925FXXU1AOE3
G925PVPU1AOE2
G925FXXU1AOD8
G9250ZTU1AODC
G925FXXU1AOE4
G925AUCU1AOE2
G925TUVU1COE6
G925FXXU1AOCY
G9250ZTU1AOE4 (5/11 kernel, seems not fixed yet, please test)
G925R4TYU1AOE2
SCV31KDU1AOCP (Japan version of S6E?)
G9250ZCU1AOCH
G9250ZCU1AOE4
G925IDVU1AOE4
G925IDVU1BOE1
G925LKLU1AODC
G925IDVU1AOE3
G925IDVU1AOE2
G925KKKU1AODC
G925SKSU1AODC
G925W8VLU1AOE1
G925VVRU1AOE2
G925R7WWU1AOE3
HTC One (M9) -- EXPERIMENTAL, UNLOCKED BL REQUIRED
htc/himauhl_htccn_chs_2/htc_himauhl:5.0.2/LRX22G/516731.9:user/release-keys
Verizon 1.33.605 (?)
New ROM and device support are coming~~
If your ROM version is not listed here, please check if any ROM with the same variant is already supported. If the supported one is newer, I suggest go and grab it instead of waiting.
Known Issues:
None
Todo:
Coming next release: (will come after SuperSU version)
TBD
In queue:
Check the workshop thread: http://forum.xda-developers.com/galaxy-s6/general/root-pingpong-root-rom-workshop-thread-t3104639 but DO NOT REPLY UNLESS YOU ARE WORKING ON ROMS. Thank you for keeping that post clean!
Usage
OK, since manual switch is too complex and there are some compatibility issue of Kinguser, I'm making a SuperSU version now.
Note that due to the natural that SuperSU su doesn't ask for permission when SuperSU apk is missing, root will only happen when SuperSU apk has been installed. Read instrucitons below CAREFULLY!
0. Read Q&A section and BACKUP your data.
1. If you already have Kinguser installed please:
a. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission
b. Uninstall Kinguser2. Download pingpongroot_<ver>.apk. Install & open it.
3. It will automatically install SuperSU 2.46 for you. Follow the instructions on screen. You may need to enable unknown source for this step.
a. Once install is finished, click “Open" and run it once to "activate" it. It will prompt an error message (unless you already rooted) and exit automatically, bring you back to PingPong root.4. Click "Download Data" button to update device data if you have Internet connection.
5. Open it and click "Get Root!" button
6. If prompted for app permissions, allow them and continue. If it reboots, just retry.
7. Once finished, please make sure to reboot.
8. You can uninstall PingPong root app once finished.
Credits
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Special thanks to:
Kingroot team (@Kingxteam) for help testing and great root manager
Q&A
Q: How to root 5.1.1 then since PingPong root will never work?
WARNING: User report that fingerprint sensor and incoming call stop working after using the engineering sboot.
A: The classic recovery root method. You shall find details in many other posts. If you are T-Mobile user, lucky for you that there is a leaked engineering bootloader which make root a piece of cake without tripping Knox warranty bit:
http://forum.xda-developers.com/gal...-root-tool-t3103016/post61684664#post61684664
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Q: My ROM is not yet supported?
A: Since I have limited bandwidth to download ROMs, I have to prioritize ROM requests and focusing on new variants/models first. And currently recruiting volunteers to help download/shrink ROMs.
If you see your ROM FP is not listed, but a very similar one (may be just the last digit or character is different) exists, please see if you can flash that version of ROM. I'm sure you can find someone helping you in corresponding forum.
Q: Will Samsung Pay/My Knox work?
A: To be honest I can't tell for sure. Indeed this root does not trip warranty bit. But it still leaves SU files, which is inevitable, on system partitions. And a lot of root features actually make change to system partition, so let's say it can be detected. If Samsung makes the decision that there will be no certain feature for presence of a su file, then there will be no fun. IMHO this is very bad idea since even Apple doesn't disable anything on jailbreak devices. Let's see what will be the outcome. This makes sense to enterprise uses but for consumers at least a choice should be given.
Q: Note4/Z3/Old Samsung/etc?
A: We also wrote the rooting engine in KingRoot 4.0 for generic 32-bit devices. Give it a try. Note that for some devices like Note4, only temp root is achievable.
Q: Why "PingPong" root?
A: Because the vulnerability affects ping socket and we are Chinese
Q: What's the current status of this tool?
A: Beta. We've thoroughly tested it on ROMs for G9200, but not other variants. You are the 1st batch of beta testers!
Q: Is my device supported?
A: You can check the version of your ROM in "About this phone" page. It shall read LRXxxx following by the ROM version.
This tool checks your ROM version as well. If you read "Your device data is still not supported." after clicking "Get Root!", your device data has not been collected yet. Please reply with your ROM version plus keyword "FPTAG" in this thread.
Q: Will this root trip KNOX warranty bit or disable OTA?
A: No, it won't trip KNOX warranty bit and YES, it will disable OTA. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Q: I'd like switching to SuperSU, what shall I do?
A: Kinguser does not have a "swtich" function. Follow these steps to do so manually: (if you are not familiar with adb, see this version: http://forum.xda-developers.com/showpost.php?p=60632150&postcount=269)
1. Download supersu.7z and extract it. You will get the files needed to install Supersu.
2. Using adb to push su and busybox (if not installed) to /data/local/tmp.
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
3. Start a su session and run the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. Your su session should be still running.
5. Uninstall Kinguser app.
6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
7. Install Supersu apk
8. Open Supersu apk to update files.
9. Reboot.
Q: S6 Edge/G Flex 2/M9/other arm64 devices?
A: We will look into them soon
S6 Edge: Done
M9: WIP
G Flex 2/others: pending
Q: I need a video to guide me through
A: Check out this one: https://youtu.be/_Ezh7Oi-jyM
(Note: these are for earlier version)
https://www.youtube.com/watch?v=gNdWX31Sqd8
and this one: http://youtu.be/eAQ4WBg9xj0
To all sent me PM: I'm sorry that the reply could be delayed. Currently we are busy working on supporting of new ROMs and fixing bugs. To all those providing useful info/suggestion, thanks a ton!
nice work
great！
Holy crap man!!! GREAT WORK!!!!
great work! knox 0x0
You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated
Any chance of the ATT variant being rooted?
Japultra said:
You guys are awesome! Patiently waiting for G920FXXU1AODG to be incorporated
Click to expand...
Click to collapse
Downloading the ROM now, mate Will be included in the next Beta which will happen soon enough
Kokorone said:
Any chance of the ATT variant being rooted?
Click to expand...
Click to collapse
Yes, they are waiting for an ATT rom to appear first though.
Wow...can't believe! [emoji33]
Nice work! [emoji106]
Now switched from beta1 to beta5 and SuperSU...worked like a charm!
Titanium Backup is now running how it should.
Yeah...root access until next Update to 5.1.1 [emoji7]
and Knox says 0x0?
Hoping for g920fxxu1a0cw to be included great job mate!
is it possible with G920FXXU1AOD9 french region
G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)
Joern85 said:
G920FXXU1AODG here, will it work for that firmware? (Vodafone Germany)
Click to expand...
Click to collapse
It's coming in the next update!
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
tutti9372 said:
and Knox says 0x0?
Click to expand...
Click to collapse
You should really read the OP
Q: Will this root trip KNOX warranty bit?
A: No. It doesn't require odin to flash in a custom recovery, so the warranty bit will remain intact.
Click to expand...
Click to collapse
I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.
Fantastic work, Idler! Will you publish the source code for this?
cpfeifer said:
I'm wondering if the vulnerability used here exists on the S6 Edge. Because I don't see anyone posting a SM-925xx Rom and to my understanding SM-920 is normal S6, where as SM-925 is the edge version.
Click to expand...
Click to collapse
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
That's good to hear. My current kernel is from April 10th and I've got the latest ota. Hopefully I can get root before a forced ota is pushed out with a kernel update.
That is truly great work....
and my FAVOURITE
After switching to SuperSU, aps like TitanumBackup, RootExplorer and many probably more works great.
I just edit my "others.xml" and just the begin of having true FUN with my phone
BIG THANKS for ROOT
idler1984 said:
Oh, I shall update the Q&A section. S6E (and may be other arm64 devices) will be investigated. And vulnerability should still be there for any kernel before 5/3.
Click to expand...
Click to collapse
Thanks for your great tool. For us who have tripped knox will it untrip or not.:
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name ROM Droid Mini/Maxx/Ultra L!te FW 4-21 ML
Tagline Faster Lighter Economical
SYSTEM Firmware SU4-21 Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- tzdata 2015e
- icudt51l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps VZW & MOTO
- replaced by sound WirelessChargingStarted
- old gapps for long work phone
- uppdate apps Chrome, LatinIME, Skip, TouchLess, MotCamera, MotGallery, Migrate
- tetering work
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/Droid
for Loked Device
Install for QDLoad9008
Root, Xposed, BusyBox is PreInstalled
- Root SuperSU v2.46
- XPosed 2.6.1
- BusyBox v30
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_4_4_4_VZW_SU6-7_BL_V30.BA_Stock.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part1.bat. Parts XX of system.
*** You can also run a file if you are sure that your phone can work 4-5 hours with the screen RUN_Rus_VZW_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_Part**.bat. Parts XX of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
installed application Xposed 2.6.1
Xposed launched clicked install, reboot your phone
I see that the application is launched is set app_process 58 (pre-installed in the system) and XPosedBridge.jar 54 version (made with the application)
then uploaded GravityBox [KK], a check mark, the next reboot, and everything works
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Droid/4.4.4 SU4-21
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Droid Mini/Maxx/Ultra L!te FW 4-21 ML, ROM for the Motorola Droid Ultra
Contributors
CrashXXL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Android 4.4.4 SU6-7 (Flash on RSDLite)
Version Information
Status: Stable
Current Stable Version: 1.02
Stable Release Date: 2015-09-01
Current Beta Version: 0.01
Beta Release Date: 2015-08-15
Created 2015-10-08
Last Updated 2015-10-08
Reserved
Reserved
Update Available
Log
- Launcher with a mesh 4 * 5 with no search string
- Smart Action Moto return ... The assistant working all options
for blocked Patch_SmartAction_Launcher.4x5.NoBar.rar https://yadi.sk/d/kxbxpTnziSg35/Droid
for unlocked MotLauncher.4x5.NoBar.zip https://yadi.sk/d/jp8ykQqFindY8/Droid and SmartActions.zip https://yadi.sk/d/jp8ykQqFindY8/SmartActions
Reserved
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Can I do Write Protection with this ROM?
OscarBrito16 said:
Can I do Write Protection with this ROM?
Click to expand...
Click to collapse
Write protection is still enabled so the root is limited as far as what you can do with it.
classic757 said:
Write protection is still enabled so the root is limited as far as what you can do with it.
Click to expand...
Click to collapse
I mean to install a custom recovery or flash a custom rom!
No, you would not be able to install a custom recovery with method. Unless you have su4-21 or lower your bootloader is locked and at this time there isn't a method to unlock it.
Also you can't downgrade to an older su version, once you have su5-24 or above the qfuse is blown.
As said above you can achieve root, but since the system is still write protected root access is limited. The other option is to perm root your device, and try safestrap, I hope I'm allowed to post that in the thread, sorry if I'm not.
Sent from my XT1080 using XDA mobile app
OscarBrito16 said:
I mean to install a custom recovery or flash a custom rom!
Click to expand...
Click to collapse
Without write protection disabled you cannot install custom recovery or flash custom roms.
Also, if you are on 4.4.4 there is no full root available at this time.
any chance to implement/add Czech language on this ROM?
dcoaster said:
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Click to expand...
Click to collapse
I have the same concerns. Are we supposed to downgrade to the SU4-21???Will this grant us the ability to use Sunshine and unlock our bootloaders?? I thought it wasn't possible to downgrade??? Please I'm lost here I want to do this but I'm am unsure of the outcome?
You can add any language, but it takes a lot of time.
can you tell me how to do it?
- unpack apk
- transtale xml value-en to value-cz
- pack
- install on update from twrp
- check work
@CrashXXL
how can I add the gesture of jedi to my phone? what files do I need to take from your rom?
I do not want to take the whole rom, would be great if i could only take a few files and push the diff to my phone
Can i use this to flash it right over my rooted SU6-7 (rooted with your method months ago, Crash) or do i need to re-flash original stock (without root)?
will my phone be still rooted if i factory reset it..?
I guess this contains only Russian and/or English language, am i right?
Einheit-101 said:
I guess this contains only Russian and/or English language, am i right?
Click to expand...
Click to collapse
no, localization saved and added 2 more Russian and Ukrainian
Yeah, so no German
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name ROM Moto X L!te FW KXA21.12-L1.26.EU.ML
Tagline Faster Lighter Economical
SYSTEM Firmware KXA21.12-L1.26.EU.ML Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- tzdata 2015f
- icudt51l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps MotoServices, Google Drive & Docs, Permissions and etc
- replaced by sound WirelessChargingStarted
- old gapps for long work phone
- uppdate apps Chrome, LatinIME, Skip, TouchLess, MotCamera, MotGallery, Migrate
- tetering work
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/MotoX/4.4.4
for Loked Device
Install for QDLoad9008
Root, Xposed, BusyBox is PreInstalled
- Root SuperSU v2.46
- XPosed 2.6.1
- BusyBox v30
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_4_4_4_KXA21_12-L1_26_BL_V30.B7.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash *******_4.4.4-KXA21.12-L1.26_CFC_1FF.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_***_Part**.bat. Parts XX of system.
*** You can also run a file if you are sure that your phone can work 4-5 hours with the screen RUN_Rus_***_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_***_Part**.bat. Parts XX of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
installed application Xposed 2.6.1
Xposed launched clicked install, reboot your phone
I see that the application is launched is set app_process 58 (pre-installed in the system) and XPosedBridge.jar 54 version (made with the application)
then uploaded GravityBox [KK], a check mark, the next reboot, and everything works
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Moto X/4.4.4
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Moto X L!te FW KXA21.12-L1.26.EU.ML, ROM for the Moto X
Contributors
CrashXXL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Android 4.4.4 KXA21.12-L1.26
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-10-14
Current Beta Version: 0.01
Beta Release Date: 2015-10-04
Created 2015-10-10
Last Updated 2015-10-15
Hi, im on 4.4.3.... I have root and bootloader unlocked. What i need to install?
Just download and install by twrp? Or i need do something before?
Hi, I'm on Moto X ATT 5.1 with locked bootloader. Can I downgrade to this rom?
which file should i download KXA21.12-L1.26.EU.ML-Post-Release.zip or KXA21.12-L1.26.EU.ML.zip ???