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!
Related
Ok here goes.
How do I know if it installed ok??
I got my Defy about a week ago and straight away followed the excellent procedure in the CM7 FAQ. I'm totally new to modding phones (came from iPhone) and CM7 etc, but am pretty good with computers etc.
So anyway, I had some issues, all of which I got past. No heart attack moments! I know I've got the Nordic ROM on there (I have the red Motorola logo on boot and have read lots of forum posts that point to that. Also, System Version ends in "ND" and firmware is 2.2.2). Thing is, I am loathe to mess with things that don't need messing with (I need a phone that works!!) and the install seemed to go absolutely fine.
I don't see a skateboard guy on startup which i probably enough. Have searched posts etc and not found a conclusive answer. If it's not CM7 then I'll have to try again. Annoying having installed various apps, added to phonebook etc.
Sorry about this.
next up, you need to root your phone using something like super one click, then re-boot it. next install 2ndinit defy, and follow the instructions provided in the app.
copy the cm7 zip to your SD card, if you haven't done so already, also try loading the swype app zip as well ( posted somewhere else on here)
when you re-boot you should get a blue light not long after the red M logo, press the volume down button at this point.
to navigate round the boot menu and recovery use the volume up and down to highlight an option and the power button to select.
select recovery, ( i use latest) and you should be able to find an option for back up/restore, make a back up of your current set up as a "safety net" if you want.
Next wipe data/factory re set then wipe cache, re-boot.
from the blue light press vol down, and go back to recovery, then select install zip from SD card.
again use vol+/- to select - press vol + to go straight to the bottom of the list, and load the CM7 zip, then load the swype zip, re-boot and job done.
Cheers mate
I reckon it's the 2nd Init bit. Will have another tinker tomorrow
It worked! Seems to me the only difference is that the first time round I did not reboot back into recovery after clearing cache...
Thanks very much for the advice.
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
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?
The original thread was closed...sorry guys I've been busy. Link to the rom has been updated!!!!
Eureka! After two days of trials, tribulations, and extreme reading, I have been successfully able to create a flashable, working Stock Rom for the MetroPCS XT1765. And yes, I figured out how to get root working on it too (albeit experimental)!!!! This has been something visibly lacking in our E4 community, and since its the phone I have, I felt it was a necessity since once you unlock the bootloader or ever took an update its impossible to get the original .xml back on the phone.
Disclaimers Before You Begin:
This tutorial is for people like me that wanted a flashable stock rom for the Moto E4 XT1765 Metro PCS Qualcomm/Perry Variant running on stock Nougat 7.1.1 Please follow the guide carefully. Cutting corners and skipping steps could have MAJOR CONSEQUENCES.
For everybody with other Perry variants, I don't know if this rom will work or not, so if you're feeling frisky try at your own risk as this has only been tested on the XT1765.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
Introduction
The A8M'S METROPCS XT1765-PERRY STOCKROM PROJECT was created from the Motorola PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml firmware, straight from their official site. This was not made from a backup, but from extracting the firmware files itself, and compiling via Assayyad kitchen. Nothing was removed from the firmware on this build, but you will have to flash Open Gapps and add it during installation, as well as No-Verity. Outside of that, it's a virgin rom slightly removed.
Preparation
1. READ EVERYTHING IN THIS GUIDE BEFORE STARTING! This variant can tear you a new one, so get a handle of what you're working with on this.
2. This is only for people that have bootloader unlocked their phones, and can successfully use TWRP on their device. I highly recommend @squid2's TWRP (which is in my download files list on this guide). I can also only give support for those using his TWRP, as that is the one I used flashing this rom.
3. Backup all your data if you want - the phone has to be wiped clean for this to work right as a dirty flash won't cut the mustard. It's not hard exporting your contact list, or using SMS Backup Restore for your call log and text msgs to your SD card. This helps putting back your phone exactly how you had it before this. Takes a second (but be sure to uninstall SMSBackupRestore when you've successfully restored your stuff unless you like it).
4. Download all the files from the list below,and put all of them but the boot.img on your SD card. That is the Stock Rom, the noverity.zip, the magisk.zip, superuser.zip, rootchecker, and opengapps.zip. Make sure the file sizes are correctly matching and that there are no errors in your transferring.
***NOTES SO YOU DON'T FREAK OUT***
Once you flash the rom its going to take 3-5 minutes to boot the first time. It's normal. If you see the "Hello Moto" constantly repeat, that's a bootloop, and you need to wipe and reflash again (even though this did not happen to me). Also, if you see a Bad Key black screen and it doesn't boot, you've made a mistake by not flashing no-verity after flashing the rom. It isn't a brick, you just need to go to recovery and flash it again.
Files Needed:
Download and add these to your SD card. These are the exact files I used on my phone. ***NOTE*** My file share service says they will delete these June 14th, so if you know of a fast share site that's free and can handle big files, please let me know.
Mod Edit: If / When you update these links, PM @Az Biker to reopen this thread.
1. My Flashable Stock Rom: https://drive.google.com/open?id=1ScvA3zO6qHY4mhMtaM4aDajx9ZH6CpYj
2. OpenGapps Nano: https://drive.google.com/open?id=1x3Uz_sia1N3OYPGrdEwJ7TBeSmyiDlEZ
3. No Verity Opt Encrypt.zip: https://drive.google.com/open?id=1FqcpWgYJ16HYjIzZgIlHEZOlKJPjaorM
4.Superuser-r259.zip: https://drive.google.com/open?id=1iFswMvZ2vycIrQ4tK7nTWZAG7zktrPH2
5. Magisk v14.0.zip: https://drive.google.com/open?id=1wyV5EJe2wtSIadFNZsbJQOfGrsNQzG4p
6. Root Checker (Playstore)
7. Boot.Img file in case you make it to the bonus round: https://www45.zippyshare.com/v/Uhru1YeL/file.html
Additional Software: you may need Minimal ADB and Fastboot in case you don't have TWRP installed already for the rooting part or if you run into problems trying to gain root; you'll have to search XDA for that one .
Part I - Installation:
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. As soon as you flash the stock you'll see the phone trying to push an update, as it auto turns on your data if you choose not to set up wifi (which you shouldn't do just yet).
3. Boot into Recovery TWRP. (If TWRP isn't installed, see 3A and skip this part.) If TWRP is installed you can power the device off and then hold the Volume Down plus the Power key to get into fastboot, and with the volume rocker select recovery and then hit the power button to boot. If you have unlocked the bootloader you will see N/A black screen in this process.
3A. If you do not have TWRP installed, With the phone on, run the command in Minimal ADB and Fastboot "adb devices" without the quotations. You should see your phone ID and device. Next, turn the phone completely OFF. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY). Connect device to PC via USB cable. Then open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your recovery image file is in the Minimal ADB directory or it won't work; the type "fastboot boot thenameofyourrecoveryfile.img". This should boot you to the TWRP.
4. Once booted into TWRP, tap Wipe, then Advanced Wipe; check Dalvik/ART Cache, System, Data, Cache ONLY, then swipe to wipe. Just to be on the paranoid safe side, click back (triangle pointing left) to the main menu, go back to Wipe, Tap Format Data, Type yes and wipe. Click back to main menu after - do NOT reboot.
5. Click Install; install A8M'S-METROPCS-XT1765-PERRY-STOCKROM-PROJECT-04142018.zip. Afterwards, go back to main menu.
6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
7. Click Install; install open_gapps-arm-7.1-nano-20180331.zip. Note: This takes 3-5 minutes. You will see a warning that StockRom Gapps is installed. That's okay - ignore it, its necessary. Click back to main menu after.
8. Click Install; install no-verity-opt-encrypt.zip. Click back to main menu after.
If you don't want root, hit Reboot, then System. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed. Congratulations, welcome to your brand spanky new stock rom flashed phone.
If you do want root don't reboot, keep reading the next section.
Part II - Rooting:
Okay, this section might be challenging, but hopefully this will ease your nerves as you walk through the ever so daunting task of rooting. It has some of the same challenges that rooting the .xml had (refer to my "The Complete Noob Guide to Rooting MetroPCS XT1765 Qualcomm Variant" guide for such challenges). This might feel totally redundant, and to a lesser degree it is, but it will pay off in the end. And remember, if at first you don't succeed, wipe clean and flash again!
9. In TWRP, click Install; install Magisk-v14.0.zip FIRST - very important. Do not install supersuser first. Afterwards, click back to the main menu.
10. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
4. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
5. Disable Updates. This thing will race you to that. On initial launch, you should not have the wifi connected. As soon as you put your Sim card back in, IMMEDIATELY cut off your data until you disable updates.
Bonus Round - In Case Of Error -1 Issues:
Hopefully, the first two parts got you straight, and you're playing on your stock rom now. However, this variant is challenging, and getting root could be a pain in the android ass. If you installed either superuser.zip or magisk.zip and got an Error -1 for either or both, this section is for you.
Unfortunately, the boot.img getting corrupted probably is the main culprit. Don't freak, it was a problem with the original root method on this variant straight out the box. Also, if you have been flashing/re-flashing a lot, sometimes it just makes it funky. But its a fix with a little patience.
1. Turn your phone on, and let it boot.
2. Go into your phone settings, and activate developer options (you know, hitting the build number 7x).
3. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below). Very Important. Also uncheck "Verify Apps Over USB", but only if you having probs with fastboot in ADB. You can recheck it later.
4. Make sure you've enabled Allow installation of apps from Unknown Sources (its in the Security section of Settings).
5. Turn your phone completely off.
6. Plug your phone via USB cable into the computer.
7. Press Volume Down and Power to boot into fastboot mode.
8. Open up Minimal ADB and Fastboot command prompt on the PC (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory (same place you see recovery.img that boots/installs TWRP) or it won't work. Download it from the files list above.
9. In Minimal ADB command prompt type "fastboot erase boot. " It might say permission denied, and that's okay. Keep going.
10. In Minimal ADB command prompt type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And no, you don't have to reflash the stock rom after this either.
11. Reboot into recovery - make sure you select READ ONLY when it launches.
12. 6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
13. Click Install; install Magisk-v14.0.zip FIRST - very important. Afterwards, click back to the main menu. It should be successful.
14. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
15. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
If you're still having problems after flashing the boot.img, start all the way over from the beginning wiping everything clean. That should correct the problem and let you install without trouble or needing to flash the boot.img again.
Bonus Round - In Case Of No Root After Root Issues:
As soon as the little bugger tried to force the update via my data when I stuck my Sim Card in, it messed with my root, even catching and cutting it off as quick as I could and not doing a full update. When I rebooted, I lost root. This has happened off and on every other flash - so your root may stick or it may not. If it doesn't, either you can 1. wait for a better method, 2. reflash, 3. live without it for now. This is still kind of experimental for me, as I had to wipe and reset to get root back. Still trying to figure out a more perm way for this like on the .xml.
Enjoy Everyone - I'm learning, taking it one android day at a time but I'll help when I can. It's an awesome day to be a nerd!
Sincere Thanks:
The devs that created a method of root for various variant E4's that sent me on this journey, I love you guys!
The devs behind Magisk, Superuser, and No-Verity!
@squid2 for the TWRP recovery that helped A BUNCH!
@ASSAYYED for the beautiful kitchen that forced me to keep learning.
@Al936 for the beautiful tutorial that helped me figure out how to extract the files needed in the journey.
@MotoJunkie01 for giving me the inspiration to try it on my own.
@madbat99 for the small, but powerful words of encouragement.
And to the community at large that let me ask questions to the point of getting on their nerves. Thank you!!!
[REPOST][ROM][PERRY][MetroPCS.XT1765][STOCK] A8M'S XT1765 STOCK ROM April 14th, 2018
Reserved.
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
ilanor said:
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
Click to expand...
Click to collapse
Everything is stock. Just as it was on a complete fresh out the box setup. You will find all the metropcs apps there.
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Moto_E4_xt1765_metroPcs said:
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Click to expand...
Click to collapse
you install ADB and fastboot on your computer then open the folder that contains those. Put the boot image in that folder
Pretty sure this guy that is extremely outdated though
this flashed fine and magisk and superuser flashed fine booted actually a little faster than normal. I don ' know how but it say no service though and it throws an error "error occured could not search" or something similar . how can i get my radios back
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .
Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?
I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.