[Q] Please help me out of my own stupidity - Eee Pad Transformer General

Hello, I am a pure noob here, and one to android in general.
I bought a TF101 a while back, and while complaining to a friend (over xbox live) that it was a bit slow at times, he told me to root it and install cyanogenmod.
So I started looking into it, and thought it looked well within my capabilities to do, so I went for it. I followed the instructions at the cyanogenmod wiki.
Wthout knowing the issues I was going to encounter before encountering them, I really didn't know what pitfalls to research, and thought I'd be fine if I just followed the instructions above.
So, I used Wheelie to root and installed CWM 6.0.1.3 using NVFlash. A little trouble, but I got through it, so far so good.
Here is my problem, in the instructions when they refer to the SD card, I took that to mean the microSD card. So now, when I go into CWM, I cannot install the rom from my external storage (CWM does not support this).
I thought I had created a backup of my current installation, but apparently, I failed at that as well.
And of course, since the instructions above, or the instructions on the Wheelie page don't mention it, I didn't enable debugging through USB before doing all of this.
So now, my tablet does nothing unless I access it with Wheelie and use NVFlash. Otherwise, it does nothing when i turn it on. I've looked around this forum and others this morning for about 2 hours and have not found any solution that will work for me. They all involve a backup on the internal SD storage (which I don't have) or using ADB (which I can't do without USB Debugging being enabled).
If any of you more knowledgeable about this stuff could take pity on my, I would appreciate any help.
Is my tablet now useless?
Thank you!

try this method at least you can go back how your tablet was before...let me know
http://forum.xda-developers.com/showthread.php?t=1688012
curmud6e0n said:
Hello, I am a pure noob here, and one to android in general.
I bought a TF101 a while back, and while complaining to a friend (over xbox live) that it was a bit slow at times, he told me to root it and install cyanogenmod.
So I started looking into it, and thought it looked well within my capabilities to do, so I went for it. I followed the instructions at the cyanogenmod wiki.
Wthout knowing the issues I was going to encounter before encountering them, I really didn't know what pitfalls to research, and thought I'd be fine if I just followed the instructions above.
So, I used Wheelie to root and installed CWM 6.0.1.3 using NVFlash. A little trouble, but I got through it, so far so good.
Here is my problem, in the instructions when they refer to the SD card, I took that to mean the microSD card. So now, when I go into CWM, I cannot install the rom from my external storage (CWM does not support this).
I thought I had created a backup of my current installation, but apparently, I failed at that as well.
And of course, since the instructions above, or the instructions on the Wheelie page don't mention it, I didn't enable debugging through USB before doing all of this.
So now, my tablet does nothing unless I access it with Wheelie and use NVFlash. Otherwise, it does nothing when i turn it on. I've looked around this forum and others this morning for about 2 hours and have not found any solution that will work for me. They all involve a backup on the internal SD storage (which I don't have) or using ADB (which I can't do without USB Debugging being enabled).
If any of you more knowledgeable about this stuff could take pity on my, I would appreciate any help.
Is my tablet now useless?
Thank you!
Click to expand...
Click to collapse

kokobsb said:
try this method at least you can go back how your tablet was before...let me know
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Wow, thanks so much. This worked! I thought it was done for.
Thank you!
Is there a thank 100 times button?

Ok, so I used this tool, and put a stock ICS on the tablet I downloaded from Asus. As I was setting everything back up, content to just have my old tablet back, it froze on me. I restarted, the tablet, and now it won't load again. It gets stuck at the EEE pad screen. Worse, when I turn it off, it automatically turns right back on.
I can manage to get this to load in recovery mode (vol down; I don't even need to hit the power button because it just automatically turns on) but I can't get it to boot up in APX for me to flash and restore again. I've tried several times, but there doesn't seem to be enough time to plug the cable in between reboots for it to not boot up regularly.
When I boot up recovery mode, it freeze there, unable to load any recovery tools.
Any more ideas? The help is much appreciated.

hmmm interesting try to reflash a recovery on it via this tool
http://forum.xda-developers.com/showthread.php?t=1681155
curmud6e0n said:
Ok, so I used this tool, and put a stock ICS on the tablet I downloaded from Asus. As I was setting everything back up, content to just have my old tablet back, it froze on me. I restarted, the tablet, and now it won't load again. It gets stuck at the EEE pad screen. Worse, when I turn it off, it automatically turns right back on.
I can manage to get this to load in recovery mode (vol down; I don't even need to hit the power button because it just automatically turns on) but I can't get it to boot up in APX for me to flash and restore again. I've tried several times, but there doesn't seem to be enough time to plug the cable in between reboots for it to not boot up regularly.
When I boot up recovery mode, it freeze there, unable to load any recovery tools.
Any more ideas? The help is much appreciated.
Click to expand...
Click to collapse

kokobsb said:
hmmm interesting try to reflash a recovery on it via this tool
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
Thanks again for your help, but I got it another way. Holding volume + and power got the tablet to shut off and stay off. From there I was able to use the first tool you gave me pointed me to again, restored it all again, re-installed the stock OS.
From there I reflashed, re-rooted and all my issues with installing cyanogen went away. I'm not sure what went wrong the first time I tried to do this, but it all went away and installed with no issues.
Thanks again for all your help. Without it I'd have no tablet anymore.
Thanks!

yeah happy to hear you have your tab back ...i am using android revolution hd rom can you tell me which built of cyanogen your using and if you are happy with? cuz i tried a jb rom i hated it...
curmud6e0n said:
Thanks again for your help, but I got it another way. Holding volume + and power got the tablet to shut off and stay off. From there I was able to use the first tool you gave me pointed me to again, restored it all again, re-installed the stock OS.
From there I reflashed, re-rooted and all my issues with installing cyanogen went away. I'm not sure what went wrong the first time I tried to do this, but it all went away and installed with no issues.
Thanks again for all your help. Without it I'd have no tablet anymore.
Thanks!
Click to expand...
Click to collapse

Related

Don't Try to Partition with Rom Manager.

If You try to partition with Rom manager it partitions the internal sd and you will brick your phone. Your screen will be black with only the capacative buttons glowing. This brick is possibly the more annoying ones where you have to flash your phone twice. If you have this problem don't panic like i did.
*REMOVING EXTERNAL SD CARD MIGHT IMPROVE ODIN CHANCES OF WORKING*(Thanks Hoey2011 for mentioning this)
Step 1: Download all files from this thread
http://forum.xda-developers.com/showthread.php?t=734475
PUt them in a safe spot you will need them for later.
Step 2: Download files from this thread
http://forum.xda-developers.com/showthread.php?t=740558
Step 3: HAVE ODIN OPENED FIRST!!(This helped it detect my phone for some reason)Get phone into download mode. The easiest way to do this is pull out battery from phone. Then plug phone into usb connected to computer it will have the battery sign. Hold volume keys and power button when the screen goes black let go of power button. You will be in download mode if Odin doesn't detect it unplug usb and replug it.
Step 4: Once Odin has recognized your phone set the pit file and .tar file FROM EUGENE'S 2.2 THREAD. NOT THE FIRST LINK THE SECOND LINK. Then click start. And follow all the directions on his thread.
Step 5: Once you have flashed that rom you put your phone in download mode again and set up the pit and .tar file for Stock 2.1. After you finish flashing it your phone should be saved!
Thanks to Eugene373, justanothercrowd and anomalous3(for being patient and helping me out when I had this problem) And to anyone else that helped me solve this problem.
Thanx for being the guinea pig. Glad you got it back working.
Yea It was a ***** tho. Spent at least 4 hrs fixing it. But glad its working
Wow that sucks well thanks for the write up.
I was in the same boat as you and as I was downloading 2.2 to try I found your thread. Works like a charm! Thanks for the info on this. I guess I shouldn't read threads backwards from now on, huh?
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
ok, so i continued my use of the search tool here at xda and found my answer
I had my MicroSD card in my phone, hadn't even thought to remove it. I have moved past the cache.rfs file and am now waiting to see the results....
IT WORKED OMG OMG OMG
Xda forums almost ruined my phone, then brought it back from the dead
god i love equlibrium
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
I did exactly this and I was so frustrated that I sent my phone back to tmobile and just purchased a new one. I don't know about yall but if there are two storage points (internal and external) there should be an option for both in default recovery because when I tried to partition the external sd card *in which i was able to execute on my nexus one* it was very easy but because I use clockwork recovery and did a rom backup, i guess the backup zip wasn't safe because I received the same results as you. There should be 2 options to choose from that says *internal storage, External SD Card* why make things difficult? lol
The manufacturers need to be a little more intuitive.
*this is my opinion*
zDisturbed1 said:
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Koush said:
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Click to expand...
Click to collapse
I haven't tried partitioning, but the card's /dev/block/mmcblk1p* entries are there and I can mount them. That's how the dc2ext hack works. It mounts /sd-ext and /data to do the copies and it does it in recovery.
hoey2011 said:
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
Click to expand...
Click to collapse
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
brandnewsimmy said:
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
Click to expand...
Click to collapse
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
hoey2011 said:
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
Click to expand...
Click to collapse
I forgot to mention to do that. I did that with mine as well. Taking out the sd card increases success. Thanks for mentioning it.
Sent from my SGH-T959 using XDA App
farrisizdaman said:
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
YEa I guessed as much thats why I was trying not to "flame" and to be informative you are a victim of exactly what I am talking about. Because so many people throw around the word brick anytime anything goes wrong not only is it losing its meaning but people are also getting confused.
This does work, it took me about 7 hours last night to fix it.
I will say if it does not work then keep trying.
My flash kept freezing on the froyo rom and would not finish, so I actually had to try and flash the full captivate stock rom (search the captivate forum) it froze but afterwords it let me go throught the whole flash process with Eugenes 2.2 rom, then flashed right back to 2.1 no prob.
I will also say that if you are on a x64 system then go find a x86 (32 bit) system. I dont know why but it just works better.
So if it doesnt work then do this:
1. Make sure you are on a 32 bit system.
2. Flash a Full Rom from the Captivate forum. (It has a more to it I believe, changes the system maybe?)
3. If it freezes that is ok. Flash the 2.2 rom. (might need to do it a couple times)
4. After successful flash then go to stock.
This needs a sticky!!!!!!!!!
I just did this. Wish I would have seen this thread first!
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
tsnow247 said:
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
Click to expand...
Click to collapse
After fighting with it I found out this worked best for me:
Battery out
Plug in USB cord to the phone and PC
Hold Vol up and down
Put the battery in
Phone should boot right into download mode.
Also, I found you should have Odin open FIRST before you do this. If I didn't I would have constant issues with Odin hanging.

Help! Droid 2 stuck in boot loop.(solved.)

Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks

[Q] Can you help a brother out?

I will post the long version here, mainly because I have nothing better to do.
Here is the situation. I bought a NC about 6 months ago. I rooted it using Auto Nooter. I have no idea what ROM I installed to be honest. I'm very much a novice at this. And I'm quite stupid to boot, I might add. It has worked relatively ok since then. The ROM seemed a bit buggy and I had some initial troubles with constant reboots, in addition to some basic things not working and way bogging the thing down, but in general it was ok. I haven't used it much since unless I was traveling.
Today....I was traveling. Traveling to BFE. As such, I decided to bust out my trusty NC and download a new book while I was waiting for my flight. I did so, and something went a bit haywire. It seems that somehow, without prompting, the device has restored itself to the stock B&N ROM (1.1 maybe?). Yet - the Android OS is still there. For example I can click on my task manager app in the lower left corner of the homescreen and it shows that all of my apps are running and I can even switch to them. But my homescreen is defaulted to the B&N one showing my eBooks and I can't figure out how to get my Android launcher back. I have tried to reboot and it does the Droid boot up but reverts to the same B&N home screen.
I was thinking about trying to update to a new ROM since it had been awhile and I figured there must be something better/more stable out there now - Honeycomb or whatever. I guess this is the kick in the ass that I needed.
So now here I sit in a hotel room in BFE. There are no restaurants open past 9. There are no bars. There IS a Super Wal Mart but I think I'm gonna pass on that.
I figured I would look into this. Where to start? Should I re-set this thing to stock and then just pick a new ROM and re-root? Can I do any of this without having a SD card slot in my laptop - just using a USB cable? Will I lose any eBooks that I downloaded?
I await your sage advice.
rooting actually means gaining super user access to the current android rom. B&N, i believe is Froyo, so you did not install any rom so to speak. you were probably just rooted.
I think the issue is with the launcher and not that it is back to stock. What happens when you long press on the home screen?
If you plan to do anything, you will definitely need an sd card reader.
If you autonootered, then you were running stock, but rooted. With a custom launcher replacing the stock launcher, it sounds like.
At any rate, you were probably hit with the automatic update to B&N 1.2 (which is Android 2.2, iirc.) You almost certainly aren't rooted anymore, but it may allow you to run any apps that you already had downloaded, just from the stock app launcher.
When you get an SD card reader, you can check out Manual Nootering. It's basically the same as the old Auto Nooter, but for B&N 1.2. If you change the rom entirely (install CM7) or just run a different rom from an SD card, you'll avoid having B&N overwrite your root access in the future.
Thanks for the responses. I believe that you are correct. I actually was running 1.0.0. I used auto-nooter to root the thing and had it working with a custom launcher. I don't think it updated to 1.2. In fact I know that it didn't update to 1.2. I am trying to get it to do that right now.
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
I could Super Wal Mart tonight for a SD card reader if I'm feeling frisky.
I've got all kinds of problems.
I went to update to 1.2 from 1.0. I removed my SD card and erased and deregistered device. I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Any advice?
I'd do a full factory reset, then try the update to 1.2 again.
A couple of things about the 1.2 update -- do not unzip the update file or rename it. Just drop it as-is into the nook. And make sure to eject the nook from your computer and unplug it.
Thank you aka. I got it to take. I am now at 1.2. Now back to square 1(.2). Any help on this?
Baboontyme said:
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
Click to expand...
Click to collapse
Baboontyme said:
I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Click to expand...
Click to collapse
ETA: lol, congratulations! I guess just skip to that link at the end.
I'd agree with akaCat that you should do a factory reset, BUT you can only do that if you still have the stock recovery utility, and it seems possible that you do not. Try to get the NC to reset by interrupting the boot 8 times. If it doesn't work, you may have installed ClockworkMod Recovery on your Nook Color in place of the stock recovery utility. You may have done so while rooting, or later from the ROM Manager app, perhaps even by accident.
Have you attempted to boot to recovery by holding down "n" while you power on the device, and continuing to hold power + n for about six seconds (1-one-thousand, 2-one-thousand, etc), then releasing both? If so, do you get a factory reset dialog (series of yes/no options) or a longer menu including items like "mounting and storage" and "flash zip from sd card?" If you get the longer menu, then that's ClockworkMod Recovery, and neither the 8-failed-boots-reset nor the automatic update are going to work.
If you do have ClockworkMod Recovery, don't do anything yet. Hopefully somewhere on the screen it tells you the version number, in the format 3.0.x.x. Just let us know that version number and power off the NC.
If you still have the stock recovery utility, then do the factory reset, boot into the stock OS, connect USB, drop the update file straight on the Nook (not in any folders), safely remove the NC from your PC, and let it sit. Hopefully it will reboot itself.
If not, the next step is probably going to involve preparing a bootable ClockworkMod SD and manually installing a CWM-compatible version of the update, or of a different ROM. This article may help you wrap your head around the different options: http://quinxy.com/guides/how-to-pick-your-nook-color-operating-system-and-install-options/
ETA: lol, congratulations! I guess just skip to that link at the end.
Thank you, Tao. I seem to be a bit stuck, though.
I'm at 1.2 stock. I was able to reformat and erase my sd card. I went to load the .gz image onto the card (for CM7, per instructions here http://forum.xda-developers.com/showthread.php?t=1000957) and I also loaded the nightly build. Then inserted card into NC and booted. Nothing.
Any idea what I'm doing wrong? Should I unzip either file?
One thing that might/might not matter....when I went to eject the SD card from my PC, I wasn't given that option so I just pulled it.
One more thing.....the instructions at the link above instruct you to "write the image to your SD card" but then go on to say "eject the SD card" and then further "insert the uSD card into your computer"
Huh?? Isn't it all on the same card? Why do I need two different cards? What am I missing?
This blog breaks down the same process a little more step-by-step, with videos: http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html
You can skip the long preamble down to "Ready? Let's get started."
You do need to unzip the disk image, and write it to the SD using a program like Win32DiskImager or WinImage. It's also definitely a good idea to safely eject the SD card from your PC.
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Can someone also tell me how to access the book I just purchased and was in the middle of reading? Do I have to go somewhere and re-download?
Baboontyme said:
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Click to expand...
Click to collapse
I should add that though I can get CM7 to boot, I never get "The Power of Reading". It's just kind of a flash.
That's all normal--verygreen had to make a new uboot, which no longer shows "The Power of Reading" and also flies through a recovery boot so fast you could miss it. If gapps didn't install, just make sure the .zip is still in the boot partition and keep trying. I'm pretty sure holding power > reboot > recovery boot works now from within CM7, but I would go into Settings>Accounts and try to sign in to Google before assuming it didn't install.
If the book was a B&N purchase, once you have the market working, just install the Nook app and sign into your account, and you should be able to re-d/l the book, possibly even still synced to where you left off.
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
btw, you can also boot into recovery through rom manager, its easier.
Baboontyme said:
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
Click to expand...
Click to collapse
You can overclock: http://forum.xda-developers.com/showthread.php?t=925451
Just make sure you grab the version for SD, and install it just like gapps, then set clock speed via CyanogenMod Settings>Performance>CPU
boxcar8028 said:
btw, you can also boot into recovery through rom manager, its easier.
Click to expand...
Click to collapse
Easier than holding power a sec, poking "Reboot," then "Reboot to Recovery?"
Really, it's about the same either way, depending how handy ROM manager is on your system.

[Q] Bootloader Ics v3.14.8 + Recovery Twrp v2.1.3, after you hit install?

Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution

[Q] Recovery Rebooting Issue

Hello,
I sure could use some help here! I just upgraded to BajaROM 16 in my stock rom slot. All was fine until I did a boneheaded thing. I wanted to go into recovery to attempt to install another ROM in slot 1 so by mistake I clicked on "recovery" in the drop screen that also has the restart and shut down buttons. Now I appear to be in a endless loop trying to find recovery. I have no idea what to do now. I tried doing the three button approach but nothing happened. I have pulled the battery and waited a few minutes but as soon as I re-start the phone, I get that damn "Recovery Reboot" message again on the top left side of the screen.
Any ideas?
Thanks!
I'm in the same boat, phone has been constantly rebooting for the last 12 hours and I can't figure out how to make it work again...
same boat here.
edit...
Resolved...
I have encountered this as well. I fixed it by Odin flashing the modem back to the phone. Once flashed, it rebooted and I had Safestrap and my rom back. Just be sure you flash the right modem file as the wrong one will brick your phone. I have done that in the past as well.
Bizack said:
same boat here.
edit...
Resolved...
Click to expand...
Click to collapse
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
Whoa, Odin wont recognize the phone in download mode?
vol dn + home & Power?
You need to not use USB3, switch USB ports, change cables, if your computer wont recognize switch computers.
Open up Kies3 and re-install drivers.
Many options, try them all, don't give up. It your shot won't even turn on, then take that **** back!!!
What IO did to achieve salvation...
I flashed NC4, Rooted using towl root, then busy box and Safe Strapped flashed the NC2 kernel and bamm(no relation) back on Baja16....
(there is a process, please don't follow the steps above, go here...)
I was in the same boat...
tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
I was also rebooting into recovery mode over and over again after my first boot up of the recent Baja and rebooting into Recovery after updating to the new version of SS.
The only thing I could do was pull the battery and it would do again. I read the above about updating the modem, but unsure what that was, I tried rebooting into download mode again. From here, instead of hitting UP VOLUME to continue, I hit DOWN VOLUME and low and behold, I got the baja flash and it booted up my phone again.
PHEW!
Just thought I'd share what worked for me...
what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?
downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on
BigHoss3 said:
what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?
Click to expand...
Click to collapse
BigHoss3 said:
downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on
Click to expand...
Click to collapse
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...
Bizack said:
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...
Click to expand...
Click to collapse
It took some work but I got it booted back to the stock rom
I also had problems getting Odin to see my phone. In my case I just needed to unistall the USB drivers bundled with my phone and install the latest drivers FROM Samsung's website.

Categories

Resources