Related
so I got a new (new to me was used) g1 today from a friend at work and everytime I turn the phone off with the power button it only starts in boot loader without pushing the camera button it does it on its own if I take the battery out and wait a minute or two then it will boot and run normally
history of the phone
not sure if this was a problem with previous owner he said that for the 3 months he owned it he never turned it off and so never saw the problem (thats crazy that he kept it charged all the time for 3 months)
phone was off when I got it running the latest ota firmware
I turned it on into bootloader and downgraded to rc29
downloaded telnet never got it to connect
while playing with telnet noticed the problem of booting into bootloader
downloaded flashrec.apk and put 1.4 cyanogen recovery on
made nandroid back up
did hard spl from the g1 faq
put on ota-tmobile cupcake with root
put expansion on for ota-tmobile cupcake with root
bump I will be back tomorrow afternoon to see if any one knows thanks everyone
Sad day today....all was well, tried to play around with Swap memory and then the trouble started,
First all the data on my SD card got wiped out !
After that the phone just went dead, no led when connected to charge,screen was dead no light, flicker of any sort, removed battery and tried many times still no luck...
suspected it could be a software problem so connected to to SUT, a phone was detected, tried completing the stock ROM reload, went to certain extent but then resulted in FAIL
Post that now I get a led red light when connected to charger but nothing else. does not go into download mode or battery charging animation.
Tried SUT once again but this time there is no phone detected.....
not sure if it is battery / handset problem....did the core areas in the phone get corrupted while playing with Swap ???
I partitioned using CWM, used Swapper2 app, all went well till I realised that data in SD was wiped clean.
Was on sharp mod...missing the phone badly...any help or guidance will be much appreciated...
Also will visit to service center help now that this phone is completely off SPICE stores ? yes it is still under "Warranty"
had to switch back to blackberry yucksss !!...for sometime I was infact trying to touch the screen
hoping to hear soon from you guys !!!!
First of all very sad to hear, My heartfelt condolences....
At this stage after trying SUT for multiple times, I think a visit to Spice service center is the only solution, please try it and update here
Be ready to part with your phone for a week atleast
BACK in BUSINESS
I got it Back folks.....thanks to SUT & Windows.....was breaking my head on what could be wrong...retraced back all my steps....
checked if the device has been wrongly configured by windows....went to device manager...lo I saw there was "Other Device" with something registered as Qualcomm CDMA. Deleted it...removed the usb and reconnected.....
Windows did a fresh installation of the device...after sometime I could see F drive of the device with image folder and all its contents....
Simply ran SUT once again, even now there was no display, just a gut feel everything will proceed smoothly....and yes SUT detected the device went through the installation. At one step it also asked if it could format F drive....I went ahead pressing OK....SUT finished successfully...after few anxious moments saw the familiar battery charging icon ......My day was made....and after few more anxious moments....I pressed power button to see SHARP Loading....my device is reborn again !
lesson learnt.....Don't play with SWAP mem, let the dev folks figure out and guide us...
If in any trouble keep SUT and preferrably Stock NB0 file handy.
Back in business folks !!
well done bro, was following your situation closely, so glad your phone is back to normal.
Sent from my SH8188U using xda premium
Glad that it works
Great job done
Sent from my Desire HD using xda premium
I will note your experience. Because I am a newbie who tend to do stupid things may be experiencing the same thing. Glad you can solved it and thanks for sharing.
Device still bricked
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
9K OMG without looking at the phone
ya that idiot has fu***-up my phone earlier too. few months back my glass cracked, although the phone kept working fine. he changed the glass and returned the phone 2 months later, with all signs of ra**e been committed on phone. they never knew anything about the phone and were surprised to see such a huge device from spice. so they tried all there *tools* to pry it open before realizing that what damage they have done. my gps stopped working since then, they refused to fix it saying that as the phone has been *opened* (ra**d by them) it is out of warranty, although it was still under warranty.
And now this has happened.
Mod edit : dont use any abusive words its against the forum rules if u do need to use them i have edited ur post OK
forthe said:
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
Click to expand...
Click to collapse
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
vijayar said:
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
Click to expand...
Click to collapse
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
haree said:
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
Click to expand...
Click to collapse
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
vijayar said:
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
Click to expand...
Click to collapse
hi
its ok budget buddy i didnt have much money and only the spice guy was giving me the buy back :laugh:
Phone not detected
I tried all the methods mentioned above on two different PC's. The Problem is that the phone is detected as "USB Input Device". The driver is provided by SUT. When it says device driver installed it shows as "usb input device" and the red notification LED glows. This happens whether or not battery is inserted. I charged the battery externally too.
Any Solutions?
Okay a few weeks ago I got a text from AT&T saying there was a new update. It gave me a link to go to, so I went and I downloaded the LGMobile Support Tool from that site. I run it, and this is all I've ever been able to get.
http://screencap.net/f/433834bf.png
It just gets about that far and sits there.
I would love to be able to update my phone but I'm stuck. Any help?
Are u in USB debug?
Sent from my LG-P925 using XDA
Yea. But I don't have my phone plugged in when I run it.
Well I just disabled USB debug and plugged the phone in. Still no.
DracoAzule said:
Okay a few weeks ago I got a text from AT&T saying there was a new update. It gave me a link to go to, so I went and I downloaded the LGMobile Support Tool from that site. I run it, and this is all I've ever been able to get.
http://screencap.net/f/433834bf.png
It just gets about that far and sits there.
I would love to be able to update my phone but I'm stuck. Any help?
Click to expand...
Click to collapse
your phone has to be in download mode to get there remove the battery hold volume + and power at the same time then plug usb in and wait 3-5 seconds insert battery till phone vibrates and release volume and power button phone should not turn on just stays dark and in the device manage in the ports (com lpt) you should see omap4430 or lg device i cant remember but when you are there try the update
That's not wat I did I just put debug it crashed a couple of times but after a while worked fine
Sent from my LG-P925 using XDA
Well it's not doing this while I'm updating the phone it's doing this while I'm installing the LGMobile Support Tool software itself
Isn't there a way I can just get a kdz file and flash it manually?
Yup
Guide Here
http://forum.xda-developers.com/showthread.php?t=1287236
While your at it just snag V21e since it has the least issues with Ghost Calls.
http://forum.xda-developers.com/showthread.php?t=1635011
That's an italian kdz. I'm in the states. Does it matter?
DracoAzule said:
That's an italian kdz. I'm in the states. Does it matter?
Click to expand...
Click to collapse
no it don't matter it will work fine just won't have at&t bloatware
sent from my acidhazard thrill
Well now it's still wanting me to install the tool
And when I click on the B2CAppSteupe.exe file, instead of getting stuck it opens, stays there for a second, then closes back out
I have an AT&T Note 3. I was rooted using the KINGO app, but returned my phone to stock several weeks ago and the rom shows official and the knox count is 0. I am running the stock AT&T Note 3 Android 4.3
The other day, an official AT&T android update was pushed to my phone. The update bricked my phone and now I am unsure if I can even recover what was on my phone...or at the very least get it running again. For now, I am without a phone.
When I can get the phone to power up, the phone attempts to "Recovery Booting" (this is displayed in blue letters in the top left corner with the galaxy Note 3 Logo in the middle). It tries to install this AT&T update following the recovery wording when powering it on normally and when using Volume UP/Home/Power . The update progresses towards 100% then "completes" sometimes, but then the screen goes black and the phone does not start back up. I have to remove the battery for a period of time and replace to get the phone to do anything
I can get the phone to go into download mode (Volume down/Home/power), but my phone did not have USB debugging turned on the last time I was able to access the options, so it is not recognized by kies/odin, etc!
Even though their update caused the problem, AT&T wont help me (over the phone or at the store) as my phone is over a year old...their solution is to buy a new phone and plan as they say they can't do anything to fix the phone.
ANY HELP WOULD BE GREATLY APPRECIATED!
Can you get into recovery?..if so try to factory reset then maby you will be able to power up get to developer options and turn on debug so you can use odin...other option..I have heard of some doing this..go to Bestbuy Samsung counter..ask them if they have the odin tool. If they do they may be able to get you up and running.
FIREKAT V11/S5-V1
Don't worry bro.
Just follow this post to put your phone back to stock and get it rooted again. My phone used to brick and I went through it.
Follow the steps carefully, and you'll get your phone back.
http://forum.xda-developers.com/showthread.php?t=2559715
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button