Zuk got hard brick. I can`t run system, telephone only show this:
{
"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"
}
I can't do it anything. Zuk is after flashing.
Same problem, with a description
I am experiencing the same problem.
I bought this phone off someone, and it had the official indian firmware. I unlocked the bootloader, flashed TWRP, then flashed Mokee 7.1.1 and the phone worked great.
Then I got curious and started playing with the phone after I noticed issues with the GPS. What is did to get in this pickle is:
1- Reinstalled Indian official firmware (MM) qith QFIL, which was uneventful. When I set up the phone, I couldn't get OTAs, phone was being read as rooted (which was not);
2- Relocked the bootloader after flashing official Indian ROM (MM), was able to get OTA; Somehow, the phone still was being identified as rooted.
3- Again, with QFIL, I flashed official Chinese MM 1.9.063_ST. Uneventful again, the phone was completely back to stock, no root detected, all official status.
4- After this, once again, with QFIL, I flashed official Chinese Nougat 2.5.334_ST. Uneventful flashing, back to stock;
5- I installed Gapps via apk packages, got the phone to sync my calendar, contacts, etc. I was happy with this but noticed that the phone would not timely display notifications. I could have lived with this by manually checking the phone every now and then for gmail, hangouts, whatsapp, but noooooo, I had to get my hand into it again
6- I tried unlocking the bootloader again, but this time the phone would not be identified or seen by my computer, I could not open port 9008
7- I completely reinstalled windows 10, android studio, drivers (in that order), set up the PC to disable signature verification, etc. I was able to open the port 9008
8- I read on Zukfans that you could get proper Gapps integration by using/flashing Chinese MM 1.9.044_ST with QFIL, and then installing Gapps. I tried that, it worked at times, but still, notifications and sync were basically set to fetch, so I again went back to QFIL nougat chinese official ROM. All this time, the phone was working;
9- I decided to simply go back to Mokee 7.1.1, as it was the best experience I had on this phone. This time I could not unlock the bootloader, I could not open port 9008, and this after a fresh installation of windows 10 (I did try on windows 7 as well, nothing would open the port);
10- I rebooted to bootloader with adb command, and then I accidentally entered the diagnostics/engineering mode. I got the same screen that Człowiek`u posted in the picture and the phone has been stuck in it since;
11- I tried flashing again the official chinese nougat with QFIL and also MiFlash. The port would not open, and I was unable to turn off the phone. The only way I had to shut it down was to the the battery run out completely.
12- I finally used the deep flash method (peeling the charging cable and "short circuiting" the wires), and I finally got the 9008 port open, so I went back to flashing official MM with QFIL. The process worked, and upon restart, the screen would only display the ZUK logo for a few moments, to then simply start flickering black and white; I repeated the process with MiFlash, same result
13- Back to QFIL, this time with Nougat official. After opening the port with deep flash method, flash successfully only for the phone to boot automatically into the diagnostics/engineering mode screen (at least it didn't flicker this time). I repeated the process by using MiFlash, same result.
Does anyone here know of a way to hard reset the bootloader (I guess that's what I have to focus on) so that it does not enter the diagnostics/engineering mode automatically on reboot? Flashing with QFIL, MiFlash is successful, and it should reset everything to normal, but this keeps happening.
When I use the deep flash method for opening port 9008, the phone does go black screen as it should, and the tools correctly identify it as COM3, 4, etc with 9008 open, I get none of those Sahara errors, no 900E message. What can I do?
hey any update i got the same problem here. is it working now?
Related
Please don't yell at me for using the 'search' thing....everything directs to "You've gotta flash your phone" blah...but the PC doesn't even detect the Arc.
So. I just rooted the phone a couple of days ago, and I'm pretty noob-ish at this whole thing, I've got no idea what I'm doing XD
So, what's happened is I flashed the Xperia Ultimate HD 2.0 thing onto the Arc, and then felt like changing stuff so...I did a very stupid, stupid, stupid beyond stupid thing and installed another ROM (via the CWM menu thing on the phone) without factory resetting etc...
Then I rebooted the phone, and now it's stuck at the Sony logo ahhahaha
The PC doesn't seem to detect the phone (or maybe there's a way it will?)
I'm screwed, aren't I? Please help the helpless noob? :3 I'll give you a free imaginary bag of chocolate home-made cookies
well what you saw about 'flash your phone' is actually correct Download flashtool, download a rootable stock ics rom, and flash it lol. Here's a tutorial. When you flash through flashtool, the software recognises your phone so don't worry about it
after flashing, root your phone and you're back at where you started
i can help you...
well i think i can help you just follow instructions...
first you need to download flash tool from here > http://androxyde.github.com/index.html?1353476156000
2nd is download stock firmware here > http://hotfile.com/dl/151203731/2a62e2b/LT18i_4.0.2.A.0.62_(1254-8596).ftf.html
after download all files..
1. install Flashtool in your pc.
2. copy "LT18i_4.0.2.A.0.62_(1254-8596).ftf" file to flash tool installed location in firmware folder > "C:\Flashtool\firmwares"
3. Open Flashtool and Click on Flash Button (see Screen 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"
}
4. Now Click on Flashmode then click ok
5. Firmware Selection Window will open then select firmware which you have copied downloaded .ftf File.
6. then click ok and follow screen instruction.
* - Unplug The Device (if connected already with pc)
* - Power off the device (Turn Of Mobile)
* - Press the back button and hold it (back button in your mobile)
* - then Plug the USB Cable (Connect your mobile with pc usb cable while holding back button)
7. wait for 2 min process will take 2 or 3 min.
8. after complete all process remove cable and restart you phone.
9. that's it. :good:
10. if this helped then please come back this thread and press thanks button on my post
same problem, arc struck at sony logo!
I have the same problem with my xperia arc, its struck at sony logo! i flashed as you instructed above, but still after flashing it, its still struck on the sony logo! also I am not able to root it. however when i proceed with the rooting instructions as provided by doom-lord with his root toolkit and start runme.bat it keeps waiting for the device.
please help
rmgunawat said:
I have the same problem with my xperia arc, its struck at sony logo! i flashed as you instructed above, but still after flashing it, its still struck on the sony logo! also I am not able to root it. however when i proceed with the rooting instructions as provided by doom-lord with his root toolkit and start runme.bat it keeps waiting for the device.
please help
Click to expand...
Click to collapse
Try another firmware.
Sent from my LT18i using Tapatalk 2
jimmysmart83 said:
Try another firmware.
Sent from my LT18i using Tapatalk 2
Click to expand...
Click to collapse
thanks a lot mate..:good:!! my dead phone now back to life..!!
I did face the similar issue couple of times after flashing Ultimate Xperia HD and another ROM. But both times, clearing Dalvik Cache by booting to CWM and then booting to system did the trick. Try it...
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running
the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.
You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?
I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying
Error Image
{
"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"
}
Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).
Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.
Can you expand the "android device" section.
See if it's android adb
sorry, i think i quite understand. Which part should i expand on?
Thanks
In
device manager, look up Android device.
Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.
The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?
Please some screenshot again. The one I linked would be fine for adb
I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)
TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"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"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?
I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"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"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
mdve123 said:
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
Click to expand...
Click to collapse
Sorry to hear that, please share your steps to disaster to let others know how to avoid this.
I assume that you used default Windows installer that broke your ufs gpt, instead of the installer you should have been used dism.
At this stage only a service may help you, they will put the device in edl mode and flash a stock firmware.
I think the only way to bring it back to life is to get it into EDL mode and force flash stock rom.
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
mdve123 said:
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
Click to expand...
Click to collapse
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
serdeliuk said:
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
Click to expand...
Click to collapse
Very useful info thank you! Just ordered a deepflash cable, hopefully i will find a workaround to flash in EDL.
If not, i'll try to get it done under warranty. I do not want to risk a keylog or a scam.
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
RoyPH9903 said:
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
Click to expand...
Click to collapse
You should download the latest MIUI Stable Fastboot update corresponding to your region (global, eeaor other) from this thread https://forum.xda-developers.com/t/miui-updates-tracker-xiaomi-pad-5-nabu.4328591/ , decompress the tgz file with 7zip or another software, and then, with your device in fastbboot mode, execute the flash_all.bat file within the folder you extracted. This should work even with a locked bootloader.
Good luck
I get this error
{
"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"
}
RoyPH9903 said:
I get this error
View attachment 5883229
Click to expand...
Click to collapse
Well, maybe I was wrong and you need an unlocked bootloader for this method to work. You could try to unlock it again with MiUnlock https://en.miui.com/unlock/download_en.html . Otherwise, I am out of idea.
I tried it and it didn't work, it tells me that I have to enable my miui account.
RoyPH9903 said:
I tried it and it didn't work, it tells me that I have to enable my miui account.
View attachment 5883255
Click to expand...
Click to collapse
Well, then I'm out of ideas. Maybe you should see what the seller's support can do.