I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share
I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P
@z3nful And an ota? Would it be usefull?
OTA LWX48S
I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with
I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?
@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!
btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.
Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?
Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.
@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"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"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse
Related
{
"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"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
thanks for you guys work
works perfectly! thanks
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1
v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here
v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P
paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?
I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?
when i run this it just keeps saying rooting device with spinning wheel at top then it reboots
Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results
Thank you for making my life easier.
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.
Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.
LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P
What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse
Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.
Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P
*** Backup your data. If not, it's your own fault if you lose anything. ***
There are a few guides out there already, but I was interested in leaving the G-Slate as untouched as possible. I didn't like the idea of flashing the bootloader, etc.
Background:
To root a device you simply need get the APK (SU GUI) at /system/app/Superuser.apk and su at /system/su with permissions of rwxr-xr-x plus "Set UID" and "Set GID" or 6755. The easiest way I could think to do this was too load clockwork recovery, then flash the superuser.zip to the /system partition. Here is how to do that...
Files needed:
Download what you need to get fastboot on you PC. There are many ways for Windows, Linux and Apple; just google.
Download the Clockwork Recovery 5.5.0.4 from the link on this page: http://code.google.com/p/lg-v909/wiki/Unlock_boot
(use something like 7-zip, to un-gzip/tar the file to get "recovery.img" out of it. Put in on your PC somewhere near your fastboot files...maybe even in the same directory as fastboot.exe.)
Download SuperUser from http://goo-inside.me/superuser (Superuser-3.0.7-efgh-signed.zip is most current today.)
If you are using windows, download the Windows Device Drivers for the G-Slate here: http://code.google.com/p/lg-v909/wiki/Install_Windows_Drivers
Process Part 1 temporarily boot G-Slate into Clockwork Recovery:
Copy the Superuser.zip file to the G-Slate SD Card. Remember where you put it. I put mine in /download/ (which looks like /sdcard/download/ on the Android system)
Shutdown the G-Slate completely by holding down the power button until you are prompted to shutdown. (Don't just shut the screen off by quickly clicking the power button.)
While holding down the the "Volume Up" button, press and hold the power button for about 5 seconds. Continue hold the "Volume Up" button while releasing the power button. When you see "Starting Fastboot USB download protocol" in the upper left you can release the "Volume Up" button.
Connect the G-Slate to your PC with a USB cable
Wait until the windows device drivers complete loading.
Open a terminal windows (Command or CMD in windows) and navigate to your fastboot executables (if they are not already in your path) and run the command "fastboot devices". You should see a device listed with "fastboot" after it. If not, sort out what is wrong with the G-Slate device drivers for your OS.
run the command "fastboot oem unlock". I am not sure if this was required, but it can't hurt.
run the command "fastboot boot recovery.img"...you should see the G-Slate boot into Clockwork Recovery.
(you are done with the PC)
Process Part 2 flash SuperUser:
Using the volume up and down keys navigate to "Install ZIP from sdcard", press the power button to execute it.
Using Volume Up/Down and Power to pick "Choose ZIP from sdcard"
Using Volume Up/Down and Power navigate to where you put the "Superuser-3.0.7-efgh-signed.zip" file and pick it.
Using Volume Up/Down and Power to pick "Yes - Install update.zip"...when it is finished, you are Rooted!!! Navigate "BACK" a few screens and pick "Reboot".
You should ave "Superuser" in your applications...and when you run something like Titanium Backup, you should be prompted to OK root permissions.
Now, without flashing recovery, you have installed Superuser to /System. No other modifications have been made to the device.
From here I generally, update all the google apps in market. Run Titanium Backup to uninstall bloatware installed on the System partion and then Menu-->batch-->"Integrate updates of system apps into ROM" which basically means move the APKs in /data/app that have updated APK's /system/app from data to system...saving a bunch of data space.
Good luck!
Tippy
Can someone help me with this? I don't know much about cmd. have team viewer.
It will be minimised to the system tray when opened
{
"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"
}
Step 13? where are you getting this update.zip from? I get all the way to step 12 and install then go back and reboot. And no root. I do see install update.zip but when installing it say no such directory
I have the same problem.SLate replies..
Can't open /sdcard/update.zip
(No such file or directory)
Anyone??
LanXL said:
Step 13? where are you getting this update.zip from? I get all the way to step 12 and install then go back and reboot. And no root. I do see install update.zip but when installing it say no such directory
Click to expand...
Click to collapse
I just edited some minor issues...and verified the steps...so sorry #13 is now the #4 on the second part.
At any rate, that "Yes - Install update.zip" is the second prompt after you pick "Choose ZIP from sdcard" when you pick file "Superuser-3.0.7-efgh-signed.zip" (or similar). In other words, there is no update.zip...it just that the verification (aka "are you sure?") prompt is badly titled with "update.zip".
If you flash "Superuser-3.0.7-efgh-signed.zip" (or similar) and it shows success, you are done. Back out of CW recovery and reboot. After you boot again, you should see a new app in your "apps" titled "superuser".
Did everything and No Root It didn't show up in apps list.
LanXL said:
Did everything and No Root It didn't show up in apps list.
Click to expand...
Click to collapse
After you tried to flash superuser,what did the screen say? Error?..or success?
Sent from my A1_07 using xda premium
for whatever reason... the gslate root thread was closed apparently and i didn't event notice it until now when i tried to log in to post about an update prompt i got just a few minutes ago.. anyway, im assuming the other thread got closed due to the little drama that happened in there..
we should keep this thread going, we all know that the device has reached EOL on tmobile but there are gslate owners around who are tied to a contract with them, like me!
so i got an update but wasn't sure what it was for and was afraid to install it because of my slate's setup, rooted and with a different kernel.. not risking to mess it up so i didn't install the update and i doubt it was ICS anyway..
I got the update also.. I decided to let it ride its course to see what would happen. I was half way asleep when I did this, otherwise I wouldn't have done it. In the middle of the update the device just froze on me. I had to push the little reset button in the back to get out if it. That's really all that happened.
Gslate03 said:
for whatever reason... the gslate root thread was closed apparently and i didn't event notice it until now when i tried to log in to post about an update prompt i got just a few minutes ago.. anyway, im assuming the other thread got closed due to the little drama that happened in there..
we should keep this thread going, we all know that the device has reached EOL on tmobile but there are gslate owners around who are tied to a contract with them, like me!
so i got an update but wasn't sure what it was for and was afraid to install it because of my slate's setup, rooted and with a different kernel.. not risking to mess it up so i didn't install the update and i doubt it was ICS anyway..
Click to expand...
Click to collapse
Agreed. I hate to say it (or not) but this is probably the last LG device I buy because of this. I bought this tablet because I had such great support with my Optimus phone (running a reasonably stable ICS right now from CM9 port). I realize now, unless LG sells a million of a device you won't ever see an update again because only the community hacks updates. LG takes the money and runs. :-(
Hello fellow Gslate users... Lol. Has anyone gotten this update and updated there tablet yet? Without losing root or getting the bootloader locked again??? I haven't updated it yet.. But would like to... I've heard the ICS for our Gslate is coming soon (alpha)
Sent from my SAMSUNG-SGH-I717 using XDA
TippyTurtle said:
Agreed. I hate to say it (or not) but this is probably the last LG device I buy because of this. I bought this tablet because I had such great support with my Optimus phone (running a reasonably stable ICS right now from CM9 port). I realize now, unless LG sells a million of a device you won't ever see an update again because only the community hacks updates. LG takes the money and runs. :-(
Click to expand...
Click to collapse
we got a really minor update , could it possibly mean that LG might still be supporting the device? hopefully we'll see ICS on the gslate , im still hoping we do .. otherwise, at least some nice devs have not abandoned the gslate and are still developing for it..
lately i've been thinking of calling tmobile to possibly trade it for that galaxy tab even if i have to pay a little more, not sure if they do that though.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
chevy383surfing said:
I got the update also.. I decided to let it ride its course to see what would happen. I was half way asleep when I did this, otherwise I wouldn't have done it. In the middle of the update the device just froze on me. I had to push the little reset button in the back to get out if it. That's really all that happened.
Click to expand...
Click to collapse
so did the update go through?
Gslate03 said:
we got a really minor update , could it possibly mean that LG might still be supporting the device? hopefully we'll see ICS on the gslate , im still hoping we do .. otherwise, at least some nice devs have not abandoned the gslate and are still developing for it..
lately i've been thinking of calling tmobile to possibly trade it for that galaxy tab even if i have to pay a little more, not sure if they do that though.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
so did the update go through?
Click to expand...
Click to collapse
No......... It didn't work.
There's a Web Site, saying that, the v10p update, kills your root access!!
Sent from my SAMSUNG-SGH-I717 using XDA
CXENTE said:
There's a Web Site, saying that, the v10p update, kills your root access!!
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Do they have the legal right to do that to someone who paid cash for and owns the g-slate?
I lost access to all my apps. Technically speaking, my g-slate is now useless. And I feel left in the dark.
... that's why im not installing the update, it is not a worthy update, nothing wrong with my tablet at all except for the 3d camera, but i don't need it anyway.
Gslate03 said:
... that's why im not installing the update, it is not a worthy update, nothing wrong with my tablet at all except for the 3d camera, but i don't need it anyway.
Click to expand...
Click to collapse
Well, I'm not real sure what to do now.. I can't access my apps anymore.
chevy383surfing said:
Well, I'm not real sure what to do now.. I can't access my apps anymore.
Click to expand...
Click to collapse
You mean all your apps? Or just the apps that need root access only?
What I would do first, is do a titaniumbackup then a factory rest, backup all your files/data of course.... If that doesn't work, try to revert back to stock honeycomb 3.0.1 if that's even possible, or stock 3.1 with locked bootloader then unlock it later...
Im not sure honestly, but do things at your own risk..
Hi! After latest OTA update I was left with an unbootable Galaxy Nexus (zygote couldn't start) and I lost root (su needed activitymanager up). So I needed to unlock to revive the phone, but I really didn't want to lose my data. After some exploration I could come up with a way to unlock bootloader without wipe and without root. I have seen several questions about this here and this was deemed impossible, so I decided to share my findings and expect they might help someone. Should work with GSM tuna phones.
Components for success:
— unlocking without wipe via putting a byte in param partition (needs root):
[1] http://forum.xda-developers.com/showthread.php?t=1650830&page=15
— OMAPFlash, a low-level utility for manipulating and flashing chipset (usually used to unbrick phones)
[2] http://forum.gsmhosting.com/vbb/f63...9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/
Take the two of them and you have a solution. I could successfully flash unlock byte to param partition using OMAPFlash.
A sketch of a guide:
1. Boot windows xp, download OMAPFlash (http://d-h.st/XNv), connect a turned off phone without battery, install drivers for omap device. (Mod edit: I've updated the download link.)
2. Dump a part of param partition. You don't need to dump the whole partition, but I think it is safer if you dump a sector-aligned area (512*n). I used 4KB (8 sectors).
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_upload [email protected] 1000 param.img
chip_upload is for downloading data from device memory
[email protected] is the start of params partition (check /sys/block/mmcblk0/mmcblk0p4/start, multiply by sector size 512 and convert to hex)
1000 is to copy 4KB.
Sometimes the process stalls (esp if you try to download larger dumps), just reconnect and retry.
3. Verify that the content is similar to first 4 KB of the dumps of param partitions attached in the thread [2]. For me they matched entirely.
4. Change the byte at offset 124 (0x7C) from 01 to 00.
Code:
echo -ne "\x00" | dd obs=1 count=1 seek=124 of=param.img conv=notrunc
5. Flash it back to the device.
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_download [email protected] param.img
Reboot, you are unlocked.
Additional links:
[3] http://forum.gsmhosting.com/vbb/f634/gt-i9250-pinout-enjoooy-1463061/ GT-I9250 JTAG pinout. Not directly releavant to the guide, but I found it while searching for solution, thought that can help someone in future.
Additional reading
The dangers of OTA when you have root, or why I was stuck with an unbootable phone at all
I learned the hard way that OTA may cause unpleasant results if you are trying to preserve root and mess with filesystem.
I was trying to preserve root in a way similar to one used by rootkeeper apps: put a copy of su somewhere in /system and make it immutable. So I went and put my su to /tts (thought that it's unprobable that OTA will do something there), and made it immutable.
And then the update came. As part of the the update process it copied a new version of /system/usr/share/zoneinfo/zoneinfo.version file and the file got 660 perms (package_extract_dir("system", "/system") in the update_script). Then it went on to recursively fix permissions so that the mentioned file would be made readable (set_perm_recursive(0, 0, 0755, 0644, "/system")). But the set_perm_recursive was met by immutable su in tts directory, chmod returned error and the recursive process was stopped before it got to zoneinfo.version file. So the latter file remained unreadable.
Unfortunately during startup zygote preloadsClasses, static constructor in some sqlite class needs DateFormat, and DateFormat reads zoneinfo. And fails cause it's unreadable. Exception, System.exit. Phone boot stuck.
To work my copy of su needs to send a message to ActivityManager service using binder. I wrote a dirty mock for AM but servicemanager didn't accept my fraud, it checked uid. I tried to bypass preloadClasses with overflowing system file descriptors count to prevent zygote from reading preload class list, but somehow it didn't succeed. Thus the only option I had was unlocking bootloader.
So it may end bad if you mess with /system on a stock rom with locked bootloader and want to receive OTA. It may seem natural, but sometimes the changes seem irrelevant, and then a chain of small failures leads you to loss of everything: boot, root, and data.
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
efrant said:
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
Click to expand...
Click to collapse
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
nichtverstehen said:
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
Click to expand...
Click to collapse
Exactly. I haven't needed this yet, but i had looked in those board files, cross examining with omap 4460 manual that can be found on the web. Thanks for sharing.
I was not aware that JTAG method had been found. Great news.
Sent from my i9250
Works!
Awesome - this worked for me! Unlocked, unrooted, TAKJU Galaxy Nexus w/JB 4.2.2. I used OMAPFlash_tuna.zip (download link).
I had issues when the downloaded param.img file was long, so I replaced 1000 with 200 in the commands. Regardless, it still took me probably 5-10 tries on each command to get it working (unplugging and replugging the phone in between), and sometimes it would freeze up and I'd have to restart Windows. If it takes longer than 5 seconds, you should press Ctrl+C and restart that step.
My problem was that one of my volume buttons is messed up, and as a result the fastboot screen doesn't work - Windows doesn't detect a fastboot device, and none of the hardware buttons or the touchscreen works either. As a result I needed to unlock the bootloader without using fastboot (oem unlock), and this did the trick!
Also, on Windows, I downloaded a hex editor (i.e., HxD) to do the editing. My modified param.img (only 512 bytes) is attached as well.
{
"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"
}
Thank you!!! It worked for me too!
The volume buttons on my Galaxy Nexus didn't work and I can't recharge the battery via USB. The USB works only as data connection. Despite all these issues on my phone, it worked for me too!!
I replaced the size in the commands from 1000 to 400 (1024 bytes = 2*512), and I had to put the battery on the phone.
Sweet jesus I cannot express enough gratitude for this post. While I was a little worried about bricking my device, it would up working perfectly.
A couple of confusing points for anyone out there trying to do this:
- The dump / reflash should only take a few seconds each. If it hangs, cancel and re-start the process.
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
- I didn't know how to get the dd command to work on windows, so I also went the Hex editor route it it worked flawlessly
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
techobrien said:
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
Click to expand...
Click to collapse
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
techobrien said:
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
Click to expand...
Click to collapse
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
Click to expand...
Click to collapse
This post thread have not been getting the attention it deserves..
Beamed from my Maguro.
cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely.
Click to expand...
Click to collapse
Good to know for next time round. The flimsy headphone ribbon cable is the bane of my existence and it seems like a somewhat common problem. I didn't think that the custom rom would touch the bootloader so I was confused, but /system/ makes sense. Thanks for the tip.
Just in case anybody was wondering, this method also worked for my Verizon GNex LTE. I also used a HEX editor.
Hi,
i'm thinking to use this method to unlock my Nexus' bootloader, in order to gain root privileges without wiping the memory.
This because i need to try and undelete files i have lost on my phone, to do this i need the root but i can't use the normal procedure that would wipe forever all the data i need to restore.
As i am new to this kind of operations, i never even rooted my Android phones, i wanted to ask if this procedure can fit my situation, and if there are any risks....
Thank you very much
EDIT: It worked perfectly!!
Thank you very much!!
Did anybody try it on MAGURO device? Does it require any change in the procedure?
Um... The op (and others) did it on a maguro? After all, the title says "on GT-I9250".
Isn't a i9250 a Maguro?
Beamed from my Grouper
Mod edit: removed quote of the OP.
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
mielli1 said:
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
Click to expand...
Click to collapse
Please do not quote the first post of threads when you reply.
As for your question, if you can get the driver to install on Windows 8, the program will work fine. The driver installs fine in Windows 7 by the way.
Don't forget to disable driver signature verification if you are trying to install drivers in Windows 8.
Windows 8 - stuck at installing drivers
beekay201 said:
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
Click to expand...
Click to collapse
I have a Nexus with a broken volume up button, so am trying this method as a way of unlocking the bootloader and rooting my device.
When I plug the powered off device into the usb port, constantly get the sounds of a device being inserted, and then unplugged (two different beeps.) This continues until I unplug the phone.
Is this the step where I should get a "found new hardware" notification? It is not happening for me, and I'm wondering if this is Windows 8 related.
FYI - I have already disabled driver signature verification.
For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.
ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?
I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.
FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?
nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots
You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Click to expand...
Click to collapse
{
"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 followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!
now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!
Which custom recovery we use?
Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.
Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).
northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.
Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.
The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...
That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.
Is It Possible To Avoid (Red) "Your Device Is Corrupt..." Message Using CM13?
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
{
"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"
}
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary
http://forum.xda-developers.com/nexus-5x/themes-apps/bootloader-theme-material-bootloader-t3298420
I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
- Gary
garybiscuit said:
I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
Click to expand...
Click to collapse
If you turn off dm-verity integrity checking in the kernel image you won't get the red corrupt message, but you'll instead get the yellow "can't check for corruption" message. That can be masked as noted earlier, but you can't stop the actual 4 second pause or the fact that it is happening without modifying the bootloader. I don't recall anybody working on that. It is likely bootloader is signed, in which case you might need to delve deeper into the phones boot process, probably the qualcomm modules.
I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own. I'm not really interested in taking it to that level. I'd just have assumed that the CM13 developers would have already solved this particular problem if they're considering their ROM an official release.
But, even if the CM13 kernel could be adjusted to not do this check... wouldn't you still get the "There's an internal problem with your device. Contact your manufacturer for details." message?
In general I'm just shocked that CM13 users (on the Nexus 5X) are okay with these messages. It sort of flies in the face of elegance.
- Gary
garybiscuit said:
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary
Click to expand...
Click to collapse
Flash attached zip.
View attachment Bootloader_fix.zip
garybiscuit said:
I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own.
Click to expand...
Click to collapse
Either flash one of the existing custom kernel/boot images with dm-verity disabled for you or flash SuperSU which will do it on the fly.
It doesn't mean recompiling entire CM13 source. The dm-verity check is an option enabled in the mount tables. Disabling involved unpacking the boot.img into kernel and mini filesystem, editing the mount table to remove the option, then repacking the kernel and mini filesystem. People have already done this for you or you can install SuperSU and it will do it for you.
Keep in mind, this won't get rid of the message or the pause, it'll just change the message from RED corrupt to YELLOW can't check for corruption.
If you don't like either message, best you can do is mask it.
The 4 second pause though will still be there as that would probably require the bootloader itself be modified rather than just the appended images.
glehel said:
Flash attached zip.
View attachment 3809902
Click to expand...
Click to collapse
Thanks here... but what is this .zip and how do I flash it?
- Gary
garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
- Gary
Click to expand...
Click to collapse
Boot Twrp recovery
garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
Click to expand...
Click to collapse
It appears to be replacing the RED corrupt image with something more legitimate looking, which, when suggested earlier, is what you didn't want to do.
Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.
garybiscuit said:
Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.
Click to expand...
Click to collapse
What did you expect? you open the bootloader, you use a non-factory system. might even with encryption turned off.
A google so declare his displeasure.
https://support.google.com/nexus/answer/6185381?p=verified_boot
I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.
I had a similar message after an update and found that I forgot to flash vendor.img. I don't use CM, but perhaps you need to fastboot flash vendor vendor.img. If you were only getting the message during the initial boot, before the android logo animation, that would be different, but since you're getting it inside android after the phone boots, this could be the culprit.
dd
garybiscuit said:
I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.
Click to expand...
Click to collapse
In this "trusted boot" world, CM will probably need to start signing their ROMs, building merkel-trees, and getting their keys distributed with the phone, but I imagine this might be difficult for them to do given the open nature of their builds and the lack of trust.