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.
A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.
Tried ZUI QPST image or CM one?
ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.
ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM
kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?
ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?
ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.
ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
What error show miflash when you try to flash in edl mode?
balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way
ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply
kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!
Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience
Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Hi!
As in the title, something wrong with my P9 Lite happened. Namely, the day before yesterday he decided to turn off by himself with a 50% battery there, but turned on normally after 2minutes. At night from Wednesday to Thursday it discharged and in the morning after charging I couldn`t start it.
The phone either booted and stopped several times on the Huawei logo and the note "Powered by Android". I can enter by using a key combination the eRecovery mode. Ultimately, it started up one time, and it worked until the evening and until it was discharged again. After that it has been charged to 60%, one time he turned on but after an hour of further charging he fell on the amen. I've been trying to fight him since the morning that maybe he'll turn on like yesterday, but no. I had this situation for the first time in August 2018, then in February and July 2019 with that it was probably a decent brick then, because this black screen was constantly displayed with an exclamation mark and some error. A visit in smartphone service has always helped, but I can't spend 80 PLN again to fix that issue. After the repair in July, I specially wrote the system version so that I would have knowledge for the future in the event of a repeat. The phone had the firmware as below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Today I downloaded the system from this link: huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9618
However, at 5% installation the error crashes and I can only restart the phone. I tried using two different sd cards, so the option of the card being faulty is 99% out of the question. I hope that some good soul will help me, because I believe that I can solve this problem independently at home and not necessarily after paying with a GSM spec. : P
I forgot to add that the phone has not been updated since it was repaired or anything. I didn't do any treatments myself with loading custom systems. He just turned himself off, without any previous signs of malfunction and end. I was surprised that the phone doesn`t want to accept the software that was uploaded by a service technician ... but maybe I am doing something wrong.
At the end fastboot situation:
PHONE: unlocked
FRP: locked
EDIT:
In another forum I got instructions to upload rollback and then soft "C432B160" and everything will be good. I took it up and the rollback installation was completed, after a minute the phone rebooted. Unfortunately, this problem caused another problem, because since I installed rollback I can`t enter the erecovery mode, where I have possibility to shut down...so phone stuck with the Huawei logo all the time. I was supposed to upload this software, but I had to leave the house and the phone was completely discharged when I returned. From that moment only fastboot mode starts, or after switching on and trying with different phone buttons, it always becomes a logo and got freezed. I was charging it for an hour, but after disconnecting from the charger the LED was blinking red and I saw on the screen message about 0% battery. After that another situation...I connected it to the charger and after a second showed me message of 100% battery, but after a second phone started automatically and hung on the logo again. After unplugging it from charger and trying to start without charging, the LED flashes red and message about disscharge was on the screen. Now I`m seriously starting to wonder, if anything from this phone will still be..... :/
Links to rollback and software (according to which I did not manage to upload before discharging the phone):
http://download-c1.huawei.com/downlo...00&siteCode=pl
http://huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9571
Nicramcio said:
Hi!
As in the title, something wrong with my P9 Lite happened.
Namely, the day before yesterday he decided to turn off by himself with a 50% battery there, but turned on normally after 2minutes. At night from Wednesday to Thursday it discharged and in the morning after charging I couldn`t start it.
The phone either booted and stopped several times on the Huawei logo and the note "Powered by Android". I can enter by using a key combination the eRecovery mode. Ultimately, it started up one time, and it worked until the evening and until it was discharged again. After that it has been charged to 60%, one time he turned on but after an hour of further charging he fell on the amen. I've been trying to fight him since the morning that maybe he'll turn on like yesterday, but no. I had this situation for the first time in August 2018, then in February and July 2019 with that it was probably a decent brick then, because this black screen was constantly displayed with an exclamation mark and some error. A visit in smartphone service has always helped, but I can't spend 80 PLN again to fix that issue. After the repair in July, I specially wrote the system version so that I would have knowledge for the future in the event of a repeat. The phone had the firmware as below:
Today I downloaded the system from this link: huawei-firmware.com/rom/huawei-p9-lite/vns-l21/9618
However, at 5% installation the error crashes and I can only restart the phone. I tried using two different sd cards, so the option of the card being faulty is 99% out of the question. I hope that some good soul will help me, because I believe that I can solve this problem independently at home and not necessarily after paying with a GSM spec. : P
I forgot to add that the phone has not been updated since it was repaired or anything. I didn't do any treatments myself with loading custom systems. He just turned himself off, without any previous signs of malfunction and end. I was surprised that the phone doesn`t want to accept the software that was uploaded by a service technician ... but maybe I am doing something wrong.
At the end fastboot situation:
PHONE: unlocked
FRP: locked
EDIT:
In another forum I got instructions to upload rollback and then soft "C432B160" and everything will be good. I took it up and the rollback installation was completed, after a minute the phone rebooted. Unfortunately, this problem caused another problem, because since I installed rollback I can`t enter the erecovery mode, where I have possibility to shut down...so phone stuck with the Huawei logo all the time. I was supposed to upload this software, but I had to leave the house and the phone was completely discharged when I returned. From that moment only fastboot mode starts, or after switching on and trying with different phone buttons, it always becomes a logo and got freezed. I was charging it for an hour, but after disconnecting from the charger the LED was blinking red and I saw on the screen message about 0% battery. After that another situation...I connected it to the charger and after a second showed me message of 100% battery, but after a second phone started automatically and hung on the logo again. After unplugging it from charger and trying to start without charging, the LED flashes red and message about disscharge was on the screen. Now I`m seriously starting to wonder, if anything from this phone will still be..... :/
Links to rollback and software (according to which I did not manage to upload before discharging the phone):
http://download-c1.huawei.com/downlo...00&siteCode=pl
http://huawei-firmware.com/rom/huaw...
Your device is natively single or dual sim ?
Click to expand...
Click to collapse
Dadditz said:
Hey dude, let me know if i understood well...
Your device won't boot up anymore, isn't it ?
VNS-L21C432B120 ?? It's one of the oldest firmware you can have..
I really don't know if i can help, but if you agree we can give a try..
Your device is natively single or dual sim ?
Click to expand...
Click to collapse
Yas, my device won`t boot up since 1st of July and I don`t know why...because I don`t tried to update firmware, unlock bootloader etc.
I know that, but year ago I have a same problem and GSM service installed that soft.
My device is dual sim.
Thanks for help!
Nicramcio said:
Yas, my device won`t boot up since 1st of July and I don`t know why...because I don`t tried to update firmware, unlock bootloader etc.
I know that, but year ago I have a same problem and GSM service installed that soft.
My device is dual sim.
Thanks for help!
Click to expand...
Click to collapse
Ok let's go..
Take a working (at least 4gb) SD,
move away all your stuff then format it as FAT32.
Download this >> update.zip << file (VNS-L21C432B160/dual sim).
Unzip it, you find UPDATE.APP file.
Turn off the phone.
On your PC create a folder and rename it DLOAD.
Copy/paste (only) UPDATE.APP file into DLOAD folder
and put it into SD, then insert the SD into your device.
Turn the device on keeping vol+ & vol- then power button
all together till an update screen appears.
Ok, release now the buttons...
After the flashing process, your device should reboot to system.
If passes over 15 mins, reboot into the e-recovery
(press vol+ & power button) and do a factory reset + wipe cache.
Done !!
NOTE: the firmwrare link is taken using Firmware Finder repo,
all credits go to this fantastic app team/users that created it.
Dadditz said:
Ok let's go..
Take a working (at least 4gb) SD,
move away all your stuff then format it as FAT32.
Download this >> update.zip << file (VNS-L21C432B160/dual sim).
Unzip it, you find UPDATE.APP file.
Turn off the phone.
On your PC create a folder and rename it DLOAD.
Copy/paste (only) UPDATE.APP file into DLOAD folder
and put it into SD, then insert the SD into your device.
Turn the device on keeping vol+ & vol- then power button
all together till an update screen appears.
Ok, release now the buttons...
After the flashing process, your device should reboot to system.
If passes over 15 mins, reboot into the e-recovery
(press vol+ & power button) and do a factory reset + wipe cache.
Done !!
NOTE: the firmwrare link is taken using Firmware Finder repo,
all credits go to this fantastic app team/users that created it.
Click to expand...
Click to collapse
Thank you, but I tried to install by dload method some kind of softwares B120,130,150,160 if I remember...but no effects. In other forum, they said that I need to install rollback, and after that firmware B160. Ok, I installed rollback perfectly but after that I can`t go to erecovery mode...only fastboot is avaliable and whene I turn on phone it would stuck on Huawei logo. Now it`s discharged and i don`t have any idea how can i charged it to over 30% of battery.
Nicramcio said:
Thank you, but I tried to install by dload method some kind of softwares B120,130,150,160 if I remember...but no effects. In other forum, they said that I need to install rollback, and after that firmware B160. Ok, I installed rollback perfectly but after that I can`t go to erecovery mode...only fastboot is avaliable and whene I turn on phone it would stuck on Huawei logo. Now it`s discharged and i don`t have any idea how can i charged it to over 30% of battery.
Click to expand...
Click to collapse
Dude if there is some hardware problem
it will be a little difficult to recover..
so when you bringed it to service have they replaced the motherboard?
If not you may still have hardware problems, but let's keep this aside ...
Try again what i wrote..
In the meantime I give you the correct rollback link, maybe you used the wrong one.
Dude, the rollback package is used only to revert from android 7 to android 6.
In order to unbrick the device, in android 6 environment, dload method is enough..
Visit the UNIFIED HELP THREAD, post #6, see by yourself..
Dadditz said:
Dude if there is some hardware problem
it will be a little difficult to recover..
so when you bringed it to service have they replaced the motherboard?
If not you may still have hardware problems, but let's keep this aside ...
Try again what i wrote..
In the meantime I give you the correct rollback link, maybe you used the wrong one.
Dude, the rollback package is used only to revert from android 7 to android 6.
In order to unbrick the device, in android 6 environment, dload method is enough..
Visit the UNIFIED HELP THREAD, post #6, see by yourself..
Click to expand...
Click to collapse
I know it`s some kind of big problem.
3 times it was unbricked in service, but that is non authorized and they don`t do anything with motherboard...only installed me somehow new software for money circa 20 USD/EUR.
Okay i`ll try that tomorow and show results. I keep my fingers crossed, that my Huawei tomorow boot normal.
Nicramcio said:
I know it`s some kind of big problem.
3 times it was unbricked in service, but that is non authorized and they don`t do anything with motherboard...only installed me somehow new software for money circa 20 USD/EUR.
Okay i`ll try that tomorow and show results. I keep my fingers crossed, that my Huawei tomorow boot normal.
Click to expand...
Click to collapse
Sorry, i forgot to add the LINK to correct rollback package,
here you are..
Cheers
Edit: next time, maybe tomorrow i will post how to extract
firmware (BOOT,RECOVERY,SYSTEM) from UPDATE.APP
and how to flash it via fastboot commands.
Dadditz said:
Sorry, i forgot to add the LINK to correct rollback package,
here you are..
Cheers
Edit: next time, maybe tomorrow i will post how to extract
firmware (BOOT,RECOVERY,SYSTEM) from UPDATE.APP
and how to flash it via fastboot commands.
Click to expand...
Click to collapse
I don`t have time to do something with my bricked phone over a week, but today I tried to install software B160 and rollback by dload mode. It didn`t work. I can`t charge my phone over 30% of battery, and when I plug off the charger, phone have probably not enough battery to turn software installation. Also when I tried to hold 3 buttons, and then connected the charger cable...the installation didn`t start. So I think, that you must tell me how to flash soft via fastboot commands...because this is the only one mode that I can turn on my phone. I feel completely helpless, because today my replacement phone broke...so I have to bring Huawei back to life.
EDIT:
I forgot to mentioned...When i hold 3 buttons to start installation process phone vibrate one, then shown red lightning sign that battery is empty, and LED flashed 3 times red...then screen go black and device is powered off...nothing else. Also I tried 4 different SD cards, so I think now the problem with dload mode is that phone is not charged over 30 or 50% (I don`t remeber that) of battery what is required to start the installation process.
Also when I try to charge it, only LED flashes red all the time and on the screen I don`t have information that phone is charging.
Nicramcio said:
I don`t have time to do something with my bricked phone over a week, but today I tried to install software B160 and rollback by dload mode. It didn`t work. I can`t charge my phone over 30% of battery, and when I plug off the charger, phone have probably not enough battery to turn software installation. Also when I tried to hold 3 buttons, and then connected the charger cable...the installation didn`t start. So I think, that you must tell me how to flash soft via fastboot commands...because this is the only one mode that I can turn on my phone. I feel completely helpless, because today my replacement phone broke...so I have to bring Huawei back to life.
EDIT:
I forgot to mentioned...When i hold 3 buttons to start installation process phone vibrate one, then shown red lightning sign that battery is empty, and LED flashed 3 times red...then screen go black and device is powered off...nothing else. Also I tried 4 different SD cards, so I think now the problem with dload mode is that phone is not charged over 30 or 50% (I don`t remeber that) of battery what is required to start the installation process.
Also when I try to charge it, only LED flashes red all the time and on the screen I don`t have information that phone is charging.
Click to expand...
Click to collapse
Hi dude,
I suspect your device has some serious hardware problem.
If the device has fallen off, it may have broken or unstuck / unsoldered something,
hence the need for a check by specialized technicians / service point.
I suggest, if you have the possibility,
to replace the device with a new or even used one,
functioning and a little more updated / upgradeable.
But trying won't cost anything, so let's do it !!!
Make sure you have minimal adb & fastboot
or a complete platform-tools (link in the same page / it's your choise)
and huawei drivers /HiSuite on your PC,
then in fastboot mode do the command > fastboot devices.
If you have a response like > numbers/letters........device <
then you're ok to go, otherwise it means your PC don't "see" your phone...
From XDA download Huawei Update Extractor and use it
to extract BOOT.img, RECOVERY.img (not RECOVERY2.img)
and SYSTEM.img from your UPDATE.APP file
you extracted from update.zip...(see attachment)
Put those three files into a folder and rename it as you want
(maybe the same where you extracted UPDATE.APP),
then tap in the folder address bar (see attachment) and type cmd then hit enter.
A command window will appears, now you're ready to flash.
In order type following commands:
1 - fastboot flash boot BOOT.img; (let it flash)
2 - fastboot flash recovery RECOVERY.img; (let it flash)
3 - fastboot flash system SYSTEM.img; (let it flash)
Once finished type > fastboot reboot and cross your fingers...
If all will take right direction your device will reboot correctly,
otherwise (if passes over 15 mins) reboot recovery (vol+ & power buttons)
and do a factory reset..
Hope sincerely it will boot up... :angel:
P.S.: I don't know why i can't post jpg directly, so i zipped into one file...
Dadditz said:
Hi dude,
I suspect your device has some serious hardware problem.
If the device has fallen off, it may have broken or unstuck / unsoldered something,
hence the need for a check by specialized technicians / service point.
I suggest, if you have the possibility,
to replace the device with a new or even used one,
functioning and a little more updated / upgradeable.
But trying won't cost anything, so let's do it !!!
Make sure you have minimal adb & fastboot
or a complete platform-tools (link in the same page / it's your choise)
and huawei drivers /HiSuite on your PC,
then in fastboot mode do the command > fastboot devices.
If you have a response like > numbers/letters........device <
then you're ok to go, otherwise it means your PC don't "see" your phone...
From XDA download Huawei Update Extractor and use it
to extract BOOT.img, RECOVERY.img (not RECOVERY2.img)
and SYSTEM.img from your UPDATE.APP file
you extracted from update.zip...(see attachment)
Put those three files into a folder and rename it as you want
(maybe the same where you extracted UPDATE.APP),
then tap in the folder address bar (see attachment) and type cmd then hit enter.
A command window will appears, now you're ready to flash.
In order type following commands:
1 - fastboot flash boot BOOT.img; (let it flash)
2 - fastboot flash recovery RECOVERY.img; (let it flash)
3 - fastboot flash system SYSTEM.img; (let it flash)
Once finished type > fastboot reboot and cross your fingers...
If all will take right direction your device will reboot correctly,
otherwise (if passes over 15 mins) reboot recovery (vol+ & power buttons)
and do a factory reset..
Hope sincerely it will boot up... :angel:
P.S.: I don't know why i can't post jpg directly, so i zipped into one file...
Click to expand...
Click to collapse
Oh men i appriciate that you wrote everything. Only one problem, I can`t download the zipped file. :/ Also I keep in mind another type of solution for my Huawei, but more on that later. Now I gonna try to flash software by fastboot my hero.
EDIT: beginning gone well
EDIT2: commands not work properly. I done everything like you told me, but you can see error in cmd (cmd is enabled as administrator).
I download adb from this tutorial:
https://www.youtube.com/watch?v=OKRTbv-6Kzc
because previous didn`t work.
As you can see I typed "fastboot flash boot BOOT.img" as you told me, but I get info FAILED. :/
Searched for information and I found, that I need to unlock bootloader once again...and after that every command should work.
Nicramcio said:
I download adb from this tutorial:
https://www.youtube.com/watch?v=OKRTbv-6Kzc
because previous didn`t work.
As you can see I typed "fastboot flash boot BOOT.img" as you told me, but I get info FAILED. :/
Searched for information and I found, that I need to unlock bootloader once again...and after that every command should work.
Click to expand...
Click to collapse
Good work dude.
I previously readed on your post
phone = unlocked
frp = locked
i was thinking you was ready to flash
but evidently that was not correct...
For some unknown reason i cannot post
screenshots so i decided to add them on postimage...
As you can see they are quite same as yours...
https://i.postimg.cc/fTNZvWY9/VNS-L21-C432-B160.jpg
https://i.postimg.cc/x1s2YKhv/Extractor-select-your-update-app-file.jpg
https://i.postimg.cc/5t6MtXWZ/extract-BOOT-RECOVERY-SYSTEM.jpg
https://i.postimg.cc/LswFgmHh/open-command-window2.jpg
Let me know how the work goes on ...
Cheers
Dadditz said:
Good work dude.
I previously readed on your post
phone = unlocked
frp = locked
i was thinking you was ready to flash
but evidently that was not correct...
For some unknown reason i cannot post
screenshots so i decided to add them on postimage...
As you can see they are quite same as yours...
https://i.postimg.cc/fTNZvWY9/VNS-L21-C432-B160.jpg
https://i.postimg.cc/x1s2YKhv/Extractor-select-your-update-app-file.jpg
https://i.postimg.cc/5t6MtXWZ/extract-BOOT-RECOVERY-SYSTEM.jpg
https://i.postimg.cc/LswFgmHh/open-command-window2.jpg
Let me know how the work goes on ...
Cheers
Click to expand...
Click to collapse
Grazie molto!
I done everything with software, step by step just like in your images...
...but again no working commands.
I`ve got only info in CMD that FAILED (remote: Command not allowed).
In other threads I menaged to get info that,
if phone has never been rooted and get custom ROM the bootloader is not unlocked and I need to relock it.
The threads are old and then you have to get a special code from Huawei site,
and then tap fastboot oem unlock "special number" or something like that.
Now I don`t know how to get that code and is there any way to try unlock bootloader and take a step forward?
Yas, we done step forward tomorrow because we know that PC see my device correctly,
we have good firmware but CMD commands caused another problem. :/
Nicramcio said:
Grazie molto!
I done everything with software, step by step just like in your images...
...but again no working commands.
I`ve got only info in CMD that FAILED (remote: Command not allowed).
In other threads I menaged to get info that,
if phone has never been rooted and get custom ROM the bootloader is not unlocked and I need to relock it.
The threads are old and then you have to get a special code from Huawei site,
and then tap fastboot oem unlock "special number" or something like that.
Now I don`t know how to get that code and is there any way to try unlock bootloader and take a step forward?
Yas, we done step forward tomorrow because we know that PC see my device correctly,
we have good firmware but CMD commands caused another problem. :/
Click to expand...
Click to collapse
Due to the conditions your device is in,
I don't know if you can unlock the bootloader.
To read the code you can use DC-Unlocker
(PC or smartphone versions), buy credits for € 4 and try.
The risk is that if it doesn't work, you throw away your money.
A user HERE suggested the idea of using a method
a little more spartan and without money,
but honestly I have never tried it and you could physically break something ...
The choice remains yours, keep me informed for future developments.
P.S .: Bardzo dziękuję za opinię ...
Dadditz said:
Due to the conditions your device is in,
I don't know if you can unlock the bootloader.
To read the code you can use DC-Unlocker
(PC or smartphone versions), buy credits for € 4 and try.
The risk is that if it doesn't work, you throw away your money.
A user HERE suggested the idea of using a method
a little more spartan and without money,
but honestly I have never tried it and you could physically break something ...
The choice remains yours, keep me informed for future developments.
P.S .: Bardzo dziękuję za opinię ...
Click to expand...
Click to collapse
Ciao!
I`ve tried to use this spartan method...but all that nordic combinations were useless...because I still have fake unlocked bootloader. I`ve decided that motherboard in my phone is a piece of **** and merda, so I`ll buy a little damaged phone. The cost of it is 27EUR, so it`s around DC-Unlocker+DC-Phoenix...but I`ll get a device that work properly and have some scratches.
I don`t want to spend money to my damage and dumping motherboard...because I have done this in the past 3 times (the cost of these repairs are around 60EUR). If I had enough knowledge that my motherboard will break down regularly in the future, I`ll buy used P9 Lite much much earlier.
https://allegro.pl/oferta/huawei-p9-lite-lekkie-pekniecie-prawy-gorny-rog-9523407957
Thanks you all, because we tried a lot of methods and solutions! I'm really thankful for all help!
Grazie mille Dadditz mio eroe. Ciao ragazzo! :laugh:
Nicramcio said:
Ciao!
I`ve tried to use this spartan method...but all that nordic combinations were useless...because I still have fake unlocked bootloader. I`ve decided that motherboard in my phone is a piece of **** and merda, so I`ll buy a little damaged phone. The cost of it is 27EUR, so it`s around DC-Unlocker+DC-Phoenix...but I`ll get a device that work properly and have some scratches.
I don`t want to spend money to my damage and dumping motherboard...because I have done this in the past 3 times (the cost of these repairs are around 60EUR). If I had enough knowledge that my motherboard will break down regularly in the future, I`ll buy used P9 Lite much much earlier.
https://allegro.pl/oferta/huawei-p9-lite-lekkie-pekniecie-prawy-gorny-rog-9523407957
Thanks you all, because we tried a lot of methods and solutions! I'm really thankful for all help!
Grazie mille Dadditz mio eroe. Ciao ragazzo! :laugh:
Click to expand...
Click to collapse
I am in complete agreement with you, you made the right choice.
I was very happy to try to help you, especially because
you are a polite and kind person.
I hope to meet again in the future, but not for device's issues ... :highfive:
I wish you all the best.
Regards
stuck on 5% , software install failed, getting package info error
i used huawei p9 lite vns L22 dual sim , device has got failed verfication ,asking for update latest version, then its stuck on 5% .software install failed, i have a poor knowledge about techniqal issues, please help me out