Related
I have had my Nexus 7 with SmoothROM on it for a long time now, I use it here and there, but I noticed it acting kind of glitchy lately especially when using the keyboard. I got 2 notifications from GROUPER (i think thats the name of it...) saying I had an update to SmoothROM (v 4.2) and that google apps needed to be updated... I did the normal crap, wiped everything, flashed the new smoothrom, flashed on the google apps, but when I rebooted it just keeps popping up saying "Unfortunately, the process blah blah gapps has stopped", then when i press ok it says Unfortunately, Setup Wizard has stopped".... and when i press ok on that it just keeps popping back up... will NOT go away no matter what I try...
On top of this... I tried going to fastboot and putting it in recovery mode but then it just goes to the main boot screen that says Google with a lock at the bottom, and it is just stuck there...
So what would be the easiest course of action here? I can't get it into Recovery mode I don't think, although I forgot how to do it in the first place, I thought it had to do with sliding the lock somewhere at the boot screen but I have tried that and nothing seems to work...
ANY HELP WOULD BE GREATLY APPRECIATED!
3..2..1...
Till someone tells you that you are a knucklehead for posting this in the Dev section and moves it to where it belongs. LOL
SquireSCA said:
3..2..1...
Till someone tells you that you are a knucklehead for posting this in the Dev section and moves it to where it belongs. LOL
Click to expand...
Click to collapse
oops >.>
SquireSCA said:
3..2..1...
Till someone tells you that you are a knucklehead for posting this in the Dev section and moves it to where it belongs. LOL
Click to expand...
Click to collapse
how do i delete this thread? i reposted it in the Q&A section. sorry about that...
Untraumatized said:
how do i delete this thread? i reposted it in the Q&A section. sorry about that...
Click to expand...
Click to collapse
Connect to computer through USB. Download Odin on computer, then download smooth ROM 4.2. Put md5 file on PDA Section and press start. Any problem just check forum. Personally I think smooth ROM is too buggy. I'm on cyanogen mod 10.1 using Trinity kernel works amazing!!
mccolvinj said:
Connect to computer through USB. Download Odin on computer, then download smooth ROM 4.2. Put md5 file on PDA Section and press start. Any problem just check forum. Personally I think smooth ROM is too buggy. I'm on cyanogen mod 10.1 using Trinity kernel works amazing!!
Click to expand...
Click to collapse
You really used Odin for a Nexus 7? I only used it once, on a Samsung GSII. I thought it was only for Samsung too.
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?
opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!
Hey guys,
So I tried looking around in the forum but can't seem to get an understandable answer.
I have a Nexus 7 (2012). I was running CM 10.2, but wanted to move up to KitKat. I downloaded the new ROM, and did the wipe and everything. But none of the new ROMs will install on my Nexus 7. Every time, it will start to install, then it will say "status 7, installation aborted" and that little android guy in the background will be lying down with a red triangle over him.
I have tried several different ROMs, but they all seem to have the same effect.
I THOUGHT about ADB sideloading, but my computer does not recognize the device. So there's that.
.....Any ideas? Please?
Update your recovery
Sent from my Nexus 5
Kangaji said:
Hey guys,
So I tried looking around in the forum but can't seem to get an understandable answer.
I have a Nexus 7 (2012). I was running CM 10.2, but wanted to move up to KitKat. I downloaded the new ROM, and did the wipe and everything. But none of the new ROMs will install on my Nexus 7. Every time, it will start to install, then it will say "status 7, installation aborted" and that little android guy in the background will be lying down with a red triangle over him.
I have tried several different ROMs, but they all seem to have the same effect.
I THOUGHT about ADB sideloading, but my computer does not recognize the device. So there's that.
.....Any ideas? Please?
Click to expand...
Click to collapse
make sure you are on the latest TWRP recovery and if it still gives you problems, make sure your using the latest bootloader, I have heard reports of an older bootloader causing problems with some rom installs....
THANK YOU THANK YOU
It works PERFECT now, looks like. Thanks again!!
THANK YOU THANK YOU
It works PERFECT now, looks like. Thanks again!!
Well it won't let me post in the actual thread, so I'm going to post the errors I got here. Maybe you guys can help.
For my Droid X .621 I followed the guide at [Kitkat] CM11 Android 4.4 for the Droid X and got all the way to having TWRP installed and booted, after wiping in CWM. However, when I tried to install the CM11 custom ROM from 4/10, I got an error. The instructions said to use assert_bypass.zip if you get an error, but there is no link to download. Others say they just removed the line that says "assert" in the ROM file? Anyway. I turned off my phone and took my SD card out to see. Didn't end up making any changes. Rebooted, and stuck on "M." I couldn't get into TWRP or CWM, just stock recovery. Lame. Had to flash back to stock using the bootloader.
So, I decided to try Aaahh's APK, app.apk. However, The "Install Bootmenu" button force closes the app. No luck.
Anyone?
Update:
Couldn't ever get "Install bootmenu" to work, but that's cool. What worked for we was also doing a wipe from within TWRP, not just CWM. Tricky, tricky.
Aph0ticBeast said:
Well it won't let me post in the actual thread, so I'm going to post the errors I got here. Maybe you guys can help.
For my Droid X .621 I followed the guide at [Kitkat] CM11 Android 4.4 for the Droid X and got all the way to having TWRP installed and booted, after wiping in CWM. However, when I tried to install the CM11 custom ROM from 4/10, I got an error. The instructions said to use assert_bypass.zip if you get an error, but there is no link to download. Others say they just removed the line that says "assert" in the ROM file? Anyway. I turned off my phone and took my SD card out to see. Didn't end up making any changes. Rebooted, and stuck on "M." I couldn't get into TWRP or CWM, just stock recovery. Lame. Had to flash back to stock using the bootloader.
So, I decided to try Aaahh's APK, app.apk. However, The "Install Bootmenu" button force closes the app. No luck.
Anyone?
Click to expand...
Click to collapse
Have you tried flashing any other release version of CM11 before opening up a spam thread? Did you go to the devs and ask about the assert_bypass? Did you even read the thread and see that aaahh's apk has issues? Act and post like a noob, and you will get treated as such, esp when you do not do basic thinga such as.reading thoroughly and asking OPs/devs for help directly.
By the way, nothing with the CM11 project, to include any errors experienced, is lame. Dx has achieved a huge dev leap with the creation of a working CM11
Sincerly, one of the founding members of the Dx CM11 project.
palmbeach05 said:
Have you tried flashing any other release version of CM11 before opening up a spam thread? Did you go to the devs and ask about the assert_bypass? Did you even read the thread and see that aaahh's apk has issues? Act and post like a noob, and you will get treated as such, esp when you do not do basic thinga such as.reading thoroughly and asking OPs/devs for help directly.
By the way, nothing with the CM11 project, to include any errors experienced, is lame. Dx has achieved a huge dev leap with the creation of a working CM11
Sincerly, one of the founding members of the Dx CM11 project.
Click to expand...
Click to collapse
Really, is that how you treat your new members? Am I not posting to the "noob" section anyway? You didn't even bother to read my post. Of course I read aaahh's thread. How else would I have found the app.apk? Of course I know that the apk has issues. He wanted us to test it: now I'm giving my feedback. It isn't my fault that the forum won't let me post my feedback on his thread. I have to make 10 spam posts as fast as possible to be able to "ask OPs/devs for help directly." and "go to the devs and ask about the assert_bypass" like you want me too.
"to include any errors experienced, is lame." So you guys do or don't want to know what issues the instructions/procedure has? You don't want to make CM11 compat better? Okay. Fine by me. You know, I thought they did nightly builds to fix bugs or something - guess I was wrong. Kinda hard to fix them, if you discourage users from posting them.
Seriously? Flamer...
Aph0ticBeast said:
I have to make 10 spam posts as fast as possible to be able to "ask OPs/devs for help directly.".
Click to expand...
Click to collapse
Asking questions is fine, but any spam posts made just to get to 10 posts, may be removed by Mods.
sd_shadow said:
Asking questions is fine, but any spam posts made just to get to 10 posts, may be removed by Mods.
Click to expand...
Click to collapse
I apologize. I do not wish to spam. That was sarcasm in response to the previous poster using the term "spam" for my thread.
I'm just here to help. Take it or leave it.
Aph0ticBeast said:
The instructions said to use assert_bypass.zip if you get an error, but there is no link to download. Others say they just removed the line that says "assert" in the ROM file?
Click to expand...
Click to collapse
I'm CM11 dev. Instruction in Aaahh's thread not actual. New ROMs don't have "assert" device check. Maybe package corrupt? Did you check md5? I need to see error message. Try to redownload ROM (MEGA is the best)and install again. If you will get error do not do the reboot - stay in TWRP and install twrp_2.7_cm11_dx.zip once more, now you can reboot.
Actual instruction:
If you on custom ROM (CM, MIUI, LiquidICS, etc.) goto step 6.
Download Droid 2 Recovery Bootstrapper CWM 5.0.2.0 and Framaroot.apk to sdcard.
On phone: Settings->Applications(Enable Unknown sources)->Development->Enable USB Debugging.
Install Framaroot.apk, launch it and select "Gimli", reboot phone.
Install Droid2RecoveryBootstrap_CWM5.0.2.0.apk, launch it, select "Bootstrap Recocery", grant Superuser access and reboot phone.
Download twrp_2.7_cm11_dx.zip, latest gapps (3-22 or newer) and ROM to sdcard.
Reboot phone into CWM Recovery or if you on stock firmware launch Droid X Bootstrapper and press "Reboot Recovery".
In CWM choose wipe data/factory reset (this will completly delete all your data on phone except sdcard), then install zip from sdcard and select twrp_2.7_cm11_dx.zip.
Reboot system.
In TWRP choose Install and select ROM, then slide, do the same with gapps, after install Reboot system.
Aph0ticBeast said:
I apologize. I do not wish to spam. That was sarcasm in response to the previous poster using the term "spam" for my thread.
I'm just here to help. Take it or leave it.
Click to expand...
Click to collapse
no worries, just didn't want you to spam 10 posts, just to have them deleted.
I'd like to add to this thread. Tried doing the upgrade to KitKat CM11 today with a droid x running 4.5.621, failed to install the CM11 rom and I tried going to an earlier version of twrp (2.6.3) and CM11 from 3/14 but it caused me to go into the bootloop with the M logo.
Steps I took:
Framaroot install - that went fine
Droid X Bootstrapper install - that went fine
Went into bootloader, wiped the data, installed TWRP 2.7
Got into TWRP 2.7, tried to install CM11 from 4/10 and it failed
I tried multiple times, confirmed md5, tried a few previous releases, nothing worked
Then I tried rolling back to twrp 2.6.3 and installing cm11 from 3/14, that's when it just rebooted and got stuck on the M logo
I have taken the battery out to preserve the charge. Tried the triangle screen, pressing search did nothing. Tried the two volume button + power and got some text but nothing past that.
Hopefully there's a solution to either go forward or backward.
Ok so I am a little impatient so I flashed it back to the stock motorola 4.5.621.MB810 using rsd lite. It's weird that it told me it failed, but it still booted up fine.
I used this guide
608615-unbrick-your-droid-x-621-bootloader-30-04-only.html (won't let me post a link yet)
If there's a way to get it to 4.4 that would be awesome, but I got this phone from a friend so I can use it for testing android apps on, so if I have to play it safe and stay on 2.3.4 I will do that just to test backwards compatible apps.
alexss3 said:
Ok so I am a little impatient so I flashed it back to the stock motorola 4.5.621.MB810 using rsd lite. It's weird that it told me it failed, but it still booted up fine.
I used this guide
608615-unbrick-your-droid-x-621-bootloader-30-04-only.html (won't let me post a link yet)
If there's a way to get it to 4.4 that would be awesome, but I got this phone from a friend so I can use it for testing android apps on, so if I have to play it safe and stay on 2.3.4 I will do that just to test backwards compatible apps.
Click to expand...
Click to collapse
Okay, I flashed(installed) cm11 on my 4.5.621 droid x with no problem. Do you have the latest clockwork mod recovery installed on your phone?
Rom Manager?
Install root checker from google play store. It will tell you if the phone is rooted.
Open bootstrap recovery app. Click top button that says "bootstrap recovery". Wait until it says "success", click ok and THEN click boot into recovery.
If you click boot recovery 1st you will get bootloop. You MUST click bootstrap recovery FIRST.
Once into recovery menu:
Click wipe data/factory reset
Then click install zip from sd card
Then choose zip
Then select twrp(use volume buttons to move up and down menu)
Then once it installs continue with the directions from the original post
Installed CM11 and have had zero issues so far. Awesome work dev. I downloaded from Mega BTW.
Sent from my DROIDX using xda app-developers app
classic757 said:
Okay, I flashed(installed) cm11 on my 4.5.621 droid x with no problem. Do you have the latest clockwork mod recovery installed on your phone?
Rom Manager?
Install root checker from google play store. It will tell you if the phone is rooted.
Open bootstrap recovery app. Click top button that says "bootstrap recovery". Wait until it says "success", click ok and THEN click boot into recovery.
If you click boot recovery 1st you will get bootloop. You MUST click bootstrap recovery FIRST.
Once into recovery menu:
Click wipe data/factory reset
Then click install zip from sd card
Then choose zip
Then select twrp(use volume buttons to move up and down menu)
Then once it installs continue with the directions from the original post
Click to expand...
Click to collapse
Not sure what I possibly did wrong the first time around, but the second time worked fine with no issues. The one thing I did change was I chose SuperSU instead of the default Superuser. Don't know if that made any difference. But in any case, it's all working now with 4.4 and it's pretty sweet! Thanks for the help on this.
Do note that there is a bug with gapps, DO NOT INSTALL GAPPS RIGHT AFTER FLASHING THE ROM, reboot to system, reboot once you are at the home screen, go back to recovery THEN flash gapps.
Can a mod please flag this thread for removal.
Shuudoushi said:
Can a mod please flag this thread for removal.
Click to expand...
Click to collapse
Why?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 08:52 PM ---------- Previous post was at 08:41 PM ----------
Shuudoushi said:
Do note that there is a bug with gapps, DO NOT INSTALL GAPPS RIGHT AFTER FLASHING THE ROM, reboot to system, reboot once you are at the home screen, go back to recovery THEN flash gapps.
Click to expand...
Click to collapse
m.ksy stop recommending
flashing separately several builds ago.
---------- Post added at 09:04 PM ---------- Previous post was at 08:52 PM ----------
see post 7 in this thread, click to show content
sd_shadow said:
Why?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 08:52 PM ---------- Previous post was at 08:41 PM ----------
m.ksy stop recommending
flashing separately several builds ago.
---------- Post added at 09:04 PM ---------- Previous post was at 08:52 PM ----------
see post 7 in this thread, click to show content
Click to expand...
Click to collapse
I say flag it for removal just to help fight clutter in the forums, and I thought it was just the assert issue that was fixed, not the gapps issue as well.
Shuudoushi said:
Do note that there is a bug with gapps, DO NOT INSTALL GAPPS RIGHT AFTER FLASHING THE ROM, reboot to system, reboot once you are at the home screen, go back to recovery THEN flash gapps.
Click to expand...
Click to collapse
you're wrong, look at 04.07 changelog
m.ksy said:
you're wrong, look at 04.07 changelog
Click to expand...
Click to collapse
Well then, nice work and it seems I need to read over changelogs better ><
M.ksy keeps his rootzwiki thread clean and up to date.
Sent from my Amazon Kindle Fire using Tapatalk
Hi Guys, so I felt in the mood to try to flash my phone with a new rom. I read tons of topics, saw a bunch of YouTube videos and tryed it out for my self.
But boy did it go wrong..
Here is what I did.
I downloaded Odin and CWM 6.0.3.22 and aded the Clock work thingy.
Then i booted up into flash recovery and wiped cache and data/factory
Then i tryed to install from external SD card with this rom: AOSP Official 5.0 - S4 Google Edition - Stable-R3
It failed on something and I thought, hey lets try again... failed again, then I wiped again and tryed this rom: Google Play Edition LRX219
Got some error, think it was something with 7.
Well now it wont even boot up to the original state, its just stuck on the samsung logo. I can still boot up into CWM, but thats it. Im not sure where to go from here, adn I'm afraid to keep failing more roms on this thing.
Any suggestion?
Best regards Kasper
Solved. I ended up doing this: Link
Now I'm all back to stock.
Kjohnsen said:
Hi Guys, so I felt in the mood to try to flash my phone with a new rom. I read tons of topics, saw a bunch of YouTube videos and tryed it out for my self.
But boy did it go wrong..
Here is what I did.
I downloaded Odin and CWM 6.0.3.22 and aded the Clock work thingy.
Then i booted up into flash recovery and wiped cache and data/factory
Then i tryed to install from external SD card with this rom: AOSP Official 5.0 - S4 Google Edition - Stable-R3
It failed on something and I thought, hey lets try again... failed again, then I wiped again and tryed this rom: Google Play Edition LRX219
Got some error, think it was something with 7.
Well now it wont even boot up to the original state, its just stuck on the samsung logo. I can still boot up into CWM, but thats it. Im not sure where to go from here, adn I'm afraid to keep failing more roms on this thing.
Any suggestion?
Best regards Kasper
Click to expand...
Click to collapse
Hi mate , it happen to all of us ....
That recovery you are using seems old , install the newest one 6.0.4.7 and try again
EDIT: I9500 version is 6.0.3.2 you are sure you have the right version for your phone??
MAX 404 said:
Hi mate , it happen to all of us ....
That recovery you are using seems old , install the newest one 6.0.4.7 and try again
EDIT: I9500 version is 6.0.3.2 you are sure you have the right version for your phone??
Click to expand...
Click to collapse
Thx, I just updated the CWM to 6.0.4.7 and I still get the Error (status 7) no matter what rom i choose. Any ideas?
Try flashing from internal storage rather than the external SD.
Hexgore said:
Try flashing from internal storage rather than the external SD.
Click to expand...
Click to collapse
I would if I could. RIght now i cant even put anythin on the sd card as it won't mount. Even if choose to do so from CWM.
I'm lost here. I was thinkin of doing that whole "erase some codes" to avoid the Cod 7 problem, but now I cant get to my files... Super annoying.
- I'm pretty much lost at this point.
Solved. Edited the first post. Thanks everyone.
Kjohnsen said:
I would if I could. RIght now i cant even put anythin on the sd card as it won't mount. Even if choose to do so from CWM.
I'm lost here. I was thinkin of doing that whole "erase some codes" to avoid the Cod 7 problem, but now I cant get to my files... Super annoying.
- I'm pretty much lost at this point.
Click to expand...
Click to collapse
hi
try flashing a twrp recovery
http://teamw.in/project/twrp2/182
http://forum.xda-developers.com/showthread.php?t=2468187
some of this newer roms work better with it , if it fails again.....start from scratch , flash stock rom again and do it all over
http://forum.xda-developers.com/showthread.php?t=2265477
---------- Post added at 05:57 PM ---------- Previous post was at 05:55 PM ----------
Kjohnsen said:
Hi Guys, so I felt in the mood to try to flash my phone with a new rom. I read tons of topics, saw a bunch of YouTube videos and tryed it out for my self.
But boy did it go wrong..
Here is what I did.
I downloaded Odin and CWM 6.0.3.22 and aded the Clock work thingy.
Then i booted up into flash recovery and wiped cache and data/factory
Then i tryed to install from external SD card with this rom: AOSP Official 5.0 - S4 Google Edition - Stable-R3
It failed on something and I thought, hey lets try again... failed again, then I wiped again and tryed this rom: Google Play Edition LRX219
Got some error, think it was something with 7.
Well now it wont even boot up to the original state, its just stuck on the samsung logo. I can still boot up into CWM, but thats it. Im not sure where to go from here, adn I'm afraid to keep failing more roms on this thing.
Any suggestion?
Best regards Kasper
Solved. I ended up doing this: Link
Now I'm all back to stock.
Click to expand...
Click to collapse
Just saw your post mate.
Glad you made it