Database Users

[Q] Wont go into recovery mode

I was trying to install a new kernel so I could overclock, and I could not get it into recovery mode. I tried the normal, turn off+hold volume down key+turn on, method. I also used the boot into recovery mode option from CWM (Acer Recovery)
I thought it may have something to do with my other software issues causing issue, so I did a master reset. It got everything back to normal, reloaded my info and backed up info, and installed rootcheck (which confirmed root and busybox) and superuser, and CWM, and have the kernel on my sd card. I tried booting into recovery mode again and it wont work
The error I get is the little tranlucent android dude with the gears rolling and then suddenly the gears stop and I get the warning sign, yellow triangle with exclamation mark.
Anyone know why this may be?

phoenixbennu said:
I was trying to install a new kernel so I could overclock, and I could not get it into recovery mode. I tried the normal, turn off+hold volume down key+turn on, method. I also used the boot into recovery mode option from CWM (Acer Recovery)
I thought it may have something to do with my other software issues causing issue, so I did a master reset. It got everything back to normal, reloaded my info and backed up info, and installed rootcheck (which confirmed root and busybox) and superuser, and CWM, and have the kernel on my sd card. I tried booting into recovery mode again and it wont work
The error I get is the little tranlucent android dude with the gears rolling and then suddenly the gears stop and I get the warning sign, yellow triangle with exclamation mark.
Anyone know why this may be?
Click to expand...
Click to collapse
Which kernal are you trying to install? Are you installing via cwm? What version are you running? Are you holding vol-key until after the Acer logo shows up and then keeping the vol rocker held until you see "booting recovery..."?
Have you successfully booted into recovery in the past?

thanks for the response. It seems the recovery image was corrupted or unknown according to cwm. i had to install the cwm one and it works just fine.

Great
phoenixbennu said:
thanks for the response. It seems the recovery image was corrupted or unknown according to cwm. i had to install the cwm one and it works just fine.
Click to expand...
Click to collapse
Glad you got it working

Installing Acer recovery installer does not install cwm. You have to select cwm from the list and click install recovery. Sounds like you figured it out, though.
Sent from my A500 using Tapatalk

A500 not switching to recovery
I also have a new A500 which already had 3.2 stock installed and it has never allowed me to go into recovery mode. I can use iconiaroot and get to a certain point with that but to install a custom rom, I haven't been able to. I want to so any ideas? I did however get to install the Acer_A501_0.017.01_PA_ATT which is about as much progress as I have got. My thought was to downgrade first then install a custom rom like Taboonay but I can't get into recovery. Please help.

bmills74 said:
I also have a new A500 which already had 3.2 stock installed and it has never allowed me to go into recovery mode. I can use iconiaroot and get to a certain point with that but to install a custom rom, I haven't been able to. I want to so any ideas? I did however get to install the Acer_A501_0.017.01_PA_ATT which is about as much progress as I have got. My thought was to downgrade first then install a custom rom like Taboonay but I can't get into recovery. Please help.
Click to expand...
Click to collapse
Why are you trying to get into recovery? What is it you are actually trying to do? If you are stock, then getting into recovery has little value, so it would help if we know what you're actually trying to do?
TD

Why recovery
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
Click to expand...
Click to collapse
I now know that recovery is locked by the system and one has to change the update.zip file. Right?

bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
I now know that recovery is locked by the system and one has to change the update.zip file. Right?
Click to expand...
Click to collapse
In order to flash a custom rom, you need to flash a custom recovery (in this case cwm) flashing custom roms with the stock Acer recovery isn't possible without out the update.zip being signed by acer.
Sent from my Desire HD using xda premium

bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
I now know that recovery is locked by the system and one has to change the update.zip file. Right?
Click to expand...
Click to collapse
Read through these forms and you'll get the information you need. But, before you can install a custom ROM you need to root(#) your device first. Once you get root then you have to install CWM which is a custom recovery. The Stock Recovery that comes installed will ONLY install updates signed by ACER therefore it is worthless. That's why you need something like CWM.
Hope this helps,
TD

Please do some reading mate as I can predict your future post....
You seem to have read through a bit of info skipping the main and most important parts. If you don't follow instructions TO THE LETTER your next post will be along the lines of "Help, I've bricked my A50*"....

Yes, thank you for replying, but no thanks. If your on here to help people, then help them. Learn some help desk manners.
If your on here to show your knowledge, then you have failed. The whole point of Linux is to help and contribute to a better os then what's available through retail. Careful or the point will get lost in translations.
Sent from my A500 using XDA

[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.

please help I need uninstall Clockwork, Android and MAGLDR

how can I uninstall clockwork from my HD2?
I know that I should flash original rom but I dont have one
Im from slovakia and I dont know whether I have T-mobile HD2 or normal HD2 and I dont know which official rom shoudl I installed
Is there any other option how to remove Clockwork from my phone ? .. I need to cancel partition.
I have installed: 1. MAGLDR
2. then I installed Clockwork
3. then I created SD partition
4. then I installed american android 2.3.7 through MAGLDR
the problem is that partition I created cant be used. It simply disapear and now I dont know what to do
I have been trying to install american android to my hd2 for 28 hours. I read many threads. Im tired and still I dont have my HD2 operating

The partition you created was from clockwork? if yes then it is ext4 and thats why windows can't see it.
Using magldr go to 8.AD recovery (press the call button)->Mounts and storage->mount usb storage. This way you can connect your phone to your pc and use your sd card to paste a rom. After that you can go back and install the zip from sd card (if you haven't installed a rom already)
Make sure you have partitioned your nand correctly using the rom developers requested values.
---------- Post added at 08:55 PM ---------- Previous post was at 08:47 PM ----------
If you want to revert back to original here are the official ruu's
http://forum.xda-developers.com/showthread.php?t=577717
But read everything before you do something.
PS:if your buttons are coloured (green phone- red phone) then propably you have the TMOUS version.

I've written a guide on this that may give you some useful information.
Kylew1212.memoryx2.com
Sent from my HD2 using xda premium

help, help me please?
Ok I have a htc no branded leo it has been switched from windows to android before.. one day i went to check it and what happens is it fails to load. now i think ok just update everything. so I do a task 29 and all. but now its stuck at the maglder at where the cwm is. it wont load into cwm at all
here is the specs so far
I installed 2.08, hspl then I did the radio, then i installed the maglder 1.13 and cwm ClockworkMod Recovery 150/5 and everytime it fails to open cwm help before i go crazy. now I noticed that the bootloader does not say coutulla on it at all
http://i1052.photobucket.com/albums/s450/tashkasru/IMAG0053.jpg
http://i1052.photobucket.com/albums/s450/tashkasru/IMAG0051.jpg
is what i end up with

I have written a guide that may have the information to fix your problem. I would recommend starting from scratch.
Task 29,
Install magldr or clk
Then cwm
Then our rom
Kylew1212.memoryx2.com
Sent from my HD2 using xda premium

@tashsru you have no modelID in bootloader, the top line shouldn't be blank. I suspect you may have corruption and may now not be able to flash.

oy
well that didn't help either now i have writing on my screen and it says failed to load recovery image this is what i ended up with...
http://i1052.photobucket.com/albums/s450/tashkasru/IMAG0055.jpg
---------- Post added at 04:52 PM ---------- Previous post was at 04:50 PM ----------
how could it be corrupted?

samsamuel said:
@tashsru you have no modelID in bootloader, the top line shouldn't be blank. I suspect you may have corruption and may now not be able to flash.
Click to expand...
Click to collapse
I didn't notice this.
I would recommend uninstalling hspl and installing win mobile just to make sure everything's okay.
Sent from my HD2 using xda premium

more
and I noticed this also in the bootlader.. like wtf?
http://i1052.photobucket.com/albums/s450/tashkasru/IMAG0056.jpg
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
so whats the idea now? any its like weird because this cell was running everything android on cm7 etc fine until i turned it on and then it was like it would not start up

- Install hspl 2.08
- Task 29
- Install clk
- Install cwm
- Install rom

that does not work tried it already

tashsru said:
and I noticed this also in the bootlader.. like wtf?
http://i1052.photobucket.com/albums/s450/tashkasru/IMAG0056.jpg
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
so whats the idea now? any its like weird because this cell was running everything android on cm7 etc fine until i turned it on and then it was like it would not start up
Click to expand...
Click to collapse
Ok so that looks ok, hmm perhaps I mistook the first pic (mobile so not checking again)
That's 2.08.0000 stock spl, it should be 2.08.hspl for android, perhaps that's the problem.

samsamuel said:
Ok so that looks ok, hmm perhaps I mistook the first pic (mobile so not checking again)
That's 2.08.0000 stock spl, it should be 2.08.hspl for android, perhaps that's the problem.
Click to expand...
Click to collapse
No, you didn't mistake. The first pic was hspl. But it was at least missing the cotulla line and maybe more.(not sure) the second pic is stock.
Just to get us up to date what have you tried now?
Sent from my HD2 using xda premium

I have tried going back to stock I have tried the hd2 took kit I have tried individual spls and mglders and cwm etc. nothing seems to get past the maglder part. the last deal said I had a 1EFATAL HIT 1 wtf is that? it happened when i tried to go into cwm.. this is weird.. and I now also notice that the volume up part of the volume button is not working either.
could i have a hardware fault issue now?

http://forum.xda-developers.com/showthread.php?t=945427
http://forum.xda-developers.com/showthread.php?t=611433
Sent from my HTC HD2

Hi,
I have also faced a similar situation and used HTC HD2 Toolkit.
See this thread.
Regards,
Vikas

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