Related
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
Ok...I've searched all over the internet and these forums and can't find an answer to my problem so here it goes:
I recently purchased the TF300T pre-owned. I had no idea if the device was rooted or not, but assumed not. I assume correctly so, as I do with all my Android devices, I proceed to look up the root method.
This device has never been able to boot into any type of recovery, stock or otherwise. I get the "Android on his back with the red triangle" error and holding the power button only reboots the device.
So far I have used fastboot to flash CWM recovery and have unlocked the bootloader. (I know the device is unlocked because it tells me so)
After all this, I proceed to enter CWM to root my device and the same error pops up. What am I doing wrong? How do I fix this? And is there any hope for me to root this device from this point?
I appreciate any input given or being directed to the correct answer.
Thanks
P.S. BTW....I did do the JB OTA Update right after I first got it and I did flash a JB Recovery Version....just so you know.
[A] Boot to Recovery
jdcrowell99 said:
Ok...I've searched all over the internet and these forums and can't find an answer to my problem so here it goes:
I recently purchased the TF300T pre-owned. I had no idea if the device was rooted or not, but assumed not. I assume correctly so, as I do with all my Android devices, I proceed to look up the root method.
This device has never been able to boot into any type of recovery, stock or otherwise. I get the "Android on his back with the red triangle" error and holding the power button only reboots the device.
So far I have used fastboot to flash CWM recovery and have unlocked the bootloader. (I know the device is unlocked because it tells me so)
After all this, I proceed to enter CWM to root my device and the same error pops up. What am I doing wrong? How do I fix this? And is there any hope for me to root this device from this point?
I appreciate any input given or being directed to the correct answer.
Thanks
P.S. BTW....I did do the JB OTA Update right after I first got it and I did flash a JB Recovery Version....just so you know.
Click to expand...
Click to collapse
hi JDCrowell99! It is possible that your installation of CWM may be causing you issues. I too had unlocked the bootloader after updating to JB OTA stock ROM. I used fastboot to install CWM. I continually got invalid signature failures whenever I tried to flash a new ROM (Stock or modified). I finally ran across a thread that stated the invalid signature problem appears on an occasion with CWM and to install TWRP. I did so using the instructions in thread:
http://forum.xda-developers.com/showthread.php?t=1672108
After upgrading to TWRP I can now flash ROMs without getting an invalid signature error.
Hope that helps and good luck!
- Mike
I'm with you, Mike. I tried CWM when I first got my tablet and it wouldn't make backups properly. I flashed TWRP with fastboot and haven't had any issues since. :good:
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Mike_SattyEng said:
hi JDCrowell99! It is possible that your installation of CWM may be causing you issues. I too had unlocked the bootloader after updating to JB OTA stock ROM. I used fastboot to install CWM. I continually got invalid signature failures whenever I tried to flash a new ROM (Stock or modified). I finally ran across a thread that stated the invalid signature problem appears on an occasion with CWM and to install TWRP. I did so using the instructions in thread:
http://forum.xda-developers.com/showthread.php?t=1672108
After upgrading to TWRP I can now flash ROMs without getting an invalid signature error.
Hope that helps and good luck!
- Mike
Click to expand...
Click to collapse
Mike, that worked perfectly!
Thanks for the advice. Much appreciated
Awesome!
jdcrowell99 said:
Mike, that worked perfectly!
Thanks for the advice. Much appreciated
Click to expand...
Click to collapse
Glad to hear it worked for you!
TF300T Bricked with bootloader unlocked, HELP PLEASE!!!!
Hi guys, I'm from Brazil, sorry about my english!! I have a TF300T, I unlock the bootloader and when I was trying to root the device I made something very very wrong and I didn´t know how to fix it!!! I execute the fastboot commands but I can´t enter in CMW menu after it, so I enter in the system menu (RCK, Android, USB, Wipe Data) and unfortunatly I click on Wipe Data icon!!! Now i can´t enter on system menu and the device don´t turn off!!!! When I push the power button plus Vol Down nothing happens. Please somebody HELP ME!!!!!
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..
Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Bizzmagizz said:
Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Click to expand...
Click to collapse
try to root again or if it wont work, back to stock and start from begining
Paget96 said:
try to root again or if it wont work, back to stock and start from begining
Click to expand...
Click to collapse
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Bizzmagizz said:
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Click to expand...
Click to collapse
you have all here
follow this,and back to stock, then root again, install cwm or twrp recovery, and install what ever you want
http://xperiafirmware.com/8-firmware/13-sony-xperia-s-lt26
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Bizzmagizz said:
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Click to expand...
Click to collapse
witch android do you want?
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
Here is 4.0.4
https://docs.google.com/file/d/0B_d8uWGbkaetLThpYzEwZUh5aTg/edit
steps:
how to install the newest Android 4.0.4 for Sony XPERIA S LT26i
a) first of all, check your firmware version (if you already have the newest one, you do not need this tutorial)
b) download and install latest Flashtool from here (mirrors Google Drive or Mega)
c) download also latest Android 4.0.4 (mirror) for Sony XPERIA S LT26i
d) paste the ftf file downloaded in step c) to folder „Firmware“ included in the XPERIA Flashtool
e) open the XPERIA Flashtool, click on flash and choose downloaded firmware, than click ok. Important - if you do not want to delete any data of your phone, just uncheck flashing userdata.sin file. All data will remain in your phone, but sometimes it can cause additional troubles. So it is better (and I recommend that) to do the backup of your personal data, than proceed with clean instalation and then restore your personal data.
f) turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
g) after few minutes all is done and your phone gets the new firmware
Here you got 3 ways to update good luck
http://androidteen.com/xperia-s-lt26i-update-to-android-4-1-2-jelly-bean-official-firmware-6-2-b-1-96/
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Bizzmagizz said:
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Click to expand...
Click to collapse
The clue's in the error message - you don't have the required drivers installed.
There's a directory named "drivers" under the main flashtool dir. Run flashtool-drivers.exe and install the appropriate drivers. I think "Common Drivers Viskan Board" is the one you need. I ended up installing all of them to get it to flash (which took ages).
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Bizzmagizz said:
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Click to expand...
Click to collapse
work??
dont forget to press thanks
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Bizzmagizz said:
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Click to expand...
Click to collapse
use this to reboot into recovery
ang go to reply, because I dont see you post
https://play.google.com/store/apps/details?id=pl.qbanin.reboot
I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
*fastboot flash recovery recovery.img
*fastboot reboot
Click to expand...
Click to collapse
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
jayalex said:
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
Click to expand...
Click to collapse
http://www.wugfresh.com/brt/
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
this is true, i had to do that... when done flashing TWRP reboot to recovery, no OS
jayalex said:
I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
Click to expand...
Click to collapse
A quick search would have uncovered a dozen or so threads detailing how to overcome this problem in the very q&a section that you've posted in. Then there's the FAQ thread that's stuck at the top:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Then there's my guide stuck in the general section:
http://forum.xda-developers.com/showthread.php?t=2839471
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Michiel0211 said:
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Click to expand...
Click to collapse
Have you tried flashing a different version of TWRP or another recovery?
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
fastboot flash recovery twrp-2.7.6.0-bacon.img
fastboot boot twrp-2.7.6.0-bacon.img
Click to expand...
Click to collapse
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
jayalex said:
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Click to expand...
Click to collapse
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Did you try using the fastboot boot command instead like I did above?
I'll give it a shot next time I get. Hope it works.
Michiel0211 said:
I'll give it a shot next time I get. Hope it works.
Click to expand...
Click to collapse
Cool, let us know how it goes :good:
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Try doing what the poster directly above you did.
I finally managed to get it working by downloading the latest version of TWRP (2.8.3.0) and (if it helped) using the command 'format cache'.
It doesnt stick, but atleast it works.