yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] thecuddy:
I have M8 through Verizon. Waiting for OTA Marshmallow. Can I just root the phone and turn it into a GPE running Android 6.0? And is this the right download?

http://xdaforums.com/devdb/project/?id=11904#downloads

I read quite a bit here also: http://xdaforums.com/showthread.php?t=2744194

I just don't want "unforseen consequences"

Any help is appreciated

Adroid version: 5.0.1

Software number: 4.17.605.9

Verizon Phone
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Should be fine. Read the ROM thread for requirements, instructions etc.: http://xdaforums.com/verizon-htc-one-m8/development/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413

Although I think the VZN version is a bit funky, as they don't allow "official" bootloader unlock, and you will need to root (or temp root) and s-off by sunshine in order to unlock the bootloader.

Verizon specific forum section is here (if you didn't already know): [URL="http://xdaforums.com/verizon-htc-one-m8/development"]http://xdaforums.com/verizon-htc-one-m8/development[/URL]

I suggest reading up and making sure you fully understand, before starting the process.
[One (M8) Q&A, Help & Troubleshooting] thecuddy:
So I have to pay 25 dollars to use sunshine then?
[One (M8) Q&A, Help & Troubleshooting] robocuff:
Yes. It's the only way with Verizon phones. Well, that or a java card. You might be able to find someone who has one who'd be willing to S-OFF it for you. There are several people who frequent this forum who have one. If you're lucky, maybe one of them lives near you. Otherwise, it would involve sending the phone to him or her.
[X Play Q&A, Help & Troubleshooting] konradinho16:
OK, so I did an network reset, it didn't help. Then I gave a battery a few days to "get used to" - nothing happened. I did a factory reset yesterday, wi fi drain is still on board... I have a stock firmware, what can I do to make my Marshmallow work properly?
[X Play Q&A, Help & Troubleshooting] brian10161:
You have disabled location scanning in location services? Disabled Network Notification in wifi?

Also, I hear using 2.4ghz may help. It's strange that some people have this issue and others don't.

Sent from my Moto X Play
[X Play Q&A, Help & Troubleshooting] K.khiladi:
There is already a thread with the name "android 6.0 performance/issues".

Move to that.

The battery stats for wifi I think are wrong because it shows a high wifi drain while actually it isn't.
[Repurposing Old Devices] XDARoni:
Use Your Old Phone For Scientific Research​

I ran across this interesting project that allows you to donate the processing speed of your old Android device to help with scientific research. This means that you're officially a scientist and your friends should call you "Doctor".

All you have to do is install an app called BIONIC and you'll be able get started supporting the research of your choice.

​

View attachment 3660714View attachment 3660715View attachment 3660716View attachment 3660720View attachment 3660721View attachment 3660722​

Download BIONIC​
[Sony Xperia C5 Ultra] pavilion_8060:
I was doing a kernel flashing it, now my problem, he will not and does not start more on. have I think the wrong kernel flashable. What can I do?
[Sony Xperia C5 Ultra] thecryptzen:
Reply

What do you mean start more on?
[Sony Xperia C5 Ultra] pavilion_8060:
If I turn on him he stays in a boot loop he also says that there is no OS on it.
[Sony Xperia C5 Ultra] carnby24:
Use adb to flash your fw again
[HTC Sensation] Ciome:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.

Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.

So I did a backup of all my datas, then proceeded to a factory reset.

After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.

The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.

I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.

Anyway, let's assume that I have S-OFF:

I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.

Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".

Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.

Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.

I need help.

edit: I found out that when I try to install the rom I get only errors saying :

[the first part is missing since I can't scroll up]

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory

unmount of /system failed; no such volume

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device

unmount of /data failed; no such volume

patching system image unconditionally...

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory

unmount of /system failed; no such volume

script succeded: result was [0.200000]

Install from sdcard complete.

FINAL EDIT:

I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
[HTC Sensation] rzr86:
you just had a very old version of recovery:)

i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
[HTC Sensation] Ciome:
No he just told me to get the last version for my phone.
[HTC Sensation] rzr86:
actually i am saying the same thing :)
[Tilt, TyTN II, MDA Vario III General] forcedalias:
Does anyone know if this thing actually supports HSUPA or not? I recall that being one of the new features mentioned when I first heard about the Kaiser, however I haven't come across any official word on it.

I wonder if it's been hidden away like the GPS feature was on the Trinity.
[Tilt, TyTN II, MDA Vario III General] alanplum:
I dunno, but if it does, I hope it's Category 6 :)
[Tilt, TyTN II, MDA Vario III General] xklipschx:
When I was in NYC I had an "H" show up on my Kaiser ... also, I have the HSUPA enabled in the device settings ... so I would say that HSUPA is supported though I have no idea what category
[Tilt, TyTN II, MDA Vario III General] austin_boy:
indeed it was tried in Dallas ( the only place with UPA ) however in few weeks all the markets in the west will be able to handle UPA ( up to 1mb on he UL)
[Tilt, TyTN II, MDA Vario III General] e-dub:
so the network is hsupa enabled or the kaiser is?

eric b
[Tilt, TyTN II, MDA Vario III General] heinz2007:
According to the data sheet the chipset is providing

- High-Speed Uplink Packet Access

(HSUPA), up to 5.76 Mbps (Category 6)

- High-Speed Downlink Packet Access

(HSDPA), up to 7.2 Mbps (Category 8)

http://www.cdmatech.com/download_library/pdf/msm7200_chipset.pdf

So it is a question of the Software an the Network/Provider.
[Tilt, TyTN II, MDA Vario III General] darkilici:
According to manual:

"Functionality

HSDPA/UMTS: Tri-band (850, 1900, and 2100 Mhz).

HSDPA: Up to 384kbps for upload and 3.6Mbps for download;

UMTS: Up to 384kbps for upload and download

GSM/GPRS/EDGE: Quad-band (850, 900, 1800, and

1900 Mhz)"

Hope class 8 HSDPA and (any class) HSUPA can be later enabled through ROM updates.
[Samsung Galaxy S7 Guides, News, & Discussion] mellofello808:
Debating the best case that protects the screen, but doesn't hinder the curve. Any suggestions
[Samsung Galaxy S7 Guides, News, & Discussion] ibcenu:
Get sammys s view or LED view. Had an s view on my note 4 and loved it. These are designed and add additional functionally to the phone by getting info and even snapping photos without opening the cover!

http://www.samsung.com/global/galaxy/galaxy-s7/accessories/
[Samsung Galaxy S7 Guides, News, & Discussion] misiokicio:
Hmm i am thinking myself to go for ringke slim :) i dont own an edge right now but using ringke slim on the s6 right now... and it looks alright on the s7 edge
[Samsung Galaxy S7 Guides, News, & Discussion] Flyer.michael:
Obliq Samsung Galaxy S7 Edge Case Naked Shield Series + Kickstand

http://obliqproduct.com/products/galaxy-cases/galaxy-s7-edge/obliq-samsung-galaxy-s7-edge-case-naked-shield-series.html?a=92&i=2

View attachment 3662676

[IMG="Obliqe S7 Edge naked"]http://ecx.images-amazon.com/images/I/711zTQaTxiL._SL1500_.jpg[/IMG]

My Note 4 died... this will be the first phone ever I´ll have in a case - to sell it, when Note 6 comes to Germany.

This case with the kickstand just looks good
[Samsung Galaxy S7 Guides, News, & Discussion] lukewilson78:
I use a Spigen Slim Armour with the kickstand, it's pretty good and protects the edge on my S6 so I've got another one for my S7 edge. I picked up a Spigen crystal clear soft case for home.
[Samsung Galaxy S7 Guides, News, & Discussion] Whiskey103:
Please look for similar questions before opening a new thread.

http://xdaforums.com/galaxy-s7/accessories

http://xdaforums.com/galaxy-s7/accessories/recommended-samsung-galaxy-s7-t3317820

Thread closed.
[XDA Assist] nortixis:
hello everyone , a friends of mine have some problems with his HTC desire 500 , the phone is nor rooted, is S-ON and locked ,the problem si that every time u start the phone it automatically boots in to FastBoot meniu and doesn't go any where , i tried to do the recovery and nothing, back to fast boot, tried to reset from factory again same thing.. and everything started with an android crash, he said that, he just opened the phone and the next second he sees an announcement that says "android has stopped working" and rebooted in fast boot mod and since then he cant do anything...i thought that i could fix the problem but there is nothing i can do, my PC doesn't see the phone so there is nothing from outside..or at least i don't know , any suggestions ?! PLS help!!

here is a video of the phone...https://www.youtube.com/watch?v=VvNS5gd3p2o

sorry for the noise its my friend talking....
[XDA Assist] Art Vanderlay:
Hi nortixis

Thanks for using XDA Assist.

There doesn't seem to be much activity in the HTC desire 500 section so if you ask here Android Q&A,Help and Troubleshooting or here [Ask Any Question][Newbie Friendly] you might be more likely to find help. Apologies for the late reply.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] abdallah_ismail:
Hello,

While trying to flash the Marshmallow update downloaded for the Uk/Ireland version , odin is giving me a fail of type write operation failed.I have the btu version of android 5.1.1 , how can i solve this problem?

thank you
[Galaxy S6 Edge Q&A, Help & Troubleshooting] bobjbain:
Just keep trying, I was on the BTU version and it took 3 attempts to get the MM XEU version on my phone.
[Android Stick & Console AMLogic based Computers] Shoog03:
Hi all,

I recently got hold of one of these OTT M8S boxes and have been banging my head against a wall ever since then. My ultimate objective is to load Openelec onto this and be done. The Android Firmware it comes with is flaky - especially on MPEG2 content (which is amazing considering how well the Pi Zero does with that content).

Trouble is the Firmware that mine came with has no functional recovery partition. Eventually I loaded a new firmware with a recovery using USB_Burning_tool using a stock .img . This image didn't have my WIFI support so I upgraded it using another zip file and the stock recovery method. This went fine, but really I was no nearer my goal since the new recovery firmware has built in signature checking and will only allow firmwares in the same series to be loaded. It seems that this has become a standard feature of all the firmware for these boxes now coming out. So there is no pathway to loading TWRP or Openelec using the standard Firmware - but it won't allow you to break out of the standard firmware signature checking. Deadend !!!

I attempted to dd a functioning TWRP onto the box using shell emulator, but this simply broke the recovery. This suggests that this issue is deeper than just the way the recovery is setup, it suggests that the issue is with the second bootloader (u-boot.ini) which seems to have signature checking built in as well. So no longer can you pick any functioning u-boot.ini file and make a bootable SD-card with Amlogics SDcardMaker.

Fairly locked down altogether, and it would seem that this feature is going to proliferate to all of these boxes since they are all using variants of the same basic Android ROM, which I suspect is issued by AMlogic themselves.

It seems to me that the only way forward is to create alternative ROMS such as Openelec as pure .img files which can be loaded at the raw NAND level using USB_Burning_Tool. None of the developers seem to be addressing this, simply repeating the old approaches which no longer work on these new generation boxes.

A lot of people are thrashing around and bricking their boxes and without a functioning recovery partition these become defacto hard bricks.

So I make a call out for the developers of the unofficial Openelec firmwares to package them as raw .img files rather than OTA zip files which can no longer be sideloaded.

Maybe someone reading this with a functioning Openelec M8S S812 box can do a dd dump and post up a .img file for me to burn into my box. Please.

Stephen
[Android Stick & Console AMLogic based Computers] Shoog03:
I attempted to use USB_Burning_Tool to burn an Openelec Wetek Core .img file and the program wouldn't pass it. So it seems that not even this is a suitable method of bypassing the bootloaders.

Stephen
[Android Stick & Console AMLogic based Computers] Shoog03:
However here is a heads up for anyone out there struggling to get a decent performance from their Kodi. I have just loaded up my box with the Wetek Core Kodi 15.2 and I can report that out of the box it solves almost all of the Amlogic codec issues people have been facing and runs all three hardware acceleration tabs. On Tvheadend PVR playback it occassionally does a black screen on channel switches and can be very slow to switch channels, but if you switch channels again and then back to the black screen channel it usually comes back. no stuttering or audio lag what so ever. Can be found here:

http://wetekforums.com/v/index.php?...-2-to-fix-23-976fps-video-sync-issues?p=23662

Here is an interesting quote from the users of this Kodi version, which suggests that the Kodi developers know what the issue are but refuse to address them, I suppose they hate these "pirate boxes" that much :

If I had to factor in my time to the cost of this box, the WETEK core starts to look a very cheap deal.

Stephen
[Android Stick & Console AMLogic based Computers] Shoog03:
I went back to this on a hunch and downgraded my Firmware to cyx_m8s_ap6330_8g2g_150728_SD.rar

this ROM has fully functioning recovery and it Flashes Openelec upgrade ROM by default with the toothpick method. So I tried as many different versions of Openelec for M8S as I could find and the sad news is that they all soft brick my box with the M8 v8_8 board. They all reproduce the same behaviour of preventing the box from booting and no Blue light on power up. Fortunately USB_Burning tool version 2.0.5.13 recovers the box without difficulty (though it usually takes two tries to get it past 3%).

It is my conclusion at this point in time that there is no functional Openelec available for this version of the board.

Stephen
[Android Stick & Console AMLogic based Computers] Zebra14:
Working TWRP?

I worked with Abdul over on this forum and he was able to port a OTT S812 2G/8G M8 4335 TWRP which might work for your box. It was for my M8 v8_6 box. I tried all other TWRPs and they didn't work. I was his guinea pig and this result works great

If you go to the Freaktab dot com forum and look into the "TWRP for Amlogic devices" folder (which is under the "AMLogic based TV Players" folder, go to message 900 and you'll see a link to a TWRP recovery which may work on your machine.

I cannot post the URL due to rules in this website to prevent spam.

Hope it helps you.
[Android Stick & Console AMLogic based Computers] Shoog03:
Thanks a lot, that TWRP works very well off of a SD-Card.

It also successful boot into TWRP recovery on my box.

Finally some progress and the possibility of loading Openelec open's up.

Cheers.

Stephen
[Android Stick & Console AMLogic based Computers] Shoog03:
I attempted to use my new power of TWRP to flash a WETEK-Core Openelec development OTA. The result was a soft brick again.

However TWRP opens up new possibilities since I can now flash my Openelec image and then flash the bootloader from a stock rom - since I believe it is the bootloader packaged with Openelec which causes it to soft brick.

Will report back if I am successful.

Update: this strategy still produces a soft brick so the problem must run deeper than the Bootloader.

Maybe you could persuade Abdul to express an opinion on why Openelec soft bricks these boxes as I am sure he would have a good understanding of what was going wrong at the boot sequence.

Stephen
[Android Stick & Console AMLogic based Computers] Shoog03:
So good news folks. I have manged to get openelec loaded onto my box and its working fine.

My method was to use BootCardMaker and to load onto it the u boot.ini file from my second stock ROM.

I then placed the same u boot.ini file into the root of the same SD-card and then unzipped the image "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" into the SD-card root (which I believe I got from the WETEK site). All seem to work fine out of the box and HD works fine. It still has lip sink issues when handling streamed MPEG4 content - but it is definitely using the built in amcodec hardware decoding. Last thing to do is to replace the recovery with the working TWRP and make a full backup of the configured system.

So the issue with all the other builds of Openelec was an incompatible u boot.bin

Openelec is a lot more snappy in the interface than Kodi as an Android app, which is really noticeable when using the crappy remote it came bundled with.

Last thing to check is if the Amcodec has the same zoomed screen issue when outputting composite that exists in the Android version. Hope not.

I can now reload either the working Android or the Openelec using TWRP which is great.

Update: It appears at first glance that this build has no AV support at all.

Stephen
[Android Stick & Console AMLogic based Computers] gap30:
Hi firstly thank you i managed to get twrp on my OTT M8s following your instructions with the link to post 900~

Now i have made a complete backup of my rom but when i try to update a different rom it always reloads my original rom - It goes through the updating apps process but is always my stock rom

Now when i say stock rom that is a bit of a lie, i bricked this box within 20 mins of getting it and had to find a compatible rom, i ended up having to use the usb flashing tool and shorting out pins 28 and 29

there is a problem in the recovery/bootloader/u.boot bin somewhere that will not let me update the firmware

I am currently on a ap6330 but have had it on bcm4335 previously (go figure)

Also when i tried to update it to the latest acemax firmware last night it said 'this rom is for n200c and this box is k200 etc' but CPUZ clearly states my box is a n200c (again go figure)

I am by no means an expert on the file system of Android as a whole but am pretty experienced in flashing roms/cyanogenmod/xposed/twrp etc

Getting twrp running is a small achievement in itself....
[Android Stick & Console AMLogic based Computers] Shoog03:
It seems that the stock recovery process for installing OTA's checks signatures and will not allow "incompatible" ROM's to be flashed. The only way to get a ROM on there would be to find a full TWRP backup of that ROM and sidestep the standard recovery process.

I am still having issues with mine in that now that I have a working version of Openelec 6.0.0.2 it will not allow me to use the standard method of installing Openelec to downgrade to the 5.95.5 version. I am very happy with the way that Openelec performs, but without AV output it is a dead duck for me.

Looks like it was a wise move to do a full TWRP backup of the Android system as it seems that is the way I am going.

Stephen
[Android Stick & Console AMLogic based Computers] gap30:
Hi Stephen

Yes been trying to update and continually getting the E:error executing updater binary in zip

Could i take the meta-inf file from my working rom and swap it out?

I am not familiar with the more complicated stuff :/

See this comment by abdul in another forum:

On newer versions i have changed device id to k200. What device do you have ? I don't recall having made a TWRP for the MXQ.

That check is made by the update-script inside the flashable zip, I DID NOT MAKE IT CHECK. And "toggle signature verification" is there but it's not related to this.

Just delete the assert in update-script or use a newer version
[Android Stick & Console AMLogic based Computers] gap30:
I have been messing about with some roms and now i cannot restore my backup:/

E: unable to mount storage

Got a feeling i am going to have to start from scratch with usb burning tool
[Android Stick & Console AMLogic based Computers] Shoog03:
USB Burn tool will generally solve most issues. Only once or twice did it fail to find my Box and then the NAND shorting trick sorted that out.

Stephen
[Android Stick & Console AMLogic based Computers] mattmartinolc:
I have the exact same PCB board M8 V8_8 and am also trying without success to get openelec running on it. Can you please explain the steps and firmwares you were using please and thank you - you are a god to me right now lol