Related
After flashing my first ROM on my new Asus TF300T I attempted to do a restore from CWM recovery and I just get bootloop. I have tried factory reset and wiping cache and dalvic but to no avail. The only way to get my tab working again is to flash back to AOKP. I have read the thread by d_crossfader but It doesn't seem to be the solution to get nand restore to work to get me back to stock. Please Help.
OK so I solved this. Sort of. Flashed a cyanogen rom and then was able to restore but then no wifi. I assume this is a kernel problem. Gonna try going to stock kernel. Can someone tell me how to backup the kernel? do I need TWRP recovery to do this? Is anyone working on an amon-ra style recovery?
Same here but solved it
I had the same problem.
i was on US.29 and wanted to upgrade to US.30 so i said before i upgrade lets try a custom rom so i tried 1) SKANKWICH CM9 KANG build and then 2) [AOKP][Build 40][4.0.4] Unofficial AOKP. I found that both builds was similar but didn't like (for my reasons) and wanted to stay as close to stock. So i tried to restore my 2 hours ago, nandoid backup. Bootloops was the result. Wiped data,factory reset,dalvik cache, and restored 5 times but no hope.
Solved this by installing the SKANKWICH CM9 KANG build from the recovery and when the device started, i downloaded the US.30 and unzipped it to internals storage root. Then restarted the tf300t in recovery,wiped data,factory reset and installed US.30 zip and everything now is fine.
I dont know if the reason is that before the first rom install i forgot to restore (copy paste) the original build.prop file.
Also finaly the machine was unlocked,unrooted without any custom recovery.
I think this is just a bug with nandroid restores, saw a few people having problems.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
i downloaded the US.30 and unzipped it to internals storage root. Then restarted the tf300t in recovery,wiped data,factory reset and installed US.30 zip and everything now is fine.
Click to expand...
Click to collapse
Good to hear! This is what worked for me too.
I then had to flash recovery again and re-root.
I used Thing O Doom's method because his tool claims to solve boot-loops and bricks as well so I figured it would be handy to keep around. Also, it is simple to use.
BE CAREFUL to insert the correct recovery blob if you use his tool though!!!
Here's the link to his thread:
http://forum.xda-developers.com/showthread.php?t=1681155
Will Try
I will try peri-04 one click root to see if i still get bootloops after nandroid restore. But where do u find the recovery blob u said u used for your Tf300?
pankobios said:
I will try peri-04 one click root to see if i still get bootloops after nandroid restore. But where do u find the recovery blob u said u used for your Tf300?
Click to expand...
Click to collapse
Under "CUSTOM RECOVERY" section in the index thread:
http://forum.xda-developers.com/showthread.php?t=1697227
After you get the blob file rename it to "recoveryblob" and replace the one that comes in the PERI folder.
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hey guys:
I recently wiped my tab clean because it kept bootlooping, but I accidentally wiped my ROM as well as my storage. So right now, my tab is stuck at the unlocked screen, and I'm not sure what could have caused the bootloop problem in the first place.
Rooted, unlocked, running CleanROM 2.7.2 with Data2SD and Clemsyn kernel. I kept fsync enabled precisely so that my system would be more stable, but it appears not to be the case. Right now, my priority is flashing any OS/ROM onto my tab so I can get it to start booting. Any help? I'm really hoping this isn't a brick scenario.
Hohumhurrdurr said:
Hey guys:
I recently wiped my tab clean because it kept bootlooping, but I accidentally wiped my ROM as well as my storage. So right now, my tab is stuck at the unlocked screen, and I'm not sure what could have caused the bootloop problem in the first place.
Rooted, unlocked, running CleanROM 2.7.2 with Data2SD and Clemsyn kernel. I kept fsync enabled precisely so that my system would be more stable, but it appears not to be the case. Right now, my priority is flashing any OS/ROM onto my tab so I can get it to start booting. Any help? I'm really hoping this isn't a brick scenario.
Click to expand...
Click to collapse
Can you still access recovery? From recovery I've able to reload the stock update files which extract and load a blob that completely rewrites my system.
If not, can you access fastboot? Load it into fastboot and then re-install a recovery, and then from there use that to either install the update or reload your rom.
d01100100 said:
Can you still access recovery? From recovery I've able to reload the stock update files which extract and load a blob that completely rewrites my system.
If not, can you access fastboot? Load it into fastboot and then re-install a recovery, and then from there use that to either install the update or reload your rom.
Click to expand...
Click to collapse
I can still access recovery, but am not sure how to or which stock files I'm supposed to extract. I've been looking into fastboot right now, but don't have the SDK installed on my computer and frankly, I'm just not sure what to do with it.
Ideally, accessing the stock files and loading a blob would be the best solution, but I'm unsure how to proceed. Thanks for the advice, as I'm frantically trying to find a solution as the tab won't shut off and I'm afraid it's going to overheat.
Hohumhurrdurr said:
I can still access recovery, but am not sure how to or which stock files I'm supposed to extract. I've been looking into fastboot right now, but don't have the SDK installed on my computer and frankly, I'm just not sure what to do with it.
Ideally, accessing the stock files and loading a blob would be the best solution, but I'm unsure how to proceed. Thanks for the advice, as I'm frantically trying to find a solution as the tab won't shut off and I'm afraid it's going to overheat.
Click to expand...
Click to collapse
I don't understand your issue, if you still can access your twrp, then just reflash your cleanrom 2.7? If you want to bypass data2sd for now, just flash clemsyn_data2sd kernel, you should able to boot up.
buhohitr said:
I don't understand your issue, if you still can access your twrp, then just reflash your cleanrom 2.7? If you want to bypass data2sd for now, just flash clemsyn_data2sd kernel, you should able to boot up.
Click to expand...
Click to collapse
Like a fool, I wiped both internal and external storage. So I don't have the zips or backups I had on my sds. I've tried removing the sd and putting backups and zips I have on my computer, but TWRP doesn't recognize the device since I have no OS.
Hohumhurrdurr said:
Like a fool, I wiped both internal and external storage. So I don't have the zips or backups I had on my sds. I've tried removing the sd and putting backups and zips I have on my computer, but TWRP doesn't recognize the device since I have no OS.
Click to expand...
Click to collapse
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
buhohitr said:
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
Click to expand...
Click to collapse
Also, my tablet kept bootlooping when trying to install the same setup (2.7 w/ data2SD) when using an SD card formated with minitool...using GParted worked like a charm the first time.
buhohitr said:
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
Click to expand...
Click to collapse
Thank you, good sir. Worked like a charm. Only problem is a boot loop that persists when I try to flash CleanROM 3.0.1, but I'll probably figure out what's wrong eventually.
Hohumhurrdurr said:
Thank you, good sir. Worked like a charm. Only problem is a boot loop that persists when I try to flash CleanROM 3.0.1, but I'll probably figure out what's wrong eventually.
Click to expand...
Click to collapse
Hey, during the install, did you selected nexus boot animation? if you are, try to clear cache and dalvik cache then reinstall, but this time select Asus stock boot animation see if it's ok.
buhohitr said:
Hey, during the install, did you selected nexus boot animation? if you are, try to clear cache and dalvik cache then reinstall, but this time select Asus stock boot animation see if it's ok.
Click to expand...
Click to collapse
Reverted back to Stock and flashed CleanROM 3.0.1 with Asus Stock boot animation this time. Yes, I was using the Nexus boot animation before, but Asus Stock isn't making a difference. Same boot loop. Reverting back to Stock until I can figure out what's wrong. I've been checking to make sure all my stuff is updated and nothing seems to be out of order...
Hohumhurrdurr said:
Reverted back to Stock and flashed CleanROM 3.0.1 with Asus Stock boot animation this time. Yes, I was using the Nexus boot animation before, but Asus Stock isn't making a difference. Same boot loop. Reverting back to Stock until I can figure out what's wrong. I've been checking to make sure all my stuff is updated and nothing seems to be out of order...
Click to expand...
Click to collapse
I think if you flash cleanrom 2.7.2, then flash 3.01, it should work.
buhohitr said:
I think if you flash cleanrom 2.7.2, then flash 3.01, it should work.
Click to expand...
Click to collapse
It does work, much appreciated.
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
cesar_cjx said:
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
Click to expand...
Click to collapse
Q1: I think you can just flash the new recovery via the current recovery if you have the new recover zip file.
Q2: Kat Kiss works fine for me.
Q3: If you want to completely return to stock, you would have to use NVFlash. There are tons of instructions on the Dev thread. I primarily use Tubuntu for flashing with NVFlash. [http://forum.xda-developers.com/showthread.php?t=1995157]
You can find other images as well. I used a stock image once to RMA the tablet but now I'm not sure where I got it. This method will ensure that every bit in your memory is exactly as it left the factory. Including the bootloader, recovery partition and everything else.
Q4: Refer Q3.
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
*Detection* said:
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
Click to expand...
Click to collapse
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
stache12 said:
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
Click to expand...
Click to collapse
Yep, so long as you reboot into your ROM after flashing the new TWRP before booting back into recovery
Thanks for your reply, i will tray soon. So i want to clean the asus stock room to see if battery goes ok, i tried wipe data, cache, dalvik, with cwm, but nothing.
If i install twrp what more options can i try before change the rom? what more wipe do i need?? and finally, if i change the rom, is possible to go back to asus stock just flashing from recovery? or how should i do?
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
46999589
*Detection* said:
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
Click to expand...
Click to collapse
Thanks!! I will try, but apart from wipe system(rom) what more wipes can i try without erase the rom?..I think not, because a week ago the battery was perfect working...i hope so.
CACHE,
DALVIK CACHE,
FACTORY RESET,
INTERNAL STORAGE,
FORMAT DATA
Only other 2 options are SYSTEM & EXTERNAL STORAGE
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?