Earlier today, my NS4G (running CM10 nightlies) rebooted itself (as it has been doing a good bit recently). I didn't think anything of it until it would not make it past the Google logo. I rebooted into CWM, and CWM could not read the sdcard. I tried this a few times, just to be sure. I even re-flashed CWM - still no sdcard access.
After this, I grabbed the factory images from Google (https://developers.google.com/android/nexus/images#sojus) and flashed them. Again, no dice. I can get into fastboot and recovery, but not even the factory ROM will boot (still stuck at the Google logo).
Is there anything I have missed? Is there any way to confirm whether or not my internal storage is dead via fastboot?
Any help is much appreciated - thanks!
Related
My friend has a Captivate. He lost all his google apps, android market, gmail, etc. He flashed gapps.zip from his recovery and now his phone is not working right. When he flashed a new rom to his phone, and it brought up the welcome screen it shows it for about 2 seconds and then reboots. He is also almost unable to access the recovery becuase of this, but even when he finally was able to access it and wipe everything, dalvik, cache, data/system, it still has issues. Nothing is fixing the issues from the gapps.zip. He was wondering if there is a way to wipe his entire phone from a update.zip file. Any help would be appreciated. Thank you in advance.
Please note that even when he wipes everything in recovery and flashes a new ROM, it still reboot on the welcome screen and he is unable to resolve this issue.
Ok, so he has now wiped all cache and system files, now instead of showing teh galaxy S logo with the cyanogen logo underneath, it shows just the AT&T screen, but it will not go any furhter, it just sits there. He says that because he is now unable toget into android he cannot access the recovery and the volume up/down is not responding. Is his phone Bricked?
Have you used Odin 1-click to revert back to stock?
had my friend use the Odin 1 click and he said it still did not work. He cannot get the volume up/down trick to work, when before all this it worked just fine. I am going to guess that the only thing he could try is the jig method. He swaers that Odin3 is not doing anything
Hi,
I have a Nexus S I9020T, rooted and running MIUI.
Today I rebooted my phone (after applying a new font via Font Changer), and it got stuck at the Google logo.
I have tried rebooting via fastboot, to no avail. I have also tried pulling the battery several times. I have even tried doing a full wipe and restoring a Nandroid backup that I made via ClockworkMod after it got stuck, but it still refuses to go past the Google logo.
Can anyone please suggest something? Thanks so much.
Edit: I forgot to mention that the device was plugged into the computer at the time, and I am not sure whether or not the SD was mounted. Could this be the cause?
If SD isn't mounting you wont get past the Google logo. See if it is mounted in recovery
Sent from my Nexus S 4G using xda premium
I bet if you reflash the original miui rom you were on you'll be good to go. Sounds like the font package messed up the miui system. Good luck.
And no need to wipe most likely. I've bootlooped my miui applying themes and such and just reflashed with no wipe and good to go.
Sent from my Nexus S 4G using Tapatalk
The the device came in today and when I turn it on The Google logo comes, turns off and restarts for a boot loop. I even did a full restore using the recovery toolkit like swoggers and even then no luck. I was able to install twrp with no issue. Anyone have the same issue ?
Thanks
Anyone?
saadkhan07 said:
Anyone?
Click to expand...
Click to collapse
I had problems AFTER I installed TWRP, but before that it booted just fine.
My problems started after unlocking the bootloader and installing TWRP. Try wiping as much as possible (except System) with TWRP. I read somewhere it's a problem with the cache partition. I also went into "Mount" in TWRP (I think that's what it's called) and mounted System. I'm telling you all this from memory, not sure exactly how I fixed it, but eventually I was able to turn the phone on.
Hopefully this is the reason you're having problems. It'd be frustrating to have to try and get another one from the Goog.
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?
Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.
I don't have any SD card in my tablet though, thanks anyways.
Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk
Tried doing a format of system as well as data/cache/dalvik, still getting same result :/
Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk
When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.
any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works