Hey, I played several times with alternate ROM. and I realized that I had in mind two systems. Through TWRP I failed to get rid of the old system standard wipe.
So I put in TWRP 3.0.2-0 format the internal memory and chose ext 4 file system and erase additionally Android Secure partition. Then I gave install a ROM (StryFlex LP v4.0 Minimal Edition also via TWRP) installation was normal, and after the restart the phone certainly does not work. Nor recovery via PC Companion and via Flash Tool. The phone does not start in fastboot or flashmode. After connecting the PC phone ever detected in the Device Manager as USB Load, but a moment to be again disconnected. I think there is still some chance of rescue? Sorry for my English is Google Translator
Related
HI,
2 of my PC (Windows 7 64) does not see my transformer in USB Debug mode. I installed the 64 bit Dell driver on each PC. Could someone provide me with some options to try.
Is there a way to completely reset the Transformer to stock without USB or being able to load a kernel from SD card?
2 ways to reset -
If you can boot then go into settings --> backup and reset --> factory data reset.
If you can't, hold volume-down then press power, and wait till wipe data appears, use vol keys to select it.
and search for the Universal Naked Drivers, those may help.
Thanks. That seemed to wipe the user settings and data, but not the recovery app "CWM-based Recovery v5.5.04 roach-tf101-r2". As a result the following happened after I reset.
System reboots
System comes up clean and runs setup (wifi, gmail account, etc).
System downloads firmware update.
System reboots to install update
Android appears and runs for a few seconds
Mesages appear: CWM-based Recovery v5.5.04 roach-tf101-r2
Finding update package, opening update package, Verifying update package
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
At this point the TF still will not install zip from sd card since as you told me before I need a different recover and is not found by the PC with a naked driver.
However, the unit is functional.
Any other options to root and get a new recovery installed and finally a new ROM.
Note: the PC does see the TF if I am in the recovery. However, as soon as boot the TF and enable USB debug the TF us not seen.
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
baseballfanz said:
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
Click to expand...
Click to collapse
I have no problem doing that, but how do I do it if I cannot connect the TF to PC via USB or load a zip file via recovery? Both of these do not work!
Did you update cwm via ROM manager? That's the issue there, you can run Roach2010's fix to fix that.
If terminal emulator app works you can flash a downloaded and extracted
(through es file explorer) recoveryblob with
Code:
su
dd if=/sdcard/recoveryblob of=dev/block/mmcblk0p4
reboot
Then you have working recovery and can either flash ROM or Stock.
Thanks for all the replies.
I finally got it working. It took me forever to understand that having a recovery that could only read from the internal memory was not a big deal. I created a folder on the internal sd and dropped in the zip for the external version of CWM . I rebooted and loaded the new restore and from then on I could load ROMs from my external uSD card. I am now happily running the latest version of Revolver.
Jerry
I wanted to update a Folio 100 that had a stock rom installed, a very old Android version (I think 2.1 or something).
I could not get the usb drivers installed properly in order to do the ADB commands in terminal like most tutorials say. Instead, I managed to install Clockwork loader by SD card.
Then with Clockwork I loaded different .zip files, e.g. cm-10-20121117-UNOFFICIAL-betelgeuse.zip, CM 10 (4.1.2) A5 [AhWz][RIP].zip.
I am not sure what to swipe before or after applying the zips from card. But after I loaded these zips I get a black screen at bootup, right after toshiba logo, I left it like that for over 5 minutes, it doesn't start.
Now if I return to boot recovery menu and I try to do a factory reset I get some errors about mounting, "cannot mount /cache/recovery/log (see attached image).
How can I boot again or return to stock ?
I cannot seem to get the USB drivers to load in windows btw (it never finds a proper device to be installed, just storage device), so if it just works to put a rom on card it would be nice.
Hello,
with CWM 3.0.0.5 you cannot install Cm 10. You have to use the appropriate CWM
try with this installation guide.
http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9
Bye
Instaled Folio 100 usb drivers and booted in download mode
I managed to fix it and install a newer version, it is a huge performance and look improvement from the stock rom of Folio 100.
Just in case others have same problems... my probme(s) were that:
- I could not install the USB drivers for the folio 100.
"debug mode" was enabled but whenever I connected the device it just appeared as a flash storage and in device manager it said that it is already up to date. I used a tool called "usbdeview" to uninstall the device (seen as storage device); then on re-connecting usb cable, windows was looking for Nvidia Tegra drivers, so now I was able to provide proper drivers and it added an "android" device in windows device manager.
- then I realized I was doing some mistakes, I didn't knew that booting in download mode is different than booting in recovery mode, so it has two ways to start it, pressing power+vol_up quick (what I was doing), and more importantly clicking power once then vol_up 3 times, this enabled me to boot in download mode and now the commands in windows command prompt worked (fastboot erase recovery, etc).
From here everything worked as expected (with update steps from these threads), loaded some images, erased partitions, etc.
So it was USB drivers and booting in download mode that confused me.
Hi Guys,
Just thought I'd provide a warning and a fix to a half day ordeal recovering from a soft-brick after wanting to make the switch from TW to WWE.
What made this all go wrong?
I have a Padfone 2 which had the latest TW_A68-10.4.17.15
I have a accidentally turned off adb USB debugging mode
The process:
I unlocked my bootloader using the ASUS official unlocker.
I had then install 2.7.0.1 twrp which didn’t work
Install 2.5.0.0 twrp which did.
Forgot to do a backup which I usually did, but guess I thought that I have done this so many times, nothing would go wrong.
DON’T GET COCKY BACKUP FIRST.
Opted for the easy way out and write to system VIA twrp using zip, which was reported to work.
This installed and didn’t report any error.
After reboot, app.phone and another OS programs crashed constantly and rebooted.
I removed my sim and this stopped the crashed apps, but not the reboots.
I realised I was in a whole world of trouble and it was only at this moment did I realise that I didn’t have USB Debugging turned on. Frantically tried to enable it in between reboots, but failed and was now presented with only a ASUS spinning circle of death, or even better later, only the which ASUS logo before it reached it.
All I had available was fastboot and twrp.
You’d think this was an easy fix, but I didn’t have a usable/original rom on the /data/media a.k.a /sdcard partition.
Note: have a handful of roms including your original rom saved on the phone before trying anything, as this phone has no access to external storage when all goes pear shaped.
I wiped caches, didn’t work.
I then wiped data, which then deleted the only rom I had access to. So I couldn’t even now retry installing from zip.
ADB didn’t work from any recovery including CWM 6.0.4.4
I was at a loss and didn’t know what to do.
The recovery:
Installed twrp 2.6.3.0 was persistent with ADB sideload, even though I didn’t have USB Debugging enabled.
Note: ADB sideload will still work even if you don’t have USB Debugging enabled. It’ll either take a min or two to register on your computer, but if not reboot and reboot again to get it to register.
Sideloaded the wrong firmware file again.
Note: If you are trying to sideload the original firmware, extract the zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip” and sideload the zip hiding within “ASUS” -> “Update” -> “TW_A68-10.4.17.15-0-ota-user.zip”
After another long time trying to get the ADB device to register, finally got a second chance and got back to the original firmware.
Did this deter me from the switch from TW to WWE. HELL NO!!
Enable ADB USB Debugging
Make sure you push the rom WWE to your /sdcard partition
How to do it right.
Load the original recovery attached recovery.stock.img
Reboot into recovery and select "apply update from external storage" and choose the zip file to flash.
This will fail! It's what it's meant to do
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
Upon rebooting to ADB stopped working under the stock recovery. It registered with my computer but the command to repush the WWE rom to /data/media kept failing.
Rebooted into fastboot and install twrp 2.6.3.0. At this stage as I knew that the partition table had been updated, I sideloaded the WWE rom, which works more reliably when it's originally enabled
Did a Wiped cache for safe measure
Reboot and welcome to another 2GBs of space and WWE firmware.
NOTE: Always flash the inner zip “TW_A68-10.4.17.15-0-ota-user.zip” not the outer zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip”
freak4916 said:
Load the original recovery attached recovery.stock.img
Click to expand...
Click to collapse
Where can I find this?
I have a Lenovo A536. My problem ISN'T device specific.
I installed a custom rom and after some time it started appearing this message "System UI has stopped working".
I downloaded the original rom to flash it.
I got into TWRP and first formated my internal sdcard. The problem is that I forgot to transfer the IMG to the external sdcard. Now it doesn't have anything to boot and also I can't get in TWRP again. I also can't get in fastboot. My only solution is to do it through META MODE. I have read that I need a special cable that fits in the headphone hole.
Can you tell me:
1. How is this cable called? (in order to buy it)
2. What programs do i need to use from the computer in order to execute commands in meta mode
3. What commands i need in order to transfer the official image to my phone and/or flash it.
Any answer is acceptible
i was trying to root my phone i done it and i am trying to install a rom to it
after that i twrp and delete all files.
i have files still in my pc can someone help me how to put some zip in the phone because my pc cant detect my phone anymore.
thanks guys
Try re-installing the proper drivers for the device and also try to boot to fastboot and check if it detected. And if it does so, try restoring to official firmware.
If you can buy an OTG cable and try a pendrive. An OTG cable is a life saver in case of Mi4i since it doesn't have an MicroSD. If you haven't bought it yet, today maybe the time
If you have installed the driver. The copying from TWRP only works sometimes.
If you rooted then you must have used Fastboot so the drivers are there.
As hunkerpunk1 said install default ROM via fastboot using MiFlash.
Also if you are going to install CM12.1 or any custom roms here. You're phone must have MIUI 6 installed before not MIUI 7. So flash MIUI 6. Then root it and flash TWRP. Then install the ROM. This time copy the files inside the phone before hand
Please check if you're able to go into recovery (TWRP, NOT Stock), if answer is yes, you can use the mount option to copy those files again into your phone.
You simply need to :
1. Boot into TWRP
2. Connect the phone with PC (With Proper drivers installed)
3. Select the MOUNT option on TWRP Recovery
4. You'll see the prompt on your PC that Mi4i (with some Chinese words prepends) detected.
5. Copy the ROM & Gapps in phone.
6. BOOM (now I'm assuming you know how to move further)