Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.
Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?
Related
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly
Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
WhiteRabbit44 said:
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
Click to expand...
Click to collapse
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Extra Info:
With Odin, I have made sure Kies is uninstalled. I've also tried multiple USB cables, including the ones the phone came with, and I've tried almost every USB port on my computer. Whenever Odin fails, it's in the exact same spot every time, which makes me think it's a software issue, not a hardware issue.
EDIT:
I was actually able to get the stock.vzw-root66 ROM installed by Odin without any errors. The phone rebooted immediately, then showed the android robot with the blue spinny thing in his chest, then the phone went back to the same Verizon error message.
BadUsername said:
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
WhiteRabbit44 said:
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
Click to expand...
Click to collapse
TW 4.3 discussion thread has most info consolidated in one place:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Cowboyup65 said:
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Click to expand...
Click to collapse
Ok, I fixed it through my engineering problem solving.
Since I could not boot the phone past the spark screen and I had only zip files to load on the phone, I had to pull my sd card, load it into my laptop, transfer a couple of file of stock roms http://cnexus.co/downloads/getdownload.php?file=SM-G900P/NE5/NE5_ROOTED_ODEXED.zip
this one being the one I used.
Then I was able to boot into Philz recovery, flash the zip file and get my phone back.
Of course the last couple weeks of tweaks and changes were gone and all the bloatware came back in a hurry, but I deleted it as expected.
Just updating this in case someone else runs into the same problem in the future.
Bummer Odin doesn't push .zip files, would have made it a little easier, but through mistakes and failure we learn and tonight I learned a few things about my phone, cool!.
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
It's been a long night and I'm at a complete loss as to what to look for next...
Around 9PM last night, my phone randomly rebooted... it's done this a few times before, and i thought nothing of it. When it finally booted back up, I was at the "choose your language" setup screen. WTF.
I lost literally EVERYTHING.
FYI, this was on stock rom, and I didn't even have the OTA(s) because I was rooted and was content with 4.4.2
Well, since all my data was gone, I figured it was about time to see what I could get with a custom ROM. The phone's been sluggish lately, so I figured a bloat-less upgrade would help.
Long story short, I loaded the 5.1 firmwares for VZW, and the HBOOT as well, and flashed GPE_5.1 on it. It took it like a champ, but refused to boot. I tried changing the kernels during the GPE install, but none of them worked. Some would loop, some would kick me into recovery, and one would just stall and the animation would run forever. No worries, I'm sure I can go to a stock 5.x rom! But that's a big NOPE. I just get "installation aborted" with no reasoning or errors in CWM (I had TWRP at one point as well, and it didn't get me anywhere either) Or I get "symlink: some symlinks failed" ... it depends what rom i'm flashing.
I've tried stock and custom, rooted and not... literally nothing will take.
ALSO, in my attempts to remedy the problem, I tried to reflash the firmware, but fastboot starts that there's not enough space. A quick google search pointed to "not enough ram in the PC" which is BS because it's done it on 2 different systems, both with 16GB ram, one running Win8.1 and the other Win7.
To top it all off, somehow I relocked the phone (but i still have S-OFF) and without being able to boot into the OS, I can't unlock it with SunShine/Firewater.
Hopefully, someone can point me in the right direction...
Welp... It's working now...
Not 100% sure what I ended up doing that worked, but I was able to run the unlocker via creating a new unlock_code.bin from htcdev and ran that with the all in one toolkit.
From there, I was able to use the toolkit to flash a stock ruu rom (I flashed the 5.0.1 RUU, but when it booted, I was still in 4.4.2)
It apparently didn't like somwething in the boot order other than the ROM itself.
I'm now running S-OFF, relocked but rooted 5.0.1 after it took several OTAs. Not sure how many more OTA's are pending, but it just keeps prompting me lol...
At this point, I'm just happy it's booting, stock or not. I don't even know what recovery I'm running at this point...
Did you update your recovery??? To the latest one
Sent from my HTC6525LVW using XDA Premium 4 mobile app