Related
I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
I purchased a nook color the other day and successfully rooted and used it for a few days. My youtube would not open so I reinstalled, it ran once and then failed to open again so I gave up on that issue. In reading about youtube app I found that you could get the new market app. I could not get it to install...and in trying multiple things I accidentally deleted my original market app.
I could not get it back so I whiped my nook color and reflashed autonooter. I got all my apps back but I get a connection error when trying to access the market now. I added my account via youtube which again opened once to allow me to sign in and now fails to open.
So I decided to try to reset it back to the way it was out of the box and start from scratch.
I tried the adb 8x reboot method.....it just reboots the nook as it normally would. No bootloader or install screen.
I tried the button method. It works once or twice then it goes through the entire boot. I did it for a half hour and used counts to verify I was doing the process correctly and no matter what I did I could get it to fail boot once and one the second or third it would always bypass and go through with boot even with my finger on the button.
I also am running windows 7 64bit and I cannot get my computer to see "nook" in the device manager for more than a second and it auto installs as a storage device. I've tried to "uninstall" the different devices and last night I was able to catch the "nook" in time to install usb drivers manually but when I reset the nook today my PC no longer see's it again. I was wondering if there is an easier way to install the adb device.
Thanks
UPDATE: Somehow the ADB way to reflash worked the second time I tried it. I also changed some settings in the development menu to fix the device manager issue. I'll update again if I can use youtube and the market.
I don't know what to tell you about everything else but for ADB I would highly recommend adbWireless... it works great on my NC and I never had to install any drivers.
To reset I used the button and counted slow to 15 after the screen gose off each time it worked for me. Good luck
Hello fellow XDA'ers!
I have come into possession of a tablet that has the following problem:
When applying the OTA update to the SGH-i957 LTE tablet from Rogers, the previous owner plugged in the tablet into a mains power supply.
Because of this, I was told that the OTA update did not "complete." Specifically, at device reboot, the tablet was not accessing the newly updated ROM. At this point, the owner went into a bit of a panic:
- They hooked up the device to ODIN3 v1.85, with no response;
- They wiped all data & performed a factory reset;
- They wiped the cache partition;
- They formatted /cache;
- They formatted /data;
- They formatted /system
- They also made sure all settings were clear.
I tried to restore via Nandroid, but I get the following output via CWM-based Recovery (v5.5.0.4):
Code:
restoring boot image...
restoring system...
restoring data...
".android_secure.img not found. Skipping restore of /sdcard/.androidsecure."
restoring cache...
Restore complete!
Obviously, this isn't good. But wait, there's more! When I am trying to activate the option to "mount USB storage," I get the following error:
Code:
E: Unable to open ums lunfile (No such file or directory)
I opened the CWM recovery log, and like the Stanley Kubrick movie "The Shining," the log printed following 10 to 12 times:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory.
I have yet to connect the device to my computer, as I don't want to mess it up any further. The tablet is currently plugged in to a mains power supply, awaiting resurrection.
I have experience in successfully restocking & flashing my Samsung Galaxy Tab (GT-P1000) via ODIN with Overcome/CM9, so I am more than happy to troubleshoot and thoroughly document anything that is happening with the tablet.
I have searched this specific forum for threads that relate to OTA failed updates, but I have not seen a similar thread or post.
I fully promise to document this problem in this thread if other people have issues in the future relating to this problem.
Therefore, how do I bring this tablet back to its former glory of sweet LTE-goodness?
Thanks,
willing_to_cooperate
Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
It works! It came back from the dead!
Eun-Hjzjined said:
Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
Click to expand...
Click to collapse
It worked!
For anyone that may have the same problem:
1) Put SGH-i957 into download mode (turn off, then hold power and volume up-down keys):
2) When you see a warning, make sure to press the volume up key (therefore, if you're looking at the tablet screen with the power cord outlet on the left hand side, it would be the bottom rocker button, furthest away from the power button).
3) Connect to ODIN v1.85.
4) Load the firmware into the PDA slot.
5) Make sure that Re-Partition and Flash Lock are NOT checked.
6) Make sure that Auto Reboot and F. Reset Time are checked.
7) Press start.
The tablet will go through its process, and may reboot 1-2 times. It will build a cache (you will see the Android figure with a geometric ball rotating in its stomach).
After that, it should boot into your carrier's logo screen, with setup of the device.
Thanks again, Eun-Hjzjined!
willing_to_cooperate
---------------------------EDIT:
This process also removes root from the tablet. However, no hiccups when re-installing root.
Hi thanks for all your help!
I have an i957 on ATT in the US, and previously had rooted with DaG v2 Kernel, worked great.
Yesterday I used the stock i957M (Bell) Update to get on ICS. Failed on Modem (known issue mo XDA), but rebooted and works fine.
It removed the root (as yours did above) - when I tried to re-root with same kernel on ODIN, everything locked up. Had to re-do the firmware with ODIN as in your entry above - now back in action.
Question: If there was some way you re-did your root so it was compatible with your build, can you point me to it?
Did some searching around, and only found dated sources that talked to how I did original root.
Maybe you have some magic.
Sure would be nice to get SU and CWM again, rather than stock.
Nevermind - Got it working - used "Method 1" - Stock Kernel from http://forum.xda-developers.com/showthread.php?t=1401100
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
picante544 said:
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
Click to expand...
Click to collapse
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
sphinxcs898 said:
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
Click to expand...
Click to collapse
picante544 said:
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
Click to expand...
Click to collapse
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
http://theunlockr.com/2012/10/16/how-to-root-the-htc-nexus-one/
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Resolved--hardware problem--trackball
Coincidentally, another user had a very similar experience with his N1 at the same time. He determined it was his trackball. I tore my phone apart, disconnected the trackball and the phone now works again.
Thanks again to those two people who responded.
sphinxcs898 said:
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Click to expand...
Click to collapse
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.