Related
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
cdjadex said:
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
Click to expand...
Click to collapse
Did you ever create a nand backup? If so, go back to it first and verify you don't have a hardware issue.
If you don't have a backup, search this forum for the Eris RUU and I'd go back to that and root using the newest method...basically start over from a working phone.
I do have a nand backup, I have been restoring when i leave work because my phone has to be working. It works fine with the OTA 2.1 that i had just rooted...
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Sjflowerhorn said:
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Click to expand...
Click to collapse
I had this same issue last night, though I kept repeating the Nexus-style boot screen (the "X" thing) over and over. I did a full data/dalvik wipe and everything came up just fine. I had this experience with two different CyanogenMod ports.
I was running GorillaSense 2.3 and decided to give CM 7 RC1 a try. When I flashed it and then rebooted, I went into a bootloop so I tried doing a nandroid restore of the backup I did prior to flashing CM 7 and I got this error:
Erasing boot before restore...
E:format_volume: no MTD partition "boot"
Error while formating BOOT:!
I am using ClockworkMod Recovery v3.0.0.5.
The only thing I can think of that I did out of the "norm" was replace the host file in the system to block ads.
Does anybody know how to solve this? I am unable to use my phone at the moment...
I am able to go into Advanced Restore and retore system, data, and cache. When I try to restore boot I get the message I wrote above.
Clockwork mod 3.0.0.5 works only with gingerbread roms. Any Frito roms need 2.1.5.2. I had this problem going from gorilla hd sense to cm7 as well. Flash a new clockworkmod or a gingerbread rom or evils miui
Sent from my HTC Glacier using XDA App
I wiped data and cache. Then Flashed this ROM Evil's HD port- http://forum.xda-developers.com/showthread.php?t=878320
I am still getting boot loops.
Evil's MIUI requires 2.1.5.4 - http://forum.xda-developers.com/showthread.php?t=874257
Note - before wiped and flashed, I had gone into advance restore and restored, system, data and cache from my prior nandroid backup.
Hopefully that didn't screw things up. I don't have access to download the GorillaSense v2.3 that I had used before to see if flashing that would work since I am at work and it's blocked. I'm going to try that next, once I get home.
Which Clockworkmod version would I need for CM 7 RC1? Would v3.0.0.6 work?
Success!
Flashing recovery 3.0.0.6 did the trick! I flashed CM 7 RC1 and I don't get boot loops anymore. Thank you for your help.
I turned off the phone and booted back into recovery to make a nandroid backup after this successful flash. Then I flashed the google apps that come along with CM 7 and I'm stuck with the boot loop again...
I have restored the nandroid back, same bootloop, and wiped data & cache, flashed CM 7 only like the first time, and I still get the bootloop. This is so weird that it only worked the first time.
The first time it didn't boot loop I was left at the "desktop" screen. Now, when I boot loop, I get to the 'Welcome to HTC Glacier ( with the android you touch ) screen, only for like a second or two and then it loops.
Any ideas how to fix this? I'm thinking maybe I need to flash a new boot.img or something.
------------------------------
Ok, I flashed GorillaSense v2.3 which is what I was using initially. It works fine. No boot loops. I want to use CM 7 though! lol
intalled AOSP Paradise and gapps on my defy(green lense) and everything seems to be working great except:
1. everytime i turn my phone off when i turn it back on the Mokee logo comes up 1st and then it loads AOSP fine but i have to re-enter all my google info
2. it doesn't save any of my settings.
3. it wont let me download any apps...they start downloading but just sit there downloading and if they do finish, it says cant install, not enough memory but i reformatted the sd partition in recovery before installing AOSP because i knew it didnt have enough memory to even install it.
4. Why does that Mokee screen come on still?
i had the Mokee ROM before but shouldnt that have gone away when i wiped data and cache?
Did i do something wrong on install? i did wipe data/factory reset, wipe cache, flashed ROM, flashed gapps, wipe dalvik cache and rebooted twice. it loads fine and everything seems to be working but i dont like having to start from scratch everytime i turn my phone on.
Help pls...frustrating
Try clean install as said in this thread.
forum.xda-developers.com/showthread.php?p=32093770#post32093770
Make sure you flash new rom before rebooting
Flash SBF and then Flash new ROM
[Q]AOSP Paradise
Euro_Rules said:
Flash SBF and then Flash new ROM
Click to expand...
Click to collapse
ok that fixed boot screen but not the redoing of google, downloading apps or saving settings...any other suggestions?:fingers-crossed:
i figured it out! i was missing the firmware from when i bricked it...so, i found a firmware file, flashed it and now it works like a charm!! yay
Moved to Q&A. Please ask all questions there.
So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.
First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.
Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.
Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
rowdypixel said:
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
Click to expand...
Click to collapse
https://s.basketbuild.com/gapps
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
xDroidZz said:
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
Click to expand...
Click to collapse
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Same problem.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
Nexus 7 2013 WiFi
Any fix for this? I've been struggling with it for a whole day now.
I have not found a fix. I reverted back to KitKat since I needed to use my phone during the week.
Bump
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Do you know what version of CWM you were running? I might try updating it over the weekend and see if that works as an alternate solution.
Try this. This worked for me.
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
Gapps crashes
rowdypixel said:
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Click to expand...
Click to collapse
Before adding gapps after flashing cm-12 wipe dalvik and cache, flash ktoonz lollipop kernel then flash gapps for lollipop. This worked for me.
anonymousguy44 said:
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Click to expand...
Click to collapse
Hey I'm having the same problem, can you describe how in Odin you got back to stock? You flashed stock and lost your custom recovery? That's weird, I figured a custom recovery was like a bios