My post count is low or I would be posting this in the CM7 thread.
I upgraded from Alien, and wifi worked then, but it now gives me an error in CM7(as in it doesn't work, and just says "error"). It does the same with bluetooth. The cell data connection works.
To fix this, would I need to reinstall CM7 or the radio or what? Thanks!
Did you follow instructions and clear everything before installing CM7? (Like the cache and dalvik cache?)
Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?
jefesaurus said:
Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?
Click to expand...
Click to collapse
it comes with its own
I had this issue as well. It is not a good sign that the bluetooth is not turning on either. For me, it was a hardware issue and I had to get a replacement. Try reinstalling kernel/wiping dalvik cache. If that doesn't work, try a fresh install of stock 1.8.3 or alien. If that doesn't work, you are SOL.
I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.
Anamnesis said:
I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.
Click to expand...
Click to collapse
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.
So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.
I didn't realize that, sorry. I'm running it with no issues, but if your having issues then I would listen to Kraise.
---------- Post added at 03:48 AM ---------- Previous post was at 03:44 AM ----------
jiggytom said:
So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.
Click to expand...
Click to collapse
I'm not sure if my Bluetooth was or wasn't working when I had the issue. I have horrible reception in my condo so when I have issues with wifi I try to fix it immediately. Yours sounds like hardware.
To be honest though, my suggestions were directed at the OP. He JUST installed a new rom, and it was all working previously. The bluetooth, wifi, 3g, ect are all part of the radio. It seems much more likely to be related to software than hardware, as others have had the same problems. You really seem to take what I said personally, like it was an attack on you or something, but I was honestly just trying to help out and contribute in a positive fashion. My comments could not have been directed at you, as you didn't even post what your experiences were in the thread. Try to chill out a bit.
I was having issues with my wifi and bluetooth out of nowhere before I ever unlocked or rooted my phone. It was a little over a month after AT&T/Motorola released the Gingerblur(2.3.4) update to my phone which I had to download using a wifi connection. Out of nowhere, it stopped working... Bluetooth would not turn on, and Wifi always says "error" underneath it. I believe mine may actually be a hardware related issue.
DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kraize said:
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.
Click to expand...
Click to collapse
Try the Faux 1.0GHz stopgap kernel. I use that and it works better for me with CM7 than the packaged kernel because you can UV.
J-man67 said:
DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
Click to expand...
Click to collapse
check if you have the correct permissions for /data/misc/wifi/wpa_supplicant.conf. Try fixing permissions first through ROM Manager. Hope it helps.
Yeah, I was looking into that and modified/changed some settings around to no avail. I am going to try wiping and re-flashing and starting from scratch. It may be related to me dropping it this am. Wasn't a big fall, but that it the only thing I can think of at this point.
PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.
J-man67 said:
PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.
Click to expand...
Click to collapse
I have the same error - as I imported the phone, I don't have much in the way of warranty.
This guide shows there's no direct lead from the radio to phone - http://www.ifixit.com/Teardown/Motorola-Atrix-4G-Teardown/4964/2
Thanks! I am going to open her up and make sure that chip is still intact. Might be soldering it back in if need be. Seems that it will be the issue as Bluetooth does not turn on either.
While I haven't had the problem, I have a friend who from what he's telling me has the same WI-Fi error problem ever since updating to the AT&T 2.3.4. He has never rooted or unlocked and wants to update to the new 2.3.6 OTA, but can't due to the Wi-Fi error. Anyone make any headway on a solution?
It's a hardware issue.
Hi,
i experience the same problem with my friend's htc mytouch 3g, when i tried to install cm7 on it,
after that i tried fastboot erase system -w, then installed another ROM to be sure, i found that the WiFi now working fine,
so before opening her up try to install another rom like Dark-Side 2.3.5 or GingerMod 2.3.6, if the problem go away then it's cm related not hardware,
Related
Hi
After finding that I had problems with the Gingerbread update draining very quickly it was apparant that something somewhere was wrong, as other people was experiencing very good battery life.
The android os is not letting the phone go into sleep mode..
I got my phone to work correctly and this has worked for many others who I have spoken with..
Ask customer to back up all relevant data, or do it for them.. Then clear off the internal SD.
Use Odin and flash an Eclair rom, with repartition and pit 512
I use :- http://www.multiupload.com/BEPEXOJKY2
JM9 PDA
JM4 Phone
JM1 CSC
Let the phone bootup to the dashboard, then switch straight off back into download mode..
From here flash the JV* rom of your choice, with no PIT or no repartition.
Once complete put and the phone has booted put back the required contents onto the SD.. Best keep it to a minimum, just titanium backup etc and other essentials.
Hope it works for you
Before --------------------------------------------------------------------------------------After
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
___
What have you done with bootloaders?
Have you flashed the froyo bootloaders when downgrading and then the GB bootloaders when upgrading again? Or just kept the GB bootloaders during both of the flashes?
hope this works...
maartenlaeven said:
What have you done with bootloaders?
Have you flashed the froyo bootloaders when downgrading and then the GB bootloaders when upgrading again? Or just kept the GB bootloaders during both of the flashes?
hope this works...
Click to expand...
Click to collapse
I flash the full roms, so it flashes the boot loaders on each and every flash that I do
What exactly is the theory behind this trick?
Flashing to Eclair, and then flashing to Gingerbread. Sounds weird...
Updates OP.. Now with Download and Images..
I think it would work with any firmware that you can repartition and use a pit.. But for me JM9 works a treat.. It sounded strange to me also.. But I tried it and it went fine..
Looking good until you trigger draining again by any app ?!?
Not getting no where near as high drain though.. As you can see by the 2 images the drain should be high as WiFi is on constantly.. I don't use many apps, but Tapatalk, email and tweetdeck is all set to 30 minute updates..
This procedure doesn't make sense, I don't believe it. Probably the first JV* flashing procedure wasn't done properly or something.
Tyxerakias said:
This procedure doesn't make sense, I don't believe it. Probably the first JV* flashing procedure wasn't done properly or something.
Click to expand...
Click to collapse
How do you mean doesn't make sense !!!!!!!!!???????!!!!!!!!
I had crap battery with jvk jvb and jvh. This install method sorted it all out... Maybe an extreme way of going about it...
Sent from my GT-I9000 using Tapatalk
What is this??? Just 3 days for this trick?! I can even use mine for 4 days on stock JVB (with some UI mods though) on moderate use. And apps still trigger Android OS problem? So what is this exactly?
EDIT: Just saw your battery usage screenshot. Sorry but I doubt it much. Your phone signal went crap (red bars) but the graph didn't even flinch a bit...
Tricky103 said:
How do you mean doesn't make sense !!!!!!!!!???????!!!!!!!!
I had crap battery with jvk jvb and jvh. This install method sorted it all out... Maybe an extreme way of going about it...
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Ι mean that it is not a logical fix, hence, it doesn't make sense. Explain why this works, and then I'll believe it's not a coincidence....
You flash one rom, then you flash another one including bootloaders, wiping the first one entirely, then you reflash the first one including bootloaders on top of it, wiping it again entirely. What changes? Why does that improve the battery?
We do not know what is it but from what i know it is not: modem driver i have now set to 2G only data OFF wifi off gps off sync off and task killer killing everything but not clock when screen goes off, screen set to minimum brightness i have deleted samsung update app and some other apps (facebook etc) on desktop only apps shortcuts no widgets no wallpaper its pure dark. Now when i launch gameloft intensive game for 30 minutes, turn it off and put phone in a pocket after some time i get it back and i could feel that back of a phone is little bit hotter (on back plate where CPU is i think) and from now on every maybe 3 minutes battery is going constantly down 1% by 1% until i do reboot nothing will stop doing that.
No doubt about it, this trick works like a charm, I had a huge battery drain I flashed eclair then froyo then XWJVH, now I can use my phone moderately for more than two days with no problem, I ask everyone with battery drain to try it before judging, I know it doesn't make sense but believe me it does work.
Tyxerakias said:
Ι mean that it is not a logical fix, hence, it doesn't make sense. Explain why this works, and then I'll believe it's not a coincidence....
You flash one rom, then you flash another one including bootloaders, wiping the first one entirely, then you reflash the first one including bootloaders on top of it, wiping it again entirely. What changes? Why does that improve the battery?
Click to expand...
Click to collapse
My belief is that it is not due to bootloaders, as the only problem they give is a corrupt screen.. I think that constant flashing possibly fragments the internal sd and system storage and flashing jv* without a repartition or pit doesn't makes the faults occur..
How kernel JVH get more baterie life
How kernel JVH get more baterie life
It is not kernels fault, it is android OS core triggering phone to not sleep because of hi cpu usage, im trying to do it now because of dirtiness i have made before flashing JVH.
Adding additional info: i could feel when sleep is not working, when i click unlock button screen goes ON immediately, when sleep was working screen goes on little bit later
what helped you here is the reflash with repartition not flashing js*something first. could be the jv* only flash and you would not have drain again.
for me one app triggered drain not letting the wifi to change its state. noticed it as i had it set to turn off 10 seconds after screen and the stats showed the wifi on whole time.
Tricky103 said:
My belief is that it is not due to bootloaders, as the only problem they give is a corrupt screen.. I think that constant flashing possibly fragments the internal sd and system storage and flashing jv* without a repartition or pit doesn't makes the faults occur..
Click to expand...
Click to collapse
Interesting. So basically if someone updates from Froyo straight to JV* without repartition, they should, in principle, have great battery from the get go, right? (has anyone tried?) In that case there must be something wrong with how Odin flashes, not previously reported, since 512.pit is identical for Froyo and Gingerbread, and as far as we know the only thing that it does is to make the partitions.
What if we use Richtofen's method (the way he used to propose for flashing the leaked ROMs he posted), i.e. to flash first the pit file alone, with nothing else, then re-enter download mode with the 3button combo, and flash JV* without repartition or anything else. *Is there anyone who tried this and checked the battery?
This can potentially open a new line of investigation into how Odin works....
I think that Your methode make a clean install of rom. But i think that is just a small update. I dont wont less my data and apk. I ask to give me another method to make more batterie life. Thanks.
id the app causing the drain
make sure thats the case
report to app developer
I tried to update my 9020a to the 4.0.4, was somewhat successful except not cellular connection. I have blank bars for signal with an x in it.
My IEMI shows correct in the EFS folder
I tried flashing my radio many times, I have UCKF1. I tried the original one, it failed but was able to flash the new version. But, I still have the same problem and it shows my baseband ver as i9020xxki1
I then went back to the pixel rom I had on before, same thing, no mobile network.
Then i brought my phone back to GB, I had a rooted nandroid. Same issue
what the hell happened and how do I get it back.
im actually really glad i have the patience to wait for the official release of ICS and don't jump on every leak and spend hours trying to fix what could of been avoided.
THIS LEAK ISN'T FOR THE I9020A!
I know it was not for the 9020a, but there is others that were successful. I got it to run, and it worked great, except the radio issue.
Now Im all the way back on GB, and still cant get it to work.
I am tired of waiting. This is not my first android and I bought this phone for the updates. Well, its just like every other att devices, updates just dont come this way.
so, how do i get signal back
blackhemi4x4 said:
I know it was not for the 9020a, but there is others that were successful. I got it to run, and it worked great, except the radio issue.
Now Im all the way back on GB, and still cant get it to work.
I am tired of waiting. This is not my first android and I bought this phone for the updates. Well, its just like every other att devices, updates just dont come this way.
so, how do i get signal back
Click to expand...
Click to collapse
what is your radio version??flash your old radio maybe will fix it..
Flash working radio for i9020a.
UCKF1 is the radio, ive tried both versions.
screenshot
here is the screenshot of the status area. Not pictured is my IEMI, but it is correct. Its acting like the radio is off. Ive even toggled the radio off and on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you've made a backup of your EFS folder, repush it to your phone. That fixed my problems regarding radio a few times already.
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
try this...
fixed had to replace efs folder and use a totally new radio.
stock 4.0.4 is way awesome
Thanks y'all
what radio did you end up using? I'm having the same problem on 4.0.4...
varandian said:
what radio did you end up using? I'm having the same problem on 4.0.4...
Click to expand...
Click to collapse
UCKE1 fixed it for me.
I put KD1 on for my 9020a on AT&T (I get better data speeds with an older radio for some strange reason) and DELETED /efs, rebooted, and it started working. To anyone else reading this, backup /efs before trying ANY of this.
varandian said:
I put KD1 on for my 9020a on AT&T (I get better data speeds with an older radio for some strange reason) and DELETED /efs, rebooted, and it started working. To anyone else reading this, backup /efs before trying ANY of this.
Click to expand...
Click to collapse
Did you replace your EFS folder or just delete it?
If you replaced it, what command did you use to replace it?
---------- Post added at 08:45 PM ---------- Previous post was at 08:11 PM ----------
I'm completely at a loss.
I tried deleting the contents of my EFS folder, replacing it with the backup files, rebooting and still no luck.
Still no signal.
Any advice?
iboj007 said:
Did you replace your EFS folder or just delete it?
If you replaced it, what command did you use to replace it?
---------- Post added at 08:45 PM ---------- Previous post was at 08:11 PM ----------
I'm completely at a loss.
I tried deleting the contents of my EFS folder, replacing it with the backup files, rebooting and still no luck.
Still no signal.
Any advice?
Click to expand...
Click to collapse
i replaced my whole efs folder with the one I had backed up.
What radio do you have installed now??
blackhemi4x4 said:
i replaced my whole efs folder with the one I had backed up.
What radio do you have installed now??
Click to expand...
Click to collapse
I have XXKB3 right now... can't seem to get UCKE1
iboj007 said:
I have XXKB3 right now... can't seem to get UCKE1
Click to expand...
Click to collapse
does KE1 not flash for you or not able to get it to download
blackhemi4x4 said:
does KE1 not flash for you or not able to get it to download
Click to expand...
Click to collapse
HA! flashed it via CWM and now its back!!!!! Anyone who has this issue, try flashing UCKE1 via CWM!
Sweet, that was the only one that worked for me. Now go and enjoy 4.0.4
Im still on my first charge from this morning. I love it!
Instable network connection on I9020XXKF1
Since I updated to 4.0.3 I've been having random network connection issues: Sometimes when waking the phone from sleep while connected to wifi the signal bar is empty only fix is to reboot the phone. I've updated to 4.0.4 on Wednesday and still have this issue. I was wondering if any of you have a suggestion for a better radio for the GSM/UMTS version of the i9020. I9020XXKF1 is supposed to be the most stable radio, unfortunately it isn't for me. Anyone else experiencing similar issues?
Ok, Tonight i tried to install ICS Passion rom on my old samsung vibrant( is running bionix 2.2 rom). Following the instruction from ICS Passion rom thread , - First i tried to install CW7 gingerbread rom ( got some boot loop, ..)
- Then i boot to recovery mode again , install ICS passion rom, screen flashed like crazy and got boot loop one more time.
- Reboot to recovery again, reinstall ICS passion , everything went though perfectly this time.
- Finally, my phone booted up and show me this screen ( WTF***** )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I tried to press the reset button , phone turned off/on and showed me this screen again. Tried this 3-4 time but nothing changed .
How i solve this problem ?
- I tried to search google to get more information about what is going with my phone. Basically, there are alot of people have exactly same problem as mine.
- I found one instruction that told me to fixed the problem, i need to flash 2.1 stock rom by using ODIN ( download everything from this link: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/.)
1st Attempt: :
- Open ODIN, load file, put my phone into download mode..Hit start.Nothing happened. ODIN recognized my phone but the process stopped
2nd Attempt: :
- Changed usb port, did exactly same thing , the process now stopped at "analysis file" ..step
3rd Attempt: :
- Looked up google again, someone suggested that using Eugene_2E_JK2_Froyo.tar.md5 instead the stock 2.1 firmware might help. So i downloaded Eugene file, ran ODIN again. Still out of luck, process stopped at "leave CS.." step. At this point, i thought i bricked my phone already. So i unplugged usb cable from my phone. Tried to turn off, turn on my phone again, and it show me this screen (
4th Attempt: :
- I took the battery off, put it in, put my phone into download mode one last time. Open ODIN, load 2.1 stock file this time, hit start button and then BUMP..ODIN started to re-flash the firmware..And now my phone back to stock 2.1 .
P/s:
- sorry for my English, but hope this might help other people who get this error when trying to install ICS on their Vibrant.
- Any suggestion for me to install ICS again in correct way ? Thank in advance!
Does your internal sd card mount and can you access it? If yes, then you probably are the first one to get through this error. Congrats! Eugene's froyo has saved many many phones.
Edit: Strike that, it was a silly question.
No no really, do you have access to everything?? Cause i havent heard of a single person yet that got thru this bug with their sd card intact
Sent from a cell tower to the XDA server to you.
Finally, I successfully installed ICS on my vibrant. When i open setting, storage, it show my internal internal storage(about 2GB) - usb storage (about 14GB) - and my 8GB external sdcard. When i connect my phone to my computer, turn on usb storage, i can acces internal SD and external SD card ( can copy, paste, transfer files..) The gallery is able to show/view/play both video and image i have on my internal-external SD card but i can only access the internal one. I tried to find the external SD card but don't know where is it located. Is it mount as folder external_sd ?
****************
Ok, i found it. On ICS, the external sd card is mount as /emmc. Now i am able to access both of them. Nothing is broken in here.
In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.
Woodrube said:
In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.
Click to expand...
Click to collapse
Yes, it show me both internal and external.
tritran18518 said:
Yes, it show me both internal and external.
Click to expand...
Click to collapse
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA
Merio90 said:
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
- Because i did a factory reset so all kind of system data is clear, but photo, video, music...other files in both external and internal sd card still there and accessable. Just like you wipe your phone when you install a new rom.
- I think the key in here is :
+ i got the error message, and i tried to press the reset button 3-4 times without take off my sd-card from my phone. And it's still give the error message
+ I odin to stock 2.1 . fail - tried 2 time
+ change usb port, flash 2.1 again. fail - tried 2 time
+ flash eugene 2.2 ...fail. And while my phone still show me the downloading screen , i just took battery off, put it on, turned on and it show me the new screen ( computer-phone)
+ turn off, put to download mode, flash 2.1 again and success.
==> that is pretty much everything i remember. And i'm sure i remember it right.
Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)
ferhanmm said:
Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)
Click to expand...
Click to collapse
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)
This bug seems to happen with several diff ics roms, not just passions....
If i may venture my uneducated guess as to what happened to you:
As your odin was writing something on your phone and you pulled the batt, you corrupted the data... that means that the encrypted data and all that stuff got wiped on the next attempt and its like you had a new phone..
Prob wrong tho
Sent from a cell tower to the XDA server to you.
tritran18518 said:
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)
Click to expand...
Click to collapse
Best ics roms out IMO are br1ck'd and team DD's ICZenwich or Team Kangs AOKP build 31, both with MP's sub zero build 61 kernal.
Sent from my SGH-T959 using xda premium
You are a very lucky man. I got mine working with cm7 after bricking it like that just enough to sell to someone as "a portable wifi hotspot for whatever plan you want." For $50
Sent from my SAMSUNG-SGH-T989 using XDA
YESSS!
I had this issue today october/31/2012, i followed OP instructions and it works! Thank you very much. The only difference is that i pressed the reset phone button and when i realized that was a mistake ( you know, when installing something and you just click and say:yeah, yeah, whats next?) i pulled out the battery as soon as i can, i searched on the web, found this thread and instead of flashing stock firmware (eclair) i flashed froyo straight.
I hope this helps somebody like it help me.
So you have access to your internal SD?
Also what ROM were you running?
Did it happen after flashing or was it random?
Please give as much info as possible as this issue (EU) is still, for the most part, a bit of an enigma.
I approve this message.
Hello there
Yes, i have access to internal and external sd card
Before the issue I was running chimera v2.2 and chimera kernel but i wanted to flash aokp lastest releases so i used odin to stock, then flashed cm7 (here it give me bootloops but i just went to next step) then chimera 2.2 (here was when EU appears, my intention was after flashing chimera 2.2 flash aokp )
If you need more details just ask me.
You're actually very fortunate to still have Int SD access esp. after pressing the EU reset button. Since EU has been primarily associated with ICS for our Vibes (and theoretically wiping /data with CWM5), you can just skip Chimera altogether. After restocking and flashing CM7 (vibrantmtd), either go straight to AOKP JB or use a recent CM10 as an interim flash.
I know im fortunate, the reason i pulled out the battery after pressing the reset button is because i knew about the EU issue.
About flashing CM7 and then AOKP JB i did not know that i can do it that way, thank you.
So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Tgab100 said:
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Click to expand...
Click to collapse
You'll need to elaborate on how exactly you flashed back to stock.
Heisenberg said:
You'll need to elaborate on how exactly you flashed back to stock.
Click to expand...
Click to collapse
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Tgab100 said:
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Click to expand...
Click to collapse
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Tgab100 said:
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Click to expand...
Click to collapse
If you flash the factory images they overwrite what's already there.
Heisenberg said:
This is why I recommend people not use the damn things.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heisenberg said:
If you flash the factory images they overwrite what's already there.
Click to expand...
Click to collapse
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Same here with SkipSoft Toolkit, after unlock, root, busybox, wifi noproblem, but no LTE/3G on my phone, i try to relock bootloader and back to Factory image now.
Sigh!?!
Tgab100 said:
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Click to expand...
Click to collapse
I honestly don't know what's going on there, it might be worth trying the L build instead of M.
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
badboy47 said:
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
Click to expand...
Click to collapse
I seem to have touched that issue I was on the L build and went to M build using toolkit but noticed my apns got screwy so I corrected them and I'm on pure nexus and a-ok now!
I'm having a similar but different issue, I bought a used 6p... Good ESN.... A 64 GB to upgrade from my current 32 GB 6p. Everything works (including mobile data and texts) except for phone calls, it won't call out and goes strait to voicemail when calling in.
I had unlocked the bootloader and installed chroma, but still no phone calls, so I flashed back to stock and relocked the bootloader. Still nothing. I read this thread suggesting that I shouldn't use the automated tool kits, so I backed up and manually flashed it back to the latest stock image via fastboot. But same issue.... Back to no phone calls in or out, everything else working though.
Any suggestions?
Justin
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
kboya said:
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
Click to expand...
Click to collapse
For me, yes. I can see my imei from the normal "about phone" settings menu.
Justin
Delete and readd your APN for your carrier.