I have an AT&T One M8 that I converted to GPE a while back. I am trying to upgrade to Lollipop 5.1 from 5.0.1 I can VolDn / Power into hboot, select recovery and it reboots to the dead android with the exclamation, but when I do the VolUp / Power nothing happens. If I hold it long enough it will reboot completely. I guess I'm doing something wrong but I have no idea what.
Any suggestions?
Sounds like you don't even have a custom recovery. And you should post this in the other m8 forum since AT&T has no gpe
ctfeet said:
I have an AT&T One M8 that I converted to GPE a while back. I am trying to upgrade to Lollipop 5.1 from 5.0.1 I can VolDn / Power into hboot, select recovery and it reboots to the dead android with the exclamation, but when I do the VolUp / Power nothing happens. If I hold it long enough it will reboot completely. I guess I'm doing something wrong but I have no idea what.
Any suggestions?
Click to expand...
Click to collapse
First suggestion is to read the Forum Rules on posting, as this does not belong in the Development Section. Then another would be read here and here, then understand regarding your device and what is requried to have GPE.
I am on AT&T, and also on Full GPE, but I am also boot unlocked/super CID, with the the latest ATT lolly firmware, fully converted to GPE, running this ROM.
Related
hboot is 1.15 i am running 1.22.651.3 i have s-on and am unlocked... i am trying to get s off i am trying to flash to cm10 but i cannot get any were can someone please point me in the right direction ... i have read and read and read and nothing adds up to what happens.. .i use clock work mod to download and install when it boots into recovery it says it installs but the screen stays black i have to hard reset (power vol down and camera) it to get anywere then it goes back into recovery and i use the back up file i had to get my phone to work... what am i doing wrong...
No offense to the developer but I would steer clear on CM10 on the Evo. It ran fine on my Nexus but it really didn't do well on my Evo. The MMS didn't work worth a darn. The biggest issue I had was no data. I reflashed it. I wiped everything. I read the instruction 20 times. It just doesn't work well and has some bugs. There seems to always be some major bugs in the AOSP line of roms. Even on the Nexus G AOKP was a constant headache. I wish I could just say do these three steps and all will be flawless. Sorry, that just isn't the case.
Sorry to point this out but this topic goes on the q&a section not on development
HTC EVO LTE
Not sure what kc is talking about I have flawless data and mms on cm10. I have 4g and it works totally fine with no data issues whatsoever. Now the op is posting in the wrong place, but I would gladly help if the post was more clear. So are you s-off or not? If not it will require you to either get s-off or flash the boot.img separately. If you are s-off try using twrp not clockwork. I have been on twrp since I got the Evo in July and have had zero flashing issues.
Sent from my EVO using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
I will add mms has been flawless since using Gosms as has been discussed in the cm10 thread multiple times. Not sure if mms works otherwise, but go sms solves it if it is still being worked on. If you don't like/want to us Gosms then just install it solely for mms because it does send and receive them and they show up in the stock messaging app as well.
Sent from my EVO using xda premium
i have s on and all i can access is twrp and hboot
I'm not entirely sure how you managed to put [Q] in your thread title AND ignore the box that says "Is this a question?". There is a very, very clearly labeled section for questions and answers, and your question is one of the most asked here.
Here's your two step fix:
1. Learn where to post. (please)
2. You are S-ON. The reason why you see a black screen is because S-ON users can't flash kernels from recovery. You have to do it seperately. Custom ROMs like AOSP or ROMs that use custom kernels can't be flashed normally on S-ON.
3. No, you did not read. At all. We can tell because the very first thread in the Questions and Answers forum (http://forum.xda-developers.com/showthread.php?t=1869377) says the following:
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
Click to expand...
Click to collapse
In the future, if you have a question, consider placing it the forum that is meant for that. Sorry to sound like an ass, but I'm in a bad mood.
thank for the help...
I am running Cyanogen Mod 10.0 on the phone for 2 weeks and not even one issue. I updated to the latest TWP before I installed the ROM. I am never going back to gay Sense. Sorry but I can't stand sense. I love the build quality of the EVO more than any other phone on the market. I really hope they come out with a Nexus Device.
Download CyanogenMod from their site and you will not have an issue.
Go to the aokp thread and at the beginning says how to push the boot.img vías fast boot after that you should be fine flashing the rom
Sent from my EVO using xda premium
Can someone delete this thread? or move it? or help this guy read instructions on how and where to post things?
Yes I'm closing this. And OP WATCH your language. YOU posted in the wrong area, not the other way around... So it's YOUR fault and No ONE herer owes you ANYTHING.
On a side note, if everyone quotes the offensive language I have to delete that too... just an FYI
Howdy all,
I've been out of the loop for a bit with my TFP since the screen/digitizer broke.
When I last had it working I had installed Rooted_CWM_SparkyAsusStock_9.4.2.28-signed.
If I wanted to change the ROM, would I go back to stock with the same Android version, then update? I do have my tablet NVFlashed and the blobs all saved, but I'd like to avoid any possible brick.
Head on over to the androwook thread and search a ways back. Team Androwook had posted a guide to upgrading to the Jelly Bean boot loader that had an easy flashable zip for ya.
Nightpath said:
Howdy all,
I've been out of the loop for a bit with my TFP since the screen/digitizer broke.
When I last had it working I had installed Rooted_CWM_SparkyAsusStock_9.4.2.28-signed.
If I wanted to change the ROM, would I go back to stock with the same Android version, then update? I do have my tablet NVFlashed and the blobs all saved, but I'd like to avoid any possible brick.
Click to expand...
Click to collapse
If you have NVFlash you can never brick.
Go to second post here http://forum.xda-developers.com/showthread.php?t=1674827 and follow "Upgrade instructions for ICS"
So I must be on ICS now, so I'd want to upgrade to JB correct?
I take it I can just jump from whatever I have installed now to one of the modded JB releases? Which one is considered the best so far? Stock, Androwook, Cyanogen?
Only want to watch movies, internet and a few games.
I was on stock ICS when I got nvFlash access and started throwing roms at my prime. I basically had to update to the JB bootloader before I could flash any JB-based rom. As far as I remember, there's no going back from the JB bootloader.
I simply flashed the stock JB firmware which includes the JB bootloader from this thread:
http://forum.xda-developers.com/showthread.php?t=1927494
(this is the WW version, there's another thread for the US version, not that I think it matters)
This updates bootloader/rom/recovery (stock/stock/TWRP) to JB, and from there you can flash anything JB-based. Mismatching rom/bootloader will not work (i.e if one is ICS and the other is JB or visa versa) then you won't boot. I did this, but I already had nvFlash so I wasn't worried.
I have NVFlash already done...waiting for my LCD replacement screen so I can put my TFP back together and use it again.
OK, could I use the stock Asus JB to update, then flash over to Androw00k?
I'm already rooted, nvflashed, etc.
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Nightpath said:
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Click to expand...
Click to collapse
It's nothing to do with twrp. I'm guessing you have now flashed the jellybean bootloader.
Hold down volume down and power and when the 4 icons appear press volume up on the first one "rck"
Or have you flashed the wrong version of twrp and put the jellybean twrp on ICS?
flumpster said:
It's nothing to do with twrp. I'm guessing you have now flashed the jellybean bootloader.
Hold down volume down and power and when the 4 icons appear press volume up on the first one "rck"
Or have you flashed the wrong version of twrp and put the jellybean twrp on ICS?
Click to expand...
Click to collapse
I flashed twrp but only have 3 icons when I do pwr + vol down. Data Reset / Fastboot / Android.
I'm going to need a How-To for idiots guide. I've been working long hours, not a lot of time off...and I'm tired as hell all the time. I really need assistance.
Nightpath said:
I flashed twrp but only have 3 icons when I do pwr + vol down. Data Reset / Fastboot / Android.
I'm going to need a How-To for idiots guide. I've been working long hours, not a lot of time off...and I'm tired as hell all the time. I really need assistance.
Click to expand...
Click to collapse
Think I have it all figured out...Androwook installing now with JB
TWRP was giving me some massive problems, had to work around it and reinstall a few times before updates would work.
Hi guys I need some urgent help. I'm wanting to go back to stock recovery so I can install OTA updates when they are available. I made the mistake of rooting my phone without thinking about updates. I just want it back to stock so it's all nice and easy to use and I don't need to worry. I've found this thread which contains the stock recoverys but when I try and flash the STOCK RECOVERY 1.54.206.5 file I can't even into recovery and just got a error symbol up.
My phone is on the o2 network (I'm in the UK) and my phone is 4.4.2 Software number 1.54.206.5. Am I right in thinking it is that file I need?
If someone could take 5 minutes of their time to help me out it would be ever so much appreciated
EDIT - When Ive sent the stock recovery and I go to boot into it the symbol is a phone with a warning sign. Is that just what it is suppose to do or is it because it's wrong? I read on the thread "You can test originals by flashing them. If you see a phone with warning sign it's the HTC original one."
PLEASE HELP!
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
es0tericcha0s said:
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
Click to expand...
Click to collapse
Ohh yes brilliant! . I panicked and thought it meant it couldn't find a suitable recovery to boot into. It's all sorted now and hopefully I will have no problem installing OTA updates when they become available. Thank you
No problem. Glad all is well.
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
XtremelyNooby said:
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
Click to expand...
Click to collapse
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
jball said:
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
Click to expand...
Click to collapse
I've read about S-OFF
I am S-On
XtremelyNooby said:
I've read about S-OFF
I am S-On
Click to expand...
Click to collapse
You need s-off to update firmware. Once you have s-off, then the firmware I would recommend for use on AT&T's network is 3.28.1540, which is posted on the ROM thread here: http://forum.xda-developers.com/att-htc-one-m8/development
Otherwise, your other option is to return to full stock ROM and stock recovery and install the official 4.4.4 OTA once it rolls out from AT&T (rumored mid-December) which will automatically update the firmware. After the OTA, you will then need to re-install custom recovery, to flash a custom ROM.
Hey guys, a series of unfortunate and idiotic events has lead me to somehow unroot my phone and get it up to 4.4 with a stock rom.
For a what feels like an eternity I've been running freeza's "[ROM|NK4|KitKat|4.4.4] Galaxy Note fre3 Hybrid De[Odex] v2.26b -BeastMode Kernel-" the previous version was recommended to me years ago by wwjoshdew and I never strayed from it. I've lurked here for a while and I understand that repeat questions to solved solutions are frowned upon and punishable, but I feel my issue is a bit unique.
So my question: What do I do to get back to my beloved ROM? I'm ok with wiping everything but my external SD, as long as I can get concise steps without any assumptions that I know any lingo or terminology I will be happy. i currently have ODIN as well as TWRP 3.0.2.0. the current status of my phone is "android upgrading: Starting apps", it's been that way for maybe an hour now, I tested it and I can boot into TWRP recovery, as well as download mode. HERE'S THE REAL KICKER THOUGH: my power button does not work, so stock recovery mode isnt an option for me, the phone does not register any activity from the power button whatsoever and i lack the know how, money, tools, and patience to remedy this. I simply power my phone off or on with a series of combinations done with a usb cable, the home button, and my volume down key.
SO how screwed am I? I CAN go to stock rom, but i really miss all of my goodies that I'm used to and my xposed installer...( Tried just running stock rom with twrp and rooted. installed xposed didnt work so gave up and came here)
Thanks for reading this far and hopefully being able to help me. I understand otherwise.
Edit: currently flashing back to this rom N900PVPUDNH7_N900PSPTDNH7_N900PVPUDNH7_HOME.tar.md5 via ODIN because I got tired of waiting for the upgrade screen and I need my phone.
Welp, so much for that. I tried various things and now I appear to be hard bricked.