Related
I nflashed which i have done on several occasions before and then tried to restore a backup from clockwork and it messed up. i re nflashed and im stuck in a boot loop at the tapntalk and n screen. how can i fix this
Please help. I have done the full format utility then nvflash stock. Still boot loops at tapntap screen. Tried flashing clockwork. 8 through nvflash and can get to recovery but can't select any options due to side touch keys not responding
Sent from my PC36100 using XDA App
Gtab boot loop tapntap screen
I nflashed which i have done on several occasions before and then tried to restore a backup from clockwork and it messed up. i re nflashed and im stuck in a boot loop at the tapntalk and n screen. how can i fix this
Sent from my PC36100 using XDA App
pitmanr2003 said:
Please help. I have done the full format utility then nvflash stock. Still boot loops at tapntap screen. Tried flashing clockwork. 8 through nvflash and can get to recovery but can't select any options due to side touch keys not responding
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Sent from my PC36100 using XDA App
pitmanr2003,
You seem to know nvflash and CWM, so I'll give you the short version.
NVFlash back and install CWM so you can work in it.
I associate boot looping with partition problems -- your tablet needs to
be re-partitions in CWM.
When you have a working CWM, go to the Advanced menu and run
the Repartition option. Set it for 2048 and 0 when requested. Takes
a while so don't panic.
When that finishes, also Fix Permissions. Then Wipe Dalvic Cache.
The go back to the main CWM menu and Wipe Cache and Wipe
Factory Data.
Having done this, you can reload your rom. If CWM is still working,
you can use it to load. If not, you have plenty of nvflash experience
now to do it that way.
Hope this helps.
Rev
P. S. -- I don't use the format utilities. Also, in CWM the Volume rocker
moves the menu selection up and down. Home selects the item. Back
will take you back a step. I think these directions are just above the
menu at the top of the screen.
P. S. S. -- If you can't flash CWM, flash stock and then look at the new
post I just created in Q&A Forum on "Emergency CWM Recovery MiniSD".
Merged related
I have got cwm. Installed. And can move up and down. The problem is I can't select any options due to the home key and the back key don't work now. They used to work perfect. Till all this happened.
Sent from my PC36100 using XDA App
pitmanr2003,
If the keys don't work with CWM, the I don't see anything to do
but go back and re-nvflash and see of that will get CWM to
working. Also, make sure the CWM is the bekit .8 version.
I mean re-nvflash to stock 1105 and reload CWM.
Rev
i can flash back to stock. I dont know what version, but all it does is boot loop, so how can i install cwm. The way i am installing cwm is through nflash by replacing part9 with the downloaded cwm for internal. I just change the name of it to part9. i have also tried the 46 nflash and it boot loops as well. i think im flashing cwm wrong through nflash, but that is all that Info i have found.
pitmanr2003,
Don't use the '46' it is for Linux and I have helped other people who loaded it and
got boot loops.
You say you are installing CWM -- what happens when you shut down, and then
restart by pressing power and volume +. Do you get CWM? Or what?
If we can get CWM installed and opened and working, then we can do several things ranging
from wiping cache to resetting factory data, to re-partitioning to wiping the dalvik
cache to fix permissions -- all of which could tip us over from not working to working.
Don't give up yet. Be patient and keep thinking.
Let us know.....
Rev
I can get cwm installed. I get to the recovery screen. And can use volume up and down to navigate but I can't select the options. My home and back button wont work. I push them and it does nothing. They worked fine before I did nflash and tried to restore a backup I had from while back.
Sent from my PC36100 using XDA App
pitmanr2003 said:
I can get cwm installed. I get to the recovery screen. And can use volume up and down to navigate but I can't select the options. My home and back button wont work. I push them and it does nothing. They worked fine before I did nflash and tried to restore a backup I had from while back.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you have bekit's 1105 image on the machine right now?
If not, what do you have on it?
I have it on there. Just don't know if I have it installed right being my home key and back button aren't workink. I queasy it is 1105. The one for internal use that is from sticky on installing cwm and roms
Sent from my PC36100 using XDA App
Ok... we're not understanding each other. I asked what version of the nvflash image you have on there.
1) You must nvflash with bekit's 1105 image
2) You must use CWM .8
Any other combination will give you trouble.
I think I need to start over. What is best steps to get clean slate. Here is what I have tried. I used the format nflash utility that is stickied. Then I nvflashed what I assume is 1105. How can I tell? I just use the one that is stickied in here as well. When I do that it acts like its going to load. But it gets to tapntap screen and just keeps looping. Then I tried to format again through nflash. And then flash cwm to try to set partition size. The way I do this and may be wrong. I take cwm and rename it to part9
Sent from my PC36100 using XDA App
And reflash that way. I then can get to bekit .8 but home buttons and back button wont select options. I think where I'm going wrong is how I'm installing cwm through nflash. But can't find tutorial for it
Sent from my PC36100 using XDA App
pitmanr2003 said:
I think I need to start over. What is best steps to get clean slate. Here is what I have tried. I used the format nflash utility that is stickied. Then I nvflashed what I assume is 1105. How can I tell? I just use the one that is stickied in here as well. When I do that it acts like its going to load. But it gets to tapntap screen and just keeps looping. Then I tried to format again through nflash. And then flash cwm to try to set partition size. The way I do this and may be wrong. I take cwm and rename it to part9
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The 1105 is part of the filename that you would download... "nvflash_gtablet_2010110500.zip"
pitmanr2003 said:
And reflash that way. I then can get to bekit .8 but home buttons and back button wont select options. I think where I'm going wrong is how I'm installing cwm through nflash. But can't find tutorial for it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
If you are looping at the TapNTap screen you can probably install CWM from an SD card instead of through nvflash. Instructions can be found here: http://forum.xda-developers.com/showthread.php?t=1020747
Thx I will try that. I don't have any blank micro SD cards. Only my phone one. Will it be safe to just put it on root of it and use it. Even without deleting my files already on it
Sent from my PC36100 using XDA App
It should be but you never know. If you can back it up to your computer first that would be better.
That's what I probably will do
Sent from my PC36100 using XDA App
Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.
Hello all, introduced myself the other day, I'm new to the Galaxy SII and have had it only a few short days. And already I've managed to screw it up! LoL. No really what I made this thread for is to let people who may have done the same thing I've done that there is a solution. Here's what I did. Download the VillainRom and the Hellraise MOD from the development section. I put them both on internal SD card, rebooted into clockwork mod recovery, and flashed Villlain ROM. After that, I was SUPPOSED to flash Hellraiser so it would be compatible with the I777 since it's an international version ROM. But I was talking to my son at the same time and FORGOT and let it reboot and boot up into VillainROM. I was at this point very worried, as I thought a bunch of errors would occur. But not a bunch did. However I knew this wasn't good and tried immediately to reboot into recovery, wipe, and redo the process PROPERLY. Except when I rebooted, it rebooted me into clockwork mod recovery 4.0 version. Now, at this point, none of the capacitive buttons or the power button would select anything. It just showed the Clockwork Mod logo when I clicked on anything to wipe, reboot, anything. SO, here's what I did to fix this mistake. I download the clockwork mod recovery .tar that is flashable with Odin (the one for I777), rebooted back into VillainRom, put the phone into Download mode, and flashed it. Then I let the phone reboot, and then rebooted a second time into what I HOPED would be the correct version of CWM. And thank God, it was. However, the capacitive buttons were STILL not working correctly. The answer? They DO work, however, they are out of order. Different buttons do different things but if you figure the order out you can wipe and flash back to a ROM for our device. I just wanted to post this, in case anyone else messed up like I did.
edit: It did not, however, change the Boot Logo from thinking I'm running the international version. That still says i9100
Phalanx7621 said:
Hello all, introduced myself the other day, I'm new to the Galaxy SII and have had it only a few short days. And already I've managed to screw it up! LoL. No really what I made this thread for is to let people who may have done the same thing I've done that there is a solution. Here's what I did. Download the VillainRom and the Hellraise MOD from the development section. I put them both on internal SD card, rebooted into clockwork mod recovery, and flashed Villlain ROM. After that, I was SUPPOSED to flash Hellraiser so it would be compatible with the I777 since it's an international version ROM. But I was talking to my son at the same time and FORGOT and let it reboot and boot up into VillainROM. I was at this point very worried, as I thought a bunch of errors would occur. But not a bunch did. However I knew this wasn't good and tried immediately to reboot into recovery, wipe, and redo the process PROPERLY. Except when I rebooted, it rebooted me into clockwork mod recovery 4.0 version. Now, at this point, none of the capacitive buttons or the power button would select anything. It just showed the Clockwork Mod logo when I clicked on anything to wipe, reboot, anything. SO, here's what I did to fix this mistake. I download the clockwork mod recovery .tar that is flashable with Odin (the one for I777), rebooted back into VillainRom, put the phone into Download mode, and flashed it. Then I let the phone reboot, and then rebooted a second time into what I HOPED would be the correct version of CWM. And thank God, it was. However, the capacitive buttons were STILL not working correctly. The answer? They DO work, however, they are out of order. Different buttons do different things but if you figure the order out you can wipe and flash back to a ROM for our device. I just wanted to post this, in case anyone else messed up like I did.
edit: It did not, however, change the Boot Logo from thinking I'm running the international version. That still says i9100
Click to expand...
Click to collapse
You could have just flashed the stock ROM though Odin. That would have fixed everything and given you a fresh start but that's up to others to decide.
Sent from my SGH-I777 using XDA App
You DID read the first post for codeworkx's CWM kernel for the button mappings, right?
IF you had CWM 5.x after flashing his tar, it did correctly flash.
Also, all you have to do now is just flash hellraiser - should be OK even after booting VR normally, although NFC might flake out... I haven't tested what happens if you flash hellraiser after /data is created
Entropy512 said:
You DID read the first post for codeworkx's CWM kernel for the button mappings, right?
IF you had CWM 5.x after flashing his tar, it did correctly flash.
Also, all you have to do now is just flash hellraiser - should be OK even after booting VR normally, although NFC might flake out... I haven't tested what happens if you flash hellraiser after /data is created
Click to expand...
Click to collapse
You DID receive my pm right? Yea I thought so...
Sent from my SGH-I777 using Tapatalk
No I didn't receive any pms ..
Have to check and see if somethings wrong on my end with tapatalk. Thanks for the tips if I ever do it again ill know what to do
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I am trying to fix my recovery partition and am not sure if I did or not. The process that the stock recovery goes through seems awfully short. Here's what it does.
Factory Reset screen
Are you sure?
Clearing Data: (5 - 10 seconds)
n screen (rebooted)
Shouldn't there be a "restoring factory software" screen or something like that?
The main reason i am doing this is so i can unroot. Indirects unrooter app fails partway through and i think this is because of the recovery partition.
old_fart said:
so if the period of time is directly proportional to the size of the data area... then logically its right cause that chunk is 'not' all that big.
Click to expand...
Click to collapse
what?
as to the op, did you flash clockworkmod recovery to your device at one point?
Cubanluke88 said:
what?
as to the op, did you flash clockworkmod recovery to your device at one point?
Click to expand...
Click to collapse
Yes.
Also, I forgot to mention this is an 8gb.
I used indirects app to flash CWM recovery http://forum.xda-developers.com/showthread.php?t=1458630 I didn't realize it was only for 16gb. (in my defense it doesn't say that anywhere in the thread).
Then still not knowing it was for 16gb i used that app to flash it back to stock recovery. Which ,i'm told, put the 16gb recovery on my 8gb nook.
So i followed veronica's instruction http://forum.xda-developers.com/showthread.php?t=1570022 to use adb to fix the partition. It seemed to work properly. Its just that, as i said in the OP, running recovery seems very quick.
My ultimate goal is to unroot, but the unrooter app doesn't work for me (possibly because recovery isn't right) and flashing the BN 1.4.2 zip doesn't work either (possibly because recovery isn't right)
eggwardo said:
Yes.
Also, I forgot to mention this is an 8gb.
I used indirects app to flash CWM recovery http://forum.xda-developers.com/showthread.php?t=1458630 I didn't realize it was only for 16gb. (in my defense it doesn't say that anywhere in the thread).
Then still not knowing it was for 16gb i used that app to flash it back to stock recovery. Which ,i'm told, put the 16gb recovery on my 8gb nook.
So i followed veronica's instruction http://forum.xda-developers.com/showthread.php?t=1570022 to use adb to fix the partition. It seemed to work properly. Its just that, as i said in the OP, running recovery seems very quick.
My ultimate goal is to unroot, but the unrooter app doesn't work for me (possibly because recovery isn't right) and flashing the BN 1.4.2 zip doesn't work either (possibly because recovery isn't right)
Click to expand...
Click to collapse
I'd try 8 failed boots (from off push and continue to hold power until screen is black) on 9th. allow NT to boot and I think you will see different results. This of course assumes you used the 8gig partitions when using veronica's instructions.
Good Luck!
Note: If not positive about which recovery (8 or 16) you used do not do this. Go back and use the 8gig.
One reset only erases data the other invokes recovery and is said to actually return to box-stock.
eggwardo said:
I am trying to fix my recovery partition and am not sure if I did or not. The process that the stock recovery goes through seems awfully short. Here's what it does.
Factory Reset screen
Are you sure?
Clearing Data: (5 - 10 seconds)
n screen (rebooted)
Shouldn't there be a "restoring factory software" screen or something like that?
The main reason i am doing this is so i can unroot. Indirects unrooter app fails partway through and i think this is because of the recovery partition.
Click to expand...
Click to collapse
Once I had time I did both resets and you are right. One only says clearing data and ends, the other says clearing data then restoring factory data and does take longer. Sorry for the delay but I was running CM9 and needed time to set everything up for the testing.
Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
funnel71 said:
Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
Click to expand...
Click to collapse
I don't know if restoring from backup will help, lets keep that option for later.
If you are able to enter twrp, I suggest you flash a cwm 6 flashable .zip, I think the older twrp had some bugs. I use cwm6.012. Now enter that, and flash only the cm10 Rom, don't worry about gapps now. Then factory reset and reboot device.
Let me know what happens then.
I don't believe it's bricked, its probably a cyanoboot issue. What happens if you hold the n button, then select first option? It looks like device is not finding the Rom, hence rebooting.
Sent from my ST27i
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
funnel71 said:
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
Click to expand...
Click to collapse
Also, in recovery, go into mounts and storage, mount system partition, then try flashing the Rom.
Do not format anything in mounts and storage.
Sent from my ST27i
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
funnel71 said:
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
Click to expand...
Click to collapse
It should mount system by default, but no harm mounting it manually.
Do not mount sdcard, unless it doesn't show the zip files.
Sent from my ST27i
That is why I mounted SD, because it didn't have it mounted, and I could not see anything, especially the zips...OK will try this later today, TYVM.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
FWIW I had huge problems when trying to use TWRP. It didn't see my sd-card as it should, and I have heard others having similar issues. I didn't try too much, but went on with CWM instead, following the steps I posted here:
http://forum.xda-developers.com/showthread.php?t=2081981
(At one point while struggling with TWRP I messed up bad enough to get into a boot loop. I solved it ny running the repart.img that is mentioned here and there)
I'm sorry, what is that repart img? Is that the "unbrick your nook using ubuntu" thing I saw in dev but can't download? Do you happen to have it somewhere? LOL
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, it's not the Ubuntu thing. It's the one in this article:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Just wanted to throw this out here from the original post on this thread too.
Dang, But all's not lost, If you can get into TWRP like you say do a full wilpe of everything and try to reflash CM7, If that doesn't get you going I would recommend starting over to insure all is well. It's actually hard to really "brick" a NT and there are many good threads here but I have used this one and it's pretty simple to get you back to factory 1.4.3 http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Lets go from there, I'll be around to help except between 3:30 - 5:30 CST, But will do what ever I can to get ya up & runnin.
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Not exactly sure what goin on in there but if you can get to a recovery menu then it's possible to just fact/dalv/cache wipe ect to clean the garbage and try a fresh install. (maybe) but the back up plan is sure to work if that doesn't
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
No do not wipe anything in mounts and backup. Formatting the bootdata, factory partition and some of the other partitions WILL brick your device. Only cache partition can be wiped (do factory reset)
Sent from my ST27i
funnel71 said:
...
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip ...
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
...
Click to expand...
Click to collapse
You can either:
Try flashing CM10 again, using a much less circuitous process such as the one described at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1; or,
Try restoring to stock using the info/tools from https://github.com/succulent/acclaim_recovery_sdcard.
And in case you're tempted to use any of the so-called "unbrick" tools/methods, first read http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31
SUCCESS!!
OK, equipped with 2 SD cards, 2gb for boot into CWM v6012 recovery and 16GB with JB ROM, GAPPS, and updated CWM 6027 recovery for EMMC...
Attempt #1
Booted into CWM SD recovery via PC usb
Swapped SDs to the 16 with the roms and new cwm emmc recovery
Flashed CWM emmc recovery - success (so now twrp that I had should be gone)
Reboot into system and held N to get to cyanoboot menu & selected internal emmc recovery - success, now in CWM 6027 emmc recovery
Selected install zip from sd card (16 still inserted), flashed sgt7-10.1-20130131-0219-acclaim-meghd00t.zip - success
Selected install zip - flashed gapps-sgt7-10.1-20130131-0219-acclaim-meghd00t.zip (I renamed it to match the other, but it's what came with it in the dev post I got it from) - success
Selected to wipe cache, then went to advanced and wiped dalvik cache - success on both.
Hmm, no main menu, it indicates it wiped it, but stayed still at that point, held power button to power off, turned back on, held N to get back into cyanoboot menu just to view its appearance, seemed normal, selected internal EMMC normal..black screen for several seconds, cyanogen loopy design spins (getting a tad happier), will just let this spin for a while... sure beats seeing a bootloop...
5 Minutes later, still getting the loopy design spin, assuming it's unable to boot, did a hard poweroff, removed SD, started again, this time just letting it run, got the cyanogen spin thing again... assuming it will not boot after 5 minutes.
Attempt #2
Repeated the same process as 1, only this time flashed TWRP recovery 2.2.2.0 into EMMC
Using TWRP, flashed the same jb rom and gapps - reboot
Exact same result.
Attempt #3
Decided to change SD cards the ROM and gapps is being loaded from, because I've heard to use a class 4 card, and the 16GB is a class 10 - changed to an old class4 512MB card - repeated the above process - whoa, twrp is gone, but I didn't flash emmc recovery...is that in the ROM perhaps?? Oh well, tried to flash with this older SD card - Ooo, getting farther, the loopy thing changed shape and now is in the center of the screen (slightly excited) - I may have it!!
Going through set up now!! Going to call this portion a success. Other problems should probably be a new thread as this was resolved...
Ultimate cause - too good of an SD card???? Seriously? Oh well, got er done. thanks to all of you for the ideas. They truly helped.
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Point well taken, thanks much. I was backwards
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
...
Click to expand...
Click to collapse
Actually, data/cache/dalvik cache just need to be wiped before first boot of the new ROM.
Of course the order doesn't matter! I really must stop reading the forum (or at least stop writing!) in the middel of the night! (I'm in Sweden). My brain moves slow enough even at it's best... Sorry!