Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
The phone with the red triangle is what you are supposed to see. When you see that, you need to hit Vol-Up + Vol-Down and Power and it will take you into recovery. With that, you should be able to do the OTA to 4.4.3. I'm not sure if you need to flash the 4.4.2 firmware first or not. You can give it a try. If it fails then go ahead and flash back to the 4.4.2 firmware from Tigerstown's thread and try it again.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
SCrosler has posted a stock rooted 4.4.3 ROM. If you flash that you will all up to date (or you could flash Viper 2.4 or NuSense 2.0) essentially flashing any 4.4.3 ROM will get you where you want to be.
Here is the link to the stock, rooted ROM: http://forum.xda-developers.com/ver...m-stock-rooted-vzw-ota-2-21-605-2-wp-t2874699. With your updated firmware and that ROM you will be stock, and up to date on 4.4.3
@BladeRunner & @jsaxon2, thank you very much for your replies and the help. Looks like this was covered to some degree, and has answered my questions.
Going to try dirty-flashing the ODEX rom. I want to flash Viper pretty badly, but don't want to have to wipe everything right now. When Android L comes out, that will be fully worth starting from scratch. I have just enough patience to wait.
Will confirm shortly that everything has worked.
FYI, dirty flash of the ODEX (just wiped cache/dalvik, left data alone) worked perfectly. Software is now reading 4.4.3. Thanks to @scrosler for the stock ROM!
Related
I have a new tf300t with Android 4.1.1 on it and I have followed an older guide to unlock the device and it said to put clockworkmod on it and the Cyanogenmod forums indicate a problem with that, so I went TWRP instead. The twrp site said to pick the right version (-jb) and I did that.
I put 2.6.latest of twrp on and did a backup. Everything is going great. I rooted the device with SuperSU, Copied over CM 10.2.nightly and the right gapps version and it flashed fine. I booted in and I let it go for awhile and it just bootlooped. I went back into twrp and reflashed to ensure that wasn't an issue (same problem) and restored and I'm back to the beginning. I decided to try the 10.1 version on Cyanogen's site and had the same issue. I'm thinking it's the bootloader version doesn't match -- needs to be 4.2, but I want to be careful not to brick the device since a lot of people have done that.
Any guidance or pointing me at a thread would be appreciated. I have a feeling that letting the OTA update take place on the device kind of ropes me into a corner I might not want to be in. I'd really like to be on the latest Android OS *assuming* most of the tf300t features work. I can handle some odd things not working quite right.
Thanks,
Rich
Step1
It appears that my semi-direct path is to get to the newest [MINUS 1] version of 4.2.1 from Asus.
TF300T-US_epad-10_6_1_27_1-UpdateLauncher.zip
Many newer ROMS require this boot loader, and many people say to stick with the twrp 2.5.0.0 because 2.6.x.x is buggy. I can confirm that 2.6.x.x (latest), the mount feature does appear to be broken.
My only concern now is timing. Upgrade to 2.5.0.0 first, or upgrade using fastboot to the new Asus rom. It might not matter and I might need to put TRWP back on after the flash anyhow.
Also, I did root my current OS before doing this update, so it will be interesting to see if that remains intact.
Rich
Step3
I used fastboot to update and I thought I could apply the TWRP 2.5.0.0 update right after it, but it wouldn't take it. I was a little worried that I borked it. It booted and went into the OS and updated a bunch of things. I noticed my SuperSU was no longer root even though it was going to try and survive the update.
Also: I switched to the 4.2 Launcher... not sure I want my tablet to run just like my phone. I might switch back.
I'm still going to try and get to a CM 10.2 rom, it might not be an official rom though.
Rich
Step 4
I decided to see where things were at with a fully tweaked 4.2.1 rom before the 4.3 rom and picked
[ROM]★●[TF300T/G/L/201/301][CROMi-X 5.0.2][ODEX/DEODEX 10.6.1.27.1][SEP 8]●★
This looks very well done/well polished and has lots of people testing it. Will update as I head to 4.3.
Hello Everyone,
New member, longtime lurker here. I have a I535 Verizon GS3, and am rooted. It has been quite a while since I did that, and I just wanted to make sure I knew what I was getting into before I tried to upgrade to a newer rom. The reason I want to upgrade is I currently have a Sony Smartwatch 2, that I love but I shattered the screen. In preparation to buy one of the new Android wearables, I need to be on a newer version of android as far as I can see.
Right now I am on: 4.1.2/ Baseband version, I535VRBMB1/ Kernel Version 3.031-86103/Build number JZO54K.I535VRBMB1
I am not sure what of that info is important so I posted it all. I don't remember the exact name of the rom I flashed before, but I think it was created by member Dalep, and it was something like "Stock Rooted". It was basically just a rooted version of the stock rom. My only reason for rooting was to use a wifi tethering app which has been working well for me. I was nervous with the initial rooting and flash process, so once I got what I needed I stopped working on it and used my phone as is until now. Now I would like some guidance on how to get my phone safely up to date.
1. I am running Clockwork Mod Recovery v6.0.2.3. Is this still usable or do I need to update it?
2. What rom would you all recommend for someone who wants a fairly stable phone and does not care so much about tinkering/customizing?
3. What does a nandroid backup do and what can I do with the backup (I did one before I installed this current rom)
4. What is the best way to get my phone back with the apps I have installed? (i.e. reinstall from Playstore, etc) I don't have many apps.
I am sure there will be more questions, but thank you for reading my long first post, I just want to make sure I am clear about my current state, skill level and intentions.
Thanks,
Victor
Update recovery to latest version of whichever recovery you prefer. I use TWRP. Flash the MF1 firmware and ML1 modem in that order. This will bring you as far up to date as possible without locking down the phone. Then you can flash any rom currently available. I run stock deodexed ML1 4.3 base and then mod it the way I want it. Scott has one in the rom threads. As far as nandroid it will make an image of your current setup in case you need to return due to problems or trying some other rom. There are several options for backing up apps such as TIBU, My Backup or even Google can restore your apps. Here is firmware and modem. Flash MF1 first and ML1 second. ML1 will replace the MF1 modem but leave rest of firmware (bootchain) at MF1 level and will retain root and unlock status.
Flash in recovery in order posted:
#1- MF1 Firmware -- http://www.androidfilehost.com/?fid=23329332407591785
#2- ML1 Modem -- http://www.androidfilehost.com/?fid=23329332407591786
Thanks for the response, I will flash those and check out that rom
(HTC One M8 on Verizon. HTC6525LVW.)
Hi everyone.
Got S-OFF Through the Sunshine method a few days ago.
No matter what custom ROM I installed I wasn't able to boot -- even messing with custom after flashing the lollipop firmware (this thread: ) I finally got my first custom ROM to actually boot last night (ARHD 40.3), only to find the roaming icon in the status bar, with no data after I turned off roaming.
I was worried that, according to one warning elsewhere, I may have corrupted my "NV partition," and that was causing the data problems. However, a quick NANDROID restore of my previous working stock ROM (w/root) booted with full cell service no problem. So that indicates that I don't have a corrupted NV partition.
Am I missing something simple within the ROM? I've rebooted a few times, the SIM gets recognized and I have my correct phone number, and I've tried the typical 2G/3G/4G auto options/selections in the mobile data settings...to no avail.
----
As an aside, everytime I exit/reboot with CWM (using cwm_v6.0.4.8_m8vzw-3.img ), it says "You may lose root. Attempt to regain root? (This process is irreversible...) yes/no. I'm wondering if this matters at all? I have root just fine inside my stock ROM, and full S-OFF, so I don't think it matters but I thought I'd ask just to be sure.
Related note: Is TWRP "better"? I did try to FASTBOOT flash recovery of the latest TWRP (twrp-2.8.5.0-m8_wlv.img) for my phone, but that recovery doesn't boot. (I saw an indication yesterday that I might just need to flash this TWRP recovery from inside a ROM or something...but in any case, the recovery seems to be working fine overall.)
----
My apologies that this isn't in the right thread(s) -- I haven't a lot of time before I go on a trip next week, and figured I would just post to see who could point me in the right direction.
Thanks in advance for all the help!
Everyone around these forums, myself included, seem to be using twrp and you did describe the current version number. I would first recommend figuring out how to get twrp installed. It's weird that you were unsuccessful getting it flashed with fastboot. To make sure, the device was recognized by "fastboot devices" and you typed "fastboot flash recovery <name_of_file>.img" right? You might also try finding a copy of the recovery that has been loaded into a 0p6bimg file that can be flashed automatically in the bootloader. I think captain throwback posted one for a user somewhere in this forum a week or two ago.
Did you flash the latest s-off ruu? You need the latest firmware for most of the current roms. That is likely why none of them boot.
...
Up to speed =)
Thanks to the first two posters! I did get TWRP finally installed (seems more capable than cwm), and did flash the firmware prior to posting the thread, but the ROMs still didn't install or work properly.
After flashing the latest RUU, I flashed SkyDragon, which seems to be working well!
Also have learned a lot more about the entire process...
Thanks again!
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
schneid said:
There does seem to be a snag with TWRP and the new 5.0 firmware. Seems like you finally got around it. I was newly S-Off and wanted to go from 4..4.4 to 5.0.
I went this route using the top firmware which has TWRP built in:
http://forum.xda-developers.com/showthread.php?t=2723159
Another issue is it must be flashed twice. For me it took three times. I also flashed the new radio although it may have already been in the firmware. The dev that posted the above also wrote your ROM so found a good match.
Click to expand...
Click to collapse
What version of twrp did you flash? I haven't had any issues flashing ROM's. Some of them do take a long time to boot at first.
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings
Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?