yashsingh1/xdaforums huggingface dataset:
[P8lite General] marcolomboss:
expect news from me tonight. I will send my own use recovery file..

Marcolomboss
[P8lite General] cristi.blidariu:
unbrick firmware ale-l21c432b052

download from here https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q extract ,now put your phone in fastboot/rescue mod,open folder that you just extract and search for FLASH-ALL.bat,right click and open as administrator,now wait til will flash all files,it will reboot automatically,if it not work i don't have any more ideas
[P8lite General] YetAnotherP8Owner:
Ran the script, phone rebooted and still black screen appeared. I can still only enter 'Huawei eRecovery' mode but stock recovery is still appear as black screen.

Console results:

Se va a flashear la ROM B052 completa,
Si no desea hacerlo cierra esta ventana.
Press any key to continue . . .

target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.555s]
writing 'boot'...
OKAY [ 0.617s]
finished. total time: 1.174s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.971s]
finished. total time: 1.845s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.547s]
finished. total time: 9.079s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 12.682s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.853s]
writing 'system'...
OKAY [ 7.409s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.811s]
writing 'system'...
OKAY [ 7.456s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.772s]
writing 'system'...
OKAY [ 7.366s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.266s]
writing 'system'...
OKAY [ 7.187s]
finished. total time: 100.220s

ROM B052 flasheada, si todo ha ido bien
debe reiniciarse el telÚfono.

Si sale el recovery hacer un hard reset y
reiniciar el telefono.

Actualizar a travÚs del men· del telÚfono.
rebooting...

finished. total time: 0.022s
Press any key to continue . . .

I thank you for giving it a try to help me out. I am really confused as to what is wrong with my phone.

Is there anyone that has a good tip or perhaps a diagnostic tool to help me locate the issue I'm experiencing?
[P8lite General] marcolomboss:
I do not understand something, do not enter the recovery mode phone does or does not turn on?

Marcolomboss
[P8lite General] YetAnotherP8Owner:
The phone does turn on. "Fastboot & Rescue Mode" works. However past the Huawei logo the phone does not respond and the screen stays blank. Recovery mode does not seem to work either.

With the boot and recovery images provided by cristi.blidariu, I am able to enter "Huawei eRecovery" mode by holding down volume up button while "Fastboot & Rescue Mode".

I do not understand why my phone locks up after the Huawei logo. I am hoping someone might know why or perhaps could help me with the diagnostic part of it.
[P8lite General] marcolomboss:
The first time I encountered such a problem. Sorry, I said I would send a file but forgot.

Marcolomboss
[P8lite General] cristi.blidariu:
try to flash this file

https://mega.nz/#!eQ0ggCyZ!O0wnMpXganPYxVonB5NQawcJkwkUV1Xmj6MYDaQm_7M

is a custom kernel made by [MENTION=7354786]XePeleato[/MENTION],download,extract and run command fastboot flash boot boot.img,i hope this will help you
[P8lite General] YetAnotherP8Owner:
Flashed with the provided boot image. Console results:

C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23896 KB)...
OKAY [ 0.611s]
writing 'boot'...
OKAY [ 0.382s]
finished. total time: 0.995s

C:\adb>

Held in volume up button to enter 'Huawei eRecovery' mode and selected shutdown. Started the device up, Huawei logo shows as normal, after two to three seconds the screen goes blank and stays blank. No boot loop but the screen just stays blank.

Thank you so much for still trying, I must admit it looks rather bleak to getting this phone to work again, shame. Please let know if there is something I could do to better diagnose the device for you.
[P8lite General] cristi.blidariu:
Now try to flash twrp recovery and boot to recovery,wipe all and see if is work
[P8lite General] beniouse:
Hello,

I tried exactly the same things because I'm stuck in a bootloop too.

None of these is working, but the difference is : I cant access to erecovery...
[P8lite General] beniouse:
For information, I updated to the last version.

I also did the tri-button reset, but installation is stuck at 5% now...

I can access to the stock recovery, when I wipe, it's stuck to 9%... it crashed, tried to wipe again ==> stuck at 2%

help ! pleaseeee
[P8lite General] cristi.blidariu:
if you have access to recovery,then flash twrp recovery over fastboot,you will need to have your bootloader unlock,when you are in twrp recovery,select wipe,advanced wipe and wipe all,i hope this will work for you
[P8lite General] YetAnotherP8Owner:
Which of the posts contain the twrp recovery? To make sure I flash with the correct recovery image.
[P8lite General] beniouse:
Twrp_3.0.2.img ?

I just flashed it, so black screen and then eRecovery.

My bad, i'm in TWRP. formatting... I keep you in touch if it works

EDIT : Ok TWRP just crashed during the formatting. My bet : HW issue. What do you think ?

EDIT2: finally i wipped everything on this phone :D

Which build should I install ?
[P8lite General] cristi.blidariu:
try to flash Ale-L21C432B132 and see if is boot,after that make local update with this

https://mega.nz/#!jEMXxSqC!F4PSJ2f6CPBxqJIhwwaG7IjfMsvwQ02NoG49GXjAiFc

is version Ale-L21C432B188,this update you will need in order to have network signal,i hope that can help you
[P8lite General] beniouse:
Ty i'll try that today.

For the flash, do you advice Fastboot or mfastboot ? i think there is no difference but just in case...

Or do I have to boot tri-button method ? (vol up/down + power) ?
[P8lite General] cristi.blidariu:
you can try fastboot,and if is not work then try with mfastboot
[P8lite General] beniouse:
Holy molly lord : IT WORKSSSSSSSS :D :D :D :D

THANK YOU VERY MUCH FOR YOUR HELP AND YOUR ATTENTION !!!!!
[P8lite General] cristi.blidariu:
You welcome [emoji1]
[P8lite General] YetAnotherP8Owner:
So I installed TWRP (using recovery image TWRP_2.8.7.x_P8Lite_kirin_v2) as instructed and entered recovery mode.

The screen is still blank however I am now able to see the device is connected via USB on my desktop while in recovery mode. Image of connected device.

Please advice.
[P8lite General] cristi.blidariu:
download from here https://mega.nz/#!B8R0xJYb!E8Ldq5_IQ3WmztjZZ-0ykrwVawr0ArPxckAEiV7WytM] is the last vers. of twrp,if is boot in recovery,then wipe all,after that,extract firmware from Ale-L21C432B132 with huawei extractor and flash boot,recovery,cust and system by fastboot commands,if your phone will boot,then you will need to update with this

https://mega.nz/#!jEMXxSqC!F4PSJ2f6CPBxqJIhwwaG7IjfMsvwQ02NoG49GXjAiFc

is the version Ale=L21C432B188 that is need to have network signal,i hope it will work for you(with vers b188 there's no need to flash by fastboot,just open settings,updater and make local update,you must putt update.zip in dload folder and then copy to your internal memory phone)
[P8lite General] YetAnotherP8Owner:
I flashed recovery with TWRP3.0.2.img and entered reboot mode. Hurra, it showed something else than black screen. I chose the wipe option and let it wipe to factory settings. Console output:

Updating partition details...
... done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media...
Done.
Updating partition details...
... done

I reboot the system into "Fastboot & Recovery mode" and flashed the device, boot, recovery, cust & system, with images from "ALE-L21 C432B132 Europe channel Dual". However the same problem presents when trying to enter recovery mode. Blank screen once again.

TWRP recovery mode works great, however any stock recovery images do not boot it seems. Please advice.
[P8lite General] cristi.blidariu:
you don't need to enter in stock recovery,just leave the phone to boot to system,once there create a folder in internal memory and named dload,download the version b188 that i have give you,now extract an copy update.zip in to dload folder,go to settings.updater and make local update
[P8lite General] YetAnotherP8Owner:
I am unable to boot the device the normal way. It is stuck upon the Huawei logo. I gave it 5 minutes and nothing happens.
[P8lite General] cristi.blidariu:
ok,then boot again in twrp,wipe all and then reboot to system,if that not work,then putt your phone to fastboot/rescue mod and flash again those 4 files from b132,it should work,since you have wipe all from twrp(Dalvik/ART Cache,system,cache,data)
[P8lite General] YetAnotherP8Owner:
Wiped and flashed with B132 images, boot, recovery, cust & system.

Console output:

Updating partition details...
... done
Full SELinux support is present.
MTP Enabled
Wiping Dalvik Cache Directories...
-- Dalvik Cache Directories Wipe Complete!
Formatting System using make_ext4fs...
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media...
Done.
Updating partition details...
... done

C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.555s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.177s

C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 0.972s]
finished. total time: 1.847s

C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.521s]
writing 'cust'...
OKAY [ 4.189s]
finished. total time: 10.712s

C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.794s]
writing 'system'...
OKAY [ 7.464s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.635s]
writing 'system'...
OKAY [ 7.202s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.853s]
writing 'system'...
OKAY [ 7.344s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.932s]
writing 'system'...
OKAY [ 7.426s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.847s]
writing 'system'...
OKAY [ 7.407s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.029s]
finished. total time: 100.987s

C:\adb>

I am now back to a blank screen upon device start up. After the Huawei logo, blank screen appears and stays blank.
[P8lite General] cristi.blidariu:
I am so sorry,but i dont have any more ideas [emoji17]
[P8lite General] marcolomboss:
friends, then install TWRP take care of business, you must install the stock recovery. TWRP while, you make a transaction with rum.

Marcolomboss
[P8lite General] cristi.blidariu:
try to istall this https://mega.nz/#!W99zUSKZ!4183H3V2zWBzhvxcVAIJqKFIdke890MZ0noIsbaBXmk that is [MENTION=7063184]sokkoban[/MENTION] custom rom,just download and copy to an sd card,now boot to twrp recovery,make all the wipes then install and see if that will work(Be patient first boot can be about 15-20min)
[P8lite General] YetAnotherP8Owner:
Wiped everything and installed 'P8Lite-ALE-L21C432B574-Deodex-Rooted.zip' through TWRP as instructed.

TWRP log: http://pastebin.com/raw/kUkWAqbB (too long to be posted)

Booted to system and waited. The screen appeared to be stuck on the Huawei logo. After 18 minutes I observed the phone rebooted, still stuck on Huawei logo. I observed two more reboots after 22 minutes and 19 minutes. In total I gave the phone one hour and observed, what I would describe, a very long reboot loop at about every 20 minutes. Please advice.
[P8lite General] cristi.blidariu:
i am sorry to say that,but i gave up,i don't have any more ideas :(
[P8lite General] Bomn:
quick reminder

always remember after flashing a new system image it will take a while

flash back sokobans rom with twrp and in the end remember to wipe and set factory defaults and after wipe cache / dalvik.

It wil take around 15 / 20 mns to boot the first time.

If you flash with fastboot another rom when you flash the recovery there's no more twrp. After you flash a stock Rom, reflash TWRP and wipe / factory defaults / wipe cache and Dalvik.

The cache wipe takes a while as well...

relax ... it's not a paperweight.. it's a fashion statement...
[P8lite General] Michel199090:
Hi everyboy, i´m having exactly the same problem with my device. device stucks at black screen and keeps rebooting , adb get-state shows as "unknown" or sometimes "recovery" , i tried all you posted before , only thing that worked was flasing twrp3.0.2 . ,cache/ dalvik wiped but did not work . anyone has solved this issue?.... thanks
[P8lite General] dkonect:
Hello, reflash your previous firmware .

(Flash by adb the stock recovery, and your previous firmware by a dload folders )

Sent from my SM-N9005 powered by QS-N9005-LP
[P8lite General] GfIsGonnaKillMe:
I am now at the point where I installed TWRP3.0.2, used this to install sokoban's ROM, and now the device won't boot - it's in the standard Huawei start boot screen for around 30 minutes, then reboots, and continue... I already wiped the cache and dalvik using TWRP, both before and after, to no avail. dload is not working, neither is adb.
[P8lite General] GfIsGonnaKillMe:
For anyone else struggling to get into the installed recovery: Some versions of the P8 Lite will always boot into the bull**** EMUI Wifi Recovery *as long as the USB cable is connected* !!! Pull the cable before booting into recovery from full shutdown!!
[G2 Q&A, Help & Troubleshooting] MattheewHun:
Hi guys. My phone fell from ~1.5m and now does nothing when i touch it. The screen seems to be OK. There's a fracture at the screen, but its hard to see. I can restart, enter recovery, and turn off the phone, and the display is fine, but doesn't recognizing touch. Can i do anything?

Thanks in advance.
[X Style (Pure) Q&A, Help & Troubleshooting] VikramK123:
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.

Running on TruePureX MM ROM at the moment with Frankenclark kernel.

Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)

But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.

Saw a couple threads with similar if not exactly the same issue but no solution as such.

The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.

Tried wiping system and reflashing the ROM already with no success.

Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)

P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
[X Style (Pure) Q&A, Help & Troubleshooting] ezeuba:
Go here: http://xdaforums.com/moto-x-style/help/navigation-buttons-issue-t3497985
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
I was on efficient rom 3.3 and wanted to update to 3.4 but I was on some older versions of bootloader and modem so I wanted to update them first before moving to efficient rom 3.4. So I downloaded the BPHJ BL and CP for 935F, opened Odin and successfully flashed the files from download mode, it said the flash was successful and the phone attempted to reboot (as it normally does after an Odin flash), and now it's stuck at the Samsung logo with a red "recovery is not seandroid enforcing" in upper left corner. I try to boot into download mode by volume up+power+home button, the phone tries to do it but it gets stuck again at the same screen. If I plug my phone to the PC now, Odin doesn't even recognize it, it doesn't say added or anything, it's like the phone is not even connected.

I know I flashed the correct files because they are for the 935F (exynos international - my phone).

How the hell did this happen? Is the phone dead? Can I try anything else?
[Samsung Galaxy S7 Edge Questions and Answers] MisterKanister:
You have to get into download mode, otherwise it's normal that ODIN doesn't see anything.

Keep trying to get into DL mode. I've read several times here that people had the same problems with getting into DL mode while being stuck in a bootloop, but eventually succeeded after a lot of tries.
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
I try to but it's just not working. I press vol up + power + home, the screen goes black for a second and then the Samsung logo appears again with the same error.
[Samsung Galaxy S7 Edge Questions and Answers] ecg803:
also i think u have to reflash through twrp the no-verity-opt-encript 2.1 zip. when flash different bootloader.
[Samsung Galaxy S7 Edge Questions and Answers] NonXtreme:
Download mode is vol DOWN + power + home.

New bootloader also required newest version of TWRP.

So after going into download mode flash the newest TWRP and that's it!.
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
Yes the vol up was a mistake, I know up is for recovery and down for download mode. I tried booting into download mode and I still can't do it. I opened this up in the efficient rom thread and yes, I ran into this problem because I wasn't aware I needed the latest twrp version.

Anyway, I try booting into download mode by vol down+power+home and it doesn't work. I try vol dow+power and as soon as the screen goes black I keep holding on the home button as well, without releasing vol down and power. Still not working. The screen goes but instead of booting into download mode it goes back to the Samsung logo with the seandroid enforcing error. This is the first time I can't boot into download mode.
[Samsung Galaxy S7 Edge Questions and Answers] NonXtreme:
Have you try holding vol down+home+power without release them until the download mode come up?

What I mean is that you don't need to wait for screen to go black. Just holding the button combo and phone will automatically reboot and go into download mode.
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
Yes, that's how I usually do it. It doesn't work. I'm thinking of going with the phone for a warranty repair but I'm worried that red seandroid enforcing error will raise questions about root. I booted into download mode a lot of times before, I know how to do it, it just doesn't work.
[Samsung Galaxy S7 Edge Questions and Answers] s8freak:
You're not hard bricked or you wouldn't have any thing showing on your screen.

First hold the power and volume down buttons only til it black screens then as soon as it does hold buttons for download Mode. It sometimes takes many times.

I've also read quite a few people let the phone die then plug it in to charge and then hold the buttons for download Mode.

That's how a friend of mine got his in download Mode.

"And on that bombshell!"

Sent from my Echoe powered AEL Driven G935F
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
Yeah I was thinking of that as well. Thanks.
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
Out of curiosity, if I go at Samsung now in this state, they will know for sure that the phone was rooted? Can I imply something like I tried updating with Samsung kies and now it's stuck?
[Samsung Galaxy S7 Edge Questions and Answers] 102skysx:
seandroid enforcing error means the device can't load the security policy cuz u voided warranty

you could always say something like your kid was playing with it and it went into a bootloop or that there was an OTA update and it stoped midway and now your phone wont boot up hope for the best if they decline u goto another store to have it replaced/fixed some ppl arent knowledgeable about voiding warranty and issue a replacement
[Samsung Galaxy S7 Edge Questions and Answers] lvnatic:
Thanks for the reply. The battery finally discharged completely and turned off the device. So from the powered off state I managed to boot into download mode from the first try. Flashed the latest twrp and everything is working fine. Topic can be closed :)
[General Questions and Answers] ScorpionSX:
Hello everyone!

I hope there isn't a topic already for this, but I searched and didn't find anything, mostly also because it's kind of difficult to describe my problem.

To begin with. I have one of those chinese car stereos that run WinCE 6 in my car. It's not the first one, I actually went through quite few of them to finally find one that suits me. I thought I did, and mostly it's true, but there is still one feature that bugs me a bit.

My stereo has two USB ports. One, mini-USB on front - for music/videos/pics, second, full size USB on the back - for 3G/WiFi adaptor. This is as described by the manufacturer/seller.

Now, obviously, many of us would think, that since it's "universal serial bus", it shouldn't matter what I put in which port. So the rear port should accept music on USB flash drive and front port should work with 3G modem. Right? Right? Wrooong!!!

For whatever reason, my stereo only accepts music in the front port, with annoying little cable that is to convert the mini-USB to full size, just bumping up and down as I drive. Also, since I have a built-in USB port, which I would like to use for this and plug it's connection to rear port on the stereo, bugs me a lot.

But no, the rear port only works with the 3G modem and seems to completely ignore any flash drive connected to it.

What's funny though is, that the front port actually works with the 3G modem too! So the front is a "2in1", but the rear is only designated for 3G/WiFi.

Since I don't want to let this just go and get used to it (+ my OCD is fighting heavilly with me on this, lol :D ), I started to look around to figure out what might cause this. I loaded Total Commander on the unit and plugged two flash drives to the stereo. Both with music files, both formatted the same. In totalcmd it showed them as USB (front) and USB1 (rear) (or something similar, the key part is the "1"). It always added the "1" to the rear one, even though it was connected alone, without the front one.

Now, this is where I believe the problem is. I think/hope/wish that the music application on the stereo only works when pointed to the "USB" (front) device. Since there is probably no way to decrypt and re-program the music app, I was thinking about renaming the USB connections, or, basically switching them for each other.

So to get (finally) to the bottom of my question, is there a way to switch the description/name/purpose of the USB ports in WinCE 6.0 platform, preferably of course in a way that it would stay like that even after restart?

Many many thanks for any help or pointing me to the right direction! Also please let me know if there is some detail that might help identifying the problem.
[General Questions and Answers] _clkownz:
Today I installed an app called USB Device Info from the play store. What it shows is that it cannot connect because of SeLinux.. CLUE?? So I went ahead and looked on how to connect via USB with Linux. I downloaded Terminus from Play Store and was able to read the files. Previously, I read it's a 'read only' connection. I'm researching how to change the 'read only' to 'read and write', and also extract and find these files. I'm currently looking for my "extracted files".
[Samsung Galaxy S7 Themes, Apps, and Mods] zapty:
Energize your HomeScreen and blow your friends away on #HomeScreenSaturdays with “Wallpaper Stories” https://goo.gl/cfzg0Y
[Verizon Note 7  Questions & Answers] pump142:
I entered my original Verizon note 7 IMEI number into their checker and this is what it says. phone purchase date was 8/22

What does yours say?

http://www.samsung.com/us/note7recall/?CID=AFL-hq-mul-0813-11000170