Lumia 1320 ENOSW RF INACTIVE ??? - XDA Assist

Hello everyone.
All over the internet, this problem is nowhere mentioned and i really hope to find a solution.
A customer delivered me this Nokia Lumia 1320.
It boots up with the Nokia logo, then it says:
ENOSW
RM994 3055.40000.9200.10517
345808 2013/11/20
RF INACTIVE
Customer assured me that nothing happened to the phone and nothing was done to the software.
I already gave the internal battery a full charge overnight with an external power supply.
if i try to do a full restore, it brings up the gears, restarts after 20 or 30 seconds with the same ENOSW message again.
Computer recognizes it, but the windows recovery tool ofcourse doesn't recognize it, also nokia care suite says it's an unsupported model.
Booting it up with powerbutton + vol up works with the lightning symbol, but then the computer doesn't recognize it all.
All this plus the fact that i really am not good with windows phones and the flashing of it.
Hopefully anyone has a solution, or knows what this message means?
Seems like some sort of test, but how to get rid of it and make this phone startup????
Any help is really greatly appriciated.
Kind regards,
Yves

Related

Windows Phone 7 Error Code: C101002E

I have been having this error where the phone prevents itself from booting, showing a screen that tells you to connect to PC , for a while. Only way to fix it is to remove the battery and restart but that is just a temporary fix. What exactly is this? What causes it? Is it a software issue or a hardware issue? Should I get an exchange or do you guys think this will be fixed with the next update?
Thanks
Never seen that error message. I'd say reset once, if you see it again, get it exchanged.
Yea this my 4th HD7 it shows the error code when you plug it to the PC in zune. Funny thing is that I owned a speck case and I reboot the phone in the case till then. This time i pulled the battery out, put it back in and powered the phone on without the case and it is working fine. I guess the case is pushing down a button or sth and that prevents the phone from working properly. Very weird..
Hey there! I've been having the same error! This is my 2nd HD7, I own the Speck case and I do not think its the case. This issue is happening on mine with or without the case. Pulling out the battery just doesn't cut it. I have to:
1. Remove the battery
2. Plug the USB Charger
3. Insert the battery back
4. Turn on.
I love the phone but this is really frustrating!
Edit: Too bad I can't post the link to youtube due to member status. But the video is up just search for it "c101002e"
Just happened to me too. First day using the Speck case too and i let the battery drain till it died and upon reboot it showed the 'plug into computer' screen. Hope it is just the case causing problems.
did you all updated the sd card ?
you could try to reflash this rom (if you are on t-mobile USA ) http://forum.xda-developers.com/showthread.php?t=810346
Take this one "RUU_Schubert_TMOUS_1.20.531.01_Radio_5.51.09.11a_2 2.31.50.09_Signed_SCHUBERT_RELEASE"
its just the stock tmous rom .
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
nrfitchett4 said:
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
Click to expand...
Click to collapse
somewhere on the board they did tell that this case make the buttons really sensitive and it make the phone unusable .
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
pierce_m said:
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
Click to expand...
Click to collapse
Yea that was pretty much what was happening to mine. Although I remember trying to boot it without the case and having the same error before so what I did that I did a hard reset ( press power and both volume buttons at the same time) then when the phone booted, I rebooted it without the case immediately and its been working no problem since. I am pretty sure that case pushes the camera button since it grips the phone very tightly. I even overloaded the ram by opening lots of apps that runs in the background and then rebooted but it is working perfectly fine as of right now. Weird.. I am guessing its just a weird bug not a hardware defect.
I found it in a post in the mozart forums, so i tried it, as you do, cause its something new to play with cause my TP2 didnt like swimming, but anyway it was something about hoding down the camera button while power on, and it brought up a picture of a phone and cable and instructing you to plug it into a pc and when i did it started Zune and something about restoration error, so like in the previous posts it may be a stuck or faulty button somewhere on the phone that is causing it.
i didnt watch the video so if that had it in it never mind
cheers
Today 11 April 2011 I got notification about NoDo update for my phone.
It is HTC Mozart on Orange France network.
The pre-NoDo update was istalled about 20 days before.
The update got stuck at step 8. It seemed I had an unusable phone. In a periodic reboot mode into the update screen.
I checked on my W7 64 bit laptop the relevant backup folder, where all my phone data was supposed to have gotten backed up during the update. The folder was empty.
I therefore realized my phone got its rom corrupted during the update and I could not get back my pre-NoDo backup, since this latter was missing from my laptop.
Zune was on no help, stating a C101002E error.
The Windows Phone Support Tool was also of no use, reporting an error code while trying to restore my data.
XDA-forum provided me with a solution:
I went here
http://forum.xda-developers.com/showthread.php?t=1000781
and downloaded both bootloaders with relative roms.
After getting into the bootloader screen (red, green and blue screen), I installed the first ROM provided by Ansar. This could not install succesfully.
With the bootloader tool I could nevertheless confirm my idea I did not have anymore a functioning rom into my phone.
The second rom, the one ending with "Signed_by_ansar" could be succesfully installed.
I now have a Mozart fully functioning.
I had to restore my windows live account, Gmail, etc. My apps did not come back up after syncing with Zune.
I realized I just lost all my SMSs and home screen settings.
My phone was originally network unlocked and remained as such.
I got a notification that there is an official update for my phone the first time I rebooted. I will wait before attempting this update. The ROM by Ansar has got anyway copy/paste, being a NoDo ROM.
The ROM from Ansar, although for Orange France, removes the Orange splash screen when the phone starts. I guess if I need to use warranty on this phone right now I may have some issues with Orange France. Maybe when I update the phone following the update notification I got, I will re-establish a fully certified Orange ROM.
i9o pls and any one pls help me , i faced problem with [260] connection problem between my hd7 and pc vista 64 bit, actually i followed to steps in forum (error code C101002E) and drivers were installed (htc usb sync) before i started to flash rom NoDo bootloader 1, But no way still the problem [260]. i also tried another RUU htc asia xxx707xxx. because i have spl 1.23.2250.0(112138).also some links of RUU to download signed by ansar disappeared in rapid and other sourses, pls help to solve connection problem
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
WPS doesnt help in my case, Im malaysian and thought that need Asia RUU, but when i tried Europian RUU it nicely works, maybe because of i have 8G phone. the RRU is RUU_Schubert_HTC_Europe_1.69.401.01_Radio_5.54.09.21_22.33b.50.10_Signed_SCHUBERT_RELEASE(2)
day2die said:
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
Click to expand...
Click to collapse
Do you know what this tool does to the computer?
I would try it but honestly don't want to do it before I have info what it does to my PC settings. Unfortunately MS doesn't share with this knowledge.
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
MusicMan587 said:
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
Click to expand...
Click to collapse
No one had this problem? am i the only unlucky on the earth!?
Return for warranty replacement. Your phone is broken.
Thank you...i hoped i could solve it to not to wait september to have my phone back.

SE x10 mini pro hard brick

Hi guys, i just wanted to unlock my phone's bootloader when my computer was suddenly getting 'blue death'. My phone turned off, I tried to turn it on but nothing happened. After that I found some fixing method like SEUS, Flashtool (installed drivers to recognize my phone..), but im still bricked 'cos none of these programs can recognize my phone. When programs say 'turn off phone - hold back key - plug in usb' i get nothing, i mean i know what is flash mode (with the green led) but i cant get into it. I've tried all buttons on the phone (even combos like - power button & back) but noting. When i plug in the charger the led isnt light. Please help me i want my phone back. - and sorry for my english
Same problem: Hard bricked x10 mini pro
I have exactly the same problem as you.
I have had no success in finding a solution, because the phone cannot enter flash mode. There are absolutely no signs of life in the phone even though bootloader unlock was reported as successful.
Any ideas guys? Or can you recommend a decent, trustworthy repairer?
Cheers

			
				
the only one here with any inkling of a solution
if i am not mistaken, the only way to solve this problem is to J-tag your phone.
basically, what that means is you take your phone to a repair shop, they take apart your phone and plug in a chip which enables certain debugging features, and they simply re-flash your phone for you.
however, unless you are willing to buy a J-tag board yourself, you need to pay 20+$CAD for this.
After all, they need to make money too..

[Q] Super Bricked O3D, Dead No POWER & Not Responding

My phone is dead after switching external sd with internal sd via CWM script .zip file and a little tinkering in the phones system files.
(“I have done this before with success but had just flashed new firmware, and in the rush I was in wile doing it I obviously did something majorly wrong and super bricked my phone”)
After rebooting to complete a step I was doing, the phone did not turn back on, the pc does not detect it properly anymore, no button combinations work, such as pressing vol up when connected without battery, power button and pressing up + vol. No RESPONSE:.
when plugged into the pc it just flashes "OMAP4430 device" but appears and disappears all the time in device manager, now I know all drivers are correct and how to go into download mode, recovery mode and every trick you can with the O3D but none work anymore, phone does not turn on and it only recognizes it for a second showing “OMAP4430 device”.
PS Sorry for the new thread but I have searched the forum and the internet with no real answers, it would be great if there’s a fix for this situation or is my O3D dead to the world never again to be reborn.
NOW IF ANY ONE HAS MANAGED TO FIX A TRULY BRICKE O3D LIKE MINE PLEASE HELP!!!!!!!​
sounds like a harware brick i did that to my thrill had to take it in
That’s what I’ve been fearing, my other issue is that the phone is actually a LG thrill from at&t I just call it a O3D because in Australia were I live we only have O3D, and let’s face it they are basically identical, any way would that mean I would have to send it back to the USA for repair?
well is it under warenty? if so youll have to send it to who ever you bought it from. if it isent ull have to get a new logic board and relace it your self or have some one relace it. or send it to lg to fix it
I had a similar problem when installing rom. KDZ:
http://forum.xda-developers.com/showthread.php?t=1473781
http://forum.xda-developers.com/showthread.php?t=1244490
The problem with "OMAP4430" device I solved by connecting the phone to the computer via a cable from HTC Wildfire (such problems I had with the original cable, LG).
It can change the cable will solve the problem.
I wish you luck.
(google translate)
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
trust me i totaly bricked my phone i tryed every trick pulling the battery out and putting it in in download mode problem was omap didnt even show up just the other one and it would flash on and off way to fast to click on it in device manager then it would just stop.
So did you end up taking it in?, it should still be under manufacture warranty well hopefully I got it in october and I don’t even think the O3D has been out for a year yet.
defcomg said:
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
Click to expand...
Click to collapse
The problem is that it only starts flashing with the battery removed so, and I can’t get into download mode at all, which is when it normally stays there and detects it properly, otherwise the drivers are all installed.
If it flashes omap its not a complete brick. If all fails try the resistor cable. You can find a post around in the forum
I have tried the resistor cable using 910k resistor, and I even checked it on the multimeter and it reads 908k resistance which should be ok since I think you can allow for a 1% difference.
I could figure out that ur device can be detected as OMAP, this means it isn't bricked totally, please be sure U remove UR battery, connect ur USB--phone side, then press volume up and insert the USB--pc side while pressing the button and continue pressing while ur pc is installing, first it will show OMAP, then after 10-20 sec it will show COM added, don't stop pressing until it finds the COM and installs it, then directly stop pressing and insert battery and don't try to turn it on and start flashing as usual
try to use other USB cable model like sony ericsson, it never failed me
hoping U will be lucky
See the problem is that no button combination work on the phone, pressing a button is like talking to a wall you get no response lol.
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
cephasara said:
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
Click to expand...
Click to collapse
its hardware bricked need a new logic board sorry to say
Hi, i had the same problem while upgrading to gingerbread. What windows version are you running? Ihad the same problem using win 7 x64. Got to a win xp computer with no lg software installed and used the tutorial of unbrick from this forum. had to try several times, but at least step by step my phone got back to life. Main thing is to get omap drivers installed on XP with no battery. Then taking the other steps mentionened under unbricking your phone in this forum.
Hope it helps
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
KurdX said:
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
Click to expand...
Click to collapse
So let me get this straight. Like a few months ago, there was a way to completely destroy your phone:
install CWM and run an OTA update on stock rom.
That completely ruined my phone. It was explicitly said that no unbrick method is available.
Now I hear several people reporting yet another unfixable brick, caused by
- Erasing your SD card through cyanogenmod
- Formatting /data ?
All the available methods of unbricking are said not to work. And by those methods I mean
- Opening recovery and do a factory reset (recovery can't be opened I heard?)
- Connecting to a Windows 7 PC with battery out and volUp depressed (device disappearing reappearing)
- Connecting to a Windows XP computer With battery out, volup depressed (Same problem as Windows 7?)
So to put it simple:
Doing some things with CWM OR CyanogenMod can render your phone unfixably bricked. There is a genuine risk in hard bricking your phone when you have CWM and/or Cyanogenmod installed.
I'm not going to install either of those for that very reason.
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
thealgorithm said:
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
Click to expand...
Click to collapse
They said that the omap driver keeps appearing and disappearing. You can't do anything if a driver does that!
Sent from my LG-P920 using XDA

[Q] Pioneer R1 Tablet not rooted and wont load past the animated logo

Hello,
My Pioneer R1 tablet the other night decided to do an automatic upgrade when booting up and hung for hours on 14 of 18 files updated. I rebooted the tablet for it to get to the home screen but come up with the error android phone services not initinalized and then froze. so rebooted and it got to the animated pioneer logo and just sits there never loading fully. Pioneer customer support sucks with helping and the tablet has a reset button on the back in a pin hole. I pressed that the tablet turns off. The tablet still stuck on animated logo.The tablet was running stock jellybean 4.2. The Pioneer people didnt want to do any troubleshooting. told me to send it to them to fix and that if they found anything wrong other than hardware issue i am liable for the charges on to of the shipping cost. I dont have money to just hand out to people who dont have a system setup for troubleshooting. Sorry for a long story but my question is is there anyone who can help me fix this issue.
Unfortunately I'm stuck with the same issue, tablet was running slow so I rebooted it, got hit with their "system breaking update"
Spent a better part of the day trying to find a way to reboot it into recovery mode and wipe user data/reinstall but so far no luck.
Fired off a email to support, tried calling but the wait time was 54mins last time I called.
Also there is a automated announcement while waiting for call time informing everyone that they "are aware of a problem with the tablet"
If I manage to get it into recovery and fix this I will let you know how
so after further testing :
holding reset for 30 seconds: fail
holding power for 10 seconds: fail
holding power for 1 min: fail
holding reset and then power:fail
power then reset:fail
opening case to disconnect battery; FAIL soldered to the board/battery wtf ?
pinhole on bottom of case between usb and power port doesnt sync up with a reboot option
ro0ks said:
so after further testing :
holding reset for 30 seconds: fail
holding power for 10 seconds: fail
holding power for 1 min: fail
holding reset and then power:fail
power then reset:fail
opening case to disconnect battery; FAIL soldered to the board/battery wtf ?
pinhole on bottom of case between usb and power port doesnt sync up with a reboot option
Click to expand...
Click to collapse
ok well this was an counterproductive day
called Cs @ 1-800-421-1404
waited 45mins on a "20min" wait
talked to someone who informed me this was the wrong number to call for help with the tablet
called Cs @ 1-888-999-0987
"we are experiencing a high call volume at this time, leave your name # and model number and we will return your call before the end of the business day"
waited until 3pm and called again finally got to talk to someone and it was horrible
I was initially told to press the reset button on the back, when I informed them that was not the issue. I was told to email [email protected] and detail my problem, after around 10mins of this, I was put on hold where 3 different ppl picked up and re-asked my problem. Finally when I asked to speak with a supervisor I was told he wasn't there.
When I explained that this is not uncommon in tablet from time to time, ppl forget what they used as a lock code, or one of their children played with it and put a passcode on the device. I was informed that they cant give me any further information because pioneer hired them to field tech support questions and they aren't part of pioneer. The whole reason they cant just tell me how to boot the device into recovery is they dont know, you see pioneer failed to give them that crucial piece of information.
supervisor is supposed to be calling me back tomorrow so lets see what kind of bs this is.
more then likely I will be de-soldering the battery leads from the board to force it into recovery tomorrow afternoon/
only thing I've found out so far thru trial and error is :
power on ,hold power till first logo, press reset and hold. 3-5 seconds later screen flashes white once (either turning on or off)
tablet off, insert usb connected to pc, rapidly tap power and it will stay on the charging screen , pc then recognizes device as libusb-win32 device "Worldcup device"
still no recovery mode
ESI is actually responsible for the tablet as pioneer leased out their logo for the tablet.
This is why there is a ridiculous run around trying to get help from pioneer's cs reps,ESI got my problem sorted.
look for a stock rom dump soon.
so what files would be needed exactly....
so far I have :
aml_logo.img
boot.img
bootloader.img
cache.ext4.tar
data.ext4.tar
logo.img
recovery.img
and still have to copy over system.ext4.tar
packaged rom file!
ok so after following this thread :http://forum.xda-developers.com/showthread.php?t=2195858
I ended up with this Pioneer r1 stock rom , anyone who has a stuck pioneer want to try ?
ro0ks99 said:
ESI is actually responsible for the tablet as pioneer leased out their logo for the tablet.
This is why there is a ridiculous run around trying to get help from pioneer's cs reps,ESI got my problem sorted.
look for a stock rom dump soon.
Click to expand...
Click to collapse
Hi, can you tell me how you solved the password issue and not able to get to factory reset. thank you.
There is no recovery mode , need to return tablet to ESI
ro0ks99 said:
There is no recovery mode , need to return tablet to ESI
Click to expand...
Click to collapse
I've been doing some searching myself, since I've got a soft-bricked R1 (Father-in-Law didn't want it any more), and from the looks of it, reflashing AML8726-based tablets is done via a rescue-SD card, or using a manufacturer produced USB burning tool:
http://www.slatedroid.com/topic/41478-how-to-unbrick-your-amlogic-aml8726-mx-series-tablet-v20/
So it appears that the tools are out there, but I haven't had any luck finding the device-specific files that will help.
I don't suppose you manged to find a way to contact ESI's technicians without going through the support number?
There is a recovery mode i unbricked mine just a few day ago need help finishing it it's very unstable
Sent from my SM-N900T using XDA Free mobile app
Could sort of get mine to boot...
My r1 crashed while watching a video and when I tried to restart it was stuck on this pioneer loading screen. I noticed if i let the battery run all the way out I could then get it to load up... but was greeted with dozens of error messages. This program has stopped this program has stopped. Every two seconds another error so trying to get on to google play for a scandisk app was pointless. I chose to restart and... back to Pioneer loading screen :/
Anyone ever locate a stock recovery flash for this tablet? TBT-7R1-P can be flashed via adb and ImageBurnTool. I have 2 tablets that 1, I do have CWM installed but need to connect a mouse to navigate (using a usb mouse plugged inthru an OTC cable) and nothing to restore since I'd wiped it.

Please help, really need it... bootloop

Basically what is now my phone is catch and display the image of "WARNING; BOOTLOADER UNLOCKED" and it restarts constantly, only to arrive there and restart again... like a "bootlop"
GOOGLE SEARCH FOR ALL SOLUTION IN FORUMS IN ENGLISH AND SPANISH, no case ...
Apparently my mistake was to install an official ROM on my device MOTOROLA using fastboot way...
It do not recognize charger or usb, I can enter the bootloader menu (which lets you choose factory normal startup, recovery ... you know which one) but by choosing an option that quickly returns to the same pattern discussed above (I select, and automatically jumps screen "warning, bootloader unlocked" and restarted to reach this constantly ..)
Do not recognize the USB or charger by simple selection, because I could not turn off the phone because they did not respond to any command, even if i use physical buttons, and obviusly i dont have acces to digital buttons...... .
However I can go to the "Fastboot" where would the bootloader menu, and there does not even recognize the charger or usb mode ...
is not recognized by selection, not because my port is broken or something, because I notice it because I could not do anything, IT WAS CONSTANTLY RESET DURING HOURS, overheating to the point it ran out of battery and I connect ... and I get the typical image of charging (battery symbol with 0%) and a second later (1% estimate when loading ...) happens again, without notice or other visually perceptible signal it restarts and does Just what i explain in the beginning ....
it doesnt recognize usb or charger... even when restarting or fastboot or bootloader mode menu NOT ACKNOWLEDGE DECIDES NOT RECOGNIZE IT, THE USB PORT ISNT NOT DAMAGED ...
I wonder if anyone could come up with the solution to have had this problem since I see that I'm the first to commit such stupidity to install an official rom via fastboot .....
And I can not find anyone with the same problem as me, nor the solution, even after having googled quite ..
could anyone tell me more or less to do?
not recognize in any way the usb connection, and the charger all ...
so it seems that the phone is broken? I doubt they can give you something that you can only destroy via software, although it is not impossible ... i didnt did so much, i just install something that i shouldnt.. should be any fix for it, and i must not be the first having this problem!
I hope you can help me, since the phone is relatively new and is to me a shame to pay now AR$4500 (1 usd = 8,50 AR$ ) i live in argentina, third world, thats why the price is high... and why i dont talk english so good, but i really really need help...
or in order to have another decent phone i will need to pay a high amount of money... hope you can help me, i know in this forum you can find very smart and helpfull people, youre my last chance
regards from argentina...

Categories

Resources