Database Develop

[Q] Wifi problem

Okay so I just rooted my HTC Vivid, ive tried many different roms and my WiFi doesnt work on any of them.
A hour ago my WiFi was working fine on Stock ICS 4.0.3.
Currently im running Holics ROM 0.8.
Anything?
Thanks,
Dom

I would try reflashing Rom run fix permission and make sure busybox is installed hope this helps.
Sent from my HTC PH39100 using xda premium

Yeah I did reflash each individual rom. I probably re-flashed over 10 times.
And i tried permissions aswell.
Nothing yet.
And what is busybox?

Its background support software basic runs some linux commands might get WiFi running.
Sent from my HTC PH39100 using xda premium

Are you s-off
Sent from my HTC PH39100 using xda premium

Mjones307 said:
Are you s-off
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
No i believe im S-ON
This is what my bootloader looks like:
*** UNLOCKED ***
Holiday PVT SHIP S-ON RL
HBOOT-1.85.0025
Click to expand...
Click to collapse

domdiv said:
No i believe im S-ON
This is what my bootloader looks like:
Click to expand...
Click to collapse
you need to fastboot the boot.img extract the boot.img from the rom you are going to use put the boot.img in the same folder as fast boot open that folder and right click will hitting shift key in a open area pick command prompt reboot your phone to hboot hook it to your computer and at the command prompt type fastboot flash boot boot.img once it is done reboot your phone and your wifi should work

What if my phone isnt even detected ?
I typed "fastboot devices" and nothing happened.
Its not even showing up

domdiv said:
What if my phone isnt even detected ?
I typed "fastboot devices" and nothing happened.
Its not even showing up
Click to expand...
Click to collapse
try different port on your computer also different cable if you can
or a different computer

Quick question: After you extract the boot.img from the rom zip and flash it via fastboot, can you leave the boot.img in the rom zip or need to remove it before flashing the rom? I am still S-on.

ncpanicfan said:
Quick question: After you extract the boot.img from the rom zip and flash it via fastboot, can you leave the boot.img in the rom zip or need to remove it? I am still S-on.
Click to expand...
Click to collapse
you can leave it in wont hurt anything

I sent you a link to the guide for flashing ROM/Kernels while on S-On, we can't post it here.

I can't seem to figure out how to fix mine. I've tried flashing the boot.img from the ROM, and I copied bcmd.ko or what ever to System/Lib/Module as well, nothing is fixing it but re flashing the ROM, but then when I install a kernel (Like the situation I'm in now) my wifi breaks. I worked hard to get my ROM and APN settings right.
Is there a way to fix it without re flashing and losing everything? Please rescue me. :,'(

keeng james said:
I can't seem to figure out how to fix mine. I've tried flashing the boot.img from the ROM, and I copied bcmd.ko or what ever to System/Lib/Module as well, nothing is fixing it but re flashing the ROM, but then when I install a kernel (Like the situation I'm in now) my wifi breaks. I worked hard to get my ROM and APN settings right.
Is there a way to fix it without re flashing and losing everything? Please rescue me. :,'(
Click to expand...
Click to collapse
read post 7

keeng james said:
I can't seem to figure out how to fix mine. I've tried flashing the boot.img from the ROM, and I copied bcmd.ko or what ever to System/Lib/Module as well, nothing is fixing it but re flashing the ROM, but then when I install a kernel (Like the situation I'm in now) my wifi breaks. I worked hard to get my ROM and APN settings right.
Is there a way to fix it without re flashing and losing everything? Please rescue me. :,'(
Click to expand...
Click to collapse
You're going to have to reflash the kernel separately from the ROM. I have to do it the same way, bc I'm "S-On" still as well. That's the only way to get your Wifi working. Make sure the kernel's boot.img is in the same folder as your fastboot.exe and your adb files. Reboot your phone into fastboot mode, then connect it to you computer.. it should then change to 'fastboot usb' which means your phone is recognised. Open your command prompt in the folder with fastboot.exe, and run the code, "fastboot flash boot boot.img," if you see 'OK' msgs then everything is done correctly. Reboot your phone n it should work perfectly.
Sent from my de-sensed HTC Vivid, Virtuous Inquisition 4.0.2.1, Faux v005 Kernel

[Q] phone stuck on boot

so i was stuck for a long time with a crappy rom that kept getting my calls stuck,so today i finally switched it to cooldroid revolution and it got stuck on boot so i tried to maybe switch some kernels and nothing worked so i tried other roms as well like Nik's Project X and paranoidandroid
and nothing works im stuck like that without a phone all day. can someone please find a answer?

Noamzoro said:
so i was stuck for a long time with a crappy rom that kept getting my calls stuck,so today i finally switched it to cooldroid revolution and it got stuck on boot so i tried to maybe switch some kernels and nothing worked so i tried other roms as well like Nik's Project X and paranoidandroid
and nothing works im stuck like that without a phone all day. can someone please find a answer?
Click to expand...
Click to collapse
What HBOOT version are you running and are you S-OFF or S-ON. You didn't give enough information to give you a straight answer.
Off hand, I would say that you are using an unlocked HBOOT, so you probably just need to manually flash the boot.img file from the last ROM you tried to install.

tpbklake said:
What HBOOT version are you running and are you S-OFF or S-ON. You didn't give enough information to give you a straight answer.
Off hand, I would say that you are using an unlocked HBOOT, so you probably just need to manually flash the boot.img file from the last ROM you tried to install.
Click to expand...
Click to collapse
im using 1.16.0000 Hboot and S-On

Noamzoro said:
im using 1.16.0000 Hboot and S-On
Click to expand...
Click to collapse
follow the steps.
1. extract boot.img from zip file
2. go to adb tools ..if you dont know what adb is google it....
3. fire up adb ...
4.put your phone in fastboot mode ..(boot in hboot by powering down your phone and press vol-down and power togethr while switching on)
5. connect to your pc
6. type fastboot flash boot boot.img
7. reboot your phone
8. done...
and yes important stuff only falsh the boot.img file of the rom installed on your device..dont flash any other boot.ing

[Q] I am stuck on CryanogenMod startup screen

i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?

tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
Have you wiped data and both cache as well..??
Also have your flashed latest Gapps..?

i need to correst apps
i was hoping to flash it back to the stock Rogers [ICS] 4.0.3 ruu do you know where i can get that ruu?

Yes
Yes ive done that and it still shows the cyanogenmod screen when i start up the phone it wont load past that

If its your first time installing... you need to wipe data as well
Sent from my Vivid 4G using Tapatalk 2

Did you fastboot flash the boot.img
Sent from my HTC PH39100 using xda app-developers app

No
i dont know where the boot.img is

tpaina380 said:
i dont know where the boot.img is
Click to expand...
Click to collapse
It's in the Rom zip, assuming your not s-off it must be flashed separately
You can check if your s-off by going to hboot, toward the top it will say s-off or s-on...which basically means security off/on - its another level of security HTC added on above the bootloader
Sent from my HTC PH39100 using Tapatalk 2

It says s-on
so what do i do from here?

Put your boot.img into the folder which your fastboot and adb are and then open a terminal to the folder. Then put your phone into fastboot by entering the bootloader. Then type fastboot devices to see if your device is connected to the computer. If it comes up with your serial number continue if not try again. Then type fastboot flash boot.img and then go to recovery and reflash the rom.
---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------
If you need help with a better guide try
http://forum.xda-developers.com/showthread.php?t=1416836
and read the flash custom kernel/recovery the third option

Didnt work
all is says is
C:\Fastboot Command Folder>fastboot devices
MB201VJ21706 fastboot
C:\Fastboot Command Folder>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'

I worked!!!!!!!!!!! DDDDDD
When i typed in "fastboot flash boot.img" it didn't work so i tried "fastboot flash boot boot.img" and it worked i flashed cm-10 afterwards and then i flashed the ics gapps and it loaded up my holiday is now running android 4.1.2 and it is awsome!!!!!!!!!!!!!!!!!!!!! thank you for the help much appreciated

You figured out what you where doing wrong before i could tell you. Well done glad to help.

tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help

Bigc13 said:
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help
Click to expand...
Click to collapse
No no... bad advice... ODIN is for Samsung...
Sent from my Vivid 4G using Tapatalk 4 Beta

Download either TWRP or WCX recovery. As long as your phone can get to the bootloader, you can get into Fastboot and flash the recovery again. Make sure the recovery is in the same folder where you have the adb.exe and fastboot.exe. Open up a command prompt, then change directory to where your fastboot and adb are. Type in fastboot flash recovery "recovery".img where "recovery" would be the name of the recovery file you download. This will flash pretty quickly. Once you get to that point, you probably are S-On so you need to make sure to extract the boot.img from the ROM you downloaded. Use either winrar or 7zip to extract the boot.img to the same location where you have the fastboot.exe and adb.exe. Then go to the command prompt again and change directories to the same folder where you have fastboot and adb. Type in fastboot flash boot boot.img. I usually would run this 3 times to make sure it loads properly. Once that is done reboot the phone again.

Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app

Bigc13 said:
Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta

Man I used a jig to put in dl mode to flash a file I can't remember exactly it was a couple years ago lol but sorry I shouldn't have said nt

rignfool said:
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
That would be a no for me as well... but these Springdale-ians... never know what they will come up with. JK.

No OS on phone, can't install a rom

I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!

Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck

Then make him use a flip phone for a week as punishment lol

I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.

Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?

Give it a shot the phone is already bricked what you got to lose

crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk

woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/

crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk

Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.

I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk

The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk

[Q] How can I reinstall a good image after flashing my boot with CWM?

My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as Understood​I was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial Solution​At first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
Question​So how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682

1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img

Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload

abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.

bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread

Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.

russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?

bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"

So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app

stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted

astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!

Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...