Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Tommyboy77 said:
Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Click to expand...
Click to collapse
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
hello
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Tommyboy77 said:
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
Click to expand...
Click to collapse
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Tommyboy77 said:
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Click to expand...
Click to collapse
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Hello
es0tericcha0s said:
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Click to expand...
Click to collapse
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Tommyboy77 said:
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Click to expand...
Click to collapse
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
hello
es0tericcha0s said:
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
Click to expand...
Click to collapse
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Tommyboy77 said:
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Click to expand...
Click to collapse
Then it is recommended to run the newest RUU to make sure your partitions, OS, radio, and firmware are all properly matched. Once that happens, you can just fastboot flash a recovery back and then redo whatever 4.4 rom you want at that stage. Yea, it sucks to have to do the extra steps, but some things you just have to do to make sure everything works properly. It never pays to cut corners when you need your phone to function correctly.
http://forum.xda-developers.com/showthread.php?t=2658910
Related
I installed the CLEANrom tapped edition rom after wiping everything as instructed. It boots and initially I had issues with wifi working, but that seems to be working after flashing a stock kernel. Now if I try to play anything with sound or change the volume using rockers or in the phone itself it forces a reboot.
Any ideas?
Thanks
You are probably on old firmware and need to flash the patch
http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/GB%20Firmware%20Patch.zip
Sent from my Rezound
Still having issues
Thanks for the reply. I actually ended up flashing it back to the rom that I had. I also made sure I flashed it to the original recovery as well which is amon ra. The rom I flashed it back to was the clean rom standard 4.4.
Unfortunately, I'm having the same problem no. If I go into the dialer and hit a number it freezes and force reboots. If I hit the volume rocker, it freezes and force reboots. It just force reboots for almost everything except for texting and going into apps.
any thoughts? The 4.4 worked fine on the firmware that's on here, and I did do the wipe and reset before I installed back. Maybe I bricked it?
Definitely not bricked. You wouldn't be able to even boot if bricked. What firmware are you on?
Here is some information
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Mr. Lando said:
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
Even though your on ics, it looks like your on gb firmware. Search for the gb patch for ics and flash in recovery and problem solved
2.11 hboot is gb firmware, 2.21 or up is ics firmware
Mr. Lando said:
The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
It runs just great on the correct firmware lulz
Correct Process for Updating firmware
Hello,
You stated that 2.11 in the hboot indicates gb firmware. Do you know a link to the correct thread that would give me the appropriate process for updating the FW one that will work with the CLEANrom 1.4 dev version? I got the wifi working again after flashing the "old firmware patch" and then reloading CLEANrom 4.4 everything went back to normal. However, I hate sense and I would like something without it which is what the dev version provides, but if I cannot get wifi working then it's kind of useless. When I say "if I cannot get wifi working" what I am indicating is that when I try to run the cleanrom dev version 1.4 WIFI gets stuck on "turning on" but never turns on and eventually just says "error" with no further details. I searched through forum feeds and found a few forums that hinted on steps, but many people have seemed to be confused by this issue in the past and perhaps it is related to firmware as you said.
Thanks
i would wipe everything again, reflash the rom, and then immediately the patch. that should fix everything. key thing is flash the patch before booting the rom. ive flashed the patch after rebooting before and had things go haywire. not a promise that it will work, just letting you know what ive run into
Scosler has everything listed in the op for the rom, and all files are there as well. There's a bunch of different instructions for however your phone is set up.
Sent from my Rezound
Continuing...
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
If s on and on 2.11 hboot Method 4:
-Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
-Reboot to recovery
-wipe data / Factory Reset
-Flash ROM
-Flash GB Fimrware Patch
-Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
-Reboot
-Profit!
Based on what you typed you didn't flash the firmware fix...
Mr. Lando said:
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
Click to expand...
Click to collapse
If i were you i would either s-off or flash one of the ics leak ruu's. that will help. there are many ways to solve your problem but those are your best bets
My issue is resolved. Thanks for all of your help and insight.
Sent from my ADR6425LVW using XDA
Care to share what you did? I am having exact same issue . . .
nvm - resolved: applied GB Patch right after ICS ROM flash (who would have known - I was kind of ignoring those GB patch instructions, since they did not apply to ICS).
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
You can simply flash a stock rom that has the update & flash the newer stock kernel that goes with it but you wont be able to update the radios. You wont lose any info this way unless something goes wrong.(always backup everything just in case something goes wrong).
As for backup, you will only be able to backup aps & data with titanium backup or some sort of program like that because If you do a nandroid backup and then restore after applying the update, you would be restoring your old rom basically over the new one and lose most update enhancements.
You should just follow the thread here http://forum.xda-developers.com/showthread.php?t=2155069 and go S-Off. I know you will have to restore everything because you will wipe your phone when you do this but its only gonna make things easier for you in the future.
Do a nan backup and save it in case you want to use it in the future and go back to what you had. Once you have S-Off, you can flash kernals, radios, & roms and put in any version you want.
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Spaded21 said:
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Click to expand...
Click to collapse
Have you unlocked the bootloader? (this step is usually done in connection with rooting the phone at the htcdev.com website). If you have an ulocked bootloader, then you can flash an alternate recovery (eithe cwr or twrp) and do a nandroid backup.
Then follow the steps to get s-off. Note: the step where you have your data wiped is unlocking the bootloader, not obtaining s-off. If you already have an alternate recovery, and root, then s-off generally will not wipe your phone. But do an nandroid backup in cwr or twrp just in case Although a nandroid won't backup pictures etc.
Once you have s-off, flash the stock (but rooted) rom you linked to in step 4. This step SHOULD flash the stock kernel if the .zip file was prepared properly. If you boot into the rom and have flickering or wifi issues, then you will need to flash the stock 2.04 kernel (in fastboot). You can also verify if the new kernel was installed when the rom is booted by looking at the Settings:About:Software Information:More (baseband, kernel etc). You should see there kernel version 3.4.10. The baseband (radio) should be 1.01.01.0110 once you have updated the radio (see the step below). The kernel file is the boot.img file you were asking about. The modules will already be built into the stock rom.
While in fastboot (not recovery) you can flash the updated radio files (that will make the baseband referred to above be 1.01.01.0110.
The time when you need to worry about flashing a kernel (boot.img) and modules is if you are s-on, or if you are s-off and the zip file was prepared as you were s-on. When you flash a "kernel", it consists of a boot.img file, along with some extraneous files (the module). When you are s-off, these can both be flashed together while in recovery. When you are s-on, the boot.img file must be flashed from fastboot (or else an alternate method using an app like Flash Image GUI). Because until recently, most DNA's were s-on, the kernel developers prepared their files for s-on devices, with instructions for s-on devices.
When you flash a rom that uses a different kernel than the one you are using, if the .zip file is prepared for a s-off device, then there are no additional steps necessary.
You may want to do a factory reset when you flash the updated 2.04 rom. I think it would be wise. As I said earlier, you shouldn't lose your /sdcard partition UNLESS you haven't already unlocked your bootloader. s-off doesn't reset your device.
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Spaded21 said:
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Click to expand...
Click to collapse
I was looking for this exact solution as well. This was before we had s-off. For a while my solution was to freeze a couple apps in TB so the OTA pop up would stop popping up. I think it was HTC DM 1.0.2219251543..... and HtcDm 1.0.221982913.... Looks the same but they are different.
I like stock but I eventually flashed ViperDNA. It looks like stock but you are able to customize the $h!!t out of it. Its an awesome ROM that I highly recommend. Although you might want to wait until he comes out with 1.2 (the new version with the latest firmware) becuase you have to wipe data. Data wiping isn't a big deal if you use TB.
Ether way you go - Stock ROM or ViperDNA - The recommended way to wipe your device is this way:
(I'm using TWRP but CR should be similar, might be in different menus)
Backup everything using TB
Backup Pics and other docs on internal SD card (JUST IN CASE)
Make Nandroid Backup in Recovery
Wipe Menu-> Wipe Dalvik Cache (some like to wipe 3 times others think its just a waste of time)
Wipe Menu-> Wipe Cache (Factory Reset wipes cache but I like to wipe cache anyway just for completeness )
Wipe Menu-> Factory Reset
Wipe Menu-> System
Don't Format Data and Don't wipe Internal Storage. You will loose SD card contents.
Once you install your ROMS, flash your kernals, flash radios...whatever you want to do...You can restore apps and data from TB
As always, follow the ROMS instructions on their page for more information.
Only Restore User Apps and Data
Never restore any system apps in RED. May not be compatible with new ROM
You can however restore system Data that is in Yellow or Green (DATA ONLY)
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Spaded21 said:
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Click to expand...
Click to collapse
Yeah, I had the same problem on the Thunderbolt, nothing stable. Viper however feels great. I would definitely freeze the HTC apps in Titanium Backup to get rid of the annoying pop ups. I noticed Viper has them uninstalled.
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
I'm actually running that rom right now.
You don't need to flash the radio if you don't want. If you are happy with your cell reception, and battery life, as well as wifi, then you can stay on the original radio.
Or if you'd like to try the new radio, you can flash that (once you have s-off) with this thread: http://forum.xda-developers.com/showthread.php?p=38197525
I'm not sure if there is a radio flash prepared to go back to the original radio. Generally speaking, once to are s-off, you can change radios at will.
From what I understand, if you flash the rom you linked to, and the radio above, then you will have everything from the update, except the updated hboot. I haven't bothered changing my hboot. changing hboot won't affect the day to day operation of the phone, but it can change the fast boot commands that are available. Until I see a good reason, I am not going to worry about my hboot.
FYI: about changing radios, from what I understand, the radio file is the code that tells the phone how to communicate with the towers. It tells the phone how to adjust the power output of the radio according to the strength of signal from the cell. This can be very aggressive, leading to better signal, at the expense of battery life (increasing power output of the phone radio takes more power from the battery), or it can be conservative, with a little lower quality signal, but conserving battery life.
It seems that the engineers at the carriers are constantly tweaking the radio code to find a sweet spot between signal quality and battery life. Different carriers may tweak the radio for the same phone with a different priority. Sprint may prioritize signal, while verizon prioritizes battery. So each carrier may have a different radio file for phone that is in the same phone family. And then each carrier may have multiple radios. On the thunderbolt there were about 6 or 7 I think, but it is generally believed that newer radios work better than older ones.
Some people on xda will often experiment to see which radio file works best for them, depending on where they live and work.
I always try to be careful to only flash redid that others have reported to work with my device, rather than experimenting personally. I would think that you can brick your phone flashing the wrong radio file.
Sent from my HTC6435LVW using Tapatalk 2
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
Firmware is the Android system. The Droid DNA is on on 4.1.1 (Jelly Bean). That version has not changed in the new OTA update so I don't know why that ROM even mentioned it.
The Kernal is the interface that alows the software to access the hardware. A more detailed explanation can be found here: http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
HBOOT is 'kinda' like your BIOS in windows. It is the bootloader. It is the first thing that is loaded on your phone. This too I believe has not changed with the latest OTA update.
This is the change log for the 2.04.605.2 710RD update
Bluetooth connectivity and volume level for specific models have been improved
Enhanced reliability and stability of the Contacts List have been made
Enhanced Recent Apps functionality has been improved
Incoming messages display with the correct timestamp
Improvements to Hotspot connectivity have been made
Improvements to Audio Quality for wired headsets and earpieces have been made
Improvements to default browser for zooming capability have been made
User can load videos on HuluPlus
Wi-Fi Connectivity has been improved
As you can see it is mostly stuff related to your radio so the radio is the main part you would want. I personally just updated my radio and din't worry about anything else.
---------- Post added at 12:15 PM ---------- Previous post was at 11:56 AM ----------
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
I don't think it is deodexed otherwise it would tell you. I think deodexed is good if you want to theme.
I'm using the first one, which isn't deodexed. But I'm keeping my rom close to stock this week
Next week, when the Viper rom has been updated to 2.04, I'll be flashing that, and probably a theme.
You indicated that you aren't currently running any mods or themes. Unless you are looking to change, I would suggest you flash the first rom you linked, which is stock, except for the root capability being added to it.
The de-odexed rom you asked about will have been modified, deleting the .odex files so that the rom can further be customized by themes etc. When a phone boots a rom that is missing the .odex files, it will take longer to boot because it will essentially create the missing .odex files on the fly while booting. But when you are modding your rom, adding themes etc., existing .odex files get in the way, so that is why developers remove the .odex files, even though the rom will take longer to boot. Once the phone is booted, whether the rom was odexed or not becomes irrelevant.
For now, if you are looking to be on the latest radio and HTC rom, I suggest you get s-off, then flash the basic 2.04 rom (the one you linked to first), and the updated radios. Hopefully HTC will soon release the updated source files for the 2.04 kernel, and then we will have more customization.
If you are looking to customize now, I would get s-off, then flash the updated radios, but stay with a rom based on the original released rom and source (like Viper). The latest Viper rom (with updates to 1.1.3) has modifications so that you won't have to worry about getting bugged to update your ROM for 2.04. If you decided to go with Viper, it is a little confusing when viper is updating from 1.1 to 1.1.1 to 1.1.2 to 1.1.3, because it uses an over-the-air (OTA) update process similar to the stock OTA update. So you may see notices for updates - but the updates would be for Viper. Once you have gotten your phone s-off, you don't need to worry about updates causing problems.
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Spaded21 said:
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Click to expand...
Click to collapse
Congrats!
I think that rom you used wasn't set up properly to flash the boot.img from recovery, so that is why you had to do it manually. As time goes on (and there are more users with s-off), I think most new roms will be set up properly, so you shouldn't run into that again.
The whole process wasn't that hard, and using TiB made it really easy to get everything back.
So how do I go about removing bloatware now that I have S-Off and I am deodexed?
Although there are several ways to start removing bloatware, one of the easiest ways is to go into TiBu, and freeze apps. Make a nandroid backup first, and start slow.
Some apps have dependencies, you freeze one, and another might not work, like contacts and dialer.
After you have frozen an app, and are confident that it isn't necessary, you can delete it if you want.
Sent from my HTC6435LVW using Tapatalk 2
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
I would highly recommend using the OTA blocking zip to kill the update messages. I'm not very handy with posting zips yet but search the threads for the disable OTA. I am on the Viper DNA rom also but I put the OTA blocking on just in case. If I were on my PC instead of my phone I could have posted the zip file for you. I'm sure with each rom the developer has added a file to make sure the OTA is killed but you can never be too sure.
Easiest way to get 2.04 OTA for rooted DNA phones
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
fastboot flash recovery dlx_recovery_signed.img
Click to expand...
Click to collapse
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" upgrade to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
zanyguy said:
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" up to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
Click to expand...
Click to collapse
Thanks zanyguy for the procedure and process outline. I have a question regarding my current format and was wondering if going to a stock rooted version would work for me. Since every end user is different then there are different things they want of course. For me the process is very simple. I like a very lean system. I also like to try and achieve many things to look as close to AOSP as I can get and keep functionality. My current setup has the phone unlocked, rooted, s-off and running Viper 1.1.3. My radio is the OTA update radio of 1.01.01.0110 and my kernel is the same 3.4.10-ga02d2c6. What I wonder is this. Should I even bother trying to flash the stock Rom? Is there any benefits to doing so? And if I do give it a spin should I just restore the Viper DNA rom or re flash anew?
Thanks
Hello everybody. I recently flashed my phone with the latest Cyanogenmod rom for the HTC one, using the wHil recovery flasher. However after playing with the rom for a bit I decided I want to swap back to stock everything that came with my phone. What is the process to go about doing this?
Thanks!
Did you make a nandroid before flashing the Rom, if yes then just flash it then flash stock tmobile recovery img then relock the bootloader..just do a quick search and you find out how to do it... But it will still say tampered on bootloader... But ota will work cause that only requires stock recovery and stock Rom
Sent from my HTC One using Tapatalk 2
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
GeePM said:
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
Click to expand...
Click to collapse
Yes, that's what I did, and OTA updates work perfert
That's great to hear. So I shouldn't experience any issues when I return to the stock rom like loosing any kind of features and such?
I've been having issues trying to adb push this backup to my phone since 4.2 andriod has things locked down in regards to backups. Been getting the device not found issue, so I'm going to try and push it using a different PC soon hopefully. With where I work I can't live without WiFi calling/texting that Cyanogenmod lacks
So I have the stock backup through clockwork mod and I have it in the proper /clockworkmod/backup folder. Problem is, clockwork mod touch isn't detecting that I have any backups to restore. So I decided to make a fresh backup just to see where it was placed so I could put this other backup I downloaded in there.
Problem. I can't find it anywhere. I don't know where to put it. I don't know where clockworkmod touch wants it to go. Any ideas?
EDIT: Apparently there are two of these folders? *looking more*
EDIT 2: Clearly, If I try to restore from the saved backups, it shows the backup I made, but no amount of searching is finding it through any of my file managers. I'm finding the backup I downloaded, but not the one I made. wtf? Are there hidden folders or something? I have root access.
EDIT 3: There are apparently two clockwork mod folders on my phone. Clockwork mod is saying that it sees the test backup I made on 6-10, but when I check in my file manager for a backup, it shows me the folder with a 4-26 backup which is what I want to restore. The FILE MANAGER sees a folder with 4-26, whereas clockworkmod sees a folder with a backup of 6-10. Both folders are apparently clockworkmod/backup. Does anyone have any idea what's going on here?
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
change yearThe
GeePM said:
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
Click to expand...
Click to collapse
Nevermind! Just went to the upgrade section and got it
GeePM said:
Nevermind! Just went to the upgrade section and got it
Click to expand...
Click to collapse
4.2?????
blackangst said:
4.2?????
Click to expand...
Click to collapse
Nevermind, I still don't have it. Was 4.2 pushed out yet?
GeePM said:
Nevermind, I still don't have it. Was 4.2 pushed out yet?
Click to expand...
Click to collapse
No. Not on TMobile.
Hello Everyone,
Ok so not sure where to start, umm yesterday i decided to root my phone i have the HTC Desire C from Cricket wireless. I was successful at unlocking my bootloader and rooting the device. Now for some reason im unable to flash a custom rom or whatever to my device, not sure if im doing something wrong, but i must have screwed something up because i cant even perform a factory reset or a hard reset to the device at all, and the google play store no longer works and the sync icon never goes away. Now when i attempt to flash the custom rom the clockwork recovery tool wont allow me to do a full wipe which i believe must be completed before you can even install the roms.
any help or suggestion would be greatly appreciated.
Thank You.
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
es0tericcha0s said:
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
Click to expand...
Click to collapse
Actually you know what, I think i know what happened. when i was trying to flash the rom i also flashed the gapps for jelly bean into my phone which is running ice cream sandwich currently because the rom flashing failed. So basically i think the gapps apps are conflicting with the stock apps on the phone ? It seems like all the google apps are the only ones messing up and the google account sync is messing up also the google playstore and google plus crashes a lot so its only the google apps. so what do you think and how do i restore the phone ? I didnt make a back up recovery either. If someone could also just walk me through how to flash a custom rom like CyanogenMod i believe everything will probably fix its self (hopefully). oh and as for the Clockworkmod i think its the actual clockworkmod recovery the one with a black hat, i accessed it through bootloader recovery options, anyway it doesnt allow me to flash any custom roms ive tried like 3 so far and everytime it ask me for some update file or something about a update not sure.
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
es0tericcha0s said:
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
Click to expand...
Click to collapse
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Silver5150 said:
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Click to expand...
Click to collapse
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
es0tericcha0s said:
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
Click to expand...
Click to collapse
Ok not sure what the RUU is and how im suppose to use it to return to full stock, and correct i cant perform a factory reset in bootloader period, when i select factory reset it does nothing but reboot and say HTC "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action." then it stays like that and nothing else happens period, not sure what im doing wrong but no worries im going to buy a new phone tomorrow and never use custom roms again, if i want a upgrade ill just go out and buy a new phone which i should have done in the first place, only thing ill be doing is rooting my devices for now on and nothing more thank you for your help.
Well, once you have a custom recovery, you don't factory reset from the bootloader screen, but via the recovery itself. That's one of the main reasons for the recovery - better options to wipe the phone as well as backing up, restoring, and flashing the custom stuff. Not saying you shouldn't buy another phone, but no reason to give up on this one. I just think it would require a bit more reading since you don't see very familiar with what to do with CWM after you installed it. Have you even booted INTO CWM?
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.