Hello, first, sorry for my bad english too :\ i'm french
I'm posting this for a friend, unfortunately it is not good at phone and do not understand English. I therefore support myself (by teamviewer).
His phone was purchased in France, he received yesterday, phone clearly worked well, apart if I understand an error message: "Process.android.acore stopped." He tried to update it to Android 5.0.1 (by about => Update, and in my opinion, that's where the problems have begun, its connection is really not stable at all, she interrupted constantly and is also very very very slow, sometimes I wonder if it exceeds 50k / s ... He told me that during the update, he went to see his friends, ( + - 3h download ...) he put his phone on charge a few hours later, he returned home and the problems started and His phone was put out .. It no longer able to restart it.. told me there have no signs of life, here is what has been've already made.
-> Press VOL +, HOME and Power at the same time to get in recovery: No results
-> Press VOL -, HOME and Power at the same time to set download: No results
-> Remove the battery, sim and sd, and press 30sec Power: No results
-> He tested his battery on his brother's phone (also S4) it works, he tested his battery (his brother) in his phone: No results
Nothing appears on the phone, black screen and no LED ... I told him that his phone was probably a DOA (Dead On Arrival), however, I still tried to help because it m ' You said the phone will require three months to repair ..
After more research, I saw that his computer recognized the phone as Qualcomm HS-USB QDLoader 9008. The phone is completely bricked, can you provide me with the necessary files and tell me how I should proceed?
Thank you
If's a SAMSUNG GALAXY S4 I9505
I had the exact same problem with the pc only recognizing qualcomm...
I'm afraid to tell you that the partitions are probably corrupted i gave it to my provider back then which took them 2 weeks to repair i think they switched the so called emmc even though i had knox 0x1 and root so better send it back/ let the seller give it to repair because the waiting time was really killing me xD.
I saw tutorial like this http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830 and other to rebuild partition, i'm sure it's possible, but i need help ^^
This is about as bricked as it gets, and software likely isn't going to fix it. This same issue has happened on the Galaxy SII and they haven't found a solution after nearly four years of trying. The phone needs to be serviced.
Related
Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on, SE refuse
to help saying it is not released in the UK so i am not entitled to support.
I have not yet had a reply from where i got it from.
Is there any way to get this piece of junk going again?
Thanks.
Try to charge your battery on another phone / external charger.
I encountered a similar problem when trying to flash the X2. I received the UPDATED FAILED error, pulled out the battery, Volume Down + Power and gave it another try.
SEUS shouldn't brick your phone, maybe it's a problem with your battery.
The battery is at about 80%, i have tried it in my X1 as it is the same battery.
I tried the X1's battery in the X2 as well.
When i press the volume down and power buttons it vibrates for a fraction of a
second and then just stays on a black screen.
Let's try then a forced bootmode connection.
1. Insert the data cable into the phone without the battery plugged in.
2. Open SEUS and go to the connection screen.
3. While the software is searching for the phone, keep VOL DOWN + POWER and insert the battery.
After the phone vibrates, the software should recognize the X2.
This procedure generally applies to dead phones and sometimes works.
Post the result.
Still nothing, i kept the buttons pressed for about 30 seconds, then vista popped up a message 'usb device not recognised' the phone stayed as it did before and SEUS did nothing.
Sadly the support excuse they are using is what a lot of manufacturers do if you are in an area where they don't support it. This is the downside of buying a device on eBay etc. before it is "officially" released in your area. Contact the point of sale and hopefully they can send it in for you. You might have to pay shipping costs.
Leave your battery out and unplugged for an hour and then try again after that to revive it.
I did not even realise it had not been released in the UK, i got it from a UK website.
I am still waiting for them to get back to me, as it is Sunday they won't be getting back to me till Mon Tue i would think.
SE were fast though, less than an hour to reply, about the only credit they get though.
I have had the battery out for more than an hour a few times so that does not work.
Thanks for the suggestions though, keep em coming if there are any more.
WINE GLASS said:
Ok, so i got fed up with my phone freezing so i thought i would get SEUS to
re install the rom, (mr1, mr2 is not available to me yet).
The indicator got to about an inch along when a message popped up saying
update failed.
Now i cannot enter bootloader to try again, the phone will not turn on...
Click to expand...
Click to collapse
The exact same thing happened to me today, but I did not even get the update failed message (but I got the inch )
The phone is now bricked. No bootloader no nothing.
I guess you guys have the Singapore English versions? A lot of those retailers in the UK were getting them through Malaysia and so on. Then selling in the UK but not informing buyers that SE wont support it in the UK yet. It's really sad
It's a French X2, and I got it in France. I think I will have no issue with getting my X2 unbricked (or replaced), SE support is pretty good over here.
But if in the mean time someone has an idea or a trick on how to unbrick a X2 (other than the tips already listed in this thread), I would be happy to test it
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Wrong phone, wrong forum, wrong idea.
-kOS- said:
HI!!
I have a T3238+ with a K3 Proccessor, I flash it with a wrong ROM, when I try to reflash again the K3Aid tool display the following error message : "Read FTM State Error" after i click the download mode button, Anyone can help me??? thank you!!!
Click to expand...
Click to collapse
Learn to "Read" and use the "Search" function newb.
Hi!
This has happened to me also. The solution was to connect the original charger (I usually charge from the USB port on my PC).
Try this:
1. Disconnect all cables from phone.
2. Remove battery.
3. Insert battery.
4. Connect original SE charger and charge for 5 minutes.
5. With the charger still connected, press volume down and then power on simultaneously - hold until SE logo appears.
If not working, repeat from step 1 several times (i tried 3 times before it finally worked).
6. Connect PC USB and run SEUS update.
Seems to me like the phone does not always charg from USB, and that when it enters the "black-screen-after-short-vibration-after-power-on"-mode it does not charge while in this mode.
Mod edit: not rom dev related, moved to general
well... when it say update fail but if save the new rom to ur phone then its fine, take the battery out and restart ur phone.. it should load the new OS.. my one says fail everytime.. so no problem for me
The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.
frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?
R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.
peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.
@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App
peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.
Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App
Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.
The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.
I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.
Hi all,
after some time in trials to recover the dead LG G2 D802 it has become true. With help of another member of the xda forum I have succeeded to recover the phone. ... But strange things appear after that. The phone does not want to start from the Power-off/on button. Also I can not enter recovery by pressing VolDown+Power. The only thing I can do is to put in DownloadMode. I mean it react to pressing VolUp and plugging it to the PC. Then I can flash it with LG_Flash_Tool_2014 and after that the phone starts.
Then I am doing all the initial steps of setting the Android and it is working. I am testing the functionality of VolUp and VolDOwn buttons and seems that they are working fine.
If I am not turning the phone OFF all is fine. If I decide to turn it off (by PowerOff) it works a bit strange - when I pres it long it does not give me the options PowerOff, Reboot etc. , but just turn-off the phone.
Then no way to turn it ON again. The only way is to put it in download mode and to flash it again.
If it is powered-off and I put it on the charger it is charging normally and when reach 100% it show the picture on the screen. And that it is.
But no way to power it ON by button.
I hope someone could help with this symptoms.
How was your phone got bricked to go into only qdloader 9008? What were you flasng or what rom were you using?
The phone was bricked during flashing of update. Then I found the tread about No Download No Recovery etc. Via the test point I moved it to qdloader 9008. Then with some help and the program similar (or same I can't exactly remember) like BoardDiag3.99c we managed to upload the main parts from the OS and the soft in case to wake up the phone. Then the phone was able to go in Download Mode and using LG Flash Tool 2014 I have flashed the official FW for it (downloaded on my PC - D80220C_00.kdz). The phone is D802 (aftabalam8c2 asked me to dismount the board and to look on it to verify the model). On the box of the phone is written that it is 16G version 6WT. I checked and seems to be Taiwan version with open soft (no operator locked). Now the phone is working very good except the problem that the button Power OFF is not working. If I press it long it is not coming the menu "Power Off - Resrat - etc." but just the phone is turning off. Then the only thing is is able to do is to go on Download again. No Recovery, No simple turn ON. Then in download I can flash it again and then the soft turn it ON after the flash is done.
I made few trials with different FW for Taiwan/HonkKong (D80220C_00.kdz - 1,62 GB (1*743*288*886 bytes) and Hong Kong D80220C_00.kdz - 1,60 GB (1*723*173*312 bytes)) but the result is always the same.
Also I disconnected and checked the buttons. They are working fine - measured wirh Ohm meter on the connector.
Also I made few trials with another equipment - Octopus Box. It is possible not to flash the whole phone. In Octopus there is an option to read the NVRAM in DOwnload Mode. If I do it the the Octopus Soft after that turns / restarts the phone and it start in normal mode.
Unfortunately this friend does not remember what FW he was trying to flash when he got bricked. One time he told me he was trying to update the FW (OTA) after that he mentioned he was trying to flash another ROM. It was mess done 2,5 months ago, but just last week I was able to pay some attention to his phone.
I assumed it was OTA and downloaded the official FW according to the model, region and the memory.
The only difference was that during the qdloader 9008 mode the phone was flashed with files for (d802 32GB mbn) 32G version. Not 16G.
Regards
Maybe something got fried on the motherboard? Anyway here are the service manuals for G2 (not all model). I hope you could track what goes wrong from the power button with the help of the service manual. https://mega.co.nz/#F!HhhQiSqA!ESK4rT7LJB3MJCRJOU2GhQ
Thank you so much. I see there is a good diagram about the power and the TPs I need to check. Next days when I have a little free time will try to read and check according to the manual. I hope it could be repaired ... but despite my hope my logic whispers me that probably your suggestion is right - something got fried on the board.
If I find something which is reasonable will inform here.
Have a nice day
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402
Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me
Thanks, I'll give it a shot
ok let me know then
Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??
Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?
Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.