Related
i have hboot 1.49.1107 and i seem to be the only person on here with that version.
my WiFi won't work on any rom, even a rogers rom. this is extremely irritating because when i sync with google it tries to sync all of my apps on 3g. this happened once and used 160mb of my data.
i tried re-packing roms with the wifi module, bla bla bla i've tried it all.
i was on a rom before that had wifi working, then i tried to upgrade to a new rom, no wifi, unfortunately no backup because i've never had such a problem. every other rom wifi is broken.
can someone please help me? i just haven't sync'd with google at all now, because it will just rape my data.
Have you tried flashing a custom kernel with GUI kernel flasher in the apps/themes section ?
Garrytheogre said:
Have you tried flashing a custom kernel with GUI kernel flasher in the apps/themes section ?
Click to expand...
Click to collapse
i've tried flashing roms but not just the kernel. does that usually work? i'll try it now.
nope, didn't work.
i'm trying to flash an older recovery and then flashing a rom, maybe it's the recovery i have no idea at this point.
does this have to do with my Hboot version? i've never heard anyone talk about this version before. does anybody have the wifi module file from a stock rogers rom with 1.49.1107 hboot?
Chillaxed said:
i have hboot 1.49.1107 and i seem to be the only person on here with that version.
my WiFi won't work on any rom, even a rogers rom. this is extremely irritating because when i sync with google it tries to sync all of my apps on 3g. this happened once and used 160mb of my data.
i tried re-packing roms with the wifi module, bla bla bla i've tried it all.
i was on a rom before that had wifi working, then i tried to upgrade to a new rom, no wifi, unfortunately no backup because i've never had such a problem. every other rom wifi is broken.
can someone please help me? i just haven't sync'd with google at all now, because it will just rape my data.
Click to expand...
Click to collapse
I have the same hboot with rogers. I don't think its anything weird. It happens after using revolutionary. I'm not sure what your issue is but I've flashed radios and kernels through cwm and didn't have problems.
Also this is dev forum not q&a
Sent from my HTC EVO 3D X515m using XDA App
Chillaxed said:
i have hboot 1.49.1107 and i seem to be the only person on here with that version.
my WiFi won't work on any rom, even a rogers rom. this is extremely irritating because when i sync with google it tries to sync all of my apps on 3g. this happened once and used 160mb of my data.
i tried re-packing roms with the wifi module, bla bla bla i've tried it all.
i was on a rom before that had wifi working, then i tried to upgrade to a new rom, no wifi, unfortunately no backup because i've never had such a problem. every other rom wifi is broken.
can someone please help me? i just haven't sync'd with google at all now, because it will just rape my data.
Click to expand...
Click to collapse
Did you capture a nandroid backup before flashing a custom ROM? If so, you can always get the kernel (boot.img) from the backup folder. This can be flashed using "fastboot" while your phone is in bootloader but not until you restore your custom ROM (flashing a ROM updates your kernel so you need to flash your custom kernel afterwards). The command is:
fastboot flash boot c:\somefolder\boot.img
You also need the matching wifi driver. Easiest way is to restore your nandroid backup and copy the \system\lib\modules\bcm4329.ko to your SD card. You can copy this file back after restoring your custom ROM
Turge said:
Did you capture a nandroid backup before flashing a custom ROM? If so, you can always get the kernel (boot.img) from the backup folder. This can be flashed using "fastboot" while your phone is in bootloader but not until you restore your custom ROM (flashing a ROM updates your kernel so you need to flash your custom kernel afterwards). The command is:
fastboot flash boot c:\somefolder\boot.img
You also need the matching wifi driver. Easiest way is to restore your nandroid backup and copy the \system\lib\modules\bcm4329.ko to your SD card. You can copy this file back after restoring your custom ROM
Click to expand...
Click to collapse
what is your hboot version? i dont have a nandroid backup because i'm stupid and wanted more space to put jackass 3d on my phone. could someone post the file i need?
Chillaxed said:
i have hboot 1.49.1107 and i seem to be the only person on here with that version.
....
Click to expand...
Click to collapse
Hboot 1.49.1107 arose because you use the revolutionary tools. Those HBoot 0007, after the tool has revolutionized the Hboot 1107. This is completely normal
soliution try it
dear have u tried kingcobra 3d ???
if not then
donwload the latest version
then install it using sd card but remember do full wipe of ur device before installation
even from advance menu too
then install it
if it stucks at boot screen then
no prob
connect ur device with computer using fastboot
then push the boot.img file from the same rom u downloaded and installed (kingcobra)
then reboot ur device
if dont knw how push the boot.img
tthen tell me i ll explain it to u
not sure if it works on the GSM 3ds, but on CDMA that are unlocked but S-ON we can use an app called FlashImageGUI that'll flash kernels from within the OS. Usually fixes wifi problems, and doesn't require using fastboot.
However, that's CDMA, do not know what it would do to a GSM
mildlydisturbed said:
not sure if it works on the GSM 3ds, but on CDMA that are unlocked but S-ON we can use an app called FlashImageGUI that'll flash kernels from within the OS. Usually fixes wifi problems, and doesn't require using fastboot.
However, that's CDMA, do not know what it would do to a GSM
Click to expand...
Click to collapse
yes thats the one I was talking about . It works well on gsm
There is another method that discovered by those ppl in Taiwan.
1. Boot your device into fastboot.
2. Connect your device to computer. (phone screen should now changed to 'fastboot usb')
3. Open cmd and type 'fastboot boot recovery.img' (providing you have all the required files as well as recovery image)
4. Flash the rom as usually.
We all know that HTCDev does not give full access to bootloader when we unlock. So his way gives your the highest permission of recovery.
Give a try and hope it works.
mildlydisturbed said:
not sure if it works on the GSM 3ds, but on CDMA that are unlocked but S-ON we can use an app called FlashImageGUI that'll flash kernels from within the OS. Usually fixes wifi problems, and doesn't require using fastboot.
However, that's CDMA, do not know what it would do to a GSM
Click to expand...
Click to collapse
i've tried this too with no luck.
also i am a dumbass and have never done a backup because i've never had anything go wrong like this.
boyzxiii said:
There is another method that discovered by those ppl in Taiwan.
1. Boot your device into fastboot.
2. Connect your device to computer. (phone screen should now changed to 'fastboot usb')
3. Open cmd and type 'fastboot boot recovery.img' (providing you have all the required files as well as recovery image)
4. Flash the rom as usually.
We all know that HTCDev does not give full access to bootloader when we unlock. So his way gives your the highest permission of recovery.
Give a try and hope it works.
Click to expand...
Click to collapse
what files do you need? the entire rom? or just the recovery?
i've used fastboot to do the recovery.img then the boot.img and still no wifi, then i tried flashing the rom as usual, then flashing a custom kernel through the GUI app, and still no wifi.
looks like this is an actual hardware problem, reverted back to stock rogers RUU and still no WiFi.
Here's a flashable zip I created to fix my Wifi issues. May be worth a shot.
This is whats happening to me too, i had wifi working before on stock rom, but once i fashed a custom one in there, i tried turning WiFi on, and all it says is ERROR under the wifi icon in settings..
im trying to flash custom kernel and hope it fixes it...
Moved to proper forum.
Have you tried flashing the module on its own
Sent from my HTC EVO 3D X515m using XDA Premium App
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Q&A for [ROM][4.4.4_r2][OFFICIAL][GPL] LiquidSmooth v3.2 - vigor - 10|12|14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
bunchies said:
Final KitKat build coming soon, Lollipop was released this morning :thumbup:
Let's see if the Rezound can run android 5.0
Click to expand...
Click to collapse
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
catcher8587 said:
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
Click to expand...
Click to collapse
Yeah, you will be fine
s-on users flash boot.img in fastboot
Last Build
I set the last build and at once found an error. If to come Settings - the Mobile network - Settings of the operator you give out an error: "In application of "com.android.phone" there was an error..." At all so? I quickly discharge the battery for some reason!
Crash video playing
added small problem... When I want to view video sometimes issues the error message. Video doesn't play...
re:chrome floating windows
Just uninstall and download an older version of chrome. Then, don't accept the update. You can't turn off the floating windows. Very annoying
HTC Rezound Liquidsmooth 3.2 ROM install failure
I used this link (theunlockr.com/2013/10/22/how-to-root-the-htc-rezound/) on my stock HTC Verizon Rezound to unlock the bootloader, installed TWRP, and SuperSU to gain access to root.
Then I downloaded LiquidSmooth 3.2 11/5/14 R2 -- Android 4.4.4 and Gapps 4.4.4 Build 8.1 (not Build 7 on this site) I used TWRP to flash both files in the same flash event to the phone. I had placed the files on the INTERNAL SD in the DOWNLOAD directory. Wiped before and after the flash. Phone came up to HTC screen, Blinked, and returned to HTC screen. Waited 10 minutes or so and had to pull battery . Tried another boot with same results. Restored. Repeated same results.
Downloaded the LS v3.2 file again. Downloaded an md5 checker program to my computer. Both files passed. Repeated using second v3.2 file with same results. Downloaded the 8/21/2014 version of the file, md5 checked it, and repeated with same results.
Then downloaded the final LS v2.9 JB4.2.2 file and the appropriate GAPPS file and md5ed it. Repeated with same results.
I am now back to my rooted but stock ROM. I would like to get this LS v3.2 KitKat ROM installed, but am at my wits end.
I also used this link (android.wonderhowto.com/how-to/ultimate-guide-using-twrp-only-custom-recovery-youll-ever-need-0156006/) to troubleshoot. That is why I did a wipe in advance of the first install attempt and I think most of the others as well, although I couldn't tell it helped. I tried the Fix Permissions hint several times but it failed each time.
The only think I have ever read about on HTC phones is S-On or S-Off, but I don't think this applies as neither link source I referred to mentioned S-ON.
Any help would be appreciated. Thanks in advance.
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Thanks a Million or perhaps 10 million!!!
acejavelin said:
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Click to expand...
Click to collapse
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
xdatsellers said:
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
Click to expand...
Click to collapse
Most general tutorials on flashing ROMs on HTC devices includes this information, although most devs will say their ROMs are for S-OFF devices only, it is assumed with a little fastboot trickery most ROMs will work fine, but devs usually make the assumption you know what you are doing.
I would HIGHLY recommend you go S-OFF... if something catastrophic happens and you are S-ON there is often no method of recovery, since all current RUU (HTC's proprietary ROM restoration image) files are prior to current, so do downgrade and restore to stock you must be S-OFF. Rumrunner makes the S-OFF process pretty painless if you are on a custom ROM already.
The boot image, or more accurately the /boot partition, cannot be written to under normal recovery well S-ON, so that affects a nandroid restore as well, you would have to extract the boot image and flash it manually as well to restore a nandroid. BUT, if you boot the recovery image via fastboot it gets around the /boot write restriction even when S-ON... this is a key difference, essentially you are taking the recovery image and telling the phone "this is your new kernel, start it like a ROM" which gets around some of the S-ON restrictions.
Grey network bars
Hello bunchies
I really enjoyed using this rom except this problem my network bars are grey but i can make and receive calls and use the 3g on slow speed (the problem when i call the customer service centre i can't press numbers)
I've checked hboot radio and recovery they are updated
Sorry for my bad English and thanks in advance
Need help to install liquidsmooth
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Thank you
Sent from my SM-N900 using XDA Free mobile app
edwardnizz said:
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Click to expand...
Click to collapse
Assuming you are on current Hboot & radios, upgrade to latest TWRP, flash ROM ZIP and Gapps, fastboot flash boot.img, then reboot and enjoy.
Hello i'm just asking if there wont be any problems with rom update such as recovery boot loop or Freeze or crashes .....etc kthnxbai
can't send SMS or ssd with liquidsmooth 3.2
Hi. As the title says , i cant sens SMS nor use ussd codes. Another issue is that i can't play music. Any help would be appreciated.
I tried to s-off my Desire 601 using rumrunner unde ubuntu and I received tis message:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
When I enter in recovery apears S-OFF, but the phone restarting at the HTC logo.
Where can I find unsecure kernel or differnt room?
boot into recovery and select "mount" then select "system" then select "file manager" and go to /system/bin/hcheck and delete or rename "hcheck" then reboot
Thank you! You save my day!
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
blue74lion said:
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
Click to expand...
Click to collapse
It's hTC's standard message on S-OFF devices.
I have a thread going for removing that red text, but it's only got hboots from the 4.4.4 OTA.
If you want to remove it you can follow the instructions in post 2 of this thread which help you with saving your OTA zip if you plan to update to to 4.4.4 (only need to save it if your carrier's version isn't there already) or dump your current hboot if you plan on staying on 4.2.2.
blue74lion said:
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
Click to expand...
Click to collapse
Also, not sure where/why you got 2.7.0.0 on there, but as of 10/22 2.8.1.0 is the official version. Yes, the version of TWRP posted here on XDA is for KitKat devices, but the official builds from their website work fine on JB (4.2.2) devices.
I've tried to update to 4.4.2, but something is missing me. OTA didnt find nothing. What are the steps to following to update?
Software number is 1.10.401.8
Kernel version 3.4.10-g31cb4f3
Zara_UL pvt ship s-off
CID-VODAP021
HBOOT-2.20.0000
Flash a stock kernel via fastboot and flash a stock rom via twrp
Child's Play said:
Flash a stock kernel via fastboot and flash a stock rom via twrp
Click to expand...
Click to collapse
You'll also need to flash stock recovery.
-Duir- said:
You'll also need to flash stock recovery.
Click to expand...
Click to collapse
No he wanted to go back to a stock kernel and rom
Child's Play said:
No he wanted to go back to a stock kernel and rom
Click to expand...
Click to collapse
Oh, I thought what you posted was in response to getting the OTA update to work.
Still no working to update to 4.4.2. I followed this steps to back to stock:
http://forum.xda-developers.com/showpost.php?p=55850035&postcount=23
Can be an issue that my phone has CID Vodafone Australia and the stock is for Europe?