Database Info

A handful of problems after performing a factory reset

Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.

Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?

pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.

Flashing *any* OS to Soft Bricked Nexus

Here are the cliff notes of what happened:
1) my screen turned off immediately after I entered the password.
2) I dismantled the phone and cleaned all relevant parts, thinking the hardware may be sending a double-click signal when I pressed the button once.
3) Help forums led me to believe the problem was a software malfunction with the front-facing camera: A sensor that interprets darkness to mean the phone was in a pocket and should have a dark screen.
4) I decided to factory reset the device to repair any outstanding software issues.
5) The factory device setup screen loaded... and the screen went dark and would not come back on.
6) I have managed to reach the boot loader. Now I am stuck; I cannot find a way to install a functioning OS.
Back information: A year ago I was running CM12. For the last six months I've been running Kali; I've had a persistant issue being unable to upgrade to Android 5.1 with Kali, so I intended to go back to CM (but 13 this time).
So presently: Factory resetting will not work because the screen goes dark before I finish the prompt. The Boot Loader is open. My computer recognizes the device but I cannot save anything to it (so I can't put a new ROM on it).
Does anyone have any suggestions for this?

If you're in the bootloader have you tired flashing a stock factory image with fastboot?
Sent from my Nexus 9 using XDA-Developers mobile app

jd1639 said:
If you're in the bootloader have you tired flashing a stock factory image with fastboot?
Click to expand...
Click to collapse
I did; and it worked, but when the setup screen loaded (the language selection page) the screen went dark and the phone became non-responsive.

Did you try cleaning around the proximity sensor by removing all of the components that are set against the screen?
Try installing the oldest factory image you can find on the Google site.

Unable to recover my OPO

Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !

Did you try to "fastboot reboot" while in fastboot mode?

Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.

The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks

Is my G620S bricked? Screen problem (2 explanatory videos avail on request)

The phone in question (Huawei G620S) = [G620S-L01] is an old phone, so just playing with it.
A While ago I installed TWRP as recovery. I managed to install Lineage 15. It used to work. Then I tried something (can't remember what, prob some sort of update), and lost of the use of the screen (as in blank pixels, not black pixels), and boot loop.
Recently I've looked at the phone again. I can manage to get beyond the Boot Loop into TWRP once in a while, difficult. Once in TWRP, the screen is still totally unstable (video demonstrates). I manage to navigate TWRP (video explains), wipe/delete partitions. I have a recent Lineage (and Gapps) on SD: lineage-15.1-20200225-nightly-cherry-signed.zip. Also got Gapps. TWRP seems to install zips fine, I then reboot from TWRP menu.
Boot Loop continues.
When I manage to get into TWRP, I also have the phone on usb to Win7. Win7 recognises the phone and I can open the phone memory on Win. I have noticed that the "internal mem" showing on Win is EMPTY. OK, this is probably because I've deleted partitions, etc. But after TWRP has installed zips, still nothing is visible on phones "internal mem" on Win.
Videos:
G620S bootloop & Using TWRP without screen working properly
I have links to video, pls email or PM me.
Is the screen issue likely a hardware problem? Just bin/throw away the phone?
Is there any other s/w install I can try?

stuck at TWRP boot screen

Hello,
I tried flashing LineageOS for my OG Pixel 2 XL because the security updates stopped. I managed to flash it , but then couldn't fit the GApps on it because the system partition was too small. Long story short I tried various methods of increasing it (even though TWRP no good) & including a format command. (Which started this issue)
Now when I try to get back into TWRP, it's just stuck at the teawin logo I can't actually get in anymore.
I also fastboot flashed the twrp image to see if that got me past the logo, but it's not still stuck.
I've pushed the full OTA image of 11 back onto it, but it's not listed any longer in fastboot devices even thoughthe driver I previously installed is still there. (Android composite ADB interface)
It's listed in ADB devices as recovery. Did I push too much? I should have just flashed back to stock when I saw that the Gapps didn't have enough space, but wanted to press ahead. The power button takes 1-5x tries to work, the screen is cracked with circuits exposed in 3 different places, it has two thick horizonal white lines on the right side because of those cracks. (which didn't appear until months later while on vacation in high elevation...) I guess I'm attached to this phone and want to say forget the security updates I'm happy going back to stock and just keeping it until it dies.
What else can I try? If I'm out of luck, I'm deciding between a 4a and an SE. (Apple at least gives 5 years of updates.)
Thanks!
https://lineageos.org/

Update I managed to get flash.all working and flashed it back to stock.
Is there no way to get LineageOS 17.1 & the stock Open GApps to have enough space on the system partition? I need those apps for work.
Thanks!