yashsingh1/xdaforums huggingface dataset:
[Android General] HoTsHoT89:
Could you post the source?

The P8 really is a lovable tablet, pity further development can't be done without getting past the bootloader hurdle...
[Android General] obvious:
Xda don't allow linking to other forums I'm afraid. I've already had one post removed
[Android General] xanthrax:
You can always write down here the description of "how to " and post links from AFH, Meg, Dropbox, Gdrive, Box, Mediafire
[Android General] obvious:
Thanks. I've outlined the normal procedure in the op. It's just that it doesn't work that way any more. Maybe a specific older version of firmware is required or maybe it's a hardware change.

I any case it's encouraging that we can install twrp with bootloader locked. Opens up the possibility of system too.

EDIT: Did you see my PM about strange posting issues in the P8 forum where posts are appearing elsewhere? This thread is an example.
[Android General] deepraupe:
I am downloading Firmware TB3-8703F_S000024_161129_ROW_QPST and will try to unlock via fastboot. It is the earliest version I can find.
[Android General] obvious:
Will be good to see although there is a possibility it was earlier versions of hardware.
[Android General] Mhden2x:
any (good) news?
[Android General] XenHai:
Any news? Lenovo fix this problem ??
[Android General] RiTCHiE007:
Yea its weird that the oem unlock option is there in dev mode but then isnt possible to activate
[Android General] hehk1234:
well, the problem persist after this month, lenovo don't provide for us the right patch for this issue :/
[Android General] Mhden2x:
Forget it, they just don't care. I've asked them on twitter, they just prompt me to use the Lenovo forum (which is user based).

This was my first Lenovo device, supposed to be value for money etc. The screen of the tablet starts to seem "yellowish" near the edges, so another reason not to buy any Lenovo device again.
[Android General] hehk1234:
for the price and with this specs I like it, no problems here. The dev from los 14.1 and 15 give patch on kernel to flash roms, but I believe with bootloader unlocked some people feel free to build custom kernel and roms. The only problem is lenovo give correct patch. Delay 1 year lenovo give for us open source code, I don't know may be I was wrong, but someone try to fix this maybe ... if we become to publish on foruns lenovo to release patch to unlock bootloader on this device, problably they work on it.
[Android General] Mhden2x:
Many users asked for a patch to unlock the bootloader (including myself) on that forum but still there's no answer. I've contacted official support months ago on their official twitter account and their first answer was "check on developer's options the switch to OEM unlock, it should work" LOL. They didn't even check what device I was referring to. I've told them that it is useless, it doesn't really unlock anything, so after all this they prompted me to ask on the user forum. What could a user do on this? Nothing.
[Android General] hehk1234:
You have reason, we need to publish again on lenovo forum, contact support again from lenovo, to provide for us the unlocked bootloader, if someone read this thread, please contact lenovo and

"disturb" them, there will come a time when they will have to do something to avoid our charges
[Android General] lhmenezes:
Hi, anyone got it? I was unlocked and I discovered this problem, someone found a solution?
[Android General] daitalos:
bootloader does not unlock on 8703F...In no one firmware

unlocks only on 8703X(3g,lte) : adb devices / adb reboot bootloader / fastboot oem unlock-go

confirmed in : TB-8703X_USR_S000024_161130_ROW & more...

---------- Post added at 02:10 ---------- Previous post was at 02:02 ----------

bootloader does not unlock on 8703F...unlocks only on 8703X

but no problem...you can rooted your device,flash twrp,custom roms etc...
[Android General] slobb11:
Are you sure that custom roms can be installed without unlocking the bootloader?

I have no trouble flashing a rom via TWRP, but it won't boot. I've tried several roms (AOSP Extended, Pixel Experience, and Lineage 15.1), and they all fail to boot.

I'm assuming this is due to the locked bootloader still looking for the factory rom. But if anyone has had success getting a custom rom to boot on an 8703F, I'd love to hear it. I could use the motivation!
[Android General] CleberJorge:
https://xdaforums.com/t/rom-unoffic...geos-17-1-for-lenovo-tab-3-8-plus-p8.4055045/
[General Topics] maxip:
Hi all

When I have my Trinity in my active car kit, the power lockout (set at 15 mins) kicks in. I want this when the phone is on battery but not when on mains / car power. Having the device lock means having to unlock it to respond to any voice calls, etc.

Anybody know how / if you can tweak to give;

battery - 15 lock require PIN entry

powered - no lock

TIA

Maxi
[General Topics] fraser:
I have this sitting on my HD, I know it has worked for me in the past but I haven't used it in a while.
[General Topics] maxip:
Thanks - will give it a go tomorrow (err, later today).

Maxi
[General Topics] maxip:
Tried but apart from saying that it was written for a different version of Windows, didn't actually do anything,

However, may have found an alternative in the forums - http://xdaforums.com/showthread.php?t=259368&page=2 post number 17.

Just changed so will see what happens.

Maxi
[Galaxy S III Q&A, Help & Troubleshooting] Zedgor:
I have a gt-i9300 with ap I9300BUALE6 cp unknown csc I9300VFGALE6 on android 4.0.4 problem was that i wanted to reflash the software because my sim card/wifi didnt work (doesnt see any wifi networks) also wont see any sd card and baseband was unknown.

Downloaded from sammobile latest firmware for vodafone germany I9300XXUGNH4_I9300VFGGNH2_VD2.zip and i flashed with odin v3.12.7 hit AP box and extracted the firmware zip file, selected the md5 and it flashed succesfully but the phone now is unable to enter on android, im stuck with samsung logo and blue led.

What can i do? I also reflashed again and entered android system recovery <3e> hit wipde data/factory reset and also wipe cache partition but i am still in bootloop. There is an e:failed to mount /efs (invalid argument) error, i had this also with 4.0.4.

Is there any way i can fix this? did i flash the wrong rom? what can i do to bring it to life?
[Galaxy S III Q&A, Help & Troubleshooting] audit13:
I think the EFS folder is where the imei and MAC address information is located. Do you have a backup of this folder? If not, you may have to have the phone reflashed at a repair shop that can also restore the imei.
[Galaxy S III Q&A, Help & Troubleshooting] Zedgor:
i dont have a backup of efs folder.

cant i reflash it without going to a repair shop?
[Galaxy S III Q&A, Help & Troubleshooting] rp158:
[MENTION=5638483]Zedgor[/MENTION]: since you flashed firmware for Germany, this repair-tool might help, at least to get a booting system. You loose your data by repartition and cannot go back to outdated 4.0 afterwards, due to 'new' bootloader.
[General Topics] tiny-penguin:
I am wondering if there is anyone who can port squid local proxy to Android?

It's already open source, but a phone that proxies the LTE connection to the mobile hotspot would be a great idea.
[Sprint Samsung Galaxy Note5] kg2014:
I just got this n920p Sprint phone and I'm trying to use it on Telus. I managed to get everything working correctly on the Stock ROM, but can't seem to get it working with TELETEAM 5.2+. MMS doesn't work , and I can't get on LTE.

Plus, the play store gets stuck during download and installs
[Sprint Samsung Galaxy Note5] Deleted member 4529355:
Do a fresh install...also, Don't use any ROM's included APNs. Edit the APN file yourself with your carrier's latest APN. I'm running Teleteam's ROMs without any problem at all on my carrier.
[Sprint Samsung Galaxy Note5] StreaMMaxx:
Did you do the GMS rom or CDMA rom? I'm trying to get ATT to work with the n920p
[Sprint Samsung Galaxy Note5] ZEMONTI:
Go to settings / about / status / sim card status / sim card status and check of you are running LTA.

If not go to general management / reset / reset network settings. This fixed my problem.
[P8 Lite (2017) Discussion] kindredkaiser:
TL;DR at the end.

Hi, I used to easily root and put a rom on my old N7000, I bought a P8 now,

and man... this forum (and others) is confusing about this phone...

I have the Huawei P8 Lite 2017 PRA-LX1C432B180 dual sim no brand, European EMUI 5.0.1, 3GB RAM.

and I have no idea where to start to install a new custom ROM, because of the confusion :

do I have to start with twrp ? rooting ? unlocking what ? a bootloader ? a frp ? what's a FRP ?

is the .img that come from these Tutorials about bootloaders and TWRP work with my P8 PRA-LX1 ?

the model PRA-LX1 is the same for P8 Lite, P8 Lite 2017, Honor 8, P9 ??? they have the same model numbers ?? even for dual sim and single sim ?? B100 B170 ?? :silly:

Use TWRP, but don't use TWRP it will brick your phone, What ??

XDA doesn't make 2 section for the P8 Lite and P8 Lite 2017, so everything is mixed... :rolleyes:

wow...

TL;DR :

Can someone tell me the order I need to install stuff ? JUST THAT, I'll do the research then, but just tell me what to install in what order ?

for example :

1- TWRP

2- unlock FRP

3- unlock bootloader

4- root

5- etc...

secondary questions :

- is there a way to prevent bricks or at least lower the odds (I read a lot of brick with TWRP, isn't there an alternative ?)

- I read the custom rom will use the free space from the internal memory, so the stock rom will still be there, so since EMUI takes 10GB from my 16GB, I'll have only 6GB to work on ?

Thank you for any constructive answers :good: :o
[P8 Lite (2017) Discussion] KuGeSch:
Please have a look here

https://xdaforums.com/p8lite/p8-lit...-to-root-huawei-p8-lite-2017-android-t3582179
[P8 Lite (2017) Discussion] kindredkaiser:
this doesn't help at all since it doesn't talk about unlocking bootlocker or what to do first :rolleyes:
[P8 Lite (2017) Discussion] kindredkaiser:
responding to my own topic, maybe it will help people

First thing that you need is to unlock the bootloader

I had a hard time with this because the huawei website doesn't allow french phone number, anyway,

- I did a factory reset

- when the phone "first" boot up, it will ask for your google mail account

- then for the huawei account, only now I can create an account

- my phone number didn't work, so I had the option on the screen to send the verification code to an email

- the email will send you to the website (you can fill any info there)

- the phone will see the mail confirmed

- on the web site fill every info you need, the website is annoying because it will send you many verification code to your mail at each action

- verify that your account is linked to honor website by going there and connection with login/password (https://club-us.hihonor.com/index for example)

Finally go to :

- https://emui.huawei.com/en/plugin/unlock/detail

- connect and fill the info and you'll have your unlock CODE.

- now download and install HiSuite and "minimal_adb_fastboot_v1.4.2_setup.exe"

- remove USB from phone, connect the other side to computer

- shutdown phone

- press volume down, stay pressed,

- connect the usb, after a while you'll see the bootloader screen / fastboot screen

- release volume down

- launch fastboot on computer

- type fastboot oem unlock #########

where #### is your huawei unlock code

- confirm and it will reboot twice and do a factory reset

- done

:fingers-crossed:
[P8 Lite (2017) Discussion] kruupos:
reply

You did not explained which ROM you choosed, do a factory reset does not make you root.

I have the exact same model as you and I've been searching all weekend for a custom ROM that work with the device and allows me to be root.

So far I have just found one img but it full of bugs (can't delete apps or access developer options anymore).

I will be thrilled if you have further info or link to share! I'm sure we can help each others :)

So far, the only step that work for me is a tutorial in french from phonandroid forum.

But, once again, I do not recommand this as it is full of bugs!

Good luck
[P8 Lite (2017) Discussion] kindredkaiser:
that's because I'm not searching for a Custom ROM yet, I know custom ROM are unstable for the P8 Lite 2017

I just wanted to know what order, and I found these infos :

1 - unlock bootloader

2 - install TWRP

3 - install Root

after that I want to remove many Apps in my phone via Root.

and backup the stock firmware in case I need it.

I'm only at Step 2 xD
[P8 Lite (2017) Discussion] Mickyvai:
Really interested in seeing if this can be the first post that lists all the steps to obtain root without bricking/problems/issues. :)
[P8 Lite (2017) Discussion] kindredkaiser:
EDIT : [ I did a factory reset and now I'm trying to install Magisk, because apparently you shouldn't trust SuperSU... ] the old post :

I installed twrp-3.1.1-2-v1-prage.img SHA1: 2FC093301A366D6E62AA442C70FFFE082F47C062

worked,

then I installed SuperSU.zip

name : "SuperSU-v2.79-201612051815-EMUI5.0.zip" SHA-1 : 119FF5E1426DBA48BD0AB0276A5A640E8D0C4F6D

worked,

now I have root,

---

Now I will unBloat EMUI5 via adb (package removal with the help of this thread : Link )

and command like : "pm uninstall -k --user 0 $packagname" (e.g. pm uninstall -k --user 0 com.android.inputdevices)

(more info here )

I don't know if you need more info

my phone works fine.

I don't intend to install custom ROM right now, too risky and too many bugs.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] Rootcarrot:
Today my phone fell in snow for about 10secs, later it showed me that my charging port had moisture in it. Now I noticed that when I play something on my phone theres no sound... for example. I went into music and played a song, put it on full sound, nothing, after a 2secs the song pauses. When I play the song again, the volume changes to before the red bit. On facebook, watching a vid had sound for like a split second, but went off again. BUT when I turn on the sound, you can hear the beep thing everytime. But no sound in songs or vids,

Any solutions?
[AOKP Q&A] HIPOKAMPing:
Hello,

Do you know what the recovery.img file is for AOKP nightly ?

Thank you
[Samsung Galaxy Note 8 Questions and Answers] jamgam:
I think my front camera is broke. I just got my Note 8 and went to setup both Iris and Face unlock and neither would work. I was fiddling around and opened the camera app and went to selfie mode and the camera app keeps working but the screen freezes and no picture from the front camera on the screen. I then did some research and found *#0*# to test the hardware and got the following errors below

Checksum Error

Data Line of Front Camera Fail

Makes me think it's a hardware issue but I thought I'd check here first?

Thanks
[Samsung Galaxy Note 8 Questions and Answers] me2151:
try a factory reset if it still fails then yes hardware.
[Samsung Galaxy Note 8 Questions and Answers] jamgam:
Ya I factory reset it. Same issue. I'll work on returning I suppose
[Samsung Galaxy Note 8 Questions and Answers] juliospinoza:
The Iris camera is independent of the front camera, an independent module I mean.

Try testing the hardware. Use this code *#0*#
[Samsung Galaxy Note 8 Questions and Answers] jamgam:
Ya. The front camera failed the hardware test as I mentioned so I'll return it tomorrow
[Samsung Galaxy J7 Guides, News, & Discussion] kp20kp:
Hey everyone, I just wanted to make this thread about rooting the J7 on Boost after upgrading to Nougat. I did not want to try the old root method because of the new firmware for the simple reason of I was afraid to be bricked. Therefore i tried this and it worked

*Disclaimer* I am not responsible for any damages to your device. Do at your own risk. I am also not a developer in any kind of way and will most likely not be able to answer any questions to problems you face. This method simply worked for me after losing my root when i upgraded to 7.1.1 Nougat.

Requirements:

1) Odin (I used 3.10) https://odindownload.com/SamsungOdin/#.Wlpm26hKvIU

2) TWRP https://xdaforums.com/galaxy-j7/development/recovery-twrp-3-0-3-0-galaxy-j7-t3560327

3) Supersu Zip http://www.supersu.com/download

4) An Unlocked Bootloader

Instructions:

1) Unlock your bootloader to enable developer options and turn on usb debugging tapping on about device 7 times and make sure OEM unlock is switched on when rooted (Never turn this off and reboot your device. You'll be soft bricked)

2) Put the Supersu zip file in your phone's storage

3) Boot your phone into download mode

4) Open up Odin and connect your phone

5) Uncheck Auto Reboot!!! if not, your phone will boot up automatically and you will lose TWRP after flashing

6) Flash TWRP where it says "AP"

7) After TWRP finish installing, pull the battery and put it back in and boot into recovery (Power + Home Button + Volume UP)

8) After booting into TWRP, press install and find the Supersu zip file

9) Flash it and then reboot (phone may boot loop a couple of times)

10) Download root checker from the play store to verify you have root

11) Enjoy :)

Thanks go out to minz1 for TWRP and the people of supersu
[Samsung Galaxy J7 Guides, News, & Discussion] Officially_GIANT_818:
I have the J7 Perx (Boost) Software Version- J727PVPU3ARC2 (Nougat 7.0).

I have the j7 perx software v- J727PVPU3ARC2, I need to upgrade to Android Nougat 7.1.1 or higher again. Can you help with this? Please let me know.
[LineageOS Questions & Answers] srgrusso:
I am trying to build LineageOS 13 for my device and I'm following this guide: https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484

I'm using this device tree: https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini

and this vendor tree: https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini

I do not have the kernel source and I am hoping I can use a precompiled kernel. I have synced the LineageOS 13.0 repo and synced the device and vendor tree.

this is my output for "source build/envsetup.sh"

including device/blu/Life_One_X2_Mini/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash

When I run the command "croot" I get "command not found". I assume it's the same as doing "cd ~/android/system". When I run the command "breakfast full_Life_One_X2_Mini" I get the following error:

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.

** Don't have a product spec for: 'lineage_full_Life_One_X2_Mini'
** Do you have the right repo manifest?

** Warning: 'full_Life_One_X2_Mini' is using CM-based makefiles. This will be deprecated in the next major release.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.

** Don't have a product spec for: 'cm_full_Life_One_X2_Mini'
** Do you have the right repo manifest?

I'm missing something obvious but I can't see it. I'm building this in Arch Linux

Thanks
[LineageOS Questions & Answers] bcrichster:
You may need to edit the(device tree) device.mk's to reflect the files you're working with
[LineageOS Questions & Answers] srgrusso:
here is my vendorsetup.sh

add_lunch_combo full_Life_one_X2_Mini-userdebug

and my AndroidProducts.mk

PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/full_Life_One_X2_Mini.mk

I have been looking at this for a week and still can't see what is wrong. I'm starting to feel stupid. Maybe someone sees something I don't. The person who built the tree has built a few roms with it so it has to be something I'm doing wrong. If you need to look at the rest of the tree here is the link.

https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini

Edit: found my error in my vendorsetup.sh should be "full_Life_One_X2_Mini-userdebug" not "full_Life_one_X2_Mini-userdebug"
[LineageOS Questions & Answers] bcrichster:
Use "lunch" instead of breakfast (device).. Lemme pull it up in a min and have a better look

Edit: another possibility could be LineageOS's change from vendor/cm to vendor/lineage that needs reflected in you lineage.mk
[LineageOS Questions & Answers] srgrusso:
Ok i have made it a little further. now when I do lunch I get the following error

You're building on Linux

Breakfast menu... pick a combo:
1. aosp_arm64-eng 9. lineage_espresso3g-userdebug 17. lineage_toro-userdebug
2. aosp_arm-eng 10. lineage_espressowifi-userdebug 18. m_e_arm-userdebug
3. aosp_mips64-eng 11. lineage_ks01lte-userdebug 19. mini_emulator_arm64-userdebug
4. aosp_mips-eng 12. lineage_maguro-userdebug 20. mini_emulator_mips-userdebug
5. aosp_x86_64-eng 13. lineage_manta-userdebug 21. mini_emulator_x86_64-userdebug
6. aosp_x86-eng 14. lineage_mondrianwifi-userdebug 22. mini_emulator_x86-userdebug
7. full_Life_One_X2_Mini-userdebug 15. lineage_roth-userdebug
8. full_P780-userdebug 16. lineage_toroplus-userdebug
... and don't forget the bacon!

Which would you like? [aosp_arm-eng] 7
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
Device Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.

** Don't have a product spec for: 'full_Life_One_X2_Mini'
** Do you have the right repo manifest?

could this be wrong?

#Dalvk Heap's
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk)
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-hwui-memory.mk)

Time to chase the errors.

thanks for helping me.