Related
I have a HTC Desire, which I rooted using Unrevoked.
This updated my recovery to ClockworkMod 2.5.0.7 - which was great and I was able to backup/restore/apply new roms. Also ROM Manager worked and I could use that application to access the recovery modes/scripts.
ROM Manager then got updated, including the ClockworkMod (5.0.2.0). Now ROM Manager fails to run any of the scripts when starting in recovery mode.
When I manually boot in to recovery, I am still on the 2.5.0.7 version and not the latest. I've tried applying the 5.0.2.0 update - which updates for that boot, but on a reboot reverts back to 2.5.0.7.
So, my questions are;
- To update my recovery program do I need S-OFF? Currently still have S-ON.
- If S-OFF, will a simple 'apply update from sdcard' update it?
Thanks, A
----------------------------------------------------
HTC Desire (Bravo) - ICS 4.0.3 CM9, b0.2.5 ROM.
Samsung Galaxy 10.1 - Stock ROM.
I have S-ON on my Hero and I always updated my recovery. I don't think it would be a problem.
Don't use rom manager. Just copy the file to your SD and flash it manually trough recovery (flash/install zip from SD), it should work.
Thanks.
but.... nope! It's stuck on ClockworkMod 2.5.0.7! As I said I can flash it to 5.0.2.0 and use it, but next time I enter recovery it's back to 2.5.0.7!
If it's not S-ON that's causing it, could it because I rooted with Unrevoked? Some how that's locked it to 2.5.0.7?
Thanks, A
----------------------------------------------------
HTC Desire (Bravo) - ICS 4.0.3 CM9, b0.2.5 ROM.
Samsung Galaxy 10.1 - Stock ROM.
It could be unrevocked, but not sure. I rooted a Desire owned by a friend but with S-OFF.
He never had any issue.
Sent from my Hero using xda premium
Same problem
I have the same problem.
Some help?
Thanks
O.
same here...tried everything!
Same here.
Rom Manager fails. (says it's worked, but upon boot to recovery it's the same 2.5.0.7
Rom Toolbox just fails and admits it.
I tried following this http://forum.xda-developers.com/showthread.php?t=1608042 thread, and tried basically the same thing via the android-terminal as well. Every time it fails.
When trying via the terminal (android or adb) I get erase and write fails, and a run out of memory error. I would like to update CWM so that I can partition the SD using the phone.
Any help would be really appreciated. Thanks.
The Answer
Well I found the answer for me. My problem was that I still had S-On and had to get that to S-Off as apparently my phone (HTC Desire) has an advanced security feature put on by HTC that stops you writing to /System, which is a necessary location to write to to update CWM. I got S-Off by using revolutionary, which was pretty noob friendly despite the scary words on the page. (google for revolutionary s-off)
Revolutionary just requires the HBOOT version and the Serial Number of the phone, which you find under the battery. DLed the fastboot drivers as they recommended as well. Once I got S-Off, I was able to use Rom Manager to update the CWM to 5.0.2 or whatever the latest is now.
Hope this helps you as it did me.
PS I have previously tried re-running unrevoked whilst the phone had BCM ICS (CM9), which didn't work (error was "is your firmware too new?"). I then downgraded to CM 6, and tried again with unrevoked, but the Rom Manager still wouldn't upgrade CWM. I checked HBOOT and as suspected still had S-On...Revolutionary is your answer methinks
so which CWM RECOVERY is latest without S-OFF and with option to partition SD EXT2/3/4 etc? thanks.
Hey guys,
I am pretty new to rooting, and I am sorry if I am noob to the max.
I just rooted my Nexus S 4G, and installed ROM Manager v5.0.0.7. I want to put cm9 (the release candidate) on my phone. Every time I open ROM Manager, and hit Flash ClockworkMod Recovery, it says "An error occurred while attempting to run privileged commands!"
Thinking this was an issue with the root access ROM Manager has, I looked at the app list in Super User, and nothing is there.
How can I fix this and get cm9 on my phone??
Thanks for your help.
EDIT: I uninstalled both SuperUser and ROM Manager, got the latest version of SuperUser (v3.1.3) and ROM Manager. When I hit Flash CWM, the blue bar at the top goes almost all of the way, then the program quits responding.
Why are you flashing a recovery when you already installed one??
you have not given Rom manager root access, hence nothing in the superuser app. try clear su's data and cache, and go to its settings>security>Automatic response>Prompt and clear rom manager's data and cache as well, and try again. this time, you will encounter a message titling superuser request and click allow and remember options and you're on your way to the ICS party, although im leaving in 2 weeks in favour of jellybean
Alternative: install TWRP, and flash it via adb, and use reboot recovery command in terminal
That didn't work.
MikeMBau said:
That didn't work.
Click to expand...
Click to collapse
what didn't go right? no prompt? more info please... and make sure you're actually rooted, not just install superuser app
Do you or do you not already have a recovery on your phone? Installing superuser =/= rooted. If you don't you should manually install a recovery so that: A. You have a better understanding of what you did (it's always better to know what you're doing when you're messing around with your phone) and B. If something goes wrong you know exactly what caused it.
If you already have recovery why are you bothering with Rom manager? Just wipe cache and data (make a backup first) then flash the Rom.
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Billchen0014 said:
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Click to expand...
Click to collapse
That was my first conclusion too, I just wanted to make sure before I flat out said that he wasn't rooted.
Just wanted to update the situation:
I definitely was rooted at the time of posting this, as I could tell by the open lock on the bottom of the boot screen under Google and it said S-OFF when I would boot into recovery.
I ended up just unrooting the phone and rerooting, and this seemed to fix whatever bug I had.
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
EDIT: I have done some tweaking with restoring my old back up and I have come to the conclusion that my /system folder is corrupt, i know a few ways to fix that but anyone one the best way and maybe a 2.3.4 system folder to use?
EDIT2: I replaced my system folder with one that i have and now it gets past the white htc screen but will loop the sprint 4g screens.
FIXED IT,\: what I did was I managed to RUU back to 2.2 through this thread, now I am on 2.2 and will continue to get an s-off root, thank you for all your help
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
Can you get into bootloader? If so, what is your hboot version and software version?
Just in case you don't know how, to get into bootloader, you need to power off or pull battery, then press and hold VolDown+Power until the white bootloader screen comes up
At the top it tells you the hboot version
Sent from my PG06100 using xda premium
I can get into bootloader.
hboot-0.99.0001
radio-1.08.01.0111
thats all I can get about my version
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
When you went through HTC-Dev.com you did not Root the Device. All you can do at the site is Unlock the Bootloader. To resolve the issue you can try a Factory Data Restore in Bootloader, but you are going to lose all the current Data on the Device. It may or may not work. If it does not then, you may have to run an RUU. To do the Factory Restore pull the Battery on the device. Then put the Battery back in. Hold Volume Button down , now at the same time press the Power Button. It will boot into Bootloader. Once it is in Bootloader use the Volume Rockers to toggle Up, or Down. Then choose Factory Restore by pressing the Pwer Button. Since your not rooted that's your only option that I know of other than an RUU. If that does get you out of the White Screen I would suggest finding out your Android version. Then following the correct process to attain Full Root.
Maybe I was a bit unclear, I went though the htcdev site to unlock the bootloader, then i moved clockworkmod recovery instead of the stock recovery, i then installed superuser through Clockworkmod, so i had root though that, but not an s-off root, so I then installed ROM manager and thought the cyanogen 7.2 rom would be a cool one to have, I forgot it was not an s-off root, so i went ahead with downloading it though Rom manager and it prompted me to install the new rom, and brought me to clockworkmod recovery and said the install was aborted, and i rebooted and then it got stuck at the htc screen, I can get into bootloader and clockworkmod recovery, I have a backup of my stock rom on my computer and put it onto my sd card hoping i can restore to that one, but i get the md5 mismatch error, working on fixing that now.
I still believe that most of the issue is that you are not Fully Rooted. What version of Android where you on when you started ? The reason I ask is because the method you used is a bit unorthodox, so I doubt your Rooted. I would still suggest doing a factory Restore. But you can look HERE on how to fix the MD5 mismatch error.
Yeah, if you only unlocked bootloader, thats not a full root, you still have a ways to go
The best thing would be to just RUU and start over using VICODAN's method, which covers 2.2 all the way up to 2.3.4
Sent from my PG06100 using xda premium
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
11telisz said:
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
Click to expand...
Click to collapse
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
prboy1969 said:
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
Click to expand...
Click to collapse
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
11telisz said:
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
Click to expand...
Click to collapse
The only way I know how to do it would be using adb and just flashing all the images through that.
Sent from my PG06100 using xda premium
Hello all!
I unlocked my HTC Desire S (with HTCdev website) and the use of "Hasoon2000's HTC Desire S All-In-One Kit"...
I can either flash TWRP 2.4.0.0 (recovery) or use ClockworkMod (recovery) to erase things and install the Cyanogenmod, but when I make a connection to the computer using USB and send the .zip-files of Cyanogenmod to the SD-card and try to install Cyanogenmod, the telephone just gives me a white startup screen with "HTC" and then the screen goes black (backlight stays on though)...
What am I doing wrong? I once managed to get Cyanogenmod on the telephone, but reverted the whole process because a new version of Android coming out back then... I do not remember how I managed to do it back then tho...
I think the main problem is, I did not make a backup and I selected "Erase/wipe system" in TWRP on the telephone...
Where should I go from here? Is he bricked beyond repair?
Thank you for reading this!
Also... after reading abit, I came across the whole "downgrade from hboot 2.02.0002 to hboot 0.98.0002"-thing?
As I remember correctly, my hboot is 2.02.0002? I did not downgrade this to 0.98.0002 yet, might that cause the problem i'm having?
Have you flashed the boot.img in fastboot?
teadrinker said:
Have you flashed the boot.img in fastboot?
Click to expand...
Click to collapse
To be honest I'm not sure what you mean, but I don't think I did that... Should I do that maybe? And could you please explain or show how in that case?
Thank you allready for your reply!
Because your phone is still s-on, despite being unlocked, you can't write the /boot partition from recovery, so you have to do it manually through fastboot (every time you install or update a rom or kernel).
See this guide for instructions, specifically steps 1 and 4:
http://forum.xda-developers.com/showthread.php?t=1525100
Thank you so much for your help, I managed to flash it and install Cyanogenmod 7 on the phone and it works flawless...
I am however a little bit displeased by Cyanogenmod to be honest... I cannot get my mobile internet to work on it (from provider, not Wifi) and there is no Google Play/Market app on it... I tried to install the "gapps-gb-20110613-signed.zip" file and it installs correctly, but it only seems to install Talk or something if i'm not mistaken...
Are there better alternatives to Cyanogenmod 7 that I can ask you about? I have read about Reaper on http://forum.xda-developers.com/showthread.php?t=1433816 and it seems it may be better than Cyanogenmod itself?
Ok, signing in to my Google account has enabled Market, although I can't seem to download any apps yet... Hmm... The trial and error continues...
Quirania said:
Hello all!
I unlocked my HTC Desire S (with HTCdev website) and the use of "Hasoon2000's HTC Desire S All-In-One Kit"...
I can either flash TWRP 2.4.0.0 (recovery) or use ClockworkMod (recovery) to erase things and install the Cyanogenmod, but when I make a connection to the computer using USB and send the .zip-files of Cyanogenmod to the SD-card and try to install Cyanogenmod, the telephone just gives me a white startup screen with "HTC" and then the screen goes black (backlight stays on though)...
What am I doing wrong? I once managed to get Cyanogenmod on the telephone, but reverted the whole process because a new version of Android coming out back then... I do not remember how I managed to do it back then tho...
I think the main problem is, I did not make a backup and I selected "Erase/wipe system" in TWRP on the telephone...
Where should I go from here? Is he bricked beyond repair?
Thank you for reading this!
Click to expand...
Click to collapse
Hey Buddy. I just got CM10.1 on my S4. What I did was install goomanager from the play store and then install TWRP that way. No flash required. Then move the CM and gapps file to the SD card. Then backup the current ROM to the SD card slot. (I'f you need help make sure to Google wwjoshdew, he has tutorials doe how to flash CM10 to the S4 that should be similar to your device) after goomanager go to wipe and "slide to factory reset" not internal storage, and then wipe system under advanced wipe. Then flash CM10 and then Gapps. Now this is what I did when following my friends tutorial and the wwjoshdew tutorial on YouTube. Good luck, I am no responsible if this doesn't work and bricks your phone.
Sent from my SGH-I337 using xda app-developers app
Friends,
I have been going through the forums and honestly, the more I read the more confusing it gets... I have a US LTE version (got it over EBay in india) of the shield tablet, I had installed all updates up till the 2.2.1 hotfix. I installed CWM recovery and rooted using ADB/FASTBOOT.
I installed backed up apps using helium and then tried to get rid of the AT&T access app, cos I wanted to use hotspot feature.
I think I may have blocked some impt processes in ES TASK MANAGER because soon after, processes (playstore, text to speech, shield hub) just kept on crashing. It made the Tab unusable and so I went to CWM and did factory reset. After rebooting the setup screen was visible but processes still kept crashing. Again booting into recovery I got the android with exclamation and using the keycombo went into android recovery and wiped data&cache from here. After rebooting, I have Lollipop, stock recovery (i think) and no root (root checker says so).
The tablet now asks for OTA update 2.2 (134 mb) in size and during install throws error saying status 7 block mounted as r/w. So I am stuck now.
At the moment am downloading "productionBL-droid-signed-wx_na_do-full_ota-29979_515.3274" and will try flashing this.
(I believe this is the latest 2.2.1 update?)
Meanwhile am I doing anything wrong? How do I update in the future? I would rather let the tablet download the OTA by itself, so what do I need to do before this,assuming I have unlocked bootloader + CWM/TWRP recovery (I love TWRP but will use CWM for now) + root.?
From what I understand, if I want the device to install incremental OTA by itself then my device must be unmodified in any way?
For this I would have to install the factory image right? Does this remove custom recovery and root?
When is it absloutly necessary to wipe dalvic cache or any other cache?
Based upon your replies I will have more questions....
Thanks
Alden