Hello guys,
So basically my phone shut down while I was using the app drawer. And it got into a boot loop. The phone is rooted, and it has Lean Kernel and Paranoid Android 3.6 installed on it. It tried to factory reset, wipe data, wipe cache, basically do everything in the recovery mode, but it still wouldn't boot. So then I formatted the sd card, and everything else there was to format. And now the phone is just stuck on the word Google. I understand (guess) that's because I've formatted the internal memory. How do I get to flash a rom to the phone now? The computer can't seem to get a connection via USB while the phone is stuck on the word Google. Thanks for your help
Isstatu1 said:
Hello guys,
So basically my phone shut down while I was using the app drawer. And it got into a boot loop. The phone is rooted, and it has Lean Kernel and Paranoid Android 3.6 installed on it. It tried to factory reset, wipe data, wipe cache, basically do everything in the recovery mode, but it still wouldn't boot. So then I formatted the sd card, and everything else there was to format. And now the phone is just stuck on the word Google. I understand (guess) that's because I've formatted the internal memory. How do I get to flash a rom to the phone now? The computer can't seem to get a connection via USB while the phone is stuck on the word Google. Thanks for your help
Click to expand...
Click to collapse
Just ran in to the exact same problem on my girlfriend's phone. Please help. It turns on and I can get into bootloader mode and recovery but when I go to reboot, it just stays on Google startup screen. I did the same things, formatting and such. The sd card is empty with nothing to flash. Help!
Ok, so I've managed to flash another rom. But it only shows me the boot animation and back to the Google logo...
Isstatu1 said:
Ok, so I've managed to flash another rom. But it only shows me the boot animation and back to the Google logo...
Click to expand...
Click to collapse
Flash the stock kernel from The Rom package.
It will boot up.
Sent from my LT26i using xda premium
ADDICT.ANK said:
Flash the stock kernel from The Rom package.
It will boot up.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I tried installing this kernel and this rom. But it still doesn't boot up. It seems that the kernel is installed on the phone, but the rom isn't, because the command line on the phone doesn't actually write Done or anything else, it just sits there for a while doing nothing.
why dont you flash back to stock using fastboot?
Been there and the "Nexus Root Toolkit" by WugFresh really came in handy. Used the software to go back to stock and since then no problem
Isstatu1 said:
I tried installing this kernel and this rom. But it still doesn't boot up. It seems that the kernel is installed on the phone, but the rom isn't, because the command line on the phone doesn't actually write Done or anything else, it just sits there for a while doing nothing.
Click to expand...
Click to collapse
Via fastboot flash the recovery first and restore from there
and then see..
it should boot up..
or
just flash a stock rom too then.
check the link for stock kernel
http://forum.xda-developers.com/showthread.php?p=44521651
and post here
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Isstatu1 said:
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Click to expand...
Click to collapse
Well that is a progress
Try to update the recovery using Nexus Root Toolkit. Push the stock ROM using the advanced option and then flash the stock again using recovery. Wipe cache and dalvik cache then reboot.
Isstatu1 said:
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Click to expand...
Click to collapse
try to lock your bootloader. if its still unlocked after you reboot your phone, your emmc chip is fried.
Having the bootloop. I've tried the Universal Nexus Tool for Linux and get no boot SIG and recovery SIG error.
I can't get it to boot at all. :/
Sent from my Nexus 7 using xda app-developers app
Zepius said:
try to lock your bootloader. if its still unlocked after you reboot your phone, your emmc chip is fried.
Click to expand...
Click to collapse
I locked it with "fastboot oem lock" and after taking out the battery it says that the bootloader is locked. So I guess the emmc chip is fine?
By the way, is emmc memory related in anyway to the Lagfix(fstrim) app that I've got from Google Play to speed up my Nexus? Maybe the problem is somewhere there?
Also, If I'd locked the bootloader and took it to the Sprint store, would they try to fix it even though I had the phone for more than a year?
I've tried everything and still a bootloop. No matter if I recover to stock or flash a custom ROM.
Sent from my Nexus 7 using xda app-developers app
Fixed the problem by buying a Nexus 5...
Related
Hi everybody ,
I have a rooted Desire HD with Jelly Time R10 and it was working like charm.
Yesterday the phone rebooted by itself and got stuck at the boot animation
I tried to wipe cache + dalvik and I was able to pass the boot animation and then got stuck again while loading application.
I pulled out the battery then started the phone but it WONT boot. It vibrates 3 times with orange flash and when trying to boot into bootloader it vibrates 5 times with a solid green led
Then I used ADB and I was able to access the recovery but not the bootloader or the system, if I used adb reboot I get the same issue.
I performed a full wipe then restored a backup nothing changed.
Any ideas please ? Is it the bootloader causing this problem ?
What can I do to fix this?
hussamite said:
Hi everybody ,
I have a rooted Desire HD with Jelly Time R10 and it was working like charm.
Yesterday the phone rebooted by itself and got stuck at the boot animation
I tried to wipe cache + dalvik and I was able to pass the boot animation and then got stuck again while loading application.
I pulled out the battery then started the phone but it WONT boot. It vibrates 3 times with orange flash and when trying to boot into bootloader it vibrates 5 times with a solid green led
Then I used ADB and I was able to access the recovery but not the bootloader or the system, if I used adb reboot I get the same issue.
I performed a full wipe then restored a backup nothing changed.
Any ideas please ? Is it the bootloader causing this problem ?
What can I do to fix this?
Click to expand...
Click to collapse
That seems to be a fried emmc chip. Try flashing an stock ruu in fastboot If you manage to boot in hboot. Of if you are not able to access hboot you are done
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
glevitan said:
That seems to be a fried emmc chip. Try flashing an stock ruu in fastboot If you manage to boot in hboot. Of if you are not able to access hboot you are done
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
thanks for your reply
but when I check connected devices to fastboot it return nothing so I cant flash a stock ruu using fastboot
I tried to flash a new jelly time rom from the recovery but the phone got stuck while flashing
hussamite said:
thanks for your reply
but when I check connected devices to fastboot it return nothing so I cant flash a stock ruu using fastboot
I tried to flash a new jelly time rom from the recovery but the phone got stuck while flashing
Click to expand...
Click to collapse
I'm pretty sure you can at least try to get the RUU to recognise the phone, as adb recognized it, so it should be able to kick it into fastboot mode
Sent from my Desire HD using Tapatalk 4 Beta
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Enpo said:
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Click to expand...
Click to collapse
Are you flashing correct kernel check that first.
sent from HOV
powered by sphongle 4.2.2
Hmm... I'm pretty sure that I flashed right kernel, but now I can't get to fasboot screen. Only to ClockWork mod recovery. When I boot device, and press vol. down, and power, it always goes to recovery, or if I start to press those buttons a bit later, it only goes to that white HTC screen with red text. =(
E: After a while phone turns screen off, vibrates, and makes the screen again, so some kind of boot loop i guess?
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
mr_nooby said:
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Enpo said:
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Click to expand...
Click to collapse
flash this boot img as the one which comes with sphongle rom doesnt boot
http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img :good: :highfive:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Enpo said:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Click to expand...
Click to collapse
haha no problem!
I wish 1ce would post the correct kernel for his ROM
wud save a lot of questions
My phone is a HTC ONE X, I recently unclocked it bootloader, then rooted the phone using CLOCLWORKMOD 5.8.3.1 recovery.
I downloaded a CYANOGENMOD 11 NIGHTLY (which maybe runs on 4.4.4 kikkat as i saw) , when i went to my phone's recovery mode, i actually wiped my phone's data and wiped my cache and dalvik cache everything, the problem is that when i installed my CYANOGENMOD my phone is constantly giving status 7 error. I cannot even use the mount usb system from my CLOCKWORKMOD recovery because I get the ''cannot open ums lunfile'' bla bla error. Thus I soft bricked my phone i guess because i can only get my phone booted to the recovery mode only and the phone stucks in the HTC QUIELTY BRILLIANT logo and then boots back to recovery, it happened yesterday and i have searched everything but couldnt figure out what to do.
Please help what should i do to get my phone to normal?
asibmkhan said:
My phone is a HTC ONE X, I recently unclocked it bootloader, then rooted the phone using CLOCLWORKMOD 5.8.3.1 recovery.
I downloaded a CYANOGENMOD 11 NIGHTLY (which maybe runs on 4.4.4 kikkat as i saw) , when i went to my phone's recovery mode, i actually wiped my phone's data and wiped my cache and dalvik cache everything, the problem is that when i installed my CYANOGENMOD my phone is constantly giving status 7 error. I cannot even use the mount usb system from my CLOCKWORKMOD recovery because I get the ''cannot open ums lunfile'' bla bla error. Thus I soft bricked my phone i guess because i can only get my phone booted to the recovery mode only and the phone stucks in the HTC QUIELTY BRILLIANT logo and then boots back to recovery, it happened yesterday and i have searched everything but couldnt figure out what to do.
Please help what should i do to get my phone to normal?
Click to expand...
Click to collapse
Upgrade recovery.
Tap via Tapatalk
but how? i cant use mount usb... how do i upgrade recovery????
asibmkhan said:
but how? i cant use mount usb... how do i upgrade recovery????
Click to expand...
Click to collapse
Find recovery kitkat based and flash it via fastboot.
Tap via Tapatalk
u mean to say download a latest clockworkmod recovery? then how do i flash it via fastboot if i cant get it in my phone storage?
Please help
Flashed a new recovery and VOILA IT WORKED!!!!!!!!!!! CYANOGENMOD INSTALLED, bt now stuck on the screen where the cyanogenmod animation looping is happening, for how long does it happen?
asibmkhan said:
Flashed a new recovery and VOILA IT WORKED!!!!!!!!!!! CYANOGENMOD INSTALLED, bt now stuck on the screen where the cyanogenmod animation looping is happening, for how long does it happen?
Click to expand...
Click to collapse
flash the boot.img from the rom, even if you have already done it, via fastboot command "fastboot flash boot boot.img" then "fastboot erase cache" and then try the rom again, and to answer your question, I have waited sometimes only a couple of minutes up to about 15 mins for some roms to boot
asibmkhan said:
Flashed a new recovery and VOILA IT WORKED!!!!!!!!!!! CYANOGENMOD INSTALLED, bt now stuck on the screen where the cyanogenmod animation looping is happening, for how long does it happen?
Click to expand...
Click to collapse
Sorry for late reply,lot works to do but hey! you managed to do it.about that problem you need flash boot.img inside that rom.
Use @nogotaclue way to flash it.
Tap via Tapatalk
yes yes!! It worked i did used cmd and flashed boot.img
now using the CM11 mod nightly, loving it thanks a lot guys for the help!!!
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time
Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.
iananderson said:
Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.
Click to expand...
Click to collapse
Thank you. Still no success :/
BLEXXAR said:
My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time
Click to expand...
Click to collapse
Never factory restore when you have a Custom ROM as it isn't made to reset with the devices stock hardware and causes things to go crazy.
Always use a nandroid of the original system with root, then unroot, then factory restore from that.
Also. YouTube search - HTC Desire 816 root unlock bootloader.
Use the .exe recovery from that video in fastboot at least twice without exiting fastboot or rebooting.
Now try the recovery.
Sent from my 710C using XDA Free mobile app
Didn't work. Thanks though.
BLEXXAR said:
Didn't work. Thanks though.
Click to expand...
Click to collapse
When you were on the stock recovery, could you wipe partitions?
Also what model do you have?