So no matter whatever recovery I use (CWM, CWM Touch, TWRP), I always get errors saying "E: Can't open....". I just got this tablet off ebay after wanting it for a long time and I've been looking for the past 5 hours trying all these methods I see online, but I haven't seen this problem before. All I want is JUST root on the STOCK ROM so I can remove what I don't use with Titanium Backup. That's it! But I don't know why this has to be so complicated compared to devices I've owned in the past. SO if ANYONE can give me an idea of what to do, it would be greatly appreciated.
Wallex said:
So no matter whatever recovery I use (CWM, CWM Touch, TWRP), I always get errors saying "E: Can't open....". I just got this tablet off ebay after wanting it for a long time and I've been looking for the past 5 hours trying all these methods I see online, but I haven't seen this problem before. All I want is JUST root on the STOCK ROM so I can remove what I don't use with Titanium Backup. That's it! But I don't know why this has to be so complicated compared to devices I've owned in the past. SO if ANYONE can give me an idea of what to do, it would be greatly appreciated.
Click to expand...
Click to collapse
What bootloader v. are you on & what recovery v. did you flash?
Ti2 said:
What bootloader v. are you on & what recovery v. did you flash?
Click to expand...
Click to collapse
So when I boot into bootloader, it says:
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.0-20130225" A03"
As for recovery, I've tried all sorts of them to no avail. IF I get a choice in the end of all this, I prefer CWM but if not that's no big deal. Like I said, all I want is the stock ROM with root. That's it. Luckily I haven't bricked it yet... but I've tried about three:
CWM Touch
TWRP 2.5
TWRP 2.3-something?
Currently have CWM NON TOUCH-based v6.0.2.3
If you could provide me with direct links so I don't get the wrong versions that'd be great.
*edit: Also worth noting, with TWRP 2.5, I was able to install zip's AFTER going into MOUNT and mounting /system (BUT NOTHING ELSE WOULD MOUNT!) and then it would read the zip off /system, which APPEARED to be my SD's contents. BUT even though it said "Successful" it actually did nothing because it wouldn't mount.
Wallex said:
So when I boot into bootloader, it says:
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.0-20130225" A03"
As for recovery, I've tried all sorts of them to no avail. IF I get a choice in the end of all this, I prefer CWM but if not that's no big deal. Like I said, all I want is the stock ROM with root. That's it. Luckily I haven't bricked it yet... but I've tried about three:
CWM Touch
TWRP 2.5
TWRP 2.3-something?
Currently have CWM NON TOUCH-based v6.0.2.3
If you could provide me with direct links so I don't get the wrong versions that'd be great.
*edit: Also worth noting, with TWRP 2.5, I was able to install zip's AFTER going into MOUNT and mounting /system (BUT NOTHING ELSE WOULD MOUNT!) and then it would read the zip off /system, which APPEARED to be my SD's contents. BUT even though it said "Successful" it actually did nothing because it wouldn't mount.
Click to expand...
Click to collapse
did you bother searching or reading before you went to unlock it? i see nothing you posted about the modded recovery for the tf300t . that you need with new jb. sounds to me like your screwed by flashing the wrong recovery with the new boot loader. so unless im wrong i think you got your self a paper weight.
kaos420 said:
did you bother searching or reading before you went to unlock it? i see nothing you posted about the modded recovery for the tf300t . that you need with new jb. sounds to me like your screwed by flashing the wrong recovery with the new boot loader. so unless im wrong i think you got your self a paper weight.
Click to expand...
Click to collapse
Too bad you're wrong.
Finally got it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=2187982
TWRP 2.4.4.0
Wallex said:
Too bad you're wrong.
Finally got it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=2187982
TWRP 2.4.4.0
Click to expand...
Click to collapse
Too BAD he's wrong??
LUCKILY he's wrong!! :good:
Related
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
infamousjax said:
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
Click to expand...
Click to collapse
Relock then try the RUU
http://forum.xda-developers.com/showthread.php?t=1761429
Sent from my HTC One X
Or push twrp recovery and flash again.
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
infamousjax said:
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
Click to expand...
Click to collapse
You should not use cwm, use twrp, CleanROMs op stated that, try pushing twrp, and flashing before you ruu, it causes issues that hasn't been fixes yet.
Sent from my HTC One X
Can't use clock work. Use team win.
If everybody is saying use TWRP and the person is still using CWM; one has to wonder how intelligent that person is.
mankind 0 monkey 1
infamousjax said:
Now it says it cannot mount the sdcard...
Click to expand...
Click to collapse
This is a known issue with CWM, mount SD simply does not work. Use TWRP like everyone is saying.
Did you try wiping anything in Aroma? Because that is a known issue as well (results in soft bricks). Only wipe in recovery, and use Aroma only for picking the various ROM options (not for wiping anything).
Got it working -- used fastboot to flash TWRP and formatted SD card and now everything is lovely.
I've been flashing CleanROM since the beginning before there was TWRP and never bothered to switch recoveries. I guess I should have read the notes more closely.. oh well, no harm done
thanks for the replies and help
Hi guys,
My tablet is rooted (and back to fully stock ROM from Acer's website). I updated OTA just a moment ago, and I was totally shocked to see the message "Booting kernal recovery image - Recovery verified failed..."
I tried rebooting, fastbooting,....they all don't work. How should I move on? What can be done now?
Please do help me. I need the tablet, and never knew such a situation could arise.
Thanks!
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
got the same problem. how do you get into fastboot again?
Liquidator said:
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
Click to expand...
Click to collapse
I assume yes, it is locked since I went back to a fully Stock ROM (which includes the locked bootloader?). But what has a bootloader got to do with an OTA update?
What I mean by they all don't work is that, even when I try shutting down, rebooting or enter stock recovery using the volume keys + power button, nothing works. Absolutely nothing! The screen just stays there.
I then thought, let the battery run down and maybe I can enter stock recovery and flash the zip for the stock ROM again from my SD card, but this doesn't work. The tablet just boots again to that same screen, with a message saying wiping off update cache and something to do with cdm.
I fear my device is gone. If anyone can lead me to getting back my device up and running, as a small token of appreciation, I will provide you with either $10 via PayPal or a $10 Google Play Gift Card code. This is really important for me, and I can't seem to find any help on this matter on the Internet.
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Temporeiches said:
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Click to expand...
Click to collapse
No, we don't have a same problem. I don't have CWM on my device, and I am doing an OTA. I can do absolutely NOTHING other than stare at the error message in red ink and the static Acer logo.
Okay sorry. Just want to tell you that I flashed the stock rom and so I lost CWM. If i find a way to fix mine ill tell you and it might help you.
As an update, after letting the tablets battery drain out and then charging it back up, the message I am seeing now is a little longer:
Erasing cache before SD update...
SD Update cmd: recovery
--Update_package=sdcard:update.zip
Booting recovery kernal image
Recovery verified failed...
PS: If anyone can make sense of this message, please tell me.
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Liquidator said:
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Click to expand...
Click to collapse
So how do I get this latest firmware? I can't find on acers website.
himmatsj said:
So how do I get this latest firmware? I can't find on acers website.
Click to expand...
Click to collapse
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Temporeiches said:
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Click to expand...
Click to collapse
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
himmatsj said:
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
Click to expand...
Click to collapse
Try this:
Here's how to get into fastboot (bootloader) manually:
Turn off your tablet
Hold the Volume Down (**) button and press the Power button
As soon as the tablet vibrates, let go of only the Power button (keep the Volume Down (**) button pressed) and immediately start switching the Screen Rotation Lock slider back and forth.
If this works continue.Connect your device to PC. Open your device manager look for fastboot under other devices and right click on it and select update driver. Then click browse my computer for driver software and locate the folder i could send by mail, just ask me. Click Next, and it might say it is a threat, but click continue (its safe as I edited it myself) and let it install. Next download http://forum.xda-developers.com/showthread.php?t=1661324 and use it to unlock bootloader. Next follow instructions on http://forum.xda-developers.com/showthread.php?t=1866378 Then place a ROM from NoThrills on an external sdcard, and insert it into the tablet. If the tablet is shut down get into CWM through the key combination for ICS bootloader power and ** sound button and for JB bootloader
* PowerON+Vol-
* At the first vibration release PowerOn, keeping Vol- pressed
* At the second vibration release Vol- and press Vol+
Next flash the rom from external sdcard and reboot. Now things should work.
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
himmatsj said:
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
Click to expand...
Click to collapse
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
malos1984 said:
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
Click to expand...
Click to collapse
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
himmatsj said:
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
Click to expand...
Click to collapse
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
malos1984 said:
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
Click to expand...
Click to collapse
Yeah, I hope someone who is directly involved in these things like NoThrills can come and enlighten us.
Thread moved to Q&A
MD
Problem SOLVED!
Hi guys,
For all those having the "recovery verification failed" error while trying to do OTA, I know the fix!
The key is, you need to restore stock recovery manually. There's a zip file of the stock recovery here (at the bottom of the first post). Just restore stock recovery as per usual.
Steps to follow in brief:
1) Install stock recovery manually from HERE
2) If your's isn't the stock Acer ROM, download the correct ICS version for your region from HERE (place it as update.zip and follow steps as per normal to flash)
3) Go to settings>apps>all apps>systemupdater, and then clear data/cache.
4) Reboot tablet and you should get an OTA notification.
5) You're done!
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.
I think I screwed the pooch. I finally took the plunge and Rooted/S-off (with Sunshine) and installed a custom recovery. Issue is, I think I had TWRP installed and then installed Philz_touch_6.43.6-m8. Now, I can't get out of a recovery boot loop. I'm not 100% sure how I managed this but now when I reboot, I'm getting the red text at the bottom stating "this build is for android development purposes only" and boots me into TWRP. If I try to fastboot flash recovery and install the Philz recovery again, it does it's business, boots into Philz and when I go to reboot Philz it reboots into TWRP. Am I hosed? Any help is greatly appreciated. I was hoping by reflashing Philz it would remove the ability to boot into TWRP. This sucks!
Thanks in advance.
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
You probably installed twrp into the stock partition, glad you got it fixed.
upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
I know you fix it...but did you 1st flash twrp via the terminal emulator?
Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!
upnsmoke67 said:
Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!
Click to expand...
Click to collapse
I asked bout terminal emulator because twrp has the partitions mapped wrong. So if you do that it will flash to the system one which is what sounded like you did.....I been with HTC forever just a quick tip always fastboot flash if you can as it is the safe way..never use apps or emulator to flash...
OK cool Tigerstown... many thanks for the tip!
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
ProSniper54 said:
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
Click to expand...
Click to collapse
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
NaminatoR1254jaime.sier said:
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
Click to expand...
Click to collapse
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
ProSniper54 said:
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
Click to expand...
Click to collapse
Probably because you have custom recovery still or you are rooted.
The android red guy happens bc you are rooted (it'll happen even if you have stock recovery).
To system update, you have to be without custom recovery AND unrooted.
EDIT: Im theoretically speaking. I am rooted, therefore, I dont update via OTA.
i tried to recover to factory but i am stuck at system.img which dun seem to be copying into my tablet i manage to flash twrp in and wat else can i do to make it working again?
thanks