Related
I just used ODIN to flash to stock ROM and modem in attempt to solve my problem with adding gmail account to my phone. It worked. I added my gmail account no problem and I was finally able to visit Android market. However, I have new problem now.
When I go to Market and download applications, I see bubble with "Your item will be downloaded" after I click on install button and then nothing happens. Application is not installed. No errors - nothing.
Does anyone have a solution? It would be much appreciated.
settings >> applications >> manage apps >> go to 'all' tab >> look for market >> clear data
after that re-login to market and see if that fixes it
Thank you xtone. I tried that to no avail. In addition to clearing cache on Market I also cleared it from Google Talk as I read they are somehow connected. Then I erased cache of all my apps and still it didn't get me anywhere.
Last thing I tried was to uninstall Market update. After that I have slightly different issue. Now it says 'Starting download....' and it never goes away. Also, it looks like Market re-updated itself to the new version! Is it possible?
I'm having the same exact problem. My issue started with Nero v2 and did not get fixed when I flashed Nero v3. Today, I tried PepperKake to see if that fixed the problem, but that didn't work either.
Even after a fresh install (after wiping and re-flashing, and before restoring my backups from Titanium), I try installing things from the market but nothing works.
If you look closely (at least on my phone), it will say "Downloading..." for a second or two, then FLASH "Download unsuccessful" and disappear almost instantly.
Somebody PLEASE help :'( This is very frustrating.
This happens to me on "occasion" where it says starting to download then nothing happens. The only way I get it to work, is if I cancel the current "download in progress" or whatever it says, then click "Install" once again, and then it starts immediatelly.
Also, I noticed that it was giving problems when I was using the older version of the market. Once updated it went away.
Duce HD2 said:
This happens to me on "occasion" where it says starting to download then nothing happens. The only way I get it to work, is if I cancel the current "download in progress" or whatever it says, then click "Install" once again, and then it starts immediatelly.
Click to expand...
Click to collapse
Just tried this, didn't work for me
Things that I found that could fix the problem...
Under settings>applications>manage applica.>running>clear data for "download manager", 'gmail".
Try re-formatting your SD card. Also, Unmount then Mount SD card.
Also, try using either data or WiFi and see if either works.
Do some research on this, there's alot of different threads concerning this issue, with possible solutions.
Duce HD2 said:
Under settings>applications>manage applica.>running>clear data for "download manager", 'gmail".
Click to expand...
Click to collapse
Tried, didn't work :/
Duce HD2 said:
Also, Unmount then Mount SD card.
Click to expand...
Click to collapse
Also tried, but to no avail.
Duce HD2 said:
Also, try using either data or WiFi and see if either works.
Click to expand...
Click to collapse
I've been on and off WiFi, but the problem persists.
Duce HD2 said:
Try re-formatting your SD card.
Click to expand...
Click to collapse
I don't mean to sound rude, but why would this affect anything? I feel like the problem must be with either the ROMs (JL5 ROMs maybe?) or the Market? As a test, I downloaded something through the browser with no problem. Also, is wiping much different from reformatting? What about disabling, then enabling voodoo (which I had to do in order to try out PepperKake)? I know they said "don't knock it till you've tried it," but backing up everything, reformatting, and then restoring everything seems like a tedious job and I wanna make sure I know why it's worth a try before doing it...
Also, to the OP: sorry if I'm hijacking your post. I just didn't want to start a new post and have people flame me with "THERE'S ALREADY A POST ABOUT THIS!" and whatnot.
Dude, all the stuff I brought up, I found through research in a couple minutes. Some of things I posted ended up fixing the issue for some people and some not. I do not believe the problem resides in the ROM or JL5 (which I'm running with no issue) but rather mods and what not that was installed previously...."ghost"
In the OP he states he went back to stock, so how could it be the ROM???
You don't want to be rude, nor do some research on the problem judging by your response. You want someone to give you an answer is all. Nobody has an exact answer, you just have to try different things and see what works.
"nuff said...do some research.
Duce HD2 said:
Dude, all the stuff I brought up, I found through research in a couple minutes. Some of things I posted ended up fixing the issue for some people and some not. I do not believe the problem resides in the ROM or JL5 (which I'm running with no issue) but rather mods and what not that was installed previously...."ghost"
In the OP he states he went back to stock, so how could it be the ROM???
You don't want to be rude, nor do some research on the problem judging by your response. You want someone to give you an answer is all. Nobody has an exact answer, you just have to try different things and see what works.
"nuff said...do some research.
Click to expand...
Click to collapse
No need to blow up like that...I was simply asking a question since this is the Q&A forum. I've had this problem for probably about two weeks and I have been searching through the forums, but I've never found a post where someone had the same exact problem (outside of the Nero post, but their questions went unanswered).
You bring up a good point about the OP using a stock ROM. However, I haven't installed any mods (I went straight to Nero from stock), so I'm not sure how there can be "ghosts."
Again, I'm not trying to be rude or appear lazy. There was no need for response like that. I'll take my research to solve my problem elsewhere.
I wasn't trying to be rude or anything.....but yes, there are various topics on issues with the market going from 2.2 back to 2.1 back to 2.2 and so on....hope you can find a solution to your problem, and maybe later share the outcome with us...good luck!
Found the cause but still no fix
Thanks everyone for feedback. After few hours of trying different things I found what's causing my Android market to not work.
Thus far, what I was doing when I got into trouble was:
1. ODIN to stock ROM and pda (repartition checked)
2. root using this method: http://forum.xda-developers.com/showthread.php?t=723479
3. as soon as my phone is rooted Android stops working
So I tried to install all the apps I really need first: ROM Manager and TBackup (my ultimate goal is to upgrade to nero3. Everything works great. However to use these apps I need root access.
So then I rooted again using same method as always and I get same result - malfunctioning Android Market.
When I root using above method everything works great but I see old icon of superuser application. Is there a newer update.zip to root my vibrant? Or perhaps different way to root my phone? Can I do it manually?
I have two Vibrant phones. One had no problems when I did above steps. One continues to give me grief!
Even when I odin to stock I know not all the folders get refreshed. What actually is untouched when I use ODIN method to revert my OS?
Duce HD2, what is the best way to eliminate 'ghosting' without bricking my phone? I also believe that it's caused by some mod that was done previously - I bought my phone used.
If reverting to 'stock' image is not good enough what else could I do to clean up my phone? I know for example that efs folder is unaffected by going back to 'stock' as my phone remains SIM unlocked when I do it.
Market problem
I'm having the same problem Nero v3 + voodoo. If you find a solution, please let me know,
Thanks!
ekloc said:
Thanks everyone for feedback. After few hours of trying different things I found what's causing my Android market to not work.
Thus far, what I was doing when I got into trouble was:
1. ODIN to stock ROM and pda (repartition checked)
2. root using this method: http://forum.xda-developers.com/showthread.php?t=723479
3. as soon as my phone is rooted Android stops working
So I tried to install all the apps I really need first: ROM Manager and TBackup (my ultimate goal is to upgrade to nero3. Everything works great. However to use these apps I need root access.
So then I rooted again using same method as always and I get same result - malfunctioning Android Market.
When I root using above method everything works great but I see old icon of superuser application. Is there a newer update.zip to root my vibrant? Or perhaps different way to root my phone? Can I do it manually?
I have two Vibrant phones. One had no problems when I did above steps. One continues to give me grief!
Even when I odin to stock I know not all the folders get refreshed. What actually is untouched when I use ODIN method to revert my OS?
Click to expand...
Click to collapse
I still use the Super User that you have and have no problems....
ODIN back to JFD
Root
reboot into CWM recovery
Wipe cache partition
Advanced
Wipe Davlik
go back
Factory Reset/Restore
and you should have gotten rid of everything
There is an update.zip root on the cynanogenmod ailing page for Vibrant.
http://wiki.cyanogenmod.com/index.php?title=Samsung_Vibrant:_Rooting
Don't know if its the new one.
Sent from THE Vibrant......
ekloc said:
Duce HD2, what is the best way to eliminate 'ghosting' without bricking my phone? I also believe that it's caused by some mod that was done previously - I bought my phone used.
If reverting to 'stock' image is not good enough what else could I do to clean up my phone? I know for example that efs folder is unaffected by going back to 'stock' as my phone remains SIM unlocked when I do it.
Click to expand...
Click to collapse
The best way ,"I" know, is to ODIN back to stock true (JFD), check repartition. Go through the usual process - root, rom manager, etc. Flash new custom ROM, "important" while it's still in recovery after installation is complete don't rebooot yet, this is where you'll perform these steps:
Wipe cache, wipe dalvik cache, fix permissions, perform factory reset. Then finally reboot phone.
I never ran into 1/10 of the problems that I see people having with their devices.
Also, after reboot make sure to leave your phone on idle for at least 15 minutes, so everything can properly get installed. Reboot, log in to gmail, give it 5 minutes, then reboot once again. Good to go.
Just like jmcghee1973 posted.
Give it a try and see if it works for you. Good luck.
Try using one click root as well. Never hurts to try...
Sent from my SGH-T959 using XDA App
Market working again
I followed the odin instructions, went back to stock, re-rooted, then re-installed nero3. This time I didn't restore system apps + data. My market is working. Hope this helps.
It worked for me too when I installed nero3 - market issues were gone.
I am actually not so sure any more that rooting caused the problem. What I observed was that my phone was downloading 'stuff' on its own soon after I reverted to stock image. I know that because I saw few 'download unsuccessful' messages. I also tested this theory - I reverted to stock. Immediately after I could use market but then 20-60 after my Market was not working, even when phone was un-rooted!
I don't know how these automatic downloads were triggered but my latest theory is that they have a lot to do with not working Market app.
Anyway, Nero 3 is not downloading anything automatically and I am really happy with it. Thank you guys for everything. You guys rock!!!
How's it going guys. Well I used Odin to go back to stock and it did pass and everything, but the phone is still rooted! Wth?? This didn't happen before so I'm a bit confused right now.
Funny thing is, all the apps that I erased are now back, but Superuser is still there....
Right now, i'm on firmware 2.1 Update-1
The files I used was
Stock-i500-VZW-System.tar.md5
Help would be appreciated!
akanightmare said:
How's it going guys. Well I used Odin to go back to stock and it did pass and everything, but the phone is still rooted! Wth?? This didn't happen before so I'm a bit confused right now.
Funny thing is, all the apps that I erased are now back, but Superuser is still there....
Right now, i'm on firmware 2.1 Update-1
The files I used was
Stock-i500-VZW-System.tar.md5
Help would be appreciated!
Click to expand...
Click to collapse
I'm not sure if that file is an official vzw file or one that was put together by someone else if I were to guess that is the case and the file you flashed contains root...if it still says your on 2.1 update one I think your odin file was really old?
where did you get that tar file?
What are you trying to accomplish exactly?
Sent from my SCH-I500 using XDA App
trying to just back to stock after updating the ClockWorkMod and totally f'ing up my phone. Every time I send text messages now, people receive blank texts :/
Did you ever find a solution?
I'm basically having the same problem nightmare.. same firmware version on my phone now, did you ever figure out what the problem was/how to fix it??
You need PIT and DL09 package. Will get you to DL09 without root. Upon first boot don't sign into google (so the market doesn't go on an installing spree) and do ota's to froyo.
good day.
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.
Ok, I have a rezound, unlocked and rooted with Amon Ra with the superuser binaries updated, all after installing the Global ICS RUU. I've been running this way pretty much since a few days after the Global RUU came out. Never had any problems or issues. Love this phone (except battery life but whatever). This morning before taking it off the charger I had it reboot (which I normally do every few days) and it did not reboot. It got stuck on the white HTC screen. The screen would come on, and then blink for a sec only to stay stuck on the HTC screen. No beats audio boot animation. I'm S-ON by the way. I use Mac so I was never able to get a windows computer to S-off, but I haven't wanted to flash any Roms since my days on the Dinc. I didn't have time to mess with it this morning so I just pulled the battery to shut it off. Now that I have a few minutes, I tried to see if it would boot, and same thing. Pulled the battery again, and powered up into the boot loader. Tried to enter recovery from there, and it just went blank. Pulled battery again, and tried it again. Same blank screen with no response from power button or anything. Now it is completely dead. Won't even go into bootloader. Won't even light up on the charger. SOME times when plugging it in it will light up for 5 seconds, but then turn off. Tried it with the battery out and pluggin it in to get into bootloader that way and nothing.
Is it completely fried? I bought it from VZW last April so it should be still under the 1 year manufacturer warranty. I'm hoping to find a fix as I haven't backed up in a while, but if not, hopefully they will replace it.
Even though I have a mac, it is set up to run adb commands, but everytime I try reboot or anything it just says "waiting for device". Clearly as it is not powered on.
Any ideas or help????
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
I just tried to do that and I can't get into the RUU zip file. I attached the kernel from the nandroid I made right after I ran the global RUU (4.03.605.2). If that's the version you are on you can try flashing this kernel and see if that does it.
Ugh... having trouble uploading it. If you have a nandroid from your global RUU you can pull the boot.img from that and flash it.
feralicious said:
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't know how to do that. I am not a newbie, but there is a lot I don't know. I follow directions well (being able to do the adb stuff with a mac) but pulling the kernel out of an RUU is not something I've ever read about doing.
I've read many threads about charging issues and what not, but I have the stock battery and the extended with a Seidio external charger so I know they both have plenty of juice in them. I know VZW will replace the thing, but I have stuff I'd rather not lose if I can fix it. If you could walk me through pulling the kernel out of the RUU.
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Once you have the kernel, pull the battery and put it back then boot into bootloader and put phone in fastboot. Attach to Mac, then use fastboot and this command:
fastboot flash boot boot.img (I named the one I'm trying to upload to ruuglobal_boot.img, you can either rename it or just flash using that name instead of boot.img)
feralicious said:
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Click to expand...
Click to collapse
I hopefully have a nandroid backup on the SD card, but I will tell you it's been a long time since I installed the RUU. I've been out of the rom'ing rooting/ fiddling game for a long time. I haven't had the time recently and apparently it ain't like riding a bike. I've had to read a ton today to refresh myself.
My dinc was so easy, you didn't have to know a whole lot. Just download a zip, check the MD5, and flash it. Rezound was more complicated with the S-on, so I didn't even bother getting started....just the RUU to ICS before it was official, and then the RUU to Global. So yes, I am running the RUU you listed.
Anyway, I don't have a way of reading the SD card until I get home to find the nandroid.....and I've never looked at a nandroid made with Amon Ra....I only was used to CWM on the Dinc.
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
feralicious said:
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
Click to expand...
Click to collapse
Was there an OTA recently?
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now. (Mine had a cracked screen so I couldn't get it replaced under warranty and had no insurance.)
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
feralicious said:
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now.
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
Click to expand...
Click to collapse
DAMN. Oh well. They will replace it most likely, and it seems like the easiest route to take. My wife's bootloader fried itself on here Moto D2 last year and it was LONG passed warranty and they replaced it......It was completely stock, but they had no way of knowing, so I'm sure they will send me a replacement phone. I just hope they still have Rezounds to send. I don't want to get stuck with something they determine for me because there are no more rezounds.
My wife's rezound is completely stock, never unlocked so I'll see if she got the update.
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
318sugarhill said:
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
Click to expand...
Click to collapse
Ok, I loaded the boot.img and no dice. Still stuck at the white HTC screen. This is frustrating now. Now I do NOT want to go to the VZW store as my bootloader says tampered unlock. I guess I can always try to run the RUU again.
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
Well, if I can get into the bootloader I can relock to run the RUU correct? I hate to have to lose everything, but I do need the phone, and if it was toasted, I would have to start over with a replacement anyway. Nothing on there can't be replaced except some pictures, but it won't kill me. Just a hastle. Should I try to relock and run the RUU? or should I try to load a Rom like Nils business sense for S-ON? I was considering trying it.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
I gave up bro. This sounds way over my head. I relocked and am running the Global RUU again. I will unlock again and load amon ra, and run the su binary zip I have again. Not worth this much time. My 3 year old is tearing up the place while I bury my face in my computer.
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
feralicious said:
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
Click to expand...
Click to collapse
I tried pushing the recovery again, I tried the boot (all three that were in the nandroid backup) and some other things on here I saw. Nothing worked. Just stayed at the white HTC screen. Relocking and running the RUU made the phone usable again. Thanks for your help, but my stuff is gone. After spending what feels like forever setting up the phone to make it usable again, it will all be gone when I unlock again. Don't have time to do that tonight, but this weekend I'll get to it.
Not everything is gone. I do have titanium but I haven't backed up in a while, so they will be old backups, but still backups. Lesson learned....schedule backups more frequently.....reset my dropbox to auto upload pics again. Turned it off Christmas day, and never turned it back on. The cloud is there for a reason right?
You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!