Database Users

Noobie Rom ?

I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.

Sounds like a case of missing to clear the cache.
Did you wipe the cache partition and dalvic cache in the recovery menu?
After making major changes like switching between roms or kernels thats recommended and if not done might cause such an issue.

I did
I did do those steps, did the factory wipe/reset, wiped cache, wiped dalvic. Once I did those 3 steps, installed from zip, goes through the steps successfully, but when I reboot it just stay on logo. I read, it could take 5-10 min, but I have waited up to 20 and it doesn't move past that. Just see what I am doing wrong, as the 2 roms have both done that, and I have tried several times with both. Just have the stock rom with Touchwiz OTA upgrade from Samsung, and pershoots latest kernel. Thanks in advance.

bad zip file?
Is it possible the zip files are getting corrupt? Are you downloading them on your tab or on computer and transferring them over? I would also check to see if there are any errors when you flash.

Download from computer and transfer over. How can I if there are errors as once I install a ROM it just stays at the logo. After it starts to install it end with, i cant recall exactly, but it says success. Thanks in advance

In cwm when you flash there is some text readout. That is where some error messages could be seen. That text will be there before you choose reboot on the menu.

sounds like you've had some issues bro. if you do get fed up and need some help, just let me know and we can video chat through gmail or skype to get you through it and get you a custom rom.

slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Well first...are you rooted? Do you have Clockworkmod, Superuser, and Busybox?
Oh and congrats on your switch from Apple to Android

slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Maybe try in "reverse" order
Flash kernel back to stock - flash the rom you want - if that works then flash pershoots kernel
Just a thought

hy
i installed the overcome rom on my 7500, and i'm so entusiast!
Try it it's very easy!
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
i did it in recovery, do wipe data

Yes its is rooted, cmw, superuser, and busybox all installed. Installed both roms in recovery, hold volume down and power method. Just can't figure it out, I will do the reverse suggestion and report back later tonight or tomorrow.thanks everyone for the advice/help.

no erreor s after install, think task's says success or something to that effect.

Well it finally stuck, I knew it was going right as when it was installing system files, it took like 5 minutes, the other time I did it took like 30 seconds. As per Stinky73 went back to stock Kernel, and wipe data, clear cache partition, and wipe Dalvik Cache, Thanks a million Stinky73 u da man! HELL YEAH this Rock, it is so responsive, seems a hell of a lot smoother, and apps just snap open. Task you did one outstanding job. This is coming from a noob who has no idea how much work goes into these, I am sure a lot. So from a noob to an expert EXCELLENT JOB, love my Tab that much more!!!!! Thanks everyone for the help, I am one happy camper! Now another dilemma, I saw new versions: How do I install these now that I have Tasks650 installed and working? Do I have to do the same steps above, wipe data, cache, and Dalvik? And if so what do I do next, do I do the same: Also is the BOB_WOW_Fix installed using the same method as i read flashable, sorry for the noob question, just want to get it right.
1. install zip from sdcard.
2. choose zip from sdcard.
NEW!!!- Task650's V7.1
Once again... I forgot to add "Desktop UAstring to V7.1 so flash this update after you boot up V7.1 if you want it.

Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks

slice2011 said:
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
Click to expand...
Click to collapse
There's no complete fix for BoB and WoW, its a continuous work in progress.

bob wow fix
Are you taking about the fix task posted?
What I had to do was wipe cache first then flash the zip just like you did on the rom. And bobs your uncle.
Edit:
Oh ya I would reboot after each flash just to be sure.

So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.

slice2011 said:
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
Click to expand...
Click to collapse
All sounds very strange...is it definitely stuck on the boot screen? These things can take anything from 5-20 minutes on initial boot, there is no definite rule for that, seems to be device related in some strange way...how long have you left it?
I am really an OCD when it comes to upgrading and always backup (nandroid or whatever) then go back to the very start before trying something new...years of PC and Mac have taught me that even tho the manufacturers say you just apply upgrades on top of previous upgrades, sooner or later they will f**k up....
I wonder why you are passing thro all the steps you are...(going thro 6.0, 6.1 etc)
I would be inclined to try going back to stock....stock whatever it was rom when you got the tab (notice you've never stated what model you have), stock kernel, nothing installed....then go direct to Tasks 7.1 (everything needed in 6.x is incorporated in 7.1) .... then, if it boots and runs, add pershoots kernel...
What do you reckon Task?? Can you chip in on this one?
Cheers, Stinky

@ slice2011.....any news?

Drpbody said:
And bobs your uncle..
Click to expand...
Click to collapse
How'd you know Bob was my uncle?
Oh wait..everybody has an uncle bob somewhere

Please help with wife's HD2

Hey guys. Been running CM nightlies on my wife's HD2 for her. Previous one I had running was the cm_leo_full-20110830.zip. Now that nightlies are back up and being built, I decided to DL the latest (cm_leo_full-20110927.zip). I booted her phone up into MAGLDR, keyed down to recovery, booted up into CWM, wiped cache and then flashed cm_leo_full-20110830.zip in recovery. Then I rebooted her phone. It has now been sitting at the CM7 splash screen with the rotating arrow for about 20 minutes. It's not bootlooping or anything. The arrow keeps spinning and spinning, but it's not booting into CM7. We're both getting a bit frustrated and can't understand what's taking so long. I have a ton of experience rooting/flashing, etc., on many phones (G1, MT3G, Nexus One, MT4G, G2x, and now my HTC Sensation), but am fairly new to the HD2 world.
Any help you can provide will be great appreciated. TIA.

Part Four said:
Hey guys. Been running CM nightlies on my wife's HD2 for her. Previous one I had running was the cm_leo_full-20110830.zip. Now that nightlies are back up and being built, I decided to DL the latest (cm_leo_full-20110927.zip). I booted her phone up into MAGLDR, keyed down to recovery, booted up into CWM, wiped cache and then flashed cm_leo_full-20110830.zip in recovery. Then I rebooted her phone. It has now been sitting at the CM7 splash screen with the rotating arrow for about 20 minutes. It's not bootlooping or anything. The arrow keeps spinning and spinning, but it's not booting into CM7. We're both getting a bit frustrated and can't understand what's taking so long. I have a ton of experience rooting/flashing, etc., on many phones (G1, MT3G, Nexus One, MT4G, G2x, and now my HTC Sensation), but am fairly new to the HD2 world.
Any help you can provide will be great appreciated. TIA.
Click to expand...
Click to collapse
Firstly make sure you have the right size partition for that particular rom
Then wipe data, cache, dalvik cache(in advanced), and lastly format boot and system in the mounting option then flash the rom

I used to meet this problem but after pull out the battery and restart the phone it is ok.
Something in SD may make the boot processing taking longer, so i think you should try with formatted SD card.

Thanks for the replies guys. I'll try both out tonight and see what happens. Not sure why the sd card would matter though, as this is a NAND install. The build should boot, even without an sd card installed.

As an addition to the replies above,
A first boot can take up to 45 minutes.
So be patient also.

Again, thanks for your responses guys. I just flashed the latest nightly/daily (9-29-11) on her phone through CWM and it booted up just fine. Only wiped cache and dalvik cache. Not sure why it worked fine this time and not with the previous build. Only problem I'm seeing is that her camera hangs now. It won't load up, just hangs and then gives the option to Force Close or Wait. Waiting does nothing. Can someone point me to the thread where discussion of these (http://cyanogenmod.arif-ali.co.uk/rom/) nightly/dailies is appropriate?
Thanks again!

Part Four said:
Again, thanks for your responses guys. I just flashed the latest nightly/daily (9-29-11) on her phone through CWM and it booted up just fine. Only wiped cache and dalvik cache. Not sure why it worked fine this time and not with the previous build. Only problem I'm seeing is that her camera hangs now. It won't load up, just hangs and then gives the option to Force Close or Wait. Waiting does nothing. Can someone point me to the thread where discussion of these (http://cyanogenmod.arif-ali.co.uk/rom/) nightly/dailies is appropriate?
Thanks again!
Click to expand...
Click to collapse
Bah! Forgive me. The answer was right within the link that I posted. Seems many are experiencing the same issues. Thanks.

Many are having problems with the cameras. May want to try downloading lgcamera from the market. Seems to work pretty well with most roms/builds

Bricked my Evo.

Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.

TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven

TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many

Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk

Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)

hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven

Stuck in the CW recovery screen, tried everything.

I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.

Had you flashed CmWR into eMMC?

Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913

@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....

@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.

DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.

Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.

can't get adb to recognize the device since it is in cwr... how did you do it?

chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.

try this:
http://forum.xda-developers.com/showthread.php?t=958748

dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.

Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.

[Q] Clockwork Mod Rom update problems?

So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.

breakneat said:
So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.
Click to expand...
Click to collapse
Go to my tips thread linked in my signature and make a bootable CWM SD per my item A10. If your books and comics are on SD do not use that SD for CWM, use a different one. Then you can flash the new CM7.2 ROM with that. It should boot fine for you. If it still balks on you, go back to CWM and do a wipe data/factory reset. That will wipe out the installed apps and settings, but will not effect the books and comics you have on your media partitions (emmc and sdcard). But you will have to reinstall all of your apps.