i have been trying to root my phone for days now, and im sick of it. so im gonna skip to unlocking the bootloader. i just have a question, will i receive future updates/will future updates brick my phone if i unlock the bootloader? i do not plan to flash anything of except for this ( http://forum.xda-developers.com/showthread.php?t=1043630) , just want to gain root access.
If you just want root access why not just try the zergrush root method its an easy one click tool that is for windows and it roots all the newest firmwares
Sent from my R800i using XDA App
i have been trying for several days now with that method, but my com cannot detect the phone with usb debugging on. mtp and msc work fine but does not work with usb debugging.
lckh66 said:
i have been trying for several days now with that method, but my com cannot detect the phone with usb debugging on. mtp and msc work fine but does not work with usb debugging.
Click to expand...
Click to collapse
You need to download and install the Android SDK. That comes with all the ADB drivers.
Sent from my R800i using Tapatalk
already did that, uninstalled and reinstalled. still cannot detect it when usb debugging is enabled.
lckh66 said:
already did that, uninstalled and reinstalled. still cannot detect it when usb debugging is enabled.
Click to expand...
Click to collapse
Did you install the standalone drivers on the first page of the zergrush post?
Also, in device manager , what does your phone show up as?
Sent from my R800x using Tapatalk
in device manager, when usb debugging is enabled, it shows up as SEMC HSUSB device with a exclaimation mark. using windows 7 btw. trying to update the driver does not work, windows just keeps saying that there is no driver software.
Have you got Sony Ericsson PC companion installed? because that usually installs all the drivers
yes, but regardless of it running, it still does not recognize my phone when usb debugging is enabled for both mtp and msc.
Can you flash an older firmware, then gingerbreak?
to do that, i need to have unlocked bootloader right? also, will updating from 2.3.2 gingerbreak to 2.3.4 remove root?
No you dont need an unlocked bootloader to flash a stock rom. Just search for flashtool or google wontanserver and pick what firmware you want. Flash 2.3.2 then root with gingerbreak, then over the air update all the way to 2.3.4 and you will still have root
wow, that sound great. i'll try that later. thx to all those who replied to this thread
Related
Hi All!
Just got myself a SE Arc that is charging right now. I have resisted playing with it for a good few hours.
Anyway was wondering should i unlock the bootloader and reflash? I am interested in stripping away the rubbish that slows the phone down. To do this, do i just find a firmware that has already removed the crap, or is there a way to remove stuff like timescape.
The phone currently has 2.3.3 HK firmware.
Sorry if this sort of info is located elsewhere...
You don't need to unlock your bootloader for that. You just need root access and Titanium Backup. With that, you should be able to remove the stuff which you don't want. Please refer to this link to know what is safe to remove and what's not.
http://forum.xda-developers.com/showthread.php?t=1089470
Many THanks. I was just looking at that list myself... Anyway i will give it a go. Was just wondering if there were any benefits to reflashing the firmware.
How do i get root access? Or should i already have root access?
Thanks
Bolo
I'm assuming you haven't unlocked your bootloader.
If you're already running 2.3.3, then consider flashing 2.3.2. Root it with Gingerbreak. And then update it OTA (Over The Air) to 2.3.3. Don't try this with an unlocked bootloader!
With an unlocked bootloader, you can just flash a rooted firmware onto your device. But do note that once you unlock your bootloader, you won't be able to use TrackID and also the facebook 'Like' feature on tracks as unlocking deletes the DRM files.
For all custom ROMS and kernals, you would need to unlock your bootloader. You can use Shazam as an alternative to SE's TrackID.
Hi xtacy.
Thanks for the info.
Any reason why i need to go back to 2.3.2 and then update again? Is it to give me root access?
Thanks!
xtacy! said:
I'm assuming you haven't unlocked your bootloader.
If you're already running 2.3.3, then consider flashing 2.3.2. Root it with Gingerbreak. And then update it OTA (Over The Air) to 2.3.3. Don't try this with an unlocked bootloader!
With an unlocked bootloader, you can just flash a rooted firmware onto your device. But do note that once you unlock your bootloader, you won't be able to use TrackID and also the facebook 'Like' feature on tracks as unlocking deletes the DRM files.
For all custom ROMS and kernals, you would need to unlock your bootloader. You can use Shazam as an alternative to SE's TrackID.
Click to expand...
Click to collapse
Yes, it is indeed to give you root access. Gingerbreak doesn't work on 2.3.3. The exploit that Gingerbreak used was fixed on the 2.3.3 ROM and hence the need to downgrade to 2.3.2.
Have you heard if anybody is working on root access for 2.3.3?
The exploit that Gingerbreak uses was fixed in 2.3.4 but SE implemented the fix in its 2.3.3 ROM. With a locked bootloader, I don't know of any other way.
But our resident geniuses here at XDA have released kernals which can root any ROM [Unlocked bootloader required] (I believe it was Blagus). Just browse our Development section and you'll come across various solutions.
xtacy! said:
Yes, it is indeed to give you root access. Gingerbreak doesn't work on 2.3.3. The exploit that Gingerbreak used was fixed on the 2.3.3 ROM and hence the need to downgrade to 2.3.2.
Click to expand...
Click to collapse
Hi just got another question.
I have the 2.3.3 usb connection problem. Therefore, is it worth updating from 2.3.2. to 2.3.3?
Many thanks for your help!
What exactly is the 2.3.3 USB connection problem?
2.3.3 does bring in improvements like facebook integration, better wifi stability, improved battery life etc. For these reasons, I would update to 2.3.3
xtacy! said:
What exactly is the 2.3.3 USB connection problem?
2.3.3 does bring in improvements like facebook integration, better wifi stability, improved battery life etc. For these reasons, I would update to 2.3.3
Click to expand...
Click to collapse
when connecting to the pc, the mtp device driver fails to load properly, meaning you can't connect to the pc. i hve tried both mtp and msc modes. I think this is a problem with 2.3.3 and not the arc...
Try reinstalling SEUS and PC Companion. Might solve your problem.
bolochan said:
when connecting to the pc, the mtp device driver fails to load properly, meaning you can't connect to the pc. i hve tried both mtp and msc modes. I think this is a problem with 2.3.3 and not the arc...
Click to expand...
Click to collapse
Do you have the prompt window on your phone "Install" "Skip" when you are connecting the phone to the PC? (If not go to Settings-SonyEricsson-Connectivity- Install PC Companion)
Are you using Windows 7?
Have you formated your SD card via Windows Explorer (right click - format...)?
For proper connecting you need Media Transfer mode (MTP).
Normaly, when you have selected MTP and you connect your phone to the PC and you press the "Install" option on the phone, Windows should locate the MTU driver and install it.
I had same problem and I found that my phone was in MSC mode.
Btw I tried reinstaling the PC companion and SEUS it didnt help.
I have searched for the driver to download it from internet but no luck.
The whole point is that I believe the driver is located somewhere in the phone and when you connect it windows should get it from there.
Ive finally flashed the .62 FW on my phone!!!!! After 3 days, i finally flashed it although that wasnt my main aim. My main aim was to get the JokaWild v3 ROM on my phone.
My phone is r800i. Now in order to get the ROM on my phone, I need CWM installed, which requires root obviously. Now, when I try to root my phone using the zergrush exploit via superoneclick, the application freezes at step 7. Ive also tried gingerbreak but still doesnt work....
Is it because, after flashing the .62 FW, flashtool told me to put the phone in debugging mode and enable non-market apps, although I did it, when i connected the phone back, it gave me an error...
I've did my research and it seems that .62 can't be rooted... So is there any way of getting cwm on my phone in order to flash the ROM?
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
rbox said:
I'm going to release recovery for both locked and unlocked Fire TV 1. The big difference being if you brick an unlocked unit, you can boot straight to recovery and fix it. If you brick a locked one, you're pretty much hosed.
Click to expand...
Click to collapse
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
zroice said:
thx for the reply.
Can unlocked bootloader be kept unlocked even with update to 5.0.5? Or does the new version require the new not unlockable bootloader?
Only way to unlock would be to hardware root the one I have or is there any other way? (with the 51.1.4.0 software)
Click to expand...
Click to collapse
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
rbox said:
Yes. If it's unlocked it will stay unlocked.
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
but amazon is not giving those out isnt it? =)
zroice said:
but amazon is not giving those out isnt it? =)
Click to expand...
Click to collapse
The tablet that uses that for their unlock has a program to generate the unlock codes. It's similar to my unlock, but it runs on your computer to generate the code versus my unlock that runs on the device.
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
Yes, mine requires root.
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
zroice said:
but to run yours the thing has to be rooted 1st correct? So basically if I really want an unlocked bootloader i better do the hardware root ..? (sorry if those questions are noobish hehe)
Click to expand...
Click to collapse
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
BreakingDroid said:
@rbox, has anything been learned about a custom recovery for the fire sticks now that we have root access?
Click to expand...
Click to collapse
I'm trying to get recovery for FireTV1 working, before I work on the stick. The problem is if I brick the stick, it's game over. I'm trying to find all the ways that I can brick it while working on the FireTV1, so I don't do it with the stick.
mjbxx said:
No. Not a hardware root. Just wait on the @rbox prerooted software rom for the Fire TV/Stick. And shortly after that AFTVnews will provide an extensive how to root guide. Just be patient and you will eventually have a rooted/unlocked Fire TV/Stick.
Click to expand...
Click to collapse
hmmm but didnt I read that once you update the bootloader unlock is no longer possible?
I got the FireTV with old software still which accoding to atfnews is not rootable but bootloader unlockable.
I read that once you update that the eFuse thing will become active and prevent unlock attempts.
All in all I just need to know if I should update the 1st Gen from the current " 51.1.4.0" build to the latest one to get root, disable OTA etc and still be able to unlock bootloader and boot directly to a recovery or if it would needed to be hardware rooted in order to do that. (to prevent the bootloader update.. which activates the efuse)
zroice said:
Hey all,
I own a FireTV 1st Gen with Software Version 51.1.4.0 which is not rootable but can be bootloader unlocked (if it was rooted).
This thing was never actually used because I didnt want to risk it beeing updated and loosing the ability to root and/or bootloader unlock... (this Software is the one with which it was shipped..)
I also own a FireTV Stick which is upgraded to 5.0.5 and rooted with kingroot.
I need some advice what to do with the 1st gen FireTV - I could update it to 5.0.5 and root with kingroot, but then it would also update the bootloader to be not unlockable, right?!
I also have that eMMC Adapter but couldnt bring myself to attempt to do the soldering root method - but actually that would be best or? Then I could unlock the bootloader, and install custom recovery..
Or might there become a way available to have custom recovery on the 5.0.5 version without prior bootloader unlock?
Halp please!
Click to expand...
Click to collapse
rbox said:
I believe there is a way to enter the unlock code through fastboot. One of the Amazon tablet devices uses that for their unlock. I don't remember which device it is though.
Click to expand...
Click to collapse
rbox is right. You can unlock the bootloader of a 1st-gen Fire TV using only an A-to-A usb cable. Although I'm not sure if it works on 51.1.4.0. I think it requires 51.1.0.2 or older.
I was going to write a guide, but the python script to generate the unlock code/file has been taken down, and it was really only useful for those who bricked with a locked bootloader, so I didn't try to find the script. Pretty sure the script was called cublock.py from here.
Assuming you can get ahold of the script, and it works on your software version, you would connect an A-to-A usb cable and reboot into fastboot by connecting via ADB and running
Code:
adb reboot fastboot
then run
Code:
fastboot devices
to ensure you're in fastboot and connected, then run
Code:
fastboot oem emmc-info
to get a code that you need for the python script. The code is in the form
Code:
(bootloader) 0x12345678
and you use the python script to generate the unlock code like this
Code:
./cublock.py 56 12345678
That will generate an unlock file which you then use as follows:
Code:
fastboot flash unlock /path/to/file.unlock
After that, you can use fastboot to flash custom recovery if you'd like. Instructions are at the bottom of this guide under the "Repair Recovery with Fastboot Mode" section. I've attached a screenshot of the process from my notes for the unwritten guide, back when I tried it.
ill try that - thanks very much
what driver to use for fastboot mode?
zroice said:
what driver to use for fastboot mode?
Click to expand...
Click to collapse
I'm not sure which Windows drivers to use. My Mac didn't need any.
This should help concerning Windows ADB/Fastboot drivers:
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Tools.zip package from this post includes the cublock.py file
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
zroice said:
ARGH that sob Fire TV.. Cannot root the damn thing in current stage with Kingroot and cant get my PC(s) to connect to fastboot.
My flashing PC which has all sorts of drivers installed only detects it as ADB device - "fastboot devices" doesnt work. And my Laptop does recognize it as "Fire TV" with no drivers installed in fastboot mode.
I need help to get that damn fastboot goin please. On the PC I forced driver install of some "universal" fastboot drivers but it still wont show up in fastboot devices (to get the info needed for the python script..). No idea why the pc thinks its an adb device when connected in fastboot mode.. (adb doesnt work in that stage either...)
Downgrading & Bootloader unlocking after updating to 5.0.5 probably wont work, right? Because the bootloader cannot be downgraded I guess..
Click to expand...
Click to collapse
P.S: I could try to boot linux from USB if that helps - but that probably also needs some sort of drivers doesnt it?
Hi all,
Running into what I think is a firmware signing issue with a T707A. Yes, I said T707A, not T707V. I've had the device for about 48 hours now, and can't seem to get a non-carrier branded firmware on it. What confuses me is that the T707A is an AT&T device, but the error I'm getting is:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
That tells me that using the dd method of twrp installation at least wrote correctly, and that the device is rooted. dd was run via adb shell. Instructions were taken from here --> twrp / devices / samsunggalaxytabs84lte.html
I've also tried Odin (3.12.3 and 3.10.6) on 3 different machines (Win 8.1, Vista, XP - Vista and XP being clean loads with good drivers) and am using the OEM USB cable. Device is charged to about 95% or so.
I can re-flash back to 4.2.2 via Odin using the following firmware (T707AUCU1ANH9_2650391_REV00 - BL / AP / CP / CSC).
And KingoRoot has been working fine to root when I have to recover.
I have access to recovery mode (power + home + vol down) as well.
I'm not sure where to go here, and I'm trying not to leave useful information out. Input is appreciated, because my Frankentab (Nexus 7 2013 LTE) is now dead.
The bootloader is locked, you can't flash anything.
ashyx said:
The bootloader is locked, you can't flash anything.
Click to expand...
Click to collapse
That would make sense, yeah. What's a reliable way to unlock it? SuperSU complains about Knox being enabled, and fails.
Chubblez said:
That would make sense, yeah. What's a reliable way to unlock it? SuperSU complains about Knox being enabled, and fails.
Click to expand...
Click to collapse
You can't unlock bootloader, but might be able to root if that is what you are asking. I have both T800 & T707A, I have tried the instructions below on T707A with success....I haven't used it on T800 yet, but assume it is that same. I didn't start from a fresh install, I just installed Kingroot and ran the removeking scripts.
[ROOT] SM-T707A - Lollipop with SuperSu - Xposed & Debloated - Part II
http://forum.xda-developers.com/galaxy-tab-s/general/root-sm-t707a-lollipop-supersu-xposed-t3468488
Hello, I have a s6 sm-g920p sprint and it can't connected to pc any more, all its configuration in development options are activated, I was using a app, its names is sim_unlock_1 and I believe that I touched badly a configuration, I lose all my information and i blocked my phone, factory reset, it was free and rooted.
In this moment it is blocked, no root and i can't connected to no one PC for unlock of sprint or rooted it, I thought that the problem with usb debugging is a software trouble. I thought that I need rooting it and search de same apk and try to fix it, but How Can I root it without wire??, It is nougat and binary 4, if you can help me please. Thanks and sorry for my english