Related
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!
Now that the new hboot doesn't allow S-ON devices to flash kernels I went ahead and adapted this for the LTE. It's something I started for the Evo 3D back in January, but when a new way to get S-OFF was found I sat it aside and had forgotten about it.
When used it tries to flash the kernel like normal and doesn't do anything special if able to, otherwise it will copy a script to the system partition and install the kernel when the ROM tries to boot up. All that's needed is for a few lines to be added to the updater-script and it can do the rest.
I'll update this with more information at a later time, but for now I just want to say thank you to everyone who has helped contribute ideas and tested. As always, any help with improving it is welcomed.
How To Use It
This is mainly for ROM and kernel devs to use before releasing, but it can easily be added to any that don't normally use it. For more detailed instructions see Page 3.
Download and add the "kernel" folder to your update zip
Edit your updater-script and use the following when you are ready to install the boot.img
Code:
ui_print("Installing Kernel, please wait...");
package_extract_file("boot.img", "/tmp/boot.img");
package_extract_dir("kernel", "/tmp/kernel");
set_perm_recursive(0, 2000, 0777, 0777, "/tmp/kernel");
run_program("/tmp/kernel/install_kernel.sh", "/tmp/boot.img", "/tmp/bootready.tmp");;
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") != "READY",(
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") == "STARTUP",
ui_print("Kernel Will Be Installed On Startup."),
ui_print("ERROR: Kernel Not Installed!")
)
));
Sign the zip and it can then be installed like normal from any device with a custom recovery
Changes
v0.57
flashboot.sh - Fixed the case statement that verifies the kernel flashed properly
flashboot.sh - Moved the call for DD to save the old kernel so that it always gets used
Downloads/Sources
Kernel Folder on DevHost (MD5: 27eB86aae3562e147d86b8dfe7a04786)
Google Code
Github - All files including the flashboot binary source
How Can I Test It With S-OFF?
If you comment out the dd command that writes the boot.img it will act like your device has S-ON.
Edit install_kernel.sh and change:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
to:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
#$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
Where Are The Log Files?
In the recovery it uses: /tmp/recovery.log
On boot it uses: /data/local/bootinfo.txt
What Does This Need To Work?
A custom recovery
A valid kernel already installed with init scripts to start either /system/bin/app_process or /system/bin/netd
What Recoveries Does It work With?
Most of my testing has been done with TWRP, but it should work just as well with any other recovery
Why Did My Phone Reboot Back To The Recovery?
If it is unable to flash the kernel it will leave the old one in place and reboot back to the recovery. If you are able to, please pull the log file from /data/local/bootinfo.txt and send it to me so I can see what needs to be fixed.
What If I Get A Bootloop?
Either the kernel you flashed doesn't work with your ROM or there was an error and it's unable to reboot back to the recovery. If you hold volume down it should bring up the bootloader, from there use the volume and power buttons to select 'Recovery'.
Why Does My Phone Boot Straight To The Bootloader?
You either managed to wipe your boot partition (kernel) or sometimes this will happen when upgrading hboots. If you are S-ON you will need to flash a new boot image from fastboot.
Reserved for later use
Cute
Does this work for AOSP based kernels as well?
-Cupper- said:
Cute
Click to expand...
Click to collapse
Thanks Cupper
sivarticus85 said:
Does this work for AOSP based kernels as well?
Click to expand...
Click to collapse
Yup, it's all the same to it. The only thing it needs to work is for some sort of kernel to already be installed.
good stuff!!!!!!!
Good stuff man. Like always, xhausx contributing genius stuff for all. Thanks. :thumbup:
Sent from my EVO using xda premium
Awesome. Thanks.
via eVo.
implimenting in my next installer
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
ca1ne said:
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Click to expand...
Click to collapse
Let me know if you need any help implementing it. I know the instructions aren't very detailed yet so I'll see about clarifying them some more here in a little bit.
Cool man
Sent from my EVO using xda premium
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
Since the kernel is only writeable from the rom this does something similar, except it does it after you flash the rom and it's automatic.
You could look at it as the rom itself installs it's own kernel. That's one of the reasons why it may look so convoluted, but for a rom/kernel dev to actually implement it is easy once you know how it works.
JohnCorleone said:
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If you no longer need it rooted personally I would get s-off first and then run the latest RUU to restore it to stock. That way you'll always be able to re-root anytime without hassle, but the device can still be completely stock and used normally.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Evolutionmods said:
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Click to expand...
Click to collapse
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
Captain_Throwback said:
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Click to expand...
Click to collapse
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
xHausx said:
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
Click to expand...
Click to collapse
And of course the Dropbox link is now dead too .
I just got a used Rezound, and was able to do some tweaks: HTC bootloader unlocked, S-off, installed Ramon Ra recovery, flashed global OTA and firmware, simplicity ROM 3.0, and Funky kernel v3.3. The features that I want from rezound are just two things: global capability (GSM enabled) and sweep2wake. Now I got the first part. But for the second part, I tried different kernels, but for some reason none of them is working. Would you shed some light on what I should do, such as what kernel/rom to flash, and if order matters, in which order? Thanks!
Sweep2wake is a default off in my kernel. Flash my kernelscripts package to enable/disable it.
Thanks very much for your reply! I was able to flash the kernelscripts package, and chose to enable sweep2wake. But it does not seem to work. I then installed Kernel Tuner, which shows (in Sys. Info>Device) Sweep2Wake is off. I flashed v3.3.4 and script again, still the same thing. Anything that I might have missed? Thanks again for your help!
Snuzzo said:
Sweep2wake is a default off in my kernel. Flash my kernelscripts package to enable/disable it.
Click to expand...
Click to collapse
It is possible that the rom dev's ram-disk does not support init.d. Which those rely on. PM me (use sendspace.com, dev-host.org, or androidfilehost.com) or post a copy of his boot.img as an attachment from the flashable rom. Maybe even a link to a PH98IMG.zip if one was created for it.
PS: You are quite welcome!! Anytime!
I got it finally, thanks!
jensenchen68 said:
Thanks very much for your reply! I was able to flash the kernelscripts package, and chose to enable sweep2wake. But it does not seem to work. I then installed Kernel Tuner, which shows (in Sys. Info>Device) Sweep2Wake is off. I flashed v3.3.4 and script again, still the same thing. Anything that I might have missed? Thanks again for your help!
Click to expand...
Click to collapse
Welcome. What was the fix?
Sent from my Nexus 7 using Tapatalk HD
Hey Everyone! So here's the quick nitty gritty...
Flashed Clean Rom Standard and Left S-On
Worked great for about 8 months
Started crashing like crazy and the only fix was to go back to stock
Went to stock and then unlocked, S is still On
Flashed ClockworkMod 6.0.2.3
Can't get any aftermarket S-On Roms to work
It can never see a PH98IMG.zip file via fastboot/bootloader
So I'm stuck and I don't know what to do
Anyway, that's where I'm at. Right now the phone is working just fine but stock roms suck and it's FULL of bloatware that I can't get rid of. So...any ideas on what I can do? I'd love to use Clean Rom once again but I can't get the PH98 file to flash
More Phone Info...
Ver - 4.0.3
Sense - 3.6
Software - 4.03.605.2 710RD
Kernel - 3.0.16-g480e1b0
Thanks in advance!
AT
AlmostTactful said:
Hey Everyone! So here's the quick nitty gritty...
Flashed Clean Rom Standard and Left S-On
Worked great for about 8 months
Started crashing like crazy and the only fix was to go back to stock
Went to stock and then unlocked, S is still On
Flashed ClockworkMod 6.0.2.3
Can't get any aftermarket S-On Roms to work
It can never see a PH98IMG.zip file via fastboot/bootloader
So I'm stuck and I don't know what to do
Anyway, that's where I'm at. Right now the phone is working just fine but stock roms suck and it's FULL of bloatware that I can't get rid of. So...any ideas on what I can do? I'd love to use Clean Rom once again but I can't get the PH98 file to flash
More Phone Info...
Ver - 4.0.3
Sense - 3.6
Software - 4.03.605.2 710RD
Kernel - 3.0.16-g480e1b0
Thanks in advance!
AT
Click to expand...
Click to collapse
The newer roms are mostly made for S-OFF and do not create a ph98img file to flash with the boot.img you have to manually do it.
You should be able to flash by extracting the boot.img from the rom you want to flash, place it in your fast boot folder on your PC,
Open command prompt in that folder, and type fastboot flash boot boot.img
Hope this helps
Just saw your location
Hi Neighbor
kc6wke said:
The newer roms are mostly made for S-OFF and do not create a ph98img file to flash with the boot.img you have to manually do it.
You should be able to flash by extracting the boot.img from the rom you want to flash, place it in your fast boot folder on your PC,
Open command prompt in that folder, and type fastboot flash boot boot.img
Hope this helps
Just saw your location
Hi Neighbor
Click to expand...
Click to collapse
Haha Howdy!
Well, so I just tried using Nils ROM and it's supposed to be an all in one installer. I can see the installer saying everything is working but when it goes back to the boot loader screen it still isn't seeing the PH98 file...I'm not super familar with using fast boot on my PC as I'm still using older roms that always worked for me before when it came to flashing doing this method.
Sorry to be a pain in the a lol
AlmostTactful said:
Haha Howdy!
Well, so I just tried using Nils ROM and it's supposed to be an all in one installer. I can see the installer saying everything is working but when it goes back to the boot loader screen it still isn't seeing the PH98 file...I'm not super familar with using fast boot on my PC as I'm still using older roms that always worked for me before when it came to flashing doing this method.
Sorry to be a pain in the a lol
Click to expand...
Click to collapse
I'll chime in, but would say that getting acquainted with how ADB works from the PC would be of great help to you. I don't like it either, which is why I s-offed. It does occur to me though that, at the very least, you are rooted, so Titanium Backup will help you freeze and/or uninstall bloat. I just had to RUU because I borked my internal storage and I am running stock, without all of Big Reds crap, and I'm actually enjoying it for a few days...
Good Luck from the mid west!
AlmostTactful said:
Haha Howdy!
Well, so I just tried using Nils ROM and it's supposed to be an all in one installer. I can see the installer saying everything is working but when it goes back to the boot loader screen it still isn't seeing the PH98 file...I'm not super familar with using fast boot on my PC as I'm still using older roms that always worked for me before when it came to flashing doing this method.
Sorry to be a pain in the a lol
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, but I don't see a way around your problem if you're unwilling to learn how to do things with fastboot or adb or (possibly) both. They're easy to figure out for basic operations, so just do it! (Hey, you're flashing custom ROMs, ya gotta give a little too! )
Good luck,
john
AlmostTactful said:
Haha Howdy!
Well, so I just tried using Nils ROM and it's supposed to be an all in one installer. I can see the installer saying everything is working but when it goes back to the boot loader screen it still isn't seeing the PH98 file...I'm not super familar with using fast boot on my PC as I'm still using older roms that always worked for me before when it came to flashing doing this method.
Sorry to be a pain in the a lol
Click to expand...
Click to collapse
There is one way to acquire temp "s-off" meaning you can flash ROMs in recovery and the boot image flash with it. It does do heavy work on your boot partition though. TWRP HTCdumlock there is instructions in flyhalf's TWRP thread to do this method
Sent from my Infected Rezound using xda app-developers app
Don't use CWM plain and simple. Switch over to TWRP. Only con, rebooting to bootloader manually. Also make sure you do a system/data/cache wipe prior to switching roms.
There is always the all in one tool that you can flash the kernel from but you still need to extract the boot img from the rom
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
xFatex said:
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
Click to expand...
Click to collapse
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
lreyes said:
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had no access to my TWRP Recovery, I actually fixed that though.
The Kernel is changed and now I have no Data access? I think my ROM is not compatible like suggested. (Sense ROM)
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
The current situations has changed sadly.
I have no custom ROM just Sense.
The Kernel: Bulletproof-EVO-v1.4.
ROM: Default Sense?
This is my first attempt at really rooting/adding kernels just messing around and doing damage.
Now instead of WiFi I have no Data Service with this Kernel and ROM combo. I will check out your links thank you very much.
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
xFatex said:
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
Click to expand...
Click to collapse
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
EDIT:
NOTE:
I AM currently reading your bottom link about Fixing system wipe.
xFatex said:
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
Click to expand...
Click to collapse
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
lreyes said:
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
Click to expand...
Click to collapse
S-ON.
I am attempting to download MeanBean after reading Fin's Fix.
Though I don't know if FlashImage GUI will work.
I also have to figure out how to flash .apk files too...
Sorry about the bother... I really am far below Novice at this I should have had someone holding my hand step by step lol.
Okay, so the problem with the Kernel originally was it wasn't compatible?
Then the next one with the service error was I suppose the same thing?
Then when I tried to restore apparently I wiped my phone of all Data resulting in a bootloop and being no one has the exe file for the factory RUU of the latest version for the Evo 4g LTE I had no way of restoring any of the files?
So then I stalked Fin's suggestions eventually lead me to MeanBean. at least it got me up and running... I attempted to back up with TWRP.
Which apparently doesn't work (I have to learn how to backup else where... Lets add it to my list.)
But after I attempted the back up I also attempted the instillation of "Operation Jelly Bean" I love the ROM I love the theme I love the sleekness
Apparently I am missing something with my touch panel software. I wish I could have kept the ROM but couldn't sadly (If you know what I am doing wrong I would love to keep that ROM in the future)
So with another failed ROM I tried to restore... which there was no restore when I went to do so... I was a little frustrated from my constant bricking as is...
I attempted factory restore apparently also wiped everything (Internal sd, external, everything.) I don't know what is up with that do you have any clue if its a glitch or am I just wiping it?
I also do Stock restore that does absolutely nothing for my phone anymore...
I will flash it... and it does nothing... it still runs like TWRP (disclaimer etc) but won't go to the twrp boot screen... this is a bit frustrating.