Flashed Speed Rom last night and am getting a wifi error. of course all benefit of the rom is negated because battery life sucks when the phone is constantly trying to acquire a connection. i read somwhere that potentially flashing faux kernel would help, but I'm s on and not certain I can flash kernels effectively out of TWRP. Any help will be greatly appreciated. And just so you know, there is one thread mentioning the kernel fix but no response from the op as to whether it worked. Is this Rom still supported? Perhaps I just need to go another direction
jsteve01 said:
Flashed Speed Rom last night and am getting a wifi error. of course all benefit of the rom is negated because battery life sucks when the phone is constantly trying to acquire a connection. i read somewhere that potentially flashing faux kernel would help, but I'm s on and not certain I can flash kernels effectively out of TWRP. Any help will be greatly appreciated. And just so you know, there is one thread mentioning the kernel fix but no response from the op as to whether it worked. Is this Rom still supported? Perhaps I just need to go another direction
Click to expand...
Click to collapse
Well speed rom definitely has no problems like that. I think it's because of your recovery and being s on. When you're s on I don't think recoveries will flash. You should switch to 4ext since the smart flash option lets you override s on. But I highly recommend s off though. Speed Rom isn't supported anymore anyway by Eclipze so that's likely why you didn't get your answer.
When you flashed, did you wipe everything?
Did you flash a kernel after you flashed speed rom? It probably gave you an error since you're s on.
So what I'd do is either go s off (recommended), or just get 4ext. How about both? If you get 4ext then your backups won't work since they aren't compatible. And also enable smartflash so you can flash custom kernels while s on.
Also be sure to check out my rom I made (Kaioken Rom) in the development section.
Sent from my HTC_Amaze_4G using Tapatalk 2
I didn't flash a kernel. Extreme noob so not sure how to go about s off. I assume if I go with 4ext: all need to flash back to stock first so I can make a new recovery prior to flashing a rom. How's battery life on your rom
jsteve01 said:
I didn't flash a kernel. Extreme noob so not sure how to go about s off. I assume if I go with 4ext: all need to flash back to stock first so I can make a new recovery prior to flashing a rom. How's battery life on your rom
Click to expand...
Click to collapse
also if I flash 4ext using Hanson's toolkit will I need to delete twrp or will it give me a choice of which recovery to boot to
jsteve01 said:
I didn't flash a kernel. Extreme noob so not sure how to go about s off. I assume if I go with 4ext: all need to flash back to stock first so I can make a new recovery prior to flashing a rom. How's battery life on your rom
Click to expand...
Click to collapse
The battery life on my rom is excellent so far. It's even better than speed ROM's battery even though my rom has faux 24 built in and over clocked. I haven't even under clocked yet!
What you should do is go to the general section and read the guide that aj made, there is also hasoons toolkit I'm the development section so you can flash 4ext with that. That's a very easy way.
Once you flash 4ext, make sure you enable smartflash. On twrp you can't flash kernels while s on, that's why people think 4ext is superior.
If you didn't flash a kernel then being s on probably caused the problem if speed rom has a custom kernel. S on blocks the custom kernel, so smartflash and s off fix that problem.
Sent from my HTC_Amaze_4G using Tapatalk 2
If I want to install 4ext via hansoons toolkit do I delete twrp or how do I establish which covert to use? Also I thought if I used the toolkit I'd be perm rot but after runner ng root checker last night there is a problem with my root. Is that all related to being s onn and what is son vs s off in layman's terms?
Regarding this WiFi calling, can one turn it off after installing. I only want it when I have no regular cell signal.
toolkit
jsteve01 said:
If I want to install 4ext via hansoons toolkit do I delete twrp or how do I establish which covert to use? Also I thought if I used the toolkit I'd be perm rot but after runner ng root checker last night there is a problem with my root. Is that all related to being s onn and what is son vs s off in layman's terms?
Click to expand...
Click to collapse
When you flash a new recovery, the recovery your phone already had is replaced with the new recovery, so you do not have to delete anything, as it is done automatically.
Done properly you can easily have perm root without S-Off.
Try this newer toolkit instead--I think it also explains how to flash a different recovery, such as 4EXT:
http://forum.xda-developers.com/showthread.php?t=2437057
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
berralac said:
Regarding this WiFi calling, can one turn it off after installing. I only want it when I have no regular cell signal.
Click to expand...
Click to collapse
In the ROM I use, Android Revolution HD 5, in the network settings wifi calling can be disabled as easily as clicking a check box like other settings that toggle. I suspect that's the case with any ROM.
pbergonzi said:
When you flash a new recovery, the recovery your phone already had is replaced with the new recovery, so you do not have to delete anything, as it is done automatically.
Done properly you can easily have perm root without S-Off.
Try this newer toolkit instead--I think it also explains how to flash a different recovery, such as 4EXT:
http://forum.xda-developers.com/showthread.php?t=2437057
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
In the ROM I use, Android Revolution HD 5, in the network settings wifi calling can be disabled as easily as clicking a check box like other settings that toggle. I suspect that's the case with any ROM.
Click to expand...
Click to collapse
Thanks. I have looked everywhere I an think of, but no toggle. It was there in the stock ROM. When I click on the "with fi calling ready" notification it takes me to the network settings, but there are none. Is there perhaps a way to just uninstall this zip?
wifi calling
berralac said:
Thanks. I have looked everywhere I an think of, but no toggle. It was there in the stock ROM. When I click on the "with fi calling ready" notification it takes me to the network settings, but there are none. Is there perhaps a way to just uninstall this zip?
Click to expand...
Click to collapse
I apologize, seems it's missing.
You can read this:
http://forum.xda-developers.com/showpost.php?p=44265984&postcount=116
and this--from a search for "wifi calling" in the speedrom thread:
http://forum.xda-developers.com/showpost.php?p=52185080&postcount=4067
According to this post, it's been removed from the version in this post:
http://forum.xda-developers.com/showpost.php?p=25399375&postcount=3
You can also turn off wifi when you are making calls.
To romove it, I used titanium backup and un-installed the wifi settings and the ims service. Fixed it for me. thanks for your help.
works
berralac said:
To romove it, I used titanium backup and un-installed the wifi settings and the ims service. Fixed it for me. thanks for your help.
Click to expand...
Click to collapse
Nice job--good for you.
Related
So what is the easiest method to root this device?
Can I install 4ext instead of cwn?
And what is this stuff about different ucl* roms I keep seeing,not sure.
http://forum.xda-developers.com/showthread.php?t=1518962
Kernel- http://forum.xda-developers.com/showthread.php?t=1504920!
I would run stock rom with a overclocked kernel get the "set cpu" app... set it to 1.84 ghz this run fine on my note seems very stable.min 384.If it seems unstable make you click set to boot "off" until everything seems stable then click set to boot enabled.
SysAdmNj said:
So what is the easiest method to root this device?
Can I install 4ext instead of cwn?
And what is this stuff about different ucl* roms I keep seeing,not sure.
Click to expand...
Click to collapse
Da_G Has an odin root available in the DEV section for the stock GB. As far as I know there are only 2 types of recovery for the Note Braway's CWM and the TWRP 2.1.2 ( I use CWM.) As far as the UCL*** those are all ICS leak builds. UCLE2 being the most recent. Personally I have pretty much stuck with Team Perfections builds but depending on what you want another ROM may suite your needs. If you install one of the new roms they keep root access and install either SU or superuser and are all flashable via CWM, however I assume you need to be rooted prior to installing which is where Da_G root comes in.
wish777 said:
http://forum.xda-developers.com/showthread.php?t=1518962
Kernel- http://forum.xda-developers.com/showthread.php?t=1504920!
I would run stock rom with a overclocked kernel get the "set cpu" app... set it to 1.84 ghz this run fine on my note seems very stable.min 384.If it seems unstable make you click set to boot "off" until everything seems stable then click set to boot enabled.
Click to expand...
Click to collapse
Stock? I hate touchwiz lol. Im honestly going to try a few custom roms.
cjsspape said:
Da_G Has an odin root available in the DEV section for the stock GB. As far as I know there are only 2 types of recovery for the Note Braway's CWM and the TWRP 2.1.2 ( I use CWM.) As far as the UCL*** those are all ICS leak builds. UCLE2 being the most recent. Personally I have pretty much stuck with Team Perfections builds but depending on what you want another ROM may suite your needs. If you install one of the new roms they keep root access and install either SU or superuser and are all flashable via CWM, however I assume you need to be rooted prior to installing which is where Da_G root comes in.
Click to expand...
Click to collapse
So I guess 4ext doesnt work on the note? Also, its easy to brick this device?
I didn't see any flash able zips for it in the dev section so I don't think its supported. Rom manager for the most part is unsupported also except for fixing permissions after flashing new stuff. This is my first experience with android (iPhone convert haha) I haven't had any bad experiences flashing yet but general rule of thumb is read and re read instructions for specific roms and make sure its specifically for the i717 not n7000 or anything else because that will hard brick. Also use only approved ics kernel because of the super brick bug out there
Sent from my SAMSUNG-SGH-I717 using xda premium
cjsspape said:
however I assume you need to be rooted prior to installing which is where Da_G root comes in.
Click to expand...
Click to collapse
Nope, you can just flash cwm with Odin and then flash a ROM without rooting first. The ROM is rooted.
The only reason to root first is if you want to run titanium backup to nip any apps you may have installed prior to deciding to ROM.
Also that "super brick bug" is only on exynos processor equipped phones, I717 has a Qualcomm. So if you stick to just kernels MADE FOR THIS DEVICE then you can't ever encounter it.
Ah was never 100% clear on that cuz I rooted prior to running saurom rom. As for the kernel thing that's what I meant about not using the n7000 stuff prolly should of been more specific didn't want ya to make a mistake on that.
Sent from my SAMSUNG-SGH-I717 using xda premium
Yup.
And now that you've made the glorious switch to Android, when you upgrade to the next beast that catches your eye, you can take the titanium backup folder from your note, drop it in the sdcard of your new phone, install cwm, flash a ROM, then restore your backed up apps.
Easy peasy
So I need to verify, I can completely install a rom that gets rid of touchwiz? Also would this same rom improve battery charging time?
If I could just flash cm7 on this baby I'd be fine with that.
Cm7 is not supported on this device
There are a couple aosp roms floating around, but they are still in early development, alpha stage.
studacris said:
Nope, you can just flash cwm with Odin and then flash a ROM without rooting first. The ROM is rooted.
The only reason to root first is if you want to run titanium backup to nip any apps you may have installed prior to deciding to ROM.
Also that "super brick bug" is only on exynos processor equipped phones, I717 has a Qualcomm. So if you stick to just kernels MADE FOR THIS DEVICE then you can't ever encounter it.
Click to expand...
Click to collapse
+1....Common misconception is that you need to be rooted to flash a custom ROM. CWM is the first thing I would flash. Like Studacris said, everything else is easy peasy.
Sent from Galaxy Note
ok so i d/l odin and it goes through i followed all steps right, and it just says sdded
removed and then it freezes after 9 total of them.... what do i do? the phone still says
downloading....
do not turn off target
been like this for over 5 minutes. i downloaded drivers and all that. step by step.
studacris said:
Nope, you can just flash cwm with Odin and then flash a ROM without rooting first. The ROM is rooted.
The only reason to root first is if you want to run titanium backup to nip any apps you may have installed prior to deciding to ROM.
Also that "super brick bug" is only on exynos processor equipped phones, I717 has a Qualcomm. So if you stick to just kernels MADE FOR THIS DEVICE then you can't ever encounter it.
Click to expand...
Click to collapse
so let me get this straight also im new. but right now all i have done is use odin to put cwm recovery on my phone and i have not installed superuser yet. because phone would not recognize with computer. so since i only have cwm i can go to this site on my phone, download a rom from my phone, to my phone and then go into cwm and zip it from there. is this correct?
joshmingus said:
so let me get this straight also im new. but right now all i have done is use odin to put cwm recovery on my phone and i have not installed superuser yet. because phone would not recognize with computer. so since i only have cwm i can go to this site on my phone, download a rom from my phone, to my phone and then go into cwm and zip it from there. is this correct?
Click to expand...
Click to collapse
Exactly. No need to root stock ROM if your going to flash a rooted ROM anyway. Make sure you do a backup of your stocker before doing anything else. The only reason to root your stock ROM would be to backup all your apps and data. If you don't do that, you have to start from scratch. What's the issue you're having with the superuser zip?
Sent from Galaxy Note
Make sure your not trying to hook the phone up to the PC while in recovery.
Sent from Galaxy Note
anyone gonna answer my question???
usmarine2141 said:
anyone gonna answer my question???
Click to expand...
Click to collapse
Don't really understand it to be honest. Need a step by step of what you did and what your trying to flash. Could be many things.
Sent from Galaxy Note
trying to root it...
I figured that, but there's more than one way to do that. You flashing cwm or kernel?
Sent from Galaxy Note
ok it said pass... what do i do now? its still on the downloading screen??????? i put the pda. tar in the pda box and then said pass... stuck on downloading screen what nex?
---------- Post added at 12:28 AM ---------- Previous post was at 12:24 AM ----------
ok so nobody explains you had to choolse something to flash after it said that!!! now my phone says firmware upgrade encountered a issue
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Both files are now uploaded!
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
droidiac13 said:
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
That was the purpose of it
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
Wow you are fast. Thanx
Sent from my HTC One X+ using xda premium
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
dekend said:
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
Click to expand...
Click to collapse
Pull boot.IMG from my zip. Place it in the kernels folder of my toolkit. Boot into bootloader. Press "with this command" to flash the boot.img.
Support is done for the night. Goodnight!
Sent From My HTC Amaze 4G via Someone's Room
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Yes and yes. You might need to relock the bootloader if you flash a stock RUU (not officially available for AT&T yet). Once installed you can unlock and root again.
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
hasoon2000 said:
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
Click to expand...
Click to collapse
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
wmg316 said:
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
Click to expand...
Click to collapse
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Downloading now! This marks day 3 with no phone! I hope this ends my nightmare. Thank you so much.
hasoon2000 said:
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Click to expand...
Click to collapse
Thanks. Just to make sure I have the steps straight (in a manual method):
Copy 'evitareul_dev_base.zip' to my internal memory ("/storage/internal memory/" in Solid Explorer)
Unlock device with Unlock Code from HTC.dev
Install AT&T Recovery provided in the All-In-One Tool; reboot to bootloader and flash recovery
fastboot flash recovery recovery.img
Enter Recovery and flash the 'SuperSU.zip' from the all-in-one tool folder
At this time I would be stock and rooted, correct?
Return to bootloader and install kernel provided in the 'AT&T Stock Deodexed Rooted Base (Devs Only)'
fastboot flash boot boot.img
Return to recovery and perform wipes....here is where I am unsure after reading the "Important and Read" threads about the /data/media. I am accustom to doing these wipes from TWRP on my OneX: (1) factory reset, (2) wipe dalvik cache and (3) wipe System....Is that what I need to do for the OneX Plus?
Install 'evitareul_dev_base.zip' ROM from recovery
I appreciate your response! I don't want to mess anything up...I guess I'm over precautious!!
I wiped, guess i wiped the wrong thing, now rom wont boot. i can get to recovery, twrp, but how do i now get this zip on to the phone since i cant boot? mount in twrp im not seeing anything on my computer. ATT X+
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
wmg316 said:
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
Click to expand...
Click to collapse
yes i did but it was the wrong zip. It was mikes 1986 rom, at the time i didnt realize it wasnt for ATT. So after wiping, i guess i wiped the stock rom. Wiped system, data, and davlik. now it just sits at HTC quietly brilliant screen.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
trying the sideload adb in twrp but that didnt work, says no device found. when i do adb devices my device shows though. now i, trying to get this stock rooted installed.
Wiping System, Data, Dalvik definitely wipes the stock ROM!
Hmmmm. Mike's OP states nearly on the first line of his thread: "Not working with AT&T One X+ LTE"
All that I've read is that you have to have the ROM on the device before booting to recovery...but there was a statement that it could be adb pushed:
http://forum.xda-developers.com/showthread.php?p=34358646#post34358646
With "no device found"...I'm not sure what to do...Hopefully one of the devs will ring in for you.
title
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
thanks. im sorry im noob i think are many people look around for this maybe if you include AT&T in the thread title more people are happy. excuse my english. thanks againg.
---------- Post added at 08:59 AM ---------- Previous post was at 08:00 AM ----------
hi i have unlimit internet no lte (i dont wan it because change my monthly pay) with my past at&t vivid i change the apn and still with unlimit internet with 5 to 7 mb speed with my international HOX i change the apn and still with unlimit iternet but no more than 3mb speed. now with your AT&T Stock Deodexed Rooted Base can i change the apn and still with my unlimit internet. i dont wan LTE. thanks. i go now to buy my new at&t HOX+.
Lloir said:
providing you dont touch the "wipe internal memory" button all is good, i use TWRP and i've been performing about 20-30 wipes a day, and my internal sd is still intact with my TWRP backups
Click to expand...
Click to collapse
from the other thread
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
xFatex said:
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
Click to expand...
Click to collapse
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
lreyes said:
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had no access to my TWRP Recovery, I actually fixed that though.
The Kernel is changed and now I have no Data access? I think my ROM is not compatible like suggested. (Sense ROM)
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
The current situations has changed sadly.
I have no custom ROM just Sense.
The Kernel: Bulletproof-EVO-v1.4.
ROM: Default Sense?
This is my first attempt at really rooting/adding kernels just messing around and doing damage.
Now instead of WiFi I have no Data Service with this Kernel and ROM combo. I will check out your links thank you very much.
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
xFatex said:
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
Click to expand...
Click to collapse
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
EDIT:
NOTE:
I AM currently reading your bottom link about Fixing system wipe.
xFatex said:
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
Click to expand...
Click to collapse
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
lreyes said:
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
Click to expand...
Click to collapse
S-ON.
I am attempting to download MeanBean after reading Fin's Fix.
Though I don't know if FlashImage GUI will work.
I also have to figure out how to flash .apk files too...
Sorry about the bother... I really am far below Novice at this I should have had someone holding my hand step by step lol.
Okay, so the problem with the Kernel originally was it wasn't compatible?
Then the next one with the service error was I suppose the same thing?
Then when I tried to restore apparently I wiped my phone of all Data resulting in a bootloop and being no one has the exe file for the factory RUU of the latest version for the Evo 4g LTE I had no way of restoring any of the files?
So then I stalked Fin's suggestions eventually lead me to MeanBean. at least it got me up and running... I attempted to back up with TWRP.
Which apparently doesn't work (I have to learn how to backup else where... Lets add it to my list.)
But after I attempted the back up I also attempted the instillation of "Operation Jelly Bean" I love the ROM I love the theme I love the sleekness
Apparently I am missing something with my touch panel software. I wish I could have kept the ROM but couldn't sadly (If you know what I am doing wrong I would love to keep that ROM in the future)
So with another failed ROM I tried to restore... which there was no restore when I went to do so... I was a little frustrated from my constant bricking as is...
I attempted factory restore apparently also wiped everything (Internal sd, external, everything.) I don't know what is up with that do you have any clue if its a glitch or am I just wiping it?
I also do Stock restore that does absolutely nothing for my phone anymore...
I will flash it... and it does nothing... it still runs like TWRP (disclaimer etc) but won't go to the twrp boot screen... this is a bit frustrating.
Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance
You can either, accept the ota and then root(which I never liked accepting a ota cause Im cautious of downloads being corrupt.) Or you can download a odin version of kitkat and flash thru odin then root(which is what I did)
Thank you very much for your answer MrWicked! One more question if I may ... I just came from US Cellular with the Note 2 to Sprint with the Note 3 - we had very little development there compared to here. I have read a ton of topics on here today about Knox, NAB engineering bootloader, Odin ... etc. and I understand that and how to follow instructions, but I see several different ways. I was wondering which method you used or would suggest? All I am trying to accomplish at this point is root, custom recovery, a (close to) stock rom, (hopefully) not trip the Knox trigger, and run titanium backup (which I read there are issues with that I have to fix afterwards).
Ok couple things, no matter what root method you chose once you flash a recovery it will trip knox. So that being said you have a couple options......
1. You flash via odin the kitkat update and use the "kingo" root method which I personally have not tried and can't give much input on. It is not supposed to trip knox it leaves you rooted but with your stock recovery. Once you flash a recovery you trip knox. But you are stuck with a stock rooted rom in which you could use titanium backup.
2. You flash the kitkat via odin, and you use Chainfire's method(which is what i did personally) I have always had good luck with Chainfire's root methods. but then it trips knox and you can flash a recovery and flash what ever roms you like. But at this time technically you warranty is voided with Samsung.
str8nitro said:
Just picked up my note 3 running 4.3 an hour ago and have not unlocked/rooted/custom recovery it yet, still 100% stock. There is an OTA available and I was wondering if I should take it before rooting?
Thanks in advance
Click to expand...
Click to collapse
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
rcjunky said:
I would wait on kitkat. I have been running it on a stock n3 for about a wk now and I'm not liking it at all. my bluetooth for my car is very buggy, stock email is buggy and I'm getting a 3rd less battery out of it. I would have 70% left at the end of my day now I'm lucky if I have 50%. I would wait for kitkat until they work out the bugs.
Click to expand...
Click to collapse
Thanks for the advice on this, may I ask what Rom you are on?
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
Yep
MrWicked1 said:
Yep
Click to expand...
Click to collapse
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!
str8nitro said:
I have used TWRP before but mostly CM, I am not familiar with PHILZ at all, Is one better than the other? I really appreciate your time and advice here as I am sure others with the same questions will as well. Thanks!
Click to expand...
Click to collapse
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.
MrWicked1 said:
Personally I love twrp but it doesn't always seem to go as smooth with it. Philz is a modified version of Cm. Philz is rpetty much the go to for least amount of problems.
Click to expand...
Click to collapse
I will give it a go then, I thought I read something about "NAB engineering bootloader" with Philz, is this something I need to read up on more or self explanatory once I get into it?
Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it
MrWicked1 said:
Haven't used the Engineering one personally to me it didn't give me any benefits for now for me to flash it
Click to expand...
Click to collapse
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.
str8nitro said:
SOrry for so many questions, but I saw that a few people has issues. Hopefully last question and I will be golden ... For Philz I see to downloads in the link provided by rlmiller - philz_touch_6.12.9-hltespr.tar.md5 and philz_touch_6.12.9-hltespr compared to just one file for TWRP - TWRP KITKAT hltespr-recovery-4.4.img. To use Philz do I need just one file or both? The reason I ask is because in the instructions it says "And lastly....
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file
you now click start and wait until it says pass and reboots. Unplug and wait for startup"
But it does not give instruction for Philz, which is 2 different files that are not the same as the TWRP.
Click to expand...
Click to collapse
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.
MrWicked1 said:
No just flash the stock....let it load up....reboot into dl again...odin cf autoroot....boot up....then reboot dl mode again then you can flash which ever recovery you like twrp or philz.....then load up reboot to recovery I would make a backup then flash Sacs rom....then you should be all good to go. And no prob on the questions it's better to ask then not.
Click to expand...
Click to collapse
Sorry, I think I didn't explain well. I am going to go with Philz because it worked well for you, but my question was which Philz file:
philz_touch_6.12.9-hltespr.tar.md5
or
philz_touch_6.12.9-hltespr
do I use in whe I get to the TWRP area of the instructions:
Now powerdown phone and start up in download mode again.
start odin and plugin phone again.
now click in phone slot and browse to TWRP file <----------------------------------- here
you now click start and wait until it says pass and reboots. Unplug and wait for startup
Yeah instead of the twrp file you use the philz tar.md5
str8nitro said:
Thanks for the advice on this, may I ask what Rom you are on?
Been reading up on Sacs v1 and it looks like I wouldn't have a problem if I go this route since I am on mj4. It looks like I can follow the instructions completely from rlmiller here http://forum.xda-developers.com/showpost.php?p=50794223&postcount=20 and do my root and everything in one stop shopping. Also from what I have read once I go to kit kat I can't go back to jelly bean ... I would assume there would be no reason to back up my stock rom after rooting since I can't go back ever.
Click to expand...
Click to collapse
I am stock no root at this time. ota update.
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
MrWicked1 said:
Obviously it varies per phone but what are you running? I had the opposite effect Bluetooth in car is wayyyyy better and battery life is great. But I'm running Sacs v1 KitKat so that might be why we are having different experiences also.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am stock no root at this with the ota update.
Hi Folks,
I have just installed CWM recovery V 6.0.4.6 using ROM Manager app in my Galaxy S3 I9300 running on stock android 4.3 . I rebooted the device to check it and it was successfully installed. While I tried to reboot device through an option in the recovery, it showed up two messages as follows,
Message 1:
ROM may flash stock recovery on boot. Fix? THIS CAN'T BE UNDONE
1.No
2.Yes - Disable recovery flash
Message 2:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. No
2. Yes - Fix root (/system/xbin/su)
I selected option "2.Yes - Disable recovery flash" from Message 1 and again option "2. YES fix root (/system/xbin/su)" from Message 2.
Why these messages are getting displayed? Is there any problem now?
Also please let me know whether it will revert to Stock Android Recovery by selecting Option "1.No" from Message 1. If so again I have to flash CWM recovery?
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks. So shall I revert back to stock recovery by selecting 1.No from message 1 and then flash cwm using odin?. Will it be fine?
I have also read that many folks facing same kinda issue even they flashed CWM recovery using odin.
Please advice that will there be any issues if I flash Cynogenmod 10.2 now?.
Any help on this? Please.
mpadhu said:
Any help on this? Please.
Click to expand...
Click to collapse
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
boomboomer said:
Don't use rom manager on the s3.
Click to expand...
Click to collapse
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
Click to expand...
Click to collapse
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
dxppxd said:
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
Click to expand...
Click to collapse
Hence the statement:
"As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. "
dxppxd said:
It's better to install cwm recovery through means other than rom manager to avoid problems.
Click to expand...
Click to collapse
My point is that of the two, Rom Manager is the one that works. I have never had issues using Rom Manager to install recoveries. Although, I always install the first time using fastboot... So my anecdotal impressions may not apply here.
Care to explain your statement? (Which is the intent of my original message. Why the Koushik XDA witchhunt?)
I would search, but XDA search is borderline unusable.
Thanks!
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
None of the stock roms I've used have ever tried to restore stock recovery, it's just left there from other devices that do it.
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
Click to expand...
Click to collapse
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
When asked those i always select "no" to both. Never had an issue.
mpadhu said:
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
Click to expand...
Click to collapse
Looks like a successful backup to me.
t1n0m3n said:
Looks like a successful backup to me.
Click to expand...
Click to collapse
Thank you. I have successfully flashed Cynogenmod 10.2.
I can see my old android files still present in the internal memory. I did wipe data/factory reset, wipe cache partition and wipe dalvik cache but still the files are present. Will it cause any problem if I remove those files? If No will a factory reset work to remove those files?