Related
Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
volk9029 said:
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
Click to expand...
Click to collapse
Edit. You also did not mention what version of recovery you use. Did you try to downgrade to different version?
Sent from my lair.
Yes I tried using the volume buttons and they didn't work. The only thing that functions is the power button, but that locks TWRP, which is no use. For the versions, I tried the newest 2.4.0.0 and 2.1.8 and both had the same problem.
One thing to note also: I received the phone yesterday and while I was contemplating about rooting or not, I decided to update since it was still back at 4.0.4 ICS. Apparently, there was an update for the phone literally today, which I may have received since I'm not seeing the version of the RUU uploaded anywhere. My software version is 3.16.651.3 710RD.
Also, I'm on HBOOT 2.09 if that helps at all.
U flashed the new firmwear zip?
Sent from my EVO using Tapatalk 2
If you mean installed the new firmware via OTA, yes. After updating everything OTA, I started the rooting process.
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Wolosyks said:
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Click to expand...
Click to collapse
And THIS is why we recommend S-OFF to people, and tell people NEVER to take OTAs. At this point, I think you're stuck, unfortunately. You won't be able to access TWRP until someone figures out what the new touch panel image broke. You'll be able to use your ROM fine, but it seems this was something that was done intentionally by HTC to prevent custom firmware (or even software) from working properly.
I could be way off base, though, I guess . . . .
Inconceivable! HTC just pledged to continue supporting developers....wait they don't really support developers
Root
mr_krunchi said:
Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Click to expand...
Click to collapse
Sorta the same problem, i dont flash roms but i like having my phone rooted. I had to redo the whole process because i lost my root access and i heard they were doing an update, so i did the 3.15 ruu and went back to complete stock, did the 3.16 update, unlocked the phone and it worked great up until i installed twrp 2.4.0.0, same problem touch screen not working. So i figured i would just run the 3.15 ruu again and just keep it there, unfortunately, the 3.16 version hboot which is 2.09 as well, will not let the 3.15 ruu run, says incompatible hboot, but it just restarts the phone, it did overwrite twrp somehow during the process of trying 3.15 the second time and removed it from the phone. From talking to some people, just have to wait until someone figures out how to fix that to get back up and running. I am pretty new to root but i like having those options to screw with the phone. Anxiously awaiting a fix though. Need to flash some roms soon, but never could get them to work, worked great on my Evo 4g...just not having the same luck with 4G LTE.
Same issue here
I never rooted my phone before and kept it updated up to the most recent 3.16.651.3 and it used to say "Locked" under Bootloader. I followed the instructions to the T from http://forum.xda-developers.com/showthread.php?t=2026938 with 2.09 Hboot files etc. All this and the problem I had is that when I got to the step where you load up TWRP, the touch screen didn't respond, nor did the volume rocker allow selection. Single pressing the power button, for some reason, showed "Slide to unlock" but I couldn't slide/unlock. Holding power still rebooted the phone.
Relocked and reloaded the original stock ROM, followed the procedure again, and it worked perfectly.
yeah I just got my phone back from RMA today ( parts of the screen were non responsive loose pin or something). when I sent it off I relocked it and Re S-ONed ( on H boot 1.19)it. as I read some places where they wont fix any hardware if the software has been S-OFFed.
when it came back it had the 3.16 stock firmware(Hboot 2.09) and now I cant S-OFF it ( dirty racoon gives errors about 3.16) cant downgrade it ( 3.15 RUU wont load) cant get roms on it( clockwork cant mount SD cards, and TWRP wont respond to touch)
needless to say I'm rather upset with HTC right now
Agreed
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
tonyevo52 said:
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
Click to expand...
Click to collapse
It's conceivably possible to change the main version on the /misc partition to match the previous OTA version (3.15.651.13), and then you should be able to flash the 3.15 RUU/PJ75IMG, since the HBOOT version didn't change.
But I'm S-OFF, so I don't have to worry about testing that theory.
I wish i was S-Off, i was rooted under 3.15 and everything was good, like a dumbass i updated my prl a couple weeks ago and totally forgot it would cause me to lose root, so i just never rerooted due to time, so when i saw the new 3.16 was out i figured i would relock, update, unlock and install twrp, worked good up to the twrp part where it would not respond to touch, and i tried to go back to the 3.15 ruu but wont let me. At least the phone still works, but a regular phone at this point and i just started rooting at the beginning of January so im still learing alot, actually don't mind screwing it up and learning from my mistakes, but my saving grace was always that i would go back to 3.15 if needed, not anymore, so now i will wait until someone figures it out, in the meantime though, learning alot more by reading on here. The only problem i seem to find is i understand most of the language here, but sometimes i see people trying to help people with step by step instructions and they miss a step or they explain it way technical and it puts people into panic mode, my eyes have glazed over a couple wonder what people are saying to do...but totally worth it and appreciate the help definitely.
Tony, updating your prl shouldn't take away your root.
Taking the ota could.
Sent from my EVO using xda app-developers app
I didn't even think about it taking away the root, but i lost root the same day i updated the prl a couple weeks ago. Never accepted any ota's while the phone was rooted, i just want root back...still learning though, fun messing with it!
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Captain_Throwback said:
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Click to expand...
Click to collapse
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
sdax2 said:
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
Click to expand...
Click to collapse
I don't know where you're looking, but this link is right there on the page:
http://techerrata.com/browse/twrp2/jewel
You seem to be looking at an EVO 3D version?
Captain_Throwback said:
I don't know where you're looking, but this link is right there on the page:
You seem to be looking at an EVO 3D version?
Click to expand...
Click to collapse
Victim of browsing because I've downloaded so many times before...
But in the "Download - Fastboot Method:" section there is a link that points to the drivers needed from HTC. Without reading carefully I just clicked on the link labeled HERE.
It does however point to an incorrect page for the HTC drivers. Sorry for the confusion, and thanks for the clarification Captain...
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...
hello everyone ! i just recently updated my firmware from 1.58.401.5 to 3.28.401.9
my question = is it o.k. to flash older ROMs. (actually one based off 1.54.401.5).
am new to htc and flashing guidelines. coming from samsung S3 for past 2 yrs.
p.s. also am unlocked , s-off , superCID .
thanks for any help/advice.
"all I can really do, is stay out of my own way and let the will of heaven be done"
First off are you on an att device? Secondly not best solution as a firmware choice for the us variant of the m8. I would suggest flashing the us developer edition 3.28.1540.5 firmware and not a euro based one. I would also suggest using a based rom for us variant,many have had issues with connectivity using euro roms on att network. If not on att network outcome may be different. I dont know if flashing an older rom will have any impact with the newer firmware or not,many have had issue with mismatched firmware and wifi. Best answer is make a backup of current rom and try it.
mrrocketdog said:
hello everyone ! i just recently updated my firmware from 1.58.401.5 to 3.28.401.9
my question = is it o.k. to flash older ROMs. (actually one based off 1.54.401.5).
am new to htc and flashing guidelines. coming from samsung S3 for past 2 yrs.
p.s. also am unlocked , s-off , superCID .
thanks for any help/advice.
"all I can really do, is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
mrrocketdog: Don't just thank the man, answer his question! And update us on what you are going to try, etc.
mrrocketdog said:
my question = is it o.k. to flash older ROMs. (actually one based off 1.54.401.5).
Click to expand...
Click to collapse
Why would you want to do this? In addition to added features, there are important security updates. Reverting to software that is several generations old is generally not a great idea.
Although I also realize that there is the rare exception where someone misses a feature of an older ROM, or has a bug on the newer ROMs that they want to try to fix by reverting.
@Wonders_Never_Cease and @redpoint73 ; sorry for late reply. have been having 'issues' to say the least.
#1. yes am on att.
#2. had no idea was euro based firmware and rom. (brand new to htc/sense and still trying to get the numbering system. am coming from att samsung S3 for past two yrs.)
#3. tried to 're-update' firmware with 2.22.1540.4 (which i thought was 4.4.3) which went well. phone rebooted back to euro ROM. then proceeded to update to 3.28.1540.5 (4.4.4) and when phone finished updating i pressed power to reboot and screen went white with htc logo and stuck. many many button presses/combos later (REALLY not knowing my device well enough) i can get to a) white screen with htc logo
b) bootloader screen (and here is where i think i really messed up , because instead of power off or fastboot or reboot ; i got in hurry and hit factory reset !).
c) have twice gotten to black screen with red triangle , exclamation mark in middle.
definitely not a good sign.
my only computer access is an old mac POS laptop (nothing against mac's ; just this one !) have re-activated my old S3 , which is what i'm typing on , and was thinking (?) should i download the original 1.58.502.1 factory everything , put it on root of extSD rename to 0p6bimg.zip and see if it will update. or try Wonders_Never_Cease's update file. (was stuck in a loop cause phone wouldnt reboot fully and each time i went back to bootloader it immediately detected new firmware zip and do its thing.). took ext.SD card out , put in old phone and deleted via es fileexplorer.
reason for older ROM was it looked to be 'lighter'. i dont care for bloatware , which was the original motivation for climbing mt.odin and receiving the blessing of root in the first place!
sorry for long post , just trying to give all info. (that i can remeber-will take freakin notes from now on). to possibly get informed advice/direction.
thank you for your time in reading this and any help you could pass along.
:banghead:
"all i can really do , is stay out of my own way and let the will of heaven be done"
more info coming. brb.
unlocked - superCID - s-off - HBoot=3.19.0.xxxxx - radio=1.21.21331147A1.19_2G - os=3.28.401.9
again , any advice/thread links/options are very appreciated.
NOT sent from my atthtcm8 lol.
"all i can really do , is stay out of my own way and let the will of heaven be done"
anyone ?
"all i can really do , is stay out of my own way and let the will of heaven be done"
You want the lowest bloat free rom,download 3.28.1540.5 ruu and run it in fastbootusb mode...then youll have updatea from htx and not any carrier.
mrrocketdog said:
anyone ?
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Wonders_Never_Cease said:
You want the lowest bloat free rom,download 3.28.1540.5 ruu and run it in fastbootusb mode...then youll have updatea from htx and not any carrier.
Click to expand...
Click to collapse
ok. thank you for that. will do and i'll cross fingers that it takes.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
[MENTION=5345690]then proceeded to update to 3.28.1540.5 (4.4.4) and when phone finished updating i pressed power to reboot and screen went white with htc logo and stuck. many many button presses/combos later (REALLY not knowing my device well enough) i can get to a) white screen with htc logo
b) bootloader screen (and here is where i think i really messed up , because instead of power off or fastboot or reboot ; i got in hurry and hit factory reset !).
c) have twice gotten to black screen with red triangle , exclamation mark in middle.
definitely not a good sign.
Click to expand...
Click to collapse
If you updated the firmware by WNC's thread (link below), you didn't follow the instructions. Red triangle is stock recovery, which flashing firmware will install (removing custom recovery). The instructions clearly state how to return to TWRP recovery:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
mrrocketdog said:
reason for older ROM was it looked to be 'lighter'. i dont care for bloatware
Click to expand...
Click to collapse
Amount of bloatware isn't a function of how old a ROM is. Its more a function of the carrier/region. Any bloatware can be frozen or removed with root anyway. So its more important to have the security updates and other updates of current OS software; and being on obsolete Android versions is usually not a great idea.
Or just flash WNC's debloated ROM included in the link above. This not only puts you on the most up-to-date and best OS software to run on AT&T, but is already very debloated.
redpoint73 said:
If you updated the firmware by WNC's thread (link below), you didn't follow the instructions. Red triangle is stock recovery, which flashing firmware will install (removing custom recovery). The instructions clearly state how to return to TWRP recovery:
http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Amount of bloatware isn't a function of how old a ROM is. Its more a function of the carrier/region. Any bloatware can be frozen or removed with root anyway. So its more important to have the security updates and other updates of current OS software; and being on obsolete Android versions is usually not a great idea.
Or just flash WNC's debloated ROM included in the link above. This not only puts you on the most up-to-date and best OS software to run on AT&T, but is already very debloated.
Click to expand...
Click to collapse
thank you for info/reply. will be at a 'real' computer this evening and follow your recommendations. apologies for not researching more , but grateful for help. after this will be more thorough in research. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
No need for apologies....:0P
Yahoo !!!!! Resolved
finally am back up and running. pure luck/grace/direction-from-knowledgeable-people. not sure what i did but am on
os-3.11.1700.5 , which i think is a GPE. how i ask ? not sure. i tried so many DLs changing them to 0P6BIMG.zip and running them thru HBOOT that i couldnt tell you or me. not what i was looking for, but at least am back in working order. will read up on changing from GPE (if thats what this is) to recommended ROM of redppoint73.
would very much like to thank those who helped me out : @xunholyx , @Wonders_Never_Cease , @redpoint73 , @serio22 , @aircooledbusses , and @DocHoliday77 (wherever you may be i hope you and yours are staying well).
"thank you" dosent seem enough but maybe me being more thorough in reading and NOT getting my butt in a sling will help.
ROFLMAO with joy. thank you mr./mrs.XDA for a helpful community.
stay well
mrrocketdog
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
I have this canadian version of Huawei honor 5x, and I've been scouring to find answers to whether if am i able to flash a custom rom such as cyanogenmod or not. Can anyone please help me out with this; I've already made several post and it get unanswered. Sofar I've managed to unlock the bootloader, flashed twrp, and rooted it. When I tried installing CM 13 from a thread on this site, I always get the "error 7" and I tried deleting the 2nd line in the meta-inf and rezipping the rom and reflashing; results remain the same.
Here's more info on my phone:
Build#: KII-L05C654B330
EMUI 4.0
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Hai bud , he mentioned that he is on emui 4 . So we have necessary proof that he is on marshmallow which we require to flash a rom on 5x:highfive:
And after thinking for a while , the last version (latest updates) have modem issues so custom roms may have stopped working for u due to this. I have solutions for u .
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Goldenmeadow said:
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Click to expand...
Click to collapse
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Thanks for reply! With the help of fellow members I figured it out - I was holding POWER button TOO LONG And if that happens, phone goes into built in recovery... You suppose to let button go once you see first splash screen.
So it's all good!
Thanks!!!
Chaos Storm said:
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Click to expand...
Click to collapse
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
kenneth_82614 said:
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
Click to expand...
Click to collapse
I will have a look. As things would be, I also need to restore my GR5 so I'll find it for both of us.