im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16
What exact version of cwm do you have, also try flashing the boot.img on the phone. Extract the zip, find the boot.img and place it in the root of your platform tools folder on you're computer, boot into fastboot on your phone, initiate the command: fastboot flash boot boot.img
It will send the boot. If you're on Mac do: ./fastboot flash boot boot.img
If it is a confirmed write of the boot.img, reboot the device.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
my clockworkmod is 6.0.3.2
Sent from my ADR6300 using Tapatalk
S-off or s-on? If s-on I would suggest flashing the boot.img via the command:
fastboot flash boot boot.img
You say you can get past the boot screen of CM 11? Its more than likely you need to flash the boot.img in fastboot.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
javinesteves said:
im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16
Click to expand...
Click to collapse
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds
zachf714 said:
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds
Click to expand...
Click to collapse
so what do i do i get an error with fastboot that remote not allowed
javinesteves said:
so what do i do i get an error with fastboot that remote not allowed
Click to expand...
Click to collapse
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery
zachf714 said:
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery
Click to expand...
Click to collapse
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore
javinesteves said:
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore
Click to expand...
Click to collapse
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk
zachf714 said:
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
so what do i do? im tired of cm7
javinesteves said:
so what do i do? im tired of cm7
Click to expand...
Click to collapse
Lower the clock speed and deal with the lag
Sent from my SCH-I535 using Tapatalk
Related
I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...
alfkhr said:
I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...
Click to expand...
Click to collapse
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
no luck
efrant said:
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
More Info Required...
alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
Are you unlocked and rooted?
Have you installed CWM?
If so, can you boot sucessfully to it?
Are you using the GN Toolkit?
Bit more info as to what you have done so far would be helpful...
unsuccessfully
I am very sad http://forum.xda-developers.com/images/icons/icon9.gif
alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2
I did all scenarios ...
efrant said:
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2
Hanging When Booting JB
alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
yes
efrant said:
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes boot loader version is lc03 and Radio is xxlf1
mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
Yeah it sounds like maybe you didn't wipe man.
Sent from my Galaxy Nexus using Tapatalk 2
Yes I do
mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
I did all kind of wipe !!!
Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.
Still
efrant said:
Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.
Click to expand...
Click to collapse
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???
alfkhr said:
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???
Click to expand...
Click to collapse
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.
Yes I do
netbuzz said:
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.
Click to expand...
Click to collapse
still the same
Up
I tried installing a custom rom today and I think I messed up really bad, because my phone does not get pass the boot screen and I cannot enter the recovery setting. I think I messed up after entering
fastboot flash boot boot.img
in the command prompt and restarting because I forgot to put the rom zip on my phone. Since then I could not get pass the boot screen and even tried running a backup using CWM, but it didn't help. I then managed to mount my phone and put the rom onto it and installed it, but again it didn't help.
Now my phone can only enter the bootloader, I select hboot and fastboot, but nothing else works. Everytime I select recovery or factory reset I get the htc boot screen and it gets stuck. Does anyone have any solutions?
Thanks
did u backup your phone rom???
if you did u can go to recovery and restore it
and never try to change rom again trust me in that
otherwise i can't help bcuz i did the same mistake
I did make a backup, but like I said I can't enter recovery anymore, so I can't load the backup.
Thanks for trying to help anyway though.
fastboot erase cache
Often fixes recovery problems.
BenPope said:
fastboot erase cache
Often fixes recovery problems.
Click to expand...
Click to collapse
Still not working, thanks anyway.
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
BlueSingA said:
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
Click to expand...
Click to collapse
I have hboot 1.39.0000 and I was trying to install the latest cyanogenmod cm-10-20130106-NIGHTLY-endeavoru.
Yeah I realized this after I restarted and did it get the zip onto the phone. I think I installed it, but the phone is still stuck on the boot screen
UPDATE: Okay I've managed to install CWM recovery, so I think I'm making progress
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
BlueSingA said:
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
Click to expand...
Click to collapse
Yeah CWM didn't load up, but I got it working again. Well it seems I'm back to getting the rom to install and being stuck at the boot screen again, so maybe I just need to use a different rom. Thanks for the help though
Okay, I've tried installing a few roms, but unfortunately I'm still on the boot screen, I can sometimes even reach the cyanogenmod boot screen, but get stuck there. I've read that this might be kernel issue, does anyone have any ideas?
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are a goddamn hero! Thanks, this solved everything.
No problem!
Sent from my EndeavorU using xda app-developers app
I've been hitting boot loops left and right. After beups s-off method, I succesfully flashed custom recovery and a ROM, but I accidentally flashed an international version of a kernel. During the aroma installer it froze and I restarted the phone, but now it will not boot normally or into recovery. I've tried to flash the stock kernel but I still can not get into recovery. Any advice? I've tried different recoveries and erased fastboot cache before each flash
Any help would be greatly appreciated
D-hes said:
I've been hitting boot loops left and right. After beups s-off method, I succesfully flashed custom recovery and a ROM, but I accidentally flashed an international version of a kernel. During the aroma installer it froze and I restarted the phone, but now it will not boot normally or into recovery. I've tried to flash the stock kernel but I still can not get into recovery. Any advice? I've tried different recoveries and erased fastboot cache before each flash
Any help would be greatly appreciated
Click to expand...
Click to collapse
Can you fastboot flash the boot.img?
Sent from my HTC6500LVW using Tapatalk 4
D-hes said:
I've been hitting boot loops left and right. After beups s-off method, I succesfully flashed custom recovery and a ROM, but I accidentally flashed an international version of a kernel. During the aroma installer it froze and I restarted the phone, but now it will not boot normally or into recovery. I've tried to flash the stock kernel but I still can not get into recovery. Any advice? I've tried different recoveries and erased fastboot cache before each flash
Any help would be greatly appreciated
Click to expand...
Click to collapse
Flash andybones bone stock rom and see if that boots. Also, make sure wipe boot in recovery.
Sent from my Nexus 7 using Tapatalk 4
APeaceofStrange said:
Can you fastboot flash the boot.img?
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
I can, but I don't see any noticable differences.
dottat said:
Flash andybones bone stock rom and see if that boots. Also, make sure wipe boot in recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
My device isn't mounting through twrp. Any way to send the rom through adb?
Success! I had to sideload it through cwm but it flashed through recovery and all is well. Thanks for the imput!
D-hes said:
Success! I had to sideload it through cwm but it flashed through recovery and all is well. Thanks for the imput!
Click to expand...
Click to collapse
No problem, sounds like you picked up some new skills tonight too !
Sent from my Nexus 7 using Tapatalk 4
D-hes said:
Success! I had to sideload it through cwm but it flashed through recovery and all is well. Thanks for the imput!
Click to expand...
Click to collapse
Hey Im having the same issue as you. How did you fix it?
BelievingThomas said:
Hey Im having the same issue as you. How did you fix it?
Click to expand...
Click to collapse
I did a factory reset through the fastboot, reflashed the recovery img and wiped the recovery cache and it allowed me to run cwm. Then, since I was having issues mounting, I used CWM's sideload program in their recovery that allowed me to flash roms without having to put them on the SD card. Where are you stuck at?
D-hes said:
I did a factory reset through the fastboot, reflashed the recovery img and wiped the recovery cache and it allowed me to run cwm. Then, since I was having issues mounting, I used CWM's sideload program in their recovery that allowed me to flash roms without having to put them on the SD card. Where are you stuck at?
Click to expand...
Click to collapse
In bootloader I clicked Factory Reset. It tried to load into recovery then looped again. I went back to Bootloader Flashed recovery Img and its still doing the same thing. How did you wipe cache without loading the recovery?
I did unlock my bootloader and root then I decided to flash cyanogenmod 10.2 stable I did wipe my phone and flashed Rom from recovery twrp and then gapps and then I was supposed to flash boot.img and Whn I connect my phone with computer at this point it doesnt recognize my phone so adb won't work I am on win8 but adb was working fine before and when I try to boot my phone without flashing boot.img it gets stuck on the cynogenmod logo I restored phone back to previous stock Rom and adb worked fine it's just Whn I try to flash boot.img it won't coz phone is not detached and one more question Whn we copy boot.img from the Rom.zip do we delete it the from the Rom or just keep a copy of boot.img there too here is my phone boot loader details please help
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1. 72. 0000
RADIO-5. 1204-167.31
CPLD-None
MICROP-None
Sent from my HTC One X using xda app-developers app
ruffain said:
I did unlock my bootloader and root then I decided to flash cyanogenmod 10.2 stable I did wipe my phone and flashed Rom from recovery twrp and then gapps and then I was supposed to flash boot.img and Whn I connect my phone with computer at this point it doesnt recognize my phone so adb won't work I am on win8 but adb was working fine before and when I try to boot my phone without flashing boot.img it gets stuck on the cynogenmod logo I restored phone back to previous stock Rom and adb worked fine it's just Whn I try to flash boot.img it won't coz phone is not detached and one more question Whn we copy boot.img from the Rom.zip do we delete it the from the Rom or just keep a copy of boot.img there too here is my phone boot loader details please help
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1. 72. 0000
RADIO-5. 1204-167.31
CPLD-None
MICROP-None
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
first flash boot.img and then flash the rom and just copy the boot .img from arhive to your fastboot folder nothing else to do. And the best way will be to use XP or Win&
Thant said:
first flash boot.img and then flash the rom and just copy the boot .img from arhive to your fastboot folder nothing else to do. And the best way will be to use XP or Win&
Click to expand...
Click to collapse
But when I wipe then phone is not recognised
Sent from my HTC One X using xda app-developers app
ruffain said:
But when I wipe then phone is not recognised
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But you flash the boot.img from computer and after this from recovery you must wipe and flash the rom. First flash BOOT.IMG after this go in recovery and flash the rom and gapps. When you use recovery you don't need computer
Thant said:
But you flash the boot.img from computer and after this from recovery you must wipe and flash the rom. First flash BOOT.IMG after this go in recovery and flash the rom and gapps. When you use recovery you don't need computer
Click to expand...
Click to collapse
True but I men before flashing Rom I need to wipe and factory reset so I first wipe then flash boot.img and then flash Rom
But as soon as I wipe my phone is not recognised
Sent from my HTC One X using xda app-developers app
ruffain said:
True but I men before flashing Rom I need to wipe and factory reset so I first wipe then flash boot.img and then flash Rom
But as soon as I wipe my phone is not recognised
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
OK listen naw do this:
1 Flash boot.img
2. go in recovery and WIPE everything exept sd card
3. Flash the rom from recovery
Report back and fallow the numbre order 1 next 2 next 3
Thant said:
OK lise naw dio this:
1 Flash boot.img
2. go in recovery and WIPE everything exept sd card
3. Flash the rom from recovery
Report back and fallow the numbre order 1 next 2 next 3
Click to expand...
Click to collapse
when into fastboot
and tried to flash the boot.img
C:\Fastboot>flashboot flash boot boot.img
'flashboot' is not recognized as an internal or external command,
any idea
ruffain said:
when into fastboot
and tried to flash the boot.img
C:\Fastboot>flashboot flash boot boot.img
'flashboot' is not recognized as an internal or external command,
any idea
Click to expand...
Click to collapse
YES look at your command it's wrong the command is fastboot flash boot boot.img not FLASHBOOT
Thant said:
OK listen naw do this:
1 Flash boot.img
2. go in recovery and WIPE everything exept sd card
3. Flash the rom from recovery
Report back and fallow the numbre order 1 next 2 next 3
Click to expand...
Click to collapse
Thant said:
YES look at your command it's wrong the command is fastboot flash boot boot.img not FLASHBOOT
Click to expand...
Click to collapse
yes frustrated the other times i tried was gud now leme do ur 123 steps
and would report back but if i wipe after flashiing boot wont it wipe it too
ruffain said:
yes frustrated the other times i tried was gud now leme do ur 123 steps
and would report back but if i wipe after flashiing boot wont it wipe it too
Click to expand...
Click to collapse
no you will not wipe the boot.img
Thant said:
no you will not wipe the boot.img
Click to expand...
Click to collapse
so i flash it while i still have my old stock rom installed right?
the flash boot
wipe/factory reset
flash rom nd gapps from recovery?
ruffain said:
so i flash it while i still have my old stock rom installed right?
the flash boot
wipe/factory reset
flash rom nd gapps from recovery?
Click to expand...
Click to collapse
yes
Thant said:
yes
Click to expand...
Click to collapse
ok one more problem whn i try to wipe it doesnt wipe nything it say wipe sucessful but the phone boots with old o/s shd i just flash the recovery again?
So I already posted before about a bootloop issue I had. I fixed it by completely rerooting from scratch by following Cyanogens wiki (including changing the firmware) and then it worked for a while, but then it started bootlooping again (no matter which ROM) I used. Then I rerooted it from scratch again and this time it's only been like a week and its starting to bootloop again. I have no idea what to do anymore, I mean seriously, what else there is to do, since I've already tried rerooting/reflashing?
EDIT: Could it be because I chose the wrong way to downgrade when rooting? Like in the cyanognemod vision rooting guide there are 2 options for downgrading, depending on if you have gingerbread or froyo. Everything did work when I did it, though, so I don't think it would be because of this.
Can't say for sure, try and grab a logcat or last_kmsg
Also boot to bootloader and write down everything on that screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Can't say for sure, try and grab a logcat or last_kmsg
Also boot to bootloader and write down everything on that screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here's the bootloader info:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010, 15:56:38
Click to expand...
Click to collapse
logcat: pastebin.com/XXCPBFg1
last_kmsg: pastebin.com/Rrr8CWEh
Everything looks good, kernel never panics and shuts off and logcat shows mostly normal startup processes. Maybe can you explain more your situation, like if you were to wipe all right now and than flash a new ROM would it work? Then latter on you get a bootloop, or will new ROMs just not flash at all?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Everything looks good, kernel never panics and shuts off and logcat shows mostly normal startup processes. Maybe can you explain more your situation, like if you were to wipe all right now and than flash a new ROM would it work? Then latter on you get a bootloop, or will new ROMs just not flash at all?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried Cyanogenmod 7 and 2 other custom roms, all three just bootloop. Could it be a hardware issue?
And yeah I can install roms just fine, they bootloop after booting up, like a few seconds after it has started up.
I wouldn't call it hardware just yet, each time you flash a new ROM does the bootanimation change? Also let's make sure you wipe everything before flashing a new ROM
http://forum.xda-developers.com/showthread.php?t=2348266
Here, in the first post, you will find a super wipe script and aio formatting script
Download these and put on sdcard
Now boot to bootloader and run these commands through fastboot (see the above link if you need help setting up fastboot)
fastboot erase system -w
fastboot erase boot
Now boot into recovery and flash both the superwipe and aio wipe tool (just like flashing a ROM)
The above is overkill yes, but its best to be sure you wipe clean when having issues like yours
Now once complete do your standard wipes from recovery and flash ROM plus proper gapps (if needed)
Let me know what happens here
If in a bootloop can you grab some new logs again, preferably with the full bootloop in them
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
I wouldn't call it hardware just yet, each time you flash a new ROM does the bootanimation change? Also let's make sure you wipe everything before flashing a new ROM
http://forum.xda-developers.com/showthread.php?t=2348266
Here, in the first post, you will find a super wipe script and aio formatting script
Download these and put on sdcard
Now boot to bootloader and run these commands through fastboot (see the above link if you need help setting up fastboot)
fastboot erase system -w
fastboot erase boot
Now boot into recovery and flash both the superwipe and aio wipe tool (just like flashing a ROM)
The above is overkill yes, but its best to be sure you wipe clean when having issues like yours
Now once complete do your standard wipes from recovery and flash ROM plus proper gapps (if needed)
Let me know what happens here
If in a bootloop can you grab some new logs again, preferably with the full bootloop in them
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the boot animation does change. Also, is there another way to do fastboot erase system -w and fastboot erase boot, without doing them through fastboot, because I'm on Windows 8.1 x64 and I've found no way to get fastboot drivers to work on this machine. Adb for example does work, so can I do it through that somehow?
EDIT: I didn't do the fastboot erase, but I did flash the superwipe and aio wipe tool and now after flashing a ROM, it has been stable for a few minutes now. I don't know if the bootloop will return, because previous times it had returned even after a week or two, but then again I had never used these wipe roms before, so who knows what will happen. We'll see, thanks!