Related
Just updated JF1.41. Everything seemed perfect, but I found I couldn't download anything from Market, and couldn't see any clips from your tube either. I am able to see the previews in both...it's odd. If I changed wifi to GPRS, everything went back to good..I really did some modificaitons on IM. But even I copied back the original files, the problem still existed..I don't know if I can flash the official build back to fix this??
for me it works with jf 1.4.1. the only issue I have so far is that snapphoto does not recognize my sd anymore (see my other thread).
Before going crazy and flashing back to RC29, try doing a full wipe and see if that fixes the problem.
nickwinn said:
Before going crazy and flashing back to RC29, try doing a full wipe and see if that fixes the problem.
Click to expand...
Click to collapse
Agreed. flashing the nbh is a bit.. extreme . Additionally, flashing the nbh is riskier than wiping or re-applying the JFv1.41 update. Flashing the nbh could potentially brick your phone, doing a wipe or re-applying the JFv1.41 update doesn't touch the bootloader, so it is much much safer.
I had to reboot my phone before downloading anything from the market but I think it was because of bad reception. I say first reboot it, if it doesn't help -wipe it.
I found that I had to log into Gmail to setup the phone and log into the market via GPRS and download one program before I could download reliably via WiFi.
JesusFreke said:
Agreed. flashing the nbh is a bit.. extreme . Additionally, flashing the nbh is riskier than wiping or re-applying the JFv1.41 update. Flashing the nbh could potentially brick your phone, doing a wipe or re-applying the JFv1.41 update doesn't touch the bootloader, so it is much much safer.
Click to expand...
Click to collapse
Actually, I had done the wipe and re-applied the JFv1.41 update many times, but that didn't work for me. I knew I did something wrong, but I just didn't know how to undo what I had done...What I had done is that I deleted [email protected]@[email protected], and applied another version of this file in order to make my MSN work with others carriers except Tmobile in GRPS mode.
Anyone else with this problem on ADP1.1? I cannot even access the internet with WIFI any longer. I have deleted NOTHING, done a wipe, and prior to installing anything, tested it again. No dice
maybe a silly question, but those help me too, sometimes...
did you re-enter your wifi settings? they are wiped, too.
sputnik99 said:
maybe a silly question, but those help me too, sometimes...
did you re-enter your wifi settings? they are wiped, too.
Click to expand...
Click to collapse
I was about to smack you upside the head (interwebz style) but I have done stupid stuff before like that and realized it would be unjustified. Yes, my settings are all good. I am connecting with WPA-PSK
I don't think it has a lot to do with the 1.41 biuld. I'm still using 1.31 and just recently I've started having this same issue. I have no clue why this is happening, all used to work fine about 1 1/2 weeks ago????
Hey guys so I'm pretty tech savvy and i know my way around this phone but something weird's been happening. I had CM 4.2 on my Mytouch3G. I tried applying a theme which made it not boot up anymore(bootloop).
I did make a nandroid backup before but when i tried restoring with it, it keeps getting stuck at the green mt3g screen or at the second loading screen. I've tried flashing the rom again but gets stuck at the same place. If I just install the htc 1.6 update it works fine. But when I go to apply the CM 4.2 update it gets stuck again. I have wiped a million times, and fixed ext system also a bunch of times. I have also unrooted also by applying sappimg.nbh and starting over. Rooted, tried again, but nothing, still getting stuck at the loading screen. I have gotten it a couple times to go all the way to the home screen but i get com.android.phone force close.
Also i've tried going from stock htc 1.6 to CM 4.1.99 and up, not just straight to CM 4.2 so i don't know what to do.
Any help appreciated!
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
charkosh said:
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
Click to expand...
Click to collapse
Maybe a mytouch issue? Hopefully we can get some help.
lupascu.marius said:
Maybe a mytouch issue? Hopefully we can get some help.
Click to expand...
Click to collapse
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
bluecluenj said:
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
Click to expand...
Click to collapse
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Make sure you wipe before applying rom
Mr Bill Florida said:
Make sure you wipe before applying rom
Click to expand...
Click to collapse
Do people even take time to read the original post, or do they just blurt out things that sound helpful? I said towards the middle of the post that i've wiped a million times and also tried fixing ext filesystem. I appreciate anyone trying to help but please read my post carefully!
I have the same problem guys, but oly with 4.2.3.1
http://forum.xda-developers.com/showpost.php?p=4851283&postcount=3677
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
jayzusfk said:
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
Click to expand...
Click to collapse
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
lupascu.marius said:
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
Click to expand...
Click to collapse
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
lupascu.marius said:
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
lupascu.marius said:
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Click to expand...
Click to collapse
Actually if you have an MT3G I believe you don't flash the 1.6 recovery image, but flash the 1.6 ADP rom. That is what I did since I was already rooted but with AmonRa's donut rom, but wanted to give Cy a shot, and I had no problems flashing this HTC ADP 1.6 DRC83 , then reboot manually but while rebooting I pushed home fast while it was rebooting to get me to the recovery screen, then I just flashed Cy's 4.2.2 then I went to the market and downloaded his Cyanogen updater and checked for an update, then found the update 4.2.3.1 and downloaded that straight to my phone and then choose to reboot and it automatically installed 4.2.3.1 straight to my MT3G with no problems at all.
From Cyanogen:
Download: Android 1.6 Recovery Image. (This isn’t like a typical "recovery" image we know -- it’s simply HTCs version of an update.zip.)
* Magic32A and Magic32B users only: Download this HTC_ADP_1.6_DRC83_rooted_base.zip
lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
mavsfan said:
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
Click to expand...
Click to collapse
That is the exact process i run thru. Sorry for the confusion, the reason i said htc recovery 1.6 is because thats what htc calls it. So i do have the htc 1.6 adp.....and i do wipe a lot also
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
jayzusfk said:
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Click to expand...
Click to collapse
The problem i have is with the stock 4.2.3.1 not the themes...and i've also tried without rebooting after installing the 1.6 base and just go straight to applying the CM update
pascanu said:
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
Click to expand...
Click to collapse
Hey thanks for your suggestion, i have tried that, I've reformatted, I've tried different SD cards and nothing changed. I'm pretty sure the sd cards are good...
[SOLVED]Finally...
So for anyone having similar issues, here's what i did to finally get this working.
Apparently with Cyanogen's newest ROM's you HAVE to partition your sdcard, so the Rom will run on certain phones. I don't know if its all phones because there's only a few people that i've heard to have this problem. So here's the steps:
Things you will need(all these can be found in this forum)
1. Phone+sdcard
2. sappimg.nbh
3. FlashRecovery.apk
5. AmonRa's recovery image(has more options than CM's RecImg)
6. Htc ADP 1.6 stock donut rom
7. CM 4.2.3+
8. A theme(optional)(check out the Eclair 2.0 theme)
Starting from scratch
1. a. Put sappimg.nbh on sd card and turn the phone off.
b. Turn phone on by holding VOLUME DOWN+POWER
c. Apply the stock sapphire image and boot up to home screen.
2. a. Now put FlashRec.apk and AmonRa's recovery image on sdcard.
b. Install a file manager like Astro and install FlashRec.apk
c. Now open it and click Backup Recovery Image.
d. Now erase whats in the box and type /sdcard/name.of.recoveryimage.img
e. Yes you do have to type .img after the recovery image name.
f. Then click flash.
3. a. Now put the HTC ADP 1.6 Rom and CM 4.2.3+ Rom on the sdcard.
b. Reboot into recovery by holding HOME+POWER.
c. Now partition your sdcard by selecting it from the menu(the one that says +swap)
d. Now convert ext2 to ext3. After that I did:
4. a. Wipe, format ext3, wipe
b. Flash HTC ADP 1.6
c. Wipe, format ext3, wipe again.
d. Flash CM 4.2.3+
e. Wipe, format ext3, wipe one more time
f. Reboot, now it should work, give it some time to boot up.
Adding the theme
1. Make a nandroid backup before starting to save you the hassle.
2. Put your theme.zip on sdcard and reboot in recovery again.
3. Choose apply any zip and choose the theme from the list.
4. Reboot once its done and enjoy.
If anyone has any questions about anything here go ahead and reply or PM me. Have a good one guys, hope this helps anyone.
Oh and if you guys see any mistakes let me know so i can fix it, its pretty late right now
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
I got no problem at all until now.
Another thing I've discovered is when I get these FCs, sometimes if I enable the bluetooth, the phone suddenly discovers the network and the FCs stop. That's just very odd, to me.
I really hope that's not a problem with my phone (especially since it does work properly with RUU).
foouser said:
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
Click to expand...
Click to collapse
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
wnp_79 said:
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
Click to expand...
Click to collapse
Tried doing the same process without fixing permissions, twice already, and I still get the same problem.
have you tried this?
http://forum.xda-developers.com/showpost.php?p=18309360&postcount=9
Helped with the market issue, but not yet with the com.android.phone FC...
foouser said:
Helped with the market issue, but not yet with the com.android.phone FC...
Click to expand...
Click to collapse
Odd. Here is how I did mine, step-by-step. (Do a NANDroid backup before this, and copy it to your PC/Mac.)
1. Install latest 4EXTRecovery from here: http://forum.xda-developers.com/showthread.php?t=1130004
2. Use this to format all partitions to EXT4. (Not sure if you are using EXT3, not sure if it matters, just saying I'm on EXT4 formatting with no issues.)
3. Do the full wipe & manual format routine (including boot) again just in case!
4. Flashed CM7.
5. Flashed Gapps.
6. Flashed Tiamat kernel (1.1.4)
7. Reboot.
I'm used the same radio as in my sig but also doubt that matters. Not sure what else to suggest. Try downloading the ROM again, and compare the MD5 of your two downloads.
Wow, I believe I'm in some big trouble now. I decided to try and get my phone replaced in the store since I just recently bought it. I used this guide: http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 to get back to S-ON, but when I tried to flash back the RUU, I get a CUSTOMER ID ERROR and the flash fails.
I've tried two RUUs: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
But they both end up the same way. I'm now stuck on the HBOOT screen with S-ON and a big purple security warning (I guess since CM7 is still on the /system partition).
Any help?
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Tectas said:
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Click to expand...
Click to collapse
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
I have FC with Market. Everytime i try to acces it.
foouser said:
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
Click to expand...
Click to collapse
Don't mind the recovery step, just do the commands within adb shell
Swyped from my Desire S
mihaibuda said:
I have FC with Market. Everytime i try to acces it.
Click to expand...
Click to collapse
Have you tried wiping cache and
dalvik cache?
I also had fc after an update, this solved it for me.
If you're using cyanogen, try changing the language to English us, this solved it for some users.
Swyped from my Desire S
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
foouser said:
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
Click to expand...
Click to collapse
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
ben_pyett said:
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
Click to expand...
Click to collapse
Sure, it's really the same process for all HTC phones and works even on the newest models (Sensation generation). Thanks a lot to EFI from AlphaRev who actually pointed me in the right direction.
I used this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I'm using Windows 7 x64 and when I inserted the card after modifying it, Windows required me to format it (as opposed to what's written in the above guide), but it still worked. Also, since my phone was stuck on HBOOT I had to use another Android phone to get the SD's CID (I used a friend's SGS, and the SD slot to query is mmc2 on it).
shrome99 said:
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
Click to expand...
Click to collapse
Well, I actually didn't use Titanium Backup at all, so nope.
Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy
Hi all,
I have a K1 and have been using it for around a year with little issues. But it became sluggish and unresponsive so I felt it was time for a fresh rom.
I first went for AICP - 12.1 - N 7.1_r9, later also tried Tesla N - 7.1.1_r13 [OMS] and Cyanogenmod 13.0 for Shield Tablet, but no matter what ROM I tried, I always end up with absolutely NO wifi.
When trying to activate Wifi during the initial setup, it takes forever and then just quits trying. No networks show up and my MAC is shown as "02: 00: 00: 00: 00: 00" which I am sure is not my actualy MAC address.
I have read into the issue here androidpolice. com/2016/02/02/nvidia-has-halted-the-android-6-0-update-for-the-shield-tablet-because-it-might-break-your-wifi/ and on other sites and it appears to be a known issue. But the bug described above is
a) so old I'm sure it has been fixed in N 7.1 or CM 13.01 and
b) is supposed to only affect the original shield tablet and not the K1 version.
(maybe not even a bug but a feature? android-developers. googleblog.com/2016/02/marshmallow-and-user-data.html)
I read somewhere that rebooting might help, it did not. Also, someone suggested to use ES File Explorer to change the MAC manually. Sadly, I get a write error when trying to change the txt file.
Any ideas?
Thanks!
What OS version were you on before going the custom rom way? 1.5 (the latest)? 1.4 had WIFI issues. And 1.5 has a new bootloader.
edisso10018 said:
What OS version were you on before going the custom rom way? 1.5 (the latest)? 1.4 had WIFI issues. And 1.5 has a new bootloader.
Click to expand...
Click to collapse
I actually have not checked but can say I have applied all OTA updates that were available from nvidia
Did you do a clean installation of your custom rom (Wipe system, cache, data)? Especially not wiping system before flashing a new rom can be the culprit.
edisso10018 said:
Did you do a clean installation of your custom rom (Wipe system, cache, data)? Especially not wiping system before flashing a new rom can be the culprit.
Click to expand...
Click to collapse
I used the standard TWRP wipe a few times and also manually did more complete wipes before flashing the different roms.
The standard TWRP wipe does not format system. You must use "Advanced" and then select system !!, cache and data (a so-called "clean flash"). If you don't format system you get incompatible settings especially if you switch between different rom and os versions. If you want to return to stock search in this forum. There is a detailed description here.
edisso10018 said:
The standard TWRP wipe does not format system. You must use "Advanced" and then select system !!, cache and data (a so-called "clean flash")..
Click to expand...
Click to collapse
quite sure I did include a system wipe at least once during the numerous flashes. But thanks for the tip, I will try this later today and let you know.
I again tried fresh installs of different ROMs, this time I have wiped everything except SD. No difference, still the same useless MAC address and no wifi.
Sorry, but I don't have much more ideas.
Tried to reset your router? Removed the tablet from the router?
I remember someone having such problems before. And his router had saved some incorrect informations. After removing the device from the router or resetting it (don't what it was anymore) the device was working again.
edisso10018 said:
Sorry, but I don't have much more ideas.
Tried to reset your router? Removed the tablet from the router?
I remember someone having such problems before. And his router had saved some incorrect informations. After removing the device from the router or resetting it (don't what it was anymore) the device was working again.
Click to expand...
Click to collapse
thanks for the ideas, anyway. I don't see how this could be router-related because the device does not even enable the wifi. I have multiple networks in my house and the error occurs long before any of them should be visible.
I guess my only option is to find a stock ROM and see if that helps. I tried HyperStock yesterday with no success...
Then you should go the hard way and return your tablet to stock 1.5.0. Remember to save your data since everything will be erased.