has anyone already tried to root there official ics Rom that was released yesterday? And how?
Sent from my HTC Desire S using xda premium
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
anyone can confirm this is working?
mayurh said:
anyone can confirm this is working?
Click to expand...
Click to collapse
Yes. I can - that's why I posted the solution.
Or you can just use the search button. :banghead:
SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
linqdesires said:
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
Click to expand...
Click to collapse
No, my DS was S-Off - done with XTC-Clip 18 months ago.
Go to recovery mode;
choose .zip from sd card
Flash this
100%
potencia said:
Go to recovery mode;
choose .zip from sd card
Flash this
100%
Click to expand...
Click to collapse
give thanks is for free
For the people, like me, who have only done the HTCdev unlock ( S-ON ), it's quite easy to update the software/ROM using the RUU.
After downloading the RUU from here : http://forum.xda-developers.com/showthread.php?t=1857478 I just immediately ran it, but it failed with an error along the lines of : RUU, security fail! update fail!
So after a bit of googling around I figured that the RUU might simply not be happy with the phone being in an unlocked state, so after doing the following the RUU ran successfully :
1. Re-lock the bootloader with the "fasboot oem lock" command. The output after running the command shows the lock process was successful but moaned about something else failing, still not sure what that was. So after doing this my phone was kinda stuck in the bootloader, where it says ***relocked*** at the top and ***security warning!*** right underneath it. Everytime I reboot or powercycle it would just boot straight back into the bootloader with the warnings, which worried me a little bit.
2. In the bootloader I selected fastboot and connected the USB cable, and then I ran the RUU again. This time it completed successfully after some time. My HTC sync was installed but not running, so seems like that isn't even needed ?
And that's actually it. This process obviously puts the phone in a relocked state, and an overall factory configuration, it also restores the recovery ROM to the factory image or whatever.
No success
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
w_hy said:
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
Click to expand...
Click to collapse
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
steps made by me
SimonTS said:
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
Click to expand...
Click to collapse
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
w_hy said:
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
Click to expand...
Click to collapse
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Sent from my Desire S using xda app-developers app
c.m.b said:
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Click to expand...
Click to collapse
Yes
SimonTS said:
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Click to expand...
Click to collapse
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
w_hy said:
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
Click to expand...
Click to collapse
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
SimonTS said:
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
Click to expand...
Click to collapse
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
w_hy said:
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
SimonTS said:
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
Click to expand...
Click to collapse
So:
hboot: 2.02.0002
s-off /xtc clip/
recovery.img: what you said /puted in new directory togeather with adb.exe and fastboot.exe/
command: as before
result: the same:
G:\0\4>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)... OKAY [ 0.987s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.988s
Related
Hi, i want to put this ROM in my phone :
http://forum.xda-developers.com/showthread.php?t=1096043
i unlocked the bootloader with HTC DEV and rooted
hboot - 2.00.0002
radio - 3822.10.08.04_M
can u tell me what i need to do to put this rom on my device
and tell me please what is use of RADIO and hboot ?
thanks !
IgorICS said:
Hi, i want to put this ROM in my phone :
http://forum.xda-developers.com/showthread.php?t=1096043
i unlocked the bootloader with HTC DEV and rooted
hboot - 2.00.0002
radio - 3822.10.08.04_M
can u tell me what i need to do to put this rom on my device
and tell me please what is use of RADIO and hboot ?
thanks !
Click to expand...
Click to collapse
1.First download Rom manager from market
2. Rom manager flashes ClockworkMod Recovery
3. Now download that rom and save to sd card
4. Now reboot into recovery from ROM manager
5. Inside recovery navigate to backup and restore. now make backup of your current ROM(Very important) or you can directly make backup from ROM manager
6) When you finish backing up,
7) format data/factory reset
8) From advanced, format data,system,cache
9) Also format cache partition
10) Finally, goto install from zip from SD card
11) Navigate your download rom and confirm by pressing YES
12) Wail till CWM flashes
13) Reboot and wait.........................done....
And never flash radio or hboot if it is not necessary.
i did all you said, and i was stuceked at htc logo for 20 mins...i pulled out battery
and tryed to go in recovery to restore backup, and now i'm sutcked at htc logo again
i have revoluntionary cwm...
what should I do ?
sagarda7 said:
1.First download Rom manager from market
2. Rom manager flashes ClockworkMod Recovery
3. Now download that rom and save to sd card
4. Now reboot into recovery from ROM manager
5. Inside recovery navigate to backup and restore. now make backup of your current ROM(Very important) or you can directly make backup from ROM manager
6) When you finish backing up,
7) format data/factory reset
8) From advanced, format data,system,cache
9) Also format cache partition
10) Finally, goto install from zip from SD card
11) Navigate your download rom and confirm by pressing YES
12) Wail till CWM flashes
13) Reboot and wait.........................done....
And never flash radio or hboot if it is not necessary.
Click to expand...
Click to collapse
@sagarda : You forgot a very important thing... He unlocked his phone using HTC dev site. That means the boot is still locked. So the kernel is still preserved from the old ROM, which is incompatible with the ROM he's flashed now, and this is never going to allow the phone to boot up with this new ROM.
So he has to flash boot.img separately from fastboot. I know you were only trying to help, but it's best to only give advice that you have actually tried yourself, otherwise you may end up bricking someone's phone trying to help him.
As for @igorICS, you need to extract boot.img from the ROM zip, and flash it separately using fastboot if you want to boot up this new ROM. And please learn to do some reading before taking the plunge, rather than later...
i pulled battery again and i enered recovery somehow, and recived message,
''can't mount ...''
and i just restored my backup
and i dont wanna **** around with this thing...
enigmaamit said:
@sagarda : You forgot a very important thing... He unlocked his phone using HTC dev site. That means the boot is still locked. So the kernel is still preserved from the old ROM, which is incompatible with the ROM he's flashed now, and this is never going to allow the phone to boot up with this new ROM.
So he has to flash boot.img separately from fastboot. I know you were only trying to help, but it's best to only give advice that you have actually tried yourself, otherwise you may end up bricking someone's phone trying to help him.
As for @igorICS, you need to extract boot.img from the ROM zip, and flash it separately using fastboot if you want to boot up this new ROM. And please learn to do some reading before taking the plunge, rather than later...
Click to expand...
Click to collapse
Thanks for your advice.why HTC dev released the method to unlock if that Does not let other to enjoy custom ROM?
sagarda7 said:
Thanks for your advice.why HTC dev released the method to unlock if that Does not let other to enjoy custom ROM?
Click to expand...
Click to collapse
Because they are a corporation. And corporations are known for this kind of stupidity.
Heard of Apple? They are the benchmark for all this nonsense!
I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx
Tried to search the error here : http://forum.xda-developers.com/showthread.php?t=1357625
But, wait for other reply here. That may not be the solution to yours.
thats not a problem my bootloader is unlocked i wait other reply.
IgorICS said:
I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx
Click to expand...
Click to collapse
MarlX said:
Tried to search the error here : http://forum.xda-developers.com/showthread.php?t=1357625
But, wait for other reply here. That may not be the solution to yours.
Click to expand...
Click to collapse
The command should be:
fastboot flash boot C:\Users\Igor\Desktop\boot.img
no way bro, maybe I'm retarded but this thing wont flash...i flashed sucsessfuly boot.img and im stucked on htc logo again...doesn't matter ill press thanks button cause you tried to help me.. this thing wont flash.. i dont know why..
IgorICS said:
I flashed CoreDroid room and after that i extracted boot.img from ROM.zip
and in fastboot entered this
C:\Android>fastboot flash C:\Desktop boot.img
sending 'C:\Users\Igor\Desktop' (2194 KB)... OKAY [ 0.374s]
writing 'C:\Users\Igor\Desktop'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.655s
i get FAILED result i dont know whats the problem but I wont try to boot my phone
im afraid getting stucked on htc logo again..
tell me whats wrong
im still S-on
2.00.0002 hboot
3822.10.08.04 radio
im waiting your reply . tnx
Click to expand...
Click to collapse
Just add a \ between Desktop and boot.img!
I try not to use desktop for cmd purposes...
Just to be 100% sure, follow the steps below:
1. Make a new folder in C:\ called boot
2. Now place the boot.img in the folder you created (C:\boot)
3. Now, using fastboot, type the following at the command prompt (for you, i see that it is C:\Android) ----- fastboot flash boot C:\boot\boot.img
4. Once you get a confirmation of a successful flash, type adb reboot
5. That's it. Enjoy your new ROM !
Hi, ive been trying to S-off and root my HTC sensation using this guide
http://forum.xda-developers.com/showthread.php?t=1870233
ive managed to get up to step 2, but unable to flash a new recovery using instructions in this guide and also whilst trying kgs utility…. Im pulling my hair out tbh been at it for hours…
so basically, I unlocked my phone, then have got s-off..but now cant get new recovery to get rooting.
when I use the utility in theafore mentioned guide. It either cant find device or just hangs. When I use the kgs utility, it looks promising until I get the message the system cannot find the bacth label specified - dl_4ext_found
any ideas?
try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img
hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>
gdallas said:
hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>
Click to expand...
Click to collapse
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>
rzr86 said:
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>
Click to expand...
Click to collapse
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks
gdallas said:
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks
Click to expand...
Click to collapse
that's why you couldn't perform the command
if i remember well after S-OFF an unlocked bootloader goes again locked
but there was no need to unlock it again
you could use an eng hboot(juopunutbear) which is unlocked
nevermind
flash this zip from recovery now
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
it will give you root
hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.
gdallas said:
hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.
Click to expand...
Click to collapse
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.
malybru said:
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.
Click to expand...
Click to collapse
thanks gents
hmm, i think i must be doing this wrong guys. it thought I flashed the recoevery ok, but then when i hit powerdown on the recovery option, it goes to an HTC logo for a while, then i see my vodafone logo etc and then have a clean install of the orginal rom i guess.
Where am i going wrong?
Many thanks
hey man u just saved my life lol
rzr86 said:
try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My htc sensation was just rebooting couldnt get into recovery, i had clockwordmod recovery, i thought i lost my phone, i searched on xda and saw ur post, and i fixed my phone thnx to you,
So just wanted to say thank you very much.
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
xtrg said:
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
Click to expand...
Click to collapse
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Hey my friend thnks for the reply. I'll try all of these right now. If u can please follow the thread, I might have more questions...Thnks again!
I've reache the point where i mount again my sd card and making all thw wipe things...
I' ve installed the rom but after it says that is succesfully installed and rebooting it shows the htc logo and after that...nothing!
The device turns off(or at least i think it is)black screen, no charge little orange light...But when it comes to this mode, I can hear the soun of the pc like when u do connect a device!
What am I doing wrong?
And yes I have hboot 1.14. What is the correct sequence in the actions????
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
exad said:
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Click to expand...
Click to collapse
exad said:
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
xtrg said:
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
Click to expand...
Click to collapse
You're wiping after flashing the boot.img... so you need to reflash the boot.img don't wipe anything, just fastboot flash boot boot.img and then reboot the phone.
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
AndySOS said:
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
Click to expand...
Click to collapse
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
jollywhitefoot said:
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
Click to expand...
Click to collapse
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
AndySOS said:
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
Click to expand...
Click to collapse
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
jollywhitefoot said:
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
Click to expand...
Click to collapse
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
AndySOS said:
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
Click to expand...
Click to collapse
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
jollywhitefoot said:
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
Click to expand...
Click to collapse
It says that." fastboot is not working proprely" . And yes it does show my device.
AndySOS said:
It says that." fastboot is not working proprely" . And yes it does show my device.
Click to expand...
Click to collapse
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
jollywhitefoot said:
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
Click to expand...
Click to collapse
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
AndySOS said:
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
Click to expand...
Click to collapse
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
jollywhitefoot said:
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
Click to expand...
Click to collapse
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
AndySOS said:
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
Click to expand...
Click to collapse
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
jollywhitefoot said:
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
Click to expand...
Click to collapse
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
AndySOS said:
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
Click to expand...
Click to collapse
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
jollywhitefoot said:
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
Click to expand...
Click to collapse
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
AndySOS said:
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
Click to expand...
Click to collapse
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
jollywhitefoot said:
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
Click to expand...
Click to collapse
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
AndySOS said:
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
Click to expand...
Click to collapse
ok. cool. no problem. glad you got it working.
I have seen threads but nothing related to the 6.0.1 version. Please do help
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
6.0 or 6.0.1... no difference, must do manual systemless install
acejavelin said:
6.0 or 6.0.1... no difference, must do manual systemless install
Click to expand...
Click to collapse
how to do that?
Already answered google it
Sent from my MotoG3 using Tapatalk
flash supersu zip in twrp.. to simple
HelpMeruth said:
flash supersu zip in twrp.. to simple
Click to expand...
Click to collapse
This doesn't work... if you just flash the latest SuperSU in TWRP, a 3rd/4th Gen Moto device will fail to boot because SuperSU's install script does not recognize that this device must have a systemless install. You must start TWRP and before flashing go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" so the SuperSU install script will parse the file and know it has to do a systemless install.
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Nikos dima said:
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.313s]
booting...
FAILED (remote failure)
finished. total time: 0.391s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (8122 KB)...
OKAY [ 0.313s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
C:\Program Files\Minimal ADB and Fastboot>
I tried to flash Twrp but iam getting this
Root 6.0.1
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
I was also facing the same problem First of all u need to unlock bootloader then at bootloader "fastboot boot recovery.img" change your name twrp to recovery after that you will gets boot into twrp from there flash https://www.androidfilehost.com/?fid=24269982087018189 this file
Hit like if I'm helped you
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Check this video to unlock bootloader. https://youtu.be/BCRpCEtcZ_c and if you are getting errors just search in google for solution
jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
jerry94 said:
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
Click to expand...
Click to collapse
If you are getting "No command" that is not TWRP, it is the factory recovery...
When you install TWRP with `fastboot flash recovery twrp.img` you must start TWRP, allow it to make changes to the system, then go to TWRP's reboot menu and select Reboot to Recovery. This action will permanently set TWRP as the recovery, otherwise the OS has a script which will restore the stock recovery on boot.
Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
8) go to Reboot and select Recovery **IMPORTANT** this step allows TWRP to "lock" itself in and prevent the OS from replacing it with the stock recovery again
9) TWRP should start again, and it should not prompt you at all and just go to the TWRP menu
10) Do what you wish in TWRP (flash SuperSU, install ROM, or whatever) if anything
11) Reboot - System
Replace twrp.img with the appropriate filename from http://twrp.me for the device. If you have already made changes to the system, just start at step #4
acejavelin said:
<< Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
..
..
.. >>
Click to expand...
Click to collapse
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
beachfl said:
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
OK... Booting TWRP without installing has nothing to do with functionality of TWRP, it is only to get a clean backup or if you want to root without installing TWRP. TBH, this entire piece is optional and could be skipped, but if you can get a clean backup it sure can makes things easier down the road.
When you flash TWRP, it is flashed... it is written into the recovery partition of your device, but if you start the operating system at this point there is a script (or something, going from my memory of the Nexus 4 which has a script that sat in /system that ran on each boot, so this has been an issue for a while in some devices) that re-writes the recovery it isn't "official". But, but flashing TWRP, allowing it to make changes, then rebooting into TWRP again, it gives TWRP a chance to do something that stops the restoring to official process to stop. I am not sure of the specific details, and I am not sure it really matters, but it works.
acejavelin said:
... Booting TWRP without installing has nothing to do with functionality of TWRP.. .
Click to expand...
Click to collapse
I get that thank you!
Sent from my Nexus 7 using XDA Labs