yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 General] eurpidees:
Forsure. Thanks a lot ilikepu. I just wasn't sure, cause I read so many posts regarding proxy settings, GRPS, etc. I got so confused, and am now still even confused about internet on the Wing and it's price. Is it just me, or does no one have as much of an abundance of free wifi spots as where I am (Berkeley, CA). Yeah, so if anyone could help me out a bit and give me some info on proxy settings and shifting from GRPS.

http://xdaforums.com/showthread.php?t=373572&highlight=proxy

http://xdaforums.com/showthread.php?t=369392&highlight=proxy

Confused :(

Thanks in advance!
[Wing, P4350 General] ilikepu:
From My Understanding, Is That They All Have The The 5.99 Data Plan For That To Work. Cant Try It Due To Me Cleaning The Phone In The Washing Machine. (yea Not Really My Fault)
[Sony Xperia M] benking007:
Hi everyone. Please help me out. I was trying to root my Xperia M C1904, so first I installed TWRP v3.0.2.0 and then I decided to flash my custom ROM as well.Unfortunately I couldn't do anything now. My phone keeps on rebooting to this recovery everytime I try to boot my phone. I somehow copied ROMs and .img files just to make sure that something,s wrong with this thing. I even download my stock firmware as well. But I can't do anything now. Neither I can boot to system, nor in fastboot as well.

And yeah, when trying to flash, I get these many errors. I thoroughly checked everything on Internet and thought that maybe flashing to stock ROM might help, but this thing won't even flash anything and just keeps on booting to recovery.

PLEASE! PLEASE Help me!

PS: Here is the error below showing in my phone.

E:Could not mount /data and unable to find crypto footer

E:Unable to mount '/data'

E: Unable to recreate /data/media folder.

Updating partition details...

E:Unable to mount '/system'

E:Unable to mount '/data'

...done

E:Unable to mount storage.

E:Unable to mount /data/media during GUI startup

Full SELinux support is present.

E:Unable to mount /data/media/TWRP/ . twrp when trying to read settings file

E:Unable to mount '/data'

MTP Enabled

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/system'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unable to mount '/data'

E:Unknown MTP message type: 1

E:Error changing file system
[Sony Xperia M] [diffER]:
I have a similar problem.. I had the AOSP 7.1.1. BETA 5 ROM but I decided to transfer to Ressurection Remix, I installed it, but it showed me the Unable to mount /cache (invalid argument) error and now it doesn't boot even if I restore my backup with the old ROM. I tried connecting the phone to the Flashtool, but the drivers seem mashed up and I can't even flash my stock software. I wasted my whole day and now I'm clueless... I hope that the phone isn't bricked, broken and somehow I could fix it.
[Sony Xperia M] taman89:
Hello folks.. I had same issue when I flashed aosp based rom from lineage ROM and vice versa. I resolved this issue by following steps..

1) Download Androxyde flashtool which will you get in Google search. This flashtool made only for Sony devices and has build in device drivers which could be install manually. For practical watch on YouTube.

2) Download fotakernel.img from https://www.google.co.in/amp/s/xdaf...cwm-twrp-recoveries-custom-roms-t3016507/amp/ and follow steps that has given.

3)After flashing you will get twrp in which mount option will have cache, system, data etc partitions. Check it to see wheather that particular partition mount.

4) Flash rom and check for further errors.. mostly I used all ROM available for our device which played this trick work..
[P8lite Q&A, Help & Troubleshooting] enzodroide:
Stucked at rescue mode

says this

RESCUE MODE

Attention!
Please update system again

Update user guide:
link from emotion download

*android error droid image*

Error!
Func NO : 9 (dsp image)
Error NO : 1 (security verify failed!)

I already make a folder called dload in my sd whit my UPDATE.APP but i cant restore my phone

I already extracted the update.app with the huawei extractor and tried flash system cust boot recovery recovery2

I tried too flash dsp.img

C:\adb>fastboot flash dsp dsp.img
Sending 'dsp' (2190 KB) OKAY [ 0.187s]
Writing 'dsp'
FAILED (remote: Command not allowed)
Finished. Total time: 0.218s

I tried too with mfastboot but nothing I tried unlocking oem but says is already unlocked and relocking says this

C:\adb>fastboot oem relock *****my number*********
FAILED (remote: root type is risk)
Finished. Total time: 0.062s

i try too flashing diferents version of twrp for my phone but still cant access to recovery

i think i got this error trying to change my data to f2fs and install MorfuZ V3.4 and i don't know what i do my last hope is this forum

pls help i need this phone for work :crying:

Im in a cam-l03 fastboot says this

Fastboot&Rescue Mode

Please Connect Usb Cable to
Your Computer and Open Hisuite(don't work)

More Information:
emotiondownloadlink
volumnkey_down_press_process_func (don't know why says this)

Phone Unlocked (bootloader already unlocked)
FRP Unlocked
[P8lite Q&A, Help & Troubleshooting] GuestK00131:
To force an update, you also need to hold vol+ vol- and power button with update.app in dload folder on your microsd card.
[P8lite Q&A, Help & Troubleshooting] enzodroide:
yes i already do this too but i can't exit from rescue mode only i can go to fastboot now im trying with a another microsd idk if is because i can't find the correct firmwere

i already see you in other post and i try this

im trying to force and update.app but its does nothing
[Android Head-Units] gtxaspec:
No support for lvds for the LCD? That would eliminate needing an HDMI converter.

It's also seems off that as designers you did not ask for input from the one community who this is targeted to, XDA...the point is to dig into the market currently dominated by the poor quality ODMs of Chinese head units.

Pricing...if it works well $300 to $500for the mezz and hikey as a bundle??? The dragon board is not interesting....you can't even run android on that. The hikey960 and 970 is a better choice, especially the 970 once things get going since it has GPS!
[Android Head-Units] 96carboard:
LVDS is really not a viable option, because every different display will require extensive work to support, as well as, in many cases, a custom physical interface. If the goal was a single fixed product in a black box, then I would consider LVDS.

As a developer, I built it because I enjoy working on it. If I can sell it, so much the better.
[Android Head-Units] gtxaspec:
Makes sense! Well, great work anyways. Are we going to see any pictures anytime soon??? I have some empty 2 din cases,and A hikey960 I would love to try this on
[Android Head-Units] 96carboard:
I should have my next batch of prototypes (bare circuit boards) late next week or early the week after. I can post pics of the bare board, but if you're asking for pics of an assembled prototype, I'd rather not post pics of the currently running one on account of it really *looking* like a prototype (there are a few "corrections" on it).

Maybe what I'll do, is take pictures of one as I'm assembling it. I'm sure that some people would find it fascinating.
[Android Head-Units] gtxaspec:
Very cool! If you need someone to test, always willing! I currently work on some ROMs for the Chinese based unita, but an opensource aosp unit has always been the goal (*_*)
[Android Head-Units] styling:
So. Ils possible use stock screen from golf mk7 facelift with your headunit?
[Android Head-Units] ti-b:
I'm very interested. It's something that i'm looking for a while now and will be willing to pay high-end price for high-end performance.

But it also need to be high-end "experience"... Meaning it requires a good looking radio app, physical volume control etc.

I would be also interested the hear about the display option that you found and how "high-end" this could be in term of screen quality but also dash integration?

Anyway, the mezzanine itself would be a huge step forward and I will frequently follow the 96boards website to see when it will be available.

A huge thanks for all the work you already did!
[Android Head-Units] 96carboard:
The radio application is the AOSP automotive radio application https://android.googlesource.com/platform/packages/apps/Car/Radio/. How it looks really is between you and google. The objective, as far as software is concerned, is to change as little as possible with respect to AOSP. As far as physical volume controls go, the buttons on your steering wheel will work, or any other buttons, knobs, switches, or whatever else you might want to hook up.
[Android Head-Units] 96carboard:
First Assembly photo

Since I've got the software into a pretty good state now for running the previous board revision, I've now begun assembling my "V1.0". This revision is "very close" to what I will be shipping.

[IMG="First assembly"]https://gitlab.com/HiKey960-Car/HiKey960-Car/raw/master/assembly/Assembly%201%20-%20Power%20Supply%20and%20Input.jpg[/IMG]

This board measures 123x78mm (under 5x3 inches).

U101 is a 3.3v very low dropout linear voltage regulator. It is used for powering all of the 3.3v components on the board, notably, the analog sides of all of the audio chips, which require a very clean and stable power supply, which is why its an LDO and not a buck.

Q101 is an N-FET, which controls the inhibit pin of the LDO. It takes input from either the microcontroller or the ignition signal. If they *both* switch off, then the LDO also switches off. D101 is a diode that prevents the microcontroller's output pin that drives Q101 from feeding to its input pin that reads the ignition signal.

U102,3,4 are optocouplers, used to read input signals from the car, which can vary within the range of 8-18 volts (though typically will be in the range of 11-15) and convert them into signals that are safe for the microcontroller and/or CPU. All three feed input pins to the CPU, U102 also feeds an input to the microcontroller.

The differences between this board and the final shipping board will be these;

1) There will be a 5th pin at J101, which will be connected to the "switched 12V output" of U203.

2) There will be two 3A diodes between the power input pins and J101.

** Together, these two changes will allow the board to be setup in a mode that allows the CPU and/or microcontroller to control power-off. J101 is a jumper block that allows the user to choose the mode of powering the system.

3) R203/204 are removed, since they are unnecessary.

4) The Anode of D701 is changed from 1.8v to 3.3v. This is to improve i2c performance of U701 (real time clock) and increase the charge on C701 (to increase the time the RTC can run for before the supercapacitor drains).

5) A zener diode is connected from the PWM pin of the fan plug to GND. This is to protect the microcontroller from excessive voltage that may be output by poor quality or incompatible fans. A good quality 5V PWM fan (like a Noctua) will pull the PWM pin up to no more than 3.3v. In fact, I checked with Noctua, and they pull it up to 2.5v. A low quality (cheap) fan may save a resistor by pulling it up to 5v, or a 12v fan could pull it up to anywhere between 3.3 and 12v. A 12v fan should not be used, but I'm sure that someone will plug one in anyway.
[Android Head-Units] 96carboard:
[IMG="Assembly 2"]https://gitlab.com/HiKey960-Car/HiKey960-Car/raw/master/assembly/Assembly%202%20-%20Microcontroller,%20switches,%20RTC.jpg[/IMG]
[Android Head-Units] 96carboard:
It sound like you're describing the ESD diodes. Some might consider it slightly abusive to apply them in this manner, but I can definitely appreciate the application.

While I do know that the SAMD has this sort of arrangement on its input pins, I'm not sure whether this arrangement is present on the SoC or not -- my guess is probably NOT, and even if it is, I definitely can NOT trust that all 96boards SBCs will be equally protected. Only one of the optocouplers is even connected to the SAMD (the bottom one, IGN), all 3 optocouplers are connected to the SoC. If you will notice, there are two voltage dividers on the output of the bottom optocoupler -- R104/107 divides 5 volts down to 1.8 for the CPU, R113/114 divides 5 volts down to 3.3 for the microcontroller.
[Android Head-Units] najaray:
think widely

I suggest you to take a look at taho screen they don't replace the stereo they add a box that work as android with the oem stereo see youtube most of the new cars now a days comes with touch screen think widely take a look of the possibilities good luck

I will become a locale official vendor (if it has a affordable price and a excellent android support)
[Android Head-Units] 96carboard:
There would be nothing stopping you from using a built-in screen with this, as long as the built-in screen has an HDMI input -- which frankly, is quite unlikely, so I wouldn't get my hopes up.

In any case, that decision is outside of the scope of my project. The selection of display device would be up to whoever is installing it.
[Android Head-Units] najaray:
I see it means that some of the customer like tahoe for example cannot use this product at all can you verify the cars that your targitting

can it run two screens at the same time like screen 1 for the stereo and a screen 2 for the car dashboard
[Android Head-Units] 96carboard:
I don't know what you mean by "tahoe" or "taho" as per your previous spelling, but it sounds to me like your questions are off topic. If you wish to continue this, please do so via PM.
[Android Head-Units] 96carboard:
Wouldn't all of these problems be solved with a TVS diode?

https://www.littelfuse.com/~/media/...utomotive_tvs_diodes_application_note.pdf.pdf
[Android Head-Units] looxonline:
Yup, that's similar to the MOV solution. The problem with this type of solution is that it can create the clamp but it can't absorb all of the energy from the load dump (some, yes but not all). It therefore requires somewhere to dump the energy and that somewhere is in the resistance within the alternator and in the leads to the product. Our products could be installed in any location within the vehicle and in a huge variety of vehicles. Controlling the resistance between the alternator and the MOV (in our case) was impossible and this is one of the reasons why the MOV solution was abandoned. Another reason was cost. For a MOV that could handle the variation in conditions that our products were exposed to we had to go for a relatively high power variant. These could cost upwards of $2 which was insanity when you are talking about designing that into a circuit that is selling in excess of 60k units per month. The cut off circuit cost a fraction of that and so we ran with it :)
[Android Head-Units] 96carboard:
Fully operational:
[One (M7) Q&A, Help & Troubleshooting] saronno76:
I read a lot in these day about what can I do on my M7. I installed TWRP and then change my rom to lineageOS 14.1. Then I read that it would be better to swap firmware to gpe. The problem is I have hboot 1,61, so the only way to set S-OFF is by paying 25$ that I sincerely don't want to do for a phone so old. So, I can't directly flash gpe firmware. What I ask is .... is there another way?
[One (M7) Q&A, Help & Troubleshooting] alray:
no

Only sunshine will turn your phone s-off on that hboot version
[One (M7) Q&A, Help & Troubleshooting] saronno76:
Thank you.
[Glass General] plabick:
A few weeks ago, I sold my totally functional google glass on eBay. The buyer later requested a return saying that the glasses will not turn on. That didn't make sense to me considering that it worked perfectly fine when I shipped it but I accepted anyway. When I received the device, sure enough it wouldn't turn on.

When I plug it in, it boots up to the "glass" screen and then shuts off. I have used a USB multi-meter to verify that the glasses do not charge for more than 30 seconds before turning off and that it stops drawing power at that time.

I have tried the following troubleshooting steps

1) Charging for 72 hours using the OEM charger and 2 different USB chargers/hubs

2) Booted device into recovery mode and performed factory reset (2x) with no success

3) Booted device into recovery mode and attempt to sideload the official zip for XE23. ADB sees the device and pushes the zip to the glasses with no issue but the update fails. I tried with XE23, XE22, XE21.3, and XE21 with no luck

4) I can NOT get the device to go into fastboot mode from recovery OR by using the camera button and power button method

I seriously suspect that whoever bought the glasses tried to flash or root them in a way that bricked them and returned them to me.

What should I try next? Am I SOL? Thank you for your help!
[Glass General] mobilejray:
Interesting as I'm having a similar issue with my Glass. After a factor reset, I'm unable to get past the "Glass" screen. The only difference in my situation is that the Glass is taking a charge. Also, I can't get ADB to "see" the Glass. What driver are you using?
[Glass General] plabick:
The google USB driver. Please tell me if you ever find a solution!
[Google Pixel 2 Questions & Answers] murderinc:
Looking to order a Pixel today and the code promo ends in a few days. Anyone have a 15% off code laying around that I could use? If so can you send it to me in a message?

Thanks in advance! :)
[Google Pixel 2 Questions & Answers] murderinc:
WOW!! Thank you for the awesome fast message!!! I used the code you sent me just now! Thanks again it was much appreciated!!! :)
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] Stive87:
Unbrick Maze

Alpha X 6/64GB

only phone is black screen and phone is total brick (format all partition).

https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view

Rom is no official :

System : official rom for

Maze Alpha B6/64GB

. (!

no update after

- OTA !!),

boot, logo and recovery is normal (copy from original my phone).

Good luck.

Sorry for bad english, my french ^^
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] ttl1982:
File not found on your drive :(
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] Stive87:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk

full rom V03 6/64GB Rom Ofifcial Stock

https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] rafaello21:
Update ?

View attachment 4576485
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] Stive87:
update possible for official rom :

full rom V03 6/64GB Rom Ofifcial Stock

https://drive.google.com/open?id=1WjXKj8abnghy_OjfUW5TYkAppjWg0amH
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] dclick:
I am looking for a stock rom of The Alpha X 6/128.

Have you any news ?

Thanks!
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] amonapophis:
Originally posted here

Flash v03, root and recover lost IMEI

I have the 6/64 version. I'll share my method with you. The only one that didn't stuck me in booting TWRP over and over again.

First, I used fastboot flash recovery recovery.img and immediately after fastboot flash boot boot.img . It's the only way I managed to escape the problem. Now, I flashed the ROM provided by them, linked in this post here #123 and I lost IMEI. I used chamelephon to insert IMEI and the IMEI is there but I can't get any signal. What to do?!

Later edit: that didn't work the second time I tried. Neither camelephon.

New method: The last thing I tried was also successful. So, I flashed the ROM they gave me (coolicool store), which you can find here. I selected "auto flash" and "except bootloader" options in SP Flash Tool, pressed "start" and let it on for 3 second and pressed "stop". Then I selected "format all+download", pressed download and connected my phone while holding VOLUME UP. I kept it pressed a few seconds after seeing the red bar getting to 100%. After flashing I started the phone and installed the latest version OTA, v04. After updating I flashed recovery by fastboot flash recovery recovery.img. Of course, I was stuck in booting in TWRP like every other time so I thought of recovering boot from a backup, and since I didn't have one of my own, I used the one provided by [MENTION=2553956]dreambo[/MENTION] found here (thanks dude). When I was prompted to select the items I want to recover, I thought of choosing only "boot", in order to restore boot, but I said why not try restoring "nvram" and "nvdata" too, maybe it will solve my other problem , the lost IMEI problem. And it worked.

I finally succeeded to restore my IMEI and boot, thanks to a recovery, which, now I see, is mandatory before every modification you implement on your phone. Especially when you don't have original ROM.

Sorry for the long post and I hope it comes in handy :)
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] shinystar77:
I have a Maze Alpha X 64GB in which I can only see a black screen will not turn on at all. Only the red charging LED light turns on to say that the phone is charging and connected to the computer.

I have tried flashing the ROM in the link in your post in this thread but only receive BROM errors in the SP Flash Tool.

I have tried the second link full rom V03 6/64GB Rom Official Stock as well but this one does not have a Preloader so I cannot use this ROM to unbrick my phone as my phone will not turn on it needs a Preloader for the phone to turn on.

My phone is being detected by my computer as it makes a sound when connecting the USB cable and also shows up in the Device Manager. Have also tried another computer and tried another USB Type-C cable but only receive BROM errors in the SP Flash Tool.

I have also uninstalled and re-installed the latest Mediatek drivers.

Any ideas?
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] amonapophis:
I'm pretty sure it does have a preloader, since I have used it twice to install with SPFlash Tools.
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] shinystar77:
This ROM does not contain a Preloader:

full rom V03 6/64GB Rom Ofifcial Stock

That ROM would work if your phone is turning on. My Maze Alpha X does not turn on at all hence the need for a ROM that has a Preloader so that I can get the phone to turn on again.

I have tried the ROM in the first post in this thread I keep getting "could not get PMT info" error messages in the SP Flash Tool. That ROM has a Preloader included.

I have installed the Mediatek drivers that are on the Maze Mobile Download Center and have tried different computers with different USB Type-C cables with no luck. My Maze Alpha X is still dead and won't turn on only the red charging light turns on and stays on when connected to USB or Mains. The charging light does not go green to show that the phone is fully charged even if the phone has been plugged in for 6 to 8 hours.

Any ideas?
[Maze Alpha ROMs, Kernels, Recoveries, & Other Deve] amonapophis:
Don't use the one provided by OP. Use the one I got from Maze, it's complete. Download here, it's the official version. I haven't tested the one provided by OP, but the one posted by me here is the one that works. You will find a folder named 18-02-06... and inside one named R14. There you will find all the files needed, including preloader. I have to warn you, though, you will lose IMEI by flashing it ( I don't know why) and the method to restore it is quite complicated, but I wrote it above. Good luck restoring your phone!