Ok I just got finished watching the NOOB video. I looked, & searched & looked some more for the answer to my question, but as you see I am still having to ask it..
I have been rooting, (& even bricking) phones since Nexus 1, Most of the time i just read forums and find any problems that get me stuck. The problem I'm having now has to do with Flashing new Kernels
Ok so the details. I have a Sprint Evo 3D, I rooted my phone when i got it. Since then i have not been able to put a new kernel on my phone. I have installed several different ROMs trying to fix this but still nothing. I am currently running Warm two-point-three, but I cannot change the kernel from what was on my phone before the past 3 roms i installed. I have tried Kernel manager. Flashing from recovery, & flashing from a root manager. But yet still no new kernel. I even used a format all zip and still am not able to change the kernel.
( side note. I have not been able to turn on my Wi-Fi either. Im not sure if it has anything to do with the kernel but im pretty sure it does seeing as how the past 4 ROMs i put on my phone did the same thing. )
sorry about the length but i just wanted to be as specific as i could
Thanks
I would take a wild guess and say you are on HBOOT 1.5 and have to flash through fastboot. There are seveal threads on flashing HBOOT 1.5.
schmeggy929 said:
I would take a wild guess and say you are on HBOOT 1.5 and have to flash through fastboot. There are seveal threads on flashing HBOOT 1.5.
Click to expand...
Click to collapse
Yes sir i am. I used to flash the same way on my Evo 4G without having to fastboot. Did i do something wrong or is there a way that i can flash kernel straight from my phone with out having to be at a computer to fastboot????
either go to CMDA or GSM development section and search for how to flash with HBOOT 1.5. there are video tutorials to help as well.
If on CDMA go here:
http://forum.xda-developers.com/showthread.php?t=1306248
schmeggy929 said:
either go to CMDA or GSM development section and search for how to flash with HBOOT 1.5. there are video tutorials to help as well.
If on CDMA go here:
http://forum.xda-developers.com/showthread.php?t=1306248
Click to expand...
Click to collapse
Thank you. I used your advice and did find this.
"If you have hboot 1.5 you have to use flashimage gui made by joeykrim on the market. It's a easy app and it safley flashes it for hboot 1.5 users since we still have s-on"
I hope this helps other people as well. (it does cost .99)
no problem hope it works out. Hear that flashgui app works great and makes flashing rom/kernels easy.
aprater118 said:
Ok I just got finished watching the NOOB video. I looked, & searched & looked some more for the answer to my question, but as you see I am still having to ask it..
I have been rooting, (& even bricking) phones since Nexus 1, Most of the time i just read forums and find any problems that get me stuck. The problem I'm having now has to do with Flashing new Kernels
Ok so the details. I have a Sprint Evo 3D, I rooted my phone when i got it. Since then i have not been able to put a new kernel on my phone. I have installed several different ROMs trying to fix this but still nothing. I am currently running Warm two-point-three, but I cannot change the kernel from what was on my phone before the past 3 roms i installed. I have tried Kernel manager. Flashing from recovery, & flashing from a root manager. But yet still no new kernel. I even used a format all zip and still am not able to change the kernel.
( side note. I have not been able to turn on my Wi-Fi either. Im not sure if it has anything to do with the kernel but im pretty sure it does seeing as how the past 4 ROMs i put on my phone did the same thing. )
sorry about the length but i just wanted to be as specific as i could
Thanks
Click to expand...
Click to collapse
To tie up any lose ends you might have in the logic between flashing on the EVO and flashing on the EVO 3D with HTC's unlock method, I've provided a fairly detailed answer previously in a few posts on here so I'm going to quote. Feel free to ask any other questions you might have if the details don't add up.
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
Thanks alot guys. It did help alot & I have been going really deep into it lately... (that what she said yea yea lol) anyway. The app does still have bugs when trying to flash a new recovery img for some reason so i did still have to use fast boot for that.
@joeykrim, From that last post you obviously know alot of the inside of the roms. More specific the locations & what the different files do. I have another question about file specifics if you can help that would be great. Ill send you an email.
aprater118 said:
Thank you. I used your advice and did find this.
"If you have hboot 1.5 you have to use flashimage gui made by joeykrim on the market. It's a easy app and it safley flashes it for hboot 1.5 users since we still have s-on"
I hope this helps other people as well. (it does cost .99)
Click to expand...
Click to collapse
Yep just use flashimage gui from the market and you are all set. Otherwise you need to use adb from a USB cable which is a drag.
have you tryed the g u i app from the market it will flash flashes kernal's also
Wow wrong thread
Typed by ---- oh wait! I'm schizophrenic!
Related
i have wiped everything like theANDROIDosX said and reflashed. I still cant seem to get wifi to work or even 4g and i cant post directly to the thread because i am a new user.
i Am using evo 3d cdma sprint by the way
wi11iams52 said:
i have wiped everything like theANDROIDosX said and reflashed. I still cant seem to get wifi to work or even 4g and i cant post directly to the thread because i am a new user.
i Am using evo 3d cdma sprint by the way
Click to expand...
Click to collapse
I've answered this question a few times on this EVO 3D Q&A board. I think I've got the details down pretty well. I'm going to quote from an earlier post. Feel free to ask if you have any questions or something isn't clear!
By the way, I found this answer by going to google.com and searching for xda evo 3d wifi error. Hope this helps!
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
http://forum.xda-developers.com/showthread.php?t=1326892
Click to expand...
Click to collapse
Thanks a lot I used your Flash Image GUI. That fix the problem i just needed to flash the kernel that was embedded into the ROM so it will actually use the kernel for that rom. Yall keep up the great work
Sent from my PG86100 using XDA App
Hi,
I am new to this forum. I have just flashed the latest version of LeeDroid v5.4 onto my EVO3D. Everything works except wifi.
My EVO3D is GSM and Hboot 1.49.0018 has been unlocked via htcdev,
security is still S-ON as I do not intend to flash a new kernel.
I have flashed revolution recovery into the phone as well.
Everything from LeeDroid 5.4 works except WIFI, which is unable to be enabled. It says an error.
Could someone please lend me a hand please?
Many thanks
fliptoback
Did you try the solution mentioned in the FAQ on leedroid.com?
Hi, thanks for the quick response.
I had a look of the faq previously...to my understanding, the faq with reference to the wifi issue refers to wifi calling (TMOUS)...I am not quite sure what that means though...
Could u pls clarify?
Thanks again.
Edit: I googled a bit more on wifi calling and I believe this is a service provided by T-Mobile? I am in Australia and we don't have this kind of wifi calling service here.
Is this patch still relevant to my current issue with LeeDroid not able to enable WIFI? Thanks again.
I dont really know if it helps, but I guess it shouldn't hurt your phone. The patch seems to be an apk file and is named SignalBoost.apk, so I would definitely try it.
Did you enable the "*Optional Orange UK Signal boost/WiFi calling selectable in Aroma" on installing? Maybe this option is a problem.
It could be that the stock kernel is not compatible, but I did not see any information that it wouldn't.
S-Off your unit and flash kernel...
Thanks guys for your response.
Is flashing the kernel the only way to resolve this? To flash the kernel I would need to downgrade the bootloader before I can do S-off.
You can flash the Kernel via ADB-commands.
Take the file boot.img from the rom archive.
Put it in the directory on your computer, that contains ADB.exe and fastboot.exe.
Enter to the HBOOT (hold volume(-) and press power, then choose fastboot)
Connect to the computer vith USB (You'll see "Fastboot USB" on the device screen)
Open CMD, navigate (in DOS-window) to your ADB-directory and write:
fastboot flash boot boot.img
fastboot reboot
The phone will reboot, you have WiFi. The problem caused because you are S-ON.
fliptoback said:
Thanks guys for your response.
Is flashing the kernel the only way to resolve this? To flash the kernel I would need to downgrade the bootloader before I can do S-off.
Click to expand...
Click to collapse
Just download and install flash image gui app either from the forums (free, forgot where the link is) or from market for about $1. This let's you flash kernels with ease. Might help to wipe dalvik and cache as well as fix permissions afterwards too.
Or just install 4ext recovery and use their smartflash enabled mode.
Hope this helps get it working! I'm Aussie, s-on, and never bothered to downgrade either.
Sent from my HTC EVO 3D X515m using XDA
Thanks ozlokie!!!!
I followed your advice, bought the $1 flash image gui from google play, use it to flash the latest kernel to the phone, reboot and I HAVE WIFI!!!!
All without downgrading hboot and mucking around with S-off.
I can't believe this is not documented elsewhere on the internet! I have been searching all day and see nothing like this mentioned.
That app is a GEM. Thanks again ozlokie and thanks again everyone who chip in and try to help.
I can finally take a rest from the PC now. It has been a looooonng day.
fliptoback said:
Thanks ozlokie!!!!
I followed your advice, bought the $1 flash image gui from google play, use it to flash the latest kernel to the phone, reboot and I HAVE WIFI!!!!
All without downgrading hboot and mucking around with S-off.
I can't believe this is not documented elsewhere on the internet! I have been searching all day and see nothing like this mentioned.
That app is a GEM. Thanks again ozlokie and thanks again everyone who chip in and try to help.
I can finally take a rest from the PC now. It has been a looooonng day.
Click to expand...
Click to collapse
S-Off is unnecessary at this point, i have a same problem just like you and it solve without using a flash image GUI, just in case you wanna use another ROM, try to push a boot.img, as explain above, mate..
Here you go. http://forum.xda-developers.com/attachment.php?attachmentid=902919&d=1329314313 try this kernal I had the same problem all I did was switched kernals and it works WiFi and all enjoy you may need to download the g u i app from the market you can use this to flash your kernal if you dont have s off yet
Sent from my Evo 3D s off using xda premium
Hey guys,
I'm new to things here. I have done a lot of experimenting though before I'm posting this... and have read A TON of forums trying to find the answers,
I unlocked my Tbolt's bootloader through the HTC method, I've been trying to load CM7, VIRUS, and MIUI rom's and they'll load up into the boot image but will just cycle there and won't go on into the UI.
I've flashed CWK recovery and SU so I don't know why they're not flashing...
The only ROM that I've had success with is the Thunderstick but I don't really like this ROM it's too close to the HTC gingerbread sence
if anyone has any ideas of how I can get CM7 or a VIRUS ROM on my phone please help!!!
Thank you in advanced!!!
The problem you have is because you used the HTC dev unlock method which unlocks the bootloader it leaves you s on. You can't flash custom kernels in recovery with s on which is why you aren't able to boot those roms. Try downloading 4ext recovery. It has a built in tool to flash custom kernels even with s on.
Sent from my ADR6400L using Tapatalk
RMseth said:
...and have read A TON of forums trying to find the answers ... I unlocked my Tbolt's bootloader through the HTC method
Click to expand...
Click to collapse
As noted, HTC's tool is certainly deceiving to users looking to "root" their phones. You need "S-OFF" status in order to flash 3rd-party ROMs. I presume you can obtain S-OFF using numerous non-HTC ways. I know that the revolutionary.io method no longer works if your phone has a newer software version of 605.5 - HTC patched the flaw that was being exploited.
yah it's really deceiving... if I would have know this I would have used another way to gain root... but oh well I'll be trying that 4ext recovery control and see if that will work for me THANK YOU!!!
what ROM's have guys been using that you really like for your TBolt?
RMseth said:
yah it's really deceiving... if I would have know this I would have used another way to gain root... but oh well I'll be trying that 4ext recovery control and see if that will work for me THANK YOU!!!
what ROM's have guys been using that you really like for your TBolt?
Click to expand...
Click to collapse
So far my two favorites are Killasense and iKream. I really like Thundershed but I couldn't get past some very minor issues with it. Here soon you may see something from me.....
Sent from my ADR6400L using Tapatalk
so I tried flashing 4ext I like it a WHOLE lot better then CWK but the setting that you were talking about with the S-on... it says it's not available for my device.... do ether of you know why that would be? do I need to go in and fix a permission or something...
I tried flashing a ROM that was giving me problems before but it still just loads into the boot.img and then just runs the cycle over and over again.
4ext probably uses the "zerg" exploit which HTC and other manufacturers have patched on various phones, but not all. On the TBolt, for example, I'm not aware of how to gain S-OFF if you're on a s/w version higher than 605.5.
I thought you could downgrade and use the revolutionary tool to unlock and gain s off. After you installed 4ext did you run the app before you restarted and booted into recovery. The first thing it asks is if you have s off. When you select no it sets the recovery up to handle flashing kernels.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
I thought you could downgrade and use the revolutionary tool to unlock and gain s off.
Click to expand...
Click to collapse
Sorry if that was confusing... But yes, I believe you have to downgrade to 605.5 to gain S-OFF. If you're on 605.9 or 605.19, there's no exploit that I know of. Ironically, if I recall correctly, you usually weren't able to downgrade or flash an older version but currently VZW/HTC allows it.
Hey guys, brand new here. I've actually browsed the forum for MANY other things in the past but never had to register because I've never had a question that hadn't been answered, but I think I might finally have one.
I have an Evo 4G LTE that's been giving me all kinds of problems. I followed qbking77's video on how to install sdk tools, how to unlock the bootloader, and how to root the device. All of that worked perfectly with no problems whatsoever. Problems started arising when I tried to install my first ROM. I chose the "CleanRom 1.5" because I really liked the simplicity of it, the overclocking capabilities, and the look. So I went ahead and booted into my recovery (TWRP 2.4.4.0), did a factory reset, cleared cache, then tried to install the ROM. After I first "swipe to confirm flash", the "CleanRom" text pops up with all the developers names and etc, so it loads correctly. Then, a few seconds into the flash, whenever it gets to flashing the boot image, the phone just turns off and restarts. I am then stuck at the HTC splash screen until I hold the power button down for 10 seconds and boot back into recovery.
I thought this had to be the ROMs fault, maybe it was corrupt. I re-downloaded it from a different computer and tried again. The same thing happened. Then I tried to install the exact one that qbking77 installed in his "how to" video, CleanRom 1.0 (older version). I downloaded this and tried again, and the same thing happened.
So then I took my suspicions to TWRP. I have the latest installed (2.4.4.0). I did a few searches and found that other people were also having trouble installing roms on 2.4.4.0 with their Evo 4G LTEs, and everyone was saying to downgrade to a more "stable" version. Most people said 2.3.1.0 was the best and most stable, so that's what I tried. After installing it (using THIS guide), I boot into recovery and TWRP loads up just fine, but none of my touch inputs work. The only button that does anything is the power button, which locks TWRP. Then I can't swipe it to unlock it again because it doesn't register the touch inputs.
I then tried to downgrade all the way down to 2.1.8, which is what qbking77 was using in his video tutorial. Also didn't work. Same touch input issue. After more reading, all the replies that I found for people who were having the touch input problem for their devices said "Upgrade to the newest version to fix", which obviously I can't do because that version doesn't flash ROMs correctly (at least on my device).
I've ran out of ideas, any help would be greatly appreciated.
Thanks in advance,
John
Honestly I didn't read all your post ( I'm tired and high) but from what I did read it seems your s-on. If you didn't run lazypanda/dirty racoon or face palm then you're S-ON. This means you have to flash your boot IMG seperately either thru fast boot or flash IMG GUI.
There's a thread called "DON'T PANIC" stickied in general or q&a. All your questions will be answered there.
Good luck man. Once you read that thread you'll be all set.
You should really look into going S-OFF. Just read up on it before you go got it.
Edit............
I read some more. It seems you've upgraded your phone to the latest so you have the new touch panel driver which means your limited to the ROMs you can run. You can only use ROMs based off the new firmware 3.16. You should download meanrom. I think its got a S-ON kernel flasher built right into the ROM and I think you'll be all set with the touch panel driver too. You may have to read a few OPs to get the answers you need.
Again if you were S-OFF you would have a kit more options
Sent from my EVO 4G LTE using xda premium
Yeah, corc is right...the latest firmware has an updated touch panel driver in it that will only work with twrp 2440 (which is why your touchscreen didn't work on 2310) and roms on the 3.16 base. I would recommend getting s-off and downgrading just the touch panel driver, then going back to twrp 2310...any rom should flash just fine then (the new tp driver is not required) and you'll have the added benefit of not needing to flash the kernel separately like you would while s-on.
Sent from my EVO LTE
Thanks for the information, guys! I found a guide on how to get s-off (looks like I'll have to use Ubuntu, though), but I couldn't find any information on downgrading the touch panel driver. Is there an extra step in downgrading it, or does it downgrade with 3.15?
Thanks, sorry for my nubness,
John
No need to apologize for wanting to learn, that's what the forums exist for
Since you're on the latest firmware, which means you have the latest hboot, you'll need to use baby racun from the unlimited.io site to downgrade your hboot (link in the dirty racun thread, stickied in Original Development). At that point you can run dirty racun to get s-off. I think the downgrade from baby racun only affects hboot (I didn't use this method so can't be 100%, but the bootloader is the only thing that matters really when it comes to s-off, so that's my hunch), which means you'll still have the latest tp driver that's giving you problems. So once you're s-off, you can flash the tp img that's under the 3.15 section in this thread to get your touch screen back:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Sent from my EVO LTE
Last bit of advice. Read as much of those threads as you can. Information is all you need to get where you wanna be
Sent from my EVO 4G LTE using xda premium
I had the same trouble with my firmware being too updated for AOSP-based ROM's. But my choice of ROM is Viper4G from Venom anyway, so it doesn't matter. For me, it's easier to load a ROM that's compatible with the latest firmware than to downgrade the firmware.
Viper4G is a bit bloated, though, at about 700 MB. It's based on the Sense ROM, and it contains the Gapps and Sprint bloat. I remove most of the Gapps and Sprint stuff, but the ROM is preloaded with a bunch of goodies, including SuperSU, CPU Spy, OC_Daemon, FX file manager, Venom Tweaks, aLogcat, and it supports Swype2Unlock & Sweep2Wake (though I don't have a compatible kernel for it yet). And, with the right kernel, you could overclock. Plus, I much prefer the Sense UI, but that's just personal preference....
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