Database Develop

[Q] Can not unlock Bootloader

I am almost too chicken to post because reading all the developer threads I feel like such a noob.
I recently rooted my Nexus One, thanks to a developer that created a painless one button rooting app. The problem is after downloading and installing many apps that require superuser access I am finding out that I am limited in what I can do without unlocking the bootloader.
I want to find a theme that replaces the standard white bar "which will cause screen burn" with a black bar.
I backed up all my apps, "Titanium Back Up"
I backed up my ROM??? "Maybe not" using a program call Rom Backup. "I have not figure out how to to nandroid backup "not sure the right name"
I googled found many procedures on unlocking the bootloader but I can not get it work.
Download ADK
Found a place that has Fastboot download it
I even found out I need to copy file from ADK folder to the Fastboot folder
Held down the power button trackball got the correct screen "even though my old eyes have a hard time reading the little character"
connected my phone
Ran the batch file
It returns saying wait for device.
The device is connected, in the right mode, my device manage says the is an Android device connected.......
But no matter what I do I can not get the screen warning me that to unlock my bootloader I void my warranty.
I found here some theme labled that hey work Nexus One 2.2 and I want to try them but Metamprgh will not load new themes on a radio that has a locked bootloader.
I am not worried about losing my warranty I live in Canada if I ever need warranty work it be a hassle anyway.
I thought unlock the bootloader.
When the phone powers up login my Google Account, reload Titanium Back up to restore my my phone.
Back up the Rom once more using Rom Backup if I want to recover my stock Rom
Run Metamorph and play with the themes
But I can not unlock the bootloader ....... "waiting for device"
How can I unlock the Bootloader, I there a more current method?
What can I be doing wrong I see a device in my Device Manager?
Will my method for restoring my phone work, never done a full phone wipe?
FYI this forum is scary there should but a developer and a Noob section.

You don't need to unlock your bootloader. My bootloader is locked and I'm rooted. It seems like you're missing superuser.apk. You need that too allow all of the programs like ROM manager and Titanium Backup root permissions. I'm not sure how the one click app works but I know that it probably should have installed the superuser application to allow those apps root access. Check and see if its in your application draw. You might want to try "one click rooting again" because it seems like it didn't work.
Side note: Titanium Backup does not back up your ROM. It just backs up apps and their data stored on your phone so it can be restored when you flash a new ROM. The way you back up your ROM is through the android custom recovery using the nandroid feature.

Thanks Magma,
Yes Superuser is installed.
A program wants superuser access I can grant it.
Metamorph does do several checks and it needs superuser access.
It is my understanding superuser access gives apps access to system hardware but if you want to use Metamorph to change the standard Android Shell that is going to modify your ROM and you will need and unlocked bootloader.
Here is what happens when I run Metamorph it finds the zipped files on my SD card, I select a file, it exacts the package, I say update al .... PLEASE WAIT for 20 or 30 minutes, it may then tell me to reboot but nothing happens my theme is still stock Android 2.2
This is where you can find out about and download the One Click Root App, it is in this section themes and apps.
It roots you device but leaves the bootloader alone
I know titanium backup just restores all your applications and data. The way I understand it if I ever need to do a master reset, I login Google, download Titanimum back up use it to restore every thing else. Yes which every ROM I was running will not be touched.
I am pretty sure I need to unlock the Bootloader.
But to unlock my Bootloader I just as I said get please wait I tried everything.

Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes

ilostchild said:
Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes
Click to expand...
Click to collapse
Wow lot to digest. I do have and install Android SDK the instructions in the tutorial I googled said I needed it, The Fastboot command needed files in the ADK directory.
The thing is since my command window did not see a device,
With your Nexus One in bootloader mode and connected to your computer via USB cable, go back to the command prompt and type “fastboot-windows oem unlock”.
Would even be able to flash anything?
At the end of the day I am very happy with Android 2.2 and I do not think I want custom roms at least for now. All I want is to get Metamorph to work so I can change how it looks.

try to type fastboot oem unlock

You do not need to unlock.
You used the one click root.
Now download Rom Manager and flash the Clockwork Recovery.
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms.
And you still have a locked bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically.

try to type fastboot oem unlock (Done but it just responds wait for device)
Now download Rom Manager Done and it seemed to back up my OEM Rom no problem and flash the Clockwork Recovery. Question is this over writing existing Nexus One ROM because as I said since really have nothing against OEM ROM I would like to keep it?
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms. At this point my phone would be powered up with the Clockwork Recovery ROM? I want to use Metamorph to flash themes on top of the Nexus One ROM
And you still have a locked bootloader.Well if Clock Recovery does the job and at the end of the day I get OEM 2.2 ROM which I can theme with Metamorph I am ok never unlocking the Bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
Yes Understood I have the program
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically. But as the questions above do I really what to keep the Clockwork Recovery ROM. I do not know what the Clockwork recovery ROM does but I do just want to theme my Nexus One OEM ROM.
So let me see if I got the steps straight.
Head to the download section find the Clockwork recovery ROM.
Copy it to my SD Card.
Open ROM Manager and install it.
Reboot my Nexus One, the ROM manager forces the Reboot and I will be running my phone with Special ROM, old version of Android?
Then do I load my back my OEM ROM and modify it with Metamorph?
or is what loading the Clockwork ROM actually do is it is not a full ROM when I load it with ROM Manager what it does is add to my existing OEM ROM. This process will then let me modify the ROM with themes. When I reboot after loading the Clockwork ROM I will find the phone looks and behaves the same as always "running Android 2.2" but the Clockwork ROM will add files and when I use Metamorph it will work......
............. Man I am such a noob, but i guess at one time we were all noobs.

You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.

Clarkster said:
You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.
Click to expand...
Click to collapse
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.

Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?

AstroDigital said:
Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?
Click to expand...
Click to collapse
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
Spend a few weeks or a month reading about everything, through the whole threads before trying to jump in. That's how I learned everything.
You seem intelligent enough to do everything, but what you lack is an actual understanding of what those things are, so you just need to spend a lot more time on it.
When you do fully understand everything, it will be a breeze and you will enjoy it a lot more. You will be less likely to completely screw your phone, and if you do you will know exactly how to recover.

I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
You maybe right, maybe I should give up for now. Learn to do a backup and restore using nandroid. Just not sure how much time I am willing to invest just to gain the able to put themes on my phone.

AstroDigital said:
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Click to expand...
Click to collapse
Yeah, you shouldn't do anything yet, read up on stuff for fun until you know what is going on.
For instance, in what I quoted above, you understood the exact opposite of what he was saying.
He was upset that he didn't find out about this way to root before he unlocked. He didn't have to unlock and is now disappointed he did.

OP. What ROM are you currently running? Stock FRF91 or something else?
To my understanding you need a De-Odexed ROM to apply themes that modify the framework.

Trying to load a custom rom, wth am i doing wrong?

Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???

First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig

Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...

o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.

TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781

o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.

Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.

I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?

Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.

tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.

Trying to restore Steak 7 Wifi to stock, need help quick!

I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...

use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.

shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.

Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.

magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.

I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?

bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.

Phone not booting into clockworkmod?

Hello all.
I'm trying to update my phone (a rooted Samsung Galaxy S - GTi9000), to Cyanogenmod Nightly build. I have Mobile Odin and Rom Manager installed. And have downloaded the latest Cyanogenmod Nightly.
I have read some tutorials, but I seem to be stuck on two parts:
1) When I try to get into the clockworkmod boot recovery, it doesn't work and boots into the android recovery instead.
2) In mobile odin, when I find my file and load it, it doesn't load anything in the main list that says "kernel, system, dbdata", etc. It just says "none" in all of them.
From looking at some youtube vids at least some of them should load...right?
Now, I may well be doing something simple wrong (hopefully!), but I'm fairly new to all this and its kinda getting to me. Plus, trying to get my head around all the jargon is a bit of a challenge!
If someone would kindly take the time and patience to kindly guide me in the right direction, I would be very, very appreciative! :thumbup:

Also, because of these problems, I haven't tried flashing any roms yet for fear of bricking...

why you dont take cwm via 3 button combo?
there you can add zip and let it install.
Did you read any tutorial? I read about 5h and then i flashed it with problems and i knew what to do. Such questions should be answered in good ones.

Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?

KieranY8 said:
Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?
Click to expand...
Click to collapse
Flash a semaphore GB kernel to solve your problem from My Android Collections

Got it sorted guys.
Thankfully it was a simple fix. I removed the battery briefly earlier, but nothing happened. Took it out for a good 30-40 seconds and it finally booted into CWM Recovery!
I'm now on ICS.
Thanks a million for trying to help me.
The learning curve is beginning to flatten out!
:thumbup:

Try To reFlash
I Think that it would be best to flash the 3 odin files on again

[Q] Problems with custom rom HTC one

I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?

There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.

iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...

Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.

iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.

Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?

Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.

bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.