Database Info

Recovery

Ok, so clockwork recovery has worked without fail for 8 months...
then today i tried to reboot into recovery (using power menu, adb etc) and it just sits on the google screen.
I have reflashed a few different recovery images and locked/unlocked the loader.
I can get into recovery only after straight after flashing the recovery, by going to the bootloader and selecting reboot (not recovery)
something is balked here, any ideas?
(i would just lock the bootloader again and take it back as faulty, but when that is done, it boots straight into recovery, i assume because there is no ROM there)

Lock the bootloader then unlock it again then reflash Clockwork.
Have you tried using the modded one on the dev forums at 4.0.0.2?

yep, im afraid ive done that... any way to reinstall the bootloader itself?

slimjimwoods said:
yep, im afraid ive done that... any way to reinstall the bootloader itself?
Click to expand...
Click to collapse
Yeah you can find the images (there was a update to the bootloader in 2.3.2 or something) and go into bootloader mode and type.
fastboot flash bootloader whatever-the-bootloader-name-is.img
My bootloader is: I9020XXKA3

any chance you could point me in the right direction of the images, google is seeming fruitless...

slimjimwoods said:
any chance you could point me in the right direction of the images, google is seeming fruitless...
Click to expand...
Click to collapse
Yup, no problem. I was just looking for it. Is the KA3 bootloader the version you currently have? Because I know it was optional to update the bootloader, especially for non-stock ROM'ers.
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90

currently I have I9020XXJK1...

slimjimwoods said:
currently I have I9020XXJK1...
Click to expand...
Click to collapse
Yeah thats the older bootloader that came with the stock phone. The KA3 bootloader is the newest bootloader that was included with the 2.3.3 OTA. Just make sure you're using a I9020 model. Which you probably are since you're in the UK so you shouldn't have anything to worry about.

excellent thankyou, and im right in saying
fastboot flash boot *above file*...

slimjimwoods said:
excellent thankyou, and im right in saying
fastboot flash boot *above file*...
Click to expand...
Click to collapse
1. put bootloader.img into \android-sdk-windows\tools\
2. command prompt, cd C:\android-sdk-windows\tools\ (or where ever your SDK folder is)
3. put phone into bootloader mode if it isnt already
4. fastboot flash bootloader bootloader.img
5. reboot bootloader
6. check bootloader version
p.s. verify its MD5 hash before you fastboot it

aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you

slimjimwoods said:
aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you
Click to expand...
Click to collapse
good luck

clockwork is fine now, flashed CM7 nightly but it just sat on the black Google screen again... going to try something a bit more stable... thankyou for your help on this

its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,

slimjimwoods said:
its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,
Click to expand...
Click to collapse
congrats CM7 nightly should of flashed too. just have to wipe dalvik,cache,factory and it should be fine afterwards.
Oxygen is pretty nice though. I manipulated the ROM to be like Cyanogen by copying over Cyanbread. More lightweight and less bloat compared to CM7.

would that add in DSP manager?

slimjimwoods said:
would that add in DSP manager?
Click to expand...
Click to collapse
Nope. have to separately add it in, Voodoo Sound is better anyways.

That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)

slimjimwoods said:
That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)
Click to expand...
Click to collapse
Just add the app in, see what happens.

[Q] deleted htc framework file and phone doesnot start

deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.

HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.

Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.

redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You

in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.

the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?

in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.

in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.

Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You

in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?

Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.

in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.

Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.

in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.

Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....

qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous

Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.

in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.

And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble

18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?

download bootloader

Is there a place where I can download (old) bootloaders?
Or do I just have to download a full ROM image, and extract the bootloader from there?
I want to flash a different bootloader without flashing anything else.

Which one are you looking for? And why flash an old bootloader???
Upgrade/downgrade of the BL is usually done through flashing the official firmware. You can do it in fastboot, but that's risky stuff... Why would you?

berndblb said:
Which one are you looking for? And why flash an old bootloader???
Click to expand...
Click to collapse
I have ICS installed on my /system partition, and the 10.6.1.14.40 bootloader I recently installed fails to boot the ICS kernel that I usually use. (It does boot Ubuntu however)
berndblb said:
Upgrade/downgrade of the BL is usually done through flashing the official firmware. You can do it in fastboot, but that's risky stuff... Why would you?
Click to expand...
Click to collapse
I have nvflash keys, so I like to live dangerously.

bsammon said:
I have ICS installed on my /system partition, and the 10.6.1.14.40 bootloader I recently installed fails to boot the ICS kernel that I usually use. (It does boot Ubuntu however)
I have nvflash keys, so I like to live dangerously.
Click to expand...
Click to collapse
I'll say....
I don't know of anyone collecting old bootloaders so you'll have to flash the system blob in fastboot I think.
Praetoriano had a collection of those: http://forum.xda-developers.com/showthread.php?t=1946456
AFAIK you cannot downgrade to anything earlier than 9.4.5.30. That was the last ICS version

berndblb said:
I'll say....
I don't know of anyone collecting old bootloaders
Click to expand...
Click to collapse
Now you do...
Code:
[email protected] ~/android/tf700/bootloaders $ ls blob.EBT*
blob.EBT.10.4.4.16 blob.EBT.10.4.4.23 blob.EBT.10.6.1.14.4-US blob.EBT.9.4.5.26
blob.EBT.10.4.4.18 blob.EBT.10.4.4.25-US blob.EBT.10.6.1.14.4-WW blob.EBT.9.4.5.30
blob.EBT.10.4.4.20 blob.EBT.10.6.1.14.10-WW blob.EBT.10.6.1.14.8-US
@bsammon: which one do you want?

_that said:
Now you do...
Code:
[email protected] ~/android/tf700/bootloaders $ ls blob.EBT*
blob.EBT.10.4.4.16 blob.EBT.10.4.4.23 blob.EBT.10.6.1.14.4-US blob.EBT.9.4.5.26
blob.EBT.10.4.4.18 blob.EBT.10.4.4.25-US blob.EBT.10.6.1.14.4-WW blob.EBT.9.4.5.30
blob.EBT.10.4.4.20 blob.EBT.10.6.1.14.10-WW blob.EBT.10.6.1.14.8-US
@bsammon: which one do you want?
Click to expand...
Click to collapse
Well.. I think I'd start with 9.4.5.30 -- in hopes that that is close enough to load my 9.4.5.26 kernel
And if that doesn't work, or if I'm feeling adventurous, I'd try the 9.4.5.26 image, and see if I can install it from the Flatline bootloader.
Or, you could send me all of them, and I'll find a website to host them on.

_that said:
Now you do...
Click to expand...
Click to collapse
LOL
Why am I not surprised? [emoji38]

[Q] Error message while installing android lollipop on Nexus 5

Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!

eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app

I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5

eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.

eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.

wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet

rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.

wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?

rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.

Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?

beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app

beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.

rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.

(NEED HELP ASAP) Phone wont boot after updating Bootloader via flashify

I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4

Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC

EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!

I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device

EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway

Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5

Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.

rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.

Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*