Had my tf700 running CleanRom 4.2.1, and decidet to install a 4.4 just for the fun of it.
Upgraded my recovery, wiped /data storage, installed rom. After this my tablet pretty much stopped booting. 90% of the time it's stuck at boot screen (sometimes with animation running, sometimes not). Although once it did booted to a 4.4 Crombi-kk rom, but every 2-3 minutes it was rebooting.
What I have:
Access to bootloader, working CWM 6.0.4.7 for TF700T, ADB and fastboot access.
What I tried:
Installing TWRP and changing back to CWM, waiting for rom to "compile" everything (i guess around 2 days of doing that gotta be enough), Installing different roms (CleanRom, Crombi-kk, Zombi-x, Cyanogenmod 11 Nightly, Rooted stock rom).
Any suggestions on what can I do to recover my tablet?
And your bootloader version is... (insert drum roll here):
??????
Related
Right. So, I screwed up. I was running cm 10 sept 25th nightly for the longest time. without taking the time to research, I attempted via cwm to flash the jellybeen cm rom 10.0.0.... Seems the bootloader got upgraded after my last update,& all cm's needed jb bootloader.
now bootloop.
System hangs on asus screen.
I can boot into cwm, and can flash roms wipe cache, etc etc, but restoring my backup done right before the update (and the next oldest backup) still results in a boot loop.
Linux box, I have fastboot access to the device.
help?
I can't get into the system to figure out which asus firmware I'd need to install, (ww tw dw, or something like that)
Damnit. damnit, damnit.
OK,
I have bootloader 10.6.1.8, TWRP 2.4.4.0 and until this morning a working CM10.2 (latest stable). The device began to switch itself off randomly a few days ago, so I used that as a reason to try Omnirom 4.4.
So, I followed this: http://forum.xda-developers.com/showthread.php?t=2575727
And when I read the line "ONLY WHEN YOU ARE ON THE 4.2+ BOOTLOADER", I looked up what 10.6.1.8 was and decided (rightly or wrongly) it WAS the 4.2+ bootloader. So I flashed TWRP 2.6.3.1 for kitkat.
That resulted in a split screen TWRP, which I managed to use enough to restore my backup (including recovery) and the tablet rebooted into my old working ROM (yay!)...until I rebooted into the recovery again and tried to flash last nights nightly 10.2 build (to see if that solved the power off issue) which failed - and now my ROM bootloops.
Where I am now:
- I can get into fastboot, my device manager (on two machines, a Win7 x86, and a Win8.1 x64) shows the Asus bootloader device, but fastboot shows no devices. ADB shows no devices as well.
- I can get into TWRP, but I cannot see all of the zip files I put on my external card. I put a new ROM there, and TWRP just doesn't see it. So I cannot flash a new ROM. I've tried re-flashing an old version of CM10.2 I found on my internal SD, but that also bootloops.
- The ROM loads up until the lockscreen, where it bootloops. Even when it tries safe-mode, it loops again. My computer see's the tablet when it's booting (if the cable is plugged in at the time) but it loops before I can put anything on the internal SD.
Before I do anything else....what do I do?
(Thank you for any help you can give, in advance).:crying:
dewils80 said:
OK,
I have bootloader 10.6.1.8, TWRP 2.4.4.0 and until this morning a working CM10.2 (latest stable). The device began to switch itself off randomly a few days ago, so I used that as a reason to try Omnirom 4.4.
So, I followed this: http://forum.xda-developers.com/showthread.php?t=2575727
And when I read the line "ONLY WHEN YOU ARE ON THE 4.2+ BOOTLOADER", I looked up what 10.6.1.8 was and decided (rightly or wrongly) it WAS the 4.2+ bootloader. So I flashed TWRP 2.6.3.1 for kitkat.
That resulted in a split screen TWRP, which I managed to use enough to restore my backup (including recovery) and the tablet rebooted into my old working ROM (yay!)...until I rebooted into the recovery again and tried to flash last nights nightly 10.2 build (to see if that solved the power off issue) which failed - and now my ROM bootloops.
Where I am now:
- I can get into fastboot, my device manager (on two machines, a Win7 x86, and a Win8.1 x64) shows the Asus bootloader device, but fastboot shows no devices. ADB shows no devices as well.
- I can get into TWRP, but I cannot see all of the zip files I put on my external card. I put a new ROM there, and TWRP just doesn't see it. So I cannot flash a new ROM. I've tried re-flashing an old version of CM10.2 I found on my internal SD, but that also bootloops.
- The ROM loads up until the lockscreen, where it bootloops. Even when it tries safe-mode, it loops again. My computer see's the tablet when it's booting (if the cable is plugged in at the time) but it loops before I can put anything on the internal SD.
Before I do anything else....what do I do?
(Thank you for any help you can give, in advance).:crying:
Click to expand...
Click to collapse
You need to upgrade you bootloader. 10.6.1.8 is not new enough, as said here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7. Flash the latest stock blob from fastboot or from TWRP.
After that, you can install TWRP 2.6.3.1 and then OmniROM.
cmendonc2 said:
You need to upgrade you bootloader. 10.6.1.8 is not new enough, as said here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7. Flash the latest stock blob from fastboot or from TWRP.
After that, you can install TWRP 2.6.3.1 and then OmniROM.
Click to expand...
Click to collapse
Hi - thanks for the reply!
I didn't think I could do that ---^ because I couldn't get fastboot to work on either of my windows machines. But I installed fastboot and adb on my Ubuntu machine, and that worked seamlessly. :laugh:
So I now have the latest Asus firmware on and running, and a working TWRP 2.6.3.0.
That should let me flash the TWRP 2.6.3.1 zip from that thread linked above - and then flash Omnirom. :victory:
For anyone else in this predicament: I had to erase all of the device partitions with fastboot BEFORE flashing the Asus firmware. Without the erase, the Asus ROM just sat on the logo screen doing nothing.
Thanks again.
So I'm fairly new to rooted android, custom ROMs and the like but I did a bit of research and decided to root my phone and install a pacman 4.3 build on it. While i was able to succesfully root the phone and have had some success with flashing roms I have run into what seems to be a recurring bootloop issue.
Phone: Samsung Captivate Glide I927
Current OS: Stock Android 4.0.4 ICS
I'll start by describing what I have done so far:
Starting with a factory Android 2.3 phone I rooted my device using the following guide
Next I used odin 3.04 to flash CWM 6.0.2.1 to my phone
I then backed up using CWM, wiped data/factory reset, wiped cache, and flashed kick buttowski's PAC 4.3 build and gapps
Upon rebooting I received a samsung logo and then a black screen with no boot (over 15 min)
After some forum investigation I decided my best bet was to try and flash from a stock ICS build
I restored and attempted to flash a stock ICS zip; phone rebooted with a black screen and a pull down menu only
I restored and flashed a stock ICS tar through odin from here
This worked nearly perfectly as I was finally able to fully boot up, although the wifi will not turn on at all - even after some troubleshooting
I backed up the mostly working stock ICS and pressed forward.
First I had to re-flash CWM through odin as my native recovery mode had returned.
I then flashed the PAC 4.3 build with the same black screen error.
I then flashed bubor's PAC 4.3 build and gapps and was able to boot into the PACMAN startup screen at last....short lived as it displayed a pacman, game over, insert coin startup animation indefinitely (over 15 min)
I tried flashing bubor's CM 10.2 Cyanogen 4.3 and gapps instead and was met with a similar issue - indefinite cyanogen startup circle (over 15 min)
I tried flashing Omni 4.4 as well but was not able to even properly flash this one for a reboot.
I have run into this problem trying to flash a number of ROM's where I get stuck in an infinite bootloop. I have restored, wiped data and wiped caches in between each flash attempt and started from a stock ICS build and at this point don't know what to troubleshoot anymore. Can anyone help me?
Hi, my tablet have the 10.6.1.14.10 version of the bootloader, 4.2 JB, stock, i've unrooted and unlocked and installed TWRP 2.7.0.0, first i wanted to use the data2sd method, but i had problems to understand if first have to be installed data2sd and then flash the ROM, or first install the ROM and then the data2sd.
Anyway, i wipe everything on my tablet, and when i try to install data2sd TWRP shows an error of "Unable to extract..../update-binary", after that all my attemps of installing the ROM has been unsuccessfull, i've wipe all many times, when i try to restore the backup it just freezes at the very beginning of the bar (the clock was still running, but after 2 hours the bar was in the same position), so the only choice i have is to install the ROM.
I've read this post, and after seeing the solution, i made a data format, and tried to install just in the system, but at the very beginning of the installation of the Cromi-X, it ends, showing no errors, nor success, sometimes the screen goes black, and it seems like TWRP reboots and i start on the home screen, again.
I have Win 7 on my PC, the stock cable, and the MicroSD card is formatted to 8 gb of FAT, and 7 gb of ext4.
I'm quite desperate at this time, so i've very grateful with all your comments
After a lot of reading and unsuccessful attempts, i downgrade the TWRP version for the 2.6, and then it worked perfectly
Hello guys.
Last time I rooted and installed a Custom ROM was like 7-8 years ago with CM5 or so. So I'm not really up to date.
On my K1 tablet, I wanted to install the CarbonROM. Tablet runs Nougat.
The Root was successful, used fastboot for TWRP recovery. (Version 3.1.1 and 3.0.2, tried both). As in many tutorials described I wiped data/cache before installing. Installed CarbonROM (latest version) + gapps micro for 7.1 then wiped cache/dalvik and rebooted.
System then was stuck in bootloop forever, waited about 20mins but nothing happend.
Managed to backup by hard-reboot into recovery/adb and flash twrp again. Tried this time with twrp version 3.0.2, same issue.
I know about the presence of "blob", whatever it is. But since a few guides use it, and few dont, I tried with once with it but managed to land in bootloop again.
Tried with CWM but it didnt even recognize my SD card, or confused the internal storage as sd card. Moved the CarbonROM to the internal storage then and tried to install it. After boot image there was an android with a red "!" and "no command". Vol up + pwr -> recovery. rebooted. Still had the firmware from before, nothing happend at all.
I don't know anymore what to do to get CarbonROM installed and actually started.
Anybody got ideas or a actually a solution?
Greetings
Try a different ROM, or try another gapps (I've often had to mess with different gapps on AOSP ROMs on previous devices).
As for just getting the phone working again, you should have made a TWRP backup before trying to flash a custom ROM. Then you could have just restored the backup.