Recently, I had saved on my HDD before PirateGhost pulled it, his ICS rom, So I followed the diretions to flash the boot.img before flashing thr rom, so it installed and such, and when it went back to the recovery menu it said installed failed, but the actual program that launched o install the stuff said it was ok..Ok lets fast forward I reboot the device and it starts booting up, and shows the boot animation, then it will freeze and of course bootloop, but me being smart I did a backup before I installed anything and it still bootloops, it doesn't even get to the bootanimation... So this is where I start worrying. So I looked and try to revert back to stock just to see if it will work, I can't even lock my bootloader because it says something about error too many links.>.< I need help and any help is most appreciative!
Did you let the PH39IMG.zip install 2 times? Or did you try to update to the newest H-Boot before you re-locked your bootloader? I saw the same error about too many links when I tried to update H-Boot before I locked the bootloader. When you go into the bootloader what version of H-boot does it show?
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
Read the instructions again. You have the wrong hboot
Sent from my HTC PH39100 using xda premium
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
pside15 said:
Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
anthromatt said:
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
Click to expand...
Click to collapse
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
pside15 said:
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
Click to expand...
Click to collapse
Yeah, I discovered that by accident after about 4 failed attempts to successfully flash. The last time I "forgot" to pull the battery after the phone powered off because I had gone into the kitchen to get coffee. When I returned, it had rebooted itself and was finishing the update.
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
I had success by flashing the RUU first then flashing the new recovery, then finally the Rum Float zip file.
Riomaru said:
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
Click to expand...
Click to collapse
Yes, that is true but you didn't complete the H-Boot update. ICS ROMs won't flash properly on the old H-boot. You need to lock the bootloader to use the PH39IMG.zip to update H-Boot then unlock and flash recovery and then ROM.
pside15 said:
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
Ok that did it !!!! Thank so much
Riomaru said:
Ok that did it !!!! Thank so much
Click to expand...
Click to collapse
No problem. Glad you got everything worked out.
I have a soft-bricked Raider and looks like I am having the same problem, I have hboot 1.83.0014 and unlocked. a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Related
Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.
make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.
Thanks pal, fingers crossed eh.
Will let you know if it worked.
It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.
What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.
Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.
Lol failed battery low
MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.
ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.
Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.
RUU
So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.
No need to re-lock or s-on just flash recovery and flash a rooted rom
bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem
I need help with figuring how to solve my problem. Whenever I try to reboot it boots straight to hboot/fastboot. I can't update my system because of it. Can't unlock because it freezes at the screen where I choose to unlock or not. What should I do??
What have you done to your phone so far?
Have you unlocked your bootloader?
Have you installed TWRP Recovery?
Have you rooted your phone?
Have you flashed any new roms or kernels?
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle)
Please give a detailed description of the things you have done, the results of each of these things if any, and when your phone started rebooting straight to HBoot.
Also, is your phone the 32 bit US model, or the 64 bit Europian/Australian model?
There's still a chance your device's firmware is recoverable, but you probably shouldn't try anything until you get some advice from someone who has a lot of knowledge and a detailed description of how you ended up where you're at.
Good luck!
What have you done to your phone so far? I have unlocked it before, but end up re-locking it after failing to root it.
Have you unlocked your bootloader? I did and relocked it.
Have you installed TWRP Recovery? Couldn't and Can't
Have you rooted your phone? No
Have you flashed any new roms or kernels? No
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle) I can't enter recovery.
I have no .img files when entering hboot. I can't unlock because it freezes after choosing the unlock option. It shows entering recovery at the stop and a discalimer message at the botto and goes no where
How to fix the issue
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
bcbradley12 said:
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
Click to expand...
Click to collapse
You should not just lock the boot loader without first reinstalling the stock recovery! When you go to use the RUU if it doesn't see the stock recovery it's going to fail... First reinstall the stock recovery and then OEM lock then you can use the RUU!
P.S. I have no idea why you're replying to some post from 2014... This post was almost a year ago lmao...
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
bcbradley12 said:
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
Click to expand...
Click to collapse
OK but why are you replying to and worried about a post from a year ago?!?