I have CM7 and it's worked well, until yesterday, when I installed SD Maid and I did some delete with Corpse Finder (maybe was not the problem). And few hours later I reboot my phone (had problem with ADW), but after still reboot immediately, when the system is up.
I tried these steps:
- with the recovery mode: wipe data/factory reset, after wipe cache partition, and install .zip (CM7) from SD Card
- wipe davlik cache
- HBOOT menu (like in downgrade): install PC10IMG.zip (in recovery mode was fail)
- try to root again in recovery mode, but cant going thru on this: adb push recovery.... .img file, and after the root_psn file, until the end of the commands.
But did not work nothing.
So please help me, what I have to do?!
you could try superwipe:
http://forum.xda-developers.com/showthread.php?t=1044992
afterwards wipe also through recovery (data/cache/dalvik) and then do a fresh install of whatever...
maybe it helps
OK, it is works, but have a problem too.
After used this SuperWipe, I put CM7 also. And it was good.
But I forget the google services, and after I installed this, had a same problem with the rebooting...
...then try different gapps or do a fresh install: flash cm7 and straight afterwards gapps (don´t boot into cm7 before flashing gapps)
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
you could google for older ones
EDIT: ok in samsung galaxy 3 forum i have read that people had problems with gapps because of a corrupted sdext partition - as far as i remember from my old htc magic where i used sdext you can fix this through recovery
Sent from my HTC Vision using XDA App
Thanks. I solved the problem (avoid the problematic step). But it was another, what I guess in the first time.
So, the gapps was correct, because I started from the superwipe again, and flash CM7 and the gapps too. And it is working properly until, when I has changed the mobile connection to "only 2g" (sometimes I prefer this, because less battery usage). And got the reboot problem again.
Now I leave my mobile in 3G and still working properly.
Thanks for the help!!
Lotec said:
Thanks. I solved the problem (avoid the problematic step). But it was another, what I guess in the first time.
So, the gapps was correct, because I started from the superwipe again, and flash CM7 and the gapps too. And it is working properly until, when I has changed the mobile connection to "only 2g" (sometimes I prefer this, because less battery usage). And got the reboot problem again.
Now I leave my mobile in 3G and still working properly.
Thanks for the help!!
Click to expand...
Click to collapse
it shouldn't happen that way you should be able to change network type as you wish..
Yes, I know, but what I should to do to solve the 2G/3G switch problem?
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!
Hi all
After upgrading my Xperia M to CM 13.0 Google Play Services stopped working. I realized that only open gapps were supported on v13.0 so I downloaded the ARM, 6.0, pico version. Then I rebooted to recovery, and tried to install with
Code:
adb sideload open_gapps_[...].zip
Installation failed with an error "insufficient storage space", which is obviously not the problem since I have more than a Go free space on internal storage.
Already when I installed CM 12.1, I had to use the other gapps package (here), because it gave me the same error.
I tried to read the install log, but I can't find it (when I type adb logcat it just says "waiting for device" but nothing happens).
Could anyone be of any help?!
Thank you very much
Edit: I managed to install the open gapps .zip after wiping everything (data, cache, media) and reinstalling the latest nightly cm 13.0 build. It works, but it's still a bit annoying to have to do that. So if anyone had an idea what went on, it's still welcome!
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Metrotor said:
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Click to expand...
Click to collapse
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
LS.xD said:
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
Click to expand...
Click to collapse
I wiped everything except internal memory. And although it gave me some error, I was able to reflash CM13 and Gapps to get the phone working again. Thank you so much!
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.