Related
hi, i wanna install a custom rom, but i have no idea how to do it at all. i do not understand most terms used in the guide. so, can someone give me a step-by-step guide on how to install a custom rom? i've tried usin rom manager to install custom rom from SD card, howvere, it always reboots and i do not get the custom rom i want. the rom im planning to install is megatron, and im using windows vista 32 bit. i dunno if it helps. please help me
helpneeded said:
hi, i wanna install a custom rom, but i have no idea how to do it at all. i do not understand most terms used in the guide. so, can someone give me a step-by-step guide on how to install a custom rom? i've tried usin rom manager to install custom rom from SD card, howvere, it always reboots and i do not get the custom rom i want. the rom im planning to install is megatron, and im using windows vista 32 bit. i dunno if it helps. please help me
Click to expand...
Click to collapse
Ive had this trouble first post your phone model and also if your phone is running a custom recovery or is rooted.
BTW this post is gonna get moved, it is in the wrong section.
its an LG P500 and its rooted
helpneeded said:
its an LG P500 and its rooted
Click to expand...
Click to collapse
can you install custom recovery?
this is new but use this. http://forum.xda-developers.com/showthread.php?t=971245
all the data in my phone are gone. is there still a need for custom recovery? and what do i do after custom recovery?
all the info you need is in this thread including custom recovery. After the custom recovery is done you shall beableto try out any of the ROMs listed there. follow the instructions to the letter.
http://forum.xda-developers.com/showthread.php?t=901247
oh, the key combo to access your custom rom(once it is done) is Home+Volume Down+Power Button It even gives you the option to connect in usb mode so you can put the ROM you want and then disable usb mode and go back to main menu then choose flash from zip.
Omnichron said:
all the info you need is in this thread including custom recovery. After the custom recovery is done you shall beableto try out any of the ROMs listed there. follow the instructions to the letter.
http://forum.xda-developers.com/showthread.php?t=901247
Click to expand...
Click to collapse
i've tried reading all the guides. the problem is, i don't understand lots of things for example, partition the SD card.
1.Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
i understand the (swap: 0, ext: 512) part, but not the rest. sorry. im a beginner at these
all those options are available to you in the custom recovery. choose partition card.
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Omnichron said:
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Click to expand...
Click to collapse
i a problem using SDK on my pc. can i use the rom manager app on my phone and flash clockworkMod recovery on it?
Edit: i managed to go to a page that's similar to that of te screen shot. how ever, it only moves up and down with the volume button. nothing to execute and commands. home page brings it t a page wit a picture of a droid and an exclamation mark in a triangle.
Omnichron said:
you will need to download Android SDK from this site
http://developer.android.com/sdk/index.html
Install it then connect you phone in USB Debugging mode. It is under Settings->Applications. Bring up a comand prompt in windows and type adb shell then su Root your phone with this app first:
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
here's a screenshot of what the custom recovery should look like:
Click to expand...
Click to collapse
UPDATE: new sdk does not contain usb drivers/adb
adb is available here ..just unzip it to the sdk folder
http://megaupload.com/?d=RTEY0Q97
sarfaraz1989 said:
UPDATE: new sdk does not contain usb drivers/adb
adb is available here ..just unzip it to the sdk folder
http://megaupload.com/?d=RTEY0Q97
Click to expand...
Click to collapse
sorry to ask,what's adb
Now you have to download a rom of your choice and copy to SD card root and flash
Sent from my LG-P500 using XDA App
taha198 said:
Now you have to download a rom of your choice and copy to SD card root and flash
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
i've tried puttng a rom in .zip file in my SD card, then use clockworkMod rom manager to flash it. it just brings me back to the original rom. am i doing the right thing?
helpneeded said:
i've tried puttng a rom in .zip file in my SD card, then use clockworkMod rom manager to flash it. it just brings me back to the original rom. am i doing the right thing?
Click to expand...
Click to collapse
Did you wipe data/cache/android_secure/ and stuff.
johno168 said:
Did you wipe data/cache/android_secure/ and stuff.
Click to expand...
Click to collapse
ou teach me how to do that?
helpneeded said:
ou teach me how to do that?
Click to expand...
Click to collapse
do you have clock work mod recovery installed? if so, reboot into recovery. then you'll see it,.
johno168 said:
do you have clock work mod recovery installed? if so, reboot into recovery. then you'll see it,.
Click to expand...
Click to collapse
they told me toconfirm my phone model. cant find my phone model anywhere
helpneeded said:
they told me toconfirm my phone model. cant find my phone model anywhere
Click to expand...
Click to collapse
Settings, then scroll right down to the bottom "about phone" then what is the part that says "model number"
I am having trouble finding how do this ..i am not even sure if its been achieved ..hope you guys have come up with something !! (Or i cud flash2.2 again and then install custom recovery and then flash 2.3 back but i dont want to go through all taht trouble )
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf
then use superoneclick (psneuter)
This is my problem these days.
There is no root application for original rom 2.3.3
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
abccccc said:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf
then use superoneclick (psneuter)
Click to expand...
Click to collapse
Frozen while running psneuter.
(superone click 1.9.5)
doktornotor said:
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
Click to expand...
Click to collapse
Thanks mate.
Works great. Its automatically rooted and custom recovery. Should I install superuser too?
optimusblack said:
Thanks mate.
Works great. Its automatically rooted and custom recovery. Should I install superuser too?
Click to expand...
Click to collapse
LOL, yeah, you definitely need that. Flash this from recovery. Once done, grab Busybox Installer from market and install busybox.
I updated my HTC EVO. And now have 2.3.3 but its not rooted anymore I want to root my phone please help me. SMH
Sent from my PC36100 using XDA App
uninvited03 said:
I updated my HTC EVO. And now have 2.3.3 but its not rooted anymore I want to root my phone please help me. SMH
Click to expand...
Click to collapse
Wrong section of the forum, dude... This one is for LG Optimus One.
doktornotor said:
Download the attached ZIP and flash the recovery via LGMDP. (CWM 3.1.0.0 included, if you want something else, replace it with whatever you want.)
- Unzip, run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job.
Click to expand...
Click to collapse
I followed the steps.. But ,it is still un-rooted..
clawsright said:
I followed the steps.. But ,it is still un-rooted..
Click to expand...
Click to collapse
Of course... It is not supposed to root your phone at all!!! It flashes custom recovery so that you could flash a rooted ROM from there, or flash the superuser ZIP (see my howto)
People, really - please think about what you are doing.
optimusblack said:
Frozen while running psneuter.
(superone click 1.9.5)
Click to expand...
Click to collapse
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
I don't know this will work or not. But if it will work the cheers to you boy.
g0mezz said:
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
Click to expand...
Click to collapse
After step 5 i forgot to write connect the phone in USB debugging, and when you put the first command adb devices is should find your device.
@sweetbinodray: this method works 100%, i told you i tested it.
it's worked man
neoonix78 said:
it's worked man
Click to expand...
Click to collapse
Told you .
i get a lot of fc of superuser when i try to open apps that requires root permission
neoonix78 said:
i get a lot of fc of superuser when i try to open apps that requires root permission
Click to expand...
Click to collapse
What is fc?
and if you mean that the applications that require root prompts the super user for access is normal.
g0mezz said:
Hi guys, regarding the problem about rooting the original GB, it can be done, and it's not that complicated.
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20G GB ROM.
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse, after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf,
Do not close the window, live it like that.
7. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it, after that start SuperOneClick.exe.
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
This is the method that i did and it worked like a charm.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you is you allow or deny it's access. click allow.
If you do not get the Allow Deny message the root was not completed successfully. do a factory reset and try again the same steps.
If you do get the message you have rooted the phone, go to market and update the superuser and install busy-box. After you can install a custom recovery. Also you can install your preferred Kernel if you don't like the stock one.
As a recovery i use AmonRa i don't like Clockworks. if you like clockworks install rom manager and install it from there. if you like amonRA download it and follow the steps from here.
Click to expand...
Click to collapse
This method did not work for me .. I have V20B Stock Gingerbread. Is there any way to root it .??
If not please guide me to return to stock froyo with proper baseband .
try this
KEEP IN MIND THAT YOU HAVE TO MAKE A NAND BACKUP ALWAYS WHEN YOU ARE MAKING A ROM FLASH.
Good luck.
Hi to all of you, I need the help of anyone on how to extract and restore (adb commands pull and push) the build.prop file in my cell (now bricked) i had the files (modified buil.prop and the original backup build.prop.bak) inside the phone...
The main problem I have: An issue with device recognition in windows PC... driver ADB VCOM MTK 6592 (tried in different PCS windows Xp and 8) (the device manager "see" the vcom preloader but only a little moment (in the first instant when connect the cell (cell off) with usb cable) and then dissapear (disconnect) the vcom preloader...
When I type the command adb devices, result: no devices found...
Tried to upgrade the vcom drivers (when i can catch it in the active state in device manager)... nothing
Tried to "on" the phone... nothing
Tried to flash a new ROM from Recovery (MIUI or Feelingme 078)... ERROR installation aborted
I can see this effect (with usbview): the usb is recognized in the PC (but just for a little moment at the instant when plug it), then disconnect...
I need to recover the original build.prop.bak from coolpad memory, rename it to build.prop and send it to coolpad again...
I think i can flash (from recovery) an original build. prop (packed as update.zip) doing the wipes and apply update from sdcard)... anyone can assist me on this?
This new 9976A item comes to me with 048 version, custom buid version 265 and rooted from factory...
Anyone can please help me?
Probably want to post in here http://forum.xda-developers.com/showthread.php?t=2635445 where there are other members with your device that are rooted and some links to some roms.
es0tericcha0s said:
Probably want to post in here http://forum.xda-developers.com/showthread.php?t=2635445 where there are other members with your device that are rooted and some links to some roms.
Click to expand...
Click to collapse
Thanksss. will do that.
It all depends on your current phone status.
Why did you try to modify it in the first place, how did you try it?
If you're able to
0) put phone in recovery-mode,
1) connect to the phone via adb,
you could
2) rename/delete the wrong build.prop directly on the phone.
So you don't need to push or pull anything.
I'd start MTKDroidTools, connect the powered off phone or while it's powered on being inside the recovery-mode, and hit the ADB-button...then:
"adb shell"
"cd system"
"rm build.prop" deletes current file
"mv build.prop.bak build.prop" renames your backup to original file
"reboot" restarts the device
If you want to use another ROM, you need a proper cwm-recovery to flash (any) kind of that .zip ...that's also the reason,why you couldn't install another ROM on your phone, because your current recovery haven't got the rights to do it. This will also be keeping you from using a update.zip containing the proper build.prop,but that's only a guess.
...on the fly with 9976A
thor2001 said:
It all depends on your current phone status.
Why did you try to modify it in the first place, how did you try it?
If you're able to
0) put phone in recovery-mode,
1) connect to the phone via adb,
you could
2) rename/delete the wrong build.prop directly on the phone.
So you don't need to push or pull anything.
I'd start MTKDroidTools, connect the powered off phone or while it's powered on being inside the recovery-mode, and hit the ADB-button...then:
"adb shell"
"cd system"
"rm build.prop" deletes current file
"mv build.prop.bak build.prop" renames your backup to original file
"reboot" restarts the device
If you want to use another ROM, you need a proper cwm-recovery to flash (any) kind of that .zip ...that's also the reason,why you couldn't install another ROM on your phone, because your current recovery haven't got the rights to do it. This will also be keeping you from using a update.zip containing the proper build.prop,but that's only a guess.
...on the fly with 9976A
Click to expand...
Click to collapse
Hi thor, I modify the buil.prop with root explorer (sound section) because the music not listening through the speakers
Backup created build.prop.bak
Restart the phone... brick...
The phone starts but no pass the main initial logo... get stuck here...
Now, with the phone off, connect it with usb cable, the pc recognizes the phone (but only by a short amount of time) with a couple of seconds disconnetcs...
i have tried a couple of coolpad 9976 vcom drivers finded in the web... (do you have a specific or ensured one?)
mtk 6592 drivers...
this phone comes to me factory rooted, build number: 4.2.048.P2.140127.9976A
custom build version: 265
i will try to do all of you advices...
is this possible to flash an update.zip (with only an original build.prop file inside it) through CWM?
Is this a nice solution?
Hold the line...
I'd try booting in recovery and once you're inside it, connect the phone to the PC, while MTKDroidtools is running. It should be found by Droidtools (MT6592,but without IMEI) and you hit the ADB-button.
After that, use the commands I mentioned earlier ...
The build.prop isn't unique, so if you're unable to use your backup you could use mine (but still need a connection through adb or update.zip).
What is the current recovery on your phone? I know, there's a way building an update.zip...but I've never tried/used that.
The short timespan, in which you can see your device in windows devicemanager, you can right click on it and use "update driver"-function pointing to the VCOM-files. As soon as you click "update driver" you've got time and it will be installed correctly.
ADB-drivers are easy to install, because it can be while the device isn't connected.
Which VCOM-driver did you install, which ADB-driver on which OS?
...on the fly with 9976A
@federimau
Here, try this update.zip...it should contain the correct build.prop
thor2001 said:
@federimau
Here, try this update.zip...it should contain the correct build.prop
Click to expand...
Click to collapse
THANKS GENIUSSSS.
I have the 3a Stock Recovery.
Will try to do this...
If this not work, can i flash what ROM with this Recovery (3a)???
any links to suggested ROMs that work with Recovery 3a???
You need a working system first.
Then use a TWRP or cwm-recovery for installing any custom ROM...
I don't use any custom ROM, so you already asked in the right thread (9976A ROOT).
federimau said:
If this not work, can i flash what ROM with this Recovery (3a)???
any links to suggested ROMs that work with Recovery 3a???
Click to expand...
Click to collapse
thor2001 said:
Hold the line...
I'd try booting in recovery and once you're inside it, connect the phone to the PC, while MTKDroidtools is running. It should be found by Droidtools (MT6592,but without IMEI) and you hit the ADB-button.
After that, use the commands I mentioned earlier ...
The build.prop isn't unique, so if you're unable to use your backup you could use mine (but still need a connection through adb or update.zip).
What is the current recovery on your phone? I know, there's a way building an update.zip...but I've never tried/used that.
The short timespan, in which you can see your device in windows devicemanager, you can right click on it and use "update driver"-function pointing to the VCOM-files. As soon as you click "update driver" you've got time and it will be installed correctly.
ADB-drivers are easy to install, because it can be while the device isn't connected.
Which VCOM-driver did you install, which ADB-driver on which OS?
...on the fly with 9976A
Click to expand...
Click to collapse
Current recovery 3a (from factory)
I think the last vcom drivers are MTKUniversalbrushdriver
Windows XP SP3
i copied AdbWinApi.dll and AdbWinUsbApi.dll and adb.exe in windows/system and windows/system32 folders
thor2001 said:
You need a working system first.
Then use a TWRP or cwm-recovery for installing any custom ROM...
I don't use any custom ROM, so you already asked in the right thread (9976A ROOT).
Click to expand...
Click to collapse
ahhhh ok, ok,... with this you say that i can not solve the problem flashing a new entire ROM through Recovery?
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
federimau said:
ahhhh ok, ok,... with this you say that i can not solve the problem flashing a new entire ROM through Recovery?
Click to expand...
Click to collapse
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
will do that first... i expect your buil.prop flashed by update.zip works...
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
By the way... what is your recomendation/suggestion/advice about: best/fast ROM, CWM version, ROOT method
will do all that in the future
I'll stay at Stock v056,because every newer fw uses the small tray icons,which I don't like.
I still use rua1 autoCWM (non-touch), which is automatically created when you're doing the backup.
Rooting could be done after making the backup, with MTKDroidTools. This should root almost any MTK-phone.
It depends on your firmware and if you're using stock-recovery or cwm-recovery.
With a cwm-recovery,you could use a Chinese update.zip to root.
In the newer FWs you need Root Genius to get system-root after you've got shell-root.
...on the fly with 9976A
Even with the messed up build.prop file, wouldn't you still be able to flash a custom recovery via Odin? Just flash one that has a file manager, boot into it, and manually restore the original build.prop.
Or am I missing something here?
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
Hi thor... tried to flash your update.zip through stock Recovery (3e) unsucessfully...
with this stock recovery i can not flash anything... tried to flash it.. error... tried to flash five different ROMs... error...
can you help with a new update.zip (only build.prop inside) that i can flash with this recovery (3e)??
Phenom2122 said:
Even with the messed up build.prop file, wouldn't you still be able to flash a custom recovery via Odin? Just flash one that has a file manager, boot into it, and manually restore the original build.prop.
Or am I missing something here?
Click to expand...
Click to collapse
Hi Phenom, i used odin with samsung phones, here we are using mtkdroid and spflashtools, i do not know if odin works with this mediateks cells??
Odin is for Samsung phones.
@federimau
Did you try connecting the phone, while it's in recovery and MTKDroidTools is running?
Like I mentioned some time ago?
Doing the trick via adb?
thor2001 said:
Odin is for Samsung phones.
@federimau
Did you try connecting the phone, while it's in recovery and MTKDroidTools is running?
Like I mentioned some time ago?
Doing the trick via adb?
Click to expand...
Click to collapse
yes it tried it... i´m focus now finding a new usb VCOM driver... can you advice me an ensured one?
Rooting and romming Sony devices is a little harder than most android devices, some things work a little different. The scattered info doesn't make this any easier either. I had to find this out the hard way, softbricked my Xperia in the process, but I finally did it. I see that there still are people that wish to root stock 5.1.1 and that there are no unified proper instructions to do this so here is my process and guide. Good luck.
There are many ways to do this, but it includes flashing your Xperia to earlier firmware then rooting and installing the recovery and then flashing back the newest firmware, so I made this little guide to make things easier for Sony newcomers. This process should be compatible with Z1, Z2 and Z3(c) - but ofcourse its made for Z2, for Z1 and Z3 download recovery files for your model respectively.
You won't loose any of your data on your stock ROM if you do this correctly.
You'll need a Windows PC, 7, 8.1, 10. (Mac and Linux are also supported)
1. Root your Z with Kingroot.apk v4.6 and v4.8 work flawlessly. Just download and install as normal apk and hit the big blue button. You have to have internet connection for this to work. It will root your Z automatically after cca. 2m.
Kingroot app is basically a super su app from a different developer. Congrats, you now have root.
2. To install a recovery do not use any flashing apps by TWRP or similar, it wont work. We will use XDZR.
XZDR is Xperia Z Dual Recovery, its basically Philz recovery and TWRP recovery flashed together. You enter Philz holding vol up and TWRP holding vol down when powering up your xperia. * Search for NUT's dual recovery for more info.
Download the recovery from here:
http://nut.xperia-files.com/path/XZDualRecovery
(Download the correct .zip for your Xperia model).
3. Download the. zip to your PC.
4. Connect your phone via USB after you have enabled USB debugging on your xperia. If you have correct Sony drivers installed your PC will recognize your device and a dialog will pop up on your phone (about allowing USB debugging from this PC). Allow the access.
5. Unpack the zip you downloaded to a random folder on your PC. Here run the install.bat if you're on a Win PC. Bat will run and here you just choose the first option, type 1 and follow the on screen instructions, keep an eye on your phone, it will pop up a couple of yes - no dialogs. Allow the access and ADB access and wait, it will be fast.
When you reboot you will see a green LED light up while SONY splash is shown, this is when you hold up or down for one of the two recoveries.
Down is for TWRP and up is for Philz.
6. Download superSU from here:
https://download.chainfire.eu/696/SuperSU/
Boot to system again and now you can unroot your phone trough Kingroot app (general settings) and then reboot to recovery again and flash the file from this link, you will get the super su app and super su binaries and this way you're fully rooted and will have dual recovery for your full flashing pleasure.
* Remember that you first need to unroot and uninstall Kingroot app and then flash Super su, otherwise you risk a bootloop or just not functional root access.
* Do not flash newer TWRP or any recovery or youll loose your recovery.
* I am not responsible if something goes wrong with your device.
And thats it, you have your data intact, stock 5.1.1 ROM, fully functional root access with super su and two recoveries, intact BL and DRM keys and you can flash almost anything that supports LB (locked bootloader).
Hey.
I have a few questions.
Does installing recovery void the warranty? Can the XZDualRecovery be uninstalled easily? Can I still update to Marshmallow via official update when it comes out when I have recovery installed on my phone?
Thanks!
cha0zine said:
Hey.
I have a few questions.
Does installing recovery void the warranty? Can the XZDualRecovery be uninstalled easily? Can I still update to Marshmallow via official update when it comes out when I have recovery installed on my phone?
Thanks!
Click to expand...
Click to collapse
I think that Sony does void warranty if you do an "unauthorized software changes" and changing software in any other way than trough OTA is unauthorized by Sony, so yes. But you can completely restore your device to factory state by flashing an official FTF image trough flashtool and restore Sonys recovery and basically get your warranty back.
If you follow the above steps installation of XZDR is quite easy and fast.
You will be able to update to official MM by flashing MM FTF image trough flashtool and restore your phone to "official" software state. But with XZD recovery you will be able to flash leaked MM from beta program even sooner and easier.
This guide does not unlock your BL and does nothing irreversible to your phone * providing you do everything correctly.
Thanks for answering! Much appreciated!
can you back up the drm keys through this method?
jeebarbas said:
can you back up the drm keys through this method?
Click to expand...
Click to collapse
Rooting with this method wont unlock your boot loader so there is no need for that, your DRM keys wont be touched.
5ageman said:
Rooting with this method wont unlock your boot loader so there is no need for that, your DRM keys wont be touched.
Click to expand...
Click to collapse
Thank you for replying. sorry, im such a noob but after flashing su and subinaries do i need to update the su binaries or i could jsut leave it as it is?
jeebarbas said:
Thank you for replying. sorry, im such a noob but after flashing su and subinaries do i need to update the su binaries or i could jsut leave it as it is?
Click to expand...
Click to collapse
You can leave it as is, you will have full root functionality. Of course you can also update binaries to have up to date bug fixes and security patches, update trough normal method works fine.
@5ageman Hi. Thanks for the tutorial. I m a noob in this rooting stuff. Last night i rooted my phone Xperia Z2 5.1.1 using kingroot bcos i was scared of rooting with some other steps and bricking my phone. But then i realized that xposed wont install unless i have custom recovery. But i m quiet confused with few things related to root even after reading so many posts. So just need to know what exactly recovery is. Like when i restart my phone and then press vol up or down key what will exactly happen? Is this something like safe mode and some other mode in laptops??
talkativetaurus said:
@5ageman Hi. Thanks for the tutorial. I m a noob in this rooting stuff. Last night i rooted my phone Xperia Z2 5.1.1 using kingroot bcos i was scared of rooting with some other steps and bricking my phone. But then i realized that xposed wont install unless i have custom recovery. But i m quiet confused with few things related to root even after reading so many posts. So just need to know what exactly recovery is. Like when i restart my phone and then press vol up or down key what will exactly happen? Is this something like safe mode and some other mode in laptops??
Click to expand...
Click to collapse
Recovery is actually closest to BIOS in PC terms although its much more. Xperia Z2 has no recovery by default, you'll need to flash it manually. See step 2. And only then you can eter recovery. By pressing vol down when the green LED lights up you will enter TWRP a custom recovery made by Team Win Recovery Project. Nothing will happen if you do nothig, you wont accidentaly wipe or brick your Z2. If unsure what to do next just tap the reboot button and then system to reboot to system as nothing happened. Go step by step, no hurry.
@5ageman thanks alot for ur answer. Now my doubt is clear.
But i have few more questions related to ur tut.
1- i have already rebooted my phone a number of times after rooting it. Like for some other purpose and not for recovery or super su. So will the tut work for me as i read somewhere that one need not restart the phone after rooting using kingroot and install recovery directly. Or if it was for some other device i dont remember.
2 - According to the end of step 5 and step 6, does that mean that i have to download super su from chainfire while i m still in recovery mode? And once agn in the system after uninstalling kingroot and rebooting in recovery do i have to install SuperSU in the recovery mode? If yes then how?
3- last question. Entering recovery is just vol down button or power + vol down both.
Once again sorry for such basic questions but i m completely new in the world of rooting plus i want to make sure i know what i m doing.
Thanks for ur patience. Appreciate.
talkativetaurus said:
@5ageman thanks alot for ur answer. Now my doubt is clear.
But i have few more questions related to ur tut.
1- i have already rebooted my phone a number of times after rooting it. Like for some other purpose and not for recovery or super su. So will the tut work for me as i read somewhere that one need not restart the phone after rooting using kingroot and install recovery directly. Or if it was for some other device i dont remember.
2 - According to the end of step 5 and step 6, does that mean that i have to download super su from chainfire while i m still in recovery mode? And once agn in the system after uninstalling kingroot and rebooting in recovery do i have to install SuperSU in the recovery mode? If yes then how?
3- last question. Entering recovery is just vol down button or power + vol down both.
Once again sorry for such basic questions but i m completely new in the world of rooting plus i want to make sure i know what i m doing.
Thanks for ur patience. Appreciate.
Click to expand...
Click to collapse
1. You cannot install recovery directly from the system on Z2 like on other phones, Z2 has no recovery partition. This can only be done with unlocked bootloader. Just make sure you have a working root access with Kingroot and USB debugging enabled when you connect your Z2 to a PC.
2. Download superSU from chainfire while still in system, then reboot to recovery and flash it trough recovery. It's a flashable zip. Before booting to recovery unroot your phone trough Kingroot app. SuperSU zip will flash su binaries and the app to system partition automatically and will root your phone again. Rooting trough Kingroot is done only to flash the recovery, then its deleted.
3. After you successfully install tge recovery when you power on your Z2 it will vibrate and flash green LED on sony bios logo. Then you hold down vol down key until led flashes purple. Afterward it will boot to recovery.
5ageman said:
1. You cannot install recovery directly from the system on Z2 like on other phones, Z2 has no recovery partition. This can only be done with unlocked bootloader. Just make sure you have a working root access with Kingroot and USB debugging enabled when you connect your Z2 to a PC.
2. Download superSU from chainfire while still in system, then reboot to recovery and flash it trough recovery. It's a flashable zip. Before booting to recovery unroot your phone trough Kingroot app. SuperSU zip will flash su binaries and the app to system partition automatically and will root your phone again. Rooting trough Kingroot is done only to flash the recovery, then its deleted.
3. After you successfully install tge recovery when you power on your Z2 it will vibrate and flash green LED on sony bios logo. Then you hold down vol down key until led flashes purple. Afterward it will boot to recovery.
Click to expand...
Click to collapse
@5ageman Thanks for ur reply. but i have few more things to say..
1- no i didnt mean in the system. What i read was that when u root with kingroot u r nt suppose to reboot until u install recovery. Otherwise it might cos prbs and nt install SuperSU.
2- What does flashable exactly mean. Is it nt just installing? I dload the superSU from chainfire while in the system and install in the recovery, right? Where will i find the zip to install it? (sorry... Had to ask)
3- i think i got that...i ll knw that exactly when i try it...lol
talkativetaurus said:
@5ageman Thanks for ur reply. but i have few more things to say..
1- no i didnt mean in the system. What i read was that when u root with kingroot u r nt suppose to reboot until u install recovery. Otherwise it might cos prbs and nt install SuperSU.
2- What does flashable exactly mean. Is it nt just installing? I dload the superSU from chainfire while in the system and install in the recovery, right? Where will i find the zip to install it? (sorry... Had to ask)
3- i think i got that...i ll knw that exactly when i try it...lol
Click to expand...
Click to collapse
1. You wont face any issues if you reboot, but you dont have to. Just plug your phone to PC while your phone is in android. Yes you download in system and then install - flash in recovery by tapping "install" and then you navigate to supersu.zip and select it and then swipe to flash it. The supersu.zip will be there where you download it, most likely on internal storage in download folder.
2. Flashable means its installed trough recovery - its flashed as opposed to being installed normally in android system.
So is it safe to root my Z2 with this? I have 15.1.1 264 stock rom, is this safe?
nemanja899 said:
So is it safe to root my Z2 with this? I have 15.1.1 264 stock rom, is this safe?
Click to expand...
Click to collapse
If you follow the guide correctly and know basic android rooting and romming then yes its safe, I rooted my Z2 the same exact way. 5.1.1 264
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Go to fastboot and boot into stock recovery, don't install. Just boot to recovery, command should be something like below.
fastboot boot recovery-name.img
If you can go to opx recovery, flash stock rom and see
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Have you tried going through the steps for unlocking bootloader again?
Exodusche said:
Have you tried going through the steps for unlocking bootloader again?
Click to expand...
Click to collapse
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
tech_master said:
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
Click to expand...
Click to collapse
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
Ah no. You'll probably need to find someone who can re-sign CM so that it'll flash.
Thanks for the answer, I have no idea how to do this, how is this done? I don't seem to find much info online...
Sent from my HUAWEI TAG-L21 using Tapatalk
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
yuv93 said:
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
Click to expand...
Click to collapse
Thank you. I had tried this procedure previosuly, and didn't work. This time, since you insisted, I tried again, on another computer, and the phone was correctly detected, drivers installed and factory image installed on phone. I am happy again