Related
Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work
How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help
Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!
Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say
Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.
so, i've been using xda for a while now and i would like to start thanking all the contributors and the nice android community there is.
today i'm posting my 1st post and it's not for good reasons...
i got my sgs [i9000 international] on september and i have to say it has been nothing but problems.
it was working ok but then came along the 1st issue - unable to receive text messages. it would just stop to receive them and i would have to place the sim card on another phone receive the 50 sms or so i was supposed to have been receiving and then place the sim card back on the sgs and it would be fine for 5 days or so and the problem would begin again and i must say walking around with 2 mobile phones is just stupid when i only need 1...
in order to solve this and some other lags the phone had i decided to update to 2.2. in portugal there's no official update in kies (at least for me...) so i decided to go custom rom. i went with doc's rom BUJP8 V9.0.1 non-wipe and then voodoo's lag fix and i finally had the mobile phone i always wanted. then came along another issue - unable to receive phone calls (it doesn't receive sms and phone calls, what kind of a mobile phone is this?!). when someone is calling me, the phone lights up, it says there's no network available, it regains the signal and i don't even know who called!
now, i don't know what to do, i have a sgs that just doesn't work and i don't know what i'm supposed to do. this thing cost me a lot of money and i just don't want to waste it, all i really want is a proper mobile phone, i want the sgs!
i would appreciate any help, tell me if i've done something wrong, what i can do to have this working.
thanks in advance
~galaxydroids
ps: sorry for the english, as i've said i'm from lisbon, portugal
the attachment shows the sgs info after the custom rom flash
Sounds really weird indeed.
Have you tried hard-reseting your phone?
Does it still do the same after a hard-reset?
Maybe there is something wrong with the phones hardware it you keep loosing signal, where other phones works perfectly.
I would say, try putting in stock ROM (2.1 for Portugal?) and see it the problems still occur. If they do, maybe you should send it in for repair.
so i was kind of avoiding the hard reset but went for it.
now the phone is...well... isn't. it did everything, rebooted and now the two led buttons are lighted up and the phone randomly vibrates. that's it. it's been like this for quite some time now. is this supposed to happen?
Mine started to do that after a reboot also I just reinstalled the rom and its working for now.
Sent from my GT-P1000 using Tapatalk
how did you reinstall the rom? i can't even connect it to the computer...
Using download mode, I guess...
yeah well i can't get into download or recovery mode, neither one of them, i've tried all the combos with the keys...
if i'm unable to get into download mode how can i use odin?
my guess is that your problem might be due to your carrier... I don't know over there in portugal, but I've always heard vodafone isn't very good....
I have same phone, international version, bought on sept. mine came from handtec.co.uk...
if your phone is like mine, you should be able to enter download mode, just hold down the volume down key + home key + power key.. in that order, you should see your phone boot to download mode.
Hope it helps
First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.
3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Hello folks!
I got my new Vivo XL less than 24 hours ago and messing around with it (as I do with all my Android devices) I tried rooting it as some people mentioned with rootking first and then remove it with something called sume-something, can't recall but I did it right lol. Right after this I restarted the device and to my surprise it was stuck in the blu logo at the startup (the one with the colors). I aint that stupid though so I went ahead and accessed the phone's original recovery to wipe cache and factory reset it as well with no success, I tried up to 5 times doing still with no success. Now concerned I tried reflashing the unit and again to my surprise since it is too new (perhaps) I haven't been able to find just 1 guide in which I could've just downloaded certain files and push them through fastboot or something, the only thing I found was installing TWRP or CMW through SP Flash Tool which I definitely tried and now the device won't even show me a colored screen. I was able to install the MDTK drivers so the unit gets recognized by my windows 10 computer and while trying to flash through SPFT the unit gets detected but right now the device just wont boot up and I can't find the way of somehow installing the stock rom (which I couldn't find) back to the device. I didn't touch the bootloader nor anything related to it just tried to root the goddamn thing -_-.
I'd really appreciate any help you guys could offer me, right now I'm downloading the VIVO XL backup someone left available at the following link but if I knew at least what to do with it :/
https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Keep in mind that my device right now is completely dead, I know I can flash it because when I connect it to the computer it gets recognized but nothing shows up in the screen , not even if I press the volume rockers or hold the power button.,
I'm even willing to issue a donation for the hero that could help me out because the unit was sent to my freight forwarder's locker and having it returned would technically be more expensive than getting the phone itself brand new, help a brother out and I'll do my best to help YOU out with at least a beer
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
MamoriNoTenshi said:
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
Click to expand...
Click to collapse
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
andymartinez96 said:
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
Click to expand...
Click to collapse
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
El Eduar said:
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
Click to expand...
Click to collapse
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
MamoriNoTenshi said:
You can actually flash the Gionee and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the , I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed , but rooted as well. Can't be happier right now, the , after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Thanks
I can´t write the imei (codes o aplications such as mtk tools, mtk engineering mode)
Saludos
ROM Stock BLU vivo XL
mediafire.com/folder/61m7ikt8k97j9/Vivo_XL_V0030UU_(TWRP)
Flash Tool (Mediatek)
mtk2000.ucoz.ru/load/soft/soft_mtk/sp_flash_tool/5-1-0-14
Kernel Source
FTP= 162.252.123.103/Vivo%20XL%20V0030UU/
Material:
plus.google.com/communities/117846429749085694805
Alguna idea para portar Cyanogenmod 13 a este modelo?
MamoriNoTenshi said:
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Glad you got it working. What kernel tweaks are you talking about ? I'd love to flash a kernel on my phone
Sent from my VIVO XL using XDA-Developers mobile app
D'not use Gionee, there is the Vivo XL posted.
You can't write the Imei with thats apk.
Flash the Vivo XL rom with SP Flash Tools.
Saludos
BLU One Plus con Tapatalk 6.0.5