Related
Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
visar.r said:
Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
Click to expand...
Click to collapse
Don't panic, this problem is called bootloop and it's normal. Just download factory images from here and flash them by using this awesome guide by efrant!!
Also bookmark this link for future reference.
http://forum.xda-developers.com/showthread.php?t=1812959
started having the same problem yesterday after 6 months of stability on a custom 4.3 rom.
oem lock then unlock to format, nothing, tried various methods of flashing back to stock via ADB with mixed results, normally more boot looping with it occasionally booting into a rom for ~5 seconds. so SOMETHING is working.
I tried Efrant's method about an hour ago, but its been sitting at the google logo since, I'm at a lost, I'm no stranger to boot loops when installing borked roms but this is the strangest problem I have ever had with an android device.
should I just chock it up to hardware failure?
Mostly yours USERDATA partition is corrupted.
Use FASTBOOT to reflash the USERDATA IMG and it should do the trick.
Sent from my Galaxy Nexus using xda app-developers app
did a total stock reflash again, got to the setup screen before it rebooted after ~15 seconds, bootlooping again. flashed the userdata img with a few different ones.
I'm trying to read my logcat but when I run the ADB command in clockwork It finds nothing.
I've done all steps by this awesome guide by efrant! But same problem here
I've tried to install 4.2.2 stock, 4.3 stock, all comands works but in the end when i press fastboot reboot my nexus it's in bootloop again restart restart and restart
Any other solutions :crying::crying::crying:
I've waited about 30 minutes after restarting non-stop, my GN boot to system i saw home screen of android but after 5 sec restarted again :crying:
I'm getting into my system once every 10 or so reboots. managed to turn off wifi in case that was the problem but still boot looping. I'm inclined to think it might be hardware related as I started having trouble in the middle of a text after several months of rom stability.
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option
Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"
supersaayuj said:
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option
Click to expand...
Click to collapse
thanks for quick reply.
Tried Wug's kit (latest version since it auto update), and tried with command line using fastboot drivers (win7 environment)
Same result
Wug's kit logging shows no problems.
BoredAtWork said:
Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"
Click to expand...
Click to collapse
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works
supersaayuj said:
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works
Click to expand...
Click to collapse
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.
BoredAtWork said:
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=orZ_iBpkn_g
Get a look at this video... I can't further help... because this is a weird problem I haven't faced with my nexus 7. Mostly flashing stock would solve this kinda problem! :angel:
Reply back if you unbricked it!
Same problem here
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?
Is there anyone can help?
micheldjerzinski said:
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?
Click to expand...
Click to collapse
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...
BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
I was experiencing this problem last night. However, I used WugFresh's NRT but when it asks to flash stock and unroot, make sure you check the box that says your nexus 7 is softbricked. Also, you may want to note what version of android it was last running before it was bricked. It worked for me and I was able to update to 5.0.1.
*Edit: The only thing you need to do is make sure fastboot is enabled, and you should be good to go.
P.S. DO NOT download the stock images from google to your computer, let the NRT automatically download it for you. It saves you time, storage and stress. Once done, also install the recovery from the NRT, that should be able to do the trick. Not sure why your device won't restart, you may have to flash again.
wugs
I had to use force flash in wugs, go to options and set it there and try a previous version. Best of luck.
It's fixed!
koymoy said:
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...
Click to expand...
Click to collapse
Haha, I found the solution elsewhere in XDA. So if you haven't beaten your Nexus 7 so bad yet, TRY this: press and hold the power button for about 1 minutes. The slate turned off and on several times, and I found nothing. BUT after several minutes (while I was watching Youtube to see how to remove battery; that would be the last method before throwing 5 stories down to ground), the Nexus BOOTED BACK:good::good::good:. Good luck!:laugh:
And I'm using Glitch kernel and turn off flar2's double-tab-to-wake. It's a neat feature, but can get us into big troubles.
That still doesn't work for me. Pretty sure my eMMC is dead, so I'll need to replace the motherboard.
Anyone know if a 16GB motherboard works in a 32GB Nexus 7 2013? 16GB motherboards seem a fair bit cheaper, and less rare.
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
8.0.0 rooting nightmare
gaw54 said:
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
Click to expand...
Click to collapse
I have the same exact issue after following the exact process described above. After a weekend of frustration, I was thrilled to see this post, but then bummed there are no suggestions. There is no way I can get it back to recovery, no matter what power/volume combination I try. The phone is not detectable by ADB either, so unless a kind soul has a suggestion, there seems to be nothing to do except let the battery die and hope.
Umm boot into bootloader and flash stock boot.img and system.img?
george241312 said:
Umm boot into bootloader and flash stock boot.img and system.img?
Click to expand...
Click to collapse
I would love to do that, but how is it possible if there is no power or volume button combination that can get me off of the Google boot screen and into bootloader?
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
george241312 said:
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
Click to expand...
Click to collapse
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
edjanx said:
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
Click to expand...
Click to collapse
That did the trick. Back to stock 8.0.0, and hoping to find a stable root method that doesn't hang-up on the first reboot. Thanks for the help!
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
mikaole said:
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
Click to expand...
Click to collapse
OK, thank you! I am not familiar with the -w method. This is a new Pixel XL I received from Google to replace a nexus 6p with a bootloader issue. I made the mistake of not attempting this before it updated from 7.1.2 to 8.0.0, or it may have been a different story.
So I have the the phone restored to 8.0.0 and was going to attempt root. But I didn't realize there are two slots to flash. I simply ran flash-all.bat and the phone came back up. So I guess I'd have to move the Sept security stock image over to the phone along with the SU, SU Config (which may not be needed if on 8.0.0?), and Su Hide. Then I boot up TWRP 3.1.1 and flash stock image to both slots, reboot, then get back into TWRP and run the SU, then SU Hide on *both* slots?
Thanks!
Janx
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
fastboot --set-active=_b
fasboot reboot bootloader
Now you should be on the other slot
Flashall.bat
Reboot to system
Back to bootloader
fastboot boot twrp.img (latest)
In twrp put latest su or in my case magisk 14.2, twrp zip on device.
If you use su just flash it
If you use magisk. Flash magisk, flash twrp.zip and magisk again. With magisk twrp will stick.
Reboot and you are good to go.
If you want a kernel you have to flash twrp and magisk after again.
mikaole said:
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
<SNIP>
If you want a kernel you have to flash twrp and magisk after again.
Click to expand...
Click to collapse
Thank you! I will be able to perform this sequence in a few hours and will report back. :good:
Ok. Will be in bed than. If you have any problems give me a PM and we can do it together via hangouts.
Update: I successfully flashed A & B, got to the step where I flash Magisk 14.2. It finished unmounting partitions, but when updating partition details fails, "failed to mount '/system' (device or resource busy)...done
It said successfully installed, so I flashed twrp to the boot image, flashed magisk again, and it is now rebooting endlessly. Wrong place to flash the twrp image I'm guessing?
EDIT: Just noticed your message, good night - thanks again. I'm working through it and will take you up on your kind offer should I not find success.
I did a 'flash-all.sh' on both A and B again, copying over my old phone, then will attempt to gain root by booting into TWRP 3.1.1, installing "SR3-SuperSU-v2.82-SR3-20170813133244", reboot bootloader, go into TWRP again and then install "UPDATE-suhide-v1.08-20170815171034"
EDIT #2: EDIT #2: Stable root achieved using newer versions of files "SR5-SuperSU-v2.82-SR5-20171001224502" & after booting, applying "UPDATE-suhide-v1.09-20171001222116". So far it has survived several reboots, so I'm hoping it's all good now.
Okay, so, I followed the guide to root my device. And everything went smoothly, until the new version of Android (8.0.0) was released for the phone and I made the mistake of trying to install it using the stock installer rather than through TWRP. Of course, it failed and I ended up doing the installation manually. Now, whenever I try to reboot my phone, it boots straight into recovery (which gives me the "No Command" error because TWRP is inexplicably missing). If I load up Bootloader (Volume Down + Power) and select START, then the phone boots like it should and I can use it just fine.
I've tried wiping the data through TWRP (After flashing it to recovery for the umpteenth time) thinking that would help, but no. It still boots directly into recovery. The command "fastboot oem fb_mode_clear" using minimal ADB and fastboot doesn't work either. Any help would be appreciated. I have no idea what else to do.
try to plugin charge cable and reboot again.
Nope. Still boots to recovery.
Hi, did you ever manage to solve this? I have the exact same problem.
Fiksdal said:
Hi, did you ever manage to solve this? I have the exact same problem.
Click to expand...
Click to collapse
try to boot to bootloader, and then use the option start
So I loaded Lineage OS 19.1 just fine, but it caused a few issues so I decided I'd flash it back to a global stock ROM.
My first step after factory resetting the phone was going into the bootloader and wiping user data. Now I just get the boot screen and restarts when it usually would go past it.
The phone is not responding to any button press combinations as well as not loading into the bootloader when a usb is inserted while the volume down button is being help in the brief off time between restarts.
Am I stuck, do I just need to put a new motherboard in the phone? Should I not have wiped user data from the bootloader, and instead used the recovery to do so?
I do have another motherboard from a working parts phone except its Google locked, but I've heard and seen that there are ways around that.
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
SurvivalHorror said:
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
Click to expand...
Click to collapse
Well I did. But now it won't accept inputs. I've already swapped the motherboard. It works, but I decided to go back to Lineage AGAIN, as the stock ROM is has WAY too many issues, and now it has a similar issue after sideloading the zip from lineage. Although the recovery partition booted just fine after I flashed it with the lineage recovery img.