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.
Related
I tried to flash latest rom from Asus website to my new Zenfone C because it had a weird issue, it came the user interface in taiwanesse, but when trying to change to english, it stayed in taiwanesse, so I wasnt able to setup it in first place.
Then, it came to my mind to flash the latest rom, and I used this guide in absence of a Zenfone C guide for flashing:
http://en.zenfoneasus.com/zenfone-recovering-returning-stock-rom-downgrade-clean-update-guide/
I did all the steps listed there first, and then tried the steps but with the red marked steps, flashing the dnx and ifwi also, no result.
The problem is that now im stuck in a bootloop, and cant advance from there, the Asus logo stays there forever.
What happened during flashing is this:
When I sideloaded the update.zip containing latest rom from Asus website, it said:
-Installing update
-Device image SKU: ww
OTA image SKU: WW
and suddenly after that it restarted, showed a huge Intel Inside logo that I never saw and then went to the dead android image. After waiting a while, the phone restarts, this time only showing the Asus logo with the Intel Inside logo beneath it (not the Intel Inside logo only that I mentioned earlier), and stays there forever.
I dont know what else to do, I dont know if Im doing something wrong.
Were you ever able to fix the problem?
No, until now, no
Sent from my Nexus 5 using Tapatalk
Solved!!!
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
kkdevta said:
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
Click to expand...
Click to collapse
I still need the fix man, I will really appreciate the posting of the solution! thanks in advance!
Sent from my Nexus 5 using Tapatalk
The Fix!
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
{
"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"
}
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Spartan Legionnaire said:
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Click to expand...
Click to collapse
Hopefully it should, I did it on a Windows 7 Professional 64 bit machine.
The USB drivers you download has Windows 8 drivers in it. I think that's all that is needed.
Yeah, I will try it then, and report back, thanks again.
Sent from my Nexus 5 using Tapatalk
kkdevta said:
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Click to expand...
Click to collapse
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Tjecing said:
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Click to expand...
Click to collapse
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
kkdevta said:
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
Click to expand...
Click to collapse
I don't know how to thank You.. But thanks a lot you safe my days..
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
do you know where i can find the correct .raw file for asus zenfone 5 A501CG ? i use lollipop, i dont know if that's matter =s
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Sent from my Mi 4i using XDA Free mobile app
hello brother...can you help me...
my zenfone 5 a500cg has been softrick and bootloop to...
if i'm turn on my phone
logo asus and then usb logo and then dead again...
i can't log into fastboot(power on+vol up)..
but i can log into cwm philz...
i try flash via adb sideload but always error bla bla bla tmp/updated.zip
if i try other ROM always like this ( please upgrade to image 4.3 first)
i try xftsk but always windriver error( i am use notebook win7)
i try asus flashtool with .raw zip rom but my serial number error just 12345678abcdef...
if i click start always device not detect...
help me bro
disappear3896 said:
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Click to expand...
Click to collapse
power and volume up (+)
Spartan Legionnaire said:
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
Click to expand...
Click to collapse
First and foremost, follow Spartan about how to deal with the driver install error. Read above. Second, those are the links for the raw images:
ww_A500CG_3.23.40.60_20150630.raw and many other phones. It was posted by thanhthuy. 500CG Lollipop: https://mega.nz/#!jwBDUKzJ!x3VD9VJrMe0CBs353DVnXlHr2dHQXepjcqtrR0gQDdU
500CG kitkat:
https://mega.co.nz/#!H8YkyLba!4Ye52JKAjzogGRVvCx2r9XoJIhou_uY3z6YH1xBges8
400CG 6.6.3 - https://mega.co.nz/#!HoRRnLCL!CV-iCMEUgRd_LwDc4QgNkevxKIGOKtFGDYrytt59EVE
400CG 7.3.3 - https://mega.co.nz/#!G8hRwYqR!Eu_l6r_6QSbhjID-MtYQU3v0q0voQ0GYkFeayy-3MFI
451CG: https://mega.co.nz/#!794U1TpT!rermqclZOpPKcYZY8z2YezUkQE-MWjYJgqyKMUAjYDo
600cg Kitkat: https://mega.co.nz/#!S1wlnYhC!doCPvf7ukeEFStcJPgqaEViE5oiHb_hpGSGnIh3n1IQ
Here for 600cg lollipop: https://mega.co.nz/#!3p4wBQAY!KUx26zaGdCBU6CGa4g68zT_iX9NxmIQCUvHiolfa_Oo
ZE550ML Lollipop 40.23 : https://mega.co.nz/#!HgBSySZA!EOxpsmPvHgCfl-9jUVRAv624Uq9LG4uvxuN83j6-P-k
ZE550ML Lollipop 40.40: https://mega.co.nz/#!P4RmXIwb!-xrDe8AYXdprZgUG4Ehs8fLNHhrdKpXdmaV3FBWPC_0
ZE551ML Lollipop: https://mega.co.nz/#!i4JRAQDR!9DzxtSd1oxDuCV6oc0rEhm-1sF4SA-94YPG9fLVw_lw
Source using Google cache (Vietnamese): http://webcache.googleusercontent.com/search?q=cache:w5AS-N1JrAoJ:zenphoneviet.com/threads/all-zen-stock-rom-firmware-kk-l-update-hang-tuan-chay-bang-asus-flash-tool.7066/+&cd=1
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
Those raw files are extremely difficult to find so if you pretend to have any of those phones i recommend to download. It works easily if you have fastboot. If you only have adb i did not saw working but i am trying.
---------- Post added at 07:38 AM ---------- Previous post was at 07:31 AM ----------
If you try to do that under adb they give a serial number mistake.
4 days trying to solve this bootloop using adb. At least one person here saved his phone with the raw links i found using google webcache in this vietnamese link so it was worth it. Looks like i will need to lose 40 days sending to Asus in Sao Paulo. What a hell folks, those asus firmwares are really crap. Set a great hardware for set poor software.
why my phone does not give any reaction when press power button+vol
I had same problem but different situation....I tried to make an experiment by changing systemui and I had done it with a wrong step .lucky I make a backup and tried to recover it.
But Things get worst when it failed to backupbang now my phone get stuck to Asus logo.I tried to follow the method that your all give in this thread but I can go to fastbootode with it must press power button+col down button.
CAN ANYBODY HELP ME WITH THIS PROBLEM
Sorry for my bad English
And I'm a newbie and try to learn something from pro
So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
NOTE: Dell just released LL 5.1 to the 7840!!! You can root it using xBIGREDDx's method here http://forum.xda-developers.com/showpost.php?p=62013578&postcount=43
You can use this guide for social-design-concept's method that xBIGREDDx mentions in his new method! PLEASE SHOOT HIM A THANKS!!!!
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
Especially social-design-concepts and his work here:
http://forum.xda-developers.com/showthread.php?t=2975096
Please shoot him a thanks! We owe him for the mad skill!
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
{
"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"
}
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.
BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP
You may want to credit some folks in your original post, for example (at a minimum) link to the place where you got the androidfilehost link, and mention the developers who created the tool.
Chyrio said:
So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.
Click to expand...
Click to collapse
Please update your post
social-design-concepts said:
Please update your post
Click to expand...
Click to collapse
Updated, sorry man I had to run out the door right as I finished the post didn't look over the thing well enough. Please let me know if I missed someone else, I'll add them in there!
Sent from my Venue 8 7840 using Tapatalk
Chyrio said:
BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP
Click to expand...
Click to collapse
How do you install xposed?
Flash the zip for the x86 based device located here http://forum.xda-developers.com/showthread.php?t=3034811 in social-design-concepts recovery, reboot and install the apk in that forum as well.
Sent from my Venue 8 7840 using Tapatalk
I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?
3itmn said:
I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?
Click to expand...
Click to collapse
I'm kinda new to it as well, but as far as I can tell, there isn't to much of a difference with how the android file structure is built. The hardware is different (obviously) creating the need for different drivers and new software. I know there is some kind of emulator for ARM architecture based apps in the OS itself but Recoveries and bootloader exploits are going to require redesign from the standard ways. Which social-design-concepts is hard at work on. Hopefully he can cook up something for us soon. I'm holding off on the 5.1 update for now waiting for the devs to work their magic.
Sent from my Venue 8 7840 using Tapatalk
Any root method for Mac osx or linux?
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
Click to expand...
Click to collapse
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?
Same here... Device state: Locked.
Have you solved your problem?
Anyone had the same issue?
UPDATE: Bootloader unlocked. Device State: Unlocked. But know when I try to insert T4 it copies the files and on the tablet is says "Okay." The cmw does not open. Please help!
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?
Click to expand...
Click to collapse
Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful
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
Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
chrismast said:
Need some help with my mi box (MDZ-16-AB) as somehow it got bricked.
Background:
A while ago I tried to connect my Bluetooth headset, connection process froze and I had to hard reboot (plug out/in power). After starting up, the box die not proceed further than the initial MI logo screen (think its the first screen altogether).
I tried already to flash diverse OTA files via recovery, to which I got access, but all ended up having similar error messages as the one attached (Can't mount/open catch etc.).
I am versed in flashing roms etc. and kind of remember seeing those messages when the file system got corrupted, hence my fear that I can't fix the box at all. To my knowledge, there is still no full rom img for the MDZ-16-AB version released!?
Anyone here with further advice?
Screenshot
Click to expand...
Click to collapse
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
brigantti said:
try anothe power supply i had a bootloop problem with my mibox and i replaced the power supply with one i had for a psp and is working now no more reboot or bootloop at all.
maybe is not same problem but you can try
Click to expand...
Click to collapse
tried that as well with my new mibox power supply, same result though.
bigtalker said:
try a different flash drive, formatted as FAT32
try formatting drive in a different computer
Click to expand...
Click to collapse
tried that, did not help
Found a guy with a similar issue on Reddit but he had also no luck...
I went thru 4 different flash drives until it relented to flash
If you cannot resolve this issue PM me and if your happy to send your device for testing/recovery purposes you can send it to me, if i recover you can have it back, i simply need it for debugging as the one someone already sent had a wipes emmc
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
sergeyouknw said:
I've got similar problem.
I have mdz-16-ab, international version, with 1st Oreo build installed (2167). Full stock, no root access, etc. Suddenly the device stopped booting properly, during boot it displays rotating Android logo for ~5 minutes following by black screen afterwards. I managed to launch recovery, did wipes and tried to flash any of the 3 available Oreo builds to the moment being written to 2 various flash drives I possess (1 gb and 16 Gb, FAT16 and FAT32 formatted accordingly). Every attempt resulted in "Failed to verify whole-file signature" error.
Looks like it could not properly read image file from the flash drive or the image itself is wrong for this model but I'm perfectly sure image is correct.
Click to expand...
Click to collapse
Sounds like you have a flaky USB thumb drive. Try formatting on a different pc and keep trying different usb drives. Current world record holder tried 8 different drives until succeeding with #9!!
Concur with bigtalker. Or a bad download. I followed a procedure that was a cross between https://www.reddit.com/r/AndroidTV/comments/9fo34b/xiaomi_mdz16ab_solution_to_downgrade_from_flaky/ and https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/:
Extracted the 2167 7zip file to a clean 2GB thumb drive (FAT32)
Booted MiBox into recovery and did a data wipe/reset
Shut down the MiBox and inserted thumb drive
Booted MiBox into recovery, again, where it automatically picked up and installed the 2167 update
Shut down the MiBox
Cleared the thumb drive, copied the 2179 .zip over to it as update.zip and restored the xiaomi_update file (from the 2167 7zip file)
Rebooted the MiBox into recovery again. It picked-up and installed the 2179 update
Booted the MiBox into Android and did a Factory Reset
Did minimal new setup configuration on boot and installed the 2396 OTA update
Done!
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
jseymour said:
Just went to update the 2nd of our two MiBox 3's. The light lights but nothing on-screen at all. It's bricked but good. I guess turning off Google Play Services wasn't enough.
Now trying to find a receipt to see if I can persuade Walmart to take it back. It's probably been too long, but it's worth a shot. I have to go back to return the now-unnecessary 2nd IR remote, anyway.
Good job, Xiaomi. You suck
I will never buy another Xiaomi product again. Ever. You could not give me a Xiaomi product.
Click to expand...
Click to collapse
Sorry to hear of your travail...
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
bigtalker said:
Sorry to hear of your travail...
Click to expand...
Click to collapse
Thanks. I'm not as annoyed as I might otherwise have been, being as I was more-or-less expecting it'd happen eventually. *shrug*
bigtalker said:
Did you update 2nd box via OTA or using manual steps as in reddit post?
What version did you start from on box #2?
Click to expand...
Click to collapse
Each of the two boxes bricked themselves, or Xiaomi bricked them for me, with absolutely no intervention from me whatsoever. Box #1 was bricked to its splash screen. That one I recovered with the aforementioned procedure. Box #2 was bricked to completely dead except its front-panel indicator.
They had both been on the same versions. I don't recall which that was at the time they were bricked. The 1st or 2nd update Xiaomi pushed out for Oreo. IIRC: 2179 created as many problems as it solved, so I didn't apply that OTA when it was available. So perhaps the one before that?
There are reports of Xiaomi MiBox 3's "bricking themselves" on every on-line forum in which I participate, BT. Some to their splash screens. Some to just dead. Just like I experienced. These all started appearing about the time 2396 became available.
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
Click to expand...
Click to collapse
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://4pda.ru/pages/go/?u=https:/...c055db0b4f8dee8d49e4b04ecf9100.zip&e=65311772
What is the AndroidTV version of the img file you posted
What is the AndroidTV version of the update.zip file you posted
Curious as to the origin of the img file. Normally such things come from the hardware vendor. Xiaomi has not been forthcoming with img files, mainly staying with flashable zip format updates
hum..
I Use USB_Burning_Tool 2.0.7 and it say Low-Power after 1' ... :'( after, crash burn...
roeer said:
hi i have an IMG for MDZ-16-AB to get unbrick
https://drive.google.com/drive/folders/1-fGnIP7iLmpHUNRPhlWyEnEVHuraDc1q?usp=sharing
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
i got brick after trying to update to version 9. and the device freeze. and now i flash this img and get out of brick. after this img burend. enter to recovery and install version 9 with this link:
https://android.googleapis.com/pack.../2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
Click to expand...
Click to collapse
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Edit: Download for latest USB Burning Tool v2.2.0:
https://mega.nz/file/Hd0CmACT#OPws8xFAPOGR6SmFJKfkVQ4SXjXpetJHmZZZ7nqkRHc
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Hitchar said:
@criscodecookies: I also tried flashing my bricked MDZ-16-AB. However, I'm also getting the low power error. With only the usb connected the device is not detected by the tool when shorting the two pads. Did you connect the power cable?
Thanks in advance
Click to expand...
Click to collapse
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
criscodecookies said:
Yes, power cable must be connected while shorting the two pads. Once USB Burning Tool sees the device you may then let go of shorting the pads but keep power connected.
Click to expand...
Click to collapse
Yeah that seems to work. The USB Burning Tool sees the device and I can start the flash. But after a minute I get the error 'low_voltage'. I've tried all my USB ports (USB2 and USB3) and also tried to use my laptop. So now I'm wondering whether my cable is good (I've soldered it myself). I've tested for continuity so the connections are good. How are the cables inside your USB cable wired?
criscodecookies said:
Thank you sooo much! You saved many once working devices from the landfill.
I got it to work following the instructions posted here:
https://forum.xda-developers.com/an...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992
Note: you will need a USB Male to Male cable (2.0 is fine) which can be found for ~$5.
Ex: https://www.amazon.com/dp/B009GUXG92/
The MDZ-16-AB is almost the same as the AA except the pins are a bit more to the right:
For the image burning tool, DO NOT ERASE ALL. Uncheck Erase bootloader and keep it to 'Normal erase', this is to keep DRM keys which allows Netflix to work.
The image linked above works flawlessly!
The image is of Oreo version 2167
Once back in recovery, I was in a recovery loop. To fix this I followed the instructions posted here:
https://www.reddit.com/r/AndroidTV/comments/97rvqg/mi_box_stuck_in_recovery_mode/e4ct7n0/
After that I was able to update to Oreo version 2562 posted above.
I then followed the same procedure to manual update to Android 9 and it succeeded.
Captured the link for MDZ-16-AB Android 9 r2926 for anyone who wants to try manual updating as well:
https://android.googleapis.com/pack.../ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
Click to expand...
Click to collapse
i've tryed to flash this oero img16-ab on my bricked mi box 3 mdz 16-ab and the usb burning tool all the time showing me error
low power with this img but when i try to flash any other rom dont showing this error only with this rom, whats the problem?