Hi All,
As I'm sure you're aware, there was a new Ouya update yesterday (Jackalope), and its stopped the Mod a Collection working?! Here's what I did and what I get now.
My Ouya was rooted, I had installed the Goole Play store using the Mod Collection and Xposed installer. When I turned my Ouya on last night, it automatically starting to download the latest update, even though I set 'Do Not Auto Update' in the Mod Collection. However, when it was trying to download, after a while it rebooted itself and tried again, when it finally downloaded the update, it rebooted and asked me to Click Ok to install the update. So I did, and it got about half way through and went straight to the black screen with OUYA in the middle, and a red Exclamation mark underneath it.
This process went round and round for about half an hour. I searched and saw that lots of people had this with previous updates. So to fix it, I factory reset the box, and it downloaded and went straight through no problems, great!
I then started to download all of my side loaded apps via my Dropbox, such as Xposed installer, Mod Collection, Rootmyouya etc etc, so I could get the play store re-installed.
However, when I went to root the box, it was already showing at Rooted, which I thought was strange, as I've read that updates un-rooted the device?! I thought nothing of it, however, when I went to install the Mod Collection APK, it installed and when I went to open it, it gave me an error at the bottom of the screen, something along the lines of 'could not access android/apps/whitelist' and immediately closed?!!
This is really frustrating as I want to put the Play Store back on, but without the Mod Collection I'm stuck! Xposed installer seems to be ok though.
Any one with any ideas, or having the same problem after the Jackalope update?
This update has also caused another annoying issue, I'm using the Mele F10 Pro remote for the Ouya Menu and XBMC, no problems up till now, after the update the 'home' button on the remote in the ouya menus now does nothing, and when in XBMC it does nothing, however, what was the Context Menu button on the remote for XBMC (the button next to the home button), is now the 'back' button' in XBMC?!!
Help?
Cheers
dmn1981
Download and flash the stock image, and wipe everything. That solved all my problems.
Sent from my XT1060 using Tapatalk
tcollum said:
Download and flash the stock image, and wipe everything. That solved all my problems.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
How do u flash a stock image???
Barney007uk said:
How do u flash a stock image???
Click to expand...
Click to collapse
You can use CWM recovery to flash it.
Manni5000 said:
You can use CWM recovery to flash it.
Click to expand...
Click to collapse
I have that installed but not really sure how I get a stock rom onto the ouya in the right place.
Barney007uk said:
I have that installed but not really sure how I get a stock rom onto the ouya in the right place.
Click to expand...
Click to collapse
You can download the latest firmware here:
dlyv5j2269q7v.cloudfront.net/ota/RC-OUYA-1.2.853-r1_ota.zip
Adb push or simply copy the zip file to the root of your Ouya's sdcard. Then reboot to CWM recovery (adb reboot recovery) and select "install zip from sdcard".
We are OUYA FREE and one of our contributors BillMan came up with this step by step allowing you to update without having to wipe your entire system then download the factory image this allows you to install the update while rooted. a quick reminder always reboot and try again anymore questions were always here to help. thanks again goes to BillMan for creating the step-by-step shown below:
"I just know how bad it sucks finding information sometimes, so just share the heck out of it, and please touch it up. Lots of spelling errors
Thanks.
If your Ouya is trying to auto update Try to go to Make, if you can't, restart and try again, you can also try to skip to step: #
1)Go to Make
2)Go to SuperUser
3)Click Play
4)Highlight Xposed Installer (If not listed, you can move on to step 6)
5)Click trash can in upper right corner of screen and Xposed Installer should be removed.
6)Click A button on controller to go back all the way to main menu.
7) If not auto updating on it's own, go to Manage
8)System
9)System Updates
10Start installing the update
11) Super User will come up after installing update, Click on Deny
Make sure to do this otherwise you will have to restart the process over again and it is hard to start with step 1, could result in several restarts and fast clicking until you get it.
12)Once system reboots, go to Make
13)Root My Ouya by Wonder Ekin
14) Click Play
15) Super User may come up, if so, click Allow
16) Should say Rooted, I clicked Start Root and had it do it again just to be safe, you shouldn't have to however. But it hurts nothing to click Start Root anyways
17)Click A twice
18)Click on Xposed Installer
19)Click Play
20) Go to Modules
21) Make sure Check mark is selected in upper left corner of screen
22) Click on Install/Update
23) Click on Reboot
24) Everything in Ouya is working just fine And you have the new system update "
you can always find us on the web by searching XBMC HELPER all one word And as OUYAFREE
8
Manni5000 said:
You can download the latest firmware here:
dlyv5j2269q7v.cloudfront.net/ota/RC-OUYA-1.2.853-r1_ota.zip
Adb push or simply copy the zip file to the root of your Ouya's sdcard. Then reboot to CWM recovery (adb reboot recovery) and select "install zip from sdcard".
Click to expand...
Click to collapse
Sorry for another stupid question but how do I get into recovery mode as I am having trouble
Barney007uk said:
Sorry for another stupid question but how do I get into recovery mode as I am having trouble
Click to expand...
Click to collapse
Follow the SDK setup section of this thread to connect your Ouya to your computer. If successfully connected, you can use the command 'adb reboot recovery' to get into recovery mode.
xbmchelper said:
We are OUYA FREE and one of our contributors BillMan came up with this step by step allowing you to update without having to wipe your entire system then download the factory image this allows you to install the update while rooted. a quick reminder always reboot and try again anymore questions were always here to help. thanks again goes to BillMan for creating the step-by-step shown below:
"I just know how bad it sucks finding information sometimes, so just share the heck out of it, and please touch it up. Lots of spelling errors
Thanks.
If your Ouya is trying to auto update Try to go to Make, if you can't, restart and try again, you can also try to skip to step: #
1)Go to Make
2)Go to SuperUser
3)Click Play
4)Highlight Xposed Installer (If not listed, you can move on to step 6)
5)Click trash can in upper right corner of screen and Xposed Installer should be removed.
6)Click A button on controller to go back all the way to main menu.
7) If not auto updating on it's own, go to Manage
8)System
9)System Updates
10Start installing the update
11) Super User will come up after installing update, Click on Deny
Make sure to do this otherwise you will have to restart the process over again and it is hard to start with step 1, could result in several restarts and fast clicking until you get it.
12)Once system reboots, go to Make
13)Root My Ouya by Wonder Ekin
14) Click Play
15) Super User may come up, if so, click Allow
16) Should say Rooted, I clicked Start Root and had it do it again just to be safe, you shouldn't have to however. But it hurts nothing to click Start Root anyways
17)Click A twice
18)Click on Xposed Installer
19)Click Play
20) Go to Modules
21) Make sure Check mark is selected in upper left corner of screen
22) Click on Install/Update
23) Click on Reboot
24) Everything in Ouya is working just fine And you have the new system update "
you can always find us on the web by searching XBMC HELPER all one word And as OUYAFREE
Click to expand...
Click to collapse
Thanks for your guide - I downloaded it and when it said it would restart and install, it went into CWM recovery, and I can't read the log as it's off the screen (is this because of overscan?) Do I have to revert back to stock recovery before it will install?
tangcla said:
Thanks for your guide - I downloaded it and when it said it would restart and install, it went into CWM recovery, and I can't read the log as it's off the screen (is this because of overscan?) Do I have to revert back to stock recovery before it will install?
Click to expand...
Click to collapse
no try adjusting it on your tv or monitor and use a Bluetooth keyboard or mouse. You do not have to change anything just follow the steps
xbmchelper said:
no try adjusting it on your tv or monitor and use a Bluetooth keyboard or mouse. You do not have to change anything just follow the steps
Click to expand...
Click to collapse
Managed to get it into recovery and installed it from a zip file instead, from here
did the update fine with root intact using CWM
tangcla said:
Thanks for your guide - I downloaded it and when it said it would restart and install, it went into CWM recovery, and I can't read the log as it's off the screen (is this because of overscan?) Do I have to revert back to stock recovery before it will install?
Click to expand...
Click to collapse
Ok so I did this the ghetto way and it worked for me.
Saw the update trying to update let it do its thing then press ok. Reboots into CWM 6.0.3.2 then let it go through untill it states the firmware is not md5 matched of something like that, then I go to top screen and scroll down to Yes Install Zip. Presto takes it boots into Jackalope with the changelog on first screen. I am still rooted and all my apps intact. Only thing I had to reinstall was [MOD][XPOSED]Mod Collection For Ouya(Play Store, Moga Controller Emu) (11202013) for CWM to reinstall because I was getting a this exclamation mark in red! when I loaded back to CWM, lost custome recovery. Once installed CWM I rechecked root was still good I have all my apps intact and no need to wipe and start all over. Have not checked for side load games has I have not hooked this up yet, but my apps work. Hope this helps others save time. Once I updated did full backup again.
don't know what the big deal to start from scratch at least for this update?
Related
Thanks in advance for the help. Like many others I have searched for something similar to what I am experiencing but have not had luck finding it. So here goes my "special" situation:
Background:
-I use a PC with Windows 7 installed
-I downloaded KFU (v. 0.9.6) and ran install_drivers
-Connected KF and ran "run"
-Selected Option 2 for a Permanent Root with Superuser
-I am not sure if this step fully worked because during the root it seemed like my PC and KF disconnected from each other and my PC flashed a message about "smartphone no attached" that I didn't catch the exact verbiage of
-I restarted my KF and found myself in the TWRP (v. 2.2.0) interface
-Followed directions from another post and selected "reboot" and then "system"
-This worked and it loaded the familiar KF home screen
-From here I again ran the "run" file from KFU
-This time I selected Option 6 for extras, then Option 1 for Google Apps / Go Launcher Ex
-The ADB Status was Online and away the install went
-Here I am not totally sure what happened, but I believe a similar problem happened as before with m PC and KF losing connection during install
-Either way, I landed on the KF boot screen (blue Fire, which implies I have FFF installed v. 1.4);
-It was stuck here so I tried the Unbrick Utility and several other suggestions from posts and was once again able to get back to the TWRP interface
-Here, I thought I had everything figured out and again navigated to "reboot" and then "system"
-This time however, I did not go back to the KF home screen and instead got right back to the TWRP interface
-It almost seemed like it tried to load the home screen (yellow word "fire"); but quickly restarted again and went back to the blue fire and then the TWRP interface
-From here, I have tried several different approached to no avail, but here is the state I am in to the best of my knowledge:
1. It appears I have FFF and TWRP installed
2. I may or may not have the Google Aps installed
3. My drivers are all still installed, but the only time my computer recognizes it is the split second when the yellow word "fire" comes up on a system reboot.
I think I am close, but maybe not. Any help is greatly appreciated and let me know if I need to provide more information. Tried to be thorough but this is my first crack at this.
hold the power button down for 20 seconds then power on when you see the white kindle blue fire press your power button to get boot menu
then select recovery from the boot menu with the power button
Download this rom http://forum.xda-developers.com/showthread.php?t=1439916
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
then hit the home button select wipe
wipe factory reset
wipe cache
wipe dalvik
wipe system
then go home again
select install again tap on rom zip flash it let it finish
then select reboot
enjoy your lovely rooted kindle fire
this is just rooted stock with playstore if you wish to try other roms use the same method with the exception of making a backup first
Thepooch said:
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
Click to expand...
Click to collapse
Thanks for the help! I have the ROM downloaded but am still cannot get my KF to be recognized on my PC to transfer files. Any suggestions on how to get the two to communicate?
Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
...or you could just pay attention to the directions Thepooch gave you. Just a thought.
soupmagnet said:
Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
...or you could just pay attention to the directions Thepooch gave you. Just a thought.
Click to expand...
Click to collapse
Thanks for getting back to me once more. I did try the directions Thepooch gave me exactly and no connection. Mounting did not allow my KF to connect. I also went into Linux and tried your code to get my KF to connect to my PC. I am no pro, but it seemed your first script just displayed a string and was rather frustrating. Inside one of the folders appeared to be a more complete script (with options 1 and 2) that your "READ ME" instructions hinted at (install_it file). I must be missing something. Would you be willing to provide more guidance on the Linux connection?
I appreciate all the help.
Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..
SOLVED!
Thepooch said:
Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..
Click to expand...
Click to collapse
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.
noobathon said:
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.
Click to expand...
Click to collapse
I think I'm going to have to change the title of that thread. I really did have faith in people.
There are instructions in that thread and in the README, and nowhere does it say to run any script other than "run_it.sh". There are separate sets of scripts for good reason.
If you had paid attention to the OP, you would have found what to do in your particular situation.
First things first:
1. Rooting essentially means you are fiddling with the installed OS. This may at times turn ugly and may result in permanent bricking of your phone (simple terms: your device will be dead, wont boot up).
2. Most companies do not entertain warranty claims for a rooted device, obviously because you have unlocked their software.
Ready to take the above risks?? Read On:
_____________________________________________________________________________________________________________
ROOTING GUIDE:
1. Charge your device to 100%
2. Go to settings/development and check the USB debugging mode to : Enabled.
3. If you have never ever connected your device to PC, connect it via USB cable. You will see that the drivers for your device will get installed.
4. Download UnlockRoot Pro v3.2 (free version) from : http://www.unlockroot.com/download.html
5. Run UnlockRoot.
6. Click root device on left panel of the UnlockRoot UI.
7. Wait till it says : your device is rooted.
8. Your device 'may' restart. Let it restart.
9. Check for 'Superuser' app in your app drawer.
10. Can you see 'Super User' app?? Congo!! Your device is now rooted.
Hey Wait !! Since you are now rooted. You can now install ClockWorkMod recovery on your device. With all the tinkering you will now do on your device, since its rooted, it becomes very important to install a 'System Backing up' tool on you phone. Every time you want to fiddle with your system, make a back up of your entire device (includes OS/Settings/Apps/Data) on an external SD card; so that if something goes wrong, you can restore your backup and your device will be good again (just like recovery point system in Windows OS).
_____________________________________________________________________________________________________________________
INSTALLING CWM and MAKING BACKUP.
1. Be doubly sure that your phone is rooted and charged to 100%.
2. Download CWM.zip file from the attachments at the end of this post.
3. Transfer the CWM.zip file to the external memory card on you device, with the help of USB cable.
4. Switch off your device.
5. Press power + volume (-) button together until you see an android logo. The moment you see the logo, release the buttons.
6. You will next see an android bot logo, with his heart ripped and and exclamation mark on it. He's heart broken that you are fiddling with him.
7. Dont freak out. Now press volume (-) button again and you will see the default recovery manager.
8. Scroll down by pressing volume (-) button, to 'install zip from ext card' option.
9. Select this option by pressing volume (+) button.
10. A new window will open.
11. Scroll down to install from 'external storage' option. Press volume (+) button to select.
12. A new window showing all contents of your SD card will come up.
13. Scroll down and select CWM.zip file. Press volume (+) button to select.
14. The zip will get installed. A new windows will open up showing the CWM recovery manager.
15. Congo !
16. Now lets take 1st backup of your System. Scroll down to backup/restore option and press power button to select.
17. Scroll down to backup and select. Backing up will start. Once finished you will be redirected to the home window of CWM.
18. Now. Scroll down to reboot system option. Press POWER button to select.
19. Your system will shut down. Manually boot up your device again.
* Be careful with the controls for 'scroll' and 'select' in default and CWM recovery. Both are different. Follow the above instructions carefully. * Every time you want to back up/restore your system you have to repeat the above steps. I have not flashed the default recovery with the CWM, so that you always have the stock recovery working, in case everything else fails.
____________________________________________________________________________________________________________
TO RESTORE A SYSTEM IMAGE YOU CREATED EARLIER WITH CWM.
1. Follow steps 1 - 15 in the above tut.
2. Once you are in CWM recovery. Scroll down to backup/restore option and press power button to select.
3. Scroll down to 'Restore' option and select.
4. Choose the backup image you want to restore. Press power button to select.
5. System restore will start and finish.
6. Reboot.
Always do a backup before you try to uninstall any system app. Never uninstall any app about which you are not sure, what it does. Follow your gut feeling.
_____________________________________________________________________________________________________________
ROM DUMP FOR MIBOOK MI3
Download ROM Dump from this link : http://www.4shared.com/zip/uPMcjz3H/ROM_Dump.html
Put zip on SD card and update from CWM recovery manager, to restore your stock ROM.
_____________________________________________________________________________________________________________
Reply back immediately if your device runs into any problem coz of the above instructions. If everything goes good, hit THANKS
_____________________________________________________________________________________________________________
CREDITS
1. To XDA member SaM-RoN for discovering and posting root method and guide prior to me. :good:
______________________________________________________________________________________________________________
Dengabhi said:
I have not flashed the default recovery with the CWM, so that you always have the stock recovery working, in case everything else fails.
Click to expand...
Click to collapse
Does the stock recovery gets totally replaced wen u flash with CWM or can u revert back to stock recovery later if needed?
Also can u create a flashable zip file or tpt of the stock recovery? It would be great.
Sorry I m a noob dont know anything about android development but just basics of rooting and flashing.
hey bro...CWM is working perfectly..... gr8 job...but where is the credit of rooting guide????i think you should mention it here...
djsanta said:
Does the stock recovery gets totally replaced wen u flash with CWM or can u revert back to stock recovery later if needed?
Also can u create a flashable zip file or tpt of the stock recovery? It would be great.
Sorry I m a noob dont know anything about android development but just basics of rooting and flashing.
Click to expand...
Click to collapse
Yes. The stock recovery will get replaced if u flash with a flashable CWM image. Working on the same. Will post soon
SaM-RoN said:
hey bro...CWM is working perfectly..... gr8 job...but where is the credit of rooting guide????i think you should mention it here...
Click to expand...
Click to collapse
Thanks mate. I skipped to give u credit for the root guide, simply coz I just discovered it late and you posted earlier than me. I was trying super one click root and several other scripts before discovering the unlock root option. Will update my post with credit to you soon.
ROM DUMP FOR MIBOOK MI3 not working
Byond Mibook Mi3
Android 4.0.3 ICS
1.2 GHz Processor
1GB RAM
I couldn't sign into Google accounts using my Mibook mi3 tablet. It said "Cannot establish a reliable connection to the server. This could be a temporary error or your device is not provisioned for data usage."
I use wifi and the connection is stable. I can browse the internet well. I tried factory resetting and getting the same error.
I cannot add Accounts in accounts and sync tab in settings as well.
So i rooted and tried to flash it with the stock flash in the thread (http://forum.xda-developers.com/showthread.php?t=2086957) hoping to resolve it.
ROM DUMP FOR MIBOOK MI3
Download ROM Dump from this link : http://www.4shared.com/zip/uPMcjz3H/ROM_Dump.html
Put zip on SD card and update from CWM recovery manager, to restore your stock ROM.
Click to expand...
Click to collapse
But the stock flash is not working. It gives an error in the beginnig itself. I re-downloaded and tried it again which did no good.
Please help me getting round the problem. Please send me a link to the stock flash or is it ok to flash it with ICS ROM. If OK please send me a link to ICS ROM.
Update available
shivji said:
Byond Mibook Mi3
Android 4.0.3 ICS
1.2 GHz Processor
1GB RAM
I couldn't sign into Google accounts using my Mibook mi3 tablet. It said "Cannot establish a reliable connection to the server. This could be a temporary error or your device is not provisioned for data usage."
I use wifi and the connection is stable. I can browse the internet well. I tried factory resetting and getting the same error.
I cannot add Accounts in accounts and sync tab in settings as well.
So i rooted and tried to flash it with the stock flash in the thread (http://forum.xda-developers.com/showthread.php?t=2086957) hoping to resolve it.
But the stock flash is not working. It gives an error in the beginnig itself. I re-downloaded and tried it again which did no good.
Please help me getting round the problem. Please send me a link to the stock flash or is it ok to flash it with ICS ROM. If OK please send me a link to ICS ROM.
Click to expand...
Click to collapse
This problem has been occuring in all mi3 tablets. I had contacted ByondTech Customer Support.
NO NEED TO ROOT TABLET FOR THIS PROBLEM.
They emailed me an update patch which again enabled Google Account access.
update.zip
Select and apply the update.zip file. [For steps check the first post for applying CWM. Similar steps just instead of CWM.zip here file name is update.zip]
Reboot and then you will be able to access Google AC, Play Store, Gmail, etc.
Thanks a lot for Update.zip
djsanta said:
This problem has been occuring in all mi3 tablets. I had contacted ByondTech Customer Support.
NO NEED TO ROOT TABLET FOR THIS PROBLEM.
They emailed me an update patch which again enabled Google Account access.
update.zip
Select and apply the update.zip file. [For steps check the first post for applying CWM. Similar steps just instead of CWM.zip here file name is update.zip]
Reboot and then you will be able to access Google AC, Play Store, Gmail, etc.
Click to expand...
Click to collapse
Thanks dude for Update.zip, was stuck for 2 days with the google account problem :good:
JB Update?
Any custom Roms with JB update?
yup, this works, but first i had to make sure that the ADB interface works from my desktop when MI book was connected in debug mode
ChiragK said:
Any custom Roms with JB update?
Click to expand...
Click to collapse
BUMP.
Anyone?
Byond Mi1 - Lying Android Bot with exclamation mark
Hello,
my topic doesn't fit perfectly, but after pressing the home and power button on the Mi1 for a few seconds, I have an Android Bot lying on his back with an exclamation mark above him.
Since the Mi1 has only a power button, a home button and a reset button, I don't know how to get it out of this state. If anyone has experienced this, and has a cure, I would be more than happy to hear about it.
I went to the local Byond support center, but they were actually not a support center anymore, they said. And searches on the net only found the same questions, but no answers. Before I try to run to other support centers in the bigger cities, I would like to try my luck here.
Thanks for listening
Stefan
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.
aeppacher said:
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.
Click to expand...
Click to collapse
Beauty I think its flashing the rogers rom to my phone from there Im good to load other roms using this odin tool? (or is it rom manager?)
also what is this clockwork mod ? I might as well go into play store and get both rom manager and clockwork?
- eddy
So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy
eddyg519 said:
So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy
Click to expand...
Click to collapse
Okay buddy looks like you need to learn some basic android 101
You are definitely not ready to root or do anything til you learn this stuff...
Okay, so first is recoveries. Basically recoveries are a bit of software that let's you flash ROMs, kernels, and whatever else to your phone. When you hold volume up and power when your phone is off, you boot to recovery. Now basically recoveries are necessary because when you are flashing a new ROM it essentially deletes the android system from your phone first so this is a way of your phone still working between flashes.
Clockworkmod is a custom recovery with a lot of features meant for flashing ROMs. There are competitors such as TWRP (team win recovery project) but clockworkmod is a great starter. Use videos or tutorials on how to use it before you flash your first ROM. I can not stress how often you need to read read and read some more.
Okay so rooting your phone. Basically there is a "root" directory of your phone. Its where all the system files are stored and it let's you do a lot of stuff, but it also means you can screw a lot of stuff up to (like really screw it up). On default you are locked out of here by the maker of your phone for various reasons. Rooting means that someone found an exploit to gain access to this folder. Usually what you then do is you find a way to inject superuser (a little app that gives root access to other apps later on). You use Odin in this case to install a stock Samsung rom (with superuser already put in the root directory of that modified ROM its installing) essentially this means you have root. Root allows you to install recoveries like clockworkmod (which you need to flash ROMs later.
Okay so that was my quick run through. At your point you need to go to YouTube and Google how to root the sgs3 and hopefully they should have one for your specific carrier. The process should be the same minus the files you flash. Essentially you should be looking for stock ROM (for your specific device) with superuser or supersu already installed. Then you should be finding a way to install clockworkmod once you have root. (You may be able to find a file or tutorial that does this in one go). I cannot emphasise enough about reading. You wouldn't be here had you read first and in the flashing business, if you don't want a sgs3 paper weight you should read first.
Oh and ROMmanager from the marketplace installs clockworkmod for you (ONCE YOU HAVE ROOT) its simple. Just download it from the play story. Click flash recovery. It will load a bit and your done. Then you can reboot into it. ROM manager (the paid version is unnecessary) it just adds extra features you don't yet need. Look at it once you have flashed your first few ROMs.
Best of luck. Let me know and slap that thanks button. I wrote this on my phone.
READ READ READ
eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!
sxorpyon said:
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!
Click to expand...
Click to collapse
He also said root wasn't sticking. He needs that before he can cwm to stick
aeppacher said:
He also said root wasn't sticking. He needs that before he can cwm to stick
Click to expand...
Click to collapse
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x
sxorpyon said:
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x
Click to expand...
Click to collapse
He shouldn't need cwm to install. If flashes a firmware with root already injected he can then just use rom manager to install clockworkmod for the first time since rom manager just needs root which he will have. You can root and keep the stock recovery on at the same time
I think his biggest issue is root not sticking. Til he does that cwm wont install
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
username4this said:
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
Click to expand...
Click to collapse
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
gooner4life said:
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
Click to expand...
Click to collapse
Your best bet is to try them.
Also give a look here:
http://forum.xda-developers.com/showthread.php?t=2544361
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
wantabe said:
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
Click to expand...
Click to collapse
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
P/S is it easier to root using that rootkit as per post above?
gooner4life said:
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
Click to expand...
Click to collapse
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
gooner4life said:
P/S is it easier to root using that rootkit as per post above?
Click to expand...
Click to collapse
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
You should not have followed that guide.
1st: Go to here: http://forum.xda-developers.com/showthread.php?t=1538053. Download the zip. DO NOT UNZIP.
2nd: Make sure that ADB is set up on your computer. To download, go to https://developer.android.com/sdk/index.html. Follow the instructions to install. Open the SDK (should be in C\development\adt-bundle-windows-x86_64-20131030\, or whereever you installed, it is an execultable file. It should have a little green android logo next to it, and it is called "SDK Manager". It will take a couple seconds to open. Once it has opened, install "Android SDK Platform-tools".
3rd: Move the Super SU zip into the C\development\adt-bundle-windows-x86_64-20131030\sdk\platform-tools, or wherever you installed the platform-tools. It should be inside the SDK folder. Just paste the zip there.
4th: Boot your Nexus 7 into recovery. Push and hold the power button and volume down button at the same time and boot into the bootloader.
5th: Boot into recovery. Do so by pressing the power button for a while, and eventually it will shut off, as mentioned above.
6th: Press and hold power button and volume down to boot into bootloader. Once in the bootloader, push the volume down button until recovery is selected.
7th: Boot into recovery by pressing the power button.
8th: In recovery, wipe the cache and dalvik under the advanced wipe in the wipe menu. Go back and click install. Click "apply from sideload", or something like that, I forgot the exact wording. Connect your tablet to your computer through a USB cable.
9th: Go back to your computer. Go to C\development\adt-bundle-windows-x86_64-20131030\sdk\ or wherever you installed the sdk. Press shift, and then right click on the folder that says "platform-tools". In the menu, click "open command window here".
10th: Copy the exact name of the supersu zip file in the platform-tools folder.
11th: In the command window type: adb sideload UPDATE-SuperSU-v1.86.zip
12th: Press enter. The name of the super su file may not be exactly that, but similar to it.
13: Reboot your tablet.
I don't know if you are a noob, or very experienced, so I made this as noob-friendly as posisble, sorry if I offended you in any way. Here are some pictures.
I did manage to boot into bootloader screen 7 the option to start, but same thing happen, it still stucked at the "4 colors" circle screen. Problem is guys i couldn't get the PC to recognise my tablet even in the bootloader screen. What should i do now?
wantabe said:
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
Click to expand...
Click to collapse
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
ok guys i think my N7 got some serious problem!!
Now it would just stucked on the Google screen and won't even go to the recovery mode!!!
What should i do now to reset it back to original state now?!!
gooner4life said:
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
Click to expand...
Click to collapse
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
wantabe said:
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
Click to expand...
Click to collapse
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
gooner4life said:
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
Click to expand...
Click to collapse
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
wantabe said:
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
Click to expand...
Click to collapse
Yep I'm serious **** now! Any more experts here have any idea? Or do i have to bring it to local mobile shop to get it fixed? Is Google able to help ?
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
wantabe said:
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
Click to expand...
Click to collapse
Nah i was just using the SuperSU zip i downloaded as per youtube link. The problem is my PC cant detect my tablet and i can't do sh**t!
Any manual hardware reset option on N7?
If a factory reset didn't clear it up you might be able to get away with just flashing the system image. Long pressing won't make it reboot?
I'll tell you how the tablet is right now, and hopefully you have some ideas where to go from here.
Atm, when i turn on and off the tablet.
but when i turn it on, it will go straight to the google screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP , and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7?
I'll tell you how my tablet is right now, and hopefully you have some ideas where to go from here.
ATM, I can turn on and off the tablet., but my PC won't recognise it
However, when i turn it on, it will go straight to the 'Google" screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP as before, and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7? :crying:
Hashcode said:
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 8.9"
Click to expand...
Click to collapse
I want to upgrade my Kindle Fire HD 8.9" with Hashcode's latest marvel. I'm currently running LiquidSmooth, and I'm a bit confused (make that very confused) about the steps I need to take to install it.
Can anyone who has flashed from a similar state give some instructions?
Does the lack of replies mean nobody else has done something similar?
nigelmercier said:
Does the lack of replies mean nobody else has done something similar?
Click to expand...
Click to collapse
I did this a while back. As I recall the install is simply a clean install (i.e.; backup everything; wipe both caches, data and system; flash ROM and GApps; wipe Dalvik cache; reboot system). I think you will find references to this process throughout the original thread. Make sure you have the most recent version of TWRP.
Sent from my Amazon Jem using XDA Free mobile app
BobJayJr said:
.... As I recall the install is simply a clean install (i.e.; backup everything; wipe both caches, data and system; flash ROM and GApps; wipe Dalvik cache; reboot system)...
Click to expand...
Click to collapse
Thanks for the reply, but I have no idea what most of that means. Instructions for the proceedures seem fragmented throughout the forum.
nigelmercier said:
Thanks for the reply, but I have no idea what most of that means. Instructions for the proceedures seem fragmented throughout the forum.
Click to expand...
Click to collapse
I've flashed ROMS on my kindle a zillion times, so I think I can give you the CliffsNotes version.
1) Download the latest CM12.1 build from the website.
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread, as he recommends using this version for flashing CM12.1.
3) Optional (but recommended for the best experience): download the latest gapps package from the link in Hashcode's other thread concerning CM12.1.
4) Reboot into TWRP if you haven't done so already. (You can do this by pressing the power button when the kindle is turned off, then immediately pressing and holding volume up, which is the button on the volume rocker that is farthest away from the power button. Keep holding it until about 2-3 seconds after you see the blue Kindle logo.)
5) Connect the kindle to your computer and copy the TWRP update zip from your computer to the kindle.
6) Flash the TWRP update zip from within your current TWRP version. When done, reboot into recovery again. This time, when you see the TWRP version, it should read 2.8.7.0 instead of what it read earlier.
7) Optional but recommended: Hook up the kindle to the computer again and copy all files from the kindle to the PC. When done, delete the original files in "/sdcard" on the kindle and then (from the TWRP main menu) select "Backup", and choose to backup at least "Data". You could also select "system" as well, but I think this would be redundant (you could always flash the base ROM and gapps and then restore your backup). When done (it might take half an hour or more, depending on how much data has accumulated), you should copy the files in /sdcard/TWRP/ to your computer.
8) [Only do if switching between ROMs, like from Candy5 to CM): When done, select "Wipe" from the main menu, choose "Advanced wipe", and select "Cache", "Dalvik cache", "Internal storage", "Data", and "System". Swipe to wipe, wait for the wiping to complete. Go to the main menu. Immediately select Reboot -> Recovery, and ignore the warnings about TWRP detecting no installed or rooted ROM. When back in recovery again, hook the kindle back up to the PC and copy the CM12.1 (and gapps, if you downloaded it) .zip(s) to the kindle. Then go ahead and flash them from TWRP (if you choose to install the gapps, remember to flash CM first and then the gapps). If you didn't flash the gapps (which automatically clear out both caches during flashing), make sure to wipe both caches when done flashing CM. Reboot into system, and be patient.
9) If dirty flashing (for example, if flashing a CM12.1 8/19/2015 build over a 8/17/2015 build), all you need to do is just go to the main menu in TWRP, choose "Install", and then browse to the ROM zip. Flash it (you don't need to worry about wiping caches unless you run into issues), and then reboot into system.
Hope this helped!
That helped hugely, many thanks.
However:
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread
I thought this would be simple, but that thread first goes off to another thread talking about things like Android SDK, Stack, Freedom, and FastBoot. WTF?
[Later] I decided to ignore all this and go ahead with your excellent instructions. Most were straightforward, although I did have to delve a little to find what I wanted. For example:
[4] Reboot into TWRP if you haven't done so already. While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button) [From HashCode's thread]
8) When done, select "Wipe" from the main menu, then Advanced Wipe
Flashed CM, then GApps, rebooting...
[Later still]
Got a little pulsing cyan android face in the middle of the screen for a couple of minutes. He zoomed off, now got Android is starting ... Optimizing app XX of 87
After last app updated, 30 second delay.
Screen dimmed, but can see Starting apps
After about 10 minutes I get a message Unfortunately Bluetooth Share has stopped
Screen eventually came back to higher brightness. I think it is working.
WOOT!
Note, the message Unfortunately Bluetooth Share has stopped comes up from time to time, although BT is turned off.
nigelmercier said:
That helped hugely, many thanks.
However:
2) Also download the TWRP 2.8.7.0 .zip for jem from Hashcode's thread
I thought this would be simple, but that thread first goes off to another thread talking about things like Android SDK, Stack, Freedom, and FastBoot. WTF?
[Later] I decided to ignore all this and go ahead with your excellent instructions. Most were straightforward, although I did have to delve a little to find what I wanted. For example:
[4] Reboot into TWRP if you haven't done so already. While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button) [From HashCode's thread]
8) When done, select "Wipe" from the main menu, then Advanced Wipe
Flashed CM, then GApps, rebooting...
[Later still]
Got a little pulsing magenta android face in the middle of the screen for a couple of minutes. He zoomed off, now got Android is starting ... Optimizing app XX of 87
Screen dimmed, but can see Starting apps
After about 10 minutes I get a message Unfortunately Bluetooth Share has stopped
Screen eventually came back to higher brightness. I think it is working.
WOOT!
Note, the message Unfortunately Bluetooth Share has stopped comes up from time to time, although BT is turned off.
Click to expand...
Click to collapse
The Android SDK (which at the bare minimum would include fastboot and ADB) would only be needed when rooting and backing up the stock software and flashing the custom boot, bootloader and recovery files. Even then, you'd most likely only need it for rooting (and backup of stock firmware), as the FireFlash app (for stock Amazon OS only?) would flash the files for you (once you plug them into the app, anyway).
The stack file (for the HD 8.9's stock firmware) is meant to block OTAs for Amazon's software. You wouldn't need to worry about it once you install a custom ROM. Similar story for the freedom-boot img - it's only needed for Amazon's stock software, as it is one of the "keys" that enables custom ROM access on the Kindle.
As for TWRP:
1) Seeing as though you flashed LiquidSmooth, I was thinking that you had known how to get into TWRP. For future reference, you do have to press and hold the volume up key (near the headphone port, or farthest away from the power button) before the yellow Kindle logo turns blue to boot into TWRP.
2) My mistake - you do need to select "Wipe" from the main menu, and then "Advanced wipe" from there to choose which partitions to wipe. (I've been flashing ROMs for so long that I forgot to mention that!)
The pulsing android logo you got after rebooting from TWRP into system was the CM12.1 boot animation featuring the CM mascot, Cid. I'm assuming it worked if you managed to get that far.
Finally, I'm thinking that the BT share crashes might be a momentary issue - I would wait until the next nightly and see what happens. Glad I could help you out!
Thanks for the extra information.
Please note that I meant to be in no way critical of your excellent instructions, I was just laying down a timeline as I did the upgrade in case it was helpful to others.
monster1612 said:
... Finally, I'm thinking that the BT share crashes might be a momentary issue - I would wait until the next nightly and see what happens...
Click to expand...
Click to collapse
Just installed cm-12.1-20150820-NIGHTLY-jem.zip but the "Unfortunately Bluetooth Share has stopped" problem persists. I'll try again in a few days. I don't seem to have a working Disable button for Bluetooth Share.
Some other related issues:
[1] When I first did the update I was asked if I wanted to root the device, I said no. I just updated again (without GApps this time, wiped both caches) but didn't get this option. Would rooting help with the Disable button?
[2] I flashed without GApps as I really don't need any of the stock apps, except Google Play so I can download a few selected apps. However, without GApps, there is no Play! Is there a way to install just this?
nigelmercier said:
Just installed cm-12.1-20150820-NIGHTLY-jem.zip but the "Unfortunately Bluetooth Share has stopped" problem persists. I'll try again in a few days. I don't seem to have a working Disable button for Bluetooth Share.
Some other related issues:
[1] When I first did the update I was asked if I wanted to root the device, I said no. I just updated again (without GApps this time, wiped both caches) but didn't get this option. Would rooting help with the Disable button?
[2] I flashed without GApps as I really don't need any of the stock apps, except Google Play so I can download a few selected apps. However, without GApps, there is no Play! Is there a way to install just this?
Click to expand...
Click to collapse
To answer your questions:
1) You wouldn't need to root, as CM already ships with root pre-installed (it's just hidden and disabled by default). To enable it, all you'd need to do is:
Open the settings app, then tap "About Device".
Tap on the build number 7 times. You'll know you're doing it right when you see a toast notification at the bottom of the screen saying "You are now x steps from being a developer."
When you see a toast that says "You are now a developer!", go back to the main settings screen and choose the newly enabled Developer options.
In this screen, look for the "Root access" setting. Tap on it, then select "Disabled". Tap on it again, and this time select "Apps" or "Apps + ADB". Agree to the warning about the dangers of root.
You should be able to grant and deny root access to apps now.
2) I would look for a minimal/micro gapps package for lollipop (5.1 compatible if possible). While I don't think it would be completely devoid of anything that isn't the Play Store or its dependencies, I think that this is the closest you can get to it. I'll try to look for another solution and update the post as needed.
Thanks again for your reply. Don't go out of your way looking for a minimal GApps package, I can just use the standard one instead. I was just trying to be clever, and failing
My main concern is the "Unfortunately Bluetooth Share has stopped" problem. I honestly don't care if it has stopped working, I just don't want to be told anymore!