Related
Hey,
My phone is faulty, and I need to return it under warranty. I had unlocked the bootloader and installed custom roms, so I just want to check that I've managed to undo all that, and that at the factory they won't be able to tell that I had it rooted.
The main-version is 3.14.980.27, which I couldn't find an RUU to work with, so I downloaded the Stock Nandroid Backup, flashed the boot.img it contained, restored the stock nandroid backup, flashed the stock recovery, relocked my bootloader and deleted eveything from the internal sd card. Having done all this am I ok to send it back for warranty?
The fault is nothing to do with rooting it, but just a little worried that if they find any evidence I rooted it, then they will refuse to fix it and I'll be out $600.
Thanks in advance for all advice.
- ed
There's plenty of threads about going back to stock
You are as stock as you can be ..... they can always tell by the relocked bootloader that its been unlocked ..... so its sending it in and hope for the best.
This is somewhat related. I need to send my phone under warranty due to the dreadful green tint camera problem that arises when some people update to jelly bean, what are the chances of them repairing my phone even though I'm rooted and have a custom ROM? Surely they must know this is not a problem caused by rooting or flashing since it occurs on the stock ROMs as well, right?
Woke up today with the radio dead on the latest Cyanogenmod. Wiped and reinstalled, still dead.
I tried a couple methods to flash the latest radio but nothing has worked.
I am still on CM11 with bootloader unlocked with S-On.
Any ideas?
Otherwise I'm about to head over to Verizon and get another phone.
Have you tried flashing a different rom? Did you recently do something before it stoped working? What do you mean by dead? Is it connected but dosent work, or is it noy connecting to the network at all?
You need s-off to flash radios,kernals,etc.
cmlusco said:
Have you tried flashing a different rom? Did you recently do something before it stoped working? What do you mean by dead? Is it connected but dosent work, or is it noy connecting to the network at all?
Click to expand...
Click to collapse
I was running a CM11 nightly for like 7 days with no issues. Woke up this morning and it just stopped connecting to the network entirely. I tried flashing stock Rom and nothing.
Well as stated above, you need to use firewater to get s-off, then you can flash the kk firmware. It may solve your problem, but it seems strange to work one day and not the next without changing anything. It could be hardware failure. What baseband (radio) version are you currently on?
No worries man I got a free warranty replacement and just got the GS5 today.
Sent from my SM-G900V
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
promsos said:
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
Click to expand...
Click to collapse
Did your firmware.zip have a boot*.img in it? You probably need the old version of the boot.img to match the old software. You might want to find on of the old Verizon RUUs and extract the boot.img from there and try flashing that in fastboot. Message me if the Verizon boot doesn't work for you, I might have some other ideas. I'd say be careful, but you're already in trouble.
Edit: You could also do a nandroid backup and try a custom ROM to get it functional in the short term.
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
promsos said:
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
Click to expand...
Click to collapse
The boot.img from an older Verizon RUU would probably work, but you might have to try a couple to get the right one. The boot.img is directly tied to the ROM version that is installed, and is often called the kernel and tells the system how to boot the ROM.
Make sure you do a backup of your working Viper before restoring the stock one and trying to flash a boot.img.
I don't understand why you re locked the boot loader and flashed a firmware zip just to revert to stock recovery? All you had to do was pull the stock recovery from the firmware.zip in the OTA then flash it via fast boot. Then go ahead and flash the OTA.
You need to now find and flash a compatible boot.img. Just keep trying different ones until it boots.
I'm making a little progress here, thanks for the help. I downloaded a 4.4.3 Verizon kernel, loaded that (after restoring the old nandroid backup) and I'm able to boot, whew... I'm having two issues now, 1) my wireless won't turn on for some reason and 2) I tried installing the 4.4.4 OTA update my carrier released (downloaded via 4G) and it won't apply - I was hoping successfully applying this OTA would fix the wireless issue. Looking at my software version it looks like I'm actually running 4.4.2, could that cause both of these issues? I'm trying to locate a 4.4.2 kernel to load but figured I'd toss out the question in the meantime.
Ashyx - I wish I had a better answer to why I temporarily relocked the boot loader and flashed firmware.zip other than desperation (trying to get that darn OTA). It was a while ago I flashed the firmware.zip file but I thought that when I initially extracted the recovery from the zip file and flashed it I could no longer boot into a recovery, maybe I'm making that up though - I can hardly remember last week lol. I'm an IT guy, so I'm not completely clueless, but I'm far from proficient with mobile technologies, as I'm sure you gathered already.
Anyways, I'd appreciate any insight, in the mean time I'm going to keep hunting for a 4.4.2 kernel to try on this thing. Thanks again to all.
http://forum.xda-developers.com/showthread.php?t=2723159
Try the zips from here, they should have a boot.img for 4.4.2.
Sent from my One M8 using XDA Free mobile app
Ok, I think I'm back up and running. I was able to find a 4.4.2 boot.img that allowed me to once again use my wireless. After getting the wireless working I had to find valid versions of flashlight.apk and calculator.apk to put in data/preload and the OTA finally took....success at last. I really appreciate the help durgis, I'll be grabbing a nandroid of my now working phone right away so I don't run into issues in the future. Again, thank you for the help, very much appreciated.
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
rook79 said:
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
Click to expand...
Click to collapse
Hey rook, I do have the same CID, are you on Cellcom out of Wisconsin? I didn't grab a bare bones nandroid, but i can do a backup, uninstall my apps and do one, or rebuild mine from my unbootable one now that I have everything i need. If you want to try a different ROM you could try Viper, it worked decent for me, just a few quirks when i bounced from wireless to 3G for some reason.
I am with Cellcom. My problems started with the recent OTA update. The update wouldn't take, because of the flashlight.apk. I decided it was time to root this phone anyway and try some custom roms. I've done it with my other HTC phones in the past with no problems. Unlocked the bootloader, loaded TWRP and did a backup. Didn't check where the backup was being put and ended up saving it to internal. Put on a new ROM and wiped my backup. Cyanogenmod 11 is the only ROM that I've had success with. Every other rom that I have tried so far will not complete the initial boot. I suspect that I'm missing something stupid, or it has something to do with the OTA update not completing. Are you running Viper, or did you get the Cellcom OTA update to work?
I was running Viper for a while but now have my phone reverted to stock with the 4.4.4 OTA applied. If you want a nandroid of stock Cellcom 4.4.4 I can work on one for you, it may take a couple days to get it but I should be able to get one.
That would be awesome. I've been looking for a stock Rom for a while now. As you know those are nearly impossible to find. Not having a stock nandroid backup or the OTA update zip kind of put me in a SOL position. Thanks for your help.
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
That worked awesome. Thanks!!!
Hi Guys, (@rook79 , @promsos)
i have the same model and running into similar problem, i was also not able to flash any other rom than SkyDragon, wanted to be able to flash other roms but no luck, i thought its the firmware that wont let me install so i went for S-Off and flashed one of the firmware from verizon, since there was not much help for this specific model and everyone was referring it as a variant from verizon, i did flash one and my problem started, my phone had no signals after flashing the firmware and was still not able to flash any other ROM, i flashed couple of more firmwares and radios to get my network working but no luck, and i got a new problem that the phone keeps rebooting after a couple of minutes it loads into system.
then somebody helped me with the stock firmware 4.4.4 from here and nandroid from this thread, firmware was still verizon, i managed to restore it but still the same reboot issue and no signals, but i was able to download OTA which wont install, everytime i try to install it, it goes to stock recovery with a progress bar 1% filled and then stuck into boot loop and after n number of attempts it boots into system, where again it reboots after a couple of minutes.
extracted the firmware from OTA and manually flashed it and tried to install OTA but still same, i tried to reboot into stock recovery but every time i do that, it goes to black screen and then keep rebooting, i am not able to get to that red triangle screen.
help less clueless trying to find complete RUU for it (not sure if thats going to help)
my partition table has 2 vzw partitions as well because i flashed dottat's RUU for verizon.
can you guys help me with that?
my phone is m8_wlv CID: LRA_001 MID: 0P6B20000
s-off, and i am on a GSM network (not US).
promsos said:
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
Click to expand...
Click to collapse
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
is this what you are looking for? https://www.dropbox.com/s/2oozc291kwe5l9r/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip?dl=0
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
Hi
Do you still have that LRA version?? I need some help
Hi everyone.
I own a HTC One M8 with CID 144, if I remember correctly. It's factory unlocked (all phones sold in Singapore are unlocked, by law), and I upgraded to Lollipop a couple of days ago, with firmware version 4.19.707.2 (Asia WWE).
I have noticed several issues, or perhaps bugs. If these can be resolved in Lollipop itself, that would be excellent - if not, I'd like to downgrade back to Kit Kat.
First - whenever I get a notification and don't unlock my phone to view it, the phone buzzes intermittently, again and again, until I check my phone. It doesn't behave like it did in Kit Kat and like it should in every other phone - vibrate twice, and stop.
Secondly, and related to the above problem, is that all my WhatsApp notifications vibrate, even when ALL notification types, both individual and group messages are set to NOT vibrate. Is the built-in notification system overriding WhatsApp's control over vibration and sound?
Next, I have Wi-Fi disconnection issues. I already sleep relatively far from the router, separated by three concrete walls, and I experienced disconnection, occasionally, in Kit Kat. It happens far more often now, even with Wi-Fi optimisation for battery switched off.
Next, I cannot tap on a notification when it appears to go into that app - also very different from Kit Kat behaviour. I can only slide it away and manually enter the app from either the home screen or the app drawer. In general, I don't much like the new notification look and feel.
Last of all, and ironically, my battery life seems to have decreased after upgrading to Lollipop - contrary to what Google promised.
Are there any solutions to these, or is there a way I can downgrade?
Thanks in advance.
Are you s-off?
spinninbsod said:
Are you s-off?
Click to expand...
Click to collapse
No - not even rooted or unlocked.
Hmm I don't know if you can do that with everything stock. Only way I know is by flashing an RUU file. But you need unlocked bootloader for that, but not sure if you also need to be s-off.
To downgrade the bootloader you need indeed s-off. But there is a possibility that you can downgrade only the software. I am not 100% sure that the older kitkat roms work on the newest hboots but that's a trial and error.
So what you need to do is
Unlock the bootloader
Flash a custom recovery
Install a kitkat rom or restore a kit kat nandroid backup
or
Buy the sunshine s-off method and downgrade also the hboot which is indeed possible with a ruu or a firmware.
Thanks for the clear replies.
However, SunShine needs the Dalvik runtime - Lollipop uses ART. How do I change it? I can't find the option in Developer Options...
Then wait for a sunshine update that might get released or try the first method i described
I confirm that it is possible to downgrade to Kitkat.
I was on Lollipop 4.16.401.10, but I needed the xposed framework.
I first installed custom recovery
then installed a nandroid backup of 3.28.401.6 and via OTA back to 3.28.401.9
dmeerpa said:
I confirm that it is possible to downgrade to Kitkat.
I was on Lollipop 4.16.401.10, but I needed the xposed framework.
I first installed custom recovery
then installed a nandroid backup of 3.28.401.6 and via OTA back to 3.28.401.9
Click to expand...
Click to collapse
Thank you for confirming the idea
Didn't work for me. I flashed a complete stock nandroid 3.28.401.9 Rom. Wouldn't boot past HTC one screen.
Had to RUU back.
Maybe the intermediate step of flashing the ota fixed it for the guy above.
Well, I see. Does anyone have a RUU for CID 044, firmware version 3.32.707.9?
SRSR333 said:
Well, I see. Does anyone have a RUU for CID 044, firmware version 3.32.707.9?
Click to expand...
Click to collapse
While I don't have an RUU for you, I do have this link to give you.
Hi,
I am facing the same issue. After upgrading to Lollipop, all notifications which come in the phone and are not read, the phone keeps on vibrating intermittently. The same happens on both vibrate or normal mode. Also, I've noticed that the notification sound is different as compared to the sound that I selected for notifications.
Whatsapp is where I am facing this issue the most. Even when I've put a group to mute, it still vibrates and keeps in intermittently vibrating until I don't swipe off the notification or read the messages.
DND mode does help in stopping the vibrations but thats not what want. I am still trying to figure out if this is bug or a feature because this is the only thread identifying this issue.
Any suggestions on how to get this corrected?
Thanks
Thanks for all the suggestions guys - but I did it the easy way. I had to send in my phone for service anyway (dirty speakers and cameras) and when the phone was returned to me, I got KitKat 3.32.707.9 back. Excellent.
bajwa2307 said:
Hi,
I am facing the same issue. After upgrading to Lollipop, all notifications which come in the phone and are not read, the phone keeps on vibrating intermittently. The same happens on both vibrate or normal mode. Also, I've noticed that the notification sound is different as compared to the sound that I selected for notifications.
Whatsapp is where I am facing this issue the most. Even when I've put a group to mute, it still vibrates and keeps in intermittently vibrating until I don't swipe off the notification or read the messages.
DND mode does help in stopping the vibrations but thats not what want. I am still trying to figure out if this is bug or a feature because this is the only thread identifying this issue.
Any suggestions on how to get this corrected?
Thanks
Click to expand...
Click to collapse
I managed to find a fix for this constant, repeated vibration issue - it's actually in Accessibility, and also exists in KitKat, but is switched off. The option is called 'Notification reminder'; switch it off and profit.
Worse battery life
Hello,
How can I reflash the stock sense Lollipop rom? I searched about it on google and forums, haven't found something relevant to my case. I got the rom package from HTC Dev website. Now I am running stock sense lollipop 5.0.1. The reason why I want to do this is because the battery life is bad after the update. A lot of people say that their battery life improved after the OTA with 20-25%. MIne didn't . I tried everything: power it off and reboot it after several seconds, 2 factory resets and deleted cache 2 times. I don't know what else to do. If reflashing doesn't solve the problem I want to downgrade to 4.4.4. Two animations, 3 design updates and 4 new features are not worth dumping the battery like that.
Phone is bootloader unlocked and s-on. No root. Everything stock.
Before lollipop, with 4.4.4 I could have location on with battery saving setting, power saver off, auto brightness, 3g and Wi-Fi on all day and every app I could think of.
During the night time I would activate power saver and turn off Wi-Fi and 3g (just the phone on). The battery would last around 1 day and 5 to 10 hours until I got to 35-40 percent. Medium to intense use.
On Lollipop things are not so good. The battery on the same setup and usage is around 19 hours or less. And I can see it dropping while using the phone.
Facebook apps are NOT guilty, or any other app for that matter. I kept the phone factory state for 2 days. Same battery drainage. It's more than a week now since I installed the update.
I'm open for suggestions and solutions. On 4.4.4 it used to be the best phone out there for me.
Thanks and sorry for the lengthy post
Mr Hofs said:
To downgrade the bootloader you need indeed s-off. But there is a possibility that you can downgrade only the software. I am not 100% sure that the older kitkat roms work on the newest hboots but that's a trial and error.
So what you need to do is
Unlock the bootloader
Flash a custom recovery
Install a kitkat rom or restore a kit kat nandroid backup
or
Buy the sunshine s-off method and downgrade also the hboot which is indeed possible with a ruu or a firmware.
Click to expand...
Click to collapse
Installed ARHD 22.2 over ARHD 40.3 , wiped data. It's working flawless. No need to downgrade the bootloader
So I'm s-off and unlocked but I'm tired of all the roms I've tried them all on 4.4!
Now to be honest I've tried some of the lollipop Roms but they take like 30mins to boot as I'm still on kit Kat firmware but some do Boot and run Fine it's just I want more options but I've been scared to upgrade my firmware because I don't want to be stuck there if I don't like it after testing ??? So once again I am T-Mobile HTC one m8 Unlocked Boot loader and S-off
Is it a Cake Walk or a Nightmare going to Lolli and or Back to Kit Kat Firmware ????? thanks for looking and Please Advise
sdwyz74 said:
So I'm s-off and unlocked but I'm tired of all the roms I've tried them all on 4.4!
Now to be honest I've tried some of the lollipop Roms but they take like 30mins to boot as I'm still on kit Kat firmware but some do Boot and run Fine it's just I want more options but I've been scared to upgrade my firmware because I don't want to be stuck there if I don't like it after testing ??? So once again I am T-Mobile HTC one m8 Unlocked Boot loader and S-off
Is it a Cake Walk or a Nightmare going to Lolli and or Back to Kit Kat Firmware ????? thanks for looking and Please Advise
Click to expand...
Click to collapse
It's a cake walk. No problems going back when you are S-Off.
I'm on T-Mobile and ive converted back and forth so many times to try out what's out there (international and GPE) that I'm finally back to stock 4.4.2 Kit Kat Tmo. So yes, it's very easy and so many guides to follow.
Sent from my HTC One_M8 using Tapatalk
So on more Very Important Question k 2 actually but this one is of super importance
Is there away to do it with out loosing s-off and root ?
And Second can you guys Direct me to the best and or Safe/Simplest Guide as Most are so up in the air and Confusing ???? Thanks and Please Advise
First of all thanks for passing by my thread , my case is a really strange one , i have an galaxy s6 edge t mobile with DOJC wich is the lastest build , i unlocked thru a direct cable software method provided by unlockbase , as always i rooted the phone , i used unikervel ver 8.0.0.2 and did the unlock , problem is that the fingerprint stopped working forever eversince , and no matter what i do it just displays the same error " an error ocurred with the fingerprint sensor " now i tried everything in my knowledge and google researching , tried the erasing cache method , flash stock bootloader and system plenty of time , downgraded a tons of times even installed a custom rom to see if there was any change , it was working before so im wondering what could happen , ive done this with multiple s6 edge with older builds and never has happened to me , today i downgraded againg do DOl1 and something more weird happened , the imei is there as always but the numbers after the slash are gone says /null now this hasnt affected anything but i dont know why it happened , the second werdiest thing its that the sensor version , in the secret menu for testing everything gives me a null version , does anybody know what can i do to get my fingerprint working againg ?? every lil comment would help thanx a lot
Sorry to hijack his thread. But I see you got root on the tmobile dojc firmware.
I got the edge today and have been going through post trying to figure out what needs to be done.
I know that two needs to be flashed through Odin. Not sure on the version tho.
And that a kernel needs to be flashed then the SU.zip
My question is what kernel. No one specifically says which one to use for the DOJC firmware and the BL option in Odin is where the kernel would go correct?
So
Odin -install tarp
Odin- kernel
And then flash the su zip in twrp
Am I missing anything ?
And hope somebody chimes in to help with your issue at hand ! Good luck
There no need my friend , just flash unikernel Ver 8.0002 thru odin adn the phone will be instantly root
epicroot said:
Sorry to hijack his thread. But I see you got root on the tmobile dojc firmware.
I got the edge today and have been going through post trying to figure out what needs to be done.
I know that two needs to be flashed through Odin. Not sure on the version tho.
And that a kernel needs to be flashed then the SU.zip
My question is what kernel. No one specifically says which one to use for the DOJC firmware and the BL option in Odin is where the kernel would go correct?
So
Odin -install tarp
Odin- kernel
And then flash the su zip in twrp
Am I missing anything ?
And hope somebody chimes in to help with your issue at hand ! Good luck
Click to expand...
Click to collapse
Installing stock kernel should make your fingerprint scanner work. Once you change the kernel, poof no scanner.
Pp.
Thanx for the reply my friend i did that alredy still does not work i think it just broke the moment i rooted coincidentially
PanchoPlanet said:
Installing stock kernel should make your fingerprint scanner work. Once you change the kernel, poof no scanner.
Pp.
Click to expand...
Click to collapse
I recall reading somewhere that not tripping knox when rooting had something to do with scanner not working.
Did you "not" trip Knox?
Pp
Have had this happen with some of my customers. Flashing stock firmware solved the issue.
Can download stock OJC here
STOCK OJC DOWNLOAD
I recommend Odin 3.10.6
ODIN 3.10.6