yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Lite Questions & Answers] hexxr:
Hello guys , i have a very very big problem here .

So lets start from the beggining :

- i was going to flash RR v5.8.2 through twrp 3.0.2-0 , i backed up boot and data from my stock , and then flashed .

- everything was ok , phone booted into RR , i was customising my android for 1 hour and then decided to restore that backup i made .

- i booted into recovery , restored the backup , and BOOOOM THE PHONE GOT BOOTLOOP

From here i tried dload method .

- put c900b300 or whatever .. UPDATE.APP file on my dload folder from sd card ( with my old phone )

- boot into 3 buttons method .

- flashed , and THEN AGAIN BOOTLOOP , BUT THIS TIME IN "your device has been unlocked and can't be trusted." :( :( :(

I have unlocked bootloader , frp unlocked ... no usb debugging enabled .

And can't get to erecovery , can't get to 3 buttons method . Its just stuck on "Your device is booting now..."

Please help me guys , i have this phone for 5 days only and I already broke it... :(
[Huawei P9 Lite Questions & Answers] TheOneWhoSpeaks:
This what happens when you don't follow the instructions.

Buy a new motherboard.
[Huawei P9 Lite Questions & Answers] zgomot:
Sorry but that's bull****!

No need to buy a new mobo. Just use one of the many downgrade guides and be on your merry way.

A full,. hard brick is pretty hard to get. You'll be ok, OP.
[Huawei P9 Lite Questions & Answers] hexxr:
I solved it .
[Huawei P9 Lite Questions & Answers] kennyweed:
Since you aren't writing HOW you solved it, i will leave here my solution for other ppl

had this problem yesterday & solved it by myself.

u will need fastboot for this

1. Boot phone into fastboot (shut down completely, plug phone in to your pc while you're holding down the "VOL -" Button

2. now download this TWRP Recovery (https://xdaforums.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847)

3. put the img file in the same folder as the "fastboot.exe"

4 go to the folder where your files are. hold shift and do a right click into your folder. Choose "Open Command Prompt here"

5. type in "fastboot devices" -- if your device is showing up then you can continue

6. type in "fastboot flash recovery FILENAME.img" (Change filename to the name of the recovery image)

7 If everything worked, shut down your phone.

8. Hold "Vol +" and the power button

The "untrusted device" screen will come. just pass it.

If everything worked and you're in the recovery then you can install every rom zip you want till ur phone works again :)

If something doesn't work or something is not clear then don't be afraid to ask :)

.... i hope i wrote everything right xD
[Huawei P9 Lite Questions & Answers] TheOneWhoSpeaks:
if he couldn';t even boot in fastboot,,,then a new motherboard was required.
[Huawei P9 Lite Questions & Answers] zgomot:
You see, he eventually managed to boot into fastboot, so your rash comment about getting a new motherboard was, well... kind of rash.
[Huawei P9 Lite Questions & Answers] TheOneWhoSpeaks:
most of the times, Fastboot may save you or not (50/50) when you have a hard brick
[Huawei P9 Lite Questions & Answers] islandman75:
HOW? there's plenty of people which hasn't been able to solve it... please share...
[Huawei P9 Lite Questions & Answers] hexxr:
I can't remeber , now I have iPhone 5S , so yea..
[Huawei P9 Lite Questions & Answers] bonnerable:
I bricked my phone when trying to downgrade from 7.0. I have bootloader unlocked and can get into fastboot screen but when I flash the recovery i get "FAILED (remote: Command not allowed)".

They say that P9 Lite drivers should be installed (usually installs when Hisuite detects the phone). Unfortunately, I'm using a new PC. Or correct me if I'm wrong.

---------- Post added at 07:24 AM ---------- Previous post was at 06:47 AM ----------

Ok just figured it out thanks to this post: https://xdaforums.com/huawei-p9lite/help/flash-recovery-failed-remote-command-t3555563

it looks like a bug that says bootloader is unlocked even if it isn't. So just perform another bootloader unlock and go back to fastboot screen. You should be able to flash images now.
[Huawei P9 Lite Questions & Answers] BalkenBrecher:
I have the same problem:

"FAILED (remote: Command not allowed)"

Any solution for this problem? I Cant boot into OS (boot loop). Fastboot and recovery are possible.
[OnePlus 3T Questions & Answers] xda890:
I am recieving my new 3T today :) and I was just wondering if I loose any features or similar if I change from the default launcher to Nova? I need much bigger desktop grid and I also like the other customizations I get with Nova.

As far as I can see, the only thing I loose is the Shelf, which I won't miss, anything else?

BTJ
[OnePlus 3T Questions & Answers] oTeMpLo:
No.. Just use nova..
[OnePlus 3T Questions & Answers] sai444:
There's nothing you loose if you switch to nova. There aren't any features in stock launcher that you will miss.
[OnePlus 3T Questions & Answers] xda890:
Ok, Nova it is... :)
[OnePlus 3T Questions & Answers] lastfugi1979:
Congrats on your new 3T. I bought mine last week. I have always used Nova and its the first app that i load on any new phone. You don't lose much except the the never settle feed and the customized launchers which the custom ROMs provide (Pixel launcher from Resurrection Remix), etc. Not a big deal though.
[BLU R1 HD Guides, News, & Discussion] Unscedeo:
Thank You

I don't understand everything that you are talking about, as I am fairly new to XDA and Android modding. I just wanted to say thank you for at least researching and trying to figure out the answer. The camera is our only major problem, and I do believe that everything can be fixed. Hopefully you can get someone who understands this stuff to help you achieve every Blu R1 HD owner's dream: a stable, fast, custom ROM.

[MENTION=3339270]linuxsociety[/MENTION], thanks for giving us a new hope. :)
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
In lamons terms it boils down to nobody has really tried to provide a custom compiled kernel based off the original BLU config, or they haven't documented their work on xda / github right. The links I provided are for the original kernel source. If the problem is an ABI mismatch it would only require the same toolchain to compile the kernel as used on the CM/Lineage rom working. I highly doubt thats the issue. I'm guessing that the BLOBs that are needed to load the camera firmware arent in place on the ported roms we need. The files will be exact or real close matches to the ones I mentioned in the previous post. Really looks like someone attempted to port the rom from a similar device, and all they got that didn't work was the camera. Thats some luck if thats the case, and is a relatively simple fix that shouldn't take over a couple hours or no more than a days worth of work.
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
Found CM13 project for p6601 / BLU R1 HD on github, and the init files needed for setting permissions on the device nodes of the camera: This info will be useful on the Nougat 7.x rom that works all except the camera: https://github.com/anpage/android_d...a68445d35fb172082/rootdir/etc/init.project.rc If someone can check out the 7.x rom and see if the device nodes/files exist that are referenced on lines 25 -48 of that init file I just pasted. a command such as

grep IMX258_CAM_CAL_DRV /etc/*init*

and/or

ls /dev/*IMX258*

and see if you get any output from either command. I need to really dig further into the actual kernel modules since the camera in the stock kernel is configured as a custom config option, I'd expect the drivers to be binary drivers that get loaded somewhere else during init. I really wish I could just get a full output of the full filesystem contents of the 7.x rom that has broken camera. Most importantly I need the contents of /lib /etc /system/etc /system/lib.

If the 7.x rom that everyone is using has been simply ported from a different mediatek device that has the same SoC and a similar boardconfig, then it would explain the whole deal about the camera not working as the camera is probably one of the only things that differs in these budget mediatek devices. Does GPS work good? Most usually you'll have another piece of embedded hardware that will fail to work too. I've seen mostly mentioning of the Camera, if thats the only piece of hardware that isn't working then we got real lucky there, but I'd like to confirm things like GPS, accelerometer, etc work properly too.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
The same sources you are referring to have been tried and used. They appear to be incomplete. But I am not a build expert. So you decide.

There are two 7.0 roms in the thread. One is built and other is the built one with attempted changes (port style)

I believe [MENTION=2472806]vampirefo[/MENTION] 's build tree is a better start for you. That tree has a succsesfull build at least.

https://xdaforums.com/r1-hd/development/lineage-os-r1hd-t3530751
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
If it builds successfully but fails to boot it may be a further regression than just taking what is actually booting and working all except the camera. I normally wouldn't recommend a port at all and would prefer things be built from scratch, but if we already have a working nougat rom where cam is the only thing that's broken, it would be a lot easier to just try to resolve the broken lib / module issue.. Honestly by the time we put enough time and effort into getting a fully working kernel, device tree / overlay sources, it won't be too ideal to try to continue development to support releases beyond Android O. It would be possible, but just not typical. If we can get a fully working Android N I'd say thats a big progress. If the stock kernel supplied is compatible with the HAL layer used in the nougat rom for the camera, then there won't really be any benefits by reworking the kernel and source tree. We could add some cool things like cpu governors / gpu governors, etc, but thats just optional features. really. If we can verify the stock kernel works, then chances are the stock device tree overlay will plug right into the 7.x AOSP/CM/Lineage sources and be patched for the small broken things such as the camera. Once we really figure out what the exact problem with the camera is we can determine from there what the best solution is.
[BLU R1 HD Guides, News, & Discussion] Unscedeo:
Hey [MENTION=3339270]linuxsociety[/MENTION], again, great work. I remember that there were some issues with the GPS before (look here: https://xdaforums.com/r1-hd/development/cm14-1-r1hd-t3518202/post70553905#post70553905). I do believe that they were fixed, but make sure to review the thread. With [MENTION=6928202]KazuDante[/MENTION] ZenUI ROM, there were some auto-rotation bugs, and those were patched. I wish I could help you with running those commands, could you tell me or point me somewhere I could learn how to do this stuff? I'm happy to help!
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
https://github.com/vampirefo/androi...260ad3582807fb162a0d4/rootdir/init.project.rc

init.project.rc

#camrea section does not fit the bill for the stock kernel's parameters:

Stock Cam section follows:

#Camera
chmod 0660 /dev/MAINAF
chown system camera /dev/MAINAF

chmod 0660 /dev/MAINAF2
chown system camera /dev/MAINAF2

chmod 0660 /dev/SUBAF
chown system camera /dev/SUBAF

chmod 0660 /dev/GAF001AF
chown system camera /dev/GAF001AF

chmod 0660 /dev/DW9714AF
chown system camera /dev/DW9714AF

chmod 0660 /dev/AD5820AF
chown system camera /dev/AD5820AF

chmod 0660 /dev/BU64745GWZAF
chown system camera /dev/BU64745GWZAF
chmod 0660 /dev/IMX258_CAM_CAL_DRV
chown system camera /dev/IMX258_CAM_CAL_DRV

VampireEFO Lineage 14.1 rom file follows:

#Camera
chmod 0660 /dev/GAF001AF
chown system camera /dev/GAF001AF

chmod 0660 /dev/DW9714AF
chown system camera /dev/DW9714AF

chmod 0660 /dev/LC898212AF
chown system camera /dev/LC898212AF

chmod 0660 /dev/BU64745GWZAF
chown system camera /dev/BU64745GWZAF

Nobody has enough commit history on any of the p6601 sources I can find to really tell what changes have been made and why. It's real hard to try to debug this stuff, but from what I see the init scripts are missing some permission settings on device nodes, about as I suspected. I'd hate to think someone hasn't already tried to fix that init script to make the proper permission changes on the correct camera device nodes.

Can anyone provide a pastebin for:

ls -l /dev/

on the 14.1 lineage rom? Thanks
[BLU R1 HD Guides, News, & Discussion] GuestK00465:
Thanks a lot for what you're doing, it'll help a lot of fellow R1 HD users out there, including myself. I tried to pick up the project a while back but a bunch of personal stuff happened and I wasn't able to. I've got a lot of school stuff going on right now but I'd love to help as much as I can. I'm not too shabby in coding, developing, meming, etc. so if you need any help with such things I'd be glad to do anything I can.

However, my Blu R1 HD runs stock because I need the camera, it's one of the main purposes of the phone lol. If you need any screwing around on PCs or on the stock kernel I can help there.

Thanks again for everything ?
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
Most everything I ask people to run will need to be ran from an adb shell prompt, or you can install a terminal emulator app on your phone, adb is a lot more comfortable to use for me, but it requires you have adb installed on your computer and the working usb drivers. I only use linux, so I can't really point you to simple adb solutions for windows, but they are available, just the drivers require more effort on windows. You don't need the full android SDK toolkit either. A lot of references will tell you to install that, and its unnecessary, you will probably need something like a universal adb driver and the adb.exe and any dll files it requires on windows.

I have a few R1 HD .zip files on here that pertained to the dirtycow exploit that had both linux and windows ADB tools, so you may already have it too. You don't need to do any modifcation or anything to paste output I request, but if anyone really wants to put some effort with root - read/write access to / and /system it would greatly help in trying to test a few things.

I really don't think we are going to need to recompile anything to get the camera working, it seems we are just missing a few file permissions and have a few mixed libraries that need to be corrected, most of which can be fixed without even needing to reboot the phone.

I really wish I didn't depend on my hotspot on the R1 so much because I can't really afford to install a broken rom and have the downtime as its the only means of internet access we have in our home (we live in the sticks )
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
If someone on the 14.1 rom that could please run this in a shell prompt and paste the output to compare the permissions and files in the dev nodes owned by the camera group it would help to start;

for i in `find /dev/ -group camera`;do ls -l $i;done

The output of the Stock Rom looks like:

I expect some differences on the 14.1 lineage and expect this to be the start of fixing the issues.
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
I appreciate you offering your help, right now I'm on the stock rom too and I can pretty much check everything on this end myself, but stick around because its very possible I can overlook something that you may think of yourself. I personally know how all these projects are and if its a one man team they usually end up going dead because nobody really has the time to put into this kind of thing just for fun all by themselves. I can contribute as much time as I can, but I will need some people willing to get their hands dirty on the 14.1 rom. I can't do anything at this point but check the sources and kinda guess what the actual ROM is doing on 14.1 and compare it to the original sources and what our stock roms actually does.
[BLU R1 HD Guides, News, & Discussion] EZJohnson:
I have an r1 hd running one of the cm 14.1 roms and have the same nodes in dev but the permissions on 235, 240, and 239 are root.root 0600 instead of system.camera.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I think a comparison to the Zen rom, which is a port, but the camera does work will confirm if this is a move in correct direction.

.

I also will go back through my notes. There was a second ported rom that I remember worked 100% , but can't find a thread for it. Will update when I find it.

This is the other rom says working all, including camera

https://xdaforums.com/r1-hd/development/wiko-feel-port-6-0-mra58k-mt6735-x32bit-t3518836

I may have some time in next few days to load my tester phone with these two roms and pull the requested permissions. Hope you are onto something.
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
It is important those nodes have RW permission by the system user and also the camera group, otherwise nothing can work unless it is the root user trying to access them. A simple modification to the init scripts will fix that issue, but you don't even need to change the init scripts to modify the permissions and test, however during the next boot they will return to the root root 0600 permissions unless the init script is changed to execute on each boot.

from adb shell you could to execute the following commands one line at a time (you must grant root access to the adb shell):

su
chmod 0660 /dev/MAINAF
chown system camera /dev/MAINAF
chmod 0660 /dev/MAINAF2
chown system camera /dev/MAINAF2
chmod 0660 /dev/SUBAF
chown system camera /dev/SUBAF
chmod 0660 /dev/GAF001AF
chown system camera /dev/GAF001AF
chmod 0660 /dev/DW9714AF
chown system camera /dev/DW9714AF
chmod 0660 /dev/AD5820AF
chown system camera /dev/AD5820AF
chmod 0660 /dev/BU64745GWZAF
chown system camera /dev/BU64745GWZAF
chmod 0660 /dev/IMX258_CAM_CAL_DRV
chown system camera /dev/IMX258_CAM_CAL_DRV

Executing those commands manually will set the appropriate permissions on the nodes. You can try to open the camera (i'd stop any previous running instance) These may need to be set in init, in that case modifying the init file to contain the missing dev node permissions will be necessary.

File is /init.project.rc
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the lineage os 14 that i have is supposed to be the stock boot.img, but i unpacked it and compaired the /init.project.rc and those last two lines in the camera section are missing. ¿ ?

there are couple other changes too. but one at a time. Will try to see if adding it will make a difference. also before I do that i need to check the boot.img foe the other two roms that camera works, to see if there is a common occurrence of those lines.

UPDATE:

I checked the boot.img used on the lineage beta 4 (camera not working) and it has all the lines in the init, but there is a "tab" in front of every line. maybe the indent is causing trouble ¿ ?

The "zen" rom that has a working camera has Identical init.project.rc to the stock V12 version

The download link to the "wiko -u fell" port is broken so cannot check that one.

so next thing for me to do is try it on live system. will update when done testing.
[BLU R1 HD Guides, News, & Discussion] linuxsociety:
The tab in front of the lines will not impact anything, but the two missing lines definitely will.

PS do you care to pastebin all the contents of the init files from the lineage boot.img? Has nobody tested flashing the stock boot.img on top of lineage 14.1 to see the results?
[Xiaomi Mi 4i] Efniak:
I was on AospExtended V4.1, suddenly apps started force closing therefore I rebooted to find a " Encryption Unsuccessful" screen so I booted into TWRP to only realise I couldn't factory reset or do wipes because every time this error will pop "Failed to mount system, cache and data (invalid argument)". The partititons size are 0 and after trying to change the file system nothing got fixed. In fact now I can't get the " Encryption Unsuccessful" error the phone boots into fastboot.

Flashing the fastboot rom or anything else like the stock recovery doesn't seem to work... any leads about what can I do? :confused:

Phone's status now

Now the phone doesn't boot recovery or fastboot and now when I connected to the computer It's detected as Qualcomm HS-USB Diagnostics 9006. I am able to flash the firmware of MIUI witth MiFlash2016.03.30(64bits) as the new beta of MiFlash stopped detecting the device.

I think somehow my phone started to encrypt data, I rebooted It which lead into partition corruption. When I had access to recovery the partition were ****ed so I got a message about failing to mount /data /system /cache. Because of this I decided to try this . After restoring the stock patition the phone enter this qualcomm mode the screen is black and is detected as Qualcomm HS-USB Diagnostics 9006.

I tried some unbrick methods and here are the results:

QFIL(Qualcomm_Flash_Image_Loader_v1.0.0.3): Download Fail:

Switch to EDL FailFailed to Switch to Emergency Download mode

ToolStudio doesn't even start on windows 10.

eMMC_DL_Tool fails to write file (NON-HLOS.bin downloading)

GNQC DownLoad Tool V1.7.1.0 can't start error

Qualfast_v1.0.2 doesn't start

GN Qcom Download Tools V2.2.0.0 it starts but Phoneplatform set error!

[/COLOR]

I got most of the software from here
[Xiaomi Mi 4i] kharbpunit:
Same here

HI...

Did you get any success.. Please share.. I have MI4I.. and stuck in same situation...
[Lenovo A6000/Plus Questions & Answers] D TheThWr:
Hi frnds, I'm playing GTA 5(2.7gb) on my Android device lenovo a6000 plus but it will be slow i will try play this game on both stock and custom roms but results will be same. Lenovo a6000 plus have 2gb ram after that why this game will slower than other game like MC 5 and many other games(2gb or above) are play smoothly but this game is very slow. I see this game will play smoth in other 2gB ram Android mobiles but not in my device .Any buddy have any suggestions for that plz tell me.
[Lenovo A6000/Plus Questions & Answers] Rio Montella:
Sell your phone, and buy google pixel
[Lenovo A6000/Plus Questions & Answers] D TheThWr:
:p
[Lenovo A6000/Plus Questions & Answers] punith.k:
can anyone send me gta5 android download link please
[Lenovo A6000/Plus Questions & Answers] UBA Tutorials:
No I can't buy it transfer to android and play

Using emulator because it's impossible gta 4 will be released on April 2018 and gta 5 on 2023 . All videos are face or streaming!! Virus:p:cool:
[Lenovo A6000/Plus Questions & Answers] GOLU13:
Lol i only played gta vc gta 3 liberty city and gta San Andreas on my lenovo A6K plus never heard of gta 5 on android
[Moto G 2015 Q&A, Help & Troubleshooting] YuZaGa:
I own a samsung galaxy j5. It has the same specs as moto g3.

We have no writing volte( voice over lte) in custom roms.

It works in the stock. Since this forum also had the same problems and somehow it got fixed can anyone tell me who was that dev/maintainer who incorporated the correct blobs and in what way the same can be done for my phone. The source is on github.