Restored the Tablet TF101 back to stock rooted and everything worked. Installed CWM Did factory reset system wipes etc. Tried to install 3 different CM 10 all failed bad installation. Tried to installed the newest TWRP same thing I can't seem to install any rom from the external or internal just keeps saying bad?
What errors did TWRP tell you?
For TWRP why not download the GOO app from the playstore and find the option in the menu to allow it to install the open recovery script for you?
Had similar issues with my S4 with a particular rom but youve tried a few so i doubt its down to the download sites.
You may have to format the emmc and see how that goes as a last resort. (just make sure you have a rom placed on a micro sd as it will completely wipe the TF again but still keep your recovery)
Related
So i decided one day to root my device i happened to do it with CWM i am currently running CWM 6.0.3.2 that turned out fine so i install a couple of roms like changing the animation of the boot screen ( running mario and i changed the font and updated to 4.3 which it was normally 4.2 i tried 4.4 but it wouldnt install so i left it then i decided to upgrade to taktik my device cwm wouldnt read my sd so i formatted it ( i dont care about the app data or anything just pictures and music so i backed it up to my computer )
heres when it started acting funny i did what was told to install taktik on a forum but my device still had the data on it after i rebooted (i thought that was abnormal but now i know it was supposed to do that i think because it still stays after i factory reset) so i go into cwm and i format all the data,the system, sd card, external sd, cache and everything else under mounts and storage i reboot and now im here
i can install a certain taktik rom and certain taktik gapps and it will boot up but it has bugs or glitches like a MF and it wasnt doing that when i had first installed taktik
Will thank all those who help bring my device back to normal
Are you still having issue
hisensesero7prouser said:
So i decided one day to root my device i happened to do it with CWM i am currently running CWM 6.0.3.2 that turned out fine so i install a couple of roms like changing the animation of the boot screen ( running mario and i changed the font and updated to 4.3 which it was normally 4.2 i tried 4.4 but it wouldnt install so i left it then i decided to upgrade to taktik my device cwm wouldnt read my sd so i formatted it ( i dont care about the app data or anything just pictures and music so i backed it up to my computer )
heres when it started acting funny i did what was told to install taktik on a forum but my device still had the data on it after i rebooted (i thought that was abnormal but now i know it was supposed to do that i think because it still stays after i factory reset) so i go into cwm and i format all the data,the system, sd card, external sd, cache and everything else under mounts and storage i reboot and now im here
i can install a certain taktik rom and certain taktik gapps and it will boot up but it has bugs or glitches like a MF and it wasnt doing that when i had first installed taktik
Will thank all those who help bring my device back to normal
Click to expand...
Click to collapse
I noticed this is an old threat. Many times it is best to install custom roms, boot into android, then go back into recovery and install gapps. Some roms need to be set up once before they can accept the gapps.
Not sure if that was your issue, but other might find it helpful. It solved a lot of my problems.
If you still have an issue write back with what you have tried.
OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
friedsonjm said:
OK, I've done this many times to many devices, never had this happen before. Unlocked, rooted, TWRP installed, have tried two different ROMS, Slim and CM11, tried both direct download and from my PC then transferred, can't get a custom ROM to install, keeps erroring out while trying to install ROM from TWRP, even though I wipe System, Dalvik, and Cache. 'Error updating binary executor in zip'
thoughts?
EDIT: on twrp 2.5.0.0 - maybe need a newer version?
Tried 2.6.3.0 - it won't wipe dalvik, cache, or system? Actually, it cant see or mount any drives...
And CM Recovery has the same issue...?
This worked:
http://forum.xda-developers.com/devdb/project/dl/?id=3727
Click to expand...
Click to collapse
If you are trying to install CM11, which is based on KitKat, looks like everyone says to use the Omni version of TWRP. Here's a link to that zip in my Dropbox. https://www.dropbox.com/s/cctivhx2kcpwnfz/TWRP-TF300T-2_7_0_1.zip. Install is different for it though. Put the zip file on a micro SD card or in the internal storage and then boot into whatever custom recovery you have working (I usually go back to stock and flash TWRP 2.4.0.0 or 2.4.4.0 whenever I run into problems. I found a great TWRP recovery installer someone made for Windows, here's that zip. https://www.dropbox.com/s/jut7sytp8n7c94u/recoverytf300t4.2.zip). Once in recovery, go to Install and flash the Omni version 2.7.0.1. After that finishes, reboot to system so that the Omni version can complete installation (you'll see the blue install bar, like what shows when you Fastboot install a recovery). Your tablet will reboot after that so I usually hold Volume Down when the display goes dark so that I can go into the new recovery. I've also recently found 2 "new" recoveries that work fairly with CM11, probably due to the fact that they are based on CM Recovery. I'll include the links for you. They both get installed via Fastboot. Hope this helps!
Philz Touch Recovery - https://www.dropbox.com/s/eea29g652s34p76/philz_touch_6.19.3-tf300t.img
Flatline Recovery (from the process of Wheelie/NVFlash for Jelly Bean, which I recommend you do if you haven't yet. It's been a life saver.) -https://www.dropbox.com/s/xvn7tg3tt0pxo8s/flatline_tf300.img
I started to install pacrom on my verizon galaxy s4 and am havings troubles. I'll start from the beginning.
I rooted the phone via Towelroot app and checked it with rootchecker.
Then i downloaded the following.
downloadandroidrom.com/file/GalaxyS4/SCH-i545/roms/PACMan/pac_jfltevzw-nightly-20130913.zip
downloadandroidrom.com/file/gapps/PA/pa_gapps-full-4.2-20130610-signed.zip
androidfilehost.com/?fid=95784891001603023 this is safestrap for "FOR USERS OF MJ7/MK2" IDK the difference between that and ME7/MI1 but i used MJ7/MK2
From here I opened up the safestrap app and installed the recovery and loaded it up. I left it on the stock rom slot while i continued to wipe everything and install the rom and GAPPS. This was a mistake, however, because i it bootlooped. I tried wiping and installing many different ways and still ended up with a bootloop. I realized in needed to use a rom slot and set that up. I wiped all the necessary things and installed the rom and GAPPS. Still it bootlooped. I have even tried to install without GAPPS with no avail. I forgot to make a backup of the stock and the stock slot just bootloops the pacrom boot screen. I cant find a way to add filed from my computer because whenever i connect it during the boot screen it shows up as a disc drive on my computer. Normally i would choose USB settings and make it where i can transefer data files, but i cant do this. I really need some help with this as I have done all I know to do. The downloads may be the problem, but from what i understand they are the correct ones. Thanks
Download this rom, move it to your phone and flash with recovery.
If you can't get the file on the phone I will help you out.
Hi,
okay, so i had a rooted samsung j500f phone running android lollipop 5.1.1 stock rom (downloaded from sammobile). I was using Apps2Sd for linking my apps to the external SD Card. Few days ago, my phone turned off on the battery getting empty and when i turned it on, all linked apps were missing. I was getting an error that "Disable mount namespace seperation in Chainfire SU". I did that but nothing happened and the App2Sd was unable to remount 2nd partition.
Frustrated, i contacted their developer who suggested to reinstall SuperSU. So, i opened the SuperSU app (chainfire) and went to settings and then chose the option "Reinstall from google play store". It uninstalled SuperSU which i later downloaded from Google Play Store. After it had installed, it asked to install binaries and gave me two options:
1) Normal in-app method
2) TWRP/CWM recovery method
I chose the second one (because i had TWRP installed).
Then my phone rebooted into recovery and ran a few scripts. However it later stated that there is no root on your device (which i believe may have been removed when SuperSU was uninstalled). TWRP gave me options to reinstall SuperSU but it did nothing. I downloaded the latest SuperSU zip file from chainfire site and tried to flash it. But the script would show failure. Now, my phone wouldn't boot into the system. Only into recovery mode.
Being really pissed, i decided to do a factory reset. So i did a factory reset from within the TWRP (normal wipe). Still, my phone wouldn't boot but would go to recovery. So i got angry, went into the Advanced wipe option in which i selected dalvik cache, internal storage, SYSTEM and wiped them all.
Now on trying to reboot, TWRP would say "There is no OS installed. Are you sure you want to continue?"
I knew i had messed up my phone and so i decided to flash it with stock rom again using ODIN. But, whenever i try to go into download mode it gets stuck on the Samsung Galaxy J5 Logo screen with "ODIN Mode" written on the top left along with a couple of other details such as Knox void 0x1(4), Rom statusfficial, etc.
Clearly, i am unable to flash using ODIN as my phone isn't being able to go to Download Mode. ODIN doesn't detect my device.
So i thought of flashing the stock rom using TWRP, which failed.
I also have a TWRP Backup but TWRP won't let me select it. I have the backup folder on my SD card.
Now my phone has just TWRP, Can't get into download mode using the key combinations or through TWRP bootloader option which on selection gives me the "No OS" error. I can't boot my device up as it goes into recovery.
Kindly help as soon as possible.
Thank you.
If you wipe the SYSTEM Partition, then of course that no OS is installed. Like a Hard Brick. Good Job...
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So, I have years of experience rooting and flashing Samsung phones with minimal adb experience. My buddy from work asks me if I can try to fix his shield tab that he F'd up trying to flash a rom on. Come to find out he never unlocked the bootloader or flashed a recovery or rooted the dang thing, just tried to flash the rom over stock like a numbskull. We thought it was dead forever because the only thing that would mount or connect in adb was the side load through the stock recovery. So, I finally got it to connect to fastboot (don't ask me how, I don't know), unlocked the bootloader, and flashed twrp. Now it won't flash supersu in adb sideload, so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one? I have no idea which version bootloader, kernel, or os is, or was, on this device, I'm not familiar with any of the roms for it, and I'm not sure what prerequisites there may be for some of them....
Thanks for the help!
rom fiend said:
it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one?
Click to expand...
Click to collapse
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
OverBit said:
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
Click to expand...
Click to collapse
I can't wipe them because they won't mount. It's as if the partitions were erased completely. Not like the partitions were wiped, but like they don't exist at all anymore...
What do you mean by changing the file format? Format of what?
rom fiend said:
What do you mean by changing the file format? Format of what?
Click to expand...
Click to collapse
TWRP, wipe ,Advanced wipe
If that doesn't work just try installing a rom, boot it
If that doesn't work try this
Tried all recovery options and tried flashing bliss 6.2 with no luck. It says that it flashes successfully but also shows some errors about not being able to mount the system and data partitions. Then when I try to reboot it gets stuck at the nvidia logo (this is the closest that I've gotten to booting a rom). I can provide pictures if you want. I'm going to try the steps that you linked to as soon as the files download.