I am having major boot loop I flashed the rom and gaps after loading them thru adb Push ,but no matter what keep rebooting got the blue logo for a minute and go back to safe trap battery is ok!
I already post it in android development got no answer
Go into Amazon (not Safestrap) recovery and select sideload adb, then install the official Amazon image and see if that solves it. Do a factory reset after for good measure. You'll need to go through the whole Kingroot and Safestrap install again afterwards.
Related
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.
I'm not entirely sure if this is where I should post this, but I am having a problem with my Fire Phone and I really hope you guys can help.
So, story time. I was thinking that I wanted to install a new ROM on my phone just to try some new things. I decided on the SlimKat android 4.4.x ROM and I installed it with GAPPS using SafeStrap 4.01. However, the new ROM was not working correctly so I thought I installed it wrong. So, I read up a little bit more on this and it said that I had to do a factory restore beforehand so I did it with high hopes that it would work. However, it sill did not work. What happens is that I power it on, it asks whether I want to go into SafeStrap or not, it continues if I say no, and they it starts with SlimKat. After about 20 seconds, it stops the starting animation and starts its boot loop.
Since I factory restore it, I had no back ups or and ROMs that I could install on my device. I try to plug it into my computer but it is unrecognizable even if it is the recovery. I also tried going into download mode, doing it multiple ways, but with not luck. It still goes into the boot loop. I factory reset it multiple times but still with no luck. Within SafeStrap, I tried to wipe it, but it is unable to wipe the Dalvik Cache or Data. If there is any way that I can move the stock ROM onto my phone, it would solve all my problems. If any of you have any ideas, please let me know.
I having same problem. Unable to go to recovery mode in normal way, but I could managed to go to recovery by attaching it to computer with usb cable and keeping pressing power + Vol up key for few seconds.
Then I tried Factory restore, Adb Sideload original file downloaded from amazon, but the problem still not solved.
My phone is keep flashing amazon logo in loop.
If any one have idea please help.
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english