a few times now over the months with my nexus 7 (2012) i have tried to convert to fsf2 with twrp manually and always seem to get stuck on the google screen for over 5 - 10 minutes, only once from my first try after simulating a battery pull (holding all the buttons down) I got past the google screen in normal quick time, but after trying my first reboot i got stuck on the google screen again. How long is the google screen at most supposed to be on the screen for before launiching the rom boot screen after converting to f2fs? Is the google screen bootlooping?
Most recent try at converting...
Reboot into TWRP (2.8.3.0) recovery
Wipe the system, data, cache, dalvik cache
Change system, cache, and data (one at a time manually) from EXT4 to F2FS
Reboot Recovery
In main TWRP menu, hit "Mount", and "Enable MTP" if it is not already enabled
Drag the two zip files you downloaded into the TWRP folder
Hit "Install", find the "TWRP" folder
Select the Slim group zip and swipe to flash
Go back and select the gapps zip and swipe to flash
Reboot the system
Wait a few minutes to boot up
stuck on google screen????
-Added Notes-
have tried rebooting into recovery and get stuck on the google screen as well
only able to get into bootloader (3.34) (Do I need to update Bootloader img?)
also my nexus 7 was from the first round shipments so its super old
Related
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Maybe try this...
http://forum.xda-developers.com/showthread.php?t=1781250
Or use this program...
http://forum.xda-developers.com/showthread.php?t=1766475
Lockable said:
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Click to expand...
Click to collapse
Reboot into bootloader (hold power to turn off, as soon as it does hold vol down)
Install the android sdk if you haven't. Download a recovery image from clockworkmod.com, put the image in your /platform-tools folder. Open a command Window there
Fastboot flash recovery xxxx.img
Fastboot boot xxxx.img
Dl a rom
Put it in your platofrm-tools folder
Adb push romxxx.zip /sdcard/Download
Flash the ROM in recovery
Reboot
Sent from my Google Nexus 7 using Tapatalk 2
When I turn on my tablet now, it automatically open up ClockworkMod Recovery. I am able to properly install a rom (wipe all data then install rom from sd) but when i reboot my device it goes back into clockwordmod recovery. Any idea how to bypass automatically booting straight into recovery mood and booting into flashboot?
EDIT
i am unable to push new roms in
mis-post, my bad.
Hey everyone,
As the title states, I'm stuck at the boot screen. It's got the Google logo with an unlock symbol at the bottom of the screen.
I was trying to update to the recent AOKP release (I had been on an earlier release) and something went wrong.
From this page http://forum.xda-developers.com/showthread.php?t=1766684 I followed these instructions:
Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system (if using CWM). To format system w/TWRP, select Wipe then System!!!
I think the issue occured after I selected to wipe SYSTEM.
Now, I can get to the fastboot menu (volume down + power). I can select restart bootloader/recovery mode/start...but the phone always stops at the GOOGLE logo (with the unlock symbol at the bottom).
So then I tried to use the WugFresh tool kit to go "Back to Stock" with Current Status of "Soft-Bricked/Bootloop" but that didn't work either. The command prompt lines came up on the PC and it said everything was supposed to reboot (and may do it a few times) but mine just sat at the fastboot menu. When I tried again, I noticed a lot of things failing in the automated command prompt.
So now I'm not sure what to do. Can anyone help me?
Thanks
Edit: I should mention that I did update the bootloader first to makoz10o from http://forum.xda-developers.com/showthread.php?t=2105983
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Check my thread, I had the same problem. 5.0.1 was fine but sensors went kaput, yes all of them. Flashed factory image 5.1, endless boot screen. After a day or two of flashing 4.4.4 (sensors were back working okay, wow big surprise), tried flashing 5.1.1 pure stock, same.
I'm back to 4.4.4 after restoring apps and data. Not sure I want to use 5.0.1 due to hte memory leak and other bugs that should be fixed with 5.1. But I'm certain that the factory image of 5.1.x won't boot on the N4.
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
Try doing this
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Hope that helps
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
I don't think that the factory reset will solve the problem. Have you tried waiting for 10-15 minutes for the phone to boot up? After OTA's and clearing cache the phone usually takes a while to boot up. If that doesn't work, factory reset using a custom recovery (this will delete your /data folder but not /data/media so your internal storage won't be wiped)
Blacksmith5 said:
.. Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
My, that text looks familiar....
So I wiped cache and so on now the thing is hanging at the Motorola screen and that's it.
I tried to get a sbf but all who should be compatible are down so that I pretty much am freaked.
Is there a way to get at least now a clean rom on it maybe something new 4.4.2 without SDCard or is that also a nogo?
----
So if your phone won'T boot and you just have a white light or nothing at all. You probably have less battery power to sbf flash something.
I used the Jumper cable method from Sorensiim.
That worked like a charm.
If you are looking for sbf files. Here are some.
----
So now I rooted that thing and tried to install bootmenu. Iused the adb method with ./install.sh permission denied after the copy procedure was complete ((data/bootmenu chmod etc.). I tried 2ndinit with the problem that the program hangs after the download. So what is it now that freakin thing wants me to do?
----
Got Bootmenu installed now the Defy has a Bootloop. For a short time before it loops the white led blinks. No volume up or volume down work.
----
Hanging at M logo on re-boot
Having rooted the phone . . .
1. Switch on and await blue LED
2. Press volume down to enter Android Boot Menu (v 1.1.8-jordan)
3. Recovery
4. Custom Recovery > Cyanogen Defy Recovery (v5.0.3.1-jordan)
5. Wipe Data / Factory Reset
6. Wipe Cache Partition
7. Advanced > Wipe Dalvik Cache
8. Install zip from SD card
9. Toggle signature verification to Disabled
10. Toggle script asserts to Disabled
11. Choose zip from SD card
12. Apply zip from SD card
13. Reboot
14. Hangs at M logo
Tried with and without step 10.
The zip files tried are the only two ‘nightlies’ on the XDA website, as I have been unable to find the last ‘stable’ version.
Can anyone help please?
Hi, I'm sorry for my English Spanish. I have since today zuk z1, installing "CM13 Coldbird" and entered correctly after performing all the steps, but connect wifi and get ip enters loop mode and does not come out of there, back at the beginning, initial settings and jump around and just 30 seconds later it happens again.
Buy two units and is installed well and gave me problems but restauré factory and it is correct but can not find this solution.
Hi Pichi. Which build did you use?
me too
I have the same problem, but in my case I have no time for do nothing, it turns on and then one second later reboot and reboot and reboot I'm desperate, I have no option to enter to fastboot or recovery because I have no time to press any button, any idea?
Alexdelgadoperez98 said:
I have the same problem, but in my case I have no time for do nothing, it turns on and then one second later reboot and reboot and reboot I'm desperate, I have no option to enter to fastboot or recovery because I have no time to press any button, any idea?
Click to expand...
Click to collapse
To enter recovery when experiencing such problems, you can hold the power button for 5 seconds to turn off / reboot device. After reboot, press and hold the volume up and down button at the same time until you see TWRP screen (2-5 seconds).
Then in TWRP screen, you can wipe system, cache, etc and perform another clean flash.
I experienced such behavior while using build 4/16 before. I recommend installing gapps micro package for such build to avoid reboots. Also, you can try and follow the following steps while installing CM13 build 4/16:
1. Wipe cache, Dalvik cache, data system.
2. Install mm tools
3. Install CM build 4/16
4. Reboot to system. Wait until stabilized (2-5 mins after you see the homescreen)
5. Reboot to TWRP
6. Make full Nandroid backup (just in case) - optional
7. Install gapps micro (if this won't work, try installing gapps Pico or the full gapps suite.
8. Reboot system