I guess I'll say what I did to end up here, first:
A few months back, I bought an unlocked HTC Hero (A626) from eBay. This evening, I decided it'd be a good idea to root the thing and install a nice 2.1 ROM.
2 hours later, I find myself with a locked phone. Or, at least, that's what it seems to be. My SIM is definitely *in* the phone, and it's quite adamant that it doesn't have one.
I *was* following the instructions at theunlockr.com about "rooting the hero in one click" - I downloaded the RUU downgrade for "unbranded European users" (though my phone is now in Canada... it *is* an unbranded European phone).
After some mess with drivers and HTC Sync, I finally got the 1.76 RUU to work (I was on 2.73 before)... until I ended up with error code 140; something about a device error.
Now, from my browsing, I'm fairly certain that I could get around this by making a Goldcard and retrying the downgrade and continuing with the root/upgrade.
What I want to know is: will this fix my phone? (making a goldcard, rooting and continuing with a custom rom, that is) Right now it's on radio 6.35.06.18, but I don't believe that changed since the RUU failed. The RUU seems to have locked the phone, and nothing else; every other piece of my data is still intact. If not, is there any way that I can make it work again?
Thanks very much; any help is appreciated
i seem to remember the 140 error when trying to apply the RUU. making a goldcard got me past it.
strange..from other ppl post on phone sim unlocking, rooting shouldnt affect the sim lock at all
krisrm said:
I guess I'll say what I did to end up here, first:
A few months back, I bought an unlocked HTC Hero (A626) from eBay. This evening, I decided it'd be a good idea to root the thing and install a nice 2.1 ROM.
2 hours later, I find myself with a locked phone. Or, at least, that's what it seems to be. My SIM is definitely *in* the phone, and it's quite adamant that it doesn't have one.
I *was* following the instructions at theunlockr.com about "rooting the hero in one click" - I downloaded the RUU downgrade for "unbranded European users" (though my phone is now in Canada... it *is* an unbranded European phone).
After some mess with drivers and HTC Sync, I finally got the 1.76 RUU to work (I was on 2.73 before)... until I ended up with error code 140; something about a device error.
Now, from my browsing, I'm fairly certain that I could get around this by making a Goldcard and retrying the downgrade and continuing with the root/upgrade.
What I want to know is: will this fix my phone? (making a goldcard, rooting and continuing with a custom rom, that is) Right now it's on radio 6.35.06.18, but I don't believe that changed since the RUU failed. The RUU seems to have locked the phone, and nothing else; every other piece of my data is still intact. If not, is there any way that I can make it work again?
Thanks very much; any help is appreciated
Click to expand...
Click to collapse
I dont see the sim lock being the cause of no network since you started messeing about with it as the sim lock is held on a totally different part of the phone so any ru update wouldnt effect that or the networks would be nackered, have you tried putting thte recovery image on http://android.modaco.com/content/htc-hero-hero-modaco-com/291486/06-jan-installing-the-patched-recovery-image-on-your-device/ and flashing one using that?
This is not a sim-lock issue. sounds like a goldcard is needed, as this is the bootloader lock you are experiencing...
Ok, well, I suppose I'll try the goldcard, then - one more question; once I make the goldcard, can I ever use the SD card normally afterwards? I don't know if I want to use my 8GB Class 6 if it's unusable as storage, after this :/ .
(Also, apologies to the mods for posting in the Development forums - 'tis what happens when one is low on sleep and stressed by phone problems )
EDIT: Ok - from some reading, it sounds like it's best for me to go looking for the 2GB card that came with the phone, as it will "just be a goldcard after this". If anyone wants to confirm this, that would be excellent. Thanks for all the help, by the way
Ok - I decided I'd try out Flashrec instead (I guess I wasn't on 2.73....7, rather 5, which apparently has the exploit needed to make flashrec work), and I flashed Cyanogen's recovery image successfully - I can boot into recovery mode and I get the familiar screen .
I just want to be very clear about this: can I now flash a custom ROM (preferably without bricking my phone )? (I was thinking Villain 4 Beta2, but if anyone else has a better suggestion... I'm looking for a 2.1 ROM with Sense). I'm not really sure I want to flash the "improved" recovery-RA-HERO right now, as I cannot su (I think this is an issue with me not having it on the phone, as I get "permission denied" errors when I try to run it). Would it be a wise idea to flash a custom ROM with su *first*, and then maybe update my recovery image?
Thanks
All right, sorry about that - disregard my above post; I went ahead with the update. I'm now running Villain4beta2 (2.1 is so nice ). However, I still have the "No Sim card in phone" issue, even though I most certainly *do* have a SIM card in the phone. Does anyone have any idea what's happened? Even better, does anyone know how I can fix this? I'd get it unlocked again, but as some of you mentioned, it doesn't really make sense that a ROM update would sim-lock the phone... Also, I have no idea which carrier it would have been locked to (it shouldn't have been locked to a carrier, really... it's a stock white international phone), so wouldn't that make unlocking rather difficult/impossible?
...and disregard *that* post as well. Turns out the Hero is *really* picky with the SIM tray. It has to be locked entirely; you can use your fingernails and swipe to the left if it doesn't work. Anyway, it had nothing to do with SIM locks and everything to do with me being incompetent at putting in the SIM . So, consider this problem SOLVED.
If it is incapable of detecting any inserted sim I imagine that will make unlocking impossible, since aiui to unlock you need to have a sim inserted belonging to a carrier other than the one it is locked to, in order for the phone to prompt you for an unlock code.
Was the sim recognised & working previously? I know you've just rooted it, but I'd be inclined to try flashing with a stock RUU, if you haven't already. Just pick an old one so you can root it afterwards without the hassle of a gold card.
If it doesn't work with a stock ROM I'd suspect a hardware problem, but it is strange if it was working prior to you starting to update flash. There's no way at any stage you attempted to flash a CDMA Hero rom to your GSM Hero (which I assume it is as you said it was European)? It doesn't seem likely, but worth double checking I guess.
Lol. I've done that before. Didn't think to suggest it as I never imagined anyone else could be as incompetent as me Glad you got it sorted.
Heheh, I do believe you've met your match . Thanks, everything is working beautifully now
krisrm said:
...and disregard *that* post as well. Turns out the Hero is *really* picky with the SIM tray. It has to be locked entirely; you can use your fingernails and swipe to the left if it doesn't work. Anyway, it had nothing to do with SIM locks and everything to do with me being incompetent at putting in the SIM . So, consider this problem SOLVED.
Click to expand...
Click to collapse
haha you clown, well at least now you have the rec image and you can flash away till your hearts content!!
Related
Hi,
I bought a Generic HTC Hero from Mobistar in Belgium with the hopes of getting the new update on there. However I've downloaded both updates but it get an ID error when flashing the device. Does anyone have any advice on how i can get this update. Blegium isn't even listed in the HTC World Directory. =(
Thanks,
-David
are you sure you need to update? That is, I suspect the belgian hero is already based on a recent rom. Does the clock flip?
I am in belgium too an I use the Modacom rom with mobistar with no problems. So I suggest you flash this one
Dont know how to get the official rom, but try reversing the last numbers of the SN.
Ya im sure itys the old one, the clock does flip =P.
I tried reversing the last digits of the SN, finnaly got though, lets see if the update works though.
<Noob_Q>How did you flash you Hero with the latest Modaco Rom?</Noob_Q>
davekilljoy said:
Ya im sure itys the old one, the clock does flip =P.
I tried reversing the last digits of the SN, finnaly got though, lets see if the update works though.
<Noob_Q>How did you flash you Hero with the latest Modaco Rom?</Noob_Q>
Click to expand...
Click to collapse
Follow this video for how to root your Hero: Link
DO AN NANDROID BACKUP AFTER THE LAST STEP OF THE FIRST VIDEO. YOU WILL SEE THIS OPTION IN THE RECOVERY SCREEN. Just in case something goes wrong, you can flash back your stock ROM.
This video for the actual flashing of the ROM: Link
They are video guides with written instructions and helped me understand what exactly is going on.
yep, just like above
davekilljoy said:
Ya im sure itys the old one, the clock does flip =P.
I tried reversing the last digits of the SN, finnaly got though, lets see if the update works though.
<Noob_Q>How did you flash you Hero with the latest Modaco Rom?</Noob_Q>
Click to expand...
Click to collapse
Did it work?? I also have one from Mobistar and I'm curious...
Yes Sir. It certainly did work. =D
Thanks guys!
One other Q...how do i now install Apps to my SD card?
davekilljoy said:
Yes Sir. It certainly did work. =D
Thanks guys!
One other Q...how do i now install Apps to my SD card?
Click to expand...
Click to collapse
It isn't working for me :-( Downloaded the update by changing the last 2 digits of my SN. Tried installing it but it gives me a customer-id error, how did you manage to install it?
I'm still having the same problem! Just changed the last number of my S/N from 1 to 0 and downloaded the package.
I'm getting the customer id error [131] as wel!
Isn't there any solution for this problem without having to root my phone?
I ended up rooting the phone and installing the Modaco ROM, very stable and fast rom!
genius
purchased my HTC Hero while on holiday in china, bought from one of those laptop/PC/phone/pirate movie/pirate software mega-malls in chengdu.
its software version was somewhere in the 1.73 range and I really wanted to upgrade but HTC responded "blah blah blah singapore blah blah no ROM available in RUU form for your phone as yet".
every time i tried the RUU exe files downloaded from here or from HTCs UK site, i was greeted with the "Error 131" Customer ID Invalid which I understand from xda-developers site relates to CUID lock being active on the phone (forgive me if it is called something other than a CUID lock)
installed nandroid which was pretty friggin easy
downloaded the "update-hero-generic-2.73.751.4-signed.zip"
copied the file to my SD Card on the phone and renamed to "update.zip"
turned the phone off.
booted up while holding the "home" key
selected "flash using update.zip" or something on the nandroid menu and press home or menu to confirm
once completed, re-booted and was greeted by the standard HTC Android setup prompts including my chinese/english language selection prompt (thank christ) - the china mobile splash was still present but the wierd green logo following it was replaced by the cute android jumping out from behind a HTC logo.
i think the key was that the nandroid installer and the update.zip packages do not respect the S-ON (CUID or whatever) lock that my phone has.
there is a procedure for removing the lock but it is beyond the steps i am willing to take as it involves making an RS232 3.3v usb connector, and sending console commands to the handset. While removing the lock would mean i could flash standard roms from RUU*.exe files, and i could remove the China Mobile splash screen, Nandroid does away with this step as it seems not to respect the S-ON lock that is set.
i LOVE nandroid now. xda-developers kicks ass.
xx
No need to use that method to bypass cid lock. Check the stickied thread on making a goldcard. Does similar thing, but without the risks from the hardware method.
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
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...
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.
Sorry for the noob talk, but here goes....
I have a SM-G900T, rooted it and installed SM-G900T1 5.1.x stock MetroPCS rom mistakenly thinking all MetroPCS phones were sim/carrier unlocked since you basically buy them outright. I thought this because after I rooted and flashed the MetroPCS stock rom and dropped in the original T-Mo sim, it did not prompt for an unlock code (I understand why now from reading other forum posts that this is because of the MVNO relationship between the two, etc.). So anyway...
I OTA'd to MetroPCS's 6.0.1 and lost root. No problem. Easily rooted again using the procedure @thisisapoorusernamechoice kindly posted (big thanks to them!). Now, all is good [except that nasty little "Set Warranty Bit : kernel" b.s. on the Sammy splash screen, and in download mode "Knox Warranty Void: 0x1 (2)"].
I'd like to give this phone to my friend living overseas. So whats my easiest and cheapest path to sim unlocking this phone? Clearly T-Mo and MetroPCS aren't going to give me the time of day. I tried the suggestions of @stkt2ya but had no success. Rooted, busybox, Region Lockaway, Galaxy_S_Unlock, all granted SU permission, etc. but no luck. Is there a nearly stock ROM I can flash that has the sim lock removed, or can someone point me in the direction of disabling it myself since I have root? I have some developer experience and could probably do it with relative ease if I knew where to look. I understand the sim unlock is probably in the radio, but I am not entirely clear on this. Any help would be greatly appreciated.
Also, can I get rid of the "Set Warranty Bit : kernel" crap on the boot splash?
Thanks in advance for your help!
I'm assuming you turned the OEM unlock on in Dev options right? I've essentially put all the different carrier Sim cards in and have even done a factory reset with no issues so I'm not sure what's going on for you.
I'm still kind of a noob myself but just managed to do it on my own with the above mentioned software. Region Lock Away: unlock, reboot then with new SIM inserted relock. Then use that Galaxy unlock. I'm not sure but I'm thinking Busybox was important in there somehow and i was rooted, had all Knox and related stuff disabled etc. I'm not even rooted right now and don't care really as my life is pretty hectic at the moment. I'm responding here only because of the 'mention' email and the fact it seems you still need help. If this doesn't work for you i don't know what to say. Check all that stuff on the phone is as factory as can be, forget root for now and try the factory reset options, clear the del cache etc. maybe until you see 'hope' then proceed with the rest, maybe that will solve it for you. Sorry i can't be of more assistance.
Not sure about the OEM unlock in DEV options, I looked for it and didn't see an option. DEV mode is on though, I had to enable it to check off USB Debugging. The issue with the apps is that it says it fails writing to the SD. The SD is good though, confirmed. Kinda at a loss.
RegionLock Away: "An unexpected error occurred! #3"
Galaxy_S_Unlock: efs file saving (Step 1) "Error, Not Saved." (and thus can't continue to step #2)
I am doing this all with no sim in the phone. Could that be the issue?
Thanks again for the help.
Luke4903 said:
Sorry for the noob talk, but here goes....
I have a SM-G900T, rooted it and installed SM-G900T1 5.1.x stock MetroPCS rom mistakenly thinking all MetroPCS phones were sim/carrier unlocked since you basically buy them outright. I thought this because after I rooted and flashed the MetroPCS stock rom and dropped in the original T-Mo sim, it did not prompt for an unlock code (I understand why now from reading other forum posts that this is because of the MVNO relationship between the two, etc.). So anyway...
I OTA'd to MetroPCS's 6.0.1 and lost root. No problem. Easily rooted again using the procedure @thisisapoorusernamechoice kindly posted (big thanks to them!). Now, all is good [except that nasty little "Set Warranty Bit : kernel" b.s. on the Sammy splash screen, and in download mode "Knox Warranty Void: 0x1 (2)"].
I'd like to give this phone to my friend living overseas. So whats my easiest and cheapest path to sim unlocking this phone? Clearly T-Mo and MetroPCS aren't going to give me the time of day. I tried the suggestions of @stkt2ya but had no success. Rooted, busybox, Region Lockaway, Galaxy_S_Unlock, all granted SU permission, etc. but no luck. Is there a nearly stock ROM I can flash that has the sim lock removed, or can someone point me in the direction of disabling it myself since I have root? I have some developer experience and could probably do it with relative ease if I knew where to look. I understand the sim unlock is probably in the radio, but I am not entirely clear on this. Any help would be greatly appreciated.
Also, can I get rid of the "Set Warranty Bit : kernel" crap on the boot splash?
Thanks in advance for your help!
Click to expand...
Click to collapse
Ok so having root won't get you sim unlocked no matter what you do. Also no rom you flash could possibly sim unlock your phone. Also the OEM unlock the other user mentioned has absolutely nothing to do with sim unlock.
You have 2 options to sim unlock.
1. Call metro or tmo (I'm confused on which device you actually have. Since you say you have the g900t but flashed g900t1) and if you are the original owner, and had/have service on it for 90 days they will give you the unlock code and walk you thru it.
2. If the above doesn't work for your situation, Google g900t unlock code. You'll have to pay could be 99 cents like some metro phones or could be 40 bucks like some higher end metro phones. EBay is a good place to look for cheap unlock codes
Cool, I kinda just needed to know what direction was the path of least resistance. The IMEI is not good and the phone never belonged to me, so I'll look for the sim code. Thanks for spelling it out for me, I appreciate you help!
Ya eh. It's been so long since I've done that but will be attempting it again soon with a friends phone. All i do remember from this was what i had mentioned prior and because that took me a week or 2 of part time screwing around with it, trying this, trying that etc, i wouldn't for the life of me truly know at which point i finally succeeded... I have been messing around with an LG unit that proved to be much more of a challenge, especially considering i must have bricked it 3 or so times over. I can't wait to get going on these i•••things•••
Do you need to be on a stock ROM to sim unlock?