Develop Bugs

Boot looping issue

Was messing around with my phone flashing roms to see what I liked best and got too far ahead of myself and forgot to wipe data and cache. Now, I'm stuck in some kind of "boot loop" and can't get back into ClockWorkRecovery(Via root) to perform a restore. My computer just isn't recognizing that I have my phone connected now although it did previously. Is there anything I can do in this situation, or am I basically screwed?
Edit: I solved the issue on my own, it just took lots of playing around and disconnecting/reconnecting before I was able to get back into CWR. If a mod sees this, go ahead and delete this thread it has no purpose.

HELP
Please, i have the same issue
My phone has been bootlooping for a week now, so much i decided to give up.
Please please please tell me how you got back to clockwork and then from there what to do
Thank you so so much in advance

My guess, and this is only a guess, is to try the following.
Assuming you have already flashed the ENG build...
1. Place a new update.zip (clockwork recovery) onto root of the phone's SD card (probably using a card reader, just to be on the safe side).
1.5 Turn the Phone off, if it's on.
2. Hold down Volume Down + Power Button to turn on the phone and boot into the phone's default recovery.
3. Press Volume Up + Power button to get the selectable menu.
4. Select the "Apply update.zip" option (2nd one down).
5. This should boot you into the Clockwork Recovery.
From there, locate the ROM you want to use that's meant for the Slide (like SlidemeRoot 5).
1. Download the ROM.
2. Navigate to the mount menu in clockwork and select the option to mount the card as USB Mass Storage.
3. Plug the phone into the PC (via USB cable).
4. Copy the ROM to the card.
(My trick here is to redownload ROMs. I've seen my phone bootloop when the ROM doesn't download all the way.)
1. Unmount USB.
2. Navigate to the Wipe Data/Factory Reset option.
3. Select Yes from the menu to wipe everything.
4. Locate the install any zip option and install the ROM
5. When that's done, select the reboot option.
From here, you can just leave the phone alone until it boots. If you worry or want to watch, use adb to watch the logs.
1. In command prompt, navigate to where you have ADB installed.
2. type in: adb logcat
3. Enjoy.
For me, the first boot for SlidemeRoot took at least a minute. I could see the logs rolling along, so I just left it alone until the logs slowed down and then stopped. By then, the phone looked like it was ready to go (complete with normal screen, signal, and everything).

I did the same thing, but I havent flashed my rom with the eng build, is there anything I can do, or is my phone hosed? My phone wont boot, and I cant get it to boot up in clockwork, so I cant reflash it...

Failed Root; Stuck in Loop "process com.google.process.gapps has stopped"

Hello and thank you for taking time to read this post.
I attempted to root my At&t Samsung Galaxy S3 today then install tha AOKP Rom, and it back fired due to poor instruction, and poor execution. At the moment my phone, whenever it turns on "inititing swager" (with a pink horse and gears) then gives me a pop-up saying "Unfortunatly the process com.google.process.gapps has been stopped." and "Unfortunately, Setup Wizard has stopped". Whenever I hit ok, the other shows up. I have access to the pull down menu, but can't open any of the links on it. I can also shut it off then get back to the root(hat menu) menu. From which I have tried the option "wipe data/Factory Reset" link, but that changes nothing when I reboot. At this point I am just looking for a way to get it back to factory settings or at least working!
How I got here:
1. Rooted the phone through my computer (successfully it seemed)
-Using this tutorial: /watch?v=bIUA1IxiJzo
2.Started puting AOPK on!
(with this: /watch?v=qzcR-G7EKSw
Look, I know none of you have to help me but any feedback will be greatly appreciated.
P.S. I hav looked through other forums about the gapps error, but the difference is mine is not running to the home screen so I can't go to application manager!

Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.

Thank you for responding so quickly! I am attempting the first method, however i am not sure how to transfer a different rom image(im assuming the adb stands for Android Debug Bridge). I was using the internal SD, but I can plug it the phone into my computer, and it says no drivers found for this device, where before it recognized the phone. Once I get that I can clear the other data and restart.
Your help is very appreciated!
smelenchuk said:
Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.
Click to expand...
Click to collapse

Gapps loop
How can I post a doubt in XDA forum?

What custom recovery is on your phone? I suggest installing Philz Touch via Odin if possible and then flash a new rom from an external SD card.

some rooting help PLEASE

Ok i would like to help andro vista for the help he has given me, but he is gone to bed due to time in India.
I followed AV's instructions
Amazon Kindle Fire First Gen ('otter' is the codename)
You are running stock.
By rooting you do not get updated to the latest version of android.
You get access to the system files though.
Here are the steps.
1) ensure your battery is at least 90% before doing all this.
2) go and download kfu 0.9.9
3) extract it to your desktop
4) open the folder and run install-drivers.bat
5) install the drivers
6) now install the drivers
7) open the run. Bat file
8) now connect the kindle to the computer
9) if you installed the drivers correctly then under the options it should show
Adb Status nline
Boot Status: 4000
10) select option 2- install permanent root with superuser
THIS WILL NOT UPGRADE THE ANDROID VERSION!
WAIT DUDE GO BELOW
11) now the device should reboot after booting into a recovery.
12) Do this step only AFTER IT BOOT NORMALLY, THAT IS, TO THE LOCK SCREEN
Go to run.bat and select option 3 - install latest TWRP recovery
After it reboots go to the lock screen
Now shut the device down. Switch it on. Yes don't panic, the kindle fire logo is blue! At this point again push the power button. It should cycle through a list. Release the button when it says recovery.
It will not you into a cool gray screen. On the top, make due it says 2.6.3.1
IF YES, go to reboot button
System
Now no need to press the button
Time to transfer files!
13)This is the OS I made. Download it. This is the latest KitKat operating system.
Put it in the downloads folder of the kindle. Make sure the download is complete.
DO NOT EXTRACT THE ZIP FILE
14) shut the kindle down and then boot in recovery.
15) in recovery, click backup. Select all partitions on the left.
Swipe to backup
The back up will take time. This completely stores all your OS files and data.
16) go to home by clicking the icon in the top right.
17) go to wipe and select advanced wipe.
18) select all OTHER THAN SDCARD
this wipes all your data and the operating system. It is very necessary
19) now go home
20) click install
21) go to the downloads folder and select the file you just put in download
The infriction one
22) select it and swipe to confirm flash!
23) wait. After its done select reboot system
24) after the blue kindle fire logo, notice any difference! That's the in friction bout animation! It goes of screen at first but comes back properly. Wait some time!
You have installed latest android KitKat! And g Google play store! Download your UK apps!
If you have any doubts/queries fell free to all me!
Everything was fine until i got to step 15 backup and the kindle got stuck backing up.
So he said to install flashify.
I got confused by this and thought (extremely stupidly) that I could retry flashing it, by restoring the kindle to factory settings, and starting from step 1 i could try again
I was totally wrong , and now I have this when I boot the kindle it still has the blue logo, and the three options and will boot normally
When i boot the kindle up it flashes with the blue screen with the screen options allowing normal boot etc, Anyone got any ideas how to start again
sorry i feel so stupid so could really use your help PLEASE guys as andro is gone for the night

update
ok i tried various things to try to get it to root, and made a mess of it.
Stopping now before I make a complete hash of it.
The only files left on the kindle fire first gen, are twrp v 2.0.0 so if someone could guide me in the right direction id appreciate it
nothing else seems to be left on it
windows 7 x64
all it does it boot into TWRP V2.0.0

[Q] Help w rooted? kindle fire 1st gen

I am a non developer (Read older woman and have never rooted however a couple years ago I bought 1st gen kindle fire running Cryogen mod. All went well until I decided to give away kindle and wanted to remove personal data.
after reading as much as I can I stumbled in here and found this on my kindle after repeatedly trying to re boot:
CWM- Based Recovery v5.0.2.7 Full (by DooMLoRD)
Amazon Kindle Fire : v01-FINAL : TouchEdition by team UtterChaos
-reboot options
-install zip from sd card
-apply/sdcard/update.zip
-factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
-power off
*******Go Back***********
Then it says more about Build:
CWM-Based Recovery V5.0.2.7 FULL (by DooMLoRD)
Built on:
Thu March 8 00:30:48 1st 2012
date time info then :
Current Kernel:
2.6.35.7+Lite
Ihave pressed several of those options and wanted to reset to original kindle functions but when it goes to boot the page says:
Kindle Fire (the fire is blue)
the bottom of the page says press power button to boot
it gives choices of:
Normal boot
Recovery
and reset boot mode
I have tried all of the above with no results I am obviously in over my head. I am patient and will try to follow any directions to the letter that I am given.
I appreciate your help and attention I hope I have given the information needed Thank you Very much

Chrysanne said:
I am a non developer (Read older woman and have never rooted however a couple years ago I bought 1st gen kindle fire running Cryogen mod. All went well until I decided to give away kindle and wanted to remove personal data.
after reading as much as I can I stumbled in here and found this on my kindle after repeatedly trying to re boot:
CWM- Based Recovery v5.0.2.7 Full (by DooMLoRD)
Amazon Kindle Fire : v01-FINAL : TouchEdition by team UtterChaos
-reboot options
-install zip from sd card
-apply/sdcard/update.zip
-factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
-power off
*******Go Back***********
Then it says more about Build:
CWM-Based Recovery V5.0.2.7 FULL (by DooMLoRD)
Built on:
Thu March 8 00:30:48 1st 2012
date time info then :
Current Kernel:
2.6.35.7+Lite
Ihave pressed several of those options and wanted to reset to original kindle functions but when it goes to boot the page says:
Kindle Fire (the fire is blue)
the bottom of the page says press power button to boot
it gives choices of:
Normal boot
Recovery
and reset boot mode
I have tried all of the above with no results I am obviously in over my head. I am patient and will try to follow any directions to the letter that I am given.
I appreciate your help and attention I hope I have given the information needed Thank you Very much
Click to expand...
Click to collapse
When you see options Normal boot, Recovery , and reset boot mode, that is the Bootloader
first could try selecting normal boot, just press and hold power button to scroll through boot menu options, release when normal boot is highlighted.
---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------
If normal boot does not work, try selecting reset boot mode
---------- Post added at 10:50 AM ---------- Previous post was at 10:39 AM ----------
If that does not work, and it's bootlooping (just says kindle fire over and over)
press power button till it powers off, release button and then power back on.
Select Recovery option
CWM- Based Recovery v5.0.2.7 Full (by DooMLoRD) is a older custom recovery, but should be fine.
I haven't used this version much so wording may not be quite right.
select factory reset, and confirm yes is asked, when reset is done, select reboot (may need to select home first)

Thank you for the quick response.
The device verified that it did factory reset.
In the programming page:
I now see in re boot Options are:
-reboot system now
-reboot into recovery
-reboot into fast boot mode
First I tried selecting reboot system now with the power switch as you suggested. it just keeps going to Kindle Fire (Fire is in blue)saying booting... and going back to Kindle Fire.
I closed and re opened.
Next I tried reset boot mode. (from the Kindle page)
it also returned back to the Kindle Fire page with reboot options on the bottom of page
Normal boot
Recovery
reset boot mode
I went back to reset boot mode and tried fast reboot and it seems to also take me back to the Kindle Fire page . Is this a boot loop?
thank you again

Chrysanne said:
I went back to reset boot mode and tried fast reboot and it seems to also take me back to the Kindle Fire page . Is this a boot loop?
thank you again
Click to expand...
Click to collapse
Yes, it's bootlooping or just won't boot.
power off kindle, connect to wall charger and see if it will charge,
you don't want battery to get too low or you will have a real problem.
If it will not boot to charge mode, try CWM recovery , it may charge in that mode or at least report battery status
I would
Download my pre root 6.3.3 stock rom update-kindle-prerooted.6.3.3.v1.zip
verify MD5: b4dda6ea38ad0748a7b4639ca6da95c4 see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Install Kindle Fire Drivers with Kindle Fire Utility
extract files from Kindle Fire Utility v0.9.9.zip, close zip, open kindle fire utility folder, run install.drivers.bat
reboot PC
connect kindle fire to pc, boot to recovery, select mounts and storage, check sd card, and select usb mount
you should get a pop up on PC about a storage device, select open, and copy update-kindle-prerooted.6.3.3.v1.zip to kindle
select unmount on kindle, then install zip from sd card, select update-kindle-prerooted.6.3.3.v1.zip, when install is complete , select reboot (reboot system now)

[Q] Non-stock ROM to Hashcode's LP 5.1.x KFHD 8.9"

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!