Related
Hi. I recently rooted and installed a WWE "sensefroyo" rom off the internet.
And I just figured out (since a couple of hours) that my speaker isn't working AT ALL.
Before, it worked when you left the battery out for a minute and put it back in. it worked flawlessly. But after a while it'd go back to being messed up.
Now its screwed. and wont work at all.
I didnt realise I needed to get it replaced till now.
I really need the Telus Desire rom asap. As I just emailed them about it, and most likely need to get it replaced/fixed. And I dont know much about Telus, if you lose warranty privileges if you root/custom ROM it.
Unless I can tell them that I installed the official 2.2 ROM (dont know if it needs root) off those .exe files (the RUU_Signed) kind. (They didn't work for me. So i rooted using recovery)
Or if you can link me to one where I can find a rom that does not require rooting, and has an .exe file and a copy of a .zip kind.
I wrote a lot here, and its all over the place.
Right now. Either link me to the Telus Desire rom. or one where I can flash without rooting.
I am going to unroot as soon as I get one of those two things^
Thanks. I just hope you guys know what kind of freaky situation I am in.
Where did you buy it, and how long has it been since you bought it?
Depending on those factors, you may not need to worry too much.
I had it activated on a 3 year contract almost a week ago(Not even a week)
What do you mean by I will not have to worry about these things?
Is Telus a carrier that is more on the 'chill' side of things?
EDIT - So I just got off the phone with Telus.
The representative told me if I installed something that Telus did not release. That basically voids my warranty. So now I really need to get back exactly as it was before.
Can someone please help me out here?
I need to go to a dealer soon to get it replaced.
I am pretty sure I can unroot it myself with no issues I guess.
I really need something that matches with the same stats as a Telus Desire.
You should probably try starting over.
If your rom is still rooted, get ROM Manager and install clockworkmod.
You can install something stable like opendesire and wipe data/cache.
You should be fine, unless you really have some unusual desire to be on Telus' rom.
I was wondering if someone can post what their 'software version' looked like on a Telus Desire
Maybe then I can try to get the same radio and 'stats' as a factory device.
I got on a rep and they also said that the worst thing that can happen is your device will be sent back.
They even said that some people wont even notice the software change and stuff.
If at the end I cant get a Telus rom. I would LOVE a link to an Eclair build rom. Possibly one that is an official.
Didn't you nandroid backup prior to moving to froyo?
From what I understand you can restore from that.
mfpreach said:
Didn't you nandroid backup prior to moving to froyo?
From what I understand you can restore from that.
Click to expand...
Click to collapse
I actually have NO idea what nandroid was.
I just followed instructions off a tut on xda.
So I cant seem to find factory eclair roms.
Now I read around a little bit more.
And just feel completely stupid.
Please. Someone. A factory Eclair build.
start by getting clockworkmod installed.
Without knowing what state your device is in, it's tough to help you.
but with clockworkmod recovery going, you will easily be able to switch between roms.
Honestly you couldn't have bought it that long ago, just return it to the store, the guys don't even know how to check.
routehero said:
start by getting clockworkmod installed.
Without knowing what state your device is in, it's tough to help you.
but with clockworkmod recovery going, you will easily be able to switch between roms.
Click to expand...
Click to collapse
I already do have it. Thats how i installed all the different roms (Leedroid, Nightly Cyanogen, and then eventually the official one)
Hold on for a couple of minutes as I can provide you with some of my hboot and so recovery options. (Using the WiFi hot spot at the moment)
Other then that. Here is my 'software version'
android 2.2 with the latest 32.43.00.32U_5.09.00.20 radio
Kernel is
2.6.32.15-g1fc4045
[email protected]#1
Build #
2.06.832.1 CL207528 test-keys
Software Number
2.06.832.1
with the obvious webkit 3.1
hboot info?
BRAVO PVT3 SHIP S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.20
Jun 10 2010, 12:12:05
Used ClockworkMod Recovery v2.5.0.1
Yes it is an SLCD display?
you needs more? - tell me what exactly you need and how I can get it
download opendesire 3.5.0, wipe data/cache, flash that.
after you set it up, let us know what's not working.
If I were you, I would go back to the store you got it from, with your recipt and contract. You have 14 days to return any phone. That's how I got my desire, I returned a Hero. Make sure you take everythign back you got, charger, phones, etc. Tell them waiting to get a band new phone fixed is a waste of your time, and you want to exchange the phone right away.
So long as you have a sense UI ROM running, I doubt they will know you have rooted the phone. The guys where I bought the phone didn't know too much about it.
If you managed to get a tech support guy to tell you they might not notice, you clearly have the power to get what you need from people. Be forceful if you have to, within 2 weeks they should just give you a brand new phone. After 14days though, your gonna have to live with no speaker, hope it's actually a software issue(doesn't sould like it if even stock it was failing), or send it back and hope they don't miss it. To the best of my knowledge there are no Telus official roms to be found, but there are many official roms from other places. As long as your background doesn't say VodaPhone or something, how will they know?
ajanu said:
If I were you, I would go back to the store you got it from, with your recipt and contract. You have 14 days to return any phone. That's how I got my desire, I returned a Hero. Make sure you take everythign back you got, charger, phones, etc. Tell them waiting to get a band new phone fixed is a waste of your time, and you want to exchange the phone right away.
So long as you have a sense UI ROM running, I doubt they will know you have rooted the phone. The guys where I bought the phone didn't know too much about it.
If you managed to get a tech support guy to tell you they might not notice, you clearly have the power to get what you need from people. Be forceful if you have to, within 2 weeks they should just give you a brand new phone. After 14days though, your gonna have to live with no speaker, hope it's actually a software issue(doesn't sould like it if even stock it was failing), or send it back and hope they don't miss it. To the best of my knowledge there are no Telus official roms to be found, but there are many official roms from other places. As long as your background doesn't say VodaPhone or something, how will they know?
Click to expand...
Click to collapse
Telus has 30 day DOA over the counter exchange.
YAh but he made the mistake of telling them e rooted and flashed it (why on earth would any one do that i dont know)
So they have flagged that IMEI in the system as void.
Your best bet is to try doing a wipe and flashing back to the telus 2.1 rom and radio, you will, the recovery is gone though as we dont hava ruu.
Actually. I didnt. I went straight for asking the question off a residential phone that uses Rogers. So they don't know who I was or any account related things.
The first time I called though, I told them that the speaker wasnt working and I wanted it replaced.
So no my IMEI is not flagged, guarantee you that part.
I will try using the OpenDesire 3.5.0 with "clear/wire cache"
This might work for you and i think its your best bet.
http://forum.xda-developers.com/showpost.php?p=6710085&postcount=3
Go to the above thread, follow the instructions and make a gold card.
then go to the following thread, download official froyo rom and flash it. It looks almost the same as the original rom.
http://forum.xda-developers.com/showthread.php?t=753672
I cant seem to do the goldcard thing.
I am using the official 2.2 at the moment.
It does look the same as 2.1 Telus itself.
What does it mean over here?
# Ensure you have unzipped the SDK, then open a command prompt to the extract location. Change to the 'tools directory.
# Type
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
and press enter. You should get a very long number which looks like this: 532600bd227d9c0347329407514d5402.
Click to expand...
Click to collapse
I cant seem to do the "command prompt" location thing.
Someone wanna help me? maybe with some screenshots?
I am done making the GoldCard. What does it even do though?
It has something to do with switching to the factory rom..
Now. I have issues with the RUU. It does not wait long enough for the phone to be in bootloader.
EDIT - Is there any way I can "remove" or uninstall the Superuser Permissions app and the "Wi-Fi Hotspot" app? To make it appear even more legitimate.
da pavinator said:
I am done making the GoldCard. What does it even do though?
It has something to do with switching to the factory rom..
Now. I have issues with the RUU. It does not wait long enough for the phone to be in bootloader.
EDIT - Is there any way I can "remove" or uninstall the Superuser Permissions app and the "Wi-Fi Hotspot" app? To make it appear even more legitimate.
Click to expand...
Click to collapse
I packed up the telus stock rom from a nandroid dump you can try it.
http://www.mightyrom.com/mrx/MRX/Bravo/Stock/Telus_HTC_Desire_Stock_2.1_NoRADIO.zip
Hey I needed to unroot my phone too and I tried a bunch of things then I was following procedures to root my phone again because I tried installing the Rom that was posted by the person that posted before me and I messed up and got lots of errors when I got the phone started and had to force close a bunch of things constantly. Anyways I followed step 3 of the tut for rooting TELUS desires on this forum site and when it restarted I got my stock TELUS Rom back unrooted. This is the step I followed
3. Go to HBOOT, this is done by shutting down your phone and powering on the device while holding the Power button down and pushing Volume down at the same time, once HBOOT is loaded do a wipe (Clear Storage). You can navigate the menus by using the volume rocker and the Power button to select your option.
forum.xda-developers.com/showthread.php?p=7818278 is the link to the tut I was following.
I dunno how it worked but it did, I got my stock TELUS Rom by doing this. Maybe I got lucky and maybe you might too. Oh and just for your info, the tut I used to root my desire initially was this one forum.xda-developers.com/showthread.php?t=750888. Good luck
Someone tell me how I can clean my phone, I need to wipe it completely, and reinstall everything from scratch. Really wish I had rooted first, would have been alot easier, alot more resources for root.
Thariz said:
Someone tell me how I can clean my phone, I need to wipe it completely, and reinstall everything from scratch. Really wish I had rooted first, would have been alot easier, alot more resources for root.
Click to expand...
Click to collapse
Menu>Settings>SD & Phone Storage>Factory Reset
let me repeat my question, and get more specific. I need to wipe all data off my phone, everything.
Then I need to get the OS back on it.
Can someone tell me if you can do this without root, I need to completely clear all partitions AFAIK and then get a new CLEAN UNHACKED OS onto my phone.
Factory reset is not enough
RUU is not enough (alone anyway)
I need to get the flashable regions of my phone totally clear of malicious code.
bump for edit for previous
I don't think you have any options without root...only other option without root is boot into bootloader and clear storage.
For curiousity, what did you do that you need to undo and how could you have pushed "malicious code" onto other partitions without root?
unless you work for HTC or know somone that does, i thnk you are pretty boned, even contacting them directly all ive gotten is the usual "it cant be done" line so ....just wait for the hboot to get hacked and do it then i suppose..
What Android version are you on and your phone is currently rooted correct?
He stated in original post that it is NOT rooted.
4.24 gb EVO
hacked as hell
i think it was rooted before not to my knowledge, and flashed. also calendar exploited via google, I hope i can get some help outside the dev forum, because I i know they dont like questions there, thats why im posting here instead.
cant clean it now that i have OTA'd to GB.
I am finding alot of cool app engines along my trials and tribulations. makes me wish I had not stopped working in security several years back.
Someone gonna give a guy a hand? I am as trustworthy as they come if you are worried about anything getting out and about.
If it was rooted before, go into the bootloader and check if it says S-ON or S-OFF. If it's S-OFF, you can flash a recovery and now you're rooted again.
If it's S-ON, no, you can't do anything right now.
yeah im screwed
i just love it when my camera and speaker come on and monitor me all day and night long.
Thariz said:
yeah im screwed
i just love it when my camera and speaker come on and monitor me all day and night long.
Click to expand...
Click to collapse
Sigh...ok...I'll bite. Why do you think your phone is doing this? What evidence?
And does the tin foil mess up your hair?
i watch the logs, i see the mic and or cameras come on, i see the filesys filling where I cant go see it because im not root, i see the traffic as it xmits it from local host to local host, i see the traces of the encryption keys and stunnels. This is only one instance.
I hope there is someone around here who has something more to offer than the people outside the dev forums, im getting killed following the rules.
So let me get this straight and my apologizies for sounding confuzed becasue every reply has been all over the place and has been of no real help to you yet..
Your on GB version 4.24 correct? Previously Rooted without you knowing? Your trying to get back too 100% stock as well? I hope I'm following this so far.
1st, the easiest way, download Root Checker from the Market and that will tell you right off the bat if your rooted or not. If thats not possible, enter bootloader as stated before and verify S-Off at top of screen. If so, flash Amon_Ra Recovery (rename to PC36IMG.zip if not already and place on root of SD Card). Enter bootloader and let it scan, apply update and from there you can do what you need to do. If it says S-On but you know your rooted, go to xHausx Auto Root guide, download the Froyo 3.70.651 Stock rom and place on Root of Sd Card named PC36IMG.zip, enter bootloader, let it scan and apply update, that will take you too 100% stock Froyo with hBoot 2.10 and you can apply GB update if desired or root with whatever method of your choice.
Once again, sorry if this is not what you were wanting but its irritating when you get the run around and people talk about tin foil hats and ridiculous stuff...and agreed, very hard to follow rules when most replies are worthless.
Heaterz16 said:
He stated in original post that it is NOT rooted.
Click to expand...
Click to collapse
Read 1 post below yours, only way to figue out how to help is to know the details. Good 2 cents though.
I will give it a go, after I upgraded OTA it made me s-on, so i think im just screwed now.
I tried the ruu to go back but as you know it says too old files etc
i imagine this will do the same but i will try anything once, the guys at sprint gave me the go ahead to do whateever i need to do to try to backrev this thing, and if i brick it they will replace it so im up for ANYTHING PEOPLE
If you were originally s-off, the ota shouldn't have updated hboot. It can't turn you s-on, unless you reverse it yourself first..
Which means you were always s-on, and currently there is no way to assist you.
lets start over. are u S-OFF or S-ON? that will determine what ur options are.
Thariz said:
I will give it a go, after I upgraded OTA it made me s-on, so i think im just screwed now.
I tried the ruu to go back but as you know it says too old files etc
i imagine this will do the same but i will try anything once, the guys at sprint gave me the go ahead to do whateever i need to do to try to backrev this thing, and if i brick it they will replace it so im up for ANYTHING PEOPLE
Click to expand...
Click to collapse
There isn't anything that can be done for you at the moment. You said your s-on which means your not rooted which in turn means your bootloader is locked and you can't install a recovery and install the files you need to fix your problem. So I would call Sprint and tell em your device is being defective.
pnewgaard said:
Read 1 post below yours, only way to figue out how to help is to know the details. Good 2 cents though.
Click to expand...
Click to collapse
If you could read his original post, he said - it is currently not rooted - who cares if it was rooted before or not. He has S-ON = NOT rooted = he is out of luck...
That's my 3 cents
Any of you super smart devs tell me if the new update from Sprint broke the new root methods?
I applied it like an idiot, it doesn't fix hardly anything that's wrong. I've given up on Sprint. I want to head off to Cyanogenmod land, but am worried it might be broken now.
Thanks!!!
mmark27 said:
Any of you super smart devs tell me if the new update from Sprint broke the new root methods?
I applied it like an idiot, it doesn't fix hardly anything that's wrong. I've given up on Sprint. I want to head off to Cyanogenmod land, but am worried it might be broken now.
Thanks!!!
Click to expand...
Click to collapse
Did it change your H Boot Version?
mmark27 said:
Any of you super smart devs tell me if the new update from Sprint broke the new root methods?
I applied it like an idiot, it doesn't fix hardly anything that's wrong. I've given up on Sprint. I want to head off to Cyanogenmod land, but am worried it might be broken now.
Thanks!!!
Click to expand...
Click to collapse
honestly, why did you do that??i just looked at androidcentral.com and the update doesnt fix anything special..anyway im sure a dev will have a rooted version soon..and just like he said, did it change the hboot?
You should always assume that an OTA update will break root (since it will not have Superuser installed) and that it may NAND Lock your phone (take away your S-OFF). If you want the update just wait around for a short time and a rooted version will appear here.
Well, try using an app that requires root permissions to see if it broke it, like titanium backup.
bpc4209 said:
Did it change your H Boot Version?
Click to expand...
Click to collapse
Hboot version is 2.16.0001
It was not clear from your OP if you had already rooted and then took the OTA or you wanted to know if you could still root your phone.
That is the same Hboot as the previous OTA so you may still be able to root with Revolution if you have not already. If you did already root your phone you need to check to see if you still have S-OFF and a recovery that you can use to get CM loaded.
Boot to recovery (hold Vol - and Power button)
What version of HBoot is it?
Cardinal Rule:
Once rooted, never bother accessing the OTA section of your Sense ROM.
Sorry, I have never rooted and am a complete rooting noob.
[my reason is that I've had blown speakers, cracked screens, etc. and have had 5 different replacements from Sprint and don't want to void my warranty unless I can get it back to make it appear as though I've never rooted]
I did find that this Hboot version still seems to be supported with the new root methods. I have one real quick question, and I have a hard time sifting through the posts, threads, forums.
I want to root, flash a new ROM and want to be able to recover my stock Sprint ROM in case I need to send my phone back for the aforementioned issues. If I follow the root procedures and install Amon_RA's backup and backup the current ROM, I should be able to flash that ROM and get back to S-ON? or would I have to go through some procedure to get back S-ON?
Again, my apologies for posting what's been posted probably 1000 times, you can just link me to a thread....I haven't been successful in my searches for a definitive answer. And the "noob guide" sticky on the forum hasn't been updated to the new root methods, so I'm not sure what will brick me and what is usable.
yes, I will never OTA update after rooting, but in case I want to get back to a stock ROM from Sprint for warranty trade in purposes.
follow up noob question to rooting, all the proper radios and account information will be imported into my phone after flashing a new ROM? Or will I have to know specific radios, PRLs or basebands after I root. It's my primary device so I can't afford to be without.
Damn. Just rooted a few days ago under the assumption Sprint has moved on as far as supporting the EVO.... Dig root but I hope this doesn't create a problem when the update is forced on me.
You can always turn off auto update, and you can also hit cancel if the auto updater pops up. You do not Have to ever update your phone if you dont want to
And if you do decide that you want the update you can wait for a rooted version to appear on XDA and flash that.
m20120 said:
And if you do decide that you want the update you can wait for a rooted version to appear on XDA and flash that.
Click to expand...
Click to collapse
*noob alert* Those normally appear in the Development forum, correct? Is there a particular title I should be looking for?
No offense, and I really mean that, but you should not root your phone if you are that worried about the consequences. If you aren't willing to accept that Sprint may be able to tell you rooted you phone then deny you warranty repairs just stick with what you have. Once you get past that point then its time to have some rooting fun.
Seriously though, everyone is going to tell you how great root is, but I bet 60% or better never actually do anything with their phone that would have required root to being with!
But to get back to a factory state, all I'd need to do is flash a Sprint RUU and turn S-ON. I'd assume that's pretty straight forward, I was just curious if anyone here knew the best instructions that were easy to follow.
mmark27 said:
But to get back to a factory state, all I'd need to do is flash a Sprint RUU and turn S-ON. I'd assume that's pretty straight forward, I was just curious if anyone here knew the best instructions that were easy to follow.
Click to expand...
Click to collapse
Using older root methods (pre-Gingerbread), yes. But the new root method for GB/Hboot 2.16 installs a new, non-official hboot - 6.16. No one has been able to get the s-on tool to work or downgrade to a different hboot. You can flash an RUU that will take you back to stock, but you cannot gain s-on. Whether or not Sprint cares about the s-off 6.16 hboot, I don't know. Sprint is supposed to service rooted phones as long as the firmware is stock. If it's not, they'll RUU for you. You may have problems or you may not, kind of depends on who you deal with.
The revolutionary root method is still in a beta phase, what I believe they call a "developer preview" or something. Perhaps once it's released officially there will be an easy way to gain s-on.
I think that if you are worried about rooting or don't know why you would be rooting ("it seems cool" is not a legitimate reason) then you shouldn't do it. But that's just my opinion.
Sent from my PC36100 using Tapatalk
my reason is that I'm sick of Sprint/HTC's flaky software that breaks things like wireless-n, my ability to stream music/contacts with my car stereo over bluetooth, icons constantly disappearing after reboot, Sense rebooting itself, etc. I don't care about its "cool" factor, I want control - its android, right? otherwise I'd just go get an ibone.
Thank you for that update on the 6.16 Hboot change and S-off/on status, its very helpful. Any thoughts on my question of new ROMs will know how to contact the Sprint network with all my information properly, or do I have to do something fancy to that.
I don't know...last month I couldn't root 2 or 3 weeks ago root pops up for GB 2.3.3 I rooted my phone and to tell you the truth I ain't gonna lie I'm still a noob when it comes to rooting...but I think once you try it yo ass ain't never goin back lol cuz I've been on CM7 this whole time and I'm blown away I'm gonna try out vaelpak RC2 tonight when I get home there's just so much you can do...but that's jus my opinion
Spectacles, Testicles, Wallet & Watch, evO²·³·³
does anyone know what sense version this update is or is it still the crappy sense 1.0
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
I'm actually pretty frustrated right now. This is not my first time messing with an Android phone. I've had several in the past, have dabbled in installing various custom roms, etc., but the guides for this phone seem to universally suck. I have a developer edition Note 4 that I rooted and unlocked the bootloader when I first got it. I bought the developer edition because I knew the bootloader could be unlocked easily, which I thought was supposed to make installing ROMs easier and less hacky. Now, It's been stuck on KitKat 4.4.4 for over a year and a half, and I wanted to update it to 6.0, but it seems like a massive pain in the ass. What gives? I'll link to all the guides I've followed thus far.
First, I found this: http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This is all I wanted to do. This guide told me to upgrade and (re?) unlock the bootloader via this guide:
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
This guide, for whatever the reason, tells me that even if I have a DE, I should install this other ROM for some inexplicable reason, then re-unlock the bootloader. Okay then. That points me to ANOTHER GUIDE:
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
And this guide tells me I have to root to unlock the bootloader (a reasonable assumption) but doesn't tell me how. I don't know how I did it the first time dude, it's been over a year and a half! So, with some searching I found this freaking 40 step guide:
http://forum.xda-developers.com/not...ide-how-to-root-verizon-galaxy-t3454593/page2
Now, not only is this guide stupidly long, its 'helpful' link to all of the software needed is broken. So I searched for the crap myself. I tried KingRoot, which rooted at first, but had other issues. I switched to Kingo Root, which seems to have worked better. I was able to get the n4-fix file to /data/local/tmp, change the permissions to be able to execute it, and run it. It seemed like I was finally making some progress. Except, when the phone restarted, it got stuck in a boot loop at the Verizon logo screen.
I don't know where to go from here, but I am really at my wit's end on this one. I've been working on this for 2 days. And before anyone asks, yes, I backed up my aboot, and I also have backups using TWRP from when I first got the phone and from its most recent state before I changed anything. Though, I don't know how to restore aboot, so if that's a problem, I'm pretty screwed.
Help would be greatly appreciated, before I throw my phone against a wall and buy a new one. I like this phone. But it really started to get bogged down and stop working right, so I thought it was time for an Android upgrade.
---------------------
I got it working, after hours. There were a couple things at play here, chief among them is the fact you have to remove the SD card from the device after attempting to unlock the bootloader, because it causes a boot loop. I also had to do a factory reset after flashing even in some cases where it wasn't specifically stated. Pretty frustrating. Anyhow, hopefully I don't have to ever go through this again any time soon. I made it to 6.0.1.