My nandroid backup was made after rooting, so after a restore from cwm (I was on jb deodexed) I was still rooted. I flashed a stock image from sammobile with Odin from PC and I lost root (that was my intention). All my apps and data are still here, did not lost anything. No wipe no cache clear nothing else. Binary count 0.
I want to be sure that when jb ota is released I'll be able to install it from the device without any issues.
Do I have to do anything else? I read in some posts that I have to flash the stock recovery, in others that the stock recovery is flashed within the stock firmware so I'm not really sure. Is there a way to verify?
Sent from my GT-N8010 using Tapatalk 2
KoRoZIV said:
My nandroid backup was made after rooting, so after a restore from cwm (I was on jb deodexed) I was still rooted. I flashed a stock image from sammobile with Odin from PC and I lost root (that was my intention). All my apps and data are still here, did not lost anything. No wipe no cache clear nothing else. Binary count 0.
I want to be sure that when jb ota is released I'll be able to install it from the device without any issues.
Do I have to do anything else? I read in some posts that I have to flash the stock recovery, in others that the stock recovery is flashed within the stock firmware so I'm not really sure. Is there a way to verify?
Sent from my GT-N8010 using Tapatalk 2
Click to expand...
Click to collapse
try booting into recovery by holding down the power and volume up button at the same time until it starts to boot then release the power button and keep holding the volume up. This will boot into recovery and there you can tell if it's stock or CWM.
It's stock. After the nandroid restore from cwm when I wanted to reboot I was asked if I want to keep cwm or to restore stock, and I choose stock. I think I''ll do a wipe and whatever I can from the stock recovery. I'm just bored....
Sent from my GT-N8010 using Tapatalk 2
yeah and if all else fails when the update comes and you aren't able to get it then you can just factory reset and odin the stock firmware and then all should go smoothly.
I already did that
The red triangle in the stock recovery is normal?
Sent from my GT-N8010 using Tapatalk 2
Use TriangleAway to get rid.
theoneofgod said:
Use TriangleAway to get rid.
Click to expand...
Click to collapse
+1 it's worth the money to always have that as an option, just make sure you follow the directions (pretty simple)
It was the first thing I did after flashing the jb. As I stated in my first post, everything is ok on my device, I just wanted to be sure that I didn't miss something and that I'll be able to receive and use future OTA updates. I guess I'll have to wait to be sure, no point in making a tutorial on this yet.
Sent from my GT-N8010 using xda premium
Related
I'm on CyanogenMod7-7.0.3-NS right now but want to go back to stock 2.3.4 as wavesecure is having issues with Cyanogen and can't verify my sim.
Baseband version: I9020XXKD1
Build Number:GRI40
Will this guide work for my Nexus S? http://forum.xda-developers.com/showthread.php?t=1061855
Sorry newbie here, just want to be really really sure as I followed a poor guide somewhere and got stuck up with the google logo and lock on boot, hence was forced to install cyanogen.
---
UPDATED: 7/8/11
Okay..so to close my question. I just followed this and everything went back to stock.
theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s
1. followed the link above.
2. I remain rooted but recovery went back to stock. no more clockwork.
3. after booting, was alerted of a 2.3.4 update..so I updated again.
4. marketplace has been upgraded to the new interface (probably bec of the update)
5. to install screenshot app and fontchanger..I needed to have super user, so I just installed Clockwork (recovery-clockwork-3.0.2.4-) again and installed SU (su-2.3.6.1-ef-signed.zip) via SD card install.
6. so far, everything's good.
If you have some questions, feel free to ask.
Download a stock rom ( unless you made a nandroid backup)
Turn off you phone then start it while holding vol+
Do a factory reset, wipe cache and dalvik cache( found under advanved)
Flash your stock rom
Sent from my Nexus S using XDA App
Emhalwis said:
Download a stock rom ( unless you made a nandroid backup)
Turn off you phone then start it while holding vol+
Do a factory reset, wipe cache and dalvik cache( found under advanved)
Flash your stock rom
Click to expand...
Click to collapse
thanks! I have made a nandroid backup but I think I may have a corrupted boot.img.
Where can I get a stock rom? Is the one from the link I posted good enough?
Emhalwis said:
Download a stock rom ( unless you made a nandroid backup)
Click to expand...
Click to collapse
Is there a way to return to stock while keeping CWM ?
You can stay on stock rom while you are rooted. You can google it. I got my 2.3.4 from ardoid.com
Its a stock rom with added arabic support. Since you dont need arabic. It wont make any difference to you.
Sent from my Nexus S using XDA App
I'm not asking for keeping root, only to revert back to stock while keeping CWM
Clockworkmod will stay on your phone. As far as i know, all your phone recoveries will be done through cwm
Sent from my Nexus S using XDA App
Emhalwis said:
Clockworkmod will stay on your phone. As far as i know, all your phone recoveries will be done through cwm
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I read somewhere that flashing a stock ROM will restore the stock boot/recovery. Is it true ?
That i cant answer u. But i can say that i went back and forth between roms. Reverting to stock when needed. CWM stayed on my phone.
Sent from my Nexus S using XDA App
Ok, will have try. Thanks
dude if install stock rom via odin then u will loss cwm bt iheard u cn gt .zip files of stock roms using tht u wont loss cwn
Thats what im trying to say. The only way (i think) to lose cwm is using odin. But you can find zip stock roms. Thats what i did
Sent from my Nexus S using XDA App
Okay..so to close my question. I just followed this and everything went back to stock.
theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s
1. followed the link above.
2. I remain rooted but recovery went back to stock. no more clockwork.
3. after booting, was alerted of a 2.3.4 update..so I updated again.
4. marketplace has been upgraded to the new interface (probably bec of the update)
5. to install screenshot app and fontchanger..I needed to have super user, so I just installed Clockwork (recovery-clockwork-3.0.2.4-) again and installed SU (su-2.3.6.1-ef-signed.zip) via SD card install.
6. so far, everything's good.
If you have some questions, feel free to ask.
Thanks for the clarification !
Been browsing around a bit and noticed that some people want to completely revert back to stock, but they don't want to use ODIN, due to the fact it'll trigger the flash counter for warranty exchanges. It's a backup I made literally IMMEDIATELY after I flashed Clockwork recovery, so it's completely unrooted and untouched. Just wanting to ask around to see if it seems like something useful to others before I upload it. Let me know! Could just flash the stock recovery and be at a completely out-of-the-box state.
Or possibly use it to make a stock flashable .zip?
It wont get rid of root and cwm and super user.
Fortune090 said:
Been browsing around a bit and noticed that some people want to completely revert back to stock, but they don't want to use ODIN, due to the fact it'll trigger the flash counter for warranty exchanges. It's a backup I made literally IMMEDIATELY after I flashed Clockwork recovery, so it's completely unrooted and untouched. Just wanting to ask around to see if it seems like something useful to others before I upload it. Let me know! Could just flash the stock recovery and be at a completely out-of-the-box state.
Or possibly use it to make a stock flashable .zip?
Click to expand...
Click to collapse
Sent from my SGH-I727 using xda premium
Actually I would certainly have a usefor this. I made some boneheaded decision and unistalled.a.couple.bloatware apps before I made my first nandroid.backup
This would be pretty useful when the ics ota comes around.
Sent from my SAMSUNG-SGH-I727 using XDA App
In order to get back to "out of box" condition for warranty/return purposes you need to reinstall 2.3.5 or 2.3.6 stock ROM, KERNEL, and 3e Recovery. The only time (based on what I've read on SR Forum), the custom binary flash counter gets tripped is when you use Odin to flash a Kernel (boot.img). So I think what you are proposing is to flash stock ROM/KERNEL using CWM, then use Odin to flash the stock 3e Recovery partition. Odin should not trip the flash counter if you only Odin flash "recovery.img" and not the "boot.img" (kernel). Correct?
appdroid said:
It wont get rid of root and cwm and super user.
Click to expand...
Click to collapse
I was running SkyIce before, fully rooted, and after restoring this, I no longer have root priveledges and Superuser.apk isn't anywhere to be found.
And yes, restoring this to get a stock kernel and everything back, then just flash stock 3e with Odin to get the recovery partition back to stock.
Sent from my SGH-I727 using xda premium
I'm sure this is discussed already but I can't seem to find it so if someone can help me or point me in the right direction.
I have a VZW GS3 that I have rooted, unlocked the boot loader and flashed CWM recovery. I then made a nandroid.
The main reason I did this was because I wanted Jelly Bean, and since Verizon is the slowest, I didn't want to wait so I installed custom ROMs.
Now that Verizon has released JB, I want to go back to my nandroid and then use the OTA firmware update service to upgrade.
Am I missing anything along the way that's essential for this to work?
Will the updated software re-root and/or relock my bootloader?
Will this automatically update the Baseband from my current VRLG7 to whatever the new one is?
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no? If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it. Here's a step by step:
1) boot into CWM, restore your rooted, stock nandroid
2) Download EZ recovery, flash stock recovery
3) Wait for OTA
The OTA will relock your bootloader and unroot your phone. The JB OTA will also update your modem, and everything else, to VRBLK3.
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
Click to expand...
Click to collapse
No, you will lose CWM if you do what I detail above. The OTA will fail if you still have CWM installed.
SlimSnoopOS said:
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no?
Click to expand...
Click to collapse
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
SlimSnoopOS said:
If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it
Click to expand...
Click to collapse
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
levilib said:
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
Click to expand...
Click to collapse
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
Absolutely.
Sent from my SCH-I535 using xda app-developers app
so which wipe(s) do I need to do?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
No you do not, the nan will overwrite everything anyways. If you feel better then factory reset and clear caches, but it's not necessary.
Sent from my VS920 4G using xda app-developers app
thanks
I followed the instructions above and I'm back on my rooted TW.
When i try and update i get the following message:
Service Unavailable
To check for system updates, go to Settings > About device when service is available
What's wrong, how do i fix that?
searched around on google and a lot of people had the same warning error, multiple solutions were offered but none of them worked.
in the end, I ended up installing from odin completely stock unrooted, locked bootloader etc 4.0.4 (as f i want to return my phone to verizon) and once i did that it automatically updated to 4.1.1
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW
dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk
New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk
richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?
I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app
z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.