So, I activated my phone and then rooted the phone fine, using the all-in-one package for root.
After that I flashed GingerVolt + BlitzKrieg . I think it was wrong to install BlitzKrieg Kernel without at least booting once with GingerVolt stock kernel.
So when the thing booted up, it failed to detect the SIM card, and won't activate again. (the SIM was already activated before rooting). But now the activation process said, 'NO SIM found' .
Anyway, after that , I was unable to boot in to recovery, the phone would hang when selecting 'revocery' from the power button option. and Power Button + Vol Down also didn't work.
So with no way to go back in to recovery, I did a 'factory reset' from the settings menu.
After that the phone boots in CWM recovery, but that's all it does. It only boots in recovery. I have tried to reflash GinngerVolt or to restore to the backup (Stock + root) but to no avail.
Now the phone is stuck booting in to recovey. "adb devices" shows
"IMEI-NO recovery". But no matter what, I can't get it to boot normal.
Any clues how I can get out of this mess ?
Replying to self.
Looks like the culprit is using 'factory reset' method. Found another thread, and a solution on another forum (Can't post links yet )
Gonna try the LGNPST method.
For any newbies looking in to this, the lesson is
1) Boot atleast once in GingerVolt before overwriting stock kernel.
2) DON'T USE 'FACTORY RESET' option, you phone will then only boot in CWM.
If that doesn't work, there is another thread somewhere that has an "exit recovery zip" that you can flash. That may work.
From My Bryce Device
Edit: here's the thread
http://forum.xda-developers.com/showthread.php?t=1161537
Thanks KaneOfMars, but I was able to get back to stock, using LGNPST, although I suspect your link would have worked just as well.
In fact using LGNPST was an adventure in it self, every time I clicked the Upgrade button, the LGNPST.exe would crash (Windows 7 64bit). So tried the China Telcom version LGNPST_CT.exe, and that one said 'c:\windows\system32\drivers\wnsdrvr.sys NOT FOUND'.
Then found another LGNPST_CT.exe standalone inside the LGNSTP.zip file which contained the LGNPST installations.
Put this LGNPST_CT.exe inside the C:\LG Electronics\LGNPST folder, and this one had another option beisdes, "Upgrade" called "Binary Download".
And that is a misnomer, coz it is infact "Binary Upload" to the phone, and this option is the one I used to upload the 'V*7.tot' file (the stock 2.3.4 image), back on LG Revo.
Hope someone can benefit from some of this, I spent a good part of yesterday figuring all this out.
gumnaam.sur said:
Thanks KaneOfMars, but I was able to get back to stock, using LGNPST, although I suspect your link would have worked just as well.
In fact using LGNPST was an adventure in it self, every time I clicked the Upgrade button, the LGNPST.exe would crash (Windows 7 64bit). So tried the China Telcom version LGNPST_CT.exe, and that one said 'c:\windows\system32\drivers\wnsdrvr.sys NOT FOUND'.
Then found another LGNPST_CT.exe standalone inside the LGNSTP.zip file which contained the LGNPST installations.
Put this LGNPST_CT.exe inside the C:\LG Electronics\LGNPST folder, and this one had another option beisdes, "Upgrade" called "Binary Download".
And that is a misnomer, coz it is infact "Binary Upload" to the phone, and this option is the one I used to upload the 'V*7.tot' file (the stock 2.3.4 image), back on LG Revo.
Hope someone can benefit from some of this, I spent a good part of yesterday figuring all this out.
Click to expand...
Click to collapse
Just for reference, you can do a factory reset but ONLY through recovery. Doing a factory reset through the phone menu is what will get you stuck in recovery.
Sent from my GingerFusion Revo using Tapatalk.
Related
I wanted to download the new update for our phone, so last night, I backed up with Titanium Backup and ROM Manager. Then, I used SL4A to undo the ext4 lagfix, as I was told that I had to do. Now, my phone won't boot. It gets to the S screen, pulses for while, and goes dark.
This is what I backed up for, right? But I can't seem to boot into ClockworkMod recovery. Pressing power+volume keys just gets me into the normal Android recovery screen. And since I don't want to reinstall packages, try another reboot in vain, or delete all user data, I'm kind of at a loss.
Can anyone help me?
If i've understood correctly, Clockwork doesn't play well with ext4, so that may be what you're running into. Shouldn't be too big of a deal, just use ODIN3 to reflash JF6 (DON'T MASTER CLEAR- just flash JF6). You should be able to do this by 1. Starting ODIN3, 2. Get your phone to the stock recovery screen and then hooking up your USB cable, 3. Start up an ADB Command Line and type in 'adb shell' (enter) and then 'reboot download' (enter). Your phone should reboot into download mode (big yellow triangle) and be picked up by ODIN3. Click 'start' on ODIN3 and wait for it to reflash JF6. When it's done, try downloading the update again. If it doesn't take (don't be surprised) just download it from the development forum and flash it using Clockwork. (You'll have to re-root, re-download and install Clockwork). Once you have JH7, re-root, re-download and install Clockwork and Titanium again, and then use the batch method to put your apps and settings back on. Let me know if you run into anything and I'll see if I can help.
-ok, just double checked, and you'll run into permission issues if you try to type 'adb shell' and then 'reboot download'. Instead, just type in 'adb reboot download' at the C:\...\tools> prompt. It gave an 'error: protocol fault <no status>' message in the command window, but the phone went into download mode 3 out of 3 tries.
had a similar issue last night. went from cog 2.1 back to JH7 and didnt fix the voodoo issue which left me in the same position. you just have to reflash to JF6 with Odin and you'll be set.
1. make sure you have the usb drivers installed
2. open odin
3. turn phone off (pull battery if needed, and replace)
4. hold both volume keys while inserting usb cable to phone (will put phone into download mode, huge yellow triangle on screen)
5. odin should now recognize the phone/com port.
6. hit 'Start', not Master Wipe or w/e the other button is.
after all said and done you'll have flashed JF6. Now re-root phone, download rom manager and restore one of your backups and you're back in business. good luck.
I just found myself in this same position, but I removed the EXT2 lagfix via SL4A and ended up with a phone that had to be reflashed - it went dead, wouldn't get past the glowing S, then black screen. Reflashed, I then recovered later via Titanium backups.
Then get this... once I flashed with Odin, I got hit with an OTA update... which I cancelled. Then I was dealing with an almost bricked phone. So I had to finagle my way into getting to where Odin would reflash the phone (I was lucky) and then I went straight to Cognition 2.1 to avoid the OTA, and I've been setting up everything else since. I've recovered my apps, et al... and tweaked it like I once had it.
There should be a way to avoid this in the future - I hate setting everything back up - but I got hit with a SL4A issue too.
Thanks a lot, guys. I'm going to use Odin3 as soon as I get home from work! Then, should I just try SL4A again to un-lagfix, or what? It's my understanding that the update doesn't play well with ext4.
Nope, once you've reflashed JF6 with ODIN3, you should be back to stock with no SL4A if i'm not mistaken. If your goal was to just have JH7, i'd make sure to delete any folders SL4A might have put on your INTERNAL SD card storage (don't know if it does, never used it), and don't do a nandroid restore- that will put you back to where you were right before the problems started. Your apps and settings should be ok, just get to JH7, reload your apps and settings, THEN do a nandroid backup before you try anything else so that you basically have a fresh JH7 install with all your apps and settings as a starting point for future tinkering.
-Ok, just read a post from Rajendra82 in the Development forums discussing this type of thing. It's the "Noob needs your help to understand" thread, and on page 2 he discusses this same situation in pretty good detail. I'm pretty sure I read that SL4A gives you two choices to lagfix- ext2 and ext4. If you chose ext2 you'll probably be ok, but if you chose ext4 you may infact still have issues with trying to use ODIN3. Go read that thread for more info, maybe even PM Rajendra82 since he seems to have a pretty good understanding about this. Good Luck.
Thank you, samoled! It's all fixed. Good lord, what a pain in the backside.
I (eventually) managed to flash a fresh JF6 install with Odin3. Tried the update the regular way; it failed. So I rooted, then used ClockworkMod to load the update from my SD card. Rooted again, got Busybox, enabled app sideloading, got Titanium backup, and finally ran the batch and restored everything. Phew.
I hear voodoo's a much less buggy way to do the lagfix (I used the Tayatumi update.zip last time). I think I'll use that - after backing up, of course!
No problem at all man, just glad I could help. Happy Modding!!!
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!
I've been searching and I should add that my bootloader is not unlocked
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !
1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons
Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.
Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.
I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!
Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??
well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"
Do you have Busybox installed?
Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?
Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.
Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.
I have a rooted droid 1 and I want to install cyanogenmod 7.0.3. I got rom manager the free edition and I flashed clockworkrecovery. When I tried to install the rom from sd card, it just rebooted and went to a triangle with an ! and that's all. I waited, but nothing happened, so I did a battery pull and rebooted my droid. I flashed clockwork again, because a friend told me it probably didn't flash properly. I got the success notice again. Then I tried again, but this time my phone just rebooted. What am I doing wrong
That's really weird... I just put that ROM on my D1 and it installed perfectly, even though it took 3 tries. I followed a guide on how to install it using ROM Manager (since it was my first time). Since I am a noob here at XDA, it won't let me post a link to the website, but I'll copy and paste the tips for you.
Problem During Flashing?
If after the "Reboot and Install" step, you immediately get a picture of Android with a big exclamation point, most likely it means the ROM image you downloaded was not cryptographically signed by the developer (which happens if they were in a hurry to release or simply don’t use encryption).
That’s OK – you can fix this by:
clicking the exclamation point screen, which goes to the ClockworkMod recovery menu or simply rebooting into recovery manually (that’s one of the options in the ROM Manager). Alternatively, you can boot into recovery by holding Power and Home buttons together while powering up your phone
selecting the option that says "install zip from sdcard"
toggling the "toggle signature verification" option to turn the verification off (it should say "Signature Check: Disabled")
giving flashing another try by selecting "choose zip from sdcard" and selecting the right ROM, just like before.
This is on the Android Police forums posted by Artem Russakovskii. I don't take credit for this.
Goodluck!!!
Adam
Thanks.
Anyways, I had to flash the latest version of clockwork. Then it worked
Sweet! Well I welcome you to the wonderful world of custom ROMs then.
Sent from my Droid using XDA App
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.