I turned off my phone (vzw galaxy nexus) today to replace the battery and it wouldn't boot back up. It was stuck on the Google screen. I've tried almost everything i could think of. I was running AOKP jb build 4 at the time with imo's lean kernel. I've tried doing restores and installing fresh aokp b4 and ics milestone 6 ROMs. The ics rom/restore goes into boot loop and any jb rom/restore gets stuck at Google.
A few odd things i did notice was that the first time i tried to wipe dalvik cache, cwm recovery was frozen for a few minutes and i had to battery pull but after that it was able to wipe it quickly. Another thing is when i restore my backups, there is a error in restoring /data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone know any fixes? I haven't tried installing a stock image yet since I'm not home but the situation doesn't look good.
Sent from my SCH-I535 using Tapatalk 2
How long did you let it sit at the Google screen? If an 'improper shutdown' is detected (no idea what constitutes improper), the JB boot loader does a full scan of the file structure to make sure everything is intact. I've had it take several minutes now and then, and others have reported longer before the Nexus animation begins.
Sent from my Galaxy Nexus using xda premium
I let it sit for a couple of minutes, but oh well i fixed it by flashing a stock Google image. Thanks for the suggestion though.
Sent from my SCH-I535 using Tapatalk 2
Impossible to brick Nexus,always there is a way to revive your phone .
youll have to flash factory image via fastboot to get it to work again
you can pull your sdcard data in recovery to your pc because after flashing via fastboot youll lose all your data even the sdcard data
Related
When i go to restire a backup it runs for 4 seconds and says successful...but no backup is actually restored anf if i reboot ill get black screen due to lack of rom...
how can i restore a backup?
Sent from my GT-N7000 using Tapatalk 2
Look in your backup folder...what files do you see?
Here is what I see... in twrp/0000000000
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from a kindle fire on cm 9
Hmm. That should restore. Have you tried reinstalling TWRP or changing versions?
How do I change versions without use of a computer?
sent from a kindle fire on cm 9
Here's one way
http://forum.xda-developers.com/showpost.php?p=22608974
Is there a way to make a zip or something of the recovery files to flasg? I don't really want touse smirkit
Sent from my GT-N7000 using Tapatalk 2
Is there a reason you don't want to use smirkit?
I am constantly flashing roms... Isnt it true that smirkit goes away after i flash a new rim? Will i still get to keep the updated twrp? Thanks for your help
Sent from my GT-N7000 using Tapatalk 2
asf58967 said:
I am constantly flashing roms... Isnt it true that smirkit goes away after i flash a new rim? Will i still get to keep the updated twrp? Thanks for your help
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes and yes. Smirkis has significantly updated his script since the last time I used it. It used to be a set of scripts to be run individually to install whatever image or binary you needed. Now, you flash the smirkit.zip installer in recovery along with any files it comes with. This makes it much easier to launch and less likely to encounter any errors, but the overall result of running the script is still the same. The image or binary gets flashed to its respective partition, to stay.
Since the smirkit.zip is flashed to the system partition in recovery, flashing a new ROM, simply overwrites the system partition along with the Smirkit installer.
So yes, you can use Smirkit and not worry about losing TRWP after rebooting or flashing a new ROM.
Smirk it saved the day. Thank you so much for your help
sent from a kindle fire on cm 9
okay, i searched, i swear i did - i just need a little help, my wife's phone updated to Jelly Bean OTA the other day, and she was playing with mine and saw i was running Codename Android 3.5.0 - she loved the added profiles in settings and wanted me to throw the rom onto her phone, so i did.
now i never had any problem with mine, but hers started up, went through the Google restoration prompts, and then went through the Sprint profile activation as always when you activate a new phone/new rom, except hers said it failed to update the profile.
i'm not as familiar as i'd like to be with PRLs and profile activation and date profiles, so i just went into settings>about phone>Sprint system updates and tried to get it to update the profile, multiple times in fact, but to no avail - it keeps saying it failed on her phone.
i tried mine and it works flawlessly, same set up, same phone, same rom - i took all the same steps to update hers as i did mine and i don't get it.
any ideas?
Wipe cache and dalvik in recovery and fix permissions. Then make sure you have a network connection and update profile. Then power off for 2 minutes when you turn it back on all should be well. This happens to me all the time.
Sent From My N7 via White Tapatalk
ÜBER™ said:
Wipe cache and dalvik in recovery and fix permissions. Then make sure you have a network connection and update profile. Then power off for 2 minutes when you turn it back on all should be well. This happens to me all the time.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
thanks for the reply!
i tried this out, twice, and it didn't work - so i decided to reflash the new radios (FH05 zip) i found on here through clockwork, and BAM! - worked immediately upon reboot of the phone.
seriously thanks for the help though.
I am experiencing this problem too, except a radio re-flash did not work. I'm gonna upload what i'm seeing. I can't send or receive MMS, but data still works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jxr94 said:
View attachment 1342567
Click to expand...
Click to collapse
did you ever figure this out?
i haven't had a problem with my phone or my wife's since i reflashed the radios...
I'm not specifically sure where I would put this thread, but is a tutorial on how to upgrade your GS3 to a leaked JB official rom
(Bell).
Note* External SD Card may be required, was the only way I could get it to work.
*Forgot to mention this removes root, so you will need to root again if you don't like this leak
Firstly, follow these instructions on using odin to flash to the latest firmware. All downloads provided in link. http://www.theandroidsoul.com/mvlalh1/
It is pretty straightforward and similar to other rooting methods. If you have a kernel installed do not worry, this firmware will overwrite it and restore all stock drivers etc.
**If you get stuck on a boot loop or the boot screen take out the battery and reboot recovery and wipe data/factory reset.**
Next you want to download the OTA leak here http://www.hotfile.com/dl/171511232/8603d3c/SGH-I747M_I747MVLALI-OTA-I747MVLALH_BMC_325174257.zip.html.
After download, place onto your External SD Card (can also try internal but did not seem to work for me).
Now go onto your phone and power it off.
Reboot into recovery (Volume Up+Home+Power. Hold all till Vibrate, then quickly release and hold again. You will see samsung logo with "recovery" in top left but its small)
Now you want to Apply Update from location of the OTA leak (cache did not work for me).
Reboot.
You should now be enjoying TouchWiz with Google Now and JB awesomeness!! Lemme know if you have any issues. Thank me if I helped you out pal!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BUGS**
Only noticed bug so far is a blue screen flickering from accessing the task manager quickly. Random, and nothing to worry about. Overall very stable.
Google+ is preinstalled, and runs in background and chews battery. Disable it. If you use it then you have to deal with the battery life.
Is this a new leak
Sent from my SGH-I747M using xda app-developers app
I'm pretty sure its the leak from around September. I'm not quite sure how new but it works well. I had problems finding the leak so I thought it would be easier for some people if I post the link here.
Sent from my SGH-I747M using xda app-developers app
actually i am using "" Xperia S Boot Manager v0.8, a real dual boot system"" since from more than month.
every thing was perfect . i have android kitkat as native rom and xperia s stock jelly bean as my loop version.
i had backup my rom on TWRP for loop when every thing was perfect. last night i had modified the some system app app replacing them with custom. so system goes in boot loop for loop version. now whenever i restore the system my system starts and restore it correctly.
but here comes the problem after restoring whenever i reboot my system without any modification it again goes in boot loop.
then i wipe data,dalvik,cache and reboot again same problem. i dont want to loose my data help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
whenever i am trying to re install my rom its showing Unable to mount system,data,cache.
help me
you have to format all the system data and cache before installing a rom
Sent from my LT26i using XDA Premium 4 mobile app
not working
Envious_Data said:
you have to format all the system data and cache before installing a rom
Sent from my LT26i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have already tried every thing but at last i have deleted the loop partation created new and reinstalled every thing .
SMARTHACKER67 said:
i have already tried every thing but at last i have deleted the loop partation created new and reinstalled every thing .
Click to expand...
Click to collapse
weird
usualy formatting before installing fixes the mounting issues after rebooting the bootmanager.
(in the loop recovery by the way)
Sent from my Xperia S using XDA Premium 4 mobile app
about sometime after i updated via OTA to get 5.0.2 on my Google Nexus 7 (2013) it's been acting weirdly with random reboots or having trouble turning on or when i finally starts it, i can see Android Logo and then reboot, i can battle with it for sometime then it starts and runs fine but then i can get random reboots surfing, gaming or just going through my app drawer i use total stock unmodded Android 5.0.2 and i got about 8,87 gb storage left on it.
Yesterday when i tried to install Summoners War from the play store it just rebooted in downloading it's files, then i started it up again it finished, then i opened the game trying to find a username and then reboot again
I tried to delete davik and cache from recovery it took away a little of the random reboots but not everything, so anyone got an idea of what i can do to fix this problem? To be honest my tablet is on all the time running with power saving mode on even it's not in use, and battery is fine so i can't see why it has to reboot, do i need to reflash the lollipop factory img or anything i can try to do?
Summoners War
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link: https://play.google.com/store/apps/...smon.normal.freefull.google.kr.android.common
Possibly the ota. Try a clean flash from the image.
I just finished my own uptime test, hit over 1000 hours. 5.0.2 is very stable. Either it's the ota, some app you have installed or (unlikely) a hardware problem.
Try flashing system.img and boot.img to see if that fixes the issue. If not, use fastboot to wipe everything then flash the 5.0.2 factory image.
Oki looks like i was able to boot my nexus 7 into android and allow my pc to have access to it, adb reboot, and then fastboot oem unlock and fastboot flash boot boot.img and then fastboot flash system system.img from razor-lrx22g-factory-bff2093e.tgz and after it was done i used adb reboot, I saw the android figure so i guess it was updating something and then rebooted now i see startup animation, so hopefully it will start and i don't have do a full wipe (crossfingers)
hmm it booted and but under setting up my Nexus 7 bam it just turned off
Oki i have fixed this, i reflashed Android 5.0.1 factory image from Google to myy Nexus 7 (2013) and it works no more random turn offs or startup trouble, i guess not every device likes update for 5.0.2