Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B
Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.
Thankyou I'll have a look round
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
jmelick07 said:
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
Click to expand...
Click to collapse
flash a custom recovery(cwm or twrp) via fastboot, then flash a custom rom(and gapps). thats all you need. all the custom roms out there have root. you dont have to flash superuser.
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Use http://forum.xda-developers.com/showthread.php?t=1250583 to root! It will recognize that your bootloader is already unlocked and skips to flashing CMW and giving you root! There's a youtube video showing it in action if you get stuck by qbking!
Will this work with osx?
jmelick07 said:
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Click to expand...
Click to collapse
heres the latest version of cwm recovery for the nexus s(not ns4G) http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
heres where all the cwm recoveries can be found, including the ns4g http://clockworkmod.com/rommanager
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
I'm fairly content just waiting for the google ics ota... when that comes will it mess my phone up because of my unlocked bootloader?
or even better can someone write me instructions to lock my bootloader?
I found this forum http://forum.xda-developers.com/showthread.php?t=875630
But obviously there are steps before this to have the terminal put these commands towards the phone.
jmelick07 said:
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
Click to expand...
Click to collapse
look at part 3 http://forum.xda-developers.com/showthread.php?t=1007782
only you dont need superuser, any custom rom has root.
Ok, I think I just want to relock my phone and wait for the ota...
I've tried just going into terminal and typing "fastboot oem lock" and it says that the command is not found... what did I do wrong?
You don't need to lock bootoader to get ota.
I've read before that accepting an ota with an unlocked bootloader will brick your phone... Can anyone else confirm that it's ok to accept the eventual ota with an unlocked bootloader?
I'm unlocked and rooted on 1.82 right now. I'm pretty new to Android (and smartphones in general) so I'm just wondering if you guys think it's worth it to upgrade to 1.85? Are ROMs eventually going to stop being based on these RUUs? I don't want to lose root, so I don't know if it's a good idea to upgrade. Plus I don't even know any of the features of 1.85. For all I know, they may have just patched the root exploit and that's it. But now I'm looking at the new ROMs coming out, and it says they are all based on 1.85, and that you need 1.85.
skeetskeeet said:
I'm unlocked and rooted on 1.82 right now. I'm pretty new to Android (and smartphones in general) so I'm just wondering if you guys think it's worth it to upgrade to 1.85? Are ROMs eventually going to stop being based on these RUUs? I don't want to lose root, so I don't know if it's a good idea to upgrade. Plus I don't even know any of the features of 1.85. For all I know, they may have just patched the root exploit and that's it. But now I'm looking at the new ROMs coming out, and it says they are all based on 1.85, and that you need 1.85.
Click to expand...
Click to collapse
I was going to post the exact same question. It's not clear to me the steps to rooting in 1.85, so for now I stay with 1.82.
leitztozeiss said:
I was going to post the exact same question. It's not clear to me the steps to rooting in 1.85, so for now I stay with 1.82.
Click to expand...
Click to collapse
right now the reason roms require being on 1.85 is because we don't have S-off. Without S-Off we have to flash a ROM then flash a boot.img separately if you aren't already on the base. For sake of making life easier on the Dev's being on 1.85 is a prerequisite.
There is a thread somewhere on here explaining in detail how to upgrade to 1.85 once you have unlocked your bootloader.
gunnyman said:
right now the reason roms require being on 1.85 is because we don't have S-off. Without S-Off we have to flash a ROM then flash a boot.img separately if you aren't already on the base. For sake of making life easier on the Dev's being on 1.85 is a prerequisite.
There is a thread somewhere on here explaining in detail how to upgrade to 1.85 once you have unlocked your bootloader.
Click to expand...
Click to collapse
Thank you!! Well, flash a ROM, then flash a boot.img separately. Hmm. Sounds like lots of landmines there. Already overcame the soft brick issue, not sure if I have the energy and will to venture down that path (today anyway. Luckily, we have the holiday tomorrow!).
Well, I took the leap and did the 1.85 RUU thing. Also, I re-unlocked the bootloader. Not sure what I have at this point. I guess I have unrooted 1.85, with an unlocked bootloader.
So . . . flash a ROM then a boot.img separately? Here we go . . .
leitztozeiss said:
I was going to post the exact same question. It's not clear to me the steps to rooting in 1.85, so for now I stay with 1.82.
Click to expand...
Click to collapse
I figured out how to root 1.85. Once your bootloader is unlocked, install CWM Recovery, then download SuperSU to your phone. (I uploaded that .zip file to DropBox from my computer, then downloaded it from my Browser to my phone) After that, just go into bootloader mode, click Recovery. CWM should pop up. Hit "install zip" and go to /Download folder and find the SuperSU. Install it and reboot and you'll have root.
Finally got unlocked/rooted 1.85. Time to install CleanROM.
skeetskeeet said:
I figured out how to root 1.85. Once your bootloader is unlocked, install CWM Recovery, then download SuperSU to your phone. (I uploaded that .zip file to DropBox from my computer, then downloaded it from my Browser to my phone) After that, just go into bootloader mode, click Recovery. CWM should pop up. Hit "install zip" and go to /Download folder and find the SuperSU. Install it and reboot and you'll have root.
Finally got unlocked/rooted 1.85. Time to install CleanROM.
Click to expand...
Click to collapse
yes you can do it that way
but one adb commend will save you all those work
adb push /path/TO/zip /sdcard/
Sent from my Amazon Kindle Fire using XDA
niceppl said:
yes you can do it that way
but one adb commend will save you all those work
adb push /path/TO/zip /sdcard/
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Thanks! Saved a lot of time with CleanROM since it's such a big file.
For anyone else who is going to use adb to get the file on your phone, the command is
Code:
adb push "CleanROM Standard 2.1.zip" /sdcard/CleanROM.zip
before I was just pushing to "/sdcard/" and it wasn't working. You gotta include the filename.
skeetskeeet said:
I figured out how to root 1.85. Once your bootloader is unlocked, install CWM Recovery, then download SuperSU to your phone. (I uploaded that .zip file to DropBox from my computer, then downloaded it from my Browser to my phone) After that, just go into bootloader mode, click Recovery. CWM should pop up. Hit "install zip" and go to /Download folder and find the SuperSU. Install it and reboot and you'll have root.
Finally got unlocked/rooted 1.85. Time to install CleanROM.
Click to expand...
Click to collapse
Done. Wow, an exercise in patience. I could've turned green, ripped through my shirt, and crushed that darn phone!
---------- Post added at 02:14 AM ---------- Previous post was at 01:49 AM ----------
CleanROM installed and booting. Sleep is for wimps. I'm going to bed anyway.
Let's see if I can spend the holiday off not screwing around with my phone!
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Check out this thread over in the dev section.
http://forum.xda-developers.com/showthread.php?t=2046439
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Frunple said:
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Click to expand...
Click to collapse
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Knightvision said:
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Click to expand...
Click to collapse
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
I can confirm that this method works. I used Voodoo to keep my root and then answered yes to allowing CWM to install the unsigned .zip and answered yes to keeping root. I then got the dreaded Verizon warning triangle and was prepared to Odin back to Stock and start over. Just by chance I went into download mode and it allowed me boot my Rom. Once in, I checked EZ-unlock and it said I was unlocked, so I went ahead and locked and then unlocked and all was good! Hope this helps saves someone else some hassle.
Real_JESRadio said:
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
Click to expand...
Click to collapse
man I tried this but it didnt work rootkeeper says its rooted but no root access the super user app is there...could i have done something wrong?? do i have do something after i upgrade to get to work?? thanx
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
It's fixed now. The CMW recovery mode wasn't working for some reason. Whatever broke ROM Manager did so by breaking CMW Recovery. I blame myself for stupidly trying to run a backup like that. Anyway, all I could get was the triangle screen and it would only reboot to that or the CMW that wasn't working. Ended up putting it in Odin mode and reflashing with one of the no-wipe leaks. Works fine now. And VZW says I am up to date.
Will get around to rerooting/unlocking again later today. And smacking myself for getting into this mess.
Good to learn from mistakes that are not fatal. Good to have LOTS of resources to figure out how to bail it out too!