Database Info

Most unusual..

My Thunderbolt is locked somehow, and I have no way to restore it to factory defaults. What I mean by "locked" is as follows:
I remove two apps from the device, change the wallpaper and delete a contact. Then, I restart the device - when it boots back all of the changes I made are gone. It's like in read-only mode, the changes look like they take affect but after a reboot everything is restored to it's current FC'ing on everything state.
I've tried factory resetting the device but instead of booting to recovery it just boots to the picture of a phone with the red caution symbol showing, it does not do anything else.
I've tried flashing over a stock RUU image but the flash either 1) looks like it works then boots back to the state it was before, 2) hangs on part of a flash and reboots to the normal state.
The device is not rooted, I've tried revolutionary and get the following error:
"rawadb_handle_msg" and then it loses connection.
Any ideas would be appreciated, I've never seen anything like this.

Turn it on and let it boot up if it can then pull the battery while its on and leave power off for 5 minutes then try again.
Also can try, with power off, hold power button and volume down button together for a few seconds and when it gets to the white screen wait for about 10 seconds then select reboot from there

Latest OTA patched the Revolutionary exploit (so it won't work). You may want to root using ADB and flash the rooted RUU. Can't say I've ever seen R/O behavior; but then again, I've been rooted for months - currently on AOSP (ShiftAo5p 2.8) and waiting for an ICS with data
I know, not too helpful, but there are still ways to root.
Any feedback from VZW or a "real" corporate store? They're actually quite helpful here with tech junkies.
OK, one more suggestion - early on, I couldn't do anything either (Market, etc) and the fix was to pave (format) my SD card. I know it sounds weird, but I was going to exchange my phone (ordered, then sent back replacement). I figured, what the heck. Took the uSD card out, put it into my PC's USB port and formatted it FAT32, popped it back in and VOILA - happy happy joy joy.
Granted I copied all the data off of it before paving - then copied back selectively (highly recommend AirDroid, by the way, no more cables). Might give this a shot.

Hey guys, thanks for the suggestions - unfortunately no luck on my end with that

nautical34 said:
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
Click to expand...
Click to collapse
I inserted the card freshly formatted (I wasn't rooted at that point) - nothing on it, and I booted up, I was able to install Market apps (which I couldn't do before) - Note - AFTER I also did (multiple) a factory reset, I was good.
That didn't work for you? Maybe try again? Or just No-Go?
Also helps prove every 'Bolt has its own personality
Good luck on your CLNR ...
I have no idea what errant app or corrupted data may have been on the card, but totally paving and starting over "fixed it". Soon after, I rooted Then I had choices Granted I've had times I've had to do a factory reset (but not pave the SD) and set up all again - I've found the larger games (haven't determined which yet) cause my phone to get into reboot fits if I do actually reboot (which I need to do sometimes to get the radios to get data again); so, boring maybe, but very few games installed. That's OK, I prefer to learn or listening to music during idle time. Good luck.

[IRC] #HTC_MT4GS - Support Channel for MyTouch4G Slide

Noticed you guys didn't have a support channel 24/7 in case people have issues with their device. I've set this up and granted I can't stay awake 24/7 I would like to see this community more involved. The more support you have for the community the more support for the phone So come in, chat, ask questions, its all up to you!
Server: irc.freenode.net:6667
Channel: #HTC_MT4GS
Browser: http://webchat.freenode.net/?channels=HTC_MT4GS

Cool idea. Thanks.
Sent from my myTouch_4G_Slide using Tapatalk

Thank you for this !

This is a good idea.
I tried to connect last night through the device, but it wasn't working out too well.
Is there a recommended way to connect through the phone? Maybe an app that works through the T-Mo network?
Also - Since this has the potential to let people work things out much more quicly/easily... Can I request that if problems get solved or new information is discovered and there are no threads about it, can one be made after the fact?
Anyone who wasn't in the irc chatroom won't have access to that fix otherwise.

Blue6IX said:
This is a good idea.
I tried to connect last night through the device, but it wasn't working out too well.
Is there a recommended way to connect through the phone? Maybe an app that works through the T-Mo network?
Also - Since this has the potential to let people work things out much more quicly/easily... Can I request that if problems get solved or new information is discovered and there are no threads about it, can one be made after the fact?
Anyone who wasn't in the irc chatroom won't have access to that fix otherwise.
Click to expand...
Click to collapse
i signed in with the app AndroidIRC, no problem. seems to work better on wifi, but i've used it on the mobile network in the past. i believe the app is a couple bucks in the market.
it would make sense to me to post any discoveries found in the channel into these forums
edit: can't seem to connect to irc.freenode.net via the app while connected to the mobile network only. it keeps saying something about needing to identify via SASL to use this server.

Blue6IX said:
This is a good idea.
I tried to connect last night through the device, but it wasn't working out too well.
Is there a recommended way to connect through the phone? Maybe an app that works through the T-Mo network?
Also - Since this has the potential to let people work things out much more quicly/easily... Can I request that if problems get solved or new information is discovered and there are no threads about it, can one be made after the fact?
Anyone who wasn't in the irc chatroom won't have access to that fix otherwise.
Click to expand...
Click to collapse
thats fine ill log the chats in case something comes up

yogi2010 said:
i signed in with the app AndroidIRC, no problem. seems to work better on wifi, but i've used it on the mobile network in the past. i believe the app is a couple bucks in the market.
it would make sense to me to post any discoveries found in the channel into these forums
edit: can't seem to connect to irc.freenode.net via the app while connected to the mobile network only. it keeps saying something about needing to identify via SASL to use this server.
Click to expand...
Click to collapse
On a quick search, that's the only one with SASL support, which is where my problem was. When I get the chance to get market apps again it's on my buy list.
I tried to log in through the web page, but on the mobile it was no good on mobile network - I imagine it would be fine on the device through wifi and i'll try sometime. I have no trouble logging in through the webpage on a computer on a wifi network.
The last time I used IRC, mIRC was pretty new, so was my first brush with it over cellular networks. If you had no issues using that app then that'll probably be my answer for out and about.
JKILO said:
thats fine ill log the chats in case something comes up
Click to expand...
Click to collapse
That would be fantastic - probably the best way. Over time we can compile a pretty thorough FAQ, if people use it, and the easy web login makes that more likely.

andChat is a way to go.

Yaaic is another one that works

hboot and recovery
I had my phone rooted for months (I think I did it properly using the method from unLocker.com, although when the hboot would load it would say no image found) Then all I would do is run recovery (clockwork I believe) to flash new ROMs... but now I am trying to upgrade to pyr-o-ice 1.1.3 from 1.1.2 and everytime I try to run recovery, it just brings me back to the hBoot. I think I messed things up when I downloaded the Clockwork app from the market and let it do it's "thing". I think it changed my hboot from 1.44.00something to 1.44.1107 (that may be the problem). I have been trying for hours to re-root using the method from unlocker but it is not working. Can anyone help me get recovery working again to flash new ROMs? p.s. Sorry if a solution is already given somewhere, I have looked for a while and haven't found it.

GooberdaNoober said:
I had my phone rooted for months (I think I did it properly using the method from unLocker.com, although when the hboot would load it would say no image found) Then all I would do is run recovery (clockwork I believe) to flash new ROMs... but now I am trying to upgrade to pyr-o-ice 1.1.3 from 1.1.2 and everytime I try to run recovery, it just brings me back to the hBoot. I think I messed things up when I downloaded the Clockwork app from the market and let it do it's "thing". I think it changed my hboot from 1.44.00something to 1.44.1107 (that may be the problem). I have been trying for hours to re-root using the method from unlocker but it is not working. Can anyone help me get recovery working again to flash new ROMs? p.s. Sorry if a solution is already given somewhere, I have looked for a while and haven't found it.
Click to expand...
Click to collapse
What's your exact HBOOT version number?

my hboot is 1.44.1107

oh wow! I just tried using the using the clockworkmod ROM manager app from the market and it actually worked this time to flash pyr-o-ice 1.1.3_2. I don't know why it didn't work the several times that I tried this before. I guess I will just use this app to go into recovery and flash ROM in the future (kind of better anyways because I don't need to do a battery pull now everytime to go into hboot) apparently this app works to flash stuff. I haven't yet tried to go into Recovery the old way and I guess I don't need to worry about it any more.

It's not necessary to do a battery pull to get into recovery...
...power off (not hibernate, turn that fastboot off in settings!) and wait for it to turn completely off.
...hold the 'Volume Down' button, and then press and release the 'Power' button (maybe 2 or 3 times if necessary while holding volume down...)
When you see the Hboot screen release volume down...
Let it load and settle for a minute, then choose 'recovery' from the menu...
...and that's it.
Not sure where you had to do a battery pull, unless you didn't have 'fastboot' turned off from in the ROM settings menu?
Go to your app drawer, then open the 'Settings' apk...
...find 'Power' in the list and tap it...
...scroll to the bottom and un-check the 'Fastboot' option.
The 'Fastboot' option in the settings -> power menu is a deep-sleep hibernation mode that turns almost everything off, but leaves the tiniest bit of power to one chip so it can wake everything up.
When it's ' off ' in HTC Fastboot mode, pressing the power button wakes the device up skipping a lot of things like hboot and so on to get your device from ' off ' to working in just a few seconds, instead of the minutes a normal boot takes.
Anyways, glad you found a way to get it all working!

That is probably why I would have to do a battery pull (fastboot was never turned off to my knowledge). One problem though... I still can't find the option "power" in the settings menu to actually turn off fastboot. I am running pyr-o-ice 1.1.3_2 right now (that I was able to flash using the ROM Manager app made by Clockworkmod) When I select Settings; it brings me into a series listed as the following:
WIRELESS & NETWORKS... Wi-Fi, Bluetooth, Data Usage, More DEVICE... Sound, Display, Storage, Battery, Apps
EXTRA SETTINGS... Toggles, Clock, Battery Text, Custom carrier label
PERSONAL... Accounts and sync, Location services, Security, Language & input, Backup & reset
SYSTEM... Date & time, Accessibility, Developer options, About phone.
I couldn't find the fastboot setting anywhere in these. Also, I think something is wrong with the Recovery that I was using before ever since my Hboot changed to the 1.44.1107 it is now, because when I am in hboot and try to go into Recovery, it just loops back to Hboot. Luckily that ROM Manager App was able to flash the ROM (pyr-o-ice 1.1.3_2) but I don't know if I would recommend that to anyone else to use as I think when I installed ROM Manager and ran some of it's features, that it probably what changed my HBoot version (and subsequently messed up my ability to use recovery straight from hboot). I guess I am OK though since I can at least flash ROMs, but I am limited from some of the other features the old recovery had to offer.

OK! So, so, sorry... I just went and did a power down and tried to go into hboot (volume down and power buttons) w/out battery pull and it DID go into hboot. I guess fastboot is turned off (even I couldn't find it anywhere in settings still). Sorry for confusing anybody (I'm a little confused myself) And now when I chose RECOVERY, it did work fine ( I have no idea what happened). I guess I just always assumed I needed to do a battery pull since that is what I had to do way back when I first rooted my phone and started flashing ROMs.
I still can't really get my USB to recognize on my computer though with this pyr-o-ice desense 1.1.3_2 (I got the Dual Mount SD app from the market but am having "weirdness"... when I plug in the USB to the phone and PC, I hear the "bloop bloop" sound but no icon pops up in the "devices with removable storage" catagory of my computer. I can only get it to recognize as a drive by selecting the "Power On Auto Mount" feature in Dual Mount SD app and then doing a power off and back on w/ the phone plugged in the whole time via USB to PC... and then that is even hit or miss. sometimes it comes up as a drive and sometimes it doesn't.) I would really, really love to get my phone to recognized as a drive just by plugging it in w/out having to do a power off and back on since I love taking pictures with the phone and getting them to PC asap. If anyone knows any tricks to help me out that would be super cool. And P.S.: sorry I'm such a noob, I am trying really hard and am a bit intimidated by complete lack of knowledge about most of this stuff.

How are there no people in the IRC? .__. It's a great way to chat guys.

the diode of "ALT" and "SHIFT" do not highlights [Pyro Ice
I have these problem: the diode of "ALT" and "SHIFT" do not highlights when i push it. I didint dropped the phone or something. But it is very annoying
How i can fix this bug? Some1 have this bug? Should i just reflash a other CWM?
Thank you

thank you!

Indirect said:
How are there no people in the IRC? .__. It's a great way to chat guys.
Click to expand...
Click to collapse
Still no people

[Q] Help - Verizon 4.0.4 OTA - Galaxy Nexus

The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh

the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu

so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j

Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.

Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?

After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!

same exact issue here.

A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!

My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.

[Q] [HELP] Heat and signal problems on ZTE V970

Hi to all, I'm writing here because I had my first problems with my v970 (with etotalk rom). This evening I checked my mobile and I found that none of the sim was active (I was not in airplane mode) and I could not activate them, as if they were not in their slots. Meanwhile the upper part of the device began to heat up, so I tought it could be an antenna/receiver problem. I almost forgot to say that I installed Truecaller (deleting Contapps) and updated facebook and few others apps less than one hour before the event, but I already uninstalled them to exclude some of the possible causes. I'll gladly listen to any advice. Thank's in advance. GL

Restart, and see if it continues.

Already tried a lot of times, with or without sim cards. I also noticed an abnormal use of battery.

When did the problem start? What did you do before it started? Does your cellphone always have no signal, or does it come & go (sometimes SIM works, sometimes it doesn't)? Have you checked your APN settings?

post-mortem said:
When did the problem start? What did you do before it started? Does your cellphone always have no signal, or does it come & go (sometimes SIM works, sometimes it doesn't)? Have you checked your APN settings?
Click to expand...
Click to collapse
The problem started yesterday and I never experimented It till now. As I Said, before I encountered It, I updated some apps from the market and I changed the default caller manager (should I call It in this way?) with Truecaller. I also deleted my sim contacts
. I can't check apn because there are no apns to check (Android shows me the voice "mobile networks" but I can't select it
Update: I tried to restore the original rom, but the problem persists. I also made a check with the recovery, and it shows me that the device cannot detect sim cards. I begin to think that it's an hardware problem (ouch). Am I right?

What did you do in recovery that checks SIM cards? Are you talking about CWM recovery?

post-mortem said:
What did you do in recovery that checks SIM cards? Are you talking about CWM recovery?
Click to expand...
Click to collapse
Nope, it's the faulty recovery that etotalk sent me with the phone. I would like to install the cwm and flash another rom, but I'll leave that as the last option

If the recovery they sent you is faulty, then what good is it? If there's a custom recovery available for your phone, you might as well go with it, not that it'll solve anything by itself.
You might try inserting some kind of shim along with the SIM card to see if the extra pressure help make contact with the leads. Careful, of course, that whatever you stick in there doesn't stay behind.

post-mortem said:
If the recovery they sent you is faulty, then what good is it? If there's a custom recovery available for your phone, you might as well go with it, not that it'll solve anything by itself.
You might try inserting some kind of shim along with the SIM card to see if the extra pressure help make contact with the leads. Careful, of course, that whatever you stick in there doesn't stay behind.
Click to expand...
Click to collapse
I know about the recovery, but I was trying to don't invalidate the warranty (as if I'll ever use it...). Now I'm charging the phone, it's already the third time today...

Aw, heck. If you've got warranty, just send it in.

post-mortem said:
Aw, heck. If you've got warranty, just send it in.
Click to expand...
Click to collapse
Yep, I've got warranty, but sending it in China will cost me almost as much as buying a new one

Ok, I flashed a recovery and a custom rom, but nothing happened.The signal is still absent and the antenna heats up the same way as before. I tried to enter engineer mode and it shows me messages as "com.android.internal.telephony.CommandExcepti on: RADIO_NOT_AVAILABLE", "3G off. Cannot set", ecc... It also shows me "invalid IMEI" if I try to look at it and I cannot change it back with the AT +EGMR command (it says "Radio on" and "SIM State: ABSENT", altough the SIM card is in its slot).

I think you have to crack the case.

ArcheoGian said:
Ok, I flashed a recovery and a custom rom, but nothing happened.The signal is still absent and the antenna heats up the same way as before. I tried to enter engineer mode and it shows me messages as "com.android.internal.telephony.CommandExcepti on: RADIO_NOT_AVAILABLE", "3G off. Cannot set", ecc... It also shows me "invalid IMEI" if I try to look at it and I cannot change it back with the AT +EGMR command (it says "Radio on" and "SIM State: ABSENT", altough the SIM card is in its slot).
Click to expand...
Click to collapse
Hmmm... if your phone is reporting invalid IMEI numbers then I would try first to get that working as it should. Read this tutorial and re-write your IMEI numbers.
Then I would try the latest stock ROM, which is available on ZTE support website. Here is the direct link to the ROM.
If your phone still doesn't work after that, then I'm afraid you have a hardware problem.

I have had the telephone for more than one month with no problem. Trying every ROM made by Bruno with no problem at all with signal, but...
About 4 days ago, I started suffering exactly the same problems stated by ArcheoGian. I have tried everything (installing older Roms, rebooting, changing SIMs from 1 to 2, etc.) but unfortunately with no success. I just have to try to install the original ROM, but I supose it will be the same.
Afer a few reboots, I can make the telephone to search for a network, it founds it, it connects, it transfers data, I can make calls, but ramdomly (can be after 30 seconds, 30 minutes or maximum one hour) it disconnects and the red X of death (Xbox 360 times ) appears on top of the screen.
I can try to go and return from airplane mode, or search for networks that it won't re-connect.
I fear it can become a typical problem for this phone.
I am "delighted" to send it back to China and wait for two months to get it back (after explaining it to the seller and so on). Fingers crossed

@prinxo: did you buy it from eto...k? (I don't know if I can write the entire name of the seller)
Update: I tried everything it was told me (except to crack the case, at least not yet...), my last hope is to manually insert the IMEIs inside the data folder. There's just one problem: none of the methods suggested in the link posted by bcgngm works on my phone, so I need to generate the IMEIs whit my pc (I couldn't open the exe with windows 7, I'll try with win xp in a while, otherwise I have to ask someone to create it for me).

ArcheoGian said:
@prinxo: did you buy it from eto...k? (I don't know if I can write the entire name of the seller)
Click to expand...
Click to collapse
No, I bought it from another seller at Aliexpress.
As I thought: I tried to re-install an original ROM, and everything remains the same. I thought I was successfull but after one hour the phone disconnected itself from the network. After that moment, I need about 3 re-boots to get signal again and it lasts for just a few minutes.
At this point, I would disregard a software problem.
Happy happy to have to send it back to China.

ArcheoGian said:
Update: I tried everything it was told me (except to crack the case, at least not yet...), my last hope is to manually insert the IMEIs inside the data folder. There's just one problem: none of the methods suggested in the link posted by bcgngm works on my phone, so I need to generate the IMEIs whit my pc (I couldn't open the exe with windows 7, I'll try with win xp in a while, otherwise I have to ask someone to create it for me).
Click to expand...
Click to collapse
Why do you say it is not working? My preferred method is to use the adb commands (and for that you have to install Android SDK). Don't forget that when you type the commands there is no output message on the screen. The phone has to be restarted so that changes take effect.

bgcngm said:
Why do you say it is not working? My preferred method is to use the adb commands (and for that you have to install Android SDK). Don't forget that when you type the commands there is no output message on the screen. The phone has to be restarted so that changes take effect.
Click to expand...
Click to collapse
The third and the fourth ones are the only methods to restore IMEI I didn't try, just because I never used sdk and adb (and I'm not sure to be able to use them). I followed the others options (I also created the IMEI file with the russian program), but it continues to show me the "invalid IMEI" message. Can you help me, maybe showing me a good walkthrough?

This ADB Tutorial looks easy to follow. Check it out!

Getting an OTA update after installing TWRP and rooting OR use RUU?

I have an HTC One E8... I know, it's ancient... But... It's been a good phone until this past year when it really started dragging. Takes forever to do anything. A year ago, the main camera (is that the front or back camera) stopped working (phone doesn't even recognize that it's there -- flash doesn't work either with a flashlight app). Before that, phone dialing using my Bluetooth earpiece stopped working. Maybe related, but the phone doesn't work as a phone (holding it to your ear). If I'm not using the Bluetooth earpiece, it will only work on Speaker-phone mode (voice command apps such as Google Assistant and song recognition apps like Sound Hound don't 'hear' anything). Lastly, the Bluetooth has been disconnecting for no apparent reason. My earpiece will say 'Phone 1 disconnected', but when I look at the Bluetooth icon on the phone, it still thinks it's connected. Tapping the icon to turn off Bluetooth and then tapping again 'fixes' the problem and it connects again. It's just annoying when it does this in the middle of a conversation (and because, when it happens, the other party doesn't hear me yelling at them to wait because my Bluetooth disconnected because the phone doesn't know that anything is wrong). I had read ones that the Bluetooth drivers for this phone were sketchy. It's strange, though, this this problem has really gotten worse over the past couple of months without me making any changes to the phone. Lastly, the battery has really gone downhill. The phone will unexpectedly shut off around 30% battery. (I even tried the HTC battery recalibration technique -- no joy.) I chalked all of this up (except for the battery issue) to software. I thought maybe a good ol' factory reset (wipe) would fix the issues. For years (literally) it's been nagging me about a system update (Android 6.0). I never did it because the phone was already running slow and it's always screaming about being out of storage space. It hovers around 500MB free most of the time. I don't have that much installed on it. Any apps that will allow it, have been moved to the SD card.
That's the back-story to give you some insight as to what's going on with the phone. I included all of that 'other' stuff (camera and voice dialing issues) in case someone has seen them before and can offer any suggestions there.
So here's where I'm at. I decided to try to do a factory reset to 'refresh' the OS (remove all the patches and updates) and start over. Afterwards, I wanted to run Link2SD with a 64GB SD card so I wouldn't have the space limitations that I'm experiencing now after all of the apps have updated. The other night, after backing up the internal memory and the SD card, I started the process. (BTW, I have another SD card that I'm going to use that I've already partitioned per the Link2SD instructions.) After much trial and error, dead download links, incompatible versions of adb.exe and fastboot.exe I finally managed to get TWRP recovery installed. Then there was the issue of getting a working SuperSU installed. Finally did that. The phone booted and started walking me through the process of setting up my Google account. Everything seemed to go well. The phone was just as speedy as the day I got it. I was even able to restore my 15000 text messages and it was still zippy. It was wonderful! Unfortunately, the camera still doesn't work. Seems like voice dialing isn't working at the moment either. The Bluetooth issue seems to have gone away. Since the camera still isn't working, it looks like I'm gonna have to bite the bullet and get a new phone. This one will just become a 'toy' or a temporary backup phone in the event something tragic happens to the new phone. I'll just use this one on Wi-Fi only to check the weather and maybe play some games (which I had pretty much stopped doing because it was so slow and always out of storage). I would also use it as my portable media device for listening to downloaded podcasts and music while I'm running or riding my bike. It could also (maybe without mobile data) track my runs and rides, etc. As long as it doesn't get slow like it was before, I think it'll do just fine in its re-purposed life. (It was so slow I could barely play music from Google Music and have Google Fit tracking my run at the same time. It would take forever to switch screens!)
Ah, what's this?! Oh, there's that software update again. I guess I'll go ahead and do it before I start setting up a bunch of apps and tweaking the phone to my preferences. Nope! It downloads the OTA update into the Downloads folder and starts the process, but when it reboots, it reboots in Recovery mode into TWRP. I'm now finding that you can't easily do an OTA update after you've rooted your phone and put a custom recovery on it. I've seen lengthy instructions on how to put get a stock recovery.img out of the OTA zip file in the Downloads folder. I've moved it to my PC and pulled the firmware.zip file out. When I try to open the firmware.zip file to get to the recovery.img file, Windows is saying it's corrupted. I also see something about using an RUU.exe or RUU.zip file to restore the phone to stock. I've downloaded the correct RUU .exe file for my Sprint e8 in case I decide to go that route.
Here's my question... I know, finally! Since I don't have really anything on this phone since I did the reset and root, would it just be simpler to use the RUU method to blow it away and start over instead of trying to resolve the corrupt firmware.zip file issue and all of the other steps that follow? That's question #1. Question #2 is this... Will this RUU that I downloaded actually take the phone straight to Marshmallow before it starts walking me through setting up my Google account? If so, that's great! I'm all for the ease of that. I noticed that OTA download was about 250MB, while the RUU download is 1.5GB. Why such a difference? Is it because the RUU is the full-blown deal and not just the patches? I'm fine doing the RUU and then reinstalling and rooting the phone afterwards if that'll work. I still have all the files that I previously downloaded.
Sorry for the novel, but I wanted to be as thorough as possible to eliminate the back and forth "Did you try this?" "Did you try that?" However, if there is anything that I left out that would help with your answer/advice, please don't hesitate to ask. Thanks in advance for any guidance you can give a noob.
lrbarrios