Related
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!
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota
There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk
Somewhat new to this, but I successfully rooted my 6633 which has stock 4.4.4 (Which I re-installed the stock firmware fresh). Afterward I Installed TWRP and attempted to create a custom recovery (I could never boot into recovery and tried many times and many ways), and assume I must at least create a custom recovery. Anyway, in attempting to create the recovery I tried to flash the img file. However, I could not find an image for the 6633 and (stupidly) flashed the image for the z3c. But other than freezing the phone the first time I shut it down, everything on the phone works fine. But a recovery was never created. I then found an img for the 6633 and tried to flash it but simply got an error message saying that "Failed remote: image is not a boot image". Apparently either the original mistakenly loaded (z3c) image won't let me flash another over it (unlikely, since it may have never even loaded) or (more likely) the new correct image is bad or corrupted. It is called "bootZ3dualmonxtest01.img" and was downloaded from another site. Searching this site I did find a kernel for the Z3 6653 but there is not any kernel for the 6633.
Again the phone works fine and I can do some file management things in the root, but the whole reason for doing this rooting process is so I can flash a mod to fix the crappy ringtone volume, that I located in another thread on this forum. It's been a journey & I had a lot of fun learning, but I'm not even sure that, in the end, the mod will even fix the ringtone volume (although posters on that thread claim it works). But that's a whole other issue. (lol). Sorry for the wordiness. I read the forums a lot and tried to be thorough. I know there are a lot of really smart people helping newbies like me. Any help is appreciated.
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
G-FACE said:
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
Click to expand...
Click to collapse
Thanks so much for your reply. However, the Bootloader was unlocked the whole time. In fact, the process did seem to correctly flash the wrong kernel (xperia Z3c). The reason I was trying to create a custom recovery is that I am apparently unable to boot to TWRP. I had read in another forum that the Z3 Dual does not come with a stock recovery and that a custom one has to be installed.
In any case, I followed the instructions to boot to TWRP (which gave a couple of methods), and it continues to just either just boot normally, or it I get an error "Damaged SD Card" and I lose some minor functionality. In that case, the phone won't shut down and I have to hold the power button and up volume to kill it. But then if I power it on, everything is normal. This error sequence only occurs when I try to boot into recovery.
Is it possible that when I flashed the wrong kernel (using the Xperia Z3c kernel) that I created this issue? I assumed that the reason for the error was that there was no stock recovery and one could be created by flashing the kernel image.
There is no stock recovery on Z3.
Here is a custom kernel for D6633, but you need to be on stock 23.0.F.1.74 firmware: http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
You can ask the dev there to prepare for you a custom kernel for another firmware version if you want.
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.
Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.
Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?
Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.
Try flashing blisspop or slimLP.
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good: