Related
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...
Hi, I've managed to use Odin to install the bell with root image, phone now working with I747MVLUEMK5..downloaded clockworkmod recovery manager and used the att recovery image. Downloaded custom Roms, factory reset the phone, wiped cache and dalvik then installed the custom ROM. It installed properly but when I reboot, it won't turn on, I have to do the download mode to recover it back using the Odin. Tried different custom ROM and I made sure they are for this image MVLUEMK5... But same result, it won't boot up... Help...did I miss a step?
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
audit13 said:
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
Click to expand...
Click to collapse
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Too much work for me. There is no need to have root before installing a custom ROM.
Do this:
Use Odin to install Philz Touch Recovery from here (use the tar version in PDA, do not check auto reboot): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Once it flashes and you see Reset in the windows, pull the battery, disconnect the phone from computer, boot into recovery, wipe cache, dalvik, system, data, flash rom, reboot.
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
snyph3r said:
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
Click to expand...
Click to collapse
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
audit13 said:
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
Click to expand...
Click to collapse
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Most of the 4.3 roms take a long time at the first boot once you flash it (when I flashed S3Rx it took 3 minutes 32 seconds, I timed it because most people say I waited a long time but have no recollection of how much time) it will stay at one of the boot image screens for several minutes then it should vibrate once the blue led should illuminate and then it will finish booting.
If the wait is too much for you turn it on, set it down, walk away, find something to do, 10 minutes later come back, if it hasn't booted now make sure you followed all the instructions correctly and flashed the right stuff for the phone model you have.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
To make sure we are on the same page, is it just stuck at a boot screen or is it getting to a screen turning off and going back to the same screen repeatedly?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Try a different ROM. I use validus and it installed without a problem.
audit13 said:
Try a different ROM. I use validus and it installed without a problem.
Click to expand...
Click to collapse
I was able to flash Validus and And Candykat but could not flash Omni and Beanstalk....flashes with no error but just wont boot up...
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
snyph3r said:
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
Click to expand...
Click to collapse
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
audit13 said:
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
Click to expand...
Click to collapse
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
snyph3r said:
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
Click to expand...
Click to collapse
That is strange. I run validus on mine and WiFi is fine. Calls and data ate fine as well.
snyph3r said:
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Click to expand...
Click to collapse
Just curious... are you going into mounts and storage to format system along with the factory reset and dalvik / cache wipes ??
Guys I have a big problem!
For about a month I have on the galaxy nexus rom slimkat + kernel dfk and until tonight I had not any problems, until this evening the phone has rebooted and the disaster happened, the boot animation was jerky and the phone has put more than 5 minutes to power, however going slow, and even after I have booted the phone is super slow, it's all jerky and unusable.
From recovery I tried to wipe system, but even if the message confirming correct operation, it really does not matter because if I reboot the phone loads the system, even if ever so slow and jerky.
I also tried to use the Nexus root toolkit but nothing, when I try to reflash stock hangs the command "writing system" and does not go forward ... I do not know what else to try.
I also tried using fastboot commands, but nothing changes ... not the operations are successful and the changes are not applied.
Please help me! Thank you very much!
Wipe system, cache, data, dalvik cache and internal.. Then flash stock factory image and then install roms
Wipe from recovery do not work.
I tried to flash from toolkit the stock factory image, but hangs on the command "writing system".
There is another way to flash it??
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
h4xx0rr said:
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
Click to expand...
Click to collapse
I've tried, the procedure seems to be successful but the recovery does not really change.
I also tried to flash the stock rom with odin, well after the half-hour procedure is successful, the phone has rebooted but nothing, everything remained as before, with the old rom.
I do not know what to think anymore, I try recovery, toolkit, fastboot and odin but nothing.
I came to doubt that it may be a hardware problem with the internal memory of the phone, do not you?
Thank you!
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
h4xx0rr said:
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
Click to expand...
Click to collapse
I boot into temporary recovery and i do successfuly all wipe, but when I restarted the system, nothing has changed, loaded the old rom
I do not know what to do!
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
h4xx0rr said:
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
Click to expand...
Click to collapse
Thanks ... I think like you!
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?
It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.
k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.
sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.
Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app
The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.
Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.
redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.
I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.
I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)
32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?
Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone
Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium
dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk
Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk
Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.
maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.