[Q] [+Problem] Can't boot into CWM Recovery - Nook Color Q&A, Help & Troubleshooting

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.

Related

Highly doubting anything can help me unbrick my Nook Color[SERIOUS]

I've spent about 20 hours total trying to unbrick my nook color.
It started when I was (happily) running CM7, but I wanted to have HC preview 4 to use at times, so I decided to dual boot it. I went in to dual boot it, and it had an error. So I flashed the remove dual boot zip to reset it, then I went looking for an answer. I find that it looks like my media partition somehow got corrupt, so I go into ADB to see if I can get that working. From within adb I run "adb reboot recovery", and then it never turned on. Freaking out, I searched for an answer. I got it booting into CWM on SD, and Nookie Froyo SD. I've tried all the unbricking methods, even the advanced one that requires DDing boot.img and system.img. I got into adb from recovery and found that my partition table - I had none. So I find out how to fix that, and I do. Fixed it properly infact, looked exactly like it should. So then I go and DD boot.img and system.img, remove the SD, unplug from power, and try to boot into recovery, no luck. Tried a normal boot, no luck. I've done this multiple times. I think it has something to do with the boot partition, I verified it had contained the proper files(u-boot.bin, uImage, etc.), it was marked as bootable, but it wasn't booting.
I held down the power button for 25 minutes just to confirm without a doubt it wasn't(I watched a show while waiting, unfortunately it was my figure holding it down, not tape).
Nothing I tried fixed it.
I think I may have been one of the first to "actually" brick my nook.
Any tips on what I can do to try to unbrick it? Ask me questions, have me acquire data, I don't care.
I have access to adb in recovery, and adb connected wirelessly via nookie froyo sd bootable(for some reason it won't let me use adb via usb).
I apologize if this is in the wrong section.
Also, before you go saying that this is pretty much a repost of other threads, I looked at multiple threads with people trying to fix their nook, threads with 60 pages, read all of them. No one had a problem like mine.
If you are willing to put CM7 on the internal memory, follow the instructions here: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Make your you use the latest version of CWR (v3.2.0.1) Once you have everything working properly, reformat the card to use as storage. Better, keep it as is in case you ever have to preform a new installation and buy a new card for storage. You will need one to properly use CM7 to full advantage.
patruns said:
If you are willing to put CM7 on the internal memory, follow the instructions here: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Make your you use the latest version of CWR (v3.2.0.1) Once you have everything working properly, reformat the card to use as storage. Better, keep it as is in case you ever have to preform a new installation and buy a new card for storage. You will need one to properly use CM7 to full advantage.
Click to expand...
Click to collapse
I was hoping doing what you said would work - but it didn't.
I follow this guide(http://mrm3.net/nook-color-how-to-blue-dot-nook-color/) to get the partitions reformatted properly then installed it.
Glad the site still was able to help you with your issue....
It didn't help. I already followed that guide. Their is one like it here.
Sent from my VM670
tannerzion said:
I was hoping doing what you said would work - but it didn't.
I follow this guide(http://mrm3.net/nook-color-how-to-blue-dot-nook-color/) to get the partitions reformatted properly then installed it.
Click to expand...
Click to collapse
That is the same site I sent you to, only a different page.....
patruns said:
That is the same site I sent you to, only a different page.....
Click to expand...
Click to collapse
No, I just didn't have to found the one on xda because there was one on that site. No need to fight.
Sent from my VM670
Since you said "trying to unbrick" then why not try to reverse back to the original state before installing/running any other ROMs
votinh said:
Since you said "trying to unbrick" then why not try to reverse back to the original state before installing/running any other ROMs
Click to expand...
Click to collapse
Tried that.
Sent from my VM670
tannerzion said:
Tried that.
Sent from my VM670
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=kOypmSCEHbc
Go to my youtube page.
Download my ROM by clicking more on my description.
Extract and burn to a SD card with WinImage or something.
Seems like you need to fix your boot partition. Hold the power button down for 15 seconds with no USB plug in the nook. Put your recovery SD in the nook and hold power for 5 seconds you should boot to the SD card. Flash the “repartition-boot_emmc-800mhz-stock.zip” if you want the 800 MHz stock kernel and reboot the nook. If you want the 1.1 GHz Kernel flashed then use “repartition-boot_emmc-1.1ghz-froyo_setboot.zip”.
Once you flash that go ahead and flash my rom just for ****s and giggles to see if you can boot into it. Enjoy. Let me know if I helped.
If this doesnt work you can always DD your way to a new partition. Example below but lets do what I put up top first.
dd if=/dev/block/mmcblk0p1 of=/sdcard/xe.nook.color-froyo-v2.2-boot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/xe.nook.color-froyo-v2.2-data.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/xe.nook.color-froyo-v2.2-system.img
Well, I'm already processing a return... But if I run across this problem on my new nook, I'll try that.
Sent from my VM670
tannerzion said:
Well, I'm already processing a return... But if I run across this problem on my new nook, I'll try that.
Sent from my VM670
Click to expand...
Click to collapse
Return it and try CM7 normally installed to EMMC. Dont **** around with dual boots and all this other crap
When you get your new one in, and if you decide to put CM7 on EMMC, just leave it as CM7 alone.
Shame you sent it back before we could work it out, I was looking forward to trying to fix this - but I can imagine just how frustrated you have been with it and I don't blame you. Probably at the end of your rope and in your place, if I could have gotten B&N to exchange it, I would have too.
Because the Nook Color boots from the SD first, you can always just install whatever else you want to play with to a MicroSD card and run it that way.
Verygreens sd card prep thread is a fantastic first step in this regard. (click "SD Install" in my sig to get to it)
I personally still have my Nook Color stock on EMMC (with B&N official updates) and run my CM7 and other installs from the sdcard. Just make sure it is a SanDisk card and you'll be good to go. (also links in my sig to find out why SanDisk if you're curious)
The benefit to running from the sd-install, especially on possibly unstable ROMS, is that if it doesn't work you simply remove the card to get your device back - instead of having to run recovery on your device.
The latest stable release of CM7 is absolutely fantastic on the Nook Color, and i'd highly recommend it as your daily driver.
Blue6IX said:
When you get your new one in, and if you decide to put CM7 on EMMC, just leave it as CM7 alone.
Shame you sent it back before we could work it out, I was looking forward to trying to fix this - but I can imagine just how frustrated you have been with it and I don't blame you. Probably at the end of your rope and in your place, if I could have gotten B&N to exchange it, I would have too.
Because the Nook Color boots from the SD first, you can always just install whatever else you want to play with to a MicroSD card and run it that way.
Verygreens sd card prep thread is a fantastic first step in this regard. (click "SD Install" in my sig to get to it)
I personally still have my Nook Color stock on EMMC (with B&N official updates) and run my CM7 and other installs from the sdcard. Just make sure it is a SanDisk card and you'll be good to go. (also links in my sig to find out why SanDisk if you're curious)
The benefit to running from the sd-install, especially on possibly unstable ROMS, is that if it doesn't work you simply remove the card to get your device back - instead of having to run recovery on your device.
The latest stable release of CM7 is absolutely fantastic on the Nook Color, and i'd highly recommend it as your daily driver.
Click to expand...
Click to collapse
I wanted something on the emmc, and my microsd card is to slow to consider booting from it. I'll probably get a better one or just use my current one, and install honeycomb on that.
xboxexpert said:
Return it and try CM7 normally installed to EMMC. Dont **** around with dual boots and all this other crap
Click to expand...
Click to collapse
I had CM7 as my normal install, I just wanted to try honeycomb and my sd card was to slow to consider booting from it.
There's an image around these forums somewhere that lets you dual-boot Phiremod and HC preview on the SD (you just flash it to the SD and go).
It's always safer to play with SD new boots, since you won't hurt your EMMC installs.
With that really said -- the HC previews on the NC are ... not really worth playing. There's no hardware acceleration - so that are abysmally slow. Really bad. You'll try swiping the home screen and go "ugh, back to CM7".
Quite honestly, there's nothing better for us than CM7 on SD or EMMC. Phiremod is just candycoating on CM7 anyhow - and nobody's ever come up with a ROM for us that isn't just fiddling around with a base CM7 or a themed layer on top of it.
What we get from our CM7-Encore installs is pretty much what we want. Theme it all you like - but in reality, nothing else beats it.
youre in luck...my Bricked nook is not getting returned...
i have a bricked nook ...had cm7 on it for 1 1/2 years ..thought i would put cm10.1 on ...to emmc... everything went well installed cm10.1 then gapps ...forgot to install cwm or twrp...oops ...been bricked ever since ..tried pulling battery ..left it disconnected 8 hours ..plugged battery back ...still unresponsive ...tried tips section from leapinlar to no avail ..tried 8 boot method nada!!...never even see a backlight flash ..battery shows 5volts so its not dead...any help ?? anyone??...thanks
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
omap3630 only sign of life .. for less than a second when power button is held down for say....10 seconds...on the USB to the pc..of course no booting happens needless to say..
bodecove said:
i have a bricked nook ...had cm7 on it for 1 1/2 years ..thought i would put cm10.1 on ...to emmc... everything went well installed cm10.1 then gapps ...forgot to install cwm or twrp...oops ...been bricked ever since ..tried pulling battery ..left it disconnected 8 hours ..plugged battery back ...still unresponsive ...tried tips section from leapinlar to no avail ..tried 8 boot method nada!!...never even see a backlight flash ..battery shows 5volts so its not dead...any help ?? anyone??...thanks
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
omap3630 only sign of life .. for less than a second when power button is held down for say....10 seconds...on the USB to the pc..of course no booting happens needless to say..
Click to expand...
Click to collapse
And bootable SDs do not work? It will not even turn the screen on unless there are valid boot files in the boot partition or on a bootable SD.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
And bootable SDs do not work? It will not even turn the screen on unless there are valid boot files in the boot partition or on a bootable SD.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
tried both from ,,A 10 post .... New Bootable CWM Recovery SD (v5.5.0.4 and now v6.0.1.2)
....tried both versions also 1gb_clockwork-3.2.0.1-eyeballer version ...win32diskimage ...hp format utility also formatted with sdformatter
bodecove said:
tried both from ,,A 10 post .... New Bootable CWM Recovery SD (v5.5.0.4 and now v6.0.1.2)
....tried both versions also 1gb_clockwork-3.2.0.1-eyeballer version ...win32diskimage ...hp format utility also formatted with sdformatter
Click to expand...
Click to collapse
Well, unless you can get a bootable SD to boot, you are toast.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Well, unless you can get a bootable SD to boot, you are toast.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
any chance I am missing some simple step...
---------- Post added at 09:36 PM ---------- Previous post was at 09:14 PM ----------
bodecove said:
any chance I am missing some simple step...
Click to expand...
Click to collapse
...what are your thoughts on making the sd cards with my linux(mint 14) laptop ...am I grasping for straws??

[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

ICS beta2+ roms can't be launched, not partitioning problem

Hey every1,
i got weird problem with all ics roms, even SD <
I can successfully install tytung beta1 rom and run it, but beta2+ roms and similar ones, and SD build all have same thing:
i have random freezes/stuck at bootlogo(it doesn't freeze, it simply continues to do the animation forever), only ONCE it booted, but since i needed kernel fix(for headphones) to apply - i restarted, and wasn't able to boot in successfully again. Now almost all the time i get freeze/reboot after ~5-10sec after i get into ics rom, SD build doesn't boot at all.
Partitioning problem? - have tried many partition layouts.(like 190/10,200/10,210/10,200/20,230/20,210/20 and so on, also with different bootloader partition size up to 8mb)
Also i have always used task29 and fully wiped everything and reinstalled from scratch, still didn't helped.
Also tried to boot with plugged in usb cable/without it or with/without memory card in.
Maby it's radio version problem, or don't know, what else can cause the problem?(radio ver:2.15.50.14)
Between i have created big cache/memory sometimes(up to 250mb partition/44mb cache) - and still it didn't worked fine :/ also tried different clockworkmod versions(3.0.0.5 and 5.something), magldr 1.13
p.s. i have europian hd2(not t-mobile)
or maby i'm partitioning it wrong? i change partition sizes inside flash.cfg and after i flash clockworkmod(i do task29 before that, and install fresh magldr), maby i should change somewhere else/more?
Also formatted memory card many times(sdformatter) and redownloaded roms, still same result.
p.s. tried ~3ics beta2+ roms(not sure mb even more), and 1sd rom
Edited:
forgot to mention, when phone kinda freezes(the boot animation/startguide for ics) - when i press physical buttons - the backlight appears and after that dims away as it does on every other android rom, so it kinda feels that rom isn't frozen, only the screen. Also sometimes after getting ics welcome screen - after ~5-10sec it gets back to bootloading animation and does it over and over again...
hey
I'm having the same problem did you figure it out I'm having same problems with ics and cm7
What has worked for me is 5/230/5. Im using tmous but that layout should work for your version.
Thanks
You are the man bro I cant believe it was something so simple
problem
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Youngmyster said:
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Click to expand...
Click to collapse
I am using the ICS beta 3 now, I have updated with every release and I didn't get this problem. It sounds like something crazy, you may just have to wait a little bit because ICS is still very beta... Check out HD2 Toolkit as well it makes it much easier flashing..
Wait, I didnt didn't see that you were having problems with cm7.. :-( I'm afraid I just wasted your time on my reply..
What Clockworkk mod recovery are you using?
And how are you transfering your data to your SD card?
---------- Post added at 05:15 PM ---------- Previous post was at 05:07 PM ----------
Try backing up your entire SD card, and then reformat it completely.
Then task29 and wipe everything.
I think you said you use magldr, since your having these problems try cLK
Use just a simple 220MB 5MB cache on HD2 Toolkit
Install ClockworkMod Recovery 5.0.2.6 as it is the newest one.
Transfer your zip file to your SD card using a card reader.
Install and see if ICS will boot.
Try that and see if it works. It should work.
Question. Do you have this same problem with any roms besides CM7 and ICS?
---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------
Don't forget when using cLk you download the main zip file for the rom, and then a separate zip for the cLK kernal..

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.

Help installing TWRP on MB525

Ok so here is a run down of my issues. Rooted my wife's mb525 via gingerbreak. Surprisingly every thing worked well didn't even realize it was a froyo phone. Not my problem is that I can't figure out how to manually install a recovery ie twrp so that I can flash roms. placed the zip on my sd card and then attempted to copy it to root via file manager but it won't work. As a result I can't see it in stock recovery. any help would be very much appreciated. Oh and I've searched the forums and the net and still can't find anything so please don't flame me.
jsteve01 said:
Ok so here is a run down of my issues. Rooted my wife's mb525 via gingerbreak. Surprisingly every thing worked well didn't even realize it was a froyo phone. Not my problem is that I can't figure out how to manually install a recovery ie twrp so that I can flash roms. placed the zip on my sd card and then attempted to copy it to root via file manager but it won't work. As a result I can't see it in stock recovery. any help would be very much appreciated. Oh and I've searched the forums and the net and still can't find anything so please don't flame me.
Click to expand...
Click to collapse
TWRP used to work like a charm on GB Roms. I've flashed multiple ROMs with TWRP and I find CWM still more reliable. Sometimes after wiping data + cache + dalvik TWRP will reboot, leaving you with a bootlogo loop and a device that can only be recovered by flashing SBF.
Use 2nd init v2.3. the app installs bootmenu + CWM v5 and it doesn't require an internet connection as of v2.3. Then you will be all set. With the defy, you cannot flash ROM zips via stock recovery; it only accepts Google signed zips.
Just figured this part out thanks to your help. Now to find a stable rom any suggestions? and for the mods i'm not asking about "the best rom" just want a stable one for my wife's phone that is stable and has good battery life.
jsteve01 said:
Just figured this part out thanks to your help. Now to find a stable rom any suggestions? and for the mods i'm not asking about "the best rom" just want a stable one for my wife's phone that is stable and has good battery life.
Click to expand...
Click to collapse
Man, that's difficult. I'm running NEGAN1911 v2.1, but the problem is that ROM has been taken down a long time ago. I'll see if I can't upload it to dropbox if you still want it. It's based on CM10 4.1.2, you can search it up on Google because the thread is still there.
If she doesn't care about GPU performance then maybe Quarx's CM10 is the best way to go. Also try ROMs based on Quarx's CM10 such as Mint and SJB. Epsy's CM9 with 2ndboot is still a fast and viable option.
No MIUI Rom I've tried is stable and bugfree, so if you're shooting for gingerbread ROMs, either use a stock 4.5.1 series sbf or CM7.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
jsteve01 said:
Ok so here is a run down of my issues. Rooted my wife's mb525 via gingerbreak. Surprisingly every thing worked well didn't even realize it was a froyo phone. Not my problem is that I can't figure out how to manually install a recovery ie twrp so that I can flash roms. placed the zip on my sd card and then attempted to copy it to root via file manager but it won't work. As a result I can't see it in stock recovery. any help would be very much appreciated. Oh and I've searched the forums and the net and still can't find anything so please don't flame me.
Click to expand...
Click to collapse
And why would we want to flame you mate? This is a perfectly good question; you've listed all the facts and your English is fine. Politeness is always appreciated.

Categories

Resources