So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Fastboot oem unlock
daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
Will that unlock the bootloader? Because I rather keep it locked for warranty!
Thanks
Try using RA recovery instead. You can install the last stable version through ROM manager.
fzr-r4 said:
Try using RA recovery instead. You can install the last stable version through ROM manager.
Click to expand...
Click to collapse
Did do it but it doesn't alway boot into recovery. It usually boots with a Android+triangle+! . If it does boot in recovery, it says signature verification error.
i.mac said:
So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Click to expand...
Click to collapse
hints on rooting without unlocking bootloader:
http://forum.xda-developers.com/showthread.php?t=792016
general Nexus One wiki:
http://forum.xda-developers.com/showthread.php?t=744720
besides I would not worry about unlocking the bootloader (fastboot oem unlock); it has been proven several times that HTC will honor the warranty if the device has a hardware failure, even if the bootloader is unlocked.
it also seems to be the easiest and safest way to get to root
... on another note... you want your thread to be in Q&A, not development. a moderator will probably move your thread soon.
daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
this. only. this.
I feel the guy (or gal). I like that my initial "X" screen doesn't have the unlocked icon on it. Big deal? I guess not? Personal preference? Yes.
I too like the boot logo with out the padlock, it looks tacky.
The one time I tried clockworkmod, it messed my phone up, I always go with RA's recovery.
Sent from my Nexus One using XDA App
Google's stock ROM overwrites the recovery at boot. That is why your RA or ClockworkMod is not sticking. As a workaround, you should flash your recovery before rebooting into it else you will boot into the stock one.
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
1) did you unlock the bootloader (fastboot oem unlock)? -- i recommend it
2) which version of amon_ra are you using?... all above 1.8 (i am using 1.9 alpha) allow flashing unsigned *.zip files
3) make sure you have downloaded the CORRECT amon_ra recovery *.img file (for NEXUS, any other will not work)
4) rename the AR recovery file to recovery.img (for easier typing and error minimization when flashing in fastboot) then put it in a folder where fastboot can find it
5) fastboot flash recovery recovery.img
6) flash a ROM of your choosing (i like CM6) - make sure it's fully downloaded and the zip file is not corrupt (= check the md5 sum)
7) flash in amon_ra recovery
8) if you use CM6, have gapps ready (http://wiki.cyanogenmod.com/index.php?title=Gapps) and flash immediately after CM6
9) reboot
i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
Get Amon RA 1.9a like so (has instructions for locked bootloader):
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
I use RA 1.8.0.1 to skip around signatures. I'm not unlocked and haven't had issues flashing or the phone unrooting.
Sent from my Nexus One using XDA App
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
You just didn't follow instructions. As someone posted, follow the link for the XDA Wiki recovery images. You missed the part where you have to remove two files, or it restores the recovery image. /!\ symbol = stock recovery; the system restores it automatically if you don't remove the two files.
So right now, read the guide, re-flash RA, remove the two files, then your recovery will stick.
As for one this-or-that ROM doesn't install; ask in their thread.
khaytsus said:
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
Click to expand...
Click to collapse
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
crachel said:
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
Click to expand...
Click to collapse
They denied my warranty (trackball does not scroll downwards anymore) stating they would have to charge $200 for the repair. But, I found a local shop that will do it for $40 and have it done in an hour. I have no regrets unlocking my bootloader, that is why I bought this phone.
I do believe it is the best method, and I would not abuse it just for warranty claims - in hopes that there will be another device with this ability.
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
wdfowty said:
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
Click to expand...
Click to collapse
To each his or her own, but I have the potential of my phone fully available. If I'd gotten the N1 in January, I may have unlocked the bootloader.
Since there were good root options when I got the phone without unlocking the bootloader, though, I was happy to go that route.
Sent from my Nexus One using XDA App
Related
Hi there,
I've just installed CM 6.1.1 via Amon Ra's recovery. CyanogenMod is pretty damn good I must say. At any rate, I got interested in the ClockWork ROM manager app and decided to give it a try. Seemed to install OK from the first menu item but (foolishly foolish now it seems) I didn't do anything to remove Amon Ra's original recovery before installing via the menu.
At any rate, any of the options I choose from the Flash ClockworkMod Recovery to require a reboot into the recovery don't work. "Reboot into recovery" and "backup current ROM" reboot and intitally give me the regular Nexus One splash (with unlock icon) then go to a black screen. I can still get to the regular bootloader screen by holding the trackball and pressing power but going to HBOOT gives me a blackscreen on reboot too.
I've given the forums a pretty good trawl but haven't found any answers so far. I wondered about flashing back to a stock bootloader but haven't found any instructions that don't also require flashing back to the stock ROM also.
Can anyone tell me how to flash the bootloader properly/fully (with ClockWork) given the fact that I appear to have broken it. Any help would be greatly appreciated - I really like the idea of being able to use the ClockWork ROM manager!
Use fastboot to flash an SLCD compatible recovery.
Blackscreen means that the SLCD driver is missing and cannot correctly display the recovery.
The compatible recoveries are Amon_ra 1.9 alpha and above and only the latest clockworkmod recovery (which is only available through a certain menu in the ROM Manager app)
Wrong forum bud but here you go:
1) Download this
2) Reboot to bootloader (Open up a cmd window in your sdk/tools/ folder and type 'adb reboot bootloader')
3) Copy recovery-clockwork-2.5.1.0-passion.img to the tools folder.
4) Verify fastboot recognises your device: 'fastboot devices'
5) Issue command 'fastboot flash recovery recovery-clockwork-2.5.1.0-passion.img'
6) Finally reboot using 'fastboot reboot'
You should then be able to use ROM manager just fine
Edit: Or follow the above post using the Rom manager gui.
Wrong forum! Doh! Apologies. Just noticed I'm now listed below this thread: "Thread DELETED/Locked??? >>>> This is DEVELOPMENT section not Q&A/General!!!! <<<<" Hope I don't get whacked with the ban hammer.
Thanks for the amazingly fast replies guys. Tried flashing the clockwork .img file (not using adb but linux-fastboot seems to work OK on my Ubuntu install) and rebooted from the bootloader with the HBOOT - recovery option and tried fasboot-linux reboot from terminal. Still getting a black screen. Same with reinstalling Clockwork recovery from the GUI. Hmmmm.
Incidentally, is there anyway to tell from the bootloader screen what recovery flashes are installed?
LargePiece said:
Wrong forum! Doh! Apologies. Just noticed I'm now listed below this thread: "Thread DELETED/Locked??? >>>> This is DEVELOPMENT section not Q&A/General!!!! <<<<" Hope I don't get whacked with the ban hammer.
Thanks for the amazingly fast replies guys. Tried flashing the clockwork .img file (not using adb but linux-fastboot seems to work OK on my Ubuntu install) and rebooted from the bootloader with the HBOOT - recovery option and tried fasboot-linux reboot from terminal. Still getting a black screen. Same with reinstalling Clockwork recovery from the GUI. Hmmmm.
Incidentally, is there anyway to tell from the bootloader screen what recovery flashes are installed?
Click to expand...
Click to collapse
Oh wait, your HBOOT is black or your recovery? Try a direct "reboot recovery" command from your terminal to see if the recovery now works...
If it's only the hboot, you should be able to flash the 0.35 hboot which supports SLCD
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Only clockwork 2.5.1.1 and above, our Amon 1.9 and above is compatible.
Open ROM Manager, and flash a newer version. The option is under All Clockwork Recoveries, at the bottom of the initial page...
Sent from my Nexus One using XDA App
RunTimeWorld said:
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Click to expand...
Click to collapse
What?!
Was this added at the same time as the laser beam?
Sent from my Nexus One using XDA App
RunTimeWorld said:
or fastboot oem rebootRUU - if your device's bootloader is unlocked, else be aware that any fastboot command will unlock it, even if you don't apply the oem unlock.
Click to expand...
Click to collapse
Utter crap.
Righto so I've already flashed to the latest version of clockwork (from the GUI) which is where things started getting funky. When I get back to my laptop ill try rebooting into recovery instead of using hboot. And perhaps try flashing to hboot 3.5 if you guys think this might help. I do still get a blackscreen from using the reboot into recovery option from theROM manager GUI.
EDIT: Oh cool. Just read your post more carefully danger-rat. Went to 2.5.1.1 of clockwork and I'm all sorted when booting into recovery from the GUI. Not sure about hboot but I guess if its working from the GUI its all good. ') Thanks for the help people.
EDIT EDIT: I really should try things before posting, anyways hboot works good too now! Niiiiice.
I rooted and flash my nexus one with a rom that was based on the cm7 nightly. It installed completely and I rebooted. It gets past the static x but loops in the moving x. I've tried so many things over the past 8 hours I need help to get a rom working on this. I tried going through the fastboot. Tried using recovery to update from sdcard and I'm having no luck getting this to work again. Hopefully someone on here knows how to fix my problem so I can get a working rom on my phone. Thanks everyone.
Did u install recovery (amon or clockworkmod?? If you did just dload another rom, wipe and flash again
N1
When I originally did the install I installed clockwork and did a back up. When I go into recovery all I can do is either wipe data, update from sdcard and wipe cache. I'm about ready to pull my hair out. I have no clue what went wrong. I've installed new roms on my old phones and no problems, I follow all the instructions.
nandroid, wipe all, retry flashing.
or restore your nandroid backup.
Looking at "adb logcat" while its booting will pinpoint the error.
I've tried to go through fastboot to use my recovery image but I get failed (remote: signature verify fail). I don't know how to get into nandroid and my computer I can only use the fastboot not adb to use logcat. Is there a way to use the fastboot that doesn't come up with the signature fail. I really don't know what happened. What other ways can I use my recovery image if I can't do it from the physical phone?
Sounds like a bad backup. DId you verify MD5?
If you want to start over..
Download AmonRa Recovery 2.2.1. From thread below...
http://forum.xda-developers.com/showthread.php?t=611829
With phone in fastboot mode and connected to PC via usb:
1. Command Prompt: fastboot devices (make sure device is connected)
2. Make sure recovery image file is in your SDK/tools folder
3. Make sure your working directory is SDK/tools folder
4. Command Prompt: fastboot flash recovery recovery-RA-passion-v2.2.1.img
5. After flash is done, reboot to recovery.
6. Wipe everything.
7. Re-flash your ROM.
You can always go back to Clockworkmod if you want. Just re-flash clockwork recovery.
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Your getting this error when flashing what?
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Did you unlock your phone (fastboot oem unlock) or did you just root it?
If you haven't unlocked your phone, perhaps try that then use the previous instructions to flash clockwork or amon recovery image.
link for reference
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Make sure you add to his "Thanks" meter! BTW. That would have been my next suggestion...
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Make sure you add to his "Thanks" meter! BTW, that would have been my next suggestion...
Sorry for the Double Post
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Glad to help. I think we've all had those "OMFG HOW DO I FIX THIS" moments.
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.
Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!
Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.
Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?
If you have the HTC ge ...I asumme since you're experienced you have knowledge of adb and fastboot...if so all it takes is fastboot oem unlock
Then flash recovery of your choice and so on
Nxxx said:
Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?
Click to expand...
Click to collapse
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.
mickey4mice said:
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.
Click to expand...
Click to collapse
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".
mickey4mice said:
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358781
Got it from this post. I also used to stock factory image from that post as well.
I'm frustrated because my battery life is pretty bad and when I check stats, the kernel is consuming 25% of battery. Any idea what gives?
mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.
mickey4mice said:
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.
Click to expand...
Click to collapse
Yeah it may have said failed. But everything seems to have worked. I'm just trying to get back to stock bc I may need to RMA.
You do know the Android on it's back is the stock recovery?...
EddyOS said:
You do know the Android on it's back is the stock recovery?...
Click to expand...
Click to collapse
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
---------- Post added at 08:32 PM ---------- Previous post was at 08:17 PM ----------
mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
Click to expand...
Click to collapse
Arrrhhh...never mind. I finally brought up the recovery menu by pressing the power+vol up/down buttons REALLY REALLY HARD! I tried this combo for 3 days without success, I think the vol up button is finally loosening up, weird I don't have any problem using it on the phone, just in the recovery mode.
Stock recovery really doesn't have anything you can do In it
a box of kittens said:
Stock recovery really doesn't have anything you can do In it
Click to expand...
Click to collapse
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back and forth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.
mickey4mice said:
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back andrth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.
Click to expand...
Click to collapse
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"
a box of kittens said:
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
I don't want to permanently flash a custom recovery like CWM, only want to sideload it to flash SuperSU and gain root. The command I use is "fastboot boot recovery.img" where recovery.img being the name of CWM. Don't know why it's not working though.
mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?.
Click to expand...
Click to collapse
Yes, that's the stock recovery. You then have to press power + volume up (in the case of the Nexus 4, for example). You have to manually flash CWM as you would for the normal One
e.g. fastboot flash recovery recovery.img
You apparently can no longer 'boot' into CWM - you have to flash it