hey guys,
i have a 1.43 nt16 rooted and running cm10 from internal. i forgot to run a backup prior to installing. i cannot find a 1.43 rooted, or stock rom anywhere. i found a 1.40, and a 1.42, however after these flash, it gets to the setup, but the touch screen is non responsive. therefore i cannot go any further. any advice? anyone have a stock, or stock rooted 1.43 i can download to get this puppy back to stock?
haloseven said:
hey guys,
i have a 1.43 nt16 rooted and running cm10 from internal. i forgot to run a backup prior to installing. i cannot find a 1.43 rooted, or stock rom anywhere. i found a 1.40, and a 1.42, however after these flash, it gets to the setup, but the touch screen is non responsive. therefore i cannot go any further. any advice? anyone have a stock, or stock rooted 1.43 i can download to get this puppy back to stock?
Click to expand...
Click to collapse
Could this work? http://forum.xda-developers.com/showthread.php?t=1663836
I just did the unbrick method and although it completed the unbrick successfully, when it rebooted, the touchscreen still doesnt work. im just going to chalk it up to a faulty refurb. im perplexed though, as CM10 works fine, if i put it back on there.
I would run cm10 from sdcard and flash back factory touch firmware
Sent from my Barnes & Noble Nook Tablet using my fingers to Swype
Did you try to hold power + N to reset your nook 8 time? It will go back to stock rom
Sent from my Barnes & Noble Nook Tablet using xda premium
BadKid3011 said:
Did you try to hold power + N to reset your nook 8 time? It will go back to stock rom
Sent from my Barnes & Noble Nook Tablet using xda premium
Click to expand...
Click to collapse
The ROM isn't the problem. The op needs to reflash the 2 touch firmware.
Sent from my CM 10 SD nook tablet. Thanks devs.
i just took it into a BN store and they swapped me for another refurb. thanks for the help though!
Related
Hi. I have a problem which never happened to me before on my tablet. My nook is rooted and has already CWM and ICS installed on it, but today when I tried to boot it after leaving it off for a couple of days, it failed to start android.
It starts up normally and loads cyanoboot, which then tries to launch android from the emmc. After this it gives a black screen for a few seconds and goes back to the first nook screen. It then loads cyanoboot and does the same thing again. I wiped everything and flashed android again but it didn't help.
I don't understand what has changed. I had it working perfectly all the time during the past month. Can anyone help me diagnose this issue?
Thanks.
Maybe it just expired if you dont have the latest version 0.03 then flash it and you should be good again.
~ Veronica
Interesting. It worked.
Never knew a ROM could expire.
Thank you very much.
sebouh00 said:
Interesting. It worked.
Never knew a ROM could expire.
Thank you very much.
Click to expand...
Click to collapse
this one yes, due to some people that would like to sell it so ... dev was smart and added an expiration feature
I had this happen and decided to just restore back to a backup but now I'm in a CWM loop. I restore clear cache and dalvik (sp?) select reboot and I'm back at CWM...any idea what I'm doing wrong?
Nikkie
Sent from my Nook Tablet using XDA
NikkieL said:
I had this happen and decided to just restore back to a backup but now I'm in a CWM loop. I restore clear cache and dalvik (sp?) select reboot and I'm back at CWM...any idea what I'm doing wrong?
Nikkie
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
Flash another rom and see what happens.
Sent from my NookTablet using Tapatalk
NikkieL said:
I had this happen and decided to just restore back to a backup but now I'm in a CWM loop. I restore clear cache and dalvik (sp?) select reboot and I'm back at CWM...any idea what I'm doing wrong?
Nikkie
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
You have to flash the latest version of Cm9. The version you're on (probably 0.02) will never boot again because it has expired. Just flash the latest build from the Cm9 thread (0.03) and you'll be fine again.
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Here's the thing I don't want to flask ice again....want to restore my back-up. I'll download the ice, flash that and see if I can restore the back up after that.
Nikkie
Sent from my Nook Tablet using XDA
NikkieL said:
Here's the thing I don't want to flask ice again....want to restore my back-up. I'll download the ice, flash that and see if I can restore the back up after that.
Nikkie
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
that "should" work, best of luck, tell us how it goes...
NikkieL said:
Here's the thing I don't want to flask ice again....want to restore my back-up. I'll download the ice, flash that and see if I can restore the back up after that.
Nikkie
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
If you restore from the backup, and then flash the newest CM9 (still 0.03) itll simply update the OS, not delete any of your user-data ie: apps, music, contacts.
Re-install of 9.03 didn't work
SilentStormer said:
If you restore from the backup, and then flash the newest CM9 (still 0.03) itll simply update the OS, not delete any of your user-data ie: apps, music, contacts.
Click to expand...
Click to collapse
I have the exact same problem and have tried to re-flash 9.03 but to no avail. It still continues to loop. I did not know these things expired. Should I consider moving to 9.04???
On .3 as well and was reading a book tonight and all of a sudden it started boot looping.
I got the same problem then flash again and again too many rom file.
With flash_stock_1.4.2.zip in _https://github.com/succulent/acclaim_recovery_sdcard my Nook Tablet works again like new. Just try it
hi, you try wipe cache when installed cm9? If you do'nt wipe cache, it loop
Ok, I'll try to be short about this.
I did the RegawMOD method and was able to install Liquid Smooth on the phone. (1.45)
When I was going to install an update for that things when odd. (I always back up, reset and wipe before hand)
The update didn't take however I was able to the home screen. As it was weird I went back to restore and the Trwp did not back up correctly. The file was bad.
I was able to get back to the home screen and then setup my phone. I decided to wait for a while until the roms grew up a bit.
Now I was going to install Mean 1.4 today so I downloaded as the post said and installed the radio. Downloaded the rom. When into recovery backup, reset and wiped. When I tried to flash the rom TWRP just started rebooting.
I have tried it several times and also tried to recover and TWRP keeps rebooting. Now I am stuck on the HTC screen.
What do I do now? I feel the recovery is bad.
Any help greatly appreciated.
Maybe a bad recovery flash or corupt download.. Try reflashing recovery through fastboot, download the ROM again, do a FULL wipe and reflash the ROM.
Sent from my ELTE using Tapatalk 2
Thankfully I was able to install an earlier backup so at least I am running now. I have tried using Goo Manger to reinstall twrp 2.2. Just stays stuck at the download.
I haven't used the fastboot method before so I'll have to look that up. I want to get to mean 1.4 as included the OTA fixes because I have the wifi issue. Guess I'll have to wait until I have more time.
Thanks for the help.
Ok so I got goo manager to reflash the recovery.
Now I am on mean 1.4 and very happy. No more WiFi issues either!
Finally as useable as my OG EVO and dandy like this phone was ment to be.
Thanks for the help and thanks developers.
Very cool.
Sent from my EVO using xda app-developers app
My phone wont boot now.
It stays stuck at the 2nd Samsung during the boot up.
What happen was I updated today to offical ICS from my rooted gingerbread.
I updated via kias today to get official ICS, got it working and I noticed I didn't have cwm install anymore, so I followed this http://forum.xda-developers.com/showthread.php?t=1504218
It is pass it did it reboot thing, and never got past the 2nd "samsung" loading screen.
Anyone know how to get my phone booting again?
Flash the latest ICS kernel
I am not sure how to do that without cwm.
Before I updated to ICS when I press power + up down, it booted into CWM. Now when I do that I boots into Android System Recovery <3e>
EDIT: Good news.
Got CWM through installed though odin and then I restored to my gingerbread backup I made earlier.
Flash your roms via clockwork recovery mod from now on.
Drop the ROM .zip on sd card and then enter recovery. Wipe everything three times each then flash a uclf6 based ROM. Never touch Odin or kies again. Be happy. Ice cream sandwich is way better than ginger bread
Sent from my SAMSUNG-SGH-I717 using xda premium
Had the same exact problem. I "believe" the problem was that the CWM I flashed was perhaps incompatible with the official ICS?
I used Odin to flash cwm 5.5.0.4 as suggested and the fone was shut down with the hanging Samsung screen as you mentioned. I used the DL screen with Odin to the 600mb Team Objection ROM, which at least got me up and running again. I found out that CWM did in fact flash once the ROM was compatible with it. Updated CWM, then to finally get full stability, I had to do a factory reset after clearing both caches, then install the CM9 official.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Update: I installed official ICS again last night, looks like I lost my root and CWM.
I don't want to mess anything up again, so could you tell me exactly what CWM file you used to flash so it doesn't hang at samsung again?
I was having the same problems but I think I was doing it wrong. How are you flashing the root files? I upgraded from Kies, then used Odin to flash cwm touch (5.5.0.4 I think), make sure to let the reboot and that it's actually turned on and you can see your homescreen. Once you do that, THEN flash the superuser 3.0.7 in cwm. Let the phone reboot properly and it should be okay.
I was doing the same without the reboots and that's what caused me to hang at the logo, but after the above it worked well. Give it a try. For anyone who needs to flash the T-Mobile radios also let the phone reboot and then flash it because I was having issues with that which was fixed by letting the phone reboot.
Make nandroids at every step in case it does hang so you can just restore and try again instead of flashing everything all over again.
Sent from my SGH-I717R using xda app-developers app
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
dcdtrax said:
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Open odin , PDA cwm file, Droid in dl mode, plug in start unplug, reboot, go to cwm recovery mode and backup onto sd card.
Im learning more, as i soft bricked mine last time
dcdtrax said:
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Click to expand...
Click to collapse
Odin....to get touch cwm, then download the super user zip and flash it, you will have root....
All can be found in "My links" see it in red...go to GNote page....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
liftedzuki said:
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
ok look for the green arrow...and use those threads....to root...k
odin for touch cwm
flash super user
your rooted
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Rooted.
erad1 said:
You realize you the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so correct...you nailed it...so many are trying to root with gb kernal....
I hope they go to the page I made and follow the green arrowed how to root ics...it is very super simple process to root the official ics...but ....
This happened to me after misreading a comment.
If you put your phone into download mode, plug it in, run kies, and do an emergency firmware recovery. You'll need the serial number. My phone is stock ICS again. Works fine.
erad1 said:
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
romeojunior said:
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Wait what??!!??!!
you need to read read read read and PLEASE read
Because CMW is not a kernel
Its a recovery
People wouldn't have these issues if they read.
Please refer to the stickies before you really damage your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The OP had posted that he flashed Da_g's GB kernel trying to get root...your issue if flashing CWM may be different. Hopefully you use the steps outlined by bigjoe in his post.
Sent from my SAMSUNG-SGH-I717 using xda premium
Hello! I have searched the forums already, but to no avail. I have a bricked G Tablet UPC300-2.2 and I am trying to find the stock files and instructions on how I can get this tablet up and running again. Can someone point me in the right direction? Thanks!
Sent from my seksi SGS3 using Tapatalk 2
Anyone?
Sent from my seksi SGS3 using Tapatalk 2
haoleflip said:
Anyone?
Sent from my seksi SGS3 using Tapatalk 2
Click to expand...
Click to collapse
Try this site and learn how to nvflash, then download the bootloader 1.2 stock rom and reset your tablet. Good luck.
http://viewsonic-gtablet-for-dummies.webs.com
Also looking for help. I got the nvflash to work but after the reboot it hangs on the "n" after TnT. When I reboot with "vol +" I see the kernel try to load and then it goes to the black Android screen and !. Any ideas were to look?
iskshoj appointed
BacDoc said:
Also looking for help. I got the nvflash to work but after the reboot it hangs on the "n" after TnT. When I reboot with "vol +" I see the kernel try to load and then it goes to the black Android screen and !. Any ideas were to look?
Click to expand...
Click to collapse
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
PHP:
BacDoc said:
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
Click to expand...
Click to collapse
You might want to try using just the stock 1.1 nvflash with stock recovery first before jumping straight to 1.2 with touch recovery. Granted NVflash was designed to write the stock IMG to you device but best to restore to a complete stock 1.1 go through setup and except the OTA update. This should put you through a better course and update both stock firmware and bootloader. Then as long as everything sticks you can update the recovery IMG using the NVflash package available for what ever ROM you decide to update to. Good luck.
BacDoc said:
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
Click to expand...
Click to collapse
I would try nvflashing again and make sure your repartition and do all the wipe caches n factory reset before and after you nvflash and hopfully that will clear things up. Might go ahead and try the Smooth Bean Rom. U wont regret it. Blazzing speed.
Thanks guys, I did get it up and running but its not stable. When I update to the firmware it crashes and won't load. After a few restarts sometimes it works some times I have to NVF to restore it again. Should I try the NVF 1.1?
At this point I have/had CWM with no rooted ROM, only stock trim.
---------- Post added at 10:26 PM ---------- Previous post was at 09:43 PM ----------
1.1 seems to allow the OTA update. Getting some forced close apps now.
Do I need to wipe everything now?
Well I found what appears to be a stable stock setup now.
I can't get into CWM now and Rom Manager won't install, neither will Google Play.
BacDoc said:
Well I found what appears to be a stable stock setup now.
I can't get into CWM now and Rom Manager won't install, neither will Google Play.
Click to expand...
Click to collapse
First off using ROM manager for you Gtab is just asking for trouble. Don't use it.
As far as Google play how are you trying to install it and what on?
Sent from The Darkside via me....
G tablet stuck "booting recovery kernel image"
I tried to restore to TnT using the zip file up date. Rebooted and the only think I get is the View Sonic logo and in the upper left hand corner "booting recovery kernel image" Also also can not access through the USB from my PC. I tried putting the recovery files on a micro sd card but the tablet does not recognize it. Is there any way I can get access from my pc? Any suggestions are greatly appreciated.
Mark
ultracorp said:
I tried to restore to TnT using the zip file up date. Rebooted and the only think I get is the View Sonic logo and in the upper left hand corner "booting recovery kernel image" Also also can not access through the USB from my PC. I tried putting the recovery files on a micro sd card but the tablet does not recognize it. Is there any way I can get access from my pc? Any suggestions are greatly appreciated.
Mark
Click to expand...
Click to collapse
At this point the only thing that would advise to do is NVflash to stock with the CWM recovery image pre-installed so that everything would be correct. When NVflash is complete boot into recovery and perform a wipe data factory reset and reboot into system.
Sent from The Darkside via me....
Hello! I've had a Nook Tablet for a while that I've ran CM 11 before in the past, and somehow the device had gotten bricked. After I was able to get it to boot from the stock sdcard and restore the partitions, it boot to the Nook Tablet setup screen, with one MAJOR problem. The touchscreen doesn't work at all. And I've tried getting it to boot from CWM sdcard, and it just keeps bringing me back to the Nook Tablet setup. Is there anything I can do?
Sounds like it has the 10 point firmware for the touch screen, reflash cm11 and see if you have the same problem. If not, change firmware (usually included in rom) and start over if you really want the stock. Search around on the forum, you're not the first to have this problem. I'm sure other threads have what you need in them to get you back right.
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Chromium,
Ant lick with this issue?I have it too.
twistedreality3 said:
Chromium,
Ant lick with this issue?I have it too.
Click to expand...
Click to collapse
You can download and burn to SD card one of the SD-based CM11 (or CM10) ROM build images from https://iamafanof.wordpress.com/category/nook-tablet-2/, then boot from SD card and use the TouchScreen FW Flasher app to flash back to 2-touch mode.