Is the a way to root with no custom recovery? i just dont want a custom ROM recovery or kernel.
You can use fastboot to boot into CWM recovery without installing it on the phone;
try:
fastboot boot recovery-clockwork-3.0.2.4-crespo.img
If you´re using the img file as I did, of course.
so just skip the actual installing part? And just load it.
could you point me to the guide you used ?
The ns automatically reinstalls the stock recovery at boot as long as the recovery.sh file isn't modified. You can flash cwr, install su then reboot to get stock recovery back. Just don't flash a pre rooted rom.
Sent from my Nexus S using Tapatalk
Sent from my Nexus S using Tapatalk
I had a HTC supersonic before the nexus s 4G and a Samsung Moment before that and I have Rooted probably 10 phone but mainly thous models sep for a epic and some intercepts but never used Linux commands so what I'm saying is I'm still a noob in the coding department not asking for a step by step walk through by maybe a link to a good guide. Thanks in advance
It ain't rocket science. Just follow the how to guide. You're acting like it is a bigger deal than it actually is. Its not difficult
Related
So I traded my galaxy s 4g on craigslist about a month ago for a nexus s (t-mobile) which besides the 4g antenna is 100% better in every way possible. I absolutely love the phone. It came previously rooted which I was ok with. It is on 2.3.3. Not sure what method was used to gain root. Now that the backstory is done here is my dilemma:
I constantly get the update message. I guess I wouldn't mind so much if I could just get rid of the message but the problem isn't just that. I also want to be on the latest greatest version of android. So I've read a bunch of walkthroughs and various ways to update to the latest firmware on a custom rom like cm7 and keep the root, or un root and go to stock 2.3.3 and manually update to stock 2.3.4.
I need an opinion on which would be my easiest way (new to android previous iPhone jail breaker) to get to 2.3.4?
You cannot lose root on a nexus s. No matter the update you can always reroot as its a developer phone with an unlocked bootloader.
Sent from my PC36100 using XDA Premium App
Do the update
Download su.zip and the right cwm recovery image for your phone
Mount USB storage
Copy su.zip on sdcard and recovery image goes into /tools folder inside your adb/sdk folder on pc
Boot into fastboot, vol up+power
In a cmd prompt do 'fastboot devices' should return a number (this step is just to check if fastboot/adb is working properly)
'fastboot flash recovery recoveryimagename.img'
Choose recovery option on phone
Install su.zip from sdcard
Done
Sent from my Nexus S using XDA App
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
stompincc said:
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i'm pretty sure that's just cause you're on a custom rom. flash a stock rom and the update should work fine
I just bought this phone yesterday and it is the i9020t (AWS version). The phone function works fine but every so often every application fails and gives an error asking to report it. I cannot manage to change the screen lock, it just comes back after reset. I only managed to remove it once. Also I cannot reset it no matter what I do, whether it is from settings or from the recovery menu. All data seems impossible to remove. How is this happening?
So Far:
-I got the boot loader unlocked (does this mean it is rooted yet?), failed to install superboot.zip
-Got the adb setup with using only part of the sdk files
(http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/)
Now I have tried this:
http://forum.xda-developers.com/showthread.php?t=884093
I can't get clockworkmod on here, I don't even know what it is exactly.
I believe I need to flash the phone onto stock firmware, the current seems corrupt as I can't do any changes such as password or wipe data.
More info on phone:
Android version: 2.3.4; Baseband version: I9020XXKD1; Kernel version: 2.6.35.7-ge382d80 [email protected]#1; Build number: GRJ22;
BTW I am on Mac OS X but can access a PC if I really have to.
Anything else I need to provide?
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
He said weeny hah but other than that he's right
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weeny very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
He said weeny hah but other than that he's right
sent from my nexus s on a kang from simms
Click to expand...
Click to collapse
Owned by auto correct
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It was a messed up phone. Returned it. Nothing would write onto sdcard. Which explains why it would not allow many functions that require data retention.
After much consideration I decided to root and install ICS from http://forum.xda-developers.com/showthread.php?t=1354263 following this guide.
I rooted successfully and used ROM Manager to make a backup. When I came to installing the mod, my phone is just stuck on this screen -> http://dl.dropbox.com/u/7960393/IMG_20111125_125549.jpg
It has been like that for about 15 minutes. Can anybody help me?
Thanks
EDIT: Apparently clockworkmod recovery got wiped :s
Flash a new cmw with fastboot and you'll be set.
Sent from my Nexus S using xda premium
Have you tried do go through the steps of the one click root process again? (assuming that is how to you rooted your phone the first time)
If you can boot into the OS, flash cwm twice in a row using Rom Manager. It takes two flashes to get the recovery to stick.
If no OS, push the cwm file using adb.
Sent from my Nexus S 4G 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?
Hello,
I recently unlocked my bootloader and installed the CWM recovery to install custom kernels for overclocking (my htc one mini is not rooted). So I went for the JmzM4_Kernel-09-4-13. And since I installed it I am in a F$%&/&%$ reboot loop. I already wiped the cache and dalvik cache twice but it doesn't help. I searched already for answers on google but I didn't find what needed, so I landed here.
Hope somebody can help me to get out of this reboot loop and get a normal smartphone again
Thank you for your attention
Here are the bootloader specs:
***Tampered***
***unlocked***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP-v19.2.0268.0927
OS-2.12.161.2
eMMC-boot 1024MB
Nov 26 2013,22:09:21.0
Did you flash the boot.img using flashboot from the kernel zip? also are you using jelly bean 4.2.2? because that's what it was built for.
Also there are no options to over clock using this kernel...
Sent from my HTC One using Xparent Green Tapatalk 2
Thank you for your reply :good:
Yes I did flash the boot.img with flashboot, but I have android 4.3 and sense 5.5 on it. Is that maybe the problem?
A friend of me said that if I flash an incompatible kernel on my device, it would be dead. Is that true? I don't think so because I still have acess to the bootloader and CWM recovery .
shouldn't brick your phone, but your gonna need to flash a kernel compatible with 4.3. There isn't one in this forum, but if you ask one of the rom devs on here really nicely they may provide a compatible kernel from one of their rom releases. Else your gonna have to re flash your rom..
Sent from my HTC One using Xparent Green Tapatalk 2
And how do I find the original/stock kernel for htc one mini 4.3 ?
Can I install HTC one kernels or are the two phones completely different?
I already searched on the net for htc one mini kernels. There is almost nothing !!!!!
Quent1_Lat said:
And how do I find the original/stock kernel for htc one mini 4.3 ?
Can I install HTC one kernels or are the two phones completely different?
I already searched on the net for htc one mini kernels. There is almost nothing !!!!!
Click to expand...
Click to collapse
there are NO 4.3 kernels as of yet. I'm saying you need ask a dev to make you one,but I doubt they'll do it unless you ask really really nicely. Your most likely going to have to flash a whole rom..
AND NO HTC ONE AND HTC ONE MINI A VERY DIFFERENT. DO NOT USE ANY KERNEL UNLESS IT'S MADE FOR THE ONE MINI. OR YOU MAY BRICK YOUR PHONE.
Sent from my HTC One using Xparent Green Tapatalk 2
RuffBuster said:
there are NO 4.3 kernels as of yet. I'm saying you need ask a dev to make you one,but I doubt they'll do it unless you ask really really nicely. Your most likely going to have to flash a whole rom..
AND NO HTC ONE AND HTC ONE MINI A VERY DIFFERENT. DO NOT USE ANY KERNEL UNLESS IT'S MADE FOR THE ONE MINI. OR YOU MAY BRICK YOUR PHONE.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
ok, I think I will go for the second option: I will flash a rom.
So here my question: What kind of rom do I have to flash, to come out of the bootloop?
I am a beginner in this kind of thing so please explain it to me step by step.
Quent1_Lat said:
ok, I think I will go for the second option: I will flash a rom.
So here my question: What kind of rom do I have to flash, to come out of the bootloop?
I am a beginner in this kind of thing so please explain it to me step by step.
Click to expand...
Click to collapse
Personally I would only recommend the one I am currently using, as I haven't tried any others except WWE Stock 4.2.2 by trigger, which is the base of what I'm using, which is Magio R3 with the JMZ Kernel. I used the guide below which worked without problems. BUT BEFORE YOU DO MAYBE MAKE A POST ABOUT CHANGING FROM 4.3 TO 4.2.2 JUST BECAUSE I AM NO EXPERT, AND I'M UNSURE IF THERE COULD BE ISSUES WITH THIS? THOUGH I THINK IT SHOULD BE FINE.
Else stick with the 4.3 Stock ROM by Trigger though this is untested by me. Also skip the kernel installation if using the 4.3 ROM.
THE GUIDE:
Ecstacy42 said:
Don't do it if you don't feel comfortable.
1. Unlock your bootloader here. Select "All Other Supported Models" and follow the instructions.
2. Download the Rom, Kernel, and a recovery, verify the MD5 checksums, and then copy the rom and kernel zips to your internal SD card. I'd recommend one of the WWE versions as they don't have a lot of the AT&T bloat.
3. Boot into the bootloader (it says how in the guide showing you how to unlock your bootloader)
4. Select fastboot, plug your phone into your computer.
5. Type "fastboot devices" to make sure it's connected, then type "fastboot flash recovery whateverrecoveryyouused.img".
6. Boot into recovery. Make a backup. Then wipe system, data, cache, and dalvik cache.
7. Reboot into fastboot, then type "fastboot flash boot boot.img" using the boot.img from the Rom you downloaded.
8. Reboot into recovery and install the rom zip using TWRP/ClockworkMod.
9. Reboot into fastboot and type "fastboot flash boot boot.img" using the boot.img from the kernel.
10. Reboot into recovery and flash the kernal zip.
11. Start up your phone, if you flashed a DeOdexed Rom it'll take a little while to boot up.
I'm not sure if you have to flash the boot.img from the rom, then flash it, then flash the boot.img from the kernel and then flash it, but it's best to follow the directions and avoid potentially causing problems.
Click to expand...
Click to collapse
Sent from my HTC One using Xparent Green Tapatalk 2
RuffBuster said:
Personally I would only recommend the one I am currently using, as I haven't tried any others except WWE Stock 4.2.2 by trigger, which is the base of what I'm using, which is Magio R3 with the JMZ Kernel. I used the guide below which worked without problems. BUT BEFORE YOU DO MAYBE MAKE A POST ABOUT CHANGING FROM 4.3 TO 4.2.2 JUST BECAUSE I AM NO EXPERT, AND I'M UNSURE IF THERE COULD BE ISSUES WITH THIS? THOUGH I THINK IT SHOULD BE FINE.
Else stick with the 4.3 Stock ROM by Trigger though this is untested by me. Also skip the kernel installation if using the 4.3 ROM.
THE GUIDE:
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
ok thank you,
but when I have the rom for my htc one mini, how do I place it in the main storage ( as a zip ). It can boot properly and reboots before my computer can detect it.
And is this Magio r3 rom compatible with the htc on mini? On the website it is shown that it is for htc one XL. And it also says that the recovery has to be the TWRP recovery and I have the CWM recovery.
Thank you for your answer. :good:
Quent1_Lat said:
ok thank you,
but when I have the rom for my htc one mini, how do I place it in the main storage ( as a zip ). It can boot properly and reboots before my computer can detect it.
And is this Magio r3 rom compatible with the htc on mini? On the website it is shown that it is for htc one XL. And it also says that the recovery has to be the TWRP recovery and I have the CWM recovery.
Thank you for your answer. :good:
Click to expand...
Click to collapse
Everything you need is here on the XDA, "HTC One mini" section. ONLY USE ROMS WHICH ARE SPECIFICALLY FOR THE "ONE MINI". NO OTHER. EVER.
Just use this one it's 4.3 stock. You flash it as a ZIP from either CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2575766
And read the OP!
Also once this is working. DON'T FLASH YOUR PHONE EVER AGAIN. YOU CLEARLY HAVEN'T READ UP ENOUGH AND DON'T CARE ABOUT YOUR PHONE. No offense but do you really want a $500 paper weight?
Sent from my HTC One using Xparent Green Tapatalk 2
I used recovery to mount usb storage worked for me
Sent from my HTC One mini using XDA Premium 4 mobile app
RuffBuster said:
Everything you need is here on the XDA, "HTC One mini" section. ONLY USE ROMS WHICH ARE SPECIFICALLY FOR THE "ONE MINI". NO OTHER. EVER.
Just use this one it's 4.3 stock. You flash it as a ZIP from either CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2575766
And read the OP!
Also once this is working. DON'T FLASH YOUR PHONE EVER AGAIN. YOU CLEARLY HAVEN'T READ UP ENOUGH AND DON'T CARE ABOUT YOUR PHONE. No offense but do you really want a $500 paper weight?
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
But how do I flash the odex rom?
I already tried to flash the whole zip file with fastboot, but the file is too big. the cmd says Failed(remote:data lenght is too large).
So how do I bring this rom to recovery from my computer?
Thank you for your answer.
RuffBuster said:
Everything you need is here on the XDA, "HTC One mini" section. ONLY USE ROMS WHICH ARE SPECIFICALLY FOR THE "ONE MINI". NO OTHER. EVER.
Just use this one it's 4.3 stock. You flash it as a ZIP from either CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2575766
And read the OP!
Also once this is working. DON'T FLASH YOUR PHONE EVER AGAIN. YOU CLEARLY HAVEN'T READ UP ENOUGH AND DON'T CARE ABOUT YOUR PHONE. No offense but do you really want a $500 paper weight?
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
But How do I flash my rom.zip? I cannot flash it from fastboot because it shows an error message in the cmd : Failed(remote: data length is too high). How do I get this $%&%&## file on my recovery or how do I flash it directly from my computer. I already searched the web on how do I do this. But no detailed or specific answer to my problem.
Please explain it to me step by step again :good:
sahilg009 said:
I used recovery to mount usb storage worked for me
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I already tried this version. I went into my CWM recovery in mout and storage and tried the "mount /external_sd" but it shows me the error message: Error mounting / external_sd!
But thank you anyway :good:
Quent1_Lat said:
I already tried this version. I went into my CWM recovery in mout and storage and tried the "mount /external_sd" but it shows me the error message: Error mounting / external_sd!
But thank you anyway :good:
Click to expand...
Click to collapse
You need to "push" the zip to your internal memory. Put your zip in your ADB fastboot folder on your computer. Then use command "adb push romname.zip /mnt/sdcard/". Then install the zip from cwm or twrp recovery. And flash the boot.img from zip with ADB fastboot...
Sent from my HTC One using Xparent Green Tapatalk 2
RuffBuster said:
You need to "push" the zip to your internal memory. Put your zip in your ADB fastboot folder on your computer. Then use command "adb push romname.zip /mnt/sdcard/". Then install the zip from cwm or twrp recovery. And flash the boot.img from zip with ADB fastboot...
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I tried adb push but the cmd didn't reconize it. It says (from german, I try to translate it) : the order adb push is either wrong writen or it couldn't be found. So how do I use or reactivate adb push ? or maybe there is another way to push the file in the htc ( for example with a program ).
Thanks in advance
Quent1_Lat said:
I tried adb push but the cmd didn't reconize it. It says (from german, I try to translate it) : the order adb push is either wrong writen or it couldn't be found. So how do I use or reactivate adb push ? or maybe there is another way to push the file in the htc ( for example with a program ).
Thanks in advance
Click to expand...
Click to collapse
flash the twrp recovery.
abzboi said:
flash the twrp recovery.
Click to expand...
Click to collapse
Already done. But nothing changes. still have the same problem.
But cool recovery
Quent1_Lat said:
Already done. But nothing changes. still have the same problem.
But cool recovery
Click to expand...
Click to collapse
Does the command "ADB devices" without the "" show your device listed?
Sent from my HTC One using Xparent Green Tapatalk 2