Related
it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.
I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..
still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu
Have you tried flashing while in quick boot?
sorry to be such a newb. but what is quick boot and how do i get to it
Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.
ok trying that now. and no errors with drivers
still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work
do you have "usb debugging" turn OFF?
I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it
RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...
Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.
I am in desperate need of help from this great community! ... I have had multiple smartphones (palm, blackberry, hero) and have hacked them all so I'm not a total noob at this, but I must admit this has me stumped ...
I rooted my phone about a month ago and installed fresh 2.0d ... everything was great with the phone ... it was superfast for me and had alot of cool features added from the stock 1.5 ... then slowly I started to notice a few bugs creaping out ... nothing major or that I couldnt handle / work around ... then yesterday my phone was in roaming mode all day and last night about 8 it lost all signal period ... I decided it was time that I reflash 2.0d ... when I boot into recovery I can wipe the data but when I try to wipe the dalvik it tells me to "run deldalv via console!" I used fresh kitchen and wiped dalvik and reflashed fresh 2.0d ... I also flashed the patch from fresh for menu-menu ... I have tried this multiple times and I still am unable to get my phone to connect to the sprint network ...
I have tried to search the forums and google several times now so if I am asking a question that is already answered somewhere else please be so kind as to point me in the right direction.
Thanks for any help!!! =o)
EDIT: I have just finished restoring a nandriod backup and I'm still not able to connect to the sprint network ...
I am still looking through the forums for answers, I'm thinking maybe flashing a new radio? possibly flashing another ROM to the phone ...
wolfscmb said:
I am in desperate need of help from this great community! ... I have had multiple smartphones (palm, blackberry, hero) and have hacked them all so I'm not a total noob at this, but I must admit this has me stumped ...
I rooted my phone about a month ago and installed fresh 2.0d ... everything was great with the phone ... it was superfast for me and had alot of cool features added from the stock 1.5 ... then slowly I started to notice a few bugs creaping out ... nothing major or that I couldnt handle / work around ... then yesterday my phone was in roaming mode all day and last night about 8 it lost all signal period ... I decided it was time that I reflash 2.0d ... when I boot into recovery I can wipe the data but when I try to wipe the dalvik it tells me to "run deldalv via console!" I used fresh kitchen and wiped dalvik and reflashed fresh 2.0d ... I also flashed the patch from fresh for menu-menu ... I have tried this multiple times and I still am unable to get my phone to connect to the sprint network ...
I have tried to search the forums and google several times now so if I am asking a question that is already answered somewhere else please be so kind as to point me in the right direction.
Thanks for any help!!! =o)
EDIT: I have just finished restoring a nandriod backup and I'm still not able to connect to the sprint network ...
I am still looking through the forums for answers, I'm thinking maybe flashing a new radio? possibly flashing another ROM to the phone ...
Click to expand...
Click to collapse
Have you tried nandroiding back to the one you made just after root?? You did nandroid right after root, right??
chfields said:
Have you tried nandroiding back to the one you made just after root?? You did nandroid right after root, right??
Click to expand...
Click to collapse
Yes I have reflashed the nandroid backup several times ... I have reverted back to 1.5 and back to fresh 2.0d ... several times and still no luck getting it on the sprint network ...
I read through the Fresh 2.0d thread and saw someone mention that they had no service as well and someone told them to update the profile and PRL ... I have tried to do both of these several times with no luck ...
I am about to DL Fresh 2.1.1 and another radio and see if flashing them on the phone will help anything out ...
could also be an issue with the raido on the hardware side, if flashing a new radio doesnt fix the issue then flash the stock radio back and then run the RUU and take it in to have it checked out.
thanks for the help chfields and wtphoto ...
I have been reading post after post and messing with the phone all night trying to get it up and running again .. somehow during one of my updates to the phone it error-ed out and now will only turn the screen on ... but when I plug it into the computer the HTC logo showed up ... I tried to flash a RUU to the phone but I kept receiving error 110 ... after searching online I found a posting where this guy says has saved about 15 Hero's that were in the same state as mine
Unfortunately it seems a bit complicated to me ... I'm having to learn about adb and fastboot (I originally used fresh kitchen to root my phone) ... at this point I'm going to take a break from this and hopefully after a taxing day at work tomorrow will have enough energy to come home and pull my phone back from the brink of death
ouch you got the 110 error that sucks man, from what I heard his method to fix it does work though.
Hey like ive offered to another guy im willing to help you out if you want just pm me if im on ive been in your shoe a while ago
It is stressfull at times but as long as you phone turns on somewhat you dont have a brick.
lostinroot:) said:
Hey like ive offered to another guy im willing to help you out if you want just pm me if im on ive been in your shoe a while ago
It is stressfull at times but as long as you phone turns on somewhat you dont have a brick.
Click to expand...
Click to collapse
Thanks for your offer! =o) ... After my last post last night I ended up trying ONE MORE TIME to bring my beautiful Hero back from the brink of death ... I was actually able to fastboot it and then to root it again ... however the post that I found while is a GREAT resource, it isn't the clearest in all of the steps of what to do for those of us that have never messed with the manual rooting ... so I'm having to referance other posts at the same time
I thought that I had it fixed last night but when I tried to boot it into recovery so that I could flash it again it started to show a triangle with an exclamation point on the inside and a phone below it ... so I'm sure that I'm very close to bringing the phone back to life, just have to play with it a bit more ...
I'm currently at work dealing with month end (I work in finance) so hopefully I can try to go home early to take care of more pressing issues!
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Shaun>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT0000000000 device
C:\android-sdk-windows\tools>adb push asroot2 /data/local/
931 KB/s (0 bytes in 74512.000s)
C:\android-sdk-windows\tools>
Correct me if I'm wrong but shouldn't the push asroot have some kind of bytes transferred? I have tried looking this up but I'm late for a birthday dinner ... the youtube video that I found shows 74512 bytes transferred
EDIT: I zeroed out my serial number just to be safe, in case anyone thought that might be an issue ...
after sifting through various forums and numerous posts I was finally able to get my phone booted into recovery! from there I was able to flash fresh 2.0d again and now have a working Hero again
However ... I'm left with my original issue that started this whole mess ... My phone will not connect to the sprint network ... I guess I'm off to many more google searches
You should try and update your PRL. If it is not 6066X then you are stuck roaming. I had this problem, and it was only after I got a new hero from the Sprint store that I found a fix. So just go to settings-about-system update and update PRL. You should get 60665. Hope that helps.
-------------------------------------
Sent via the XDA Tapatalk App
you could also try unrooting and sending it totally back to factory stock (see my signature for my guide) and then re-rooting again
My Hero is alive again!!!
After searching and reading every post I could get my hands on I was still unable to get my phone to connect to the sprint network ... I saw on the various forums that it was due to a PRL update issue ... I tried to use the built in PRL update feature with no success ... then I tried to manually update the PRL but was unable to without a code from sprint (and I wasn't willing to try a hack to find it on the phone) so I called sprint this morning and after spending over an hour on the phone with them I was finally able to get the PRL to update ... once that happend my phone was super happy!
Hey,
I'm a "noob" and not SUPER technically advanced when it comes to phones, but I have a decent idea how to do things with it.
I got an Incredible used from someone and it was already rooted by him. I was told the other night that you need to have the phone unrooted in order to get the official OTA 2.2 update. That night I attempted to unroot it, but turns out I was doing it wrong. I went to bed, and woke up with the OTA update on my phone asking if I wanted to install it, so I said Install Now, and it went to the Boot screen and I dont know if I did something wrong, or it just wouldnt work because my phone was rooted.
So now, 3 days later I've got it Unrooted finally, and I've tried several different update.zip files that I've downloaded from different forums, etc. None of them will work, and they all say Installation Aborted.
Also, when I am in the recovery screen, it says E: Can't open /cache/recovery/command
I've tried several different sd cards thinking that was the problem, and same failure everytime. I have a feeling it is my phone itself..
Any ideas, help, advice??
Greatly appreciated..
bbrown35 said:
Hey,
I'm a "noob" and not SUPER technically advanced when it comes to phones, but I have a decent idea how to do things with it.
I got an Incredible used from someone and it was already rooted by him. I was told the other night that you need to have the phone unrooted in order to get the official OTA 2.2 update. That night I attempted to unroot it, but turns out I was doing it wrong. I went to bed, and woke up with the OTA update on my phone asking if I wanted to install it, so I said Install Now, and it went to the Boot screen and I dont know if I did something wrong, or it just wouldnt work because my phone was rooted.
So now, 3 days later I've got it Unrooted finally, and I've tried several different update.zip files that I've downloaded from different forums, etc. None of them will work, and they all say Installation Aborted.
Also, when I am in the recovery screen, it says E: Can't open /cache/recovery/command
I've tried several different sd cards thinking that was the problem, and same failure everytime. I have a feeling it is my phone itself..
Any ideas, help, advice??
Greatly appreciated..
Click to expand...
Click to collapse
Just download the Verizon 2.2 Froyo update RUU. Run it on your computer with your phone connected and you'll get it. You didn't need to unroot either cause it will automatically zap that.
ejdavis72 said:
Just download the Verizon 2.2 Froyo update RUU. Run it on your computer with your phone connected and you'll get it. You didn't need to unroot either cause it will automatically zap that.
Click to expand...
Click to collapse
Hey, sorry but I don't know what an RUU is, and where/how I get it.. also, I have a macbook, is that a problem?
Thanks!
bbrown35 said:
Hey, sorry but I don't know what an RUU is, and where/how I get it.. also, I have a macbook, is that a problem?
Thanks!
Click to expand...
Click to collapse
I'm not sure if Mac is a problem but I'm sure you can find someone with a PC that will let you use it. I will private message you the link cause xda won't let me post a link here cause I'm too new to the forums. Check your inbox.
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
JDM-Bb said:
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
Click to expand...
Click to collapse
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Strephon Alkhalikoi said:
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Click to expand...
Click to collapse
thanks for the reply, so then what you are saying is that the phone was on GB at one point? man, i knew this guy tryed to flash a dif rom before he sold it. He told me he just got it replace by Dell and decided he didn't want it. i fixed my second problem but im still having the issue with the phone rebooting when data is turned on and then freezes at boot screen.
cdzo72 said:
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Click to expand...
Click to collapse
thanks for the reply
correct i do have drivers and adb in my PC and this is not my first time using adb commands. and yes i did bother reading many threads and using the search tool and found lots of great info but nothing pin pointing to the same problem im having with the phone not liking it when i turn my data on.
Btw i figure out why non of the GB roms were working, when i was doing the factory reset i was only doing it through streakmod recovery. but when i FR on the previous menu it worked.
i also made the diagnostic test through fastboot menu to test the sim and every thing else and everything is fine
Sorry for the late reply. I believe your data issues will resolve themselves by installing 407. From there you can install one of the custom ROMs.
hmm ok ill try that
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
thorindwarf said:
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
Click to expand...
Click to collapse
I have tried with a couple of SIM cards, and also without it. No luck, the SIM Cards were pretty old tho, I will try with a new one and see what happens.
Other thing, Shouldn't I see the IMEI and baseband without a SIMCARD in anyways??
Thanks
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
raptir said:
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
Click to expand...
Click to collapse
Hi, I already tried that, the 4.2.2 that i flashed was from there :/ (with fastboot)
Also I completely took apart the phone today, and the motherboard seems fine (for what the naked eye can see)
The battery seems to drain really fast tho.
pocketrussian said:
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will do that as soon as I figure out how to do it.
With diagnostic mode you mean that download mode or there is another one?
Also I noticed that every time i use LGNPST a window saying that my device is being installed pops up, could it be a driver issue?
I don't think that this would work in download mode. I just tried with LGNPST in download mode and it's asking for an spc code. I tried 000000 but I didn't work. I tried qpst and it says it can't read phone settings in download mode. Again, I don't know much about this but there must be another mode (diagnostic) for which this might work. I googled but wasn't able to find any # codes that work on the n4. Perhaps from the terminal emulator if your phone is rooted. I wish I could help more but I just got this n4 recently and I am not an expert in any of this stuff.
Sent from my cm_tenderloin using xda app-developers app
Same problem here...
venec said:
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Click to expand...
Click to collapse
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
stenosis said:
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
Click to expand...
Click to collapse
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
venec said:
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
Click to expand...
Click to collapse
I'm with the same issue. Any good news?
elbosio said:
I'm with the same issue. Any good news?
Click to expand...
Click to collapse
Nope, tried everything nothing works so far
I'm thinking about sending it to this guys or wait for kitkat and hope for the best:
http://mobiletechvideos.mybigcommerce.com/lg-phones/
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
I'm having the same issue so the phone is going back to Google for replacement. It has been acting wonky for a few days anyways.
I tried the Google factory flash script, flashed a few different radios, and followed this thread:
No luck.
I was running AOKP 2013-10-15 Nightly. And the problem started with the phone doing a constant boot loop for a few hours without me noticing. It was some kind of issue with the power button getting stuck that appears to have resolved itself but it took the radio with it.
Droid2drummer said:
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes it was 4.2, so you mean do the LGNPST thing and after flash 4.2 image?
I already did that with the 4.2.2 (JDQ39) image and still no luck
I had the same issue, and I solved it by flashing the factory images... Twice.