So I flashed clockwork when rooting and renamed the script that always reverted to the stock recovery. I could always access clockwork from the bootloader.
However I just started using rom manager. Since it made me flash the recovery again I can't access clockwork from the bootloader. Can someone offer me advice on what to do to remedy this? I want to be able to access recovery no matter what.
Sent from my Nexus S using XDA App
fchipm said:
So I flashed clockwork when rooting and renamed the script that always reverted to the stock recovery. I could always access clockwork from the bootloader.
However I just started using rom manager. Since it made me flash the recovery again I can't access clockwork from the bootloader. Can someone offer me advice on what to do to remedy this? I want to be able to access recovery no matter what.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you can't access recovery from the bootloader you probably need to flash it again from within rom manager. That happened to me once and a reflash of recovery worked.
Power button and volume up to access with phone off to get in.
so i have a tb and rooted it. no problems there. i tried a few roms switched back to stock one . then tried to flash one and i got stuck on a boot animation. couldnt get anyting to work so i ended up taking it back to stock. ive seen in recovery mode it said s-on which i figured meant not rooted... but i still have the superuser app and stuff it just wont grant access to root apps that need permission like rom manager which wont flash or reboot into recovery or anything for me now. any suggestions.. what to do or try. i tried using the same root method that worked before but it wont work this time. the phone doesnt reboot when its supposed to after the first step.
beeholtz said:
so i have a tb and rooted it. no problems there. i tried a few roms switched back to stock one . then tried to flash one and i got stuck on a boot animation. couldnt get anyting to work so i ended up taking it back to stock. ive seen in recovery mode it said s-on which i figured meant not rooted... but i still have the superuser app and stuff it just wont grant access to root apps that need permission like rom manager which wont flash or reboot into recovery or anything for me now. any suggestions.. what to do or try. i tried using the same root method that worked before but it wont work this time. the phone doesnt reboot when its supposed to after the first step.
Click to expand...
Click to collapse
S-on doesn't mean you've lost root, s-on is a bootloader unlock. Try going to tthe superuser app to see if some of the root apps are set to deny
Sent from my ThunderBolt using XDA Premium App
nope, under apps there is nothing, logs has nothing, and the settings i looked through.... nothing
beeholtz said:
nope, under apps there is nothing, logs has nothing, and the settings i looked through.... nothing
Click to expand...
Click to collapse
Can you boot into CWM?
Sent from my ThunderBolt using XDA Premium App
no i can boot into recovery but i cant flash a file of course, and all it tries to do is check the pmg005 zip file and do an update in which it doesnt even update everything.. or at least last time it didnt. so i was unsure if i should just go back to stock and then reroot
beeholtz said:
no i can boot into recovery but i cant flash a file of course, and all it tries to do is check the pmg005 zip file and do an update in which it doesnt even update everything.. or at least last time it didnt. so i was unsure if i should just go back to stock and then reroot
Click to expand...
Click to collapse
Why do you still have a pmg05.zip file at the root of the sdcard for it to scan? Need to delete, move, or rename that to get to clockwork recovery
Sent from my ADR6400L using XDA App
Sounds like you've missed a step or done something wrong to not get s-off
Sent from my ADR6400L using XDA App
haah youre probably right. i have already removed that zip file from the root directory, and i did have it set to s-off however after i reloaded (im assuming) thats possibly what is causing it. thanks for the help guys, much appreciated
ok so when i try to boot into cwm or recovery it wont even let me pick anything it just has hboot highlighted and tries to read the pmg005 zip file that is not there fails... then i can reboot, reboot hboot, but not do recovery to flash anything,
You have to redo the rooting procedure. It sounds like you flashed a shipped RUU and rewrote all the partitions.
i tried rerooting using the same 3 step method I found on Droid forums. it wouldn't reboot when its supposed to after step 1. should I just try another method
I have an inspire that I got T-mobile working on it and after I rooted the phone i didn't flash it to a custom rom. So now I want to get ClearDroid in it, but when I tried to go to ROM manager there wasn't a pop-up saying there's an update for clockworkmod recovery.
Now I don't know how to get clockworkmod installed. I've tried looking in the forums for solutions but still no luck. I also want to know if I did something wrong with the rooting.
I would really appreciate the help.
Wel can you tell me what the first entry is in your rom manager? Mine is flash clockwork recovery. Give that a go and see if it works for you.
What root method did you use? I used ACE HACK KIT and if I recall it put a clockwork recovery on my device.
Spark is correct...hack kit does add a clockwork recovery. Start adb and type adb reboot recovery to boot into it. Or, install Droid explorer on your pc and click tools, install custom ROM.
http://de.codeplex.com/releases/view/50997
Sent from my wife's nemesis using XDA Premium App
I used Bubby's simple root program. It's weird tho because I first used it on another inspire and I was able to root it and flash it to another ROM. The second time I rooted on a different inspire(the one with the T-mobile) I can't flash it to a different ROM.
I've confirmed with root checker that the phone is rooted and I was thinking if it's advisable if I should root it again.
One more thing when I tried to go into boot mode and there was an orange blinking light. I just took out the battery and got it working again. What I heard is that it could be a sign of semi-bricking the phone.
Might be best to flash back to stock using the RUU in Bubby's one click, however, you may lose the ability to use T-mobile. I'll think about it after I get some sleep.
Sent from my Desire HD using XDA Premium App
I was also thinking about flashing back into stock and after that just try to root everything again to work with T-Mobile
So, I have a strange issue that has me confused.
Got sidekick off craigslist, used the hamidall wipe to put it back to factory.
Rooted. Fine.
CWM. Fine, also up update.zip in root of SD card.
put smooth maximus rom in root too. Fine.
Boot to recovery. Choose update. Boots to clockworkmod.
Flash rom zip.
finishes successfully.
Reboots.
Sticks on boot screen, and dosn't go anywhere.
Come on guys, i want to de-bloat this thing.
There is like10 plus threads of these please look a little and look T a rom first and read the steps
Sent from my SGH-T839 using XDA App
Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app
Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.
You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks
OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)
Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app
TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app
briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.
On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.
Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app
Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.
So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app
Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app
Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?