So i got the update yesterday morning, i was rooted, but wasent thinking when i did it, nothing happened tho, it dident change from C to M, and i dident get a bootloop or anything, i dnt have twrp, and i am now back to being unrooted, so my question is, how can i get the update to happen again, do i just wait for it to show up again, or is there a non difficult way to make it happen,.. Thanks
Related
Hello,
My Gnex was in a bootloop 1 week after purchasing it, (I was running ICS then) now I have JB, after wiping all my data, I decided I should root it, (stock ROM) and unlock it, so I could make Nandroids, now once again, it got in a bootloop, I know how to relock it, but I can`t unroot it for some reason( I am using WugfreshDkit).
My problem is now, my computer crashed with the back up I made before installing Custom blue Softkeys, I need to send it back to the service center, and I am afraid I will get the response ""This is your own mistake for tampering with your phone"" I already backed everything up, and I am able to Lock the device, but it still has root, Will they mind this? does anyone have experience with this? and does anyone know for a fix for the softkeys?
I know it has one hardware defect,( Connecting the chargedock to the Motherboard) and the bootloops...
Also, If I get a new phone, is it save to just Unlock & Root it and use my Nandroid backups on it? or does this give a chance that it will get bootloops again?
I know Sprint and Verizon make a big deal about this, and even charge people for it... Will samsung do this too?
Already got it, Also after Wiping I got updates to 4.2.1
Hey guys, I've been using this site for a while (Thanks for all the info...seriously), but I've never actually posted a problem till now.
I needed to take my phone back to sprint for reasons so I wanted to unroot and reset flash count. Looked online for anything new (honestly not going with my normal methods ****ed me).
mdf_w_count_reset.zip
Ended up there, one file, from a youtube link I can't post, opened it, resets flash count, recovery and stock rom. Sounds cool right?! Would be if those meddling kids and their stupid dog didn't get in the way....
So it worked like it was supposed to ACCEPT the fact that when I tried to re-root my phone, it says LOL NOPE. Odin says it went through, detects my phone properly, says it succeeded, but I go to recovery and it's stock, flash count rises by one. should have done this before my flash count went past one but I didn't and we are here now.
Honestly I need to just reset my flash at this point, stock rom I can live with for a while till I get something else figured out but, hey, not gonna turn down any options.
Thanks!
Sup, so in my last post I was told to read some info, get a better idea of what to do and how to move forward.. Problem being is, Where do I start? There is no actual help for the situation I am stuck in.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe.
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off.
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along.
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again.
P.S in work, Will reply when possible.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe. As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop. Golden rule - Never Never Never take an OTA when running a custom recovery.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off. Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place??
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along. Samsung are completely different. I know as I've rooted my GF's and it was painful
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again No OTA's are safe to use with a custom recovery.
There are a couple of things I'm not sure on, I think you have done the following so far
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Is that correct?
Can you get into TWRP recovery?
Also you have a thread about this open already. Either delete that thread or this one.
As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2 - Nope, Upon taking out the box on day 1, there was an update required and did it straight away.. then a smaller one. Guessing thats 4.4.3 and 4.4.4.
Golden rule - Never Never Never take an OTA when running a custom recovery - hahah, Ive established this now >.< I originally saw rooting as a "inject" sort of methodology.. before the os booted.. Thats not the case!
Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place?? - I rooted following "TheUnlockr" video guide, It did say S-OFF, Bootloop and **** up with the OTA removed this I think. This was using the Hasoon2000 AIO tool.
Samsung are completely different. I know as I've rooted my GF's and it was painful - Good to know, I wont take too much advice from him, he did highlight a tool called Odin. Would that be any benefit to myself?
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Basically.. yes.
Yes I can get into TWRP, but as I say, when I boot to system, this is where the loop starts.. phone starts up normally.. gives me 1min before restarting over and over.
I am sorry, Im aware that another topic is open. I did try to close it, dont have permissions on account. havent used forums in a few years and its all over the shop now hahaha.
Sorry for late reply.. hectic couple of days.
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr
Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk
Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store
Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!
ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!
ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.
+1
its better its included on CM based ROMs also
Hi guys! I'm hoping someone can help me with my problem.
I was trying to update my p6 to Kitkat, but I needed to downgrade first so I flashed it with cmd, however I got distracted by my sister and flashed the boot.img instead, so now my phone was stuck at bootloop. What I did is I forced upgrade to Kitkat, which was a total stupidity. Because of that, the whole SystemUi Stopped working and I couldn't do anything with my phone. I tried to hard reset, delete data/cache, did that over and over until my P6 couldn't read any firmwares at all anymore...
Someone told me that as long as my phone can boot, there's still hope for repair. But I don't know what to do. Please if there's anybody who can help me.
I am willing to try helping but gonna need some exact steps of what you did.