Ladies and gentlemen, I would like to present to you all a formal guide to venture into one of the best smartphones in the market, the underdog to the other mass marketers, the Sony Xperia Z3v for Verizon!
*Please note I am not responsible for any bricking, destruction of your device, alien invasions, or any other problems. It is up to the user's choice to seek out what is done on your device on your own terms.*
This is the method I would recommend that's much quicker and efficient is Kingroot. I know there were some previous controversy about what could be behind Kingroot, but from what I will show here is using Kingroot as leverage to gain access quickly into my prerooted Lollipop firmware that can stand alone after removing Kingroot afterwards.
1. Have the Z3v in your possession.
2. Google "Kingroot" and download for Android and run the rooting process there.
3. Download "Superuser" from the Play Store to have the binary to run root fully. (Optional just in case the next step doesn't work)
4. Install XZDualRecovery (grab the flashinstaller for the Xperia Z3) to install TWRP from here: http://nut.xperia-files.com/path/XZ...40vagg0tpcrnm1vlnt63je5&randomizer=_ehkq575vz
(The link is subject to change, so if that happens, navigate through here: http://nut.xperia-files.com/)
5. Download my new 5.1.1 prerooted Lollipop zip from my thread here: http://forum.xda-developers.com/z3/...08-prerooted-lollipop-5-1-1-23-4-b-0-t3338967
6. Access TWRP by opening an app called NDR Utils in your App Drawer
7. Flash my zip through the install button and now you'll be on the latest prerooted stock build of Lollipop with a few mods.
Optional Step 8. Uninstall any traces of Kingroot from your phone and you're good to go. This step may already be done for you after you flash the prerooted because reportedly there were already no traces left behind. Enjoy!
Thanks to the following people:
@zxz0O0, for achieving root for our Z3v
@jal3223, for helping me as much as you can to guide me through myself
@[NUT], for the custom recovery to install onto our Xperia devices
Please hit thanks for the all in one guide to freedom!
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Mountainfisher said:
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Click to expand...
Click to collapse
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
GigaSPX said:
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
Click to expand...
Click to collapse
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Oh No, I vowed to stop messing with my phones....
jal3223 said:
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Click to expand...
Click to collapse
Personally, I'm fine without doing custom ROMs. I like how Sony's UI works as it is and I prefer it that way than going full AOSP like any other Nexus phone. I just like to buy what came with the package as is intended.
Bobby Buggs said:
Oh No, I vowed to stop messing with my phones....
Click to expand...
Click to collapse
This is well worth to do. I installed Xposed, and unlocked some awesome stuff. Such as using Superior Auto mode with 15 mp right off the start or 20.7 MP. Greater the details, amazing functions made.
Oh and also, I will now proceed to upload the flashable zip of the latest FW being prerooted. Just so there's some better things to deal with.
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Mountainfisher said:
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Click to expand...
Click to collapse
This guy said it took him 10 times so I am going to keep trying till it works!
sthrnsprtsmn said:
I was getting the same errors. I had to factory reset the phone multiple times and redo the steps. On about the 10th time, it took. I skipped the phone set up steps, and kept a root checker apk on my sd card to speed it up. Also, I unchecked the verify apps over USB. I didn't see that mentioned anywhere.
Time to send my donation. Thank you very much @zxz0O0
Click to expand...
Click to collapse
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
JediDru said:
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
Click to expand...
Click to collapse
Your C:/flashtool/firmware folder should be empty. Place the firmware you want to use in /USERNAME/.flashtool/firmware
make sure you uninstall all java and re install fresh!! that was what was holding me up
Someone should do a youtube of this process live
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Bobby Buggs said:
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Click to expand...
Click to collapse
You completely skipped steps 1 and 2 because you're on the latest build. Step 6 is following the instructions that are listed within the exploit.bat.
You won't be reflashing the latest until you've followed through to the new list of steps that occurs after 9.
Giga, sent you a Pm
---------- Post added at 09:31 AM ---------- Previous post was at 09:20 AM ----------
Call me a idiot but I dont see any instructions, I ran the exploit file and my screen shows daemon started successfully but nothing else
ROOT Z3V
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Great write up!
Thanks for the time and effort you put on rooting our abandoned Z3v.
Really look forward to flashing the Pre-rooted firmware that you're about to made
xratablancax said:
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
Click to expand...
Click to collapse
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
What line of code
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
If you look at the link I provided, that gives your a different set of root files, one that the Exploit runs and right after root runs automatically.
VERY IMPORTANT... YOU NEED TO FLASH YOUR DEVICE TO STOCK ROM, YOUR DEVICE NEEDS TO BE IN ROM, 23.0.E.0.376, BACKUP DEVICE, FLASH THEN ROOT THEN OTA UPDATE
Related
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
What we need:
1. Nexus One with FRF72
2. The files I provide
3. Android SDK
4. Transcend Class 6 4gig(High recommend but not a must)
5. A brain!!!
Click to expand...
Click to collapse
YOU MUST FOLLOW ALL STEPS, OTHERWISE YOU LOSE!
Step 0:
- Install the SDK
- Make sure there is no "update.zip" in SD card
- Connect your phone with the USB
- Extract all files I provided to your <SDK>/tools
Step 1:
Enable Debugging in Setting->Development
Then, shut down your phone
Step 2:
Booting into bootloader by holding vol- and press Power
Use vol- button to highlight "Recovery"
Step 3:
Open CMD, and cd to the <SDK>/tools
Run "loop"
Step 4:
Press Power to enter Recovery now, you will see the triangle and <!>
Hold Power and vol+ to show the menu
Step 4a:
If your CMD shows you the devices is in recovery, press control + c to stop the "loop"
Step 4b:
If there is nothing, reboot your phone and repeat step 2-4 until it shows up.
(This is 99% caused by the sd card, faster card make it easier to show up)
Step 5:
Select "Apply update.zip", and it will show failed(IMPORTANT!!!!)
Step 6:
Run "adb push ota.zip /sdcard/update.zip"
Run "adb push busybox /sdcard/busybox"
Step 7:
Type but not run "adb push root.zip /sdcard/update.zip"
Step 8:
Select "Apply update.zip" again and run the step-7-code half a second later.
IF IT SHOWS ERROR STATUS 6, DOWNLOAD THE NEW ZIP I UPLOADED
Step 8a:
If it works, it will print ""Nexus One Rooting modified by Booker from Hong Kong"
Step 8b:
If it failed, repeat step 6-8
Step 9:
Finished the process, you can now immediately flash_image.
Step 10:
If you do flash a new recovery image, you may need to remove "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p"
This prevent the system automatically re-flash your recovery image to the stock one.
Click to expand...
Click to collapse
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
requirements. for this method
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
actuallly you can get the official version, put it on your sd card and install it without being rooted. That is what they want you to do.
You see those of us who were rooted had to wait for a repacked version of the FRF72 update or we had to revert to stock with a stock recovery to get it to install. So sir, this is a valid method and you will keep your warranty intact!
O_O this is a really big deal NO?
anangphatak said:
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
Click to expand...
Click to collapse
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
madj42 said:
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
Click to expand...
Click to collapse
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
artcarney said:
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
Click to expand...
Click to collapse
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
jroid said:
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Click to expand...
Click to collapse
Really? I have been looking for this file for EPE54B for days!
all i have found was FRF50 from EPE27, FRF72 from FRF50, FRF83 from FRF50...
can you please advise us where we could find the one for EPE54B please?
Zapo said:
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
Click to expand...
Click to collapse
i still haven't got a confirmation from anyone that updating radio requires unlocked bootloader....
but i understand everyone's concern as flashing radio is pretty much the only way to brick you phone therefore no one has the guts to be the 1st one flashing Froyo and the new radio with a rooted phone w/o an unlocked bootloader, right?
Rayman0625 said:
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
Click to expand...
Click to collapse
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
kaiser_tytnii said:
can you please advise us where we could find the one for EPE54B please?
Click to expand...
Click to collapse
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
christiankk said:
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
Click to expand...
Click to collapse
my apologizes, i did not see any Froyo ROM there.
madj42 said:
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
Click to expand...
Click to collapse
if you stay with stock recovery and ROM, you will receive OTA from Google.
You can still flash Stock ROM with Custom Recovery but will not be able to install OTA from Google.
hope this help.
Booker-T said:
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
Click to expand...
Click to collapse
proud of you Konger!
Is there any way this can work on FRF83?
or
Is there a way to revert back to FRF72?
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
M9x3mos said:
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
Click to expand...
Click to collapse
Do you think you could give me a link to the passimg.zip that I can use without having to unlock the bootloader? I've been searching for hours.
PS: there is no busybox in the "Nexus_One_Full_Root.zip" from the original post.
Just a quick advice for everybody.... If someone (like me) is still stuck with the 2.1 Update 1, before update to 2.2 FRF52 test on your phone the point between 2 and 4.b. Once you will have your phone recognized by ADB then you can update to 2.2 FRF52.
For now my 4 microSD (1 * Class 6 Sandisk / 1 * Class 4 Kingston / 1 * Class 6 Transcend and 1 * Class 2 Samsung) doesn't work at all....
Hope this help
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Once you select Option 1, you need to go back to the main windows to uncheck one box (F something) and then click start before it does the rooting. I missed it yesterday also and just keep waiting until I realized there was a step I didn't do.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Help!
I am having the same problem and my phone is sitting there with a large android icon and message reading "Downloading.. Do not turn off target!!" I am afraid to disconnect the phone from the USB. What should I do?
ThugosaurusRex said:
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Same here, Verizon Samsung g s4.
I followed the instructions: unchecked the F. reset box, and selected tar and clicked start. The "<OSM> All threads completed. (succeed 0 / failed 0) line showed up, and nothing else.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
whichonespink73 said:
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
Click to expand...
Click to collapse
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
dabs delicious said:
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
Click to expand...
Click to collapse
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
goldberg96 said:
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
Click to expand...
Click to collapse
You're talking about the popup window on your phone, right? Because It pops up for me too, and I click "confirm" each time, but to no avail
Does anyone else have any suggestions?
Question about using the 3 in 1 tool
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Super Noob
Hello everyone this is my very first post, I am looking to root my verizon s4 using the one tool kit i dont believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. i didnt want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
missjamie said:
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Click to expand...
Click to collapse
Root just allows you to hack the software on your phone, and the "unlock" refers to the bootloader. It does not unlock the phone for other carriers; this is done (from what I understand) by dialing a specific set of codes, generally provided to you by the original carrier of the phone if you have an account in good standing with them and you tell them you plan on travelling out of the country and need to use GSM. I have never needed to do this and as such only have a minor theoretical knowledge of the subject; I would appreciate it if somebody with more knowledge on this would confirm or deny my suspicion that you are better off trading the phone for an AT&T/T-Mobile one that actually was meant for GSM, or otherwise obtaining one.
JNava420 said:
Hello everyone this is my very first post, I am looking to root my Verizon s4 using the one tool kit i don't believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. I didn't want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock Verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
Click to expand...
Click to collapse
This is the original bootloader; not the stock firmware. You need to flash this after you successfully root, start the phone, start SuperSU, and update the SU binary.
The full stock firmware is rather large and available here:
http://forum.xda-developers.com/showthread.php?t=2289325
might not know as much as i thought
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
If you need assistance. Pm me. If I sm available ill help you.
JNava420 said:
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
Click to expand...
Click to collapse
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
OverkillSD said:
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
Click to expand...
Click to collapse
Well said. Only correction is the bootloader still remains locked. The recoveries included are loki patched. This bypasses the bootloader. All roms and kernels are loki patched so flashing them is safe. This is as close as we're gonna get to an unlocked bootloader for now.
Ah. I was under the impression the bootloader was unlocked. Thanks for the info.
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
dabs delicious said:
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
Click to expand...
Click to collapse
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
chrisxstyle1182 said:
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
Click to expand...
Click to collapse
Could be a couple of things first make sure your using the cable that came with your phone. Try switching usb ports. Alsi try rebooting your pc
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
AronR said:
Hi Guys
I recently bought a Tablet Z and am currently running the latest official 10.4.b.0.109 firmware for Wifi models.
I am aware that there are guides for rooting the firmware version before this as well as upgrading a rooted device to the latest version but I can't seem to find a guide for rooting my current official firmware from scratch.
I'd like to be able to do this so I can run 'root-only' apps and be able to turn off the screen whilst using an MHL adapter.
Any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I did this a week ago, and what a carry on I had, I thought i bust my tablet
I downgraded to .370 version using official firmware with flashtool, then I rooted using DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit (this is the easy part)
Then I used .109 version firmware (stripped ftf and flashable zip) - this is where it went wrong as I got into a boot loop
http://forum.xda-developers.com/showthread.php?t=2671276
I used both DE versions (German) for the flash/install - still works on UK tablet
I think there is a specific order to install busybox before or after dual recovery - this might be where it went wrong for me.
I also used an older version of dual recovery, (TabZ-lockeddualrecovery2.7.94-BETA.installer) and have yet to flash to the latest version
Sorry this is a bit muddled.
I just got my tab a couple days ago I guess I screwed up upgrading from 370 to 109. Following along closely to this thread
Sent from my SGP311 using Tapatalk
This is a guide that I wrote to enable root on Android version 4.3, build number 10.4.1.B.0.109 for SGP311. Follow at your own risk. I will not be responsible for damage to your Xperia Tablet Z! I am going by memory and XDA posts I have re-read.
Please read this first then follow the steps!!
1. Firstly you need to ensure you have the drivers installed for your tablet, so you could install Sony PC Companion http://www.sonymobile.com/gb/tools/pc-companion/
2. On your tablet make sure that Developer options is enabled (if not, press About tablet in the tablet settings menu several times), USB debugging is ticked and Verify apps over USB. Also turn on Unknown sources in Security settings
3. Assuming that the tablet is running version 10.4.1.B.0.109 you need to downgrade to version.370
4. Download and install Flashtool by @Androxyde http://www.flashtool.net/download.php - install this to your C: drive
5. Download the official .370 (I used SGP311_10.1.C.0.370 DE_Unbranded.ftf) firmware from here http://forum.xda-developers.com/showthread.php?t=2402863 thanks to @DevMark. This file should be placed inside the firmwares folder of Flashtool and thanks to @ donedos for his initial suggestion
6. Download the rooting kit from http://forum.xda-developers.com/showthread.php?t=2333566. Thanks to @DooMLoRD
7. It is suggested that a backup is carried out on the tablet as this flash/root will wipe the data from it – I never did this, as I was quite happy to install apps/.apk again, and I had a lot of crap on my tablet anyway
8. Open up Flashtool, power off the tablet, and plug the usb cable into the tablet.
9. With the tablet still turned off press the volume down button, and plug the usb cable into your PC, this should get your tablet into flash mode
10. There is a lightning bolt symbol on top left corner of Flashtool, click this, and two options should pop up. I think you click the top one; if so, you will be prompted to locate the .ftf file, select the .370 file. If this file is not visible, you probably need to select the second option that popped up!
11. The tablet should be flashing now, and takes a few minutes or so. Instructions will appear in Flashtool to unplug and power on your device.
12. It will take a while for your tablet to turn back on; when it does you might need to carry out the actions again in 2. above. Just make sure you are running firmware .370 now instead of .109
13. Now connect you tablet again to USB, device drivers might install again. Open up/extract DooMLoRD_Easy-Rooting-Toolkit_v17 and click the runme_win.bat file and follow the instructions – your tablet should now be rooted. Check for the Super SU app in your app list, or if it’s not there install from Play Store.
14. Download the file Xperia Tablet Z (SGP311) 10.4.1.B.0.109 VMo De from here http://forum.xda-developers.com/showthread.php?t=2671276, thanks goes to @bernddi . Extract the file so there are two files (SGP311_10.4.1.B.0.109_VMo De_stripped.ftf and SGP311_10.4.1.B.0.109_VMo De.zip)
15. Download and use this file http://www.winmd5.com/ to verify the md5 checksum matches the .109 files you downloaded.
16. If everything is okay, place the large zip file onto the root of your external memory card, and the .ftf file into the firmwares folder of Flashtool (later on don’t mix this file up with the .370 file)
17. Download the correct version of XZDualRecovery file for your tablet, – thanks to @[NUT]. I first tried the most recent version, but had problems with flash and root, so then I tried the older version TabZ-lockeddualrecovery2.7.86-BETA.installer. Files are linked from here http://forum.xda-developers.com/showthread.php?t=2261606.
18. Download and Install BusyBox from the Playstore, and run the app, then install again to your Tablet (using default options I believe) – this install failed first time for me, if same happends with you try again until it works
19. Connect your .370 rooted tablet to your PC, and run the DualRecovery file by clicking on install.bat – this will install the recovery to your tablet
20. Your tablet should power back on, or you’ll need to turn it on yourself. Make sure stuff works fine, you might need to carry out No. 2 again, I’m not sure
21. You should also have a file called NDR Utils on your tablet, if not install from the PlayStore, and run this. The option to boot into Philz Touch Recovery should be visible, select this option and reboot. You can reboot by pressing power up, while the tablet is turning on, but I have problems getting this to work. NDR makes it much easier
This is where it might get risky. It appears that the older version of DualRecovery does not have the option to verify the md5 checksum, but if the file winmd5free said the numbers match you should be okay
22. In recovery you need to select Install Zip, then select install zip from storage/sdcard1, then go to the zip file, and press it. The flashing of version .109 should begin – it takes a while
23. After the flash you must power off the device, DO NOT reboot
I believe this is where I got into a boot loop, and I am not certain how I got out of it. This link might help http://forum.xda-developers.com/showthread.php?t=2703882. Thanks to @Cat McGowan. When I finally got out of the boot loop, I started all over again from step No.8!
24. Open up Flashtool again, and flash the stripped ftf file like you did in No. 9 and No. 10
25. Follow the instructions to disconnect and power on your tablet, you should now have version .109 and still be rooted after the initial setting up of the tablet.
Please let this work!
If there is anyone reading this that spots an error or omission please post it
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
cirovi said:
grat guide, Aid777, thanks.
I had already done exactly as you explain but I did not delete anything when I did the downgrade and I found everything working.
Now I'm still stuck with the firmware because I want to install the correct localization of the 109 version (I downloaded the ftf from Sony) and I'm trying to figure out how to do the zip and ftf whit this...
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
Some root apps and recovery need it.
Sent from my SGP311 using Tapatalk
cirovi said:
But i'v a question..what is the purpose of installing busybox?
Click to expand...
Click to collapse
actually it is already integrated in recovery package (/xbin/busybox), so there is no need to install it manually.
Well my tab went tits up a little while back, and I followed my guide and it worked
worked perfect for me... thank you very much
Help Needed
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
CentinelX said:
Hi Guys,
I followed Aid777's instructions to the dot. Unfortunately im now stuck in the "Boot loop". It keeps showing SONY, and then restarts, and over.
Please help me to recover my tablet. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Ok I managed to get out and install 370 again. But where did I go wrong?
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
white5pirit said:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Mention 'EveryThing' about your phone. You can Take a screenshot of 'About Phone' and post it here.
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
white5pirit said:
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
Click to expand...
Click to collapse
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
hitman-xda said:
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
Click to expand...
Click to collapse
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
white5pirit said:
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
Click to expand...
Click to collapse
You could just press the 'thumbs up' instead writing 'thanks' everytime.
Well, why do you want to change the permissions of the folders? You could mess-up your device if you change permissions for the root folders.
The problem looks strange. If you have rooted successfully and GRANTED permissions for ES file explorer through SuperUser, you should not get any problem changing permissions. Check in SuperUser app that you see ES file explorer.
Also try using other explorer app. I use 'Solid Explorer' and its great.
If you have temporarily rooted your device as I mentioned in above post, try using TowelRoot app for rooting your device permanently and manually download SuperSU.
If you want to use CyanogenMod (it'll be pre-rooted) you need to carry below steps;
1. Unlock your Bootloader
(Wipes everything)
2. Install recovery.
3. Take stock ROM backup.
4. Flash ROM.zip
5. Flash GApps (optional)
6. Wipe cache+dalvic+factory reset
7. Reboot
Regards,
hitman-xda
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
white5pirit said:
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
Click to expand...
Click to collapse
If your bootloader status says
'unlock bootloader allowed = NO'
Then you can't flash anything on your phone. Almost every ROM needs an unlocked bootloader. There will be some ROMs that can be flashed over locked bootloader but they will be stock based.
EDIT: You have a good Luck, you can flash recovery on Locked bootloader
http://forum.xda-developers.com/xperia-m2/development/d2303-clockworkmod-6-0-4-6-t3011821
If you flash recovery successfully, that means you can flash ROM
Check below link for ROMs Available;
http://forum.xda-developers.com/xperia-m2/development
Regards,
hitman-xda
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
white5pirit said:
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
Click to expand...
Click to collapse
It can be a drivers issue. Install PC companion and connect your phone, let PCC install essential drivers and after that follow the same steps for installing recovery.
If you post any screenshot, that would be better.
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
white5pirit said:
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
Click to expand...
Click to collapse
Yup! Everything looks good. Just try to enter into recovery before downloading CM.
1.Switch off your phone and wait for 10 sec
2. switch on
3. When you see LED, try pressing either of vol buttons.
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
es0tericcha0s said:
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
Click to expand...
Click to collapse
Yeah you are right! Purely CM doesn't work on locked bootloader. But there must be any ROM available that is based on CM or even other ROMs that has some CM features.
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
es0tericcha0s said:
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
Click to expand...
Click to collapse
Z4 experience looks great ;
http://forum.xda-developers.com/xperia-m2/development/rom-z4-experience-locked-unlocked-bl-t3079811
Your xposed idea is great. Plus there must be GravityBox