Related
FIRST THINGS FIRST:
This represents very little work that I've done on my own. It is mostly appropriating the work of others. The important thing to note is that the file works and it works well.
All I did to create this file was incorporate a modified version of stachre's updater-script into the official WiFi 3.1 update from Google (this is not the file you should flash).
I then added the kernel & all of the files from bigrushdog's HC3.1 .zip EXCEPT the system.img file (which is the vast majority of the update). BRD's HC3.1 installs the 3G version of 3.1 with Hotspot/Tethering options in the settings menu under Wireless & Networks, and I personally want to have the WiFi-only software on my WiFi XOOM. His version seems to work just fine and the only difference I noticed was in the Settings menu, but that was enough of a difference for me to prefer the WiFi only software. I'm sure more of you may feel the same. If there are any other differences between the WiFi & 3G software I'd be curious to know what, if any, there are.
I then added the code from BRD's updater-script (minus the parts relevant to flashing the system.img) on to the end of the updater-script from stachre's updater-script.
One of the benefits of this approach is that it does not require you to perform a factory data reset, as BRD's method currently does. And yes, you will have access to your external SD Card in the /sdcard/external folder.
It is super late and I am exhausted, but I wanted to share this with you before I fall asleep. If you seem to notice that these instructions are more or less copy and pasted verbatim from stachre's thread, that is because they are. This is a simplified version of his method with the addition of BRD's modified version of the stock 3.1 kernel for SD Card storage. There are fewer steps (now only 2) because more files are included in the zip.
[size=+1]DOWNLOAD HERE - FLASH IN CLOCKWORK RECOVERY:[/size]
MZ604_3.1_ROOT_update.zip
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk. If you're stuck in a boot cycle, try a factory data reset in recovery.
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (MZ604_3.1_ROOT_update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Pushes Superuser and su, sets correct permissions to enable functioning root
Flashes the system partitions to stock (required at this time)
Flashes bigrushdog modified stock boot.img (kernel) to enable external storage
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Leaves recovery intact
Outstanding Issues:
The new
Videos.apk does not appear in app drawer after update, according to Motorola this was done intentionally. Videos still play in Gallery. For some reason Motorola doesn't want us to use this app yet on the WiFi Xoom, but it's available on the 3G Xoom.
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the update here: MZ604_3.1_ROOT_update.zip
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola also available via torrent
You've flashed a recent version of ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Flash stock system.img & boot.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
The pre-update checks also include the boot partition. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
If you are unlocked and running unrooted stock Android 3.0.1, you can skip step 1. If you are already on 3.1 and just need root and/or external SD card storage, see this thread.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
You may need to re-enable USB debugging in the Application settings menu before you can send the above adb command. Alternately after sending 'fastboot reboot' in step 1, wait a few seconds after you see the Motorola logo and tap the Volume Down button. If you see "Android Recovery" at the top of the screen, tap the Volume Up button to boot into recovery and install from there.
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy MZ604_3.1_ROOT_update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "MZ604_3.1_ROOT_update.zip"
Select "Yes - Install MZ604_3.1_ROOT_update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulations! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
CUSTOM KERNELS:
I told you guys it wouldn't be long. TDR has already released an overclock kernel for WiFi Xooms on 3.1.
Tips & Tricks for quick-booting into Fastboot & Recovery:
Booting into Fastboot:
Hold down both the power button and the Volume Down button. Fastboot support will boot and you can flash system/recovery/userdata images.
Booting into Recovery:
I haven't seen anyone else mention this. If you power up, wait a few seconds after the Motorola logo appears, then hit the Volume Down button you will see "Recovery" appear at the top of the screen. Hit the Volume Up key to boot into recovery!
Great instructions, the simplest I could see so far! The above process worked for my WIFI only XOOM which I had rooted and installed the Tiamat Xoom Kernel. I am in Australia so was impatient to wait for OTA which probably wouldn't have worked anyways from what I have read.
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
it is different because no wipe is needed, if you are stock (unrooted) you will have to wipe when you unlock the bootloader
This is exactly the method I used, though I did thinks manually and it took a while, but works great
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Sent from my Xoom using Tapatalk
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
xoppaw said:
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
Click to expand...
Click to collapse
Yeah, the two main differences between this and BRD's procedure is that you don't have to perform a factory reset to get this one to work, and this method requires adb/fastboot. I don't think you should have to erase all your data just to install an official update. It's also only one file to flash.
The other difference is that this version doesn't have artifacts from the 3G version in the Wireless & Networks Settings menu (if that bothers you).
I don't know if this update would apply on an unlocked and unrooted Xoom, but if your Xoom is unlocked this version of the update should give you root. Both would be worth testing
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
tekuru said:
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
Click to expand...
Click to collapse
You can still play videos/local content fine through the gallery app, so we are safe in that respect. I can still watch all my movies or videos filmed on the Xoom just fine.
Here are some observations that I made. The WiFi update only included the Videos.apk file while the 3G update also included a Videos.odex file as well. I chose to add the Videos.odex to the update file in the OP, but it didn't make a difference (Videos apk still doesn't show in the app drawer).
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Land Master said:
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Click to expand...
Click to collapse
Thanks, I updated the OP to take account of that. Ever since I figured out how to boot into recovery from the Motorola logo I haven't really needed to send the 'adb reboot recovery' command.
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
kev0153 said:
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
Click to expand...
Click to collapse
Yes, I'm pretty sure for whatever reason the Videos.apk is enabled for the 3G version of 3.1 but not for the WiFi version of 3.1. I agree that the extra settings isn't a big deal, I made this file mostly because I wanted a way around wiping all of my user data.
Rumor has it that Google has said that the Videos.apk will be working on the WiFi Xoom in a few days.
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
IXIKelsonIXI said:
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
Click to expand...
Click to collapse
Download and flash this file:
http://www.mediafire.com/download.php?2bj5taicy3buc5c
Basically do what I said to do in the OP but skip step 1.
You are beautiful, and I love you.
I installed brd's 3.1 update yesterday, and i tried to install this zip over his method because i have a wifi xoom and wanted to get rid of the hotspot settings, but when i try to flash this in cwm i get an error:
Assert failed: file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.0.1/hwi69/110420:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/hmj37/124251:user/release-keys"
E: error in /sdcard/mz604_3.1_ROOT_update.zip
(status 7)
installation aborted
What is the problem? Is it not possible to flash this over his method? Do i have to change the build.prop?
Thanks
Edit:
Solved by going back to stock 3.0.1 and installing the cwm to get updated to 3.1.
WARNING Boot Loop!
Warning. This method set me in to a boot loop. The tip at the bottom of the instructions eventually saved me as I booted in to recovery (adb stopped working after awhile) and upgraded via bigrushdog's clockwork thread. Not sure if it was my custom boot theme or something else. I reflashed twice while adb was still working. All looked good each time but then when I rebooted to do the final cwm step, this is where I looped each time. I was careful. Not sure why it messed up.
Thanks a lot for putting this together, worked like a charm.
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
kntdookoo said:
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
ericdabbs said:
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
Click to expand...
Click to collapse
1. It's weird. My understanding is that even, unrooted stock WiFi Xoom owners can't access the new Videos apk on 3.1. The Videos.apk is there it just doesn't show up in the app drawer so there isn't any way to access it. If you look for it in a file manager like Root Explorer you can see it. There are other "ghost" apps like that in Android like the SoundRecorder.apk, so that's not completely unheard of. What's puzzling is why the 3G Xoomers got one that works and we didn't. If/when this is solved I will update the OP. It does work if you use bigrushdog's update method (but you gotta wipe all your data).
The Videos apk is mostly a showcase for their Video rental service that they announced Tuesday, you can still play videos in Gallery, so you're not really missing out on any major functionality at the moment.
2. The new features are cool! It's hard to compare performance since I was overclocked before and now I'm not. I love the resizable widgets. Overall it does feel like a more polished OS, they fixed a whole bunch of little itty bitty issues here and there. I can't really think of any downsides to the upgrade, it just feels like a step in the right direction. I'm definitely looking forward to see where Honeycomb development goes in the future.
I have installed this update over my rooted wifi only 3.0. It worked great, i did get a boot loop and was forced to wipe in recovery (luckily i did a titanium backup first), apart from that it went through no problem.
I haven't used the browser extensively yet, but it does seem more stable, hasn't crashed yet and the overall browser seems much better, especially the thumb menu from labs.
Good work!!
(I have the wifi only UK version BTW)
All,
Ok, time to re-wrte the OP as there are now MUCH better tools for flashing the update.zip (and you can make backups) Make sure to say thanks to the TWRP team!!!. The update.zip file available here is a derivation of the work originally started by JackpotClavin (he did an initial proof of concept but a number of features that I wanted didn't work so I figured I'd pick up where he left off and see if I could get the ROM working for me with the missing features)
The initial thread was here if you care to look.
At this point sound, video (both in the browser and standalone) and hardware acceleration are now working with CM7 on the Fire. I'm off now poking at the MAC address issue and then I'm off to see about Bluetooth.
UPDATE:
- 01/01/12 - Back from the break and starting to work on things again. I've had a number of people ask for my current configs so I set up a repo at https://[email protected]/whistlestop/CM7KF to let people track my progress. If you want to build your own KANG then below are the steps that I currently follow with the current repo files.
-Pull the CM7 source. Check out this link for a how to on that: http://wiki.cyanogenmod.com/wiki/Nexus_One:_Compile_CyanogenMod_(Linux)
Symlink the amazon directories from the CM7KF repo into the CM7 tree. Specifically:
-cd <path to the CM7 tree>/vendor
-mkdir amazon
-ln -s <path to CM7KF tree>/vendor/amazon amazon
-cd <path to CM7 tree>/device
-mkdir amazon
-ln -s <path to CM7KF tree>/device/amazon amazon
Copy the cyanogen_blaze.mk file from <path to the CM7 tree>/vendor/amazon/blaze into <path to the CM7 tree>/vendor/cyanogen/products and add the following line to the AndroidProducts.mk file in the same directory.
$(LOCAL_DIR)/cyanogen_blaze.mk \
Ok, go to the top of the CM7 tree and do ". build/envsetup.sh && brunch blaze" and go get a cup of coffee while it builds. It'll take awhile.
- 01/02/12 - New update.zip files uploaded that fix the MAC issue as well as the build issue with the gps.omap4.so library.
- 01/03/12 - New update.zip and update-wipeall.zip files uploaded that fix the regression on the hardware acceleration. Sigh...
- 01/13/12 - Update to remove the recovery option on reboot (as it continues to cause problems for folks), removal of the search from the soft buttons by default, addition of the home to the soft buttons by default (again as that seems to be a constant question) While I built and tested the changes I didn't make the updates. You have IngCr3at1on to thank for that.
Backlog of tasks (as of 01/02/12)
-FIXEDSeems that all Wireless MAC IP's are the same (meaning that everyone that flashes the ROM will have the MAC of 08:00:28:12:03:58. While the first three octets register the MAC as being owned by Texas Instruments (the manufacturer of the OMAP chipset), the fact that the last octets don't vary is BAD. From a little Googling, I'm not sure this is something specific to this ROM/device as other CM7 ROMs on different devices seem to have the same issue but with a different MAC address it sounds. I'll look to make sure I'm not doing anything that is causing this issue. A tip of the hat to "TheKid2" for this post which appears to provide a hand workaround to the issue for now.
-The update.zip file is now signed but the update-wipeall.zip isn't yet. I'll get to that but as it doesn't seem to cause any issue in flashing it's not too high on the list to chase given the two issues below.
-No Bluetooth (yet...) This is still my personal quest so once I get the base CM7 capabilities working then this is my next thing to poke at. From the postings/reading I've done so far this seems doable (just a matter of time and programming, no rocket science required it appears at this point)
Before you start, make sure your Kindle Fire is fully charged, rooted, you know your way around adb, your kindle fire actually connects to adb and works successfully and you've installed TWRP (and I recommend installing FireFireFire as well to keep from having to issue idme commands to get into the recovery image).
I used the directions here to get all the pre-requisites done. Assuming everything above is done, then it's time to install CM7.
First a note, installing CM7 will replace the current ROM on your device and I'm not responsible for any malfunctions :/ I've done this for versions 6.2 only so your mileage may vary (but there is a good group of members on this thread so they'll help out if possible)
If you're coming from a STOCK ROM then use this version to flash. It will wipe the data and cache partitions (as well as the system partition) as a part of the flash process which should get rid of any FC issues.
md5sum for update-wipeall.zip
e7c85c3bcc01bcea59ffcc5647a6be97 update-cm7-wipeall.zip
If you're upgrading from an EXISTING CM7 install then use this ROM instead. This one will NOT wipe the cache and data partitions which should mean that you can upgrade from one version of CM7 to another without losing any of your existing date (or that's at least the idea)
md5sum for update.zip
ab80c089d0c93f02bd7271c5e4401cf7 update-cm7.zip (CHECK THAT THIS MATCHES THE DOWNLOADED UPDATE.ZIP)
Copy the CM7 update.zip to the root of your sdcard, so it's /sdcard/update.zip (e.g. "adb push update.zip /sdcard/")
OPTIONAL STEPS FOR INSTALLING GOOGLE APPS
If you want to add in the Google apps then:
-Download the gapps zip from here
-Copy them to your sdcard (e.g adb push gapps-gb-20110828-signed.zip /sdcard/ )
NOTE: if you have issues with the included Google Market FC'ing, then download this versions and it seems to fix the issue (again thanks to detnap in this thread for that tip)
Reboot into TWRP (when the FireFireFire screen comes up hit the power button to launch TWRP.
-If you reboot by holding the power button until the power screen comes up make sure when you select reboot that you DON'T say boot into recovery as this will put you into a loop where the device always boots into TWRP (even if you don't press the power button during the boot) READ THIS PART AS ALMOST EVERYONE IS MISSING THIS PIECE: If you find yourself in this loop then connect with "adb shell" and issue "idme bootmode 4000"
-For me I hold the power button until it goes orange. Just pressing it quickly doesn't do the trick at least for me.
Once it boots into TWRP then I ALWAYS recommend you perform a backup before you start anything (that way you can go back in case of a problem) You can do this by hitting the backup button.
Now that you have a backup, on the main TWRP screen hit the install button. This should put a list of the possible .zip files on your /sdcard partition in the right window. Tap the file you want to flash and hit the flash button (right now don't do any MD5 or signature checks as I've not yet got that included in the update.zip) If you see some errors about not being able to load volume /misc don't worry, I see that right now as well and everything still seems to work. I'll chase that issue once some other bigger issues are run to ground.
If you are coming from a stock ROM then make sure to click the wipe Cache/Dalvik so that we rebuild everything for the new CM7 image. If you're coming from a previous CM7 ROM then you can skip this step (I at least have and everything appears to work fine and you don't have to re-install everything)
Now hit the reboot button and you should again see the FireFireFire yellow triangle again. It will sit there for a bit and then it will go away and you should be greeted with the CM7 boot screen. If everything goes well, then a few seconds later you should be sitting on the main page (in my case it takes me back to my lockscreen as I didn't wipe any of the cache or data partitions)
Ok, that's it or now. Have fun and I'll post an update when/if I get the MAC or Bluetooth issues resolved.
So is the link to the update.zip the one with the sound fixed or calvins original?
It's the updated ROM with the updated MD5SUM for the file.
I can confirm this works. Thanks!
Sent from my Kindle Fire using xda premium
Yeahhhhhhh
Sent from my Nexus S 4G using XDA App
woot woot! Can't wait til Christmas comes around so I can play with my moms new kindle fire
Sent from my SAMSUNG-SGH-I997
You mention the video is not working, is it meaning that the video player in CM7 can't play any format of video?
Or is it just the flash video in the browser?
YouTube works, does Netflix?
Sent from my HTC Incredible 2 using XDA App
Just curious, how long does it take to go from stock to this cm 7?
loki154: Veritass tested the update.zip for me and he said that netflix worked for him.
ck_looi: I haven't tried anything other than trying to play youtube videos in the browser and they cause the browser to exit.
Ah yeah, flashing it now then.
Can you please try out any video format which suppose to work in stock ROM? Maybe can try out the mp4 video.
someone should make a video on how to install this
Sent from my ADR6400L using XDA App
I'm just another "me too" from the crowd, but thanks for continuing this project.
I made the decision to pull the trigger on the Fire after seeing the efforts to port CM7 and ICS to the device, and especially with Transformer Prime availability up in the air.
I know JackpotClavin did most of the work so far, but it's great that others are continuing the work he started, now that he's moved on to ICS work.
Like all the others, I'm excited to be able to enjoy the fruits of everyone's labor when I unwrap my self-bought Fire in a week and a half.
Thanks again.
Hmm, to get the market on this rom, would we just go by the instructions on the thread for the stock rom or should we flash the gapps by renaming it to update.zip?
don't know about the stock rom's way to do it, but in cm7 gapps is the way to go and it's proven to work on clavin's port so my money is on gapps
Poler166 said:
someone should make a video on how to install this
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
here is the video:
http://www.kindlefirewire.com/2011/11/16/how-to-root-kindle-fire-video-tutorial/
iluretar said:
don't know about the stock rom's way to do it, but in cm7 gapps is the way to go and it's proven to work on clavin's port so my money is on gapps
Click to expand...
Click to collapse
http://goo-inside.me/gapps/
Which one should I download?
The tegra looks tempting, so does HDPI. Or should I just stick with universal?
tannerzion said:
http://goo-inside.me/gapps/
Which one should I download?
The tegra looks tempting, so does HDPI. Or should I just stick with universal?
Click to expand...
Click to collapse
Universal for CM7 at the top.
foxdog66 said:
Just curious, how long does it take to go from stock to this cm 7?
Click to expand...
Click to collapse
I'm doing it over and over so I have it down but for me all of a couple of minutes once everything is in place (meaning you've already rooted, you've already set up your android SDK environment and can talk to the device...)
The act of flashing and doing the various commands is maybe 2min from start to finish.
NOTE: I DO NOT HAVE WINDOWS, AT THE MOMENT! THE DEVELOPEMENT HAS STOPPED TEMPORARILY!! I'M SORRY FOR THIS!
Welcome to the original thread, of Beatsleigher's Root Helper!!
This program is completely free, with no Xtra options for donators...
What this program will do:Well this program is designed for beginners, and advanced users.
Beginners, can learn, about flashing. And learn, what to do, to get a custom ROM running...
Advanced users & pros, have a few more options, they can flash their ROMs, even some advanced options, like RadioOptions (If you know, what that is).
If you need to setup ADB drivers, then follow the steps, in the ADB -> Help menu!!
List of features:Several Reboot options,
Backup/Restore
Unlock bootloader (fastboot)
Relock bootloader (fastboot)
Root (ADB+fastboot)
Flash recovery (fastboot)
All-in-one solutions (Some new ones, again ^^)
Using a complete GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
Install apps, as user apps.
Install apps, as system apps.
Push files, to SD.
Flash ROMs.
Flash stock ROM.
Context menus!!
And much, much more!
What's to expect:In-program E-Mail subscription, to get notified about updates.
User experience program…
More updates
Requirements::[/CENTER]
This program requires following, to run:
.net framework +Ver. 3.5 (SP1)
.net framework 3.5 Client Profile
.net framework 4.0 Client Profile
Windows Installer ver. 3.1 & 4.5
It uses just over 30 MB of RAM (Excluding the scripts) on average.
CPU usage is at 5% at the moment
If RAM usage goes over 90%, the program WILL shut down... (Not the computer)
ADB is the ONLY background process, used by BRH (The only 3rd party process)
FAQ:Q:When installing the drivers, why do I need to change my system configuration?
A:You need to configure your machine, to notice the device, but to leave it alone, instead of looking for, and downloading drivers for it. This just confuses the computer, meaning you can't do anything in the bootloader, because Windows Update doesn't yet have the needed drivers...
Q: Why have you gone over to making a GUI? The batch files, were just fine...
A: I'm going over to making a GUI, because it is easier to use, less work. And I have the option, to just, drag & drop a button, write two lines of code, to make the button functional and then it's just a matter of creating the batch file, converting it to an EXE. Easy as pie. Whereas, with the batch files, to create one more option, you have to write 6 lines of code, then the batch file, and then half of the stuff doesn't work properly, because you didn't debug... If you know, what I mean...
Q: Why are there so many files???
A: This program needs so many files, so it can perform different processes/options/tasks
. But it isn't hard, to find out, what file, does which job
Q: Why is there only a version for windows??
A: I am working on a version, for Mac users, but it will take some time. I'm glad to be nearly finished, with the Windows version
Q: I want to donate to you, but you won't allow it. Why?
A: I don't accept any donations, because I only wrote the program to flash files on to your phone... I don't want to take credit for things, that other people did.
Instead of trying to donate to me, donate to chainfire, ChainsDD, and Kousik Dutta; for creating such brilliant recoverys, Apps (like superuser and ROM Manager) and ROMs...
BTW: If you really want to donate (which you won't ), you can send me some albums ^^ I need house music, to work.. And all my songs/albums have been listened dead -.-
Q: Do you mind if I use this program for commercial use, and post videos(tutorials) on Youtube?
A: As long as you DO NOT create mirrors, and let me know, I'm not that fussed... But then please post the link of the video to me, so that I can tell you if I like the way you did it, or not.
Q: When are you gonna stop talking about things, that don't interrest anyone (the FAQ)??
A: Now, but still thx for reading, other good questions will be posted here, aswell...
Thanks:Many thanks to Kouschik Dutta for creating the recoveries for near-to all Android phones. Yo the man!
And not to forget the awsome app: ROM Manager ^^
Thanks to my good friend Accendare (baddinski), for creating the splashscreen. I appreciate it much
Thanks to Google, for creating the AOSP, for the great developers, to create even greater ROMs, for us!
Also, thanks to Google, for buying Android, and making suh a (rather) bug-free OS!!
If I forgot anyone, please let me know immediatly!!
Downloads:
If you want to flash stock firmware, you will need to install this. This contains all the neccessary files/folders you need:
GSM: to be downloaded, by clicking this...
CDMA: to be downloaded here...
Current version (From the 28.03.2012 02:58 GMT +!) is 2.6.5.5.
There are some new and juicy features, that have come in this update. Especially, for those fellow developers So, give this a try, if you're not too busy ^^ Download here
Before updating, please run this...
Fulll release!! Version 3.0.0.8!!
It's an ISO image. I'll provide a link, to power ISO, should you not have an Image-mounting software, on your computer… If you have Windows 8 CP, you do NOT Need this…
Well, I hope, you will enjoy this new version!!
Download: Beatslei9gher's Root Helper_Install_CD Power ISO 5
Screenshots:View attachment 928851 View attachment 928852View attachment 966857 View attachment 966858
View attachment 966859 View attachment 966860
View attachment 966861 View attachment 966862
View attachment 966863 View attachment 966864
View attachment 966865 View attachment 966866
View attachment 966867 View attachment 966868
View attachment 966871 View attachment 966872
View attachment 966873 View attachment 966874
View attachment 966876
If you want to see more, download it
Installer:The installer will install to your C:\ drive. Some older scripts, are still working with "%homedrive%" so, to make sure, that everything is working, please make sure, that your homedrive is your C:\ drive. Or, if you have a seperate C:\ drive (like me), copy a copy, of the "Beatsleigher_root_helper" folder, to your homedrive. Then it should do the trick. By the tiome, the program is released properly (full) all scripts should be working with "C:\".
Should you have NOT got a C:\ drive, because your homedrive is named differently/you deleted the C:\ partition, see: installation help.
Requests:If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Please read!!:
Befor moaning, that there are not enough ROMs/kernels, remember, since 2.6D ALPHA, you can flash both kernels & ROMs via ADB & fastboot!
Download, and see for yourself
Changelog:
Verison 3.0.0.8 (Full release):
All scripts were re-written...
A few changes...
Full release(!!!)
Version 2.6.5.7 (BETA) [Minor 3]
Working context menus!! (On selected forms)
And that was really about it.
Version 2.6.5.5 (BETA) [Minor 2]:
Added some juicy developer features! (Using the ADB shell)
A few options, for n00bs, are in there, aswell...
Added options, to the ADB menu.
Added a complete new form. (Dev. options)
Added a few more scripts. Making the update zise about 6MB, on your HDD
Removed some buggy code.
When navigating, from ADB menu to Dev. Menu, ADB menu closes, but can be re-opened from the "File" menu.
Dev. menu has also got CPU/RAM usage detector!
Download, for more changelog
Version 2.6.5.4 (BETA) [Minor]:
Working progressbars(!!!)
Added CPU/RAM usage detection.
ADB menu has got a makeover.
Added option to enable/disable CPU/RAM usage detection in fastboot menu...
Fixed bug in ADB help menu.
Cleansed the code (again)
I probably forgot the rest, or just find out, for yourself
Version 2.6.5.3 (BETA):
Removed bug that caused phone crash, whilst prompting device name.
Cleansed the code.
Removed two un-used forms.
Repaired the menustripbutton.
Added scripts, to update package.
Removed other scripts, from update package.
Compressed some, of the files (drivers, executables)
Using traditional installer, again.
Installation path set to: C:\Beatsleigher_root_helper\
Version 2.6.5.2 (BETA):
Fastboot menu fully working.
Fastboot help menu, is popping up/has been created, though it has no content.
ADB help menu is working/all buttons have a task.
Some unneeded code has been removed.
A complete list of ROMs & kernels is present (CDMA + GSM).
No change in the IE engine...
All messages giving a tone/sound.
Options have ben added to the ADB menu.
New all-in-one solutions for ADB menu.
Scripts have been edited, for more friendliness
More tooltips.
Progressbars still not working ( )
Maximization has been disabled in ALL windows.
Better usage of RAM, whilst opening other exe - files
Version 2.6.5.1 (BETA)
Added update check-support.
Changed file hoster to mediafire (updates coming from there)
Added ADB reboot options.
Fastboot reboot options working.
Added (hidden) features.
Using a proper installer.
Can be installed anywhere on HDD, will work anyway
Two packages are to be downloaded, not one. This ensures, that updates are working, as planned.
(Hidden features will be released, when version is 2.6.5.3 (next update) )
Version: 2.6 D:
Everything you see, down the bottom is working.
You can now flash a recovery via fastboot menu!!
Kernel and ROMs, I have decided, to take them back out. They were a bit buggy...
The size of the EXE itself, has gone up to, ca. 2.4 MB.
Option to flash stock ROM (LTE + GSM) has been enabled, for fastboot.
Looks a bit more friendly
Icons have been added!
You'll have to find the rest out, yourself
Version 2.6C:
ADB menu has been carried on. You are now able to flash a kernel (LTE & GSM)
It will open the Explorer for you, when you need to copy the file!!
LTE menu is finally working!! It had problems opening, due to a minor type-error.
Though the LTE menu is working, you will only be able to use one button, in about an hour. Once I've completed doing the ADB menu...
(See: "What's to expect", for more info's on what's coming!!)
Version 2.6:
New GUI!
Complete new code.
In-program help.
Direct link to thread.
Seperate fastboot and ADB menus!
More explicit details...
Removed the music, that pops up, upon start. (To many house haters )
All batch files converted to executables... (This prevents tampering with the code)
Fully compatible with 64x machines. Doesn't use as much RAM, but therefore shows up as a process.
Installation help:
Not much can go wrong, when install9ing this program.
Mostly, the reasons, of failure, to use this program, are due to:
Not having a C:\ drive.
Not copying a copy of the root folder, to hamedrive, if C:\ is not the homedrive, of your windows machine.
Tutorial 1:
Problem: I installed the program, but my homedrive is not C:\. I installed to C:\, but I can't use half of the program.
Well, first of all; sorry, for this. I could of said this earlier... I forgot to edit the scripts, to use ONLY the C:\ drive, so it useshalf the C:\ drive, and half your homedrive. But, that's why I posted this tutorial.
It's quick & easy ^^
Tutorial:
Install the program, to your C:\ drive. Close the installer, and re-open it.
Once back in the installer, set the installation path to your homedrive (Where Windows is installed).
Install to that directory, and done
It should now work ^_^
Tutorial 2:
Problem, I don't have a C:\ drive, and the ROM-Full/Less version, isn't available for download... What to do??
This is also no problem!! With a few, simple clicks of your mouse, we will fix this minor problem
Tutorial:
Type following key-combination, on your keyboard; START(WIN)+R.
The "Run" prompt should now pop up.
In the RUN prompt, type: "diskmgmt.msc" and it enter.
Once the disk manager pops up, shrink your homedrive(or, if you have unalocated disk space, which is 3GB or more, right click on that)
Shrink your homedrive, about 3GB. If you can, allocate more space, because you will need quite some space, because of stock ROMs/custom ROMs/kernels and backups.
To shrink, right-click on the partition and select "Shrink Volume". Enter this amount, to shrink: 3072 MB, that should be 3GB. Like I said, feel free to allocate more space.
Now you should see a black field. This is unallocated disk space. Right click on this space and select" Create simple partition" Make sure, you create the exact space, you shrunk, other wise, you will have some unallocated space, on your HDD and this can cause problems, if unnoticed.
Name the partition : C:. Wait, for the Diskman. to create the partition (can take up to 5 Minutes, for that amount of space, depending on size of HDD, CPU clock speed and amount of RAM).
Now, just install Beatsleigher's Root Helper to your C:\ drive and again, to your homedrive. Done! You can now use Beatsleigher's Root Helper.
If you should notice any other problems, please let me know, so I can solve them.
EULA:Please read the EULA, should you not have, during installation. Or, you are interested in installing the prgram.
There is vital information, in this text document!
Some misc. text
Hmm... I'm at the end of my stream of thoughts...
Now, I'm asking YOU!
Please tell me, what would you like me, to add to this program.
Don't forget, if you like this program, and you are happy, to recommend it. Don't be shy, post your thanks, and a comment or two. Hit the thanks button. Even if you are dissatisfied, just post a comment, and I'll try and do it better.
If you are a junior member, send me a PM, and I'll post it for you
I'll ask again;
I know, I'm not that well known, and I know, I've done mistakes (ROM-Full version)
But, I'm trying to make this program, a better enviroment, for everybody. Please, would you give it at least a try, instead of just ignoring this...
NOTE: Short term for: Beatslleigher's Root Helper: "BRH"!!
To prevent confusion, in future!
Well, I mentioned there will be a working version on Linux, right? Well, I only just found out a few days ago, that you can use wine to emulate Windows... :O Well, there you are! It works pretty much fine, but then a agin, there will be a few bugs, so I'll get on to that...
Sorry for not updating this thread, for such a long time... I'm using UBuntu, and I've got quite a lott to do, as the schoolyear is coming to it's end
News, tips & tricks!!
News:
IMPORTANT:
Verizon has just released their version, of the GNex...
Beatsleigher's Root Helper, will be one of the first, to provide their images, for recovery... Other than that, everything will be the same!! I'm updating the files, right now!!!
New concept:Beatsleigher's Root Helper, is written and hosted by one person: me. I have been working hard, and have noticed, that I need to change the concept. Instead of being big, and cluttery. It is now small and efficient. Like a car manufacturer, I am working hard, on producing a very small, but powerfull piece of technology (in this case, virtual technology). And, instead of relying on the user, to type everything, this new version, needs only a few clicks of a button. As an example, the first version, which used a lot of RAM, and waisted processes, used up (with all ROMs/kernels/bootanims) over 1 GB. Now, you can download the ROMs, you wish and kernels, and just flash them, with the click of a button. The best thing is, all of the data, I provide version 2.xx with, the size comes out, at a maximum of 300-350 MB of disk space. (Counting both CDMA & GSM stock ROMs).
Beta has been released!!:After a few weeks of hard work, I can finally say: "I'm almost done!"
It took 4 weeks, 3 Albums, 5 DVDs, 5 Gigs of HDD space, and lot's of testing.
But now, It's nearly done, and I'm proud of it.
This project will NEVER be abandoned. (Unless the GNex gets boring, at some point in time)
It brings a lot of new features with it, including working help menus.
This is also a new part, of the concept, keep it in BETA, untill EVERYTHING works. Of course, I will keep it updated and will constantly change it, to make it better, and easier to use.
If you like it, you may also advertise!! (Just a tip. I also have competition...)
Askng for help?!:Yes, I'm asking you, for help.
After all my hard work. It seems, noone is downloading it...
That's why, I need you, to post requests, and suggest things
I think, it's important, for me to know, what YOU really want, in this program.
Don't be shy, just post your opinion, and suggest someti=hing, to make it better
And if this, doesn't help, I will probably close this thread, and leave this program, as it is, and start other projects, for other phone's, like: HTC devices.
I shall then declare this program as final. This is not giving up, it's you not giving it a chance... But anyways, back to the point: I need you, to tell me your oppinion!!!
Google has done it again!:
After some time, on 4.0.2 (Stock), Google has released the stock version, of 4.0.4, for it's flagship devices (Motorola Xoom WiFi, for some reason, aswell..)
I am currently downloading the factory image, and will be creating an installer, so you can enjoy the joys, of 4.0.4!
So, again, another thing, to look forward to, when using this program!!
Windows metro style app!:After the nearly complete nervous breakdown, of my computer, I have decided, to install Windows 8 Cons. preview.
Whilst installing the new OS, I was downloading the SDK, VS 2011, and decided, because Windows 8 will be available, next month, I shall start creating this program, also as a Metro-styled app.
I, however, have decided, to keep the style secret, and keep on developing, and as soon, as Windows 8 is officially released, I shall also release the new program. If, however, you are lucky, I will have enough time, to work on this new project, and release it in a week, or so
But, as I said it depends, on whether, this program get's downloaded a bit more, or not, and if I am quick enough, on deving this...
Having trouble, with Wndows 8?Well, I have found a solution, to all your ADB/fastboot problems...
Interested? Click here...
The thread contains all info, you need, to install and configure the ADB drivers, on Windows 8...
If you have a problem, please let me know, by either: Answering the thread, sending me a PM, or post your problem here...
New cooperation!!: Because so many of you, are wanting more kernels and ROMs, I have decided, to cooperate, with sonicxml This means, there will be an option, for you, to flash his kernel img, via fastboot. This means, there is one less step, in the al-in-one procedure!!
So, I'm thanking him, for accepting my request
CDMA issues I've come to notice, that some people, are having issues, with their CDMA devices...
This will be fixed, in the next update, release will be, in a few days. I'm very sorry, that this has happened, whilst testing, I didn't have any problems, what so ever...
But, because I guaranteed you, that I will fix ANY and EVERY bug, that you/I can find, I've already started, on a new and better flasher, for 4.0.2 stock flashers...
These will be hosted on my FTP server, in future, so the program can download the files, itself... So that shouldn't be a problem.
Should you have any more problems, please let me know, IMMEDIATLY, because, there is no point, in me updating, uploading the files, and literally half an hour, after release, someone tells me, that they're having problems, for a few days...
So, please. Tell me, I'm always happy to help. That's what I'm here for
Info's on updates...
All-in-one fix: Well, it looks like I've managed to fix the all-in-one problem... It seems, that there was an error, whilst in recovery. Added the feature; it flashes an insecure boot image... This allows the recovery, to stay put, and it grants the ADB remount access... This means, you are as close to stock, as possible, but you are fully rooted...
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
bk201doesntexist said:
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
Click to expand...
Click to collapse
Thx for the force
I said it's harder scripting for Linux, because I'm a noob, when it comes to Linux/Unix... I only just found out, that Linux has the drivers for my laptop a few days ago And I'm used to Windows, that's why I said it.
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
imfloflo said:
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
Click to expand...
Click to collapse
Currently working on it I'm just removing some scripts
To all size lovers!
The size has gone down, to under 60 MB.
I'm trying, to keep it under 80MB...
Thanks, for using Beatsleigher's Root Helper!!
Facebook page now open!!
Hey guys, I've created a FB page, for Q&A as well as the Q&A Thread, in the Q&A section (thx imfloflo)
There are also a few other things, which might interest you! So give it a looksee, it's not done yet, it will also take a while, because I'm busy with school and my root helper...
But, here's the link^^ Beatsleigher's Facebook page!
Info on 2.6 ALPHA (GUI version)
Please read!
This builds are only alphas. As most of you know, alphas are very buggy... I'm doing my best, on keeping them bug-free, so please don't complain about them not working properly... Some menus also haven't been taken care of, I know. If you are looking for the version, that works best (at the moment), take/download the ROM-Less 1.2.7 version.
Why did I jump from 1.2.x to 2.6?
There have been many unreleased version, during the batch period. Well, they weren't unreleased as that, they weremore or less kept for private use, because it was too big, to upload/for you to download. So I kept it on my HDD & USB flash drive.
Info on 2.6B ALPHA
ABTextBox1.Visible = FalsDB menu working properly. All buttons have got their purpose. All linken with an "OpenFileDialog" so you can flash like that. You just choose the file you want, open it and click on "push". The same goes for ROMs. Fastboot menu is planned to work in 2.6C or D.
BTW; have you noticed, that the size of everything has shrunk, again? Well, guess what, it will start to rise, soon. Why? The program you asked for is nearly 2 MB :O
Well, I hope you had fun reading, and I also hope, you know, why the updates are taking so long
Ok, the beta will be delayed, again.
I'm currently busy, and not near home...
I'm currently writing a EULA. So, please read it. It will prevent lots of miss understandings... It's not drastically big, nor hard to understand. It will be uploaded, as a txt file, and provided in the next update package. ...
I guess, the update will be released at about 18:00 o'clock GMT +1.
Who care's how I sent IT?
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
familyguy59 said:
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
Click to expand...
Click to collapse
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
HSKalay said:
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
Click to expand...
Click to collapse
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Oh, yes. I forgot to mention: The program pushes the zip file automaticly, to your SD, to make the whole process, as comfortable, as possible
familyguy59 said:
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
Click to expand...
Click to collapse
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
HSKalay said:
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
Click to expand...
Click to collapse
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
familyguy59 said:
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
Click to expand...
Click to collapse
BRH...sorry what is that?
HSKalay said:
BRH...sorry what is that?
Click to expand...
Click to collapse
Short term, for: Beatsleigher's Root Helper
familyguy59 said:
Short term, for: Beatsleigher's Root Helper
Click to expand...
Click to collapse
ha, I should of known that
You wouldn't happen to have a link handy, to the cwm rom i can flash? (or know where i can find it on my machine?!)
*edit its ok, i found it! it was under fastboot...i was in adb
* Second edit, nah, still didn't work.
i'm leaving it for now, don't wanna mess the phone up. I'll blank everything and start again one day.
This is the thread for us A100 owners to have a general Q&A, chatter, thanks, non specific bug reports, or anything else you feel like posting related to the A100 CM10 builds by waydownsouth.
You can find his preview build thread here
Use this gapps for now.
Please keep his Dev thread clean of the usual thanks, you rock, take my wife please, shut up and take my money pictures, etc, and post them here. Please keep the Dev thread clean and Dev related only.
Specific backed up suggestions for fixes, logs, and other development related posting can be directed to his release thread in the dev forum.
Some general information
Bugs
The first thing you may notice, the boot animation will blank out, just a black screen for a bit halfway through the CM9 animation. Don't freak out, it isn't wrecked. It only occurs on boot animations that have 2 stages, it blanks when the loop kicks in. If this bothers you, replace the boot animation with either one that is always a loop, or doesn't have a second stage, so animation, then stops.
The stock launcher is always landscape, I'm not sure why this is, the rest of the system will work either in portrait or landscape. 2 ways around this, first is use something like Apex launcher or Nova launcher (or any launcher really) OR force Tablet UI, see the FAQ for information on this. This isn't really a bug, its just confusion caused by Google adding a 3rd UI, and our screens mess it up.
There is two gallery apps and two camera apps, one gallery is normal, the other is the 3D version, I'm not clear on why there is 2 camera apps, it may be from the GApps. It'll eventually calm down, and if it annoys you, you can uninstall through TiBu or whatever app you choose, or manually renaming, removing or deleting the apk in /system/app.
FAQ
Yup, I already have some questions about this, so here's some answered here.
Q: Should I do a full wipe before flashing this?
A: It's always recommended to do a full wipe moving from one base to another, or upgrading from one version to the next. IE, CM9 to CM10. You can always feel free to flash anyways and see how it goes, but if you have problems, you'll know why.
Q: What can I restore?
A: As usual, you can restore whatever apps you wish, however I suggest not restoring System apps (red in TiBu) or their data. User apps and data (green in TiBu) are generally safe. Restore in steps, a few at a time, and check for any issues, reboot, then try some more. This is the careful route, of course. Issues from User apps and data are pretty rare unless the app is outdated and doesn't work with Jellybean.
Q: What works and what doesn't?
A: Please view the Dev thread for this information, it will be more current and up to date. The link is in the first post of this thread.
Q: I hate this new 7" Jellybean UI, how do I get the combined bar back ("Tablet UI")?
A: Setting density to 130 or lower will force the normal Tablet UI back to ICS style. This of course comes at the cost of some apps not working, play store issues, and everything being smaller on the screen. Up to you if it's worth it in the end.
Q: Why is there still the CM9 Boot Animation? Isn't this CM10?
A: Yes, it's CM10, however CM hasn't included a new boot animation for it, even CM9 went for awhile before one was introduced, and it was later changed to the current version. It'll happen in time as ideas are tossed about and the new animation is voted in, then gets merged for the appropriate device types and resolutions.
Q: If this is just a preview, when will we see an Alpha, Beta, or RC?
A: Don't ask. waydownsouth is only 1 man, and he can only do so much on his own. As the device tree gets cleaned up and the rest of the Iconia-Dev guys can get to cracking, it'll move along quickly. Until then, sit tight, and don't ask for an ETA. Or, just take this as your ETA "It'll be done when it's done."
Q: I use the Crossix Mount Swap script and now everything is broken, what gives?
A: The Crossix Mount Swap was intended for HC then ICS, it hasn't been updated for JB yet. Please stop using it. If you use it, please stop reporting storage issues as bugs, its not the ROM, its the script. If you choose to use it, consider your CM10 warranty void.
Q: Does the EzT20 Kernel work in CM10?
A: Reports say yes, it does, however WDS changed the audio hal from nVidia's to something far better (notice CM9/CM10 doesn't pop like stock based ROMs? Thank him for that) and the EzT20 kernel still uses the nVidia audio system. While it appears to not cause any outright issues, I would not suggest using it. If you choose to use it (your choice of course, have fun and experiment) please don't report any bugs AT ALL. Consider your CM10 warranty void.
Q: WTF did my overclock go?
A: Overclocking was removed in the later builds (preview builds) for stability. Bug reports coming in due to overclocking and running a destabilized ROM are hard to track, and are generally not a real bug, just system instability due to overclocking or undervolting. If you just HAVE to have your overclocking, see the Q above.
Q: Will this work on my A101?
A: It will if you don't mind losing 3G. The modem hasn't been integrated yet by waydownsouth, and while I'm sure he'll get it going, he hasn't yet. If you want to play around with CM10, just make a nandroid backup, wipe, flash CM10, play with it, then go back to recovery, full wipe, restore the backup, then resume normal usage with 3G.
Q: Where is the device tree?
A: Right now WDS is keeping it private, no one has access to it, and he'll make it public when he feels it's ready to be available to everyone, please be patient and respect his wishes on this.
Q: Does linux society's kernel work with this?
A: Yes, it does, however if you have issues please don't report in the CM10 threads, but his kernel thread, if you wish to report an issue please use the stock kernel first.
I'll keep adding things as I come across them in this or other threads (even other forums if I happen across them) and PMs I receive.
Last updated FAQ 8.17.12
Flashing now...
Awesome! Flashing now...
:laugh:
Boot Animation is still CM9 (no biggie)
When the tab is unlocked it goes to Landscape mode but when you go into settings for example it turns to portrait mode but when you exit settings it goes to landscape again. Is there a setting for this that I am missing? (Yes, rotation lock is off.) Apps list is also stuck in landscape mode...
All for the moment... looks AWESOME!
Originally I did NOT restore Data, gonna live dangerously and try it to just see how it reacts. Will probably regret it but thats the fun in this. Will report back later today (Tuesday) time for bed here on the coast of Maine...
Just as mentioned above by pio_masaki, dont restore data... it will not like it. LoL Just had to try it though... now to wipe and flash... maybe I'll sleep tonight... maybe...
aszelinski said:
Awesome! Flashing now...
:laugh:
Boot Animation is still CM9 (no biggie)
When the tab is unlocked it goes to Landscape mode but when you go into settings for example it turns to portrait mode but when you exit settings it goes to landscape again. Is there a setting for this that I am missing? (Yes, rotation lock is off.) Apps list is also stuck in landscape mode...
All for the moment... looks AWESOME!
Click to expand...
Click to collapse
A lot of the weird things in Jellytime will appear here as well, namely the stock launcher always being landscape. In the pulldown there is a rotation lock button, if you choose. A lot of the odd behavior is also just Jellybean vs ICS.
The recent apps list in landscape is swipe up to remove, and in portrait swipe left or right.
2nd Go taking a more subtle approach...
2nd Go taking a more subtle approach...
Recovery - TWRP 2.2.0
Installed - pio_masaki Blackhole_System_Wipe_1.5a_A100.zip
cm-10-20120723-Unofficial-a100.zip (THANK YOU DEVS!!!)
gapps-jb-20120717-signed.zip (THANK YOU DEVS!!!)
Rebooted into system (blank screen for a few moments after boot animation stopped,known issue) let tab sit for 10 minutes. Signed in.
Loaded apps only from TiBu. Nothing screamed
GPS working: GPS Test reports 10 sats in view / 10 in use. / took maybe 15 seconds
GPS Status reports 10 sats in view / fix on 8-9 / took maybe 15 seconds
Cameras works : Front and out facing. ICS Camera app is still better that standard camera app.
Gonna play with it more as the day progresses...
Not understanding the flash process?
Greetings.
I must be missing something in the flash process. I downloaded cm-10-20120723-UNOFFICIAL-z100.zip, did
adb push cm-10-20120723-UNOFFICIAL-z100.zip /mnt/sdcard
to get it onto my a100. Ran ROM Manager and installed from the zip file. The tablet says
Code:
ROM Manager Version 5.0.0.8
July 24, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
Creating filesystem with parameters:
Size: 1283457024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 4896
Label:
Blocks: 313344
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78400 inodes and 10305/313344 blocks
Formatting /data...
Skipping erase of /data/media.
Formatting /sd-ext...
-- Installing: /sdcard/cm-10-20120723-UNOFFICIAL-a100.zip
Finding update package...
I:Update location: /sdcard/cm-10-20120723-UNOFFICIAL-a100.zip
Opening update package...
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/cm-10-20120723-UNOFFICIAL-a100.zip")
Suggestions anyone?
croldham said:
Greetings.
I must be missing something in the flash process. I downloaded cm-10-20120723-UNOFFICIAL-z100.zip, did
adb push cm-10-20120723-UNOFFICIAL-z100.zip /mnt/sdcard
to get it onto my a100. Ran ROM Manager and installed from the zip file. The tablet says
Code:
ROM Manager Version 5.0.0.8
July 24, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
Creating filesystem with parameters:
Size: 1283457024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 4896
Label:
Blocks: 313344
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78400 inodes and 10305/313344 blocks
Formatting /data...
Skipping erase of /data/media.
Formatting /sd-ext...
-- Installing: /sdcard/cm-10-20120723-UNOFFICIAL-a100.zip
Finding update package...
I:Update location: /sdcard/cm-10-20120723-UNOFFICIAL-a100.zip
Opening update package...
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/cm-10-20120723-UNOFFICIAL-a100.zip")
Suggestions anyone?
Click to expand...
Click to collapse
Which recovery do you run? Usually that assert failed means your recovery is reporting the old way, picasso / a500. The fix is update recovery, the work around is to remove the assert lines from the updater script. Has this occured with with any of the CM9 builds (if you tried any)? If its failing this but not say Flex Reaper, its because that doesn't check which device you are on.
croldham said:
Suggestions anyone?
Click to expand...
Click to collapse
You may want to boot into recovery manually do everything. Usually Rom Manager would give errors like that (even though nothing's wrong).
Installed fine with CMW recovery. Only bugs I've seen so far is the ones listed already.
I tried to use the SD card int/ext switch by copying to /etc but that did not work. No surprise there.
Used script manager to run it with SU and boot and it seems to work. However, I was not able to access anything in the SD card. It boots up fine and the folders are there but not accessible. Anyone have better luck? Did I miss a step somewhere?
pio_masaki said:
Which recovery do you run? Usually that assert failed means your recovery is reporting the old way, picasso / a500. The fix is update recovery, the work around is to remove the assert lines from the updater script. Has this occured with with any of the CM9 builds (if you tried any)? If its failing this but not say Flex Reaper, its because that doesn't check which device you are on.
Click to expand...
Click to collapse
CWM-based Recovery v5.5.0.x (thor2002ro rev1.7)
I haven't tried any CM9 based builds, I was going right from stock 4.0.3 to Jelly Bean.
You may want to boot into recovery manually do everything. Usually Rom Manager would give errors like that (even though nothing's wrong).
Click to expand...
Click to collapse
Tried this too, booted into recovery and selected 'install from zip file'. I get finding...opening...Installing update...Installation aborted. Is there a way to do it from adb?
croldham said:
CWM-based Recovery v5.5.0.x (thor2002ro rev1.7)
I haven't tried any CM9 based builds, I was going right from stock 4.0.3 to Jelly Bean.
Tried this too, booted into recovery and selected 'install from zip file'. I get finding...opening...Installing update...Installation aborted. Is there a way to do it from adb?
Click to expand...
Click to collapse
Have you tried downloading again to make sure its not a bad download?
croldham said:
CWM-based Recovery v5.5.0.x (thor2002ro rev1.7)
I haven't tried any CM9 based builds, I was going right from stock 4.0.3 to Jelly Bean.
Tried this too, booted into recovery and selected 'install from zip file'. I get finding...opening...Installing update...Installation aborted. Is there a way to do it from adb?
Click to expand...
Click to collapse
It's your recovery, thats the old recovery, updating with the new CWM or TWRP will correct this error for any zip you will try to install. Mine all have that check on them, and do all CM builds.
Here is TWRP, my personal favorite
Here is CWM, also a very solid recovery
Either of those two will offer a fix for this issue on any ROM you flash in the future.
Theonew said:
You may want to boot into recovery manually do everything. Usually Rom Manager would give errors like that (even though nothing's wrong).
Click to expand...
Click to collapse
pio_masaki said:
It's your recovery, thats the old recovery, updating with the new CWM or TWRP will correct this error for any zip you will try to install. Mine all have that check on them, and do all CM builds.
Here is TWRP, my personal favorite
Here is CWM, also a very solid recovery
Either of those two will offer a fix for this issue on any ROM you flash in the future.
Click to expand...
Click to collapse
pio_masaki: You are right, I flashed to TWRP and was able to successfully flash Jelly Bean. I had to turn off archive integrity checking to do it, but the flash went fine and I'm now "munching them beans."
I have a bunch of desk work to do today so I'm going to be watching Netflix as a test.
here are my first impressions:
-device is stuck at landscape during home screens and app drawer as previously reported.
-HDMI audio is definitely not working for me. Tested with MX Video.
Will edit and add more issues as I find them.
On a side note, is Chrome being problematic for everyone else since the last update? (ICS too) Sometimes it won't render websites or freezes itself, all it takes is a swipe on the task manager and open it again to get it to work, but it still seems unreliable and inconvenient.
littleemp said:
here are my first impressions:
-device is stuck at landscape during home screens and app drawer as previously reported.
-HDMI audio is definitely not working for me. Tested with MX Video.
Will edit and add more issues as I find them.
On a side note, is Chrome being problematic for everyone else since the last update? (ICS too) Sometimes it won't render websites or freezes itself, all it takes is a swipe on the task manager and open it again to get it to work, but it still seems unreliable and inconvenient.
Click to expand...
Click to collapse
Chrome has been problematic for awhile, I think we figured out the version that they started in either the aoikaze thread or the cm9 nightly thread. Also I think the tegra drivers has a memory leak issue that causes issues with chrome.
Thank you for reporting the HDMI audio it was something I could not test as I don't have a cable for it. I'll forward it to wds.
Tapatalked from my Galaxy S II.
Agreed on Chrome--it was flaky on ICS for me a well.
---------- Post added at 11:26 AM ---------- Previous post was at 11:10 AM ----------
So far so good with 4.1. Couple of things I've noticed--the keyboard is much more sensitive than under ICS and repeats keys often (like the old double-bounce problem with the first electronic keyboards). Second, as has already been noted, Chrome isn't stable really.
I have another question somewhat unrelated--I have several email addresses but I route them all to one account. Can the stock email client allow me to change the From: address for an email? It shows it in the compose/reply screens but tapping on it doesn't do anything. I haven't found another client that makes this easy.
Need to do more testing, but I think the light sensor/automatic Brightness might not be working properly.
littleemp said:
Need to do more testing, but I think the light sensor/automatic Brightness might not be working properly.
Click to expand...
Click to collapse
Ah yeah forgot that one. It does work, however resume while on auto makes it 100% brightness. Wds is taking a look at the brightness levels as they are currently incorrect. It didn't bother ICS but JB seems to care.
Tapatalked from my Galaxy S II.
I remember a way to backup all your apps into a zip, will it work for jelleytime?
sent from my sexy-a$$-iconia tab
das_webos_transformer said:
I remember a way to backup all your apps into a zip, will it work for jelleytime?
sent from my sexy-a$$-iconia tab
Click to expand...
Click to collapse
I don't see why not, TiBu etc all work fine. Haven't tested that personally though, so maybe report back if it works or not?
Tapatalked from my Galaxy S II.
I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?
cisoprogressivo said:
I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?
Click to expand...
Click to collapse
haven't found a method yet so far,just wait till international version rom release
Same here. Couldn't find a way to install Play Store yet >_<
The only way for now, is either to wait for a miracle on a root method on the tablet, or wait for the official international release for their ROM.
My N1 is back into its box, as it's pretty much useless now, since over 80% of the apps these days requires Google Service Framework.
It's fine to be a MP4 player now.Install MX player, some comics reader, and some China online games. Hope official GSF come out asap.
LeignHan said:
haven't found a method yet so far
Code:
,just wait till international version rom release[/QUOTE]
I tried several times also. I noticed the model at GMC was had the chinese version info on the back of the device but was running Play Store. Tried a few versions but it exited after a breif pinwheel. The N1 device is listed on googles accepted device list pdf with no specific model information. Maybe the next version of Play store ? IDK how it works. Anyway device is not useless for me - I found most apps I require on Amazon Store or APKs. The Nokia zlaunch is excellent and waking up with screen double touch I like also. I owned apple ipad mini and prefer the build of this. Feels very sturdy - well built.
Click to expand...
Click to collapse
I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?
crys_ said:
I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?
Click to expand...
Click to collapse
I think the GAPPS zip file is not signed officially. Unless 3rd party recovery is installed, the un-signed gapps is no way to get into N1.
How did you get adb working? It doesnt seem to work for me with the Google USB drivers
EDIT: Nvm I figured it out, I needed to manually install the Google USB driver
Hello,
Has anyone of you checked if fastboot is available? Is the bootloader finally locked or not?
What have you actually checked/tested? At least could save some other guy sometime avoiding non-working retries ...
---------- Post added at 09:29 PM ---------- Previous post was at 09:19 PM ----------
Just in case it gives someone some idea. Latest nexus player came with a 64bit Atom. Could gapps be obtained from there? Just in case architecture is the problem ...
inakipaz said:
What have you actually checked/tested?
Click to expand...
Click to collapse
Okay, so I am far from an expert, here's what I found:
1. You can boot into fastboot by pressing power + vol. down when the device is off. See the attachment how it looks. I've tried a few oem commands: fastboot oem unlock, fastboot oem ?, fastboot oem command list, they don't work.
2. AFAIK there is no root method. I've tried Kingo root, others tried Root Genius, both fail to root it. Looking at chinese forums with Google translate looks like they're waiting for an international ROM with Google stuff to flash.
3. You can install Google play services. It will just crash each time something tries to use it. I've made a sample app that tries to use it, I see these exceptions in Logcat:
Code:
java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.gms.app.settings.GoogleSettingsActivity}: java.lang.SecurityException: caller uid 10060 lacks any of android.permission.INTERACT_ACROSS_USERS
java.lang.RuntimeException: Unable to create service com.google.android.gms.gcm.GcmService: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
If you are interested in anything else I can try it (unless its some dangerous stuff)
Thanks syddd,
As you say i would not flash anything. I'm not an expert either.
In other ocassions a command useful to me was to boot (not flash) into custom recovery. For recovery I would try one working on similar hardware ... And from there, install superuser to root. If it is simply a clean android, that should do it.
As I said previously on other posts, I will start doing this works on mine once I got one by mid-april.
Remember, It is always important to backup current status!
As I first step I will test something like it appears on this guide for the nexus 7:
http://forum.xda-developers.com/showthread.php?t=2415668
Adapting things to similar hardware ...
Trying fastboot boot with custom recovery to know if the device is locked. If it is it should not allow this operation.
Something like method 1 in this other guide
http://forum.xda-developers.com/nexus-player/orig-development/root-google-adt-1-android-tv-t2962905
Guide on how to port CWM
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Similar guide on twrp
http://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Thanks for the guide!
I tried to follow the clockworkmod recovery one, but could not dump the boot partition. I am thinking of extracting it from the official ROM, I just dont know where those are... We could find out by snooping on the connection while the device gets a new update.
EDIT: Also "fastboot boot test.img" results in:
C:\>fastboot boot test.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 2.521s]
BUT the device does not reboot and I see the following for a split second:
"boot command stubbed in this platform!"
where test.img is just an emty file. Does this mean that the boolloader is locked?
EDIT2: I've managed to get 2 update files by clicking the "check for update" button and snooping with Wireshark what happens. It makes a POST request to http://www.fc811.com/OTA/GetOTAFirm...&fw_id=A5CN30B&serial_no=XXXXXXXX&version=1.0 , where serial_no is the serial of your device (found in the about menu) and fw_id is your current firmware. I could download 2 firmwares with this method A5CN30B and A5CN315B. Both are minor updates, if someone has the fw version from the initial release it would be useful because we could get the 5.0.2 update.
I've put these in my dropbox: https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN30B_update.zip https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN315_update.zip
Both have a droidboot.img file inside them, which is a RAMdisk boot image.
Really really nice advances!!
Thanks! You`ve been able to download I think a valid ROM for the device! Now it should be explored ...
And yes, I suppose the boot is locked which means it will not be easy to make changes.
We will need more expert hands to guide on what's next ...
In my opinion I would try to open the Image you have downloaded.
I've opened it, as you can see they are simple .zip files. But they are not ROMs. Part of them are Android patchfiles which contain just binary diffs. The bootloader is a RAMDisk which can be opened and patched with the methods you linked. The big question is whether they can be installed or not.
EDIT: see my other post, one of the older updates contains a full system image
I've been using for about 2 months. And had it repaired once, 'coz of screen issues. They sent me a new one. Very nice! Just the color changed from silver, originally, to grey, otherwise is fine.
The battery is good. It could last longer, if very much, when compared with N7.2013.LTE. The new Intel Atom looks very promising. But as you all know, there's no google play store. So I left it sleeping in the drawer.
New Play Store APK available. Just in case can anyone test it on the device?
http://forum.xda-developers.com/showthread.php?t=1996995
Hope it now works ...
It does not work.
It installs normally, but closes when I open it, just like previous versions. The problem is that play store/Google play services need some special permissions that need root. So no root = no play store.
Just need to wait for the international ROM to leak for this thing. The problem is Nokia is taking it's sweet time to release this thing anywhere else....