Database Info

Huawei Ascend 540-U01 must reinstall from scratch

Hi there!
I have this Huawei Ascend 540-U01, from Portugal, running (or not running) its original rom. It was working find until it start to run slow. At boot it was blinking a half screen wite square, from time to time it shows "process com.android.play stoped" and some other times "com.android.google stoped". At this point I decided to enter in recovery mode and wipe cache and reset to factory defaults. The problem ware not fixed with this action and I decided to "scan system" from the recovery mode too. It showed lots of files corrupted. Knowing it woldn't solve nothing I tryed again for a reset. Now, the system simply don't boot, but I'm able to reach the recovery mode.
May anyone guide me (or point me) to re-install the stock rom for this device? It was not rooted and I can't boot on normal mode.
Thanks
UPDATE - 03/11/2016
- Fastboot says: "Warning: App has root actions first in 2015-01-01"

My Google Pixel seems bricked - Could someone confirm there is nothing I can do ?

Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do

rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way

muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...

rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device

My phone continuously reboots itself during booting; only fastboot and recovery mode are accessible -- are there any alternatives of factory reset?

I switched off my phone (Motorola Z2 force, XT1789-06) during ringing. I am not sure if this caused the problem, but since then I can't switch it on. During booting, when it starts to show the animated "Moto" logo, it restarts booting, so I can't get to the normal graphical user interface. If I don't touch it, it repeats rebooting until its battery gets empty. It is not rooted, has latest official Android (version 9, I think, nash_retail) on it.
Until now the only thing I could do is to boot into fastboot mode. There I can log in into recovery mode or do some diagnostics, check some logs etc. As far as I can tell they show no problems at all. Except maybe "failed to read fstab from dt" in /tmp/recovery.log -- is it normal in recovery mode?
I tried some manual reboots from fastboot/recovery menu (on the phone), with and without SIM card inserted, with and without being connected to the charger, but they changed nothing: the phone keeps rebooting at the same stage of booting.
I hoped to be able to adb connect to the phone and pull the files from it, hoping I could use these data after a reinstall. But adb devices show no connected devices. I guess adb is not available in this stage of Android loading. Or is it available somehow?
fastboot devices show the phone, but I am not sure what can I do without triggering a factory reset. E.g. what if I would 'fastboot flash boot boot.img' from the stock ROM? I guess something went wrong on the boot partition, so rewriting it could solve the issue. But I afraid rewriting the boot partition would result in a complete factory reset.
My questions:
* what to try to make the phone booting normally?
* can I change boot config to skip logo animation?
* if booting normally is not possible: can I somehow copy my files from the phone to my laptop (linux)? If I can copy them: is it realistic to be able to use those files to restore the apps' states after a reinstall (after a factory reset)? I would like to keep e.g. my phonebook, SMS, Whatsapp and Signal chat history, OsmAnd favorites, Colornote notes, AndOTP credentials, etc. (I have a backup of some of my files, like photos or gps tracks, synced to my laptop with SnycThing automatically, but many others are not backed up recently.)
* if backing up my data is not possible: can I try to fix the booting issue by e.g. flashing a new boot.img without risking a factory reset? What exactly should/could I flash?
* if none of the alternatives above work: are there any other thing I could try or shall I simply accept the data loss and do a factory reset from fastboot menu?
Thanks a lot for your help and ideas in advance,
Peter

Update 11.1.1.1 installed successfully on OP 6T but is stuck in loading

Hello,
Anyone else having problems after this update? I did it now and my phone does not start anymore. Or at least it hangs in the loading screen with the red and 2 white dots.
I shut it down with power and vol + twice but with no effect. It does not react on the power cable being inserted. When it's powered off and I insert the cable it starts to the loading screen, currently showing 14 %.
How to solve this?
Thank you!

I can boot into recovery or fastboot. Not sure how helpful that is though.

try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet

dewa5227 said:
try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet
Click to expand...
Click to collapse
But how can I save my data? I mean when I'm in recovery I have to enter the password before, so the data gets decrypted. But with USB attached I can only see 5 files on my desktop computer.
I emptied the battery and loaded it fully, then restarted. After a long time it say "This device has entered an unstable state. Please try rebooting your device using the exit button below..." and so on.
I hope a data recovery company isn't the only solution.
Also, is there no way to repair it? Like running the update again or something?

Why is there no „apply update from adb“ option in the recovery menu of OnePlus? Apparently I could have used that to backup all my data from the phone.
I tried wiping the cache partition without success so far.

So did Android squeeze security so much that not even the owner can save his data in this status now anymore? A bit sad when they themself break the phone with an update then.
What about these recovery services that also recover data from harddrives? Do they break the phone when they do their thing?

How to bypass Recovery Mode?

Hello everyone,
So I have a rare issue. I have a OnePlus 6. Today, it started to act really weird. It became so slow that even swiping on home screen with no apps opened takes like a minute to register. I forced power off the device. When powering on again, it seemed like it take around 10 minutes or so to boot. Again, extremely slow. I tried everything from restarting and clearing app cache while in the system itself but no luck.
So, next thing I booted to recovery mode, typed my pin, and cleared system cache and settings. It started to progress until just a tiny bit left before the end of the progress bar, and it got stuck again. Kept like this for a long time. I had to force power off the device again. Now, when I try to power on the device, it launches into Recovery Mode. I tried my pin but it wouldn't decrypt and looks like the device is no longer recognizing it. I tried a couple of "default passwords" but it wouldn't work either. It only gives the option to "Forget Password?" Which should wipe everything off the phone. The only other mode it launches into is Fastboot Mode. I'm using Stock everything and Device State is Locked. I'm not sure where to go from here.
Now my question is, is there any way I can open my device again without losing data? Maybe some way I can pull files using adb in that state then factory reset? Or maybe someway I can bypass Recovery Mode and boot again? I have important data that I can no longer access if the only way to fix this is by wiping everything!
Can anyone help? Much appreciated in advance.

When a phone permanently boots into Recovery mode then either Android OS is corrupted - for whatever reason - or phone's bootloader is misconfigured.
If phone is accessible by either ADB or Fastboot you can try to exit Recovery mode by forcing phone to boot into Android OS ( Normal mode AKA System ) by applying the related ADB and/or Fastboot command.