Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Boot Loop

OP nero0345

3rd August 2014, 02:36 PM   |  #41  
Recognized Contributor
Thanks Meter: 2,498
 
3,527 posts
Join Date:Joined: Oct 2012
More
Quote:
Originally Posted by nero0345

If I try it, I get this back.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.036s]
finished. total time: 0.038s

But I belive in the terminal for fastboot, I dont get an error before.
What should I make now?

Hmm, apparently wiping cache worked even though the recovery had problems writing to it... try "fastboot -w" to wipe user data (this will erase *ALL* user data on the device). If that works, too, try booting to recovery again and see if the write errors in dmesg are gone.
3rd August 2014, 05:35 PM   |  #42  
OP Member
Thanks Meter: 0
 
47 posts
Join Date:Joined: Nov 2011
Quote:
Originally Posted by _that

Hmm, apparently wiping cache worked even though the recovery had problems writing to it... try "fastboot -w" to wipe user data (this will erase *ALL* user data on the device). If that works, too, try booting to recovery again and see if the write errors in dmesg are gone.

Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [  0.666s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 27562868736
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8176
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 6729216
    Block groups: 206
    Reserved block group size: 1024
Created filesystem with 11/1684256 inodes and 149746/6729216 blocks
sending 'userdata' (139009 KB)...
writing 'userdata'...
OKAY [ 23.760s]
erasing 'cache'...
OKAY [  0.037s]
formatting 'cache' partition...
Creating filesystem with parameters:
    Size: 918552576
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8016
    Inode size: 256
    Journal blocks: 3504
    Label:
    Blocks: 224256
    Block groups: 7
    Reserved block group size: 55
Created filesystem with 11/56112 inodes and 7256/224256 blocks
sending 'cache' (16340 KB)...
writing 'cache'...
OKAY [  2.839s]
finished. total time: 27.309s
And the new dmesg.txt look like the old one, with the errors.
3rd August 2014, 07:30 PM   |  #43  
Recognized Contributor
Thanks Meter: 2,498
 
3,527 posts
Join Date:Joined: Oct 2012
More
Quote:
Originally Posted by nero0345

And the new dmesg.txt look like the old one, with the errors.

The output from formatting via fastboot looks perfectly fine, so I don't understand how you can still get errors. Have you tried booting to Android after wiping, does that work?

@sbdags: Does any recovery exist for the TF701 that uses a stock kernel, just to rule out any possible influence from a custom kernel?
3rd August 2014, 07:53 PM   |  #44  
OP Member
Thanks Meter: 0
 
47 posts
Join Date:Joined: Nov 2011
Quote:
Originally Posted by _that

The output from formatting via fastboot looks perfectly fine, so I don't understand how you can still get errors. Have you tried booting to Android after wiping, does that work?

@sbdags: Does any recovery exist for the TF701 that uses a stock kernel, just to rule out any possible influence from a custom kernel?


I try it, but it doesnt work.
3rd August 2014, 09:43 PM   |  #45  
sbdags's Avatar
Recognized Contributor
Flag Kenilworth, Coventry
Thanks Meter: 13,191
 
11,649 posts
Join Date:Joined: Jun 2007
Donate to Me
More
Quote:
Originally Posted by _that

The output from formatting via fastboot looks perfectly fine, so I don't understand how you can still get errors. Have you tried booting to Android after wiping, does that work?

@sbdags: Does any recovery exist for the TF701 that uses a stock kernel, just to rule out any possible influence from a custom kernel?

They are all cm11 based but those are based from asus stock..... droidbasement.com hosts them - they are always quote asus source.
4th August 2014, 09:59 PM   |  #46  
OP Member
Thanks Meter: 0
 
47 posts
Join Date:Joined: Nov 2011
Ok and what should I make now?
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes