Database Develop

locked security warning by doing nothing

okay guys this is weird. til now i have only read the forums and did think about rooting my phone to install a custom rom because the latest htc update made my phone so horrible. but now anything changed cause this just happened:
i got an sms (using the preinstalled sms app) and answered to it. send the phone to "sleep" (?) by pressing power button once, like always. laying the phone back on the table, continuing playing darksiders2. maybe 5 minutes later the display brightens up by itself like if an incoming call but nothing happens. i grab the phone and try to press anything or swipe to see whats going on, but no input gets recognized. plus the button row doesnt get lighten up like normally. confused i tried to press the power button but even that shows no reaction. it just stayed that way, nothing i could do. because i had one freeze under 2.3.5 or so i took the battery out to do a hard reset. booting up again gets me now into the screen i only read here before: where you have to go to install roms from zips etc. but i have booted normally, without pressing the volume keys. the title row says: locked, security warning. rebooting the phone out of this only gets me back here. i dont get it. i mean i know this version is messed up but what is this? my phone is broken and i havent even tried to unlock or anything else it... my god. i dont know what to do. next week is coming up and i dont have multiple phones.
has anyone any idea? please help!
ps: please forgive me any language flaws, english isnt my mother tongue.

Possible solutions
- Wipe the data from recovery if you can, or from bootloader
- Install the ruu when you had before

What country are you/the phone from?

And give us the output of the command
Fastboot getvar all
Sent from my HTC Incredible S using xda app-developers app

hello, thank you for your replies!
i bought the phone over amazon.de and i'm from germany.
where do i have to write "Fastboot getvar all"? do i need to install something and connect the phone to usb or anything like that? i mean i read about some incS roms on the forums but never tried anything myself so i have to look into that first on how to set things up..
edit: so i finally managed to setup android sdk adb and get this command running. yay!
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-baseband: 3831.18.00.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4069mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e50e7
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s
Click to expand...
Click to collapse

I think your best option is to just run the ruu http://d-h.st/7UC

ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?

benutzer001 said:
ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?
Click to expand...
Click to collapse
It is an executable program. Just run it on a Windows PC and follow the instructions.

ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?

benutzer001 said:
ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?
Click to expand...
Click to collapse
I don't know why this happen but yes everything will be gone.

i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.

benutzer001 said:
i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.
Click to expand...
Click to collapse
Try it again.

error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..

benutzer001 said:
error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..
Click to expand...
Click to collapse
Do you have the HTC Sync app installed on your PC? If so, make sure it is not running in the System Tray or remove it all together and try again.
If you don't have HTC Sync installed, then install it to get the current drivers and then you can uninstall it and try it again.

which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.

benutzer001 said:
which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.
Click to expand...
Click to collapse
You can extract the Rom.zip file that the ruu is using and update manually.
Start the ruu software and stay on the first screen.
In your Start>Search programs and files box type %temp% and press enter. A temp window should appear.
search for rom.zip in that window and copy this file to your fastboot dir.
Now you have 2 options. Flash through fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
or rename rom.zip to PG32IMG.zip, copy to your sdcard root, reboot bootloader(hboot mode) and let the bootloader detect the zip and install.

Nonverbose said:
and copy this file to your fastboot dir.
Click to expand...
Click to collapse
where is my fastboot dir? for the adb commands i've setup an android-sdk-windows folder in C: but nothing else.
just running the "fastboot oem rebootRUU" command from somewhere gets me this:
C:\Users\XXXX>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(730): error 2
OKAY [ 0.052s]
finished. total time: 0.055s
Click to expand...
Click to collapse
i am doing all this with my bare phone, no sd and sim card inserted. is it necessary to backup my sd card and insert it?!
and does everything needs to be done in an elevated cmd?

Looks like hardware failure. Try the PG32IMG.zip method but I don't like your chances. From what I see, you did everything right.

so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?

benutzer001 said:
so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?
Click to expand...
Click to collapse
I think you have fried emmc chip. Some batches of incS are notorious for it. It commonly occurs by powering down by removing the battery, but It's possible that it just died.
If you have another sdcard, I would try that before giving up hope. You should be able to copy the pg32img.zip by entering hboot USB mode.
edit: I had look back at your previous posts and noticed you didn't have sdcard inserted. It should be installed in the phone.

[Q] Fastboot detect USB but adb doesn't [SOLVED]

Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!

fenix71230 said:
Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!
Click to expand...
Click to collapse
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.

attanasi0 said:
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.
Click to expand...
Click to collapse
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !

fenix71230 said:
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), and which ROM you are/were using. (you say no OS installed, how did you wipe it?) post more details so we can figure out where you are at.

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data

fenix71230 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data
Click to expand...
Click to collapse
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that

nkk71 said:
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that
Click to expand...
Click to collapse
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.

fenix71230 said:
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.
Click to expand...
Click to collapse
adb should work in CWM (I had one version that didnt, but the rest should), so just because it works for me, can you download the following one:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
Once you've downloaded and verified MD5:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
and confirm "adb devices" now shows you are connected. we'll proceed from there.
BTW: hboot 11 March 2013 is good for revone, I'll PM you a link for a ROM that works for that when you confirm adb is working.
EDIT: can you copy/paste you command prompt as you do the above mentioned fastboot commands.

All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Pc has well installed USB composite device, Mass storage USB device, won't install Android Phone : device disconnected, well installed HTC Android Phone USb Device
When I type adb devices it detect nothing I fear a hardware failure?
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.064s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot flash recovery recov
ery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.143s]
writing 'recovery'...
OKAY [ 0.649s]
finished. total time: 1.794s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.053s]
finished. total time: 0.053s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>

I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!

fenix71230 said:
All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Click to expand...
Click to collapse
This is normal.
fenix71230 said:
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.

nkk71 said:
This is normal.
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.
Click to expand...
Click to collapse
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone

stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
I've done all that and after my PC won't install : USB MTP device, Android Phone

fenix71230 said:
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone
Click to expand...
Click to collapse
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!

nkk71 said:
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!
Click to expand...
Click to collapse
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:

fenix71230 said:
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:
Click to expand...
Click to collapse
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:

fenix71230 said:
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:
Click to expand...
Click to collapse
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.

nkk71 said:
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.
Click to expand...
Click to collapse
How can I update the title ?

fenix71230 said:
How can I update the title ?
Click to expand...
Click to collapse
go to your first post and EDIT it, at the bottom of the edit window there's GO ADVANCED, once you click that you can see the main thread title and change it to include [SOLVED]

stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU!
Fixed finally!

[REQ]Dump of the preinstalled rom

Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all

Enabling debugging is pretty simple:
Settings -> About -> Tap the build number 7 (I think) times.
Enable debugging.
Allow debugging from the prompt that appears on the paired device.
I was able to do a system dump and will post it as soon as I have developer status on Android File Host.
I was unable to run the fastboot command though. It seems you need to have the device actively connected in order to authorize adb access.
Here's a link to the dump: http://www.androidfilehost.com/?fid=23501681358554418

unkillable_thrill said:
I was unable to run the fastboot command though. It seems you need to have the device actively connected in order to authorize adb access.
Click to expand...
Click to collapse
If you already have adb access, you can also do
Code:
adb shell getprop ro.boot.bootloader
for the same results.
Could you also list the model number?
It's SM-??? something, there's pictures of the back of the device, but the ones I saw were too blurry to make it out.

Here is the first part of the build.prop and the bootloader. It just says "NF5"
Code:
> adb -s localhost:4444 shell getprop ro.boot.bootloader
NF5
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KMV78N
ro.build.display.id=KMV78N
ro.build.version.incremental=1245698
ro.build.version.sdk=20
ro.build.version.codename=REL
ro.build.version.release=4.4W
ro.build.date=Mon Jun 23 21:00:37 UTC 2014
ro.build.date.utc=1403557237
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfk1.cbf.corp.google.com
ro.build.tags=release-keys
ro.product.model=Gear Live
ro.product.brand=samsung
ro.product.name=sprat
ro.product.device=sprat
ro.product.board=SPRAT
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.wifi.channels=
ro.board.platform=msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sprat
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sprat-user 4.4W KMV78N 1245698 release-keys
ro.build.fingerprint=samsung/sprat/sprat:4.4W/KMV78N/1245698:user/release-keys
ro.build.characteristics=nosdcard,watch
# end build properties
I can do a dump, but it takes far too long and i have a busy day today, if I have time later ill try to do a full dump and put it up on Mega

I would appreciate if either if you two could do a dump, if it means having to wait that's perfectly acceptable.
Edit:
Daegalus said:
Code:
ro.build.date=Mon Jun 23 21:00:37 UTC 2014
Click to expand...
Click to collapse
Do you know if your gear live/the one you had access too had an ota? that's very new for a rom, it seems like it already recieved an ota due to the age

I don't know. I got it an Google I/O on Thursday. Also when I first turned it on, I think it got an update of some sort when it did the first sync so I think it had some kind of initial OTA applied.
I think i might have some time in a bit to do a full dump of /system I'll try to get it done quickly.
[Edit] I will also try to get it into Fastboot and see if I can do a proper full dump. Im just a little hesitant as I wouldn't know how I would interface with fastboot as the watch requires a connection through the phone's bluetooth to do ADB. I don't know if I can connect a USB directly to it through the adapter and do actual fastboot operations.

Daegalus said:
I don't know. I got it an Google I/O on Thursday. Also when I first turned it on, I think it got an update of some sort when it did the first sync so I think it had some kind of initial OTA applied.
Click to expand...
Click to collapse
If anyone happens to get a gear live that has not been turned on yet, could you attempt to get the rom before it connects to the internet?
I have no idea what the pair process is, so I cant provide any advice to that end.

TheManii said:
If anyone happens to get a gear live that has not been turned on yet, could you attempt to get the rom before it connects to the internet?
I have no idea what the pair process is, so I cant provide any advice to that end.
Click to expand...
Click to collapse
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.

Daegalus said:
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.
Click to expand...
Click to collapse
That sounds effectively like the setup for the 2013 N7, you need to modify the rom to bypass that, or make it think you already finished the setup process.
Both of which requires fastboot to bypass via a custom recovery. I expect that you can eventually flash a custom recovery on a wear, but not simply with fastboot.

Well once i finish this system dump, I will try to get it into fastboot with "adb reboot bootloader" or something. Hopefully Samsung hasnt done the usual thing and locked it down like a high security prison.
---------- Post added at 05:04 PM ---------- Previous post was at 04:16 PM ----------
I did this dump on Windows, I just replaced my macbook so I havent got it setup to do any of this, so I resorted to my windows machine. Heads up incase it causes file permissions to be off.
Samsung Gear Live /system dump: https://mega.co.nz/#!SVACgawC!sFYfSgvLOIdwlDyP_r-7voggecZNwRkrnarQ4Y_SZkU
fastboot getvar all:
Code:
PS C:\Users\Yulian\Desktop\SamsungGearLive> fastboot getvar all
(bootloader) console:disable
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:true
(bootloader) unlocked:false
(bootloader) secure-boot:yes
(bootloader) version-baseband:NONE
(bootloader) version-bootloader:SPRAT.NF5
(bootloader) version-hardware:4
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:persist:ext4
(bootloader) partition-size:persist: 0x700000
(bootloader) partition-type:recovery:ext4
(bootloader) partition-size:recovery: 0xa00000
(bootloader) partition-type:boot:ext4
(bootloader) partition-size:boot: 0xa00000
(bootloader) partition-type:aboot:ext4
(bootloader) partition-size:aboot: 0x200000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xc800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xc14abe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x10000000
(bootloader) serialno:R3AF600G54J
(bootloader) kernel:lk
(bootloader) product:sprat
all:
finished. total time: 1.251s
I will see if I can dump anything from fastboot.
---------- Post added at 05:17 PM ---------- Previous post was at 05:04 PM ----------
For anyone else with a Samsung Gear Live, here are the steps to get it setup.
1. Enable Debug over Bluetooth.
2. Enable debugging in the Android Wear app on your phone.
3. Use the instructions here: https://developer.android.com/training/wearables/apps/bt-debugging.html to setup a connection to the watch through the phone BT.
4. You should have adb access now, and you can run 'adb reboot bootloader'
5. Once booted into the bootloader you, you can connect the USB adapter to the back of the watch and hook it up directly to a computer and run normal fastboot commands on it. Including 'fastboot oem unlock'. I havent run this yet, but wouldn't see why it couldn't be done. This should allow flashing of custom recoveries.
The watch has a standard android recovery and bootloader enhanced with touch support so you can navigate them with swipes. I'll post pictures once my phone charges a bit.

Daegalus said:
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.
Click to expand...
Click to collapse
Is adb over USB expected to work? I tried in the pre-pair state, and two different computers both failed to detect the device as a USB device at all.
I kind of suspect that, before the initial pairing, the device has an extremely limited image installed. But there are five USB pins, so presumably the device contains USB gadget hardware.

I have not been able to do ADB over USB. It does have data bit. I did fastboot over usb, as there is no bluetooth when in the bootloader. So it is possible to do data over usb, not just power.
The issue is, when you are booted into android, it doesn't let you do ADB over USB, at least not by default or with the options given to you. I can only do over Bluetooth.
I think what Manii said earlier applies. We won't be able to do anything to bypass the forced update or hookup adb unless we get custom recovery on it and do a custom bypass like the 2013 N7
Here is an image of the bootloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm not at all surprised that it has a standard android recovery, as it's a goog rom device.
The issue is if you can return to fastboot without adb, what if you broke the rom and cant boot.
If anyone seriously want to dump the initial rom though: you'd both have to wait until a recovery is ported (whenever that is, due to dev interest) and also obviously cant pair it until then.
We have dumps of the initial roms for the 2013 n7 and N5 this way, but I dont really expect as many wear users.

Also @TheManii , you mentioned earlier you wanted the model off the back. Its SM-R382 on mine.

Can someone please make a quick port of this to the Original gear? It's pretty much the same and I would be willing to test. Had to ask here since there is not much going on in the Gear Forums.

uvbeenzaned said:
Can someone please make a quick port of this to the Original gear? It's pretty much the same and I would be willing to test. Had to ask here since there is not much going on in the Gear Forums.
Click to expand...
Click to collapse
I second this... Would love it on my OG Gear
Sent from my Nexus 5 using Tapatalk

Ep3n3wp said:
I second this... Would love it on my OG Gear
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I would love this to!

By the looks of it the Gear 1 originally ran 4.2.2 (JDQ39), the Gear live runs 4.4W (KMV78N).
The Gear 1 also has an exynos 4 and the Gear live is a snapdragon S400.
They're different enough that it's like asking to port KK to any abritrary android device.
You may as well be asking someone to port tizen to the N10.
It's not impossible for either case, but it's nowhere as easy as it sounds.

TheManii said:
By the looks of it the Gear 1 originally ran 4.2.2 (JDQ39), the Gear live runs 4.4W (KMV78N).
The Gear 1 also has an exynos 4 and the Gear live is a snapdragon S400.
They're different enough that it's like asking to port KK to any abritrary android device.
You may as well be asking someone to port tizen to the N10.
It's not impossible for either case, but it's nowhere as easy as it sounds.
Click to expand...
Click to collapse
Well could you do it for us? You sound like you know what you're doing. There can be a PayPal donation involved.
Sent from my Nexus 5 using Tapatalk

The system doesn't matter nearly as much as the kernel.

Amazon Fire 7 (2015) 5.1.1 Stuck in Bootloop with No Recovery. Help ):

Hi all,
This is my first post here as I've been using XDA for years without issue, following other threads and seeing the community thrive. But i've gone and got myself stuck.
I recently got the 2015 Amazon Fire 7 and upon tuning it on, it updated to 5.1.1 after this I quickly saw how awful Fire OS is. I rooted (Thanks to RootJunky's Supertool) Installed GAPPS and Nova launcher, before I realised it's potential was wasted with the Fire OS.
After this I used another RootJunky tutorial to use Flashfire and install SlimLP with GAPPS.
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
My question is; Does anyone know how to install anything without Recovery, ADB or a functioning device? This has been the hardest device I've ever tried to root, and now I'm stuck.
Thanks in advance guys

5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.

glitch3yf0x said:
5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.
Click to expand...
Click to collapse
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.

DizzyJK said:
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.
Click to expand...
Click to collapse
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)

i cannot get to recovery using the volumeup and power it gets stuck with amazon logo , rootjunky says there is some issue in 5.1.1 after using flashfire to get in to recovery

glitch3yf0x said:
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)
Click to expand...
Click to collapse
Sorry to sound stupid, but could you explain how I would do it? I've tried to sort the SDK before and just either got it completely wrong (most likely) or just not understood what it is I'm meant to be doing.
Volume Down leaves me hanging at the 'Amazon' start up screen. I'm assuming this is the recovery mode without the options? So from here, sideloading should be completely possible with a fixed ADB command?

can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance

See this video and make sure to push the correct button.
https://www.youtube.com/watch?v=RQLoH-ahjy4

fastcar22 said:
can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance
Click to expand...
Click to collapse
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
That has been the problem I am facing; when pushing Vol Down +Power it hangs on the Amazon logo. From what others have said, I believe this is the recovery mode but as it doesn't have the options I need, I don't know how I would go about applying the ADB update.
I will try all the steps you have mentioned when I get back home today and report back. I have the stock ROM file and the drivers installed from the previous processes, but as everything I believe will have to be done via command prompt I just hope i'll be able to apply the ADB update that way.
Thank you very much for your help. I really do appreciate the time you've taken to help.

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.

I have the same problem, Amazon recovery was working at one point as i have used it before, but try as i may it will not boot now, all i have is fastboot and a flashing CM12 logo.

DizzyJK said:
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.
Click to expand...
Click to collapse
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also looks like dirty loading a Rom is a currently unresolved issue.

thekrakah said:
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
It also looks like dirty loading a Rom is a currently unresolved issue.
Click to expand...
Click to collapse
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.

DizzyJK said:
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.
Click to expand...
Click to collapse
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.

DizzyJK said:
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
Click to expand...
Click to collapse
Exact same boat here, long time lurker 1st time poster too. If anyone finds a solution please post here.

Davey126 said:
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.
Click to expand...
Click to collapse
You are an absolute genius! I got in touch with Amazon, told them exactly what I did and they sent me another out for free. It isn't the technical solution I was hoping for, but this more than makes up for it. Thank you so much for showing me this. I will still look for a solution to the problem, but I did get a free tablet out of the whole thing

If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.

northmendo said:
If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.
Click to expand...
Click to collapse
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?

Davey126 said:
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?
Click to expand...
Click to collapse
Confirmed, both commands just return you to fastboot (one flashed up an error). Absolutely no way to reboot into recovery or sideload that I've found.
If you allow it to boot normally, at the CM logo it connects as an unauthorized device so it is at least getting pasrt way into the boot. But without fully booting you cannot authorize the usb connection.
I think its unlikely a fix will be found for this, unless there's some unknown adb commands in fastboot that might work to somehow sideload a recovery or allow CM to at least boot.
---------- Post added at 11:03 PM ---------- Previous post was at 10:14 PM ----------
Maybe this helps somone:
I wonder if the fact it shows locked is causing the problems. >fastboot unlock or unlock-critical return an error, as does any of the flash commands.
The unlock code is interesting, but I have no idea what it means.
Code:
>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0x8eaXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.817s

ASUS ME176CE / K013C - Need Help with This Unicorn ...

I have this ASUS tablet and it's a nice one. It's got 1.8GHz Quad-Core processors and 2 GB of (actual) RAM. It was, apparently, issued for educational purposes by Google in their Android for Education program.
I was able to root the tablet - it accepted the same rooting method as the ZenPhone 5. Please ignore me calling this an ME176CX in the linked post - that was incorrect and I just now fixed it.
About the Tablet:
OS: Android Lollipop 5.0
Kernel Version: 3.10.20-x86_64_byt
[email protected] #1
Thu Mar5 16:30:07 CST 2015
Build #: LRX21V.WW_epad-12.9.3.19-20150305
BootLoader Info:
Variant: K013C 16
HW_Version: 2
Bootloader Version: WW_epad-12.9/3/19-20150305
IWFI Version: 200.7
Secure Boot: Yes
The major issues I have with it are:
Battery consumption is high.
Data partition is encrypted by the BootLoader.
BootLoader recovery fails.
System updates fail.
I understand that Lollipop 5 is a battery hog and I believe that is my battery issue - I restored a TWRP backup I made (without the data partition of course) and the tablet is currently running nothing but the OS and still consuming battery at about 10% an hour.
I would like to put on a different version or flavor of Android. Before that happens, I need 3 things:
My BootLoader Unlocked
My Data Partition unencrypted
A ROM that will improve battery consumption and maintain full functionality without bricking the tablet.
Can anyone help me with these issues?
I have searched the internet for a ROM or MOD for this tablet without success. In fact, there's very little info out there on this tablet at all. I suspect that ASUS tried to sell it for too much money, decided it was a flop and wound up donating it for educational purposes as some sort of tax break.
Here is a link to my Lollipop backup on Google Drive
Let me know if there's any additional information you need - any help would be appreciated. Thanks in advance.
Update: Oooh - found something! Teaching myself ADB and FASTBOOT commands and stumbled on this getvar command by chance - it may help people who know a lot more than me:
Code:
C:\[ADB Files Location]>fastboot getvar all
(bootloader) partition-type:reserved: hidden
(bootloader) partition-size:reserved: 0x0000000002e00000
(bootloader) partition-type:metadata: raw
(bootloader) partition-size:metadata: 0x0000000000100000
(bootloader) partition-type:ESP: vfat
(bootloader) partition-size:ESP: 0x0000000002100000
(bootloader) partition-type:boot: hidden
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:recovery: hidden
(bootloader) partition-size:recovery: 0x0000000001000000
(bootloader) partition-type:fastboot: hidden
(bootloader) partition-size:fastboot: 0x0000000001000000
(bootloader) partition-type:reserved_1: hidden
(bootloader) partition-size:reserved_1: 0x0000000002000000
(bootloader) partition-type:panic: raw
(bootloader) partition-size:panic: 0x0000000002000000
(bootloader) partition-type:factory: ext4
(bootloader) partition-size:factory: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000002000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000058000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000002bcff6e00
(bootloader) partition-type:mnt/sdcard1: vfat
(bootloader) partition-size:mnt/sdcard1: 0x0000000edda00000
(bootloader) max-download-size: 536870912
(bootloader) version-bootloader: 2.0
(bootloader) kernel: droidboot
(bootloader) product: baytrail
all:
finished. total time: 0.102s

Shadeclan said:
I have this ASUS tablet and it's a nice one. It's got 1.8MHz Quad-Core processors and 2 GB of (actual) RAM. It was, apparently, issued for educational purposes by Google in their Android for Education program.
I was able to root the tablet - it accepted the same rooting method as the ZenPhone 5. Please ignore me calling this an ME176CX in the linked post - that was incorrect and I just now fixed it.
About the TabletS: Android Lollipop 5.0
Kernel Version: 3.10.20-x86_64_byt
[email protected] #1
Thu Mar5 16:30:07 CST 2015
Build #: LRX21V.WW_epad-12.9.3.19-20150305
BootLoader Info:Variant: K013C 16
HW_Version: 2
Bootloader Version: WW_epad-12.9/3/19-20150305
IWFI Version: 200.7
Secure Boot: Yes
The major issues I have with it are:
Battery consumption is high.
Data partition is encrypted by the BootLoader.
BootLoader recovery fails.
System updates fail.
I understand that Lollipop 5 is a battery hog and I believe that is my battery issue - I restored a TWRP backup I made (without the data partition of course) and the tablet is currently running nothing but the OS and still consuming battery at about 10% an hour.
I would like to put on a different version or flavor of Android. Before that happens, I need 3 things:
My BootLoader Unlocked
My Data Partition unencrypted
A ROM that will improve battery consumption and maintain full functionality without bricking the tablet.
Can anyone help me with these issues?
I have searched the internet for a ROM or MOD for this tablet without success. In fact, there's very little info out there on this tablet at all. I suspect that ASUS tried to sell it for too much money, decided it was a flop and wound up donating it for educational purposes as some sort of tax break.
Here is a link to my Lollipop backup on Google Drive
Let me know if there's any additional information you need - any help would be appreciated. Thanks in advance.
Update: Oooh - found something! Teaching myself ADB and FASTBOOT commands and stumbled on this getvar command by chance - it may help people who know a lot more than me:
Click to expand...
Click to collapse
Its actually 1.3GHz that can reach 1.8GHz and Its GHz, not MHz, i havent made you the edited boot.img with encryption off because ive been a bit busy ill try to do it tomorrow and give it to you.

Ruben Craveiro said:
Its actually 1.3GHz that can reach 1.8GHz and Its GHz, not MHz, i havent made you the edited boot.img with encryption off because ive been a bit busy ill try to do it tomorrow and give it to you.
Click to expand...
Click to collapse
Thanks, Ruben - I fixed it.
Thanks for making the boot image - hope it works!

Shadeclan said:
I have this ASUS tablet and it's a nice one. It's got 1.8GHz Quad-Core processors and 2 GB of (actual) RAM. It was, apparently, issued for educational purposes by Google in their Android for Education program.
I was able to root the tablet - it accepted the same rooting method as the ZenPhone 5. Please ignore me calling this an ME176CX in the linked post - that was incorrect and I just now fixed it.
About the TabletS: Android Lollipop 5.0
Kernel Version: 3.10.20-x86_64_byt
[email protected] #1
Thu Mar5 16:30:07 CST 2015
Build #: LRX21V.WW_epad-12.9.3.19-20150305
BootLoader Info:Variant: K013C 16
HW_Version: 2
Bootloader Version: WW_epad-12.9/3/19-20150305
IWFI Version: 200.7
Secure Boot: Yes
The major issues I have with it are:
Battery consumption is high.
Data partition is encrypted by the BootLoader.
BootLoader recovery fails.
System updates fail.
I understand that Lollipop 5 is a battery hog and I believe that is my battery issue - I restored a TWRP backup I made (without the data partition of course) and the tablet is currently running nothing but the OS and still consuming battery at about 10% an hour.
I would like to put on a different version or flavor of Android. Before that happens, I need 3 things:
My BootLoader Unlocked
My Data Partition unencrypted
A ROM that will improve battery consumption and maintain full functionality without bricking the tablet.
Can anyone help me with these issues?
I have searched the internet for a ROM or MOD for this tablet without success. In fact, there's very little info out there on this tablet at all. I suspect that ASUS tried to sell it for too much money, decided it was a flop and wound up donating it for educational purposes as some sort of tax break.
Here is a link to my Lollipop backup on Google Drive
Let me know if there's any additional information you need - any help would be appreciated. Thanks in advance.
Update: Oooh - found something! Teaching myself ADB and FASTBOOT commands and stumbled on this getvar command by chance - it may help people who know a lot more than me:
Click to expand...
Click to collapse
the recovery doesnt fail, its normal in every stock recovery you have to press all buttons at same time to show available commands

Making Some Progress ...
Ruben Craveiro said:
the recovery doesn't fail, its normal in every stock recovery you have to press all buttons at same time to show available commands
Click to expand...
Click to collapse
Thanks, Ruben. I'm still learning this stuff. Probably be doing and saying lots of stupid stuff in this thread. However, if displaying my ignorance gets me a decent tablet, I'm OK with it. :silly:
Currently, I'm excited that I finally figured out how to load stuff back onto the tablet with ADB. Restoring the backup without the data partition blew away all the software, including the keyboard and some apparently necessary system apps. The Google Play app in particular seems to be having all sorts of problems, so that I'm unable to easily restore the software connected to my Google account. I think there's probably some sort of missing app connected with accounts that I'm missing.
I'm still in communication with ASUS - they want me to clear the cache on the DMClient app and try to restart the Lollipop upgrade but the DMClient app is missing - in fact, that may be the client piece that I have to restore to make Google Play work again. I'll look for DMClient on APK Mirror later. If you happen to have handy a list or link to a list of apps that should be on the tablet, that would save me some time.
Pressing all the buttons seems to put the tablet into some sort of FastBoot mode. To get out of it, I have to do a hard reboot. Shouldn't Recovery mode default to whatever is in the Recovery partition? If that's true, then either the data in the Recovery partition is bad or [more likely] Recovery mode has issues with the encrypted Data partition.
I appreciate your time and help, Ruben. You've been a big help through this whole tablet issue. Thanks:good:

Shadeclan said:
Thanks, Ruben. I'm still learning this stuff. Probably be doing and saying lots of stupid stuff in this thread. However, if displaying my ignorance gets me a decent tablet, I'm OK with it. :silly:
Currently, I'm excited that I finally figured out how to load stuff back onto the tablet with ADB. Restoring the backup without the data partition blew away all the software, including the keyboard and some apparently necessary system apps. The Google Play app in particular seems to be having all sorts of problems, so that I'm unable to easily restore the software connected to my Google account. I think there's probably some sort of missing app connected with accounts that I'm missing.
I'm still in communication with ASUS - they want me to clear the cache on the DMClient app and try to restart the Lollipop upgrade but the DMClient app is missing - in fact, that may be the client piece that I have to restore to make Google Play work again. I'll look for DMClient on APK Mirror later. If you happen to have handy a list or link to a list of apps that should be on the tablet, that would save me some time.
Pressing all the buttons seems to put the tablet into some sort of FastBoot mode. To get out of it, I have to do a hard reboot. Shouldn't Recovery mode default to whatever is in the Recovery partition? If that's true, then either the data in the Recovery partition is bad or [more likely] Recovery mode has issues with the encrypted Data partition.
I appreciate your time and help, Ruben. You've been a big help through this whole tablet issue. Thanks:good:
Click to expand...
Click to collapse
The fastboot you'r talking abiut is actuaky DnX mode that i know of its not meant ti be used as a regular fastboot but more to recovery the device from a hardbrick, The fastboot is where it says the info about the device, the unlock state, name and where it gives u options from where to boot... You can unlock the bootloader using jearbear method, since the only difference you have is that its a 2gb model

Ruben Craveiro said:
The fastboot you'r talking abiut is actuaky DnX mode that i know of its not meant ti be used as a regular fastboot but more to recovery the device from a hardbrick, The fastboot is where it says the info about the device, the unlock state, name and where it gives u options from where to boot... You can unlock the bootloader using jearbear method, since the only difference you have is that its a 2gb model
Click to expand...
Click to collapse
Do you have a link to JearBear's method?

Shadeclan said:
Do you have a link to JearBear's method?
Click to expand...
Click to collapse
its actually jerbear, my bad xD
Here it is: https://forum.xda-developers.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603

How i install it?
Shadeclan said:
I have this ASUS tablet and it's a nice one. It's got 1.8GHz Quad-Core processors and 2 GB of (actual) RAM. It was, apparently, issued for educational purposes by Google in their Android for Education program.
I was able to root the tablet - it accepted the same rooting method as the ZenPhone 5. Please ignore me calling this an ME176CX in the linked post - that was incorrect and I just now fixed it.
About the Tablet:
OS: Android Lollipop 5.0
Kernel Version: 3.10.20-x86_64_byt
[email protected] #1
Thu Mar5 16:30:07 CST 2015
Build #: LRX21V.WW_epad-12.9.3.19-20150305
BootLoader Info:
Variant: K013C 16
HW_Version: 2
Bootloader Version: WW_epad-12.9/3/19-20150305
IWFI Version: 200.7
Secure Boot: Yes
The major issues I have with it are:
Battery consumption is high.
Data partition is encrypted by the BootLoader.
BootLoader recovery fails.
System updates fail.
I understand that Lollipop 5 is a battery hog and I believe that is my battery issue - I restored a TWRP backup I made (without the data partition of course) and the tablet is currently running nothing but the OS and still consuming battery at about 10% an hour.
I would like to put on a different version or flavor of Android. Before that happens, I need 3 things:
My BootLoader Unlocked
My Data Partition unencrypted
A ROM that will improve battery consumption and maintain full functionality without bricking the tablet.
Can anyone help me with these issues?
I have searched the internet for a ROM or MOD for this tablet without success. In fact, there's very little info out there on this tablet at all. I suspect that ASUS tried to sell it for too much money, decided it was a flop and wound up donating it for educational purposes as some sort of tax break.
Here is a link to my Lollipop backup on Google Drive
Let me know if there's any additional information you need - any help would be appreciated. Thanks in advance.
Update: Oooh - found something! Teaching myself ADB and FASTBOOT commands and stumbled on this getvar command by chance - it may help people who know a lot more than me:
Code:
C:\[ADB Files Location]>fastboot getvar all
(bootloader) partition-type:reserved: hidden
(bootloader) partition-size:reserved: 0x0000000002e00000
(bootloader) partition-type:metadata: raw
(bootloader) partition-size:metadata: 0x0000000000100000
(bootloader) partition-type:ESP: vfat
(bootloader) partition-size:ESP: 0x0000000002100000
(bootloader) partition-type:boot: hidden
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:recovery: hidden
(bootloader) partition-size:recovery: 0x0000000001000000
(bootloader) partition-type:fastboot: hidden
(bootloader) partition-size:fastboot: 0x0000000001000000
(bootloader) partition-type:reserved_1: hidden
(bootloader) partition-size:reserved_1: 0x0000000002000000
(bootloader) partition-type:panic: raw
(bootloader) partition-size:panic: 0x0000000002000000
(bootloader) partition-type:factory: ext4
(bootloader) partition-size:factory: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000002000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000058000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000002bcff6e00
(bootloader) partition-type:mnt/sdcard1: vfat
(bootloader) partition-size:mnt/sdcard1: 0x0000000edda00000
(bootloader) max-download-size: 536870912
(bootloader) version-bootloader: 2.0
(bootloader) kernel: droidboot
(bootloader) product: baytrail
all:
finished. total time: 0.102s
Click to expand...
Click to collapse
HOW CAN I INSTALL THE win FILES?