Database Users

[Q] [+Problem] Can't boot into CWM Recovery

Hi,
I really love my Nook Color (firmware 1.2/blue dot on package) which I picked up two days ago. I Installed CM7 on the microSD card right away and it's running fine overall. -- However, I cannot boot into recovery. - DANG!!!#[email protected]#
I have looked allover this forum and beyond, but none of the other threads deal with my NC's CWM problem - or offer a working solution I could understand/use...
The ingredients I took to cook up my CM7 install:
1.) "generic-sdcard-v1.3.img" ('extracted' to SD using Win32DiskMgr)
2.) "update-cm-7.0.3-encore-signed"
3.) "gapps-gb-20110613-signed"
Everything installed OK, including CWM 3.0.2.8., which is showing as app.
BUT... no matter how [often] I try to boot into CWM Recovery, it always boots straight into CM7.
(And, yes... I've tried all the "N" + "Power" button press combinations, I think... but none of them worked).
MY QUESTIONS:
- Any idea what I did wrong? Why can't I boot into recovery?
- How can I fix this without having to use ADB? (Note: Yes, I am willing to learn, but command-line programming is not exactly my idea of fun). I was hoping there actually is a simple fix to this problem... something like "place this [...] on your SD card and boot", or so???
...Thanks for your help & suggestions.

Have you tried holding down the power from cm7 and selecting reboot into recovery?
Sent from my LG Optimus V using Tapatalk

I think i know your problem. The 1.3 installer image is not fully compatible with CM7.0.3. You might be able to update to the RC or a nightly and get it to work. Otherwise you are going to have to remake the SD card.
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
I think i know your problem. The 1.3 installer image is not fully compatible with CM7.0.3. You might be able to update to the RC or a nightly and get it to work. Otherwise you are going to have to remake the SD card.
Click to expand...
Click to collapse
Thanks for your help, koopakid08! After flashing CM7 three more times in the meantime, I had that hunch, too...
Can you tell me what to use if one of my "components" is no good(?)??
I want to run CM7 off my microSD (not the eMMS install). -- So.. what do you recommend me to do, as I'm afraid I don't quite understand what you mean with "update to RC or nightly"...
Is my issue related to the CM7 version, or is it the "generic-sdcard-v1.3" image?? If it's the CM build (7.0.3), there is no RC available for the "encore" yet; just a nightly (#177) dated 8/31/2011.
If the problem is the sdcard 1.3 image, what else is there I can use to run CM7 off my microSD?
-- Thanks!
---------- Post added at 11:48 PM ---------- Previous post was at 11:34 PM ----------
Interesting... just found another guide on the web. Didn't see that all weekend .. :-(
http://androidforums.com/nookcolor-all-things-root/352736-how-install-cm7-your-nook-color.html
I'll try this one, hope it's finally working also for me...
---------- Post added 19th September 2011 at 12:31 AM ---------- Previous post was 18th September 2011 at 11:48 PM ----------
I can't believe it was THAT easy... [email protected]@##%$&$%@%*(!%%^& !!!!!!
It was indeed either the sdcard image, or CM7.0.3. Which one, I really don't care anymore, as I just flashed the latest CM nightly (#177) ... and CWM Recovery ...WORKS [:gasp:] !!!
It's a bit late now here in Chicagoland, so I better hit the pillow (it's a school night ..ha ha... tomorrow].
I will post instructions later; just in case someone else runs into the same issue.
Thanks, again, koopakid08, for getting me on the right track.
Good Night!!

Just in case you want to know what the problem was. It was the CM version you were using. The 1.3 image only works with cm7.1 versions. Glad you got it figured out.
Sent from my NookColor using Tapatalk

Just an additional observation... You are using an old version of CWR. The newest is 3.2.0.1.

I don't know if you got everything sort out but, bear in mind: booting off uSD has NOTHING to do with CwM R., whatever version.
Moreover, you boot into "recovery", not boot into "clockworkmod recovery"
If you intend to run off uSD, you can completely ignore anything about ROM Manager or CwM Recovery since those are not go together and it causes more headache than help.

Running Rooted 3.2.1 to ICS? Do I unroot?

I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks

tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA

3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.

Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?

tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA

3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA

I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.

thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:

dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA

BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA

3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting

what is the backdoor program you guys talk about?

tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.

jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....

This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy

Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA

3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage

I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA

TF101G completely bricked, can't mount SDcard...need big help!

Hello! I'm new here, but, as an Asus TF101G's owner (from september 2011), I've always take a look at this forum to stay update on the newest custom roms!
Unfortunately, I've got a big problem.
2 week ago, tired of the stock rom, I've installed CyanogenMod 10 B2 By Rayman and all went good.
Yesterday, I've tried to install the latest update, version B4, but I cant install it at all.
Infact when I tried to wipe all data from CWM recovery 6.0.13 menu, it crashed and stuck. Also when I try to mount from my sdcard stock asus firmware or a custom firmware, it says "E:cant mount sdcard".
I've tried all methods to flash at least the stock firmware, but with no results..Easyflasher (doesnt work with tf101g), BR Rootkit vers. 8.0 (successfull installed driver and correctly goes in apx mode, but crashes when try to flash a firmware), 1-Click Transformer Root (stuck on installing drivers), peri 0.4 (seems not working)...
The tablet remain stucked at EeePad logo and the only think I can do is to enter in CWM recovery, but I can't mount SDcard nor Usb, and all wipe commands aren't working.
Is there's anything I can do? or I have to send to RMA?
p.s. I've already tried to format the sdcard from windows, but nothing changed.

Try this step from this website Reverting to Stock ROM (unroot and remove CWM recovery)
its help u rollback your tablet to original version
IF DONT HAVE ANYONE CAN HELP YOU FIX IT

leonly1232 said:
.....
its help u rollback your tablet to original version
IF DONT HAVE ANYONE CAN HELP YOU FIX IT
Click to expand...
Click to collapse
Thx for the tip, but NvFlash works with TF101G? I thought it only works with TF101 model...am I wrong?

If so go to this page and read be careful red lines
Asus Transformer NVFlash Stock 3.1 & Stock 3.2 Recovery Roms (Unbricking Tools)

cttents was
leonly1232 said:
If so go to this page and read be careful red lines
Asus Transformer NVFlash Stock 3.1 & Stock 3.2 Recovery Roms (Unbricking Tools)[/URL]
Click to expand...
Click to collapse
It's a B70 model unfortunately..

yep, same here. Also bricked but no recovery (I was downgrading from stock ICS when happened).
I dont think that ASUS will approve RMA with that CWM and stucked custom rom.
What is that the wipe commands are not working? Is there any error message?

VITUSH said:
yep, same here. Also bricked but no recovery (I was downgrading from stock ICS when happened).
I dont think that ASUS will approve RMA with that CWM and stucked custom rom.
What is that the wipe commands are not working? Is there any error message?
Click to expand...
Click to collapse
when I select "wipe data" it stucks and seems is not going to say "done"..other wipes are ok.

and yes, any APX based technique (basic nvflash, easyflasher, wheelie) of reflashing the firmware wont work on the TF101G (sbkv3) - Ive tried everything I found.
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
keizer86 said:
no when I select "wipe data" it stucks and seems is not going to say "done"..other wipes are ok.
Click to expand...
Click to collapse
try to wipe cache and dalvik cache and then try to boot (or better cold boot if possible).

VITUSH said:
and yes, any APX based technique (basic nvflash, easyflasher, wheelie) of reflashing the firmware wont work on the TF101G (sbkv3) - Ive tried everything I found.
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
try to wipe cache and dalvik cache and then try to boot (or better cold boot if possible).
Click to expand...
Click to collapse
Already tried, didn't work

I successfully unbrick my TF101 with this
www*addictivetips*com/mobile/how-to-unbrick-asus-eee-pad-transformer-honeycomb-tablet
Note, i did it with Linux.
PS.- Replace * with dots

francf said:
I successfully unbrick my TF101 with this
www*addictivetips*com/mobile/how-to-unbrick-asus-eee-pad-transformer-honeycomb-tablet
Note, i did it with Linux.
PS.- Replace * with dots
Click to expand...
Click to collapse
uses classic nvlash - useless for tf101g
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
I guess we have to wait for devs to figure out a way to use nvflash on sl101 and tf101g

VITUSH said:
uses classic nvlash - useless for tf101g
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
I guess we have to wait for devs to figure out a way to use nvflash on sl101 and tf101g
Click to expand...
Click to collapse
I've started to think the only actual solution is to send to Rma and hope that they go over this modification

keizer86 said:
I've started to think the only actual solution is to send to Rma and hope that they go over this modification
Click to expand...
Click to collapse
I guess so.. Im doing the same thing, but I think Ive got better chance than you luckily stucked with ASUS ROM

Hi,
I'm concerned about the possibility of briking my tablet reading your posts
So, based on your experience, what do you think are the facts/actions/bad practices can brick TF101? Is there any recommendations to avoid brick? I think this would be very useful for beginners like me :highfive:
It would be nice to have 2 list:
What you should never do:
- Sit on it
...
What you can do with relative low risk:
- Hold it on your hands.
...
Thanks!

VITUSH said:
I guess so.. Im doing the same thing, but I think Ive got better chance than you luckily stucked with ASUS ROM
Click to expand...
Click to collapse
Last try..anyone have a final solution? Asus RMA seems not really good..and with custom rom installed my chances to get free warranty are tending to zero:crying:

keizer86 said:
Last try..anyone have a final solution? Asus RMA seems not really good..and with custom rom installed my chances to get free warranty are tending to zero:crying:
Click to expand...
Click to collapse
You have recovery, can you format sdcard?
No access to apx if you can't use sdcard you can't flash rom.
So im out of ideas. You can try to join the irc channel and talk with someone more experienced.

Try reformatting it FAT32 instead of NTFC
Sent from my DROID BIONIC using xda premium

dshedt and
tbird22tg said:
Try reformatting it FAT32 instead of NTFC
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
already formatted in fat32..I think that internal sd is broken..no way to access or repair it..or I dont know what to do..

Last update: I'm trying to use adb commands to see if I can do anything before going to RMA...adb correctly see my device connected (also can go in apx mode) but when I try to type "adb shell" it says "adb failed -exec '/system/bin/sh' failed: No such file or directory (2)...any suggestion?

I also got a brick at T101G (B90) :crying:
I only available APX interface, nvflash does not help.

[Q] Install Errors: [Kitkat] CM11 Android 4.4 for the Droid X

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

Need help with 2012 N7 that is kind of bricked!

OK so I know there is A TON of info on these forums.
I searched around but I did not see anything similar to my situation.
If there is a thread, please just link it and ill delete this thread.
Basically I had rooted my N7 back earlier this year and had a custom rom as the 5.0 OTA made my N7 run like crap.
It was fine until the last few months, it got REALLY slow. I didnt update it, or mod it other then flashing the roms.
So I set out to get a new rom. I figured id try the 6.0 AOSP rom.
DL it, as well as the GAPPS and tried to install it. All I ever got was a continuous error saying, "setup wizard has stopped".
Searched some more and saw that someone fixed it by installing a bare bones GAPPS and then WIPING Dalvik and cache immediately after flashing GAPPS.
I did this and no change. Still an error.
So I noticed that when I was in Windows, my N7 showed as having 5+/- gigs free out of 13gb.
So I figured let me wipe this whole thing clean and start fresh.
BTW- this has all been done with Wugfresh toolkit.
So I went ahead and erased/ formatted and planned to return to stock and then re-root and flash a 4.44 rom as I saw that on the grouper nothing over 4.44 works great and all I want is a stockish N7 that stays fast and works 100%.
Well now all I get is the Google scree with the Unlock icon and a green start icon and when you try to go into bootloader it says booting failed in upper left corner.
Any ideas hahaha.
Thanks!

I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk

twics said:
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I had the latest twrp recovery, I think 2.08 ?
I can't seem to get to the recovery screen.....only the bootload screen.

Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk

twics said:
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
NO!! Your device is not toast if it powers on then it should be recoverable, my advice forget WugFresh check out this page on how to get TWRP installed> https://twrp.me/devices/asusnexus72012wifi.html for latest twrp recovery, on this page you will find info how to get ADB running properly, once you have Twrp recovery installed try this Rom it is stock Lolliopop and runs great better than previous ones http://forum.xda-developers.com/nexus-7/development/rom-t2931064
---------- Post added at 02:00 PM ---------- Previous post was at 01:54 PM ----------
Please let me know how you get on. also if you get TWRP installed wipe everything apart from internal storage before install Rom.

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk

twics said:
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.

1993cb7 said:
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
Click to expand...
Click to collapse
OK Im back. Roughly an hour and a half. Not bad.
So what I did(if you're stuck on the bootloader screen like me)
Updated to the latest version of Wugfresh.
Made sure it updated all of the files it needed etc.
I then went through the process of uninstalling and reinstalling the drivers for ADB etc. I actually had an issue with it not detecting my device so it recommended installing the generic Google drivers....I did that.
Even after doing that, when I would check ADB connectivity it would say no devices found. I remembered that sometimes it would still communicate with the device even though it said nothing was found. I decided to do a fastboot format under advanced utilities because I knew that i erased it previously and I think that is where I ran into problems.
Sure enough adb found my device and formatted the bootloader no problem. I then continued with the restore to stock/w boot loop function and had patience...it took FOREVER to load the system image and then it took like 10 minutes to reboot but it did and I have a fully functional device right now.
I logged in and turned USB debugging on and re-locked the device. I then did a system wipe from inside the system and will sell it tomorrow.
So have faith, its not over till its over.
and p.s. I changed the USB port that I was plugged into. I have a USB hub that I usually connect too but I figured id connect directly to a USB port on the machine. Not sure if that helped, but people recommend it anyway.