yashsingh1/xdaforums huggingface dataset:
[P8lite Q&A, Help & Troubleshooting] Antonireykern:
Hey there.

I've really f*cked up the Huawei P8 Lite of a friend, when trying to root it with CWM and Supersu package.

He once tried it himself, but that ended up with a new paperweight and he got a new one from the seller.

The old one could boot to TWRP, but ended up with a bootloop when trying to install supersu.

The new one can't even get into TWRP or CWM! Yes, both devices were OEM-Unlocked.

The new one shows a blank screen right after booting to recovery, but i was able to get to system and fastboot.

But after installing CWM (because TWRP didn't work either) it just goes blank after oem logo and adb tells me it is in recovery mode!

C:\Windowws\System32>adb devices
List of devices attached
W3D7N------------- recovery

So every time i try to power the phone on, it boots straight to recovery and same outcome on adb.

It is possible to reboot it with adb in recovery but it does nothing. Just goes to recovery.

Cant get into fastboot either. Adb on system not possible and key combination (tried VolUp+PWR VolDown+PWR and VolUp+VolDown+PWR).

I don't know..

Have i made a second brick? Am I screwed?

Because i don't know if the seller will give my friend a new one AGAIN...

Have i f*cked up? :eek:

Please Help!

UPDATE:

I played a bit around with the adb/recovery and i rebooted it somehow into a mysterious mode...

It showed up as "Red is the Red" in chinese symbols in the device manager..

That is quite mysterious and a lil bit scary... I wasnt able to do anything, tried drivers but no response in fastboot/adb

UPDATE II:

THANK GOD!!!

I somehow got it right with adb reboot bootloader!

You don't know how glad i am :o :o :D

So i would say: SOLVED!
[P8lite Q&A, Help & Troubleshooting] amageek:
How did you get it back to fastboot?
[P8lite Q&A, Help & Troubleshooting] Antonireykern:
I just kept trying with manual reboot and adb reboot and eventually it worked. :victory:
[General Topics] juniofdm:
This link:

mega.nz

/#!QsVQzCTL!xVSUncK04mAeo0IfCx4gLYaxCixzIXqh6EHf0VSETXI

Install with SP Flash Tool.

:good:
[General Topics] yurais:
Thanks for sharing this file.

no thanks button available :(
[General Topics] rotula:
Hello my friend the link does not work is asking for encryption key please help
[General Topics] RXT8:
I need to unlock my blu life x8 bootloader can any one help me
[Samsung Galaxy S7 Questions and Answers] jarro28:
Hi Guys, first time posting here

Well im having problems with my phone Galaxy S7 G930F, first time updating it via OTA and problems started. First update that my phone recibed via OTA and freeze during installation, have to do a hard reboot and it pass.

Going back to factory reset didn't help me.

The phone reboot doing nothing o regular use and enters in bootloops in Galaxy S7 G930F android and the only way to stop it sometimes its to use the recovery and power off or if im lucky just reboot.

So i think its a software issue, so tried using samsung smartswich and keeps with the problems.

Next i flash my phone via ODIN using the another firmware for my phone model. and i noticed i cant seem to use the CSC file, the phone just freeze during earising or installing system.

So next i have to flash using HOME_CSC, i know how it work but for a month i had no issues but i didn't install third party's apps , pass that time keeps freezesing doing nothing o regular use, rebooting, bootloops, etc.

Try to flash to another firmware this time from my country Argentina unbranded lastest firmaware, but i cant use CSC file again, the phone just freezes during installation.

I guess it have to be something relating to memory partition.

In ODIN options im just using the default options Auto Reboot and F. Time Reset. Should i use the Re-Partition also and flash with the CSC file? to try? the FRP lock is ON dont know if that will be an issue or posible brick.

If someone could help me plz
[XDA Assist] denede:
Hi there,

Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.

I've found official ROM package on their site:

ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/

Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?

Thank you.
[XDA Assist] :
Hi,

I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.

Good luck!
[XDA Assist] denede:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..

I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.

I've let it to do so until the battery went dead from 100% and still the same.

I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands :mad:

Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.

In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
[XDA Assist] :
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.

So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
[XDA Assist] denede:
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.

Have the damn files and don't know what to do with them, OMG.

I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :| :confused:

I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.

edit: 100% and no good...

edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.
[Nexus 5X Q&A, Help & Troubleshooting] user822:
Hi,

wanted to ask if the Nexus 5X will support the Galileo satellites on launch tomorrow?

Do I need some special vendor.img for that, or are we left out entirely?

Thanks
[Nexus 5X Q&A, Help & Troubleshooting] yilun:
Probably not, IMO GPS and GLONASS are more than enough...
[Nexus 5X Q&A, Help & Troubleshooting] The_Jacoz:
looks like nope:

https://www.qualcomm.com/news/relea...pport-galileo-across-snapdragon-processor-and

No chances for some software fix maybe?
[HTC Excalibur] abaaz:
hello,

I just installed the Rogers WM6 Rom on my tmobile dash. I use an exchange server and require an always on data connection for my push email to work.

I have specially negotiated a 1gb data plan from Fido and do not care about costs and abttery.

however, everytime I hit the End Call key or the red button, my data conection drops and resets.

How can i fix this can anyone help me please?
[HTC Excalibur] djdanska:
I was wondering the same thing.
[HTC Excalibur] Technology:
ConnTweak Data Always On Settings

This application "ConnTweak" maybe what you guys are looking for and need. It has a setting for keeping the data always "ON"! Get the "ConnTweak" download here http://www.mediafire.com/?3byujynzgik ..........!
[ZTE Axon 7 Questions & Answers] h3ndrik:
According to the Quick Start Guide there is an 'auxilliary' microphone at the top of the device.

However, the test via the diagnostics menu (*983*07#) only picks up the mic at the bottom.

how can i find out if mine is working?
[Google Pixel XL Questions & Answers] Sh0X31:
Hi guys,

The great kitchen from [MENTION=5787964]SuperR.[/MENTION] is not supporting the new file structure of Pixel and Pixel XL (slot a & b). He don't own the phone.My English is not the best and I'm not a dev like you guys so maybe someone can help to get it working.

SuperR's Kitchen Thread
[Google Pixel XL Questions & Answers] cam30era:
[MENTION=2456950]*$M3RT$*[/MENTION],

[MENTION=4544860]osm0sis[/MENTION] Android Image Kitchen is working for Pixel and Pixel XL. Go here > http://xdaforums.com/showthread.php?t=2073775
[Google Pixel XL Questions & Answers] CZ Eddie:
Weird, I tried to get Android kitchen working a few weeks ago but couldn't.

I don't remember why not.

And I'm a ROM building newbie so it's entirely possible I was doing something wrong.

If it works and DU isn't released within the next week (unlikely), then I'll probably sit down and try to learn Kitchen again. :good:
[Google Pixel XL Questions & Answers] cam30era:
It does work. If you're having any issues, [MENTION=4544860]osm0sis[/MENTION] is very willing to help.
[Google Pixel XL Questions & Answers] Sh0X31:
SuperR's Kitchen is much easier.

Benefits of SuperR's Kitchen

it can disable force encryption in boot.img

it can extract the hole factory image like "image-sailfish-nmf26o" or RUU files from HTC

it build update-script

it can add root & busybox

and much more

-> full features
[Google Pixel XL Questions & Answers] osm0sis:
Yup, it's an excellent full-automation menu-driven kitchen. Highly recommended.

It also uses my image tools, my kitchen as an add-on (for any manual changes) and my busybox. ;)

It's not a contest, we all work together. :)
[Google Pixel XL Questions & Answers] Sh0X31:
Yes, really easy to cook a ROM but the Pixel/Pixel XL Firmware not work :'(
[Google Pixel XL Questions & Answers] Sh0X31:
push
[Google Pixel XL Questions & Answers] CZ Eddie:
I couldn't get Android Kitchen or SuperR to work a few weeks ago.

Just opened up SuperR today and found an update available.

Whatever the update was, I don't know.

But I am getting further along in the process than I did last time.

It's my first time with any kitchen though and I'm still early in the process so I don't know if it's fully working or not.
[Google Pixel XL Questions & Answers] DespairFactor:
What exactly are you guys trying to do?
[Google Pixel XL Questions & Answers] SuperR.:
We are trying get SuperR's Kitchen to work with the Pixel devices. Below is a link to the updater-script that is generated by the kitchen currently. It does not work, and I don't have a Pixel or even a general understanding of how the new partition layout works. If you or anyone else could modify the attached script to make it work and post it, I would be very grateful :)

https://hastebin.com/isadepekif.lisp
[Google Pixel XL Questions & Answers] Sh0X31:
First post updated
[Google Pixel XL Questions & Answers] DespairFactor:
I suggest looking at weta updater script and using my slot detection in my kernel zip to find out the current slot and extract the zip files to the partition on device. If you need help contact me directly
[Google Pixel XL Questions & Answers] Sh0X31:
I post it in the SuperR's Thread already.
[Google Pixel XL Questions & Answers] SuperR.:
Thanks to [MENTION=5169465]mdalexca[/MENTION] for providing a slot detection method, I have put together a test kitchen for Pixel devices. Unfortunately there are other issues besides slot detection, but let's get the slots working properly and then tackle the rest. Right now, we need to know if we are mounting, formatting, and flashing the correct slot. Let me know how it goes :)

Donate version v4:

https://gitlab.com/superr/plugins/raw/master/SuperRs_Kitchen_v2.1.3.9-Pixel4.zip

Standard version v4:

https://bitbucket.org/superr/superrs-kitchen/downloads/SuperRs_Kitchen_v1.1.2.9-Pixel4.zip
[Google Pixel XL Questions & Answers] Mentalmuso:
Hi, I want to mention that I was able to build a perfectly bootable ROM by using the latest non pixel version of superr. Using the set meta_data option. Using sparse-dat didn't work.

Edit, sparse did build correctly, but it didn't flash in TWRP.

I have only come across one issue, wifi is draining battery when on. Though this may well be related to deodexed framework files

FYI as far as mounting goes, a simple "mount /system" shell script run in TWRP mounts the current boot slot /system

--->

---------- Post added at 10:31 AM ---------- Previous post was at 10:26 AM ----------

Also, I am available to do any testing needed. Your kitchen helps a lot with the packaging of sparse images for me. Thanks

--->

---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------

Aaaaand also the method of installing SuperSU zips and BusyBox zips that superr uses hasn't been working on the pixel either. I haven't looked into it at all, I created a method for BusyBox using an sh script

--->
[Google Pixel XL Questions & Answers] SuperR.:
Thank you for the feedback :)

If the latest non-Pixel kitchen worked for you, slot_a must be active so you got lucky lol. It has most of the Pixel related fixes included but only uses slot_a which will be a problem in the future for some users. The Pixel test kitchen checks which slot is active and uses that one to mount, format, and flash (hopefully)

Regarding sparse_dat I think the problem is with symlinks, or maybe building the system.img. Is there anything different about building a system.img for the Pixel? Do kitchen-built system.img's work on the Pixel (I am guessing no)?

I am not sure why Busybox and SuperSU are not working on the Pixel. Possibly they are trying to flash to the wrong location? Maybe [MENTION=4544860]osm0sis[/MENTION] can help
[Google Pixel XL Questions & Answers] Mentalmuso:
The zips work for BusyBox if flashed outside the ROM flash. It's something to do with the zip flash commands in updater script for the ROM.

As far as the boot slots go, yeah I noticed it was flashing to slot a. Just giving feedback on the flashing of the ROM files.

I'll be testing later today to try and figure out why wifi is causing a drain. And I'll try out the pixel specific superr.

I've messed with creating system.img manually and all the old methods work when flashing the IMG in TWRP using the TWRP flash IMG function. So I think it's got more to do with the updater script flashing commands more than anything

Edit.. hold on, sorry I remember there being an error in the recovery log saying something about the sparse list not matching or something.. I'll get you the log later

Thanks!

--->

---------- Post added at 11:22 AM ---------- Previous post was at 11:14 AM ----------

Here's a screen shot that should give you an insight of the error flashing the system sparse image. And also just below it is the start of the error when flashing the BusyBox zip.

--->

---------- Post added at 11:23 AM ---------- Previous post was at 11:22 AM ----------

--->
[Google Pixel XL Questions & Answers] osm0sis:
Hmm. The latest SuperSU v2.79 should definitely work for Pixel devices.

By the looks of that log, I'm guessing [MENTION=5787964]SuperR.[/MENTION]'s unzip code either needs to be updated to a) clean up after previous unzips, or b) force-overwrite when unzipping. Then they might work. :)
[Google Pixel XL Questions & Answers] cam30era:
Over in the Pixel XL SuperSU thread, several users are noting that for 2.79 to work they have to reboot to recovery, and delete fstab.marlin
[Google Pixel XL Questions & Answers] SuperR.:
Here is the answer to the sparse_dat issue. A couple posts after that post is an update-binary posted by [MENTION=1162986]Captain_Throwback[/MENTION] that should fix the problem. I will be updating the kitchen at some point, but you can give it a try if you want.

This is only a problem on the Pixel devices and only when flashed from within the zip. I don't think we are mixing files since the first zip is SuperSU and it fails when there are no files to replace. I wonder if the update-binary needs to write to /system/system if it is a Pixel device similar to what needs to be done in the updater-script on the Pixel.

Do you mean /fstab.marlin or the fstab.marlin in the boot.img? Is this something I can do safely on every Pixel rom if root is chosen?
[Google Pixel XL Questions & Answers] cam30era:
I don't know the answers. Head over to the SuperSU thread > http://xdaforums.com/pixel-xl/development/root-supersu-t3490156

And search for 2.39. You'll see a lot of posts. Or just post your question there.

---------- Post added at 04:56 PM ---------- Previous post was at 04:20 PM ----------

@SuperR.

Sounds like a new release, 2.79 SR1 solves some Pixel/xl comparability issues
[Google Pixel XL Questions & Answers] SuperR.:
Updated the Pixel test kitchens with the following:

SuperSU v2.79-SR1

New update-binary from [MENTION=1162986]Captain_Throwback[/MENTION] which will allow using sparse_dat on Nougat

Still need:

feedback whether the slot is detected and used correctly

to know if the new update-binary will work on M sparse_dat

Thanks :)
[Google Pixel XL Questions & Answers] Mentalmuso:
Great thanks, it seems that did help with avoiding the error for flashing a sparse_dat, though now i have done some more testing and found that the actual images built by Superr, arent functional.

Also the boot slot selection seems to be working great.

ive tried...

sparse_dat (flashed in twrp with updater-script)

system.img (flashed with fastboot)

raw system.img (flashed with fastboot)

None boot past the splash screen, (no boot animation) though all the files seem to be in place in /system and /system/system

This is telling me that it may be the applying of symlinks and permissions.

Though like i mentioned earlier, building the rom as set_meta_data creates a bootable rom, with only one issue which is rather detrimental to battery life.

Which was associated with wifi being on, (when off there is no drain) (wifi works by the way) and there was a recurring error constantly which read...

qmi_hw xport service_id=0x35 or something like that...

--->

---------- Post added at 07:29 PM ---------- Previous post was at 06:53 PM ----------

Using the V2 version of Superr

So i just built a stock rom using sparse_dat.. here are my results

The system.new.dat image is just not getting flashed.

I tried setting the by-name at /dev/block/bootdevice/by-name and also /dev/block/platform/soc/624000.ufshc/by-name

In TWRP the script formats the /system partition properly, though when it goes to flash the system, it doesnt flash, it just skips on to install script succeeded.

I then check /system in TWRP file manager and there is nothing in there.

Could it have anything to do with the setting of the partition size? im selecting system.img on that option

--->
[Google Pixel XL Questions & Answers] SuperR.:
I understand that set_metadata works with the wifi battery drain, and I am not sure why.

I am confused about why sparse_dat flashed when built in the normal kitchen, but not in v2. It can only be the slot detection, right? Seems to be the only difference. However, if system is being formatted and mounted correctly it seems the slot detection is working. So what is the difference?

I am pretty sure system.img is not booting because of the symlinks. The kitchen actually grabs the symlink data when you extract a system.img and deletes the physical symlinks. When it builds a system.img, it creates all the symlinks from the collected data in 00_project_files/symlinks, builds the img, and deletes the links again. I think I know how to fix it. Pixel roms need the symlinks to point to /system/system if created from TWRP (I think lol), so I made this happen in the symlinks file. When the kitchen creates them again before building the system.img, it is linking to /system/system instead of /system. When Android is running, the link should be pointing to /system and not /system/system as it is now.

Unfortunately, I will be very short on time through the holidays but I will try to get an update out somehow :)

edit: just looked at the symlinks again, and I think they should be set up correctly lol. If you figure anything out, let me know and I will get to it as soon as I can :)

edit2: I compiled the latest make_ext4fs from AOSP source for 64-bit Linux. You could give it a try if you want. May be some different things for Nougat

http://xdaforums.com/showpost.php?p=70167164&postcount=4861

edit3: Using system.img for the system partition size should be good. It uses the raw img size which should be exactly the same size as your system partition (or / in this case).
[Google Pixel XL Questions & Answers] Mentalmuso:
Thanks for all your work. And don't stress about getting anything out over the holidays. I'm certainly in no rush. I am just wanting there to be an avenue for others to get into the pixel dev arena. It's lonely in there haha.

Sorry I haven't been too clear on the sparse_dat. It never actually flashed. I got rid of the original error that showed in the recovery log regarding the sparse list version number, but the image just still won't flash. It's as if the block_image_update command isn't working. Whereas I know that using simg2img works to flash system.img. as that is how I've been flashing a system.img in TWRP for my ROM. I copy the IMG to /tmp then run a small script to flash it using simg2img. It's convoluted but works.

My first step I think, will be to try again and focus on actually getting a working system.img out of the kitchen,

--->
[Google Pixel XL Questions & Answers] SuperR.:
Pixel test kitchens updated to v2.1.3.9-Pixel3/v1.1.2.9-Pixel3

Changes:

Updated img2sdat by [MENTION=5132229]xpirt[/MENTION] to v1.1.

Use the correct sparse_dat transfer list version for the ROM we are building.

Replaced set_perm with set_metadata in custom zip updater-script.
[Google Pixel XL Questions & Answers] Mentalmuso:
I'll be running a test on this in about an hour.

--->
[Google Pixel XL Questions & Answers] Mentalmuso:
I'm still running into some of the same issues.

Using set_metadata there is permissions or symlink issues resulting in a recurring crash/error that drains battery. See 1st pic for logcat. Probably no suitable info though.

Using sparse_dat the image won't flash, there seems to be no errors in the recovery log, though the flash literally takes half a second, and when filesystem is checked, nothing has flashed.

Building a system.img (sparse) and fastboot flashing results in a non boot situation. Permission and symlink problem again I think. Didn't even get to boot animation.

The flashing of SuperSU from the ROM zip isn't succeeding either, nothing happens in TWRP . Do you think maybe this is related to mounting system?

--->