Database Develop

[Q] HTC Incredible S stuck in limbo :(

Well here's the story, someone gave me their phone to root (i'm the official rooter in my city ) and i accidently skipped over a major step, infact a few of them.
1: I unlocked the phone and flashed clockwork touch recovery
2: Did not backup the original non rooted rom
3: Did not S-off the phone
4: Flashed Android Revolution HD
Now No rom is working, IT gets stuck on the white HTC logo. At least tried 2-3 of them. Cyanogen and ARHD to start with. Tried a few RUU but those aren't going through too. Tried extracting rom.zip from the RUU and flashing manually but they dont work.
Attached is an image with the details of the Firmware on the phone and radio atm
I checked the HTC CID and it's 044 ... Any sort of help would be appreciated.

I feel bad for your city where did you get cwm touch recovery?
Have you flashed the boot.img in fastboot?

If flashing the boot doesn't work. Couldn't you just attempt to s-off through fast boot and flash the RUU etc?
Sent from my Incredible S using xda premium

I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.

shani248 said:
I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.
Click to expand...
Click to collapse
I'll ask again, have you flashed the boot.img in fastboot? The link you provided has no touch recovery in the OP or am I required to read all 29 pages?
If you're using cwm from the OP, you should update. Here's the newest version I know of http://www.clockworkmod.com/rommanager
To your question about flashing an ruu with a modified android_info on an s-on device: no.
You can find what ruu you need by entering the command
Code:
fastboot getvar version-main
the number returned corresponds to the ruu that you should be looking for.
As you are an experienced rooter you probably already know to wipe cache and usually data when you flash a new Rom.
@vizzy how would you gain s-off in fastboot mode?

HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??

shani248 said:
HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??
Click to expand...
Click to collapse
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky

THANKS !!!
Nonverbose said:
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky
Click to expand...
Click to collapse
You, sir, are a gentleman, and a hero. I salute you for your help. ! The phone is fixed ! I see what i did wrong there, and thanks alot for helping me with it. I learned something that was quite frankly logical.
Again, thanks !!!!

[Q] Re: Hasoon2000's HTC Vivid All-In-One Kit

Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)

psterrett said:
Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)
Click to expand...
Click to collapse
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?

bilibox said:
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?
Click to expand...
Click to collapse
Correct CW or WCX just have to choose which you want

It's pretty straight forward and noob friendly...follow instructions to unlock bootloader, choose cwm or wcx recovery then press button to flash...kernel is optional, if you want one download one from here and put it in the kernels subfolder...
Everything comes from/is located in the data folder and its sub-directories you also extracted
Sent from my HTC PH39100 using xda app-developers app

Thank you
Thanks for the replies. I found a simpler to follow method, using fastboot.exe and an included recovery image, and successfully rooted the phone.
Now, I'm going to do some RTFMing, so this won't be an issue again.

One piece of information that might help you is understanding that the term "recovery" can mean two things. In the context of "flashing a recovery" in the process of rooting your phone, what this means is flashing a recovery tool to the recovery partition of your phone. Your phone has a special place set aside for a backup OS (or recovery tool) in case things go south for your actual OS. The recovery you can flash with the all-in-one tool will install CWM (ClockWorkMod), or WCX. Personally, I use CWM. By holding the power key and volume down when you start your phone, you gain access to the boot menu, where you can load the recovery tool. This allows you to do all sorts of powerful things, from flashing kernels and ROMS, to preforming backups and restores, to clearing caches, and all sorts of other power-user type functions.
Hope that helps, and glad you got your phone rooted. These things are a lot of fun once you open them up a little

in serious need of help for the phone!!!!

Hi guys,
I'm new to the android world. I was playing around with my mum's HTC(was on ICS) and tried to root it, but im not sure if its rooted now, but i have ****ed the phone up hardcore
The problem is phone stuck on HTC Logo and won't boot. It's possible to get it in bootloader and it looks like this: I have unlocked it HTCdev.com
*UNLOCKED*
S-ON
HBoot: 1.28.0004
RADIO-3831.15.00.20_M
eMMC-boot
I dont get a connection to the PC, but after first time plug-in it installed the drivers.
So now my question is how can I get an new Ruu on this phone. Would it be fixed by me installing the ICS RUU.exe file?
I can't seem to find it i do have the code from the HTCdev, but i do not have ANY clue what to do..... Please help me out

To get the correct drivers that are needed for the phone you either should install htc sync then uninistall it again or you should go download my tool, it has an installer for drivers for windows, just not windows 8.
About the code from htcdev, that part you have used correctly. That is a bin file you used to get bootloader *UNLOCKED* and since its saying unlocked you should be good to go.
After unlocking the bootloader you can go to bootloader and flash a custom recovery. To do that you can simple install my runnymede aio tool and press either twrp or cwm recovery button. It will pop up with a box that says "Press Ok when in bootloader" and since you are already in bootloader you can just skip that part and press ok.
after it has flashed recovery it will try to boot to the system just go to bootloader again
When you are in bootloader you can go into recovery.
After that you can flash any custom rom but if you want to stay on a custom rom i will recommed you to flash to specific roms first, found in the "guide" in my Runnymede AIO Tool. And then after that flash any rom for our phone. I know it sounds a little stupid and is is also not cofirmed giving any diffrence but it looks like the htc sensation xl is much more hard to brick if these two roms have been flashed.
If you just want to go back to stock , then flash a custom rom and boot it up.
Then use the function in my tool from fully booted to s-off just remeber to use the one that says your hboot version.
A note here: Hboot version 1.25 = 6.25 and 1.28 = 6.28
after that is done boot the phone up normally and run a ruu.exe file and you will end up in a stock locked rom after that.

Thanks Anders3408 i have followed your instructions and have downloaded your tool(which works like wonders).
Now i am facing another problem. My current rom is a custom one (1.56.401.2), but it tells me there are no hard disk spaces and i keep getting Contacts Storage stopped message (even after i press send report to HTC or even if i declined it....)

I have a similar problem....i'm S-ON UNLOACKED....hboot 1.28.0006 ....i can only have fastboot connection...i even tryed an RUU (RUU_RUNNYMEDE_ICS_35_S_HTC_Europe_2.31.401.2_Radio_20.70.30.0832U_3831.16.00.16_M_release_258303_signed) but still bootloop! :/ I'm driving crazy!!!
ps: tried to flash a custom recovery but doesn't work!!! (during flash i was on s-on because i couldn't flash hboot s-off )...The phone has no root.

It you have EUROPE CID then flash this
http://www.shipped-roms.com/index.ph...odel=Runnymede
If link doesnt work then here the same
http://hotfile.com/dl/145704399/e91...822.10.10.12_M_release_222101_signed.exe.html
Install that Europe Version of GingerBread.
When finish let it boot and when setup is finish update via OTA to ICS..
If this still doesn´t work then S-off with this. ----->
http://unlimited.io/runnymede.htm
You will change your hboot version. Use that 4445 version in download. Its unsecure hboot.
Follow the ADB steps carefully and when done reboot into bootloader again. Flash custom recovery like TWRP
Wipe cache,dalvik,system
Then reboot into bootloader again
FastbootADB and run the RUU from PC

Sv: in serious need of help for the phone!!!!
bihslk said:
It you have EUROPE CID then flash this
http://www.shipped-roms.com/index.ph...odel=Runnymede
If link doesnt work then here the same
http://hotfile.com/dl/145704399/e91...822.10.10.12_M_release_222101_signed.exe.html
Install that Europe Version of GingerBread.
When finish let it boot and when setup is finish update via OTA to ICS..
If this still doesn´t work then S-off with this. ----->
http://unlimited.io/runnymede.htm
You will change your hboot version. Use that 4445 version in download. Its unsecure hboot.
Follow the ADB steps carefully and when done reboot into bootloader again. Flash custom recovery like TWRP
Wipe cache,dalvik,system
Then reboot into bootloader again
FastbootADB and run the RUU from PC
Click to expand...
Click to collapse
No need to do everything by yourself. My tool uses the same files and procedure to make the phone s-off. Just boot it up and enable debugging in settings then press the s-off button that fits hour hboot
Sent from my HTC Sensation using xda premium

anders3408 said:
No need to do everything by yourself. My tool uses the same files and procedure to make the phone s-off. Just boot it up and enable debugging in settings then press the s-off button that fits hour hboot
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Yeah he can do this 2 but how can he BOOT and enable DEBUG mode if he stuck at HTC LOGO???

Sv: in serious need of help for the phone!!!!
bihslk said:
Yeah he can do this 2 but how can he BOOT and enable DEBUG mode if he stuck at HTC LOGO???
Click to expand...
Click to collapse
Many phones do have ADb connection while booting
Sent from my HTC Sensation using xda premium

anders3408 said:
Many phones do have ADb connection while booting
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
OKEy

[Help] White screen

Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?

Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.

tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\

Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???

prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?

Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??

prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??

prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.

tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.

Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.

Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU

tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.

tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.

[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...