Yesterday my smartphone started showing the following message when I try to turn it on:
Smart Up Failed
Your device didn't start up successfully.
Use Software Repair Assistant on your computer to repair your device.
I've tried using Rescue and Smart Assistant (LMSA) as prompted, the process goes smoothly and doesn't show any errors. The same with adb, the process goes without any problem, but the smartphone does not start.
1 - I already tried to unlock the bootloader, but the message appears saying that I must access the device settings and activate an option.
2 - I also tried to use Blankflash on the device but it is not recognized on the COM port.
3 - The device is recognized by the fastboot devices command.
4 - I already tried to install an old version of android, but the following message appears - Validation image failed (Bootloader) -
Does anyone have an idea how to solve this problem?
Related
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
Hello and thanks for reading!
I just got my hands on this Nexus 7, and it was working correctly for two days, but three days ago, i didn't use it that day and i think it discharged. Well, after that, it won't go pass the Google logo and it was restarting over and over...bootlooping. I tried going to the bootloader and then to the recovery to perform a factory reset, but when i selected the recovery, it went back to bootlooping.
Since i CAN access the bootloader and can get the fastboot device recognized on my computer (Windows) using the command "fastboot devices", i thought i was saved and tried flashing the stock 6.0.1 image via fastboot. That didn't work well. Everything flashed well except the System. When it tried to flash the system, i got the following error: "FAILED (remote: Unknown chunk type)". There is little information on the internet about that error. On one site, someone said that he was getting that error and sent the tablet to Asus for repair and when he got it back, they had flashed 4.4.1 on it, so i tried flashing 4.4.1 and to my surprise, when i flashed System, it said "Okey" instead of FAILED, again, i thought i was saved, but when i tried to boot the table, there is no bootloop but it just stays on the Google logo and won't go pass it. No bootloop, just stays there showing the Google logo. I let it sit there for about 20 mins, but nothing happened.
Here is the info it displays on the Bootloader:
PRODUCT NAME - flo
VARIANT - flo_16g
HW_VERSION - rev_e
BOOTLOADER VERSION - FLO-04.02
CARRIER INFO - None
SERIAL NUMBER - 08feeecf
SIGNING - yes
SECURE BOOT - enabled
LOCK STATE - unlocked
Is there something im missing? Any suggestions? I would like to fix this tablet.
Bump.
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------
In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.
Hi!
I recently bought an LG G4 from an online seller. The cell phone itself is working fine, but it has some problems. It is a refurbished model.
I will very much appreciate any help.
The cell phone is actually a F500L model (I checked it by looking at the motherboard), but in the software information it shows to be a model H81510h.
The phone is not rooted. But I believe that someone did it, changed the device's descriptions and then uninstalled it.
It is an android 5.1, but I cannot update using the update center. There it shows that it is already in the latest version.
In the developer settings, I try to enable OEM unlock, it activates for 1 second and deactivates automatically.
I try to do the hard reset, but when restarting to start the process, it presents an error "Secure booting error 1002".
I can activate USB debugging, it is recognized in ADB tools and I can send commands to it. But it does not start the bootloader with the command "adb reboot bootloader", and it presents the same error "Secure booting error 1002" if I try to send the command "adb reboot recovery".
I can activate the Download mode (by pressing the VOL UP button and inserting the USB cable), but it is not recognized by LGup (UNKNOW / COM5 H81510h), LGup does not let me work with it.
In the LG Flash Tool, it does not start the flash process, when it reaches "BIN CRC Check" it presents the error "Failed PreviousLoad0". (I already changed the port to COM41)
In LG Bridge, it is recognized as F500L and shows that there is an update. But when trying to update, it does the first steps, but after the download, when installing it gives an error and asks to start over.
I have tried to use UPPERCUT_1.0.0.0, without success.
I do not know what else to do...
Any help will be appreciated.
Hello,
We've had this phone for almost 2 years now. Never rooted, it was used by an elder in the house for watching youtube videos and reading news. A few days back, the device went into Fastboot mode (with only two choices available, once in fastboot mode - Reboot & Recovery) for inexplicable reason (no I wasn't trying to root or flash a custom rom; I'm a techie but not this much into Android) and no matter what I tried, it would keep booting back to the same mode. None of the following worked:
1. Keeping the power button pressed for 15-30 seconds.
2. Clicking Reboot.
3. Clicking Recovery.
After the aforementioned measures didn't work, I took the phone to a service center. They claimed that software was not getting downloaded into the device and that it's motherboard needed to be replaced (I should point out that before this issue popped out of nowhere, the phone was working perfectly fine; no battery issues, no performance problems, etc.). I refused to get the motherboard changed, brought back the phone and hooked it up with a PC and ran a few fastboot commands. Here are the observations:
1. "fastboot devices" - shows device id (which means drivers are fine and device is accessible).
2. "fastboot reboot" - phone reboots to fastboot mode (again!)
3. "fastboot continue" - phone moves beyond fastboot mode. Almost instantaneously, Vivo logo comes up and in the top left corner, I see the message " any key to shutdown" (the word "Press" before "any" is not visible).
4. "fastboot oem unlock" returns "unknown command" error. (NOTE: I had never enabled "OEM Unlocking" in Developer Options.)
5. all other fastboot commands return "unknown command" error.
After some digging, I learned about the EDL mode, how to enter it and flash stock ROM using QFIL for unbricking purposes. I was able to successfully enter EDL mode after shorting the test points. After several attempts to flash stock ROM, my swift progress was finally halted by the EDL authorization issue:
INFO: Target Said: ret_auth = -1
INFO: Target Said: "Warning: Unauthorized tag 'program'"
(I can post the full log, if needed).
So here's my question: how do we get past this EDL authorization issue ? I've gone through the forum for Vivo V9 and also scoured the web but have not seen anyone getting past this issue successfully. I'm not particular in bypassing this security mechanism by any shady means; I'd be really glad if Vivo service center or customer support helped. But Vivo hasn't been helpful at all; they're maintaining that their service center's diagnosis is final. Apparently there's no grievance redressal process by which I can get a more senior support team to double-check the conclusions of the service center.
Looking forward to inputs from the community here; any help would be appreciated.
Thanks,
AS.