yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There isn't one for the T999L. You can't downgrade it.
[T-Mobile, Samsung Galaxy SIII] alarmdude9:
I misread it damg nab it
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Read back the last few pages of the unlock thread. Couple of people found a service that'll do it for $5.

---------- Post added at 01:46 PM ---------- Previous post was at 01:40 PM ----------

I posted a link in my last post in the unlock thread.
[General Questions and Answers] jackdubl:
Anyone have problems with the Google search app not giving any results after typing something? It seems to happen a lot to me lately. Then, if I use the voice input to run the exact same search, it gives results instantly. If I type the words and hit search, the circle just keeps spinning but no result come up. It's getting to the point that I'm starting to look for alternatives. Anyone else notice this?
[General Questions and Answers] immortalneo:
Try clearing app data/cache of Google Search app. :)
[General Questions and Answers] bharathv499@gmail.com:
Clear app cache.
[Xperia Z1 Q&A, Help & Troubleshooting] paullu:
I purchased z1 from uk and come with free smartwatcher also with FREE SONY ENTERTAINMENT CONTENT

the question is how can I get it?free movies games? because when I try to install xperia privilege app from play store

it said region not support? I am in USA anyone know how to get this offer?
[Android Software Development] dolorespark:
[Obsolete] Remove Screenshot Button / Add Instant UI Switcher

The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.

If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.

If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.
[Android Software Development] Trekker56:
Good work. Hope to see more devs and more Roms :)
[Android Software Development] PesSarmiento:
Really good. I'm using it right now. Keep going with the good work
[Android Software Development] helluvaman:
Good Job! Looking forward to more posts!
[Android Software Development] gberpa:
Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.
[Android Software Development] lordroy:
Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!
[Android Software Development] kc12:
Thank you. Your ROM runs smooth and fast.
[Android Software Development] DavidSnake:
Great work man, downloading it now! Thanks!
[Android Software Development] taba4real:
Antutu result for this ROM

12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
[Android Software Development] tinybeetle:
Installed and working. Thanks.
[Android Software Development] larryf:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.

Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.

Larry
[Android Software Development] lordroy:
Why am I getting 10500 on this ROM then?
[Android Software Development] jhienk:
Does this root and cwm change kernel like xbox's?
[Android Software Development] Cooter007:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.

EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.

https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
[Android Software Development] lordroy:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
[Android Software Development] Cooter007:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.

My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
[Android Software Development] lordroy:
Of course as soon as I mention something, my Sero decides to play nice.

Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.
[Android Software Development] taba4real:
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good:
[Android Software Development] MrSimmonsSr:
I doubt it is in your head. I'm rocking a Galaxy S3 as well for comparison... Good luck!
[Android Software Development] dolorespark:
Update to SystemUI/Phab7 package

I've updated the package described in post #3 that removes the screenshot button and adds Phab7, an instant UI switcher.

If you've already installed an earlier version of that mod and would just like to upgrade to the latest version of Phab7 (v0.95), please see this thread for details and a download link.
[Android Software Development] taba4real:
NFC

NFC still not working for this rom?
[Android Software Development] MrSimmonsSr:
I could be wrong, but I think you might be confusing this ROM with some of the Android 4.3 and 4.4 work that Randomblame has been working on. NFC is not working on those, but I think it is working on this one. This one is based on the stock ROM from Hisense and I think NFC is working.. I could be wrong and I apologize of that is the case..
[Android Software Development] jerbear294:
Correct. I am on the Dopa rom and NFC works fine. It doesn't work on randomblame's ports of Jellytime and taktiK, but according to davepmer, it's because for Wifi, Bluetooth and NFC, the Sero uses something similar to the Nexus 4 chipset. And it seems he fixed it.

This is from a PM:
[Android Software Development] davepmer:
Correct I have changes that should fix the NFC, working fine on mine with cm-11 waiting for Randomblame to check them out.
[Android Software Development] taba4real:
sorry for this question, can you direct me to the updated one? thank you!
[Android Software Development] davepmer:
Not yet, was wanting to wait for Ramdomblame to take a look at it.
[Android Software Development] taba4real:
thank you for your reply... will wait then...
[Android Software Development] solomon4400:
Hey does any one know if this rom will work on Canadian 8gb version?
[Android Software Development] NubzX:
Seems a little snappier compared to stock and of course I like the bloat crap gone.

Re!oved a few things you had in there that I didnt like (preference not a put down).

Anyway thank you for your work and hoping that it hasnt been abandoned.
[Android Software Development] jerbear294:
Show us the partitions. If they're the same as the US one odds are it will work.
[Android Software Development] LivinOne:
Trying to root and not getting it to work. (I've rooted 6 Android devices over the years so not a noobie)

1st problem, still might be an issue... I could not get the Sero drivers to install until I edited android_winusb.inf to add below line to both [Google.NTamd64] and [Google.NTx86] ...

; Sero7Pro ADB IDs

%AdbInterface% = USB_Install, USB\VID_109B&PID_9106&REV_0232

Seems like my hardware ID is different than others?

BUT, I tried running both XE_Sero7_Pro_Root and sero7pro-root-win-dopa ... neither see the Sero connected to Windows? I do have 'Android ADB Interface' showing under 'Android Phone' in Device Manager... is that correct?

thx for the help!
[Android Software Development] jerbear294:
If you're computer is x86,the drivers for ADB in the Xboxexpert package are only for x64. The Dopa one has x86 drivers.
[Android Software Development] LivinOne:
I'm running in7 Pro x64.

Problem was drivers included with BOTH Dopa & XBoxexpert did not recognize my Sero Pro.

After finding http://xdaforums.com/showthread.php?t=2442491 I installed SnapPea application which FINALLY installed the proper Hisense ADB drivers and Dopa's root worked fine.

I hope someone updates the first post to help others as I just spend 4 hours working on this.
[Android Software Development] dolorespark:
I was at work and away from my tablet so I couldn't comment knowledgeably while this discussion was going on. However...

If you used the package I posted, it includes "USB\VID_109B&PID_9106&MI_01" (as I'm sure xboxexpert's does), so that shouldn't have been the issue. Once you could report that "I do have 'Android ADB Interface' showing under 'Android Phone' in Device Manager", Windows was set up properly.

What I wonder is whether you ran my "step1-adb.bat" script. ADB only knows about devices with Google's own USB Vendor ID. It has to be told to look for other vendors' devices. That's what this script does - without it, the device won't be recognized. Then too, "USB Debugging" has to be enabled under "Developer Settings" in the system's Settings app. Again, without this, the device won't be recognized.

If there is some as-yet-unrecognized problem with the package I posted, then I'm sorry I wasn't around to help because this is the first report of any problems since it was posted 2 months ago.
[Android Software Development] LivinOne:
I'm pretty seasoned at rooting, this was not a rookie mistake or missing something. The IDs in your INI, and all other INIs I found did not have the ID my Sero has. The drivers SweetPea installs work 100% and allowed me to run your BAT files without issue. My Sero is rooted and running your ROM (very nice btw - thanks you!)

in case you want to research, my Device Manager now shows

Hisense Composite ADB Interface

w/ Hardware ID : USB\VID_109B&PID_9106&REV_0232&MI_01

BUT, when I first plugged in the Sero and it was under unknown devices as...

M470BSA

w/ Hardware ID : USB\VID_109B&PID_9106&REV_0232

.... note the difference in IDs from what you, and all other INIs have.

As I explained, I tried to add the lines in INIs to get it to work, but while that allowed ADB drivers to 'attach/install' - running any root kit (your BATs or others) did not allow the root apps to "see" any devices, thus the daemon started and sat doing nothing.

I'm curious if anyone else has seen, or starts to see, this problem as new people start getting recently releases Sero Pros.
[Android Software Development] kngdmond:
Just to give you a heads up....Hisense as of 10 minutes ago via Facebook, said they will be releasing the source code in a few days. Although that is all they said. Didn't mention for what version.
[Android Software Development] kngdmond:
Here's the link to the Sero 7 Pro firmware-sources:

http://hisense-usa.com/support/firmware/Sero 7 Pro_kernel_opensource_us.tar.gz
[Android Software Development] Talon65442:
dolorespark,

Any chance you're working on an updated version?

I have to reflash and will wait a bit on it if you are planning on a new release.

Just bought Modern Combat 4 on sale for $0.99 and realized I was going to need to move some files so I'd have enough space to install the 1.9-some-odd-GB.

Decided that since Calibre Sync won't let me choose where I get to store my books (only 'Internal' shows *shrug*), I'd fire up FolderMount and link them to my SD card...

stuck at Requesting Root...

ok, close that, Open SuperSU, check logs, FolderMount isn't in the list (ok, maybe I last used it when I previously had Superuser installed).

Reopen FolderMount, stuck at Requesting Root...

Open ESFileExplorer, have root...

Reopen FolderMount, stuck at Requesting Root...

Back to SuperSU, let's try the option of making it a system app (which will automagically reboot for me)...

screen goes off, screen comes on, Hisense logo displays, black...

black...

yeah, screen backlight is still on, black...

OK, recovery, fix permissions...

black...

reflash su...

still black... *sigh*

reflash dopa1.1...

error 7 (right, build.prop is saying I have a Nexus 7)...

So, I'm done for the night... if you don't have a new version in the works, I'll just comment out the build.prop check and rezip then flash tomorrow (later today).
[Android Software Development] jerbear294:
What I would have done is find out where Modern Combat 4 saves it's files, create that folder, foldermount that folder and then download MC4.
[Android Software Development] dolorespark:
The check for an "m470" tests a different entry than the ones used to impersonate a Nexus7 so that shouldn't be the problem. Besides, you're in CWM when flashing & it has its own build.prop (actually, everything is in default.prop) and that hasn't been messed-with.

Random thought: if you have an external SD card in the slot, remove it and try to reboot.

Another thought: if you're in CWM, you might try backing up to a different SD card, then wipe out everything. When you're running again, you can try restoring just /data and /data/media/0. (If you do this be sure that /data actually was backed up - I've seen CWM claim to back up /data but leave an empty file on the external SD card.)
[Android Software Development] Talon65442:
Tried that after I woke up...

good luck getting ".../android/obb/com.gameloft.android.anmp.gloftm4hm" out of a google search for "Modern Combat 4 files" or "Modern Combat 4 data" even added the words location and SD...

I won't mention what the first 3 pages of results were for each search... don't wanna get banned :silly:

Even if I had successfully found the file path, the whole 'Foldermount being without root and unable to actually run' thing still kinda killed that option.

Thanks though!

Addendum:

just reflashed... when I went to reboot, CWM told me that I had in fact lost root. Up and running again, now to just edit the scripts for 180dpi, Phab7UI, flash 'em, re-remove the minor system bloat, re-convert my main apps to system (anyone else notice that the system partition on this thing is HUGE?), and

this time

have titanium make an update.zip of all those app conversions :eek:

Sidenote:

Don't you just hate it when you do a ton of work on one project, start a second similar project, finish the first project, then the second one... and then something goes wrong with the second project and you realize that all that backing up you just did...

The only reason you remember doing it is because it was for the project that didn't have problems. :crying:

Project 1 was get NOOKColor ready to give to a friend, Project 2 was get Sero 7 Pro (replacement for NOOK) setup for me.

---------- Post added at 06:09 PM ---------- Previous post was at 05:43 PM ----------

:facepalm: Why didn't I think of rebooting without the SD Card...

I seem to have a strange aversion to Nandroid backups... not sure if it's the amount of time, or the 'all-encompasing' nature of them, or that I don't feel like rebooting into recovery every time a system app updates (TB is scheduled to integrate into ROM nightly).

Anywho, backups of actual app data and files wasn't a concern (TB and per app internal backups are done almost daily).

Hmm... guess mine was

really

having issues then...

I wiped system 3x to see if getting rid of the .props would let me get past 'Status 7', no joy.

Once I commented out both lines in the update-script and rezipped, flashed just fine...

btw, still get Status 7 on 180dpi and phab7 zips, and my default.prop only has

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1

the two variables that the script checks are both located in build.prop however...

I just edited it to

#assert(getprop("ro.product.device") == "m470" ||
# getprop("ro.build.product") == "m470");

I suppose I could just change it so that checks for ro.product.device will accept "m470" or "grouper"

*shrug* running now.

Thanks for the help!

And WTFH is up with my novel length posts lately:confused:
[Android Software Development] nccruz:
where do I find gravitybox on the sero7pro dopa v1.1???? found gravity box after installing xposed installer....

should my model number be nexus7 after flashing dopa v1.1???

thanks....
[Android Software Development] jerbear294:
The build.prop was changed to Nexus 7 to make most market apps compatible. Some don't show up as working when they work fine on the Nexus 7.
[Android Software Development] rocketero:
thanks, it worked great in my Hisense Sero 7 Pro 8GB. I did my first CWM Nandroid backup, good to have it around.

thumbs up!

---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
[Android Software Development] slicingtaco:
Any reason for this error???
[Android Software Development] Talon65442:
The assert failed line tells you what happened. It was checking the build.prop(? been told it checks somewhere else?) to make sure you aren't trying to flash to a non-compatible device.

It could be that <tab> (looks like a tab on the screen) or <carriage return> (seems to be treated like a carriage return{AKA new line} in Notepad++) in the script that is breaking the check...

Just take the 'updater-script' file (no file extension) and comment out the lines

#assert(getprop("ro.product.device") == "m470" ||
#getprop("ro.build.product") == "m470");

and re-zip

Personally, I edit it to check for Sero 7 Pro

or

Nexus 7 (should only work if you have a Sero 7 Pro with or without build.prop edits to look like a Nexus 7 to Play Store and other stuff)

This works because the ro.build.product apparently doesn't get used by the system. Comments in build.prop state but it can still be checked from script.

Since it doesn't actually get used by the system for anything, it's still shown as being our original value of m470 (Sero 7 Pro)
[Android Software Development] dolorespark:
Posting a photo of a tablet taken at an angle with significant glare from the lighting wouldn't normally be overly helpful in trying to identify what the problem is, much less identifying its cause. However in this case, I think I can identify both.

You got an assert error when the DoPa update zip tried to confirm it was installing on an m470. The problem is caused by using a version of CWM that doesn't correctly identify the tablet (randomblame's, I'd assume). You can either switch CWM versions to one that does, or you can unzip the update and edit the updater script to remove the test.

Note: the reason for the test is to prevent our friends in Britain, Australia, and elsewhere from trying to flash a ROM that would brick their tablets.
[Android Software Development] Talon65442:
Do we have a flashable CW Touch 6.0.3.2 or should we just use adb script #3 from yourRoot/CWM packageshttp://xdaforums.com/showthread.php?p=46196739&postcount=2?
[Android Software Development] dolorespark:
The one named step3-cwm.bat will install xboxexpert's compile of CWM Touch (and nothing else). It identifies the tablet as an "m470". Sorry for the hassle, but I think a bit of caution is called for when a package could cause some people a lot of grief.
[Android Software Development] Talon65442:
Can't say I disagree with you... sorry if I've been a bit of a (gigantic) pain!

Now to see if we can get one version of CWM that will work for flashing DoPa

and

taktiK that still correctly identifies the device (preferably CWM Touch).
[Android Software Development] slicingtaco:
Agree, sorry to bother you like that. I did try tinkering with the updater-script earlier by switching m470>grouper but it didnt work so i turned to you guys.
[Android Software Development] Talon65442:
No worries, that's why were all here, to get help and help people with their android devices!

Seen you over in the tiktaK thread too, IIRC, the CWM Touch 6.0.3.2 (xboxexpert's compile of CWM Touch) won't work with tiktaK and as dolorespark has pointed out, the CWM 6.0.4.5 that randomblame compiled won't properly pull the identity of the tab (hopefully that's the only thing it does wrong)...

Am looking at several pages of info on compiling a new CWM... looks like it will be a few days before I can even try it. Need to get my flashdrive back from a friend to put ubuntu on.
[Android Software Development] johnb380:
Deleted
[Android Software Development] gberpa:
Stuck at 'Recovery'

Using either 'power button + volume down' or Power or Quick Boot, I am unable to get into Recovery. It locks at the Recovery screen. Don't know why this is happening. I briefly tried TWRP form the play store but removed it. I can reboot but wanted to make a new CWM backup and also try installing randomblame's TWRP w/theme. One concern I have with CWM, I can't find my backups on my SD card so they must be in internal memory.

update:found the CWM backups in data/media and copied to the SD card and my PC.
[Android Software Development] dgjenkins:
You could download "flashify" from the play store and then flash cwm from the OP from there. Assuming your recovery is currently corrupt that should write over it.
[Android Software Development] gberpa:
Up and running again with CWM. I used suggestion by DoPa to run her Windows install package for the ADB drivers and CWM flash in Post#2 or so.
[Android Software Development] cammykool:
Nevermind wouldnt be a bad idea to READ lol
[Android Software Development] Talon65442:
Nope, no reading allowed in here. You have to turn off your screen and use Text-to-Speech!
[Android Software Development] dolorespark:
USB-OTG support package

I've posted a new package (sero7pro-usbotg-dopa-v1.1.zip -see OP) that enables you to connect USB drives to your tablet. It works with the current DoPa v1.1 ROM and may work with xboxexpert's.

Drives are automatically mounted at /usbdisk when attached. There's no built-in way to unmount them, so use caution when detaching a drive you've just written to (if needed, you can do a clean umount using "adb shell umount /usbdisk"). Unmounting shouldn't be an issue if you're only reading from the disk.
[Android Software Development] kibachris:
When I got my tablet, I had the same issue (It should be noted I received the tablet pre-loaded with P756.6.02.20); the MAC address would flip to a variation of 00:34:9a- every time I toggled the wifi or reboot the tablet, which got frustrating because every time that happened, I'd have to re-register my device at work. I rooted and installed taktiK R10, same problems. In resignation, I flashed the P756.6.02.11.00 stock rom from the XE-SeroROM v².² page and my MAC address now begins with 00:1a:99 and stays the same after toggles and reboots. I'm now running XE-SeroROM v².² and I think I'm content with the older OS, sans-wifi issues.
[Android Software Development] nccruz:
Using dopa 1.1 and it started getting laggy..... Cleared browser cache and everything seems OK again..... Anyone else?
[Android Software Development] dolorespark:
Interesting... I recently discovered that the mac address is passed to the kernel on its commandline by the bootloader. I just looked at the kernel code that parses and validates the value and it seems OK - but apparently it isn't. It would be really helpful if someone with this problem could post their commandline. To do so, run adb shell cat /proc/cmdline. You'll get several lines of stuff; what we're looking for is something like this: 'wifiaddr=00:1A:98:68:A2:43' (if you consider this to be "privileged information", send it to me in a PM) Please don't change the value or formatting since that may be where the problem lies.