The short of it is during my attempt to use the CASUAL one-click, it failed to do... something, and said my phone should be rebooting. It isn't.
Basically, I am stuck with my phone saying "Downloading... Do not turn off target !!" I have no idea what to do, and am scared to death I have done something unfixable.
For the record, I did find people who reported this problem in the development thread... but if they were answered, it must have been in jargon that I am not familiar with. Half the time I cannot tell what people are saying in that thread, I am just not well informed enough with what's going on to follow everything. So please don't get too upset with me for posting.... I need a fairly plain english explanation of what I can do...
I wasn't sure if the log would be helpful. Here's a chunk toward the end of it. If having all of it is better, I can do that.
Driver Problems suck. Lemme make it easy.
1. Check that your device is download mode and connected up.
2. Select the one that says ---Gadget Serial--- in the main window
3. Click ---install driver---.
4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted
to use Heimdall instead of Odin for download mode. It only affects
ONE usb port.
Open-Source Heimdall Drivers...21504kb Open-Source Heimdall Drivers config...8kb Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
ERROR: Protocol initialisation failed!Your device should be rebooting into Android now.
Mandolin
==================
EDIT: OK, so I got impatient and took a leap of faith that I was reading the forum correctly.... I popped out the battery, disconnected the cable, replaced the battery, and plugged it back into the pc and hoped that it booted, then appeared to finish the process. However, when trying to run GL to SD, an app that requires root access, it said I don't actually have it.
What should I do? How do I know if CASUAL changed anything? Do I need to do anything before trying again?
Having the same issue, can anyone help?
Mandolin Bee said:
The short of it is during my attempt to use the CASUAL one-click, it failed to do... something, and said my phone should be rebooting. It isn't.
Basically, I am stuck with my phone saying "Downloading... Do not turn off target !!" I have no idea what to do, and am scared to death I have done something unfixable.
For the record, I did find people who reported this problem in the development thread... but if they were answered, it must have been in jargon that I am not familiar with. Half the time I cannot tell what people are saying in that thread, I am just not well informed enough with what's going on to follow everything. So please don't get too upset with me for posting.... I need a fairly plain english explanation of what I can do...
I wasn't sure if the log would be helpful. Here's a chunk toward the end of it. If having all of it is better, I can do that.
Driver Problems suck. Lemme make it easy.
1. Check that your device is download mode and connected up.
2. Select the one that says ---Gadget Serial--- in the main window
3. Click ---install driver---.
4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted
to use Heimdall instead of Odin for download mode. It only affects
ONE usb port.
Open-Source Heimdall Drivers...21504kb Open-Source Heimdall Drivers config...8kb Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
ERROR: Protocol initialisation failed!Your device should be rebooting into Android now.
Mandolin
==================
EDIT: OK, so I got impatient and took a leap of faith that I was reading the forum correctly.... I popped out the battery, disconnected the cable, replaced the battery, and plugged it back into the pc and hoped that it booted, then appeared to finish the process. However, when trying to run GL to SD, an app that requires root access, it said I don't actually have it.
What should I do? How do I know if CASUAL changed anything? Do I need to do anything before trying again?
Click to expand...
Click to collapse
Weird? after about the 10th try today and on two seperate computers, it worked
You can download Rootchecker from the play store to verify root. Also generally if you can't open a root only app, you are not rooted. Sometimes you have to try again. I would redownload the file and start over. Sometimes you can get a corrupt file. Also it's good practice to reboot your PC as well.
Sent from my SCH-I605 using Tapatalk 2
MPeterson21 said:
You can download Rootchecker from the play store to verify root. Also generally if you can't open a root only app, you are not rooted. Sometimes you have to try again. I would redownload the file and start over. Sometimes you can get a corrupt file. Also it's good practice to reboot your PC as well.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for being ignorant on this. I get that the root failed, but... I really don't want to end up with a broken or bricked phone. Is just re - running it "safe"?
Or do I need to somehow make sure the previous attempt didn't leave anything behind first? And should I be concerned at all about why it may have failed the first time?
if ya just want root then odin root66.
droidstyle said:
if ya just want root then odin root66.
Click to expand...
Click to collapse
Not to be terribly impertinent, but you may as well have just suggested that I smackerdip the hallywagon.
If it hasn't already been made pretty evident by my previous posts, I can't seem to wrap my head around mobile jargon in this respect. As far as I have been able to tell, there's no way to "only" want root to start with, you MUST both root and something else or I will get some kind of evil triangle (and if I do, is that bricked?)
All I really want to do is be able to move apps onto my SD card, and everything I can find says I must root my phone for that.
I'm sorry if it's irritating for some that I really need people to reply without assuming some kind of prior knowledge. I'm pretty tech savvy in general, but this whole mobile thing is new to me, and nothing I ever tried to do on my PC was going to potentially cause me $700 of irreversible damage. So if anyone could just take the time to treat me like the mobile noob I am and not just throw words at me like I am supposed to know what they mean or what to do with them, that'd be appreciated.
Thanks.
Mandolin Bee said:
Not to be terribly impertinent, but you may as well have just suggested that I smackerdip the hallywagon.
If it hasn't already been made pretty evident by my previous posts, I can't seem to wrap my head around mobile jargon in this respect.
Thanks.
Click to expand...
Click to collapse
I'm pretty new to this too, at least new to this phone. I rooted my Thunderbolt but that was pretty easy compared to the Note it seems. I spent a considerable amount of time last night researching this stuff and I have gone from 'extremely limited' to 'somewhat capable.' Takes a bit of time.
What droidstyle is suggesting is that you use the Odin app (lots of links on this forum) to load ROOT66 factory image, also known as the "alternate restore file", to your phone. root66 does not attempt to modify the bootloader (harder to do with note2 due to verizon).
Read this for some more information: http://forum.xda-developers.com/showthread.php?t=2196891
No one will ever tell you that rooting is 100% safe. Of course you are taking risk but if you follow the walk through you should be fine. When I first rooted/unlocked I had issues completing it, and I had to re download and start over. It should cause no harm as long as you follow the steps.
Sent from my SCH-I605 using Tapatalk 2
Dude. I have the EXACT same thing right now. Still stuck on this screen and I have no clue what to do. Anyone PLEASE help me.
EDIT: here's the Casual log:
{
"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"
}
Lepryy said:
Dude. I have the EXACT same thing right now. Still stuck on this screen and I have no clue what to do. Anyone PLEASE help me.
Click to expand...
Click to collapse
It's scary, right? Here's what you do:
LEAVE THE PROGRAM ON!
1) Disconnect the usb cable from your phone
2) Open the back cover and pull out the battery
3) Put the battery back in
4) put the cover back on your phone and reconnect the usb cable
5) hold your power button until it starts booting
OK, now the program will take over again and look like it's installing things. I don't know what it's actually doing, but at some point, it will tell you that "you should be rooted now".
Then you'll end up on some screen that also looks scary with some options for rebooting. I picked the one that was closest to "reboot normally", and my phone booted up just fine.
However, my phone was NOT actually rooted..... but at least it isn't a brick.
Now I am trying to figure out if it's safe to try this whole process again, but I can't get a straight, non-jargon answer out of these people.
MPeterson21 said:
No one will ever tell you that rooting is 100% safe. Of course you are taking risk but if you follow the walk through you should be fine. When I first rooted/unlocked I had issues completing it, and I had to re download and start over. It should cause no harm as long as you follow the steps.
Click to expand...
Click to collapse
In fairness, I'm not looking for anyone to tell me it's 100% safe. I'm looking for information that to most of the people around here is probably considered "common knowledge". I'm admitting I lack any level of "common knowledge" when it comes to mobile technology.
Like.. it may be "common knowledge" that if the CASUAL one-click fails, you have to go in and delete files x, y, and z before retrying or you might brick your phone. Or perhaps you need to go and make sure directories a, b, or c didn't get renamed/deleted/copied/turned into cake.
There's any number of things that I should perhaps need to "be careful" of now that I have attempted to root my phone, but failed.... or perhaps there is NOTHING I need to "be careful" or watch out for. That's what I want to know.
You know... like if I show back up and say "I followed the directions and now my phone doesn't work at all!" and someone comes along and says "Well, did you do it more than once without doing a factory reset between attempts? You shouldn't have done that."
I'd rather avoid such a dialog, tyvm. Hence, I am asking if it is "safe" to run the program again, meaning am I running the -same- risk as I was for attempt number 1, or is a second attempt likely to screw me over harder because I didn't do something ELSE first?
Mandolin Bee said:
It's scary, right? Here's what you do:
LEAVE THE PROGRAM ON!
1) Disconnect the usb cable from your phone
2) Open the back cover and pull out the battery
3) Put the battery back in
4) put the cover back on your phone and reconnect the usb cable
5) hold your power button until it starts booting
OK, now the program will take over again and look like it's installing things. I don't know what it's actually doing, but at some point, it will tell you that "you should be rooted now".
Then you'll end up on some screen that also looks scary with some options for rebooting. I picked the one that was closest to "reboot normally", and my phone booted up just fine.
However, my phone was NOT actually rooted..... but at least it isn't a brick.
Now I am trying to figure out if it's safe to try this whole process again, but I can't get a straight, non-jargon answer out of these people.
Click to expand...
Click to collapse
Thanks dude. In another thread I asked the same question. You and I should be at the same point right now. I ran the process again and, it worked perfectly. I would go ahead.
Mandolin Bee said:
It's scary, right? Here's what you do:
LEAVE THE PROGRAM ON!
1) Disconnect the usb cable from your phone
2) Open the back cover and pull out the battery
3) Put the battery back in
4) put the cover back on your phone and reconnect the usb cable
5) hold your power button until it starts booting
OK, now the program will take over again and look like it's installing things. I don't know what it's actually doing, but at some point, it will tell you that "you should be rooted now".
Then you'll end up on some screen that also looks scary with some options for rebooting. I picked the one that was closest to "reboot normally", and my phone booted up just fine.
However, my phone was NOT actually rooted..... but at least it isn't a brick.
Now I am trying to figure out if it's safe to try this whole process again, but I can't get a straight, non-jargon answer out of these people.
Click to expand...
Click to collapse
big high-5 to you my new friend. this saved me. thanks! :highfive:
Thanks, had the same issue, saved my phone :laugh:
Keep getting this error trying to do this root - doesn't seem successful.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
ERROR: Failed to send file part packet!
ERROR: BOOT upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Blargh, unfortunately pulling battery soft bricked me. I got stuck at same spot the OP did. Kept app running, pulled USB, then battery. Put battery back, then plugged in and powered on. CASUAL ran thru the rest of it's script, obviously failing at certain points as OP mentioned, but then mine got to:
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading recovery
0%12%25%37%50%62%75%87%100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
It again hung in Download mode for several minutes, so I tried the same trick as above, unplugged, removed battery etc but mine is doing a fast loop on the Samsung Galaxy Note 2 screen. Will pop up for about 1 second, reboots repeat. This is actually the original reason why started this journey. URL of my story: http://forum.xda-developers.com/showthread.php?t=2264319 as you can see OP I too struggle with getting the answers I need LOL.
I'm going to restore to stock and will just root with the APK and give up hope for now of custom recovery and ROMs. One thing I could ask, though i seems you did a good job of following instructions was if you did enable USB Debugging.
Try a restart of PC, etc. I believe you said in a previous post that you were just looking for root. If that is true and you don't want a custom recovery or ability to install ROMS, and just want root access to uninstall and move app's. Reply back to thread, there is an application you can launch from the phone itself that will give you root. Just don't make mistake of trying to install the recovery or roms as you will get a nasty VZW has bricked your phone for unauthorzied software. Easily fixed but highly inconvenient as it requires restoring to Stock aka hard reset
dannymac77 said:
I believe you said in a previous post that you were just looking for root. If that is true and you don't want a custom recovery or ability to install ROMS, and just want root access to uninstall and move app's. Reply back to thread, there is an application you can launch from the phone itself that will give you root.
Click to expand...
Click to collapse
What application are you talking about here? Can you give some detail? I really only need root as well, just to get all the VZW bs out of my face and run droid wall.
I attempted CASUAL and it hung at the exact same spot as OP, "protocol initilisation failed". I unplugged phone, pulled/replaced battery, powered on and the phone started normally and has worked perfectly since (week ago).
I got a few helpful hints but no one knew exactly the problem, I think one of the few people who could say exactly what has caused it to crash there is the original developer, and they don't seem to watch these details. One person did suggest I try a different USB cable, and I've noticed bad cables have caused problems for many people on here. Haven't tried yet. I have rooted a few Droid Xs before, but I am tired of people on here with the "oh its easy, perfect, run CASUAL it's great, I've run it 1,583,000 times and never had 1 problem". I don't have time anymore to waste hours trying to recover my phone.
Log info.....using VRAMC3
[INFO]We are running Windows 8
Creating Temp Folder in:C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:465 build:3662
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Chris\Downloads\Samsung%20Note2%20tools\BackAtchaVerizon-CASUAL-Revision465b.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]Picking Jar File:/C:/Users/Chris/Downloads/Samsung%20Note2%20tools/BackAtchaVerizon-CASUAL-Revision465b.jar
[DEBUG]Found Windows Computer
[DEBUG]Found: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]sleeping for Windows ADB start
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb_usb.ini
[DEBUG]File verified.
[DEBUG]###executing: C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb.exe###
[VERBOSE]List of devices attached
[DEBUG]device
[DEBUG]Device List:
42f77da2077bbfe1 device
[DEBUG]Control Change requested but Statics.MasterLock is set.
[DEBUG]OMFGWOOT GUI running!
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
[DEBUG]Searching for scripts
[DEBUG]Updating Scripts for UI
[VERBOSE]From Resource: true
[INFO]--WindowsLinux Galaxy Note 2 Jailbreak--
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
[DEBUG]Created zipResource at /SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.zip
[DEBUG]Exiting comboBoxUpdate()
[DEBUG]attempted to lock controls but controls are not availble yet
[DEBUG]Extracting archive....
[DEBUG]Target Script Is resource
[VERBOSE]Unzipping Superuser.apk
[VERBOSE]Unzipping boot.img
[VERBOSE]Unzipping busybox
[VERBOSE]Unzipping dependentinstaller.sh
[VERBOSE]Unzipping exploit
[VERBOSE]Unzipping exynos-abuse
[VERBOSE]Unzipping recoverThis
[VERBOSE]Unzipping rootGN.sh
[VERBOSE]Unzipping su
[VERBOSE]Unzipping swagBoot
[VERBOSE]Unzipping viewmem
[VERBOSE]Unzip Complete
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]State Connected commanded
[DEBUG]Controls Enabled status: true
[ERROR]
[DEBUG]StartButtonActionPerformed() Script Activated
[DEBUG]Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
[DEBUG]Controls Enabled status: false
[DEBUG]disk location for script resources
[DEBUG]Loading internal resource: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Lines in Script 66
[DEBUG]Executing Scripted [email protected]
[DEBUG]CASUAL has initiated a multithreaded execution environment
[DEBUG]***WEB VERSION***
IDString:VERIZON GNOTE
SVNRevision:464
ScriptRevision:2
supportURL:http://forum.xda-developers.com/showthread.php?t=2118348updateMessageUPDATE: Im not supporting old versions
[ERROR]ERROR. CASUAL is out-of-date. This version of CASUAL cannot procede further. See http://forum.xda-developers.com/showthread.php?t=2118348 for more information.
ccllabel said:
Log info.....using VRAMC3
[INFO]We are running Windows 8
Creating Temp Folder in:C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:465 build:3662
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Chris\Downloads\Samsung%20Note2%20tools\BackAtchaVerizon-CASUAL-Revision465b.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]Picking Jar File:/C:/Users/Chris/Downloads/Samsung%20Note2%20tools/BackAtchaVerizon-CASUAL-Revision465b.jar
[DEBUG]Found Windows Computer
[DEBUG]Found: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]sleeping for Windows ADB start
[DEBUG]Attempting to write C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb_usb.ini
[DEBUG]File verified.
[DEBUG]###executing: C:\Users\Chris\AppData\Local\Temp\ChrisTEMPCASUALFBCCE1FD\adb.exe###
[VERBOSE]List of devices attached
[DEBUG]device
[DEBUG]Device List:
42f77da2077bbfe1device
[DEBUG]Control Change requested but Statics.MasterLock is set.
[DEBUG]OMFGWOOT GUI running!
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
[DEBUG]Searching for scripts
[DEBUG]Updating Scripts for UI
[VERBOSE]From Resource: true
[INFO]--WindowsLinux Galaxy Note 2 Jailbreak--
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
[DEBUG]Created zipResource at /SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.zip
[DEBUG]Exiting comboBoxUpdate()
[DEBUG]attempted to lock controls but controls are not availble yet
[DEBUG]Extracting archive....
[DEBUG]Target Script Is resource
[VERBOSE]Unzipping Superuser.apk
[VERBOSE]Unzipping boot.img
[VERBOSE]Unzipping busybox
[VERBOSE]Unzipping dependentinstaller.sh
[VERBOSE]Unzipping exploit
[VERBOSE]Unzipping exynos-abuse
[VERBOSE]Unzipping recoverThis
[VERBOSE]Unzipping rootGN.sh
[VERBOSE]Unzipping su
[VERBOSE]Unzipping swagBoot
[VERBOSE]Unzipping viewmem
[VERBOSE]Unzip Complete
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]State Connected commanded
[DEBUG]Controls Enabled status: true
[ERROR]
[DEBUG]StartButtonActionPerformed() Script Activated
[DEBUG]Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
[DEBUG]Controls Enabled status: false
[DEBUG]disk location for script resources
[DEBUG]Loading internal resource: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Lines in Script 66
[DEBUG]Executing Scripted [email protected]
[DEBUG]CASUAL has initiated a multithreaded execution environment
[DEBUG]***WEB VERSION***
IDString:VERIZON GNOTE
SVNRevision:464
ScriptRevision:2
supportURL:http://forum.xda-developers.com/showthread.php?t=2118348updateMessageUPDATE: Im not supporting old versions
[ERROR]ERROR. CASUAL is out-of-date. This version of CASUAL cannot procede further. See http://forum.xda-developers.com/showthread.php?t=2118348 for more information.
Click to expand...
Click to collapse
Im pretty sure casual is not working on the ota 4.1.2, you probably have to wait till Adam updates casual bevause of recent update, also wont work on windows 8
Sent from my SCH-I605 using XDA Premium HD app
Adam himself said it does work...
Sent from my SCH-I605 using xda premium
I have tried three different computers and nine different USB ports......three different USB cables as well including the OE one. I am rooted but still have the OE recovery. I have uninstalled and re-installed the drives countless times. To my knowledge I am using the latest build of BackAtchaVerizon-CASUAL-Revision465b that was posted late last night. I have also posted many log files.
Related
NOTICE: This will not work on the latest firmware updates. Flashing will cause bootlooping and you will have to reload software.
If CASUAL brought you here, your version is outdated.
Well, this has been quite the saga thus far...
Us: Suck It Verizon (exploit)
them: Suck it XDA-Developers (OTA patch)
Us: Back Atcha Verizon (exploit)
them: Stop it XDA (OTA Patch)
Us: No You! (exploit)
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. CTRL+L>Pastebin> come back here and press ctrl+V. We need a log or it didn't happen. 70% of the time when someone posts a general description, we need more information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Windows 8 is supported but you must install drivers for Download Mode first. See this post
Windows XP IS NOT supported! If you can make Windows XP work, share the knowledge. XP is 12 years old now, Microsoft and I both discontinued support for Windows XP.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk gksu dpkg
NOTE: Linux 32/64 bit Heimdall may require an update. I will be taking care of it this weekend. If it works, please let me know so I can remove this message.
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUAL(R515b) No You Verizon! CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"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"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
8May13: After last the issues with this release, I spent 5.5 hours updating to VRAMC3 and .1 testing this package. . It works well, I assure you.. I assume the previous release had a bad MD5. I apologize for any inconvience.
9May13: Initial Release
10May13: Fixed windows driver issue. Added clearer instruction messages to wait (fixed "hanging"). Added better error handling. CASUAL R492 -- killed old versions
F.A.Q.
//TODO
General
//TODO
Windows :
//TODO
Linux :
//TODO
Mac OS X :
Heimdall keeps failing with "ERROR: Claiming interface failed!"
You need to disable the default USB drivers with the following commands:
Code:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;
I just got my Note 2, I've tried your tool several times and I keep getting this when my phone reboots into download mode:
<took out the garbage>
USB connection seems a bit shaky.
You have a different cable to try?
Dont post logs here. They're ugly. Use pastebin. Please remove all of that. I specifically said not to post that.
Try it again with a better cable. I see it is disconnecting and reconnecting repeatedly. That's a bad cable if I've ever seen one... Odin mode does not have error correction like ADB. Its really picky about having good cables and a good USB port.
When this works, please post that it worked.
jrloper said:
USB connection seems a bit shaky.
You have a different cable to try?
Click to expand...
Click to collapse
not right now, but I tried other USB plugs and its not connecting on those.
---------- Post added 10th May 2013 at 12:00 AM ---------- Previous post was 9th May 2013 at 11:57 PM ----------
AdamOutler said:
Dont post logs here. They're ugly. Use pastebin. Please remove all of that. Holy cow man! I specifically said not to post that.
Try it again with a better cable. I see it is disconnecting and reconnecting repeatedly. Thats a bad cable if I've ever seen one...
When this works, please post that it worked.
Click to expand...
Click to collapse
Sorry, I'm a novice with having to post that stuff. I don't have to post logs much.
I don't understand how the cord could be bad since its the one that came out of the box yesterday. But I don't have access to one right this second
ShotgunSam said:
not right now, but I tried other USB plugs and its not connecting on those.
Click to expand...
Click to collapse
We've seen this a lot. Its your cable. I have several cheap cables that don't work with Heimdall or Odin. Also some usb ports dont work either.
Good job Adam once again. Wonder when they'll eventually just give up and stop pestering Samsung.
Sent from my SCH-I605 using Tapatalk 2
No you!
I do believe that this is my very 1st post on this site. Adam thank you for all of your hard work.
On EDIT: Went into the temp file and individually clicked on each of the .exe files. Rebooted phone and restarted CASUAL. Everything worked fine after that.
Thanks again! Donation sent yesterday.
Tried 2
different cables on 2 different ports. No luck so far. http://pastebin.com/741wqT3T
Any ideas?
This is a brand new Note 2 on the latest OTA which installed at the store when I got it.
Thanks!
Thank You Adam!!! You sir, are a life saver!
Original thread you posted 2 days ago worked for my Note 2 I purchased used on Sunday. Same cable I have connected to my computer for years now, process was butter smooth. Phone updated to 4.1.2 before I had a chance to get home and root.
Only had to battery pull after it hung initially. Thanks! Will send donation as soon as I get PP funds.
Worked on my Note 2 unlocked it to where i can use my Tmobile sim, but it keeps giving me a warning "sorry this sim card is not supported" but i can make calls, i cant add APN settings though.
Jgun33 said:
On EDIT: Went into the temp file and individually clicked on each of the .exe files. Rebooted phone and restarted CASUAL. Everything worked fine after that.
Thanks again! Donation sent yesterday.
Tried 2
different cables on 2 different ports. No luck so far. http://pastebin.com/741wqT3T
Any ideas?
This is a brand new Note 2 on the latest OTA which installed at the store when I got it.
Thanks!
Click to expand...
Click to collapse
Looks like it failed while attempting to install CADI. Do you have administrative permissions?
We may need to make a change to the execution of CADI.
I got an error as well.
http://pastebin.com/ddD8b749
Taking a deep breath...here we go
---------- Post added at 06:05 PM ---------- Previous post was at 05:32 PM ----------
Worked like a charm. Booted right into TWRP. Lost root - but TWRP fixed it
Im getting the same error with numerous usb cables and using different usb ports.
http://pastebin.com/sWSn891k
mmoorman12 said:
I got an error as well.
http://pastebin.com/ddD8b749
Click to expand...
Click to collapse
Looks like your virus scanner trashed CASUAL before you even ran it. Disable your virus scanner.
Osmannm123123123 said:
Im getting the same error with numerous usb cables and using different usb ports.
http://pastebin.com/sWSn891k
Click to expand...
Click to collapse
No you didn't. You're the first to get this error. You have UAC disabled or you have no administrative permissions. Notice the loop while attempting to install drivers. also, it returned "null" as in it returned less a blank line.
UPDATE: I have updated this post with a file named "board diag v2.99.zip" This should now support more phones!!!
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command prompt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
{
"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"
}
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
NOTES: If you get an error about a dll missing you need to download and install the following http://www.microsoft.com/en-us/download/details.aspx?id=5555
Also make sure that you use "B2 (MSM8974AC)" as the AP Chipset for the LG G3.
thanks a lot brother.... just one Q...where can I get the TOT file?
paragxx said:
thanks a lot brother.... just one Q...where can I get the TOT file?
Click to expand...
Click to collapse
I assume that you are using sprint ls990 if so here is are the latest tot files. ZV8 and ZV6 can be found here http://downloads.codefi.re/autoprime/LG/LG_G3/LS990 thank autoprime. The files are zipped just extract the zip and then do the process above.
ZV4 can be found here direct link. http://downloads.codefi.re/wolfgart/LG_G3/LS990/ZV4/LS990ZV4_04.51101.zip
Any chance this works on ATT D850?
For myself and the benefit of others, I'm just clarifying something. I've always understood there to be the "hard brick" and the "soft brick". The soft brick is what you describe above where your phone lights up but doesn't boot. A hard brick is where nothing lights up, and your phone doesn't respond at all.
If someone were to describe what you describe above, I'd say that's not a hard brick. There's hope for a soft brick but not a hard brick. Am I wrong, or have the terms morphed a bit in the past several years?
mjjcb said:
For myself and the benefit of others, I'm just clarifying something. I've always understood there to be the "hard brick" and the "soft brick". The soft brick is what you describe above where your phone lights up but doesn't boot. A hard brick is where nothing lights up, and your phone doesn't respond at all.
If someone were to describe what you describe above, I'd say that's not a hard brick. There's hope for a soft brick but not a hard brick. Am I wrong, or have the terms morphed a bit in the past several years?
Click to expand...
Click to collapse
I was always told that a soft brick could be repaired with either recovery or fastboot and that a hard brick was anything that you needed more tools to fix. But I guess that everyone's definition is different. Also This method works on any kind of brick as long as there isn't a hardware issue. No screen on, no power on etc.
BlackSportD said:
Any chance this works on ATT D850?
Click to expand...
Click to collapse
Sorry that I missed your post.... but yes this should work on all variations of the LG G3 as long as it has the points on the motherboard posted in the picture. I do know that the international dual sim version has different pins and I don't know those pins but ATT, Sprint, Verizon, should all work.
l33tlinuxh4x0r said:
Sorry that I missed your post.... but yes this should work on all variations of the LG G3 as long as it has the points on the motherboard posted in the picture. I do know that the international dual sim version has different pins and I don't know those pins but ATT, Sprint, Verizon, should all work.
Click to expand...
Click to collapse
hey, mine is F460K (snapdragon 805) APQ8084 and not msm8974. My device shows as Qualcomm HS-USB QDLoader 9008 (COM6) . I assume i dont need to sort wire as its sole purpose is to show the device as Qualcomm in Device manager.
I think i need to create a file under model like B2 (MSM8974AC) with 2nd_loader.hex etc. Can you help me on this or is it unnecessary ?
currently i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
Pannam said:
hey, mine is F460K (snapdragon 805) APQ8084 and not msm8974. My device shows as Qualcomm HS-USB QDLoader 9008 (COM6) . I assume i dont need to sort wire as its sole purpose is to show the device as Qualcomm in Device manager.
I think i need to create a file under model like B2 (MSM8974AC) with 2nd_loader.hex etc. Can you help me on this or is it unnecessary ?
currently i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
Click to expand...
Click to collapse
You are right about not needing to short the wire and also about needing the correct 2nd_loader.hex etc. However I don't know how to make those. Attached are some more models that I found online. Hope that this helps.
l33tlinuxh4x0r said:
You are right about not needing to short the wire and also about needing the correct 2nd_loader.hex etc. However I don't know how to make those. Attached are some more models that I found online. Hope that this helps.
Click to expand...
Click to collapse
Thanx man, but they dont show my chipset.
Pannam said:
Thanx man, but they dont show my chipset.
Click to expand...
Click to collapse
What phone do you have? This tutorial is for the LG G3 from what I just googled the chipset that you are looking for is the Samsung Galaxy Note 4?
l33tlinuxh4x0r said:
What phone do you have? This tutorial is for the LG G3 from what I just googled the chipset that you are looking for is the Samsung Galaxy Note 4?
Click to expand...
Click to collapse
this is my phone it is lg g3 but upgraded version. http://www.gsmarena.com/lg_g3_lte_a-6520.php
Pannam said:
this is my phone it is lg g3 but upgraded version. http://www.gsmarena.com/lg_g3_lte_a-6520.php
Click to expand...
Click to collapse
I don't know then. I know that this method works on the carrier versions of the lg g3 but people have had issues with other versions.
l33tlinuxh4x0r said:
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command promt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
Click to expand...
Click to collapse
hi
i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
model ls740 volt
G2MLTE (MSM8926)
help
nemran said:
hi
i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
model ls740 volt
G2MLTE (MSM8926)
help
Click to expand...
Click to collapse
Sorry I don't have that device to test. This is confirmed on the carrier version of the LG G3 only.
Thank You
I found a post similar to this that no matter where I looked - I was always referred back to that post - which was written in poor english - no download links worked. I appreciate this post. Saved my ass.
EMMC test fail
using D855 16gb
any fix ??
zohaibkhan143 said:
EMMC test fail
using D855 16gb
any fix ??
Click to expand...
Click to collapse
I have never had that error myself but it means either that you are using the wrong firmware images or that you have a hardware issue.
l33tlinuxh4x0r said:
I have never had that error myself but it means either that you are using the wrong firmware images or that you have a hardware issue.
Click to expand...
Click to collapse
tot is correct. I think so its a hardware issue.. I need a medusa box for fix maybe its the last solution for my G3:crying:
LGD855AT-00-V10e-EUR-XX-JUL-08-2014-16G+0
using this tot. Is it fine ?
l33tlinuxh4x0r said:
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command promt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
Click to expand...
Click to collapse
I'm going to go insane. I'm stuck at doing the gnd and the capacitor. My laptop detects the device but it says devce not recognized. i installed the qualcomm high speed drivers you had in download on 32bit windows 7 and also tried on 64bit windows 8. Exact same thing, usb device not recognized. Also, I've installed the verizon lg g3 specific drivers and tried too but it doesnt work. Please HELP !
Thanks to USFBjornTutorials for the video at https://www.youtube.com/watch?v=I4kI8ZdwcZ4
ALL INSTRUCTIONS ARE SOLELY THE STEPS CREATED BY USFBJORNTUTORIALS I MERELY JUST MADE THE STEPS UNDERSTANDABLE AND EASIER TO FOLLOW . I NOR XDA ARE RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
PRE-REQUISITES
Un-rooted Sony XPERIA Z3V
All Files Below
Fully Charged Phone
Phone in USB Debug mode active
Phone with Unknown Sources for App install active
TESTED
January 17, 2016
There was some IMPORTANT missing steps that I was able to figure out and lay out a proper step by step guide.
Step 1: Make sure you disable Driver Signature if you're running on Windows 8-10: HERE
Step 2: Download and install correct Flashtool Version and install HERE
>>>>CORRECT FILE SHOULD BE flashtool-0.9.18.6-windows.exe 119MB
>>>>Install 3 drivers, from C:\Flashtool\drivers (Fastboot Mode, Flashmode, Xperia Z3 Device Driver) - If all install successfully, you successfully disabled Driver Signature.
>>>>Driver pack verstion v1.8(20141101)
Step 3: If you do not have build # 23.0.E.0.376, download this firmware and place it in C:\Users\(YourUser)\.flashTool\firmwares
>>>>NOTE This was a little confusing since the 0.9.18.8 FLASHTOOL is the one that creates the Firmware folder in .flashtool
>>>>DOWNLOAD FROM HERE (Otherwise Skip This Step)
>>>>FILE NAME D6708_23.0.E.0.376_VER.ftf 1.54GB
Step 4: Download this file , and place it in your SD card or Internal Phone Memory. You will need this in a later process (Do not Unzip) :
>>>>DOWNLOAD FROM HERE
>>>>FILE NAME flashable-prerooted.zip 1.54GB
>>>>Copy file to SD
>>>>Placing file in Internal Storage causes problems during flash.
Step 5: Download this, it will be used to root when you have Build # 23.0.E.0.376:
>>>>DOWNLOAD FROM link bad at Youtube page.
>>>>I BELIEVE THIS IS THE FILE HERE
>>>>FILE NAME D6616_ROOTFULL.ZIP
>>>>Unzip to same Download folder. Creates folder called D6616_root
>>>>The video uses a file called D6616_ROOTFULL.zip so I was able to find the file.
Step 6: Download this to install DualRecovery Click XZ Dual Recovery, then XZDualRecovery 2.8.21, and download the second one on the list, which is an installer.
>>>>DOWNLOAD FROM HERE
>>>>FILE NAME T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip 24.9MB
Step 7: Flashing Steps
Launch FLASHTOOL
At this point your Phone should say its Android 4.4.4 Build 23.0.E.1.44
WAIT
If Phone asks to Allow USB Debug, click YES
Select D66XX Sony Xperia Z3 and double click
Click YES to continue
WAIT
Copy flashable-prerooted.zip to Phone SD Card. >Copying to Internal causes problems during flash<
Click Lightning Bolt
Select FLASHMODE
Click OK
If Firmware does not show up, click the '...' box and find your file
Click 'Flash'
WAIT
Wait until is says to Turn Phone OFF
Now Hold Vol- button then insert USB
Phone now in FLASH Mode
Allow FLASHTOOL to continue
WAIT
Disconnect Phone when done and Turn ON
At this point you should have Android 4.4.4Build 23.0.E.376 on your phone
Go through phone setup steps
Reconnect Phone in USB Debug with Unknown Sources checked >>>IMPORTANT<<<
Now go the D6616_root folder
Install javainst.exe. (If not already done)
This installs Java 8, Java x64 8, JDK 8 and JDK x64 8
Allow Java installer to finish
Close Java Installer
Run exploit.bat
Go to Developer Options, Scroll down to 'Select Debug App' and select com.dosomder.testapp2
Check 'Wait for Debugger' right below the Select Debug App option
Then hit any key to continue the Exploit in the CMD box
Wait for commands to finish
If everything went OK you will see a message that says exploit.bat was successful
Hit any key to continue again and wait for all the commands to finish
Phone with auto Restart
Phone is now ROOTED!!!
SuperSU is now installed on phone
Check ROOT access by opening SuperSU. If file opens properly you have access. If not you will have to retry.
Now go back to your main folder and un-Zip T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip creating a folder lockeddualrecovery
Go to folder and run install.bat
Select #4 to install ADB drivers to windows. (If not already done)
Click any Key to continue and go back to main menu
Select #1 to install on ROM with SuperSU
Grant USB debug on phone
Grant ROOT access on SuperSU
Wait for installer to so its thing
Unplug USB
Phone Restarts to Recovery
You now have TWRP v2.8.7.0 Recovery!
Click Install
Find the flashable-prerooted.zip file you copied earlier
Swipe to Confirm Flash
Allow Phone to install Firmware
Click REBOOT SYSTEM
Wait for Phone to boot, takes a while. About 10 minutes
You now have a Sony Z3V Rooted with Lollipop Android 5.0.2 Build 23.1.D.0.509 on your phone!!!!!!
You can access TWRP by clicking Power + Vol- during boot or use the Quick Boot app
IF PHONE GETS STUCK AT SONY BOOT LOGO, TRY AGAIN AND DOWNLOAD FLASHABLE-PREROOTED.ZIP FILE AGAIN. Since both files are so big you can expect errors in the download.
Thanks to @zxz0O0, for achieving root for our Z3v, @USFBjornTutorials for initial video, @Androxyde for FLASHTOOL, @[NUT] for TWRP Flash Tool, @hqdvista for Java exploit tool, @GigaSPX for the Flashable Pre-Rooted 5.0.2 Firmware and countless others for their individual work.
{
"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"
}
Here it is. Android 5.0.2 Build 23.1.D.0.509 on the Sony Z3v D6708.
Runs great and smooth
Good writeup, very detailed.
MOD EDIT There is never a need to quote the whole OP, especially for a 4 line reply.
It is nice that it's very detailed, but I've updated my guide to skip all these frustrating steps from the beginning. Now this can be done in merely a few steps.
Oh and, you've never credited the prerooted Lollipop zip in my name since I have added a mod to it and it's the exact same link that I distribute.
GigaSPX said:
It is nice that it's very detailed, but I've updated my guide to skip all these frustrating steps from the beginning. Now this can be done in merely a few steps.
Oh and, you've never credited the prerooted Lollipop zip in my name since I have added a mod to it and it's the exact same link that I distribute.
Click to expand...
Click to collapse
Done. I've been looking for various methods and one that I tried last year Bricked phone. The video helped fill in the gaps. No disrespect meant by any of this. I do procedures for a living so I wanted to make something that was easier to follow.
bullriders said:
Done. I've been looking for various methods and one that I tried last year Bricked phone. The video helped fill in the gaps. No disrespect meant by any of this. I do procedures for a living so I wanted to make something that was easier to follow.
Click to expand...
Click to collapse
How was your phone bricked?
I remember when the bootloader was first unlocked and I tried method. Worked for 2 days then phone would not do anything. Not charge, reset or even go into download mode.
Took it to store acted like I didn't know what happened and they ended up replacing it since they could not reset either
bullriders said:
I remember when the bootloader was first unlocked and I tried method. Worked for 2 days then phone would not do anything. Not charge, reset or even go into download mode.
Took it to store acted like I didn't know what happened and they ended up replacing it since they could not reset either
Click to expand...
Click to collapse
Could you perhaps go into deeper details how you achieved it? It might be related to the other developer whose phone hard bricked on him too.
I'm sorry...
Did you just seriously release a 57 step procedure to install rooted Lollipop to the z3v without doing the research here to see that it can be done in 7 steps?
AddictedToGlass said:
I'm sorry...
Did you just seriously release a 57 step procedure to install rooted Lollipop to the z3v without doing the research here to see that it can be done in 7 steps?
Click to expand...
Click to collapse
Don't be too hard on him. This would have gotten my guide beaten if he released his before or at the same time mine came out. But it's good to rather simplify things in a matter of 7 steps to get where you need to be. xP
I could have done it in 7, but the other guide I was using seemed to have steps missing and a bunch of information missing.
I am only trying to help, But I guess providing detailed instructions for people that aren't experienced isn't necessary.
And I did check every once, the ones I tried last year bricked my phone and I didn't want to chance it again.
GigaSPX said:
Don't be too hard on him. This would have gotten my guide beaten if he released his before or at the same time mine came out. But it's good to rather simplify things in a matter of 7 steps to get where you need to be. xP
Click to expand...
Click to collapse
bullriders said:
I could have done it in 7, but the other guide I was using seemed to have steps missing and a bunch of information missing.
I am only trying to help, But I guess providing detailed instructions for people that aren't experienced isn't necessary.
And I did check every once, the ones I tried last year bricked my phone and I didn't want to chance it again.
Click to expand...
Click to collapse
I've always felt everyone needs to root at least one phone step by step to gain a grasp of what is actually going on during the process. GigaSPX's "automated" method is far easier and greatly appreciated but if someone who has never done this before has a problem then unbricking the phone is a lot more difficult and intimidating. Having contact with the actual rooting/installing a ROM process is a learning experience.
It's like putting a kid new to driving behind the wheel of my manual shift truck or sitting them in front of a DOS computer. I grew up with DOS and tinker around with Linux a little so the command line is sort of an old friend. My stepkids look at it as if it is a mutated monster.
What about updating without root and not wanting to root phone? Just flash ftf works?
Sent from my Sony Z3v on Tapatalk
I don't think that will or can work because to flash 5.0 you have to unlock the bootloader and install TWRP
MGSBigBoss said:
What about updating without root and not wanting to root phone? Just flash ftf works?
Sent from my Sony Z3v on Tapatalk
Click to expand...
Click to collapse
bullriders said:
I don't think that will or can work because to flash 5.0 you have to unlock the bootloader and install TWRP
Click to expand...
Click to collapse
You can flash unrooted stock Lollipop. You just download the FTF file through Xperifirm, put the Z3v in flash mode, then just flash it there. Although I think you would have much better benefits being rooted.
GigaSPX said:
You can flash unrooted stock Lollipop. You just download the FTF file through Xperifirm, put the Z3v in flash mode, then just flash it there. Although I think you would have much better benefits being rooted.
Click to expand...
Click to collapse
I'm going to wait before the flashing til Feb and see if verizon drops a update. If not I'll flash but a rep told me expect it in summer or spring break. Have you spoken with verizon again for any validity?
Sent from my Sony Z3v on Tapatalk
I wouldnt count on update. Verizon is in the business of getting you to spend money on phones, not give life to older devices.
Sony has had the Lollipop update available to carriers for a year now but many in the US deny the updates to users.
I'm aging if the computer industry behaved how wireless providers do, people would flipping riot.
from a business standpoint I don't see how either Sony or Verizon would gain from releasing an update this late in the game. This phone was released in October 2013? The people that upgraded to this phone when it was released will be coming out of their contracts in a few months so Verizon has no incentive to upgrade it. They want people rolling in to a new two year payment plan on a new devices rather than going month to month with an old device. I can't see why Sony has any stake at all in this at all. They aren't selling any new phones to Verizon customers and likely won't be anytime in the near future so they have zero reason to assist/push verizon with the update. I could be wrong but I think this phone is dead and forgotten. Which is too bad because it was better version of the Z3, imho, with wireless charging and better reception than the other versions.
BladeRunner said:
from a business standpoint I don't see how either Sony or Verizon would gain from releasing an update this late in the game. This phone was released in October 2013? The people that upgraded to this phone when it was released will be coming out of their contracts in a few months so Verizon has no incentive to upgrade it. They want people rolling in to a new two year payment plan on a new devices rather than going month to month with an old device. I can't see why Sony has any stake at all in this at all. They aren't selling any new phones to Verizon customers and likely won't be anytime in the near future so they have zero reason to assist/push verizon with the update. I could be wrong but I think this phone is dead and forgotten. Which is too bad because it was better version of the Z3, imho, with wireless charging and better reception than the other versions.
Click to expand...
Click to collapse
The only difference is that the regular Z3 has the better, all aluminum around look, better ISO camera for nightshots, and it has a screen RAM for improving battery life to be as good for two days.
Pretty much, we got jipped.
In my personal experience with both an unlocked Z3 and a T-Mobile Z3 I was not impressed, the Z2 and the z3v were far better devices. Whatever improvements may have been made in the camera were more than offset by the poor reception (it is a phone, after all) The Z2 had the best battery life of any pjhone I've owned. I was getting 60+ hours off the charger with 5+ hours of SOT. I'm decidedly not a power user but that is still a significant time not being plugged in. In my normal use I couldn't really see much of a difference between the z3v and the Z3 battery life.
I have a problem trying to root the Samsung Galaxy Express 3, model samsung-SAMSUNG-SM-j120a
I have tried KingoRoot, One-Click-Root, and SRS Root. does anyone know of maybe a batch or quick root for this model?
Any advice in any direction is appreciated.
SRS Root log says rooted, but it is not rooting. strange.
---= SRS One-Click-Root v5.1 =---
1:18:28 PM - Starting ADB Server..
1:18:34 PM - Manufacturer: samsung
1:18:34 PM - Model: SAMSUNG-SM-J120A
1:18:34 PM - Android Version: 6.0.1
1:18:34 PM - Build ID: MMB29K.J120AUCU1APC8
1:18:35 PM - Board ID: universal3475
1:18:35 PM - Chipset Platform: exynos3
1:18:35 PM - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
1:18:35 PM - Query Server for Best Method.. Found Rootkit: 8
----= Start Rooting Process.. Please Wait =----
1:18:36 PM [+] Testing exploit: root8 (please wait..)
1:18:37 PM [+] Remounting /system Filesystem as R/W..
1:18:37 PM [+] Installing SU Binary...
1:18:38 PM [+] Installing SuperUser APK...
1:18:38 PM [+] Remounting /system Filesystem as R/O..
1:18:44 PM [+] Rooting Complete !
Sincerely, The-mechanic-who-covered-his-s6-edge-in-metal-dust-in-his-pocket-and-ruined-the-thing.
Just searched and saw this - SRSroot update from 6/6 on twitter :
#SRSRoot: samsung SAMSUNG-SM-J120A (Build: MMB29K.J120AUCU1APC4) #Android 6.0.1 Now Supported for #Root at
google search for
root Samsung J120A
Thank you
MR_Sysexpert_AND said:
Just searched and saw this - SRSroot update from 6/6 on twitter :
#SRSRoot: samsung SAMSUNG-SM-J120A (Build: MMB29K.J120AUCU1APC4) #Android 6.0.1 Now Supported for #Root at
google search for
root Samsung J120A
Click to expand...
Click to collapse
Thank you sir, ill be back to let you know if it worked. For those who dont know, the galaxy express 3 is a decent cheap phone. 75 bucks at Walmart. Mine is a go phone
Animonger said:
Thank you sir, ill be back to let you know if it worked. For those who dont know, the galaxy express 3 is a decent cheap phone. 75 bucks at Walmart. Mine is a go phone
Click to expand...
Click to collapse
It showed that in mid may also... I'll retry too.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
It showed that in mid may also... I'll retry too.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
If your problem is not solved try the latest version of kingroot. It should root almost all samsung devices.
Link are just below. Its one tap root app. No PC needed.
http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-3-android-apk-download/
grandpajiver said:
It showed that in mid may also... I'll retry too.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope, still dont work. lame.
Samsung Galaxy Express 3 J120A
I can't find any no pc required rootkit software for this lame ads phone I should just throw it against the wall
Delete plz
mdmaher said:
If your problem is not solved try the latest version of kingroot. It should root almost all samsung devices.
Link are just below. Its one tap root app. No PC needed.
http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-3-android-apk-download/
Click to expand...
Click to collapse
Tried it, no go.
I've rooted the s4, the original Kindle fire, some weird Motorola photon, both Nexus 7s, htc 8 & 9. All required unlocking the bootloader. Not sure how to do that with this phone. I turned on adb debugging, oem boot unlock.. I remember with the s4 I had to load a crap ton of stuff in kies... then something else to reset the knox flag.
The phone only has 8 gigs of internal storage, 5 of which is used up by the os. Not all games/apps want to move to the SD card and because Sammy decided that no one would like the option to have s spanned file system between internal and external storage, it has become somewhat useless. Xposed with obb on SD is the cure, but I need twrp and su.
I can't get this thing to even go to fast boot.. that just reboots the phone. Download I'd nominally more useful, but it wants files. Recovery allows adb side load.. that's about it.
It's a nice cheap phone, but I have just been avoiding manufacturers who lock the thing down, so I'm way out of the loop. Any pointers are welcome.
Sent from my HTC One M9 using XDA-Developers mobile app
Still no luck
I've tried everything I know of. Thanks for keeping up with this page. Lets keep it alive, this is the only thread in existence that i've seen so far.
Isn't a rebrand of the Samsung j1? Maybe the instructions for rooting that would work for you guys I could be wrong but it was a thought when I seen this thread
inub said:
Isn't a rebrand of the Samsung j1? Maybe the instructions for rooting that would work for you guys I could be wrong but it was a thought when I seen this thread
Click to expand...
Click to collapse
Does the j1 run marshmallow?
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
Does the j1 run marshmallow?
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm sure it does if the express 3 does all the hardware is the same
MR_Sysexpert_AND said:
Just searched and saw this - SRSroot update from 6/6 on twitter :
#SRSRoot: samsung SAMSUNG-SM-J120A (Build: MMB29K.J120AUCU1APC4) #Android 6.0.1 Now Supported for #Root at
google search for
root Samsung J120A
Click to expand...
Click to collapse
I just had to give it a try myself, even though two other people claimed it didn't work. And they are right, it claims your phone is rooted, but it's not. Very aggravating. If it can't be rooted, it just can't be rooted....but why the heck does SRSroot claim their software will do it when in fact it will NOT?
I'm just disappointed if it can't be rooted, but it makes me angry to be lied to. And SRSroot lied. Makes me wonder exactly what their software actually put on my PC....since they can't be trusted. Now I have to waste even more time scanning and scrubbing my PC for whatever malware they wanted to install with their bogus software that does not work. And if it doesn't do what it claims to do, exactly what is it doing? No telling what their bogus software put on my phone, because it sure didn't root it. Despite claiming it did.
inub said:
I'm sure it does if the express 3 does all the hardware is the same
Click to expand...
Click to collapse
Dunno... I've seen references to j100a-h, j120a/sm-j120a seems different (not dual-sim, exynos processor).. dunno if the others are gsm-based.
Haven't seen any firmware replacements in case loading the partitions (or whatever Kies does) above through Kies is flat out wrong and messes with the radio.
My knowledge with Sammy's internals is rather lacking, and until that specific at&t model has a stable root (and twrp would be nice) I'm going to be a chicken about this.
I saw king root had a new release. May try that again. Will message if it's working.
you can try to root it from computer.. i ever heard about geniusroot.. but i never try it, hope this will work for you
i asked my best friend who knows alot more then i ever thought of and he said the best bet with the new samsungs is king root like yall have been trying or a program called iroot he talked about developer settings on the phone called oem unlock and usb debugging and download mode being volume down + home + power in his text message I think if you could get into download mode you should be able to use tools like odin or adb to push a recovery or get root access but that might take a developer or someone with more knowledge to use ota tools and dump a boot image and build a custom recovery or some advanced **** like that if someone hasnt already I'm sure xda university could turn up detailed steps to porting clockworkmod for now I guess its a waiting game for yall till more ppl end up with these devices in hand and some free time i included some files you may need with a grain of salt to get anyone started that turned up from a quick search for your device
https://drive.google.com/file/d/0B6wa4Qj-h93HbkdRVGN5QjRqbGM/view?usp=sharing
inub said:
i asked my best friend who knows alot more then i ever thought of and he said the best bet with the new samsungs is king root like yall have been trying or a program called iroot he talked about developer settings on the phone called oem unlock and usb debugging and download mode being volume down + home + power in his text message I think if you could get into download mode you should be able to use tools like odin or adb to push a recovery or get root access but that might take a developer or someone with more knowledge to use ota tools and dump a boot image and build a custom recovery or some advanced **** like that if someone hasnt already I'm sure xda university could turn up detailed steps to porting clockworkmod for now I guess its a waiting game for yall till more ppl end up with these devices in hand and some free time i included some files you may need with a grain of salt to get anyone started that turned up from a quick search for your device
https://drive.google.com/file/d/0B6wa4Qj-h93HbkdRVGN5QjRqbGM/view?usp=sharing
Click to expand...
Click to collapse
Yes, if I could fastboot flash recovery twrp.img/cwm.img that would make life easier. However, the bootloader is locked, and generally one must unlock it... I cant even figure out how to get the phone to respond in fastboot mode.
I turned on adb debugging, and I can adb shell, adb push, adb reboot bootloader (which just reboots the phone), adb reboot recovery (which allows sideloading.. I think), and adb reboot download, which seemed the most useful.
I can't set adb to root, I can't mount system r/w so I can place/flash su/supersu.
Latest KingRoot did not work, havent seen iRoot before, looks like you have an md5 of the boot image in there, instead of the actual image...
Yeah. I'm clueless about this one. I'm sure its something stupidly easy.
i dont have the device so I cant hand it off to my friend or i would also i was wrong about the j1 as someone said but i do belive the amp 2 but searching specs the amp 2 looks to be a sister phone you might wanna keep up with the root options that may pop up for that only thing i was told was enabling usb debugging and the oem unlock option first in the developer settings like in the screenshot from that phone id look into maybe frama or towel that might work from the phone side idk just trying to help
{
"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"
}
grandpajiver said:
Yes, if I could fastboot flash recovery twrp.img/cwm.img that would make life easier. However, the bootloader is locked, and generally one must unlock it... I cant even figure out how to get the phone to respond in fastboot mode.
I turned on adb debugging, and I can adb shell, adb push, adb reboot bootloader (which just reboots the phone), adb reboot recovery (which allows sideloading.. I think), and adb reboot download, which seemed the most useful.
I can't set adb to root, I can't mount system r/w so I can place/flash su/supersu.
Latest KingRoot did not work, havent seen iRoot before, looks like you have an md5 of the boot image in there, instead of the actual image...
Yeah. I'm clueless about this one. I'm sure its something stupidly easy.
Click to expand...
Click to collapse
Hey bro we appreciate the insight, we've tried this as a collective but to no avail yet. Our best bet is to keep trying different things until we come up with a working batch file unless kingo comes up with something. Thank you all for keeping the thread alive
there is a method to unlock the bootloader of this device. researched and found nothing about it
therafael1910 said:
there is a method to unlock the bootloader of this device. researched and found nothing about it
Click to expand...
Click to collapse
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
And
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
aryanhington said:
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
Click to expand...
Click to collapse
Says who? This is blackjack/XT2055?
sd_shadow said:
Says who? This is blackjack/XT2055?
Click to expand...
Click to collapse
I can confirm that it's not possible on the XT2055-1 running Mediatek MT6765 SoC
Did anyone try this? Can someone confirm if this works for you?
link
or folllowed this
read my post
aryanhington said:
read my post
Click to expand...
Click to collapse
It is easily possible, stop spreading BS
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
{
"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"
}
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, (only use this in case you wiped the bootloader in order to reflash it, the actual unlocking is done by using this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows (which again contains the first command, which should only be used if the bootloader is corrupted or so, unlock using second command from terminal) . Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen.
You'll also get a big "CARRIER INVALID" message on the home screen. I tried relocking the bootloader to fix it, but that put the phone into red state and I had to reflash the bootloader using the above mentioned command. On another note, when I trial and error-ed the unlocking process, I first used the bootloader reflash command (which effectively invalidated it) so that may be the sole cause of the invalid message and not the unlocking itself (as the message appeared after reflashing and before unlocking). If anyone tries this, just use python mtk da seccfg unlock and report back.
FakedKetchup said:
It is easily possible, stop spreading BS
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
View attachment 5889467
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, If it wont unlock using the custom G8 script, just run this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows. Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
View attachment 5889471
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen. You'll also get a big "CARRIER INVALID" message on the home screen, so after you ROOT make sure to relock the bootloader using the same method but the command is python3 mtk da seccfg lock
Click to expand...
Click to collapse
please can you kindly elaborate how you got proinfo.bin and seccfg.bin in the first place? also do you know if it uses any of the payload.bin files which are included with the mtkclient program?
aryanhington said:
please can you kindly elaborate how you got proinfo.bin and seccfg.bin in the first place? also do you know if it uses any of the payload.bin files which are included with the mtkclient program?
Click to expand...
Click to collapse
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
FakedKetchup said:
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
Click to expand...
Click to collapse
do you mean the file you attached bootloader_g8powerlite.zip , you dont know where desbloq_bootloader.bat, proinfo.bin , seccfg.bin are from? because they are not mentioned on https://github.com/bkerler/mtkclient
FakedKetchup said:
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
Click to expand...
Click to collapse
also how is the scatter file used ? i see you attached it but no mention on how its used
aryanhington said:
also how is the scatter file used ? i see you attached it but no mention on how its used
Click to expand...
Click to collapse
1. as i said i dont know, i found the files in the video description
2. scatter file is a useful file for flashing stuff like bootloaders though SP-Flash-Tools. I ripped it from the stock rom which i also just downloaded from the internet. I haven't tried flashing anything yet but it seems the scayyer file (and thus the MTK chip) deosnt allow flashing a nev recovery/bootloader/rom anything really. Need to check again later and play with it a bit more
FakedKetchup said:
1. as i said i dont know, i found the files in the video description
2. scatter file is a useful file for flashing stuff like bootloaders though SP-Flash-Tools. I ripped it from the stock rom which i also just downloaded from the internet. I haven't tried flashing anything yet but it seems the scayyer file (and thus the MTK chip) deosnt allow flashing a nev recovery/bootloader/rom anything really. Need to check again later and play with it a bit more
Click to expand...
Click to collapse
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off. i think you may have the wrong scatter file in that case
aryanhington said:
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off. i think you may have the wrong scatter file in that case
Click to expand...
Click to collapse
Yes i think there is another video on his channel showing that before flashing you need to once again short the 2 pins and execute another program, then flash using SP Tools. There is no error, but when i load up the scatter file, it shows bunch of partitions, none of which are named boot/recovery/bootloader etc. so i don't know if its actually possible. Also I recommend doing all this on Linux, much less hassle, but you will need to compile libpng-12 in order for SP Tools to work. On Ubuntu there should be a binary package in the repos but i used Debian and the package is not supported since release 16.04 so...
according to his channel, you can root it. He uses something called Avenger Box which i assume is some flahing hardware, but we can use SP Flash tools just fine
First, backup NVRAM using SP flash tools in the Readback section
Click ADD NEW and save it to a location on your PC
Then open up your scatter file and look for partition called NVRAM, see the lines "LINEAR START ADRESS", as well as PARTITION SIZE, enter these values to the readback popup menu as such:
(the values on the picture are not real)
Press OK, plug in your device with the shorted pins, press Readback ICON and see if its successful. I am not sure if disabling the protection is needed for readback, will attempt tomorrow.
Tutorial video or a generic guide
Then you can take advice from this video although he isn't using SP Tools so its not a step by step kind of thing. Also for some reason he refuses to share the unlock protection scripts as he is "running a business" by rooting these phones, what a clown , ill try to DM him and see if he shares it or whatever. Ill try to find a way to root it via SP but its a hit or miss.
Edit: Found the script on this exact website:
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
So on some phones you hold downa volume button to flash but in our case we most likely need to short the 2 pins again
aryanhington said:
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off.
Click to expand...
Click to collapse
FakedKetchup said:
Yes i think there is another video on his channel showing that before flashing you need to once again short the 2 pins and execute another program, then flash using SP Tools. There is no error, but when i load up the scatter file, it shows bunch of partitions, none of which are named boot/recovery/bootloader etc. so i don't know if its actually possible. Also I recommend doing all this on Linux, much less hassle, but you will need to compile libpng-12 in order for SP Tools to work. On Ubuntu there should be a binary package in the repos but i used Debian and the package is not supported since release 16.04 so...
View attachment 5891625
according to his channel, you can root it. He uses something called Avenger Box which i assume is some flahing hardware, but we can use SP Flash tools just fine
First, backup NVRAM using SP flash tools in the Readback section
View attachment 5891651
Click ADD NEW and save it to a location on your PC
Then open up your scatter file and look for lines "LINEAR START ADRESS", as well as PARTITION SIZE, enter these values to the readback popum menu as such:
View attachment 5891667
Press OK, plug in your device, press Readback ICON and see if its successful. I am not sure if disabling the protection is needed for readback, will attempt tomorrow.
Tutorial video
Then you can take advice from this video although he isn't using SP Tools so its not a step by step kind of thing. Also for some reason he refuses to share the unlock protection scripts as he is "running a business" by rooting these phones, what a clown , ill try to DM him and see if he shares it or whatever. Ill try to find a way to root it via SP but its a hit or miss.
Edit: Found the script on this exact website:
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
So on some phones you hold downa volume button to flash but in our case we most likely need to short the 2 pins again
Click to expand...
Click to collapse
in regards to not seeing the recovery partition etc on sp flash tool, its because the scatter file you have used doesnt contain those partitions. I can help you do a full readback of the rom via sp flash tool and create a proper scatter file for your device, because that one you used is most likely incomplete or for another device.
also you lost me at the part regarding libpng-12 , thats only used to render png files . you can come on libera.chat irc and i have created a channel called #motog8powerlite if you need help as its easier to communicate on there
aryanhington said:
in regards to not seeing the recovery partition etc on sp flash tool, its because the scatter file you have used doesnt contain those partitions. I can help you do a full readback of the rom via sp flash tool and create a proper scatter file for your device, because that one you used is most likely incomplete or for another device.
also you lost me at the part regarding libpng-12 , thats only used to render png files
Click to expand...
Click to collapse
libpng-12 is a dependency of the program, probably for the Welcome tab which is made out of pictures instead of a mark language elements...
In regards to the recovery partitions, i found out it is because on devices with A/B partitions, the recovery is merged into the boot.img file. Im not aware of any custom recoveries made for it.
Patching it for root is as straightforward as installing older version of Magisk App on any android phone, copying the stock boot.img anywhere on the device, then patching the file from the app and flashing using SP Tools.
I patched the boot.img from the stock rom. I also managed to successfully execute the bypass script. It used to throw out Missing Default Config error, but i found the default config on github (exploits-collection; attachments) and used that just fine - copy the contents of the archive into the root folder of the bypass utility:
So, in order to unblock the protection, one needs to SOLDER the two pins, any other method was extremely unreliable. On Windows, install LIBUSB drivers from the attached file or from sorceforge. Do it in such a way that you run the installer and you'll get to this popup:
then click next
and youll see bunch of devices. Now plug in the phone with unplugged battery and shorted pins, then wait till a new device pops up, could be called MTK Device or anything like that. You select it and install the libusb library to it. Unplug the phone.
CD into the Bypass Utility folder via CMD/Terminal and run as root: python3 main.py, but install the requirements beforehand (sudo) pip install pyusb pyserial json5 ( running the program as root, the dependencies may not carry over so install them as root as well)
If you did everything right, you should see a prompt saying "Waiting for device"
Then you keep the 2 pins shorted and plug in the phone, if all goes right you should see this output:
On linux, you need a custom patched kernel, either get the patch or get a prepatched kernel or live boot a FireOS iso.
from the README file:
## Usage on Linux
Skip steps 1-2 after first usage
To use this you need [FireISO](https://github.com/amonet-kamakiri/fireiso/releases) or [this patch](https://github.com/amonet-kamakiri/kamakiri/blob/master/kernel.patch) for your kernel
Prebuilt kernels for various distros are available [here](https://github.com/amonet-kamakiri/prebuilt-kernels)
1. Install python
2. Install pyusb, pyserial, json5 as root with command:
```
pip install pyusb pyserial json5
```
3. Run this command as root and connect your powered off phone with volume+ button, you should get "Protection disabled" at the end
```
./main.py
```
4. After that, without disconnecting phone, run SP Flash Tool in UART Connection mode
Click to expand...
Click to collapse
As long as you keep the phone plugged in, the protection is off, however i found myself often needing to re-run the script before each action that utilizes the bootrom.
Using the mentioned scatter file throws out errors. I tried to first remove the protection and then immediately run the NVRAM readback but it failed
Full guide https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
I tried to make my own scatter file by using MTK Droid Tools, but this utility only supports MTK65xx and below CPUs, so it isnt possible in our case. I also tried a generic MTK6765 scatter but that didn't work either. Without the scatter file, the tool doesn't kow where to write the boot.img and thus its a dead end. I'll try to do this on a different PC see if anything changes but i highly suspect its just a wrong scatter file. I got it from this allegedly stock rom.
What i stumbled across is this mirror site, where basically every ROM this device ever had is uploaded, so i think ill start there.
HUGE EDIT:
Accidentally i didnt load up the scatter file from the ROM directory but instead from a different location, tus it didnt load all the other necessary parts. It seems like you have to flash everything, not just one part like recovery or bootloader. Or maybe you can flash a single thing and that is what the square checkboxes are for lol
Thus i can happily announce that i successfully flashed the boot.img, after which Root Checker wstill reported NON-ROOT. I installed MAGISK APP once again and it asked me to reboot to finalize, then it rebooted, i entered the Magisk app and rooted directly from the app. -and the phone is rooted !
Technically it could be possible to flash a custom ROM using this exact tool, although i can only imagine few of the hardware actually working without manually fixing ACPI etc.
It is certainly one of the most difficult root procedures, but nothing unusual in the world of reverse engineering
FakedKetchup said:
libpng-12 is a dependency of the program, probably for the Welcome tab which is made out of pictures instead of a mark language elements...
In regards to the recovery partitions, i found out it is because on devices with A/B partitions, the recovery is merged into the boot.img file. Im not aware of any custom recoveries made for it.
Patching it for root is as straightforward as installing older version of Magisk App on any android phone, copying the stock boot.img anywhere on the device, then patching the file from the app and flashing using SP Tools.
I patched the boot.img from the stock rom. I also managed to successfully execute the bypass script. It used to throw out Missing Default Config error, but i found the default config on github (exploits-collection; attachments) and used that just fine - copy the contents of the archive into the root folder of the bypass utility:
View attachment 5892949
So, in order to unblock the protection, one needs to SOLDER the two pins, any other method was extremely unreliable. On Windows, install LIBUSB drivers from the attached file or from sorceforge. Do it in such a way that you run the installer and you'll get to this popup:
View attachment 5892951
then click next
View attachment 5892953
and youll see bunch of devices. Now plug in the phone with unplugged battery and shorted pins, then wait till a new device pops up, could be called MTK Device or anything like that. You select it and install the libusb library to it. Unplug the phone.
CD into the Bypass Utility folder via CMD/Terminal and run as root: python3 main.py, but install the requirements beforehand (sudo) pip install pyusb pyserial json5 ( running the program as root, the dependencies may not carry over so install them as root as well)
If you did everything right, you should see a prompt saying "Waiting for device"
Then you keep the 2 pins shorted and plug in the phone, if all goes right you should see this output:
View attachment 5892965
On linux, you need a custom patched kernel, either get the patch or get a prepatched kernel or live boot a FireOS iso.
from the README file:
As long as you keep the phone plugged in, the protection is off, however i found myself often needing to re-run the script before each action that utilizes the bootrom.
Using the mentioned scatter file throws out errors. I tried to first remove the protection and then immediately run the NVRAM readback but it failed
View attachment 5892981
Full guide https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
I tried to make my own scatter file by using MTK Droid Tools, but this utility only supports MTK65xx and below CPUs, so it isnt possible in our case. I also tried a generic MTK6765 scatter but that didn't work either. Without the scatter file, the tool doesn't kow where to write the boot.img and thus its a dead end. I'll try to do this on a different PC see if anything changes but i highly suspect its just a wrong scatter file. I got it from this allegedly stock rom.
What i stumbled across is this mirror site, where basically every ROM this device ever had is uploaded, so i think ill start there.
HUGE EDIT:
Accidentally i didnt load up the scatter file from the ROM directory but instead from a different location, tus it didnt load all the other necessary parts. It seems like you have to flash everything, not just one part like recovery or bootloader. Or maybe you can flash a single thing and that is what the square checkboxes are for lol
View attachment 5893083
Thus i can happily announce that i successfully flashed the boot.img, after which Root Checker wstill reported NON-ROOT. I installed MAGISK APP once again and it asked me to reboot to finalize, then it rebooted, i entered the Magisk app and rooted directly from the app. -and the phone is rooted !
Technically it could be possible to flash a custom ROM using this exact tool, although i can only imagine few of the hardware actually working without manually fixing ACPI etc.
It is certainly one of the most difficult root procedures, but nothing unusual in the world of reverse engineering
Click to expand...
Click to collapse
please can you elaborate why you're using exploits_collection-master as before you mentioned you were using mtkclient-main? also do you know why a patched kernel is required on linux?
Not sure but without them it throws out errors, I looked up the error and found a GitHub page which was referenced to the mtkclient - it essentially needs a default config and I supplied that, the file contains configurations for many APUs which are listed in the readme file
Patched kernel I assume is necessary for the bootrom exploit, again if you took few minutes to check the links I mentioned it's all there on GitHub. The kernel needs a way to communicate with the MTK protocol, on Windows there is the VCOM Driver and LIBUSB wizard, on Linux you need to apply the driver to the kernel manually or download a prepatched one.
Hope I proved my point that it's indeed possible to root it and unlock the bootloader, it took me dozens of hours so least you could do is go ahead and edit all the messages where you confidently said it isn't and link this forum there.