Hi there,
A few weeks ago I rooted my tf101 and installed clockworkmod 5. Installing the rom from Raymanfx isn't a problem, but it doesn't run very smoothly. So I wanted to try the ROM of EOS4. Installed both nightly's .93 and .92, but both don't work. I've wiped the cache, but it still stays stuck in bootscreen. I'm wondering, how can I find out the problem and how can I solve it?
Thx in advance!
Yours sincerely,
Anderverhaal
Any time you flash a different ROM (from a different DEV), for best results you should wipe:
Cache
Davlik Cache
System (ROM)
Factory Reset (will not wipe the /data/media/ aka /sdcard/ directory, just the apps installed in the /data/ directory).
Failing to do a factory reset, there may be some system settings from your previous ROM that are still lingering and causing issues with the TeamEOS 4.
Also, I would HIGHLY recommend using TWRP 2.3.2.3 for EOS 4. The new multi-user file structure does not work well with CWM 5.X.
If you want to update, you can boot to CWM, connect to your tablet via ADB, push the latest TWRP blob and use the ADB shell command to dd it to the recovery partition.
Otherwise, install a ROM that boots, then install GooManager and then choose the Install OpenRecovery Script.
Related
I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?
Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.
Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.
solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S
Hi,
I am trying to update to 4.4 from 4.2 on my A700. I used the nightly and gapps files recommended in this thread [NIGHTLY][ROM][4.4] CyanogenMod 11.0 for Acer A700 here: http://forum.xda-developers.com/showthread.php?t=2563610
I booted into CWM Recovery v6.0.4.4 and installed both files. After that, I did a factory reset. I told it to reboot and now all I get is a boot loop of the Acer splash screen showing Bootloader Verion JB-653b3d3 (unlock mode) in the upper left. Then it vibrates once and reboots again. Can someone help me out?
btw, I have previously tried updating to a newer version of 4.2 and I was getting the same thing. At that point, I was able to flash my old files. Now I don't have the old files to flash. Also, I can't find a way to load files via usb. In CWM, it doesn't seem to want to mount so my XP machine can see it.
I am not too well versed in custom roms. I have looked over other threads in this forum but so far I don't see what I need. If my question has already been addressed (I wouldn't be surprised), I need some direction on this. I am stuck...
Thanks very much!
John
frankred said:
Hi,
I am trying to update to 4.4 from 4.2 on my A700. I used the nightly and gapps files recommended in this thread [NIGHTLY][ROM][4.4] CyanogenMod 11.0 for Acer A700 here: http://forum.xda-developers.com/showthread.php?t=2563610
I booted into CWM Recovery v6.0.4.4 and installed both files. After that, I did a factory reset. I told it to reboot and now all I get is a boot loop of the Acer splash screen showing Bootloader Verion JB-653b3d3 (unlock mode) in the upper left. Then it vibrates once and reboots again. Can someone help me out?
btw, I have previously tried updating to a newer version of 4.2 and I was getting the same thing. At that point, I was able to flash my old files. Now I don't have the old files to flash. Also, I can't find a way to load files via usb. In CWM, it doesn't seem to want to mount so my XP machine can see it.
I am not too well versed in custom roms. I have looked over other threads in this forum but so far I don't see what I need. If my question has already been addressed (I wouldn't be surprised), I need some direction on this. I am stuck...
Thanks very much!
John
Click to expand...
Click to collapse
Hey John.
What it sounds like, is that you didn't do your "wipes" before flashing the CM ROM. This is pretty much mandatory, and sounds like what happened.
I would boot back into CWM. These are what you need to wipe/format "before" flashing CWM.
1. Data/factory reset (this wipes your data partition)
2. System (this wipes pretty much all current system files)
3. Cache
4. Dalvak Cache (might need to look for this in "advanced", it depends on the recovery.)
5. Flexrom if it's an option. If not, don't worry about it, as it seldom causes issues.
Then, flash your CM. Now, for myself, I usually flash CM first, boot the system, bypass all the setup screens, then let it stabilize. Then I go back into CWM and flash the Gapps. That's just me though. Some folks flash CM, then Gapps in that order at the same time.
Good luck
MD
Thanks very much for the reply MD!
I tried the steps you suggested but I am still stuck in the same place. Let me explain.
When I select wipe data/factory reset, it processes for a second and then reboots. Is this normal behavior?
When I select Wipe Dalvik Cache, I get:
E:Unknown volume for path [/sd-ext]
Dalvik cache wiped.
I selected Show Log:
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78400 inodes and 10305/313344 blocks.
warning:wipe_block_device: wipe via secure discard suppressed due to bug in EMMC firmware
Cache wipe complete.
I:Ca't partition non mmcblk device: /decisces/platform/sdhci-tegra.0/mmc_host/mmc2
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': no such file or directory
rm: can't remove '/cache/dalvik-cache': no such file or directory
rm: can't remove '/sd-ext/dalvik-cache': no such file or directory
Dalvik Cache wiped.I have my rom and gapps in /storage/sdcard1/cminstall/
cm-11-2014-111-NIGHTLY-a700.zip - not renamed cmupdate.zip
gapps-kk-20131209.zip
I feel like I have a larger issue here...
Well, it has been a while but I am still stuck in the same boat. I have since had the flu and I was out of town for work for 3 days then 5 days.
My rom and gapps files are currently on my external SD card. Should they be on the internal storage?
I have been trying to connect via usb to my xp laptop but I am not having any luck. The best I can get is an A700 in Device Manager with a yellow exclamation point. I have tried installing the Acer usb drivers but they won't take.
The closest I get to Windows finding the tablet with my laptop is when I let it attempt to boot. Windows finds the device for about 5 seconds before it reboots again.
Can anyone point me in the right direction?
Any help would be much appreciated.
John
I want to flash SlimROM, but I think I messed up.
I installed CWM, and wiped everything I needed to (factory, data, cache, system) WITHOUT putting the SlimROM zips in ahead.
Right now I can get into fastboot and CWM.
I tried installing with adb sideload, but the device turn to unknown device (Android > Nexus 5) when I access the adb sideload function.
Is there a driver somewhere that I missed?
Any help would be great!
ADB Driver Installer
Don't use CWM, support has been discontinued. Use TWRP 2.8.1.0 instead.
It's an ASUS Nexus 7 2012.
I installed 'lineage-15.1-20200706-UNOFFICIAL-grouper' and 'MindTheGapps-8.1.0-arm-20180808-grouper' (is this the right file?) successively before rebooting while first wiping Dalvik/ART Cache, System, and Data.
It boots, but Gapps don't work. I managed to enter playstore but only once before it froze and since then, I can't enter it no more.
Here, they tell you to change filesystem from EXT4 to F2FS first and also to sideload the OS and Gapps instead of placing the zips in the root folder and installing from device. Does that make a difference?
see nothing is wrong or right it is just about compatibility use default instruction as much as possible
well regarding gapps flash it after setting up phone
Just make sure all the tools you've downloaded are compatible for your device.
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
<EDITED>
Device 2: Galaxy S3 GT-I9300 - I solved this so i removed this section.
Thank you for any help.
Beeblebrox-BSD said:
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
Device 2: Galaxy S3 GT-I9300, with working TWRP. This device is giving a "Failed to mount /efs (Invalid argument)" error. The previous setup was shared storage with sdcard and encryption on both internal and sdcard. The sdcard got corrupted, hence the error. This post suggests running
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
but the device does not have identifiable boot device under /dev/block. I think this might work if I can identify the boot partition name?
Thank you for any help.
Click to expand...
Click to collapse
Flash a custom ROM for i9300 via TWRP. Download a custom ROM for i9300 and the appropriate Gapps to go with the ROM, store them on external sdcard. When you are in TWRP, before you flash your ROM, select the "Wipe" option, then select "advanced wipes", on the next menu, choose the system partition, data partition, cache partition and dalvik cache partition then swipe the slider to wipe. Then go back to home screen in TWRP and choose the "Install" option, then choose your ROM file and your Gapps file then swipe to flash. When the flash is finished, select the "Reboot system" option and see if it boots into system.
If that doesn't work, we will take some steps further back and try starting from the beginning.
Keep in mind that some of the custom ROMs for i9300 may have a different partition structure and partition sizes than the stock firmware for i9300 has and may require resizing certain partitions such as the system partition by flashing a custom PIT file like the Galaxy S2 had to do before it flashed certain custom ROMs.
Hi, thanks for the input.
* I had already solved the GT-I9300 issue before your post (I should have added to thread rather than edit the original post). I solved issue with that device by including system partition in the wipe.
* For the SM-T800, I used a LineageOS-14.1 that I had stored somewhere. That also did not work, until I only flashed Lineage and did not include any GApps. If I really need it, I can always flash later. I assume the latest GApps 7.1 build conflicts with older ROMs.
An unexpected problem was the lack of current ROMs for the 2 devices. SM-T800 has nothing other than last build Lineage-14-1-20190205. The I9300 has several unofficial ROMs floating around for newer Android versions, but they are all debug/dev builds with enabled options that drain the battery very quickly.
If anyone comes across a decent ROM for either of these devices please LMK. Thanks.