deck evo4g ICS Alpha4 boot.img Boot Manager - General Questions and Answers

I have used Boot Manager for quite a while now and while the Boot Manager dev explains that most ICS ROMs will not work with it, Deck's EVO 4g ICS mod did work in Boot Manager with the pre-releases, alpha1, and alpha2 . I never got to try alpha3 but alpha4 does not work with boot manager anymore. What changed that prevents a proper boot.img being built on alpha4? Is there something I can do or is it up to deck to decide if he wants to make alpha4 compatible with boot manager (as were the pre-releases and alpha1 and alpha2)?
I figured it out late last night. I reinstalled my boot image from phone ROM, restored slot1 (CM7 256) with boot image, re-installed slot 2 (alpha4) with newly built boot image and all is well. Guess I jacked it up at some point .... good thing for back-ups eh

Related

Not loading recovery boot or kernel.

I am somewhat new to this, I've been rooted for a while but finally got tired of the stock annoying stuff. I downloaded rom manager and kernel manager. I wanted to see if it worked so I flashed my kernel, it says its installed but it doesn't do a thing and when I do a reboot the menu still notes the original kernel. Wth!!!! And when I tried to do the cm7 rom it gets to the point where it tells me to restart recovery and it freezes on the HTC startup screen. I have to remove the battery to reboot it normally. Why is it doing this??? I have a stock rooted HTC EVO shift 4G. I do not have nand unlocked.
thronnos said:
I am somewhat new to this, I've been rooted for a while but finally got tired of the stock annoying stuff. I downloaded rom manager and kernel manager. I wanted to see if it worked so I flashed my kernel, it says its installed but it doesn't do a thing and when I do a reboot the menu still notes the original kernel. Wth!!!! And when I tried to do the cm7 rom it gets to the point where it tells me to restart recovery and it freezes on the HTC startup screen. I have to remove the battery to reboot it normally. Why is it doing this??? I have a stock rooted HTC EVO shift 4G. I do not have nand unlocked.
Click to expand...
Click to collapse
I'm no expert here, but I believe this has something to do with not having a custom recovery. Have a look in the EVO section for threads relating to amon-ra and ClockWorkMod (CWM). Hopefully this will help you around the recovery issue and allow you to flash your kernel.
Good luck!
just a thought mate.... you do know that you need to do a full wipe before installing CM7 & also make sure your using "Clockwork 3*** with CM7" & "not Clockwork 2*** with CM7" or you will get a bootloop!
Hope this helps

[Q] Kernel Flash Help...

Currently running a SkyRocket i727 with GB 2.3.5. I have ROM Manager, Root Explorer and ROM Toolbox installed and the device is rooted. Also flashed CWM. I would like to flash my kernel to one that allows me to replace/modify the boot animation. I tried this one from Da_G:
ponack.net/TPC/dagnarf/cwm-ke...el-0.43-v2.zip
On reboot, I get a "Process system....." failure and the phone won't do anything. Pulled the battery, booted in CWM and restored from backup. Phone is working now.
Can someone help me with doing a kernel flash that will work? The ROM is the stock ROM. I was told that you can flash the kernel without having to flash a new ROM.
Thanks.
This is my favourite gb kernel
http://forum.xda-developers.com/showthread.php?t=1437563
Flash 010 mainline edition
If that doesn't work try Eugene's sgs2 streamline kernel

Unable to put back to stock RUU (Need Original ROM HTC Incredible S)

Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.
2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.
why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit
okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...
Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar
Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app
tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.

[Q] MultiROM secondary ROM boot loop

I had stock 5.0 and installed MultiROM via fastboot. And after that I tested out xTraSmooth 3.1 on the secondary ROM so I pretty much liked it so I said **** it, why not make it the primary. So I formatted the device completely secondary and primary and all. And I copied the zip files and flashed them as primary. I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. Anyway, I wanted to test some more ROMs now, I ended up with a bootloop or updater binary error.
So, I said I'll test it on the same ROM I had tested before, which is now my primary one. So I flashed another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop. What should be done? Or is this some new problem with MultiROM?
Bump
SA3DX said:
... I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. ...
Click to expand...
Click to collapse
That sounds very strange to me! I'd try a fresh install using the MultiROM Manager Android App. Make sure that the status displayed in the app does NOT say Kernel: doesn't have kexec-hardboot patch! (see Installation section in the first post of the MultiROM thread).
... another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop.
Click to expand...
Click to collapse
Did you try the newest version of xTraSmooth (3.3)? I had a quite similar situation with AICP for Nexus 7. In fact, at first it never got past the boot animation and then "suddenly", with a newer version, things were fine.
You may also want to try installing another ROM as secondary, just to make sure your current MultiROM installation works as it should.

Categories

Resources