No fastboot, TWRP flickering screen

Search This thread
By:
Advanced…
Y

y3akup

Member
Oct 20, 2011
21
1
istanbul
It is working know after wipe evertyhing seems okey but the performance is stiil not so good. Thank you so much for your helps.
 
Last edited:
D

djakolis

Member
May 2, 2014
12
1
Performance wise, check lucius.zen's guide. It's named Guide/Tweak/Mod/Script... over at TF700 Android Development, 2nd page.

I did exactly like he said and the tablet is awesome now.
 
G

gilbertlucas46

Member
Aug 27, 2015
10
0
pasig
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Hi How did you fixed it im having the same problem, when i use this line of code " dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 "
its giving me an error "not recognized as an internal or external command, operable program or batch file"

---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------
berndblb said:
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code: 
adb logcat -v long > logcat.txt
Post that one too.
Click to expand...
Click to collapse
im having the same problem what is Aroma installer ? where and when will i use it?
 
berndblb

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
gilbertlucas46 said:
Hi How did you fixed it im having the same problem, when i use this line of code " dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 "
its giving me an error "not recognized as an internal or external command, operable program or batch file"

---------- Post added at 01:05 PM ---------- Previous post was at 12:49 PM ----------


im having the same problem what is Aroma installer ? where and when will i use it?
Click to expand...
Click to collapse
You have what problem?
Some devs incorporate Aroma into their roms zips. It starts when you flash the rom and let's you choose installation options.
 
G

gilbertlucas46

Member
Aug 27, 2015
10
0
pasig
berndblb said:
You have what problem?
Click to expand...
Click to collapse
I have the same problem as user: djakolis from post #4 No fastboot, TWRP flickering screen.
you can see it in youtube titled TF700 - No fastboot, recovery stuck -- this video is not mine.
im using lenovo k910L i accidentally wiped my os. i cant go through TWRP, the teamwin banner is just flickering.



okay here's what i did so far from reading the comments
I did this while my phone is connected to the pc while the TWRP is open and flickering on screen.
1. i tried this adb pull /tmp/recovery.log

I received this
D:\Minimal ADB and Fastboot>adb pull /tmp/recovery.log
7890 KB/s (1136043 bytes in 0.140s)
and got recovery.log file.

2. adb logcat

----
I received this
D:\Minimal ADB and Fastboot>adb logcat
/sbin/sh: exec: line 1: logcat: not found

3. Next I tried this
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
---
I received this
D:\Minimal ADB and Fastboot>adb shell
~ # ←[6nkillall -19 recovery
killall -19 recovery
~ # ←[6nmake_ext4fs /dev/block/mmcblk0p8
make_ext4fs /dev/block/mmcblk0p8
Need size of filesystem
~ # ←[6ndd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
1+0 records in
1+0 records out
64 bytes (64B) copied, 0.069722 seconds, 917B/s
~ # ←[6nreboot
-- my phone did not reboot. i have recovery.log but i dont know how to upload here
 
Last edited:
berndblb

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
To upload the log click Reply, scroll down and use "manage attachments".
You have to do this in your browser. Tapatalk or similar won't work
Do not type the # or anything following in the commands. That's just a comment - as it said in _that's post ...
 
J

jmms1124

Member
Dec 8, 2007
6
0
I seem to have encountered the same issues in this post. I have ADB access but cannot access fastboot OR CM Recovery. I tried the ADB commands and did not get the same results. Please help!
 
T

_that

Recognized Developer / Inactive RC
Oct 2, 2012
4,821
4,211
jmms1124 said:
I seem to have encountered the same issues in this post. I have ADB access but cannot access fastboot OR CM Recovery. I tried the ADB commands and did not get the same results. Please help!
Click to expand...
Click to collapse

The thread title says "TWRP flickering screen". You say you can't access CM recovery. So if you have TWRP installed, it's clear that you can't access CM recovery. And if you didn't get the same results and you really want help, it would be a good idea to post the results that you got instead.
 
  • Like
Reactions: lj50036
You must log in or register to reply here.

Similar threads

Dees_Troy
[RECOVERY][TF700T] TWRP 3.1.1-0 touch recovery [2017-05-19]
Replies
682
Views
264K
yaseen.soror
yaseen.soror
L
[RECOVERY] KANG TWRP TF700T 2.8.x.x@AREA51 JAN 4
Replies
192
Views
136K
R
rregn
sbdags
[ROM][Nov 1]★★ CleanROM Inheritance 3.5 | JB 10.4.4.25 | ODEX/DEODEX | Full ROM ★★
Replies
5K
Views
699K
berndblb
berndblb
berndblb
[GUIDE] Convert /data to f2fs with TWRP 2.8.+ [TF700T]
Replies
106
Views
109K
S
skapika
timduru
[ROM][N 7.1.2] [ KatKiss - Nougatella #039 ]
Replies
2K
Views
528K
Djiban
Djiban

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    T
    _that
    djakolis said:
    Tried adb pull /tmp/recovery.log and got recovery.txt file.

    Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
    Click to expand...
    Click to collapse

    Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):

    Code: 
    adb shell        # connect to a shell on the device
killall -19 recovery       # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8      # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1    # remove "wipe data" request
reboot
    View
    1
    T
    _that
    djakolis said:
    Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:

    I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
    Click to expand...
    Click to collapse

    Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.

    djakolis said:
    Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
    Click to expand...
    Click to collapse

    What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.

    Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.

    djakolis said:
    P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
    Click to expand...
    Click to collapse

    Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
    View
    1
    T
    _that
    jmms1124 said:
    I seem to have encountered the same issues in this post. I have ADB access but cannot access fastboot OR CM Recovery. I tried the ADB commands and did not get the same results. Please help!
    Click to expand...
    Click to collapse

    The thread title says "TWRP flickering screen". You say you can't access CM recovery. So if you have TWRP installed, it's clear that you can't access CM recovery. And if you didn't get the same results and you really want help, it would be a good idea to post the results that you got instead.
    View

New posts