A new type of brick? [FIXED!] Possible solution to brick 3

Search This thread

hanzo001

Member
Mar 16, 2011
10
7
[SOLVED!] read on to find out what happened:

Hello y'all.

I hope you are all doing well in this fine pre-summer morning.

So I'm running the latest Virtuous Prime ROM, and flashaholic I am, I decide to try something new.

A little background:

1. I download AOKP + Gapps via Goo.Manager
2. I flash goo manager's custom recovery.
3. I make a nandroid of my current ROM.
4. Flash AOKP + Gapps; everything is working fine, but whenever the screen rotates I get a black overlay. I hate it, so I try to restore.

Here's where it gets interesting:

1. From the recovery, I wipe System/Data/Dalvik Cache
2. I restore my old ROM, hit 'reboot'
3. I get the splashscreen and then... nothing
4. I try to get into the recovery (Power + Vol. Down) but
5. I don't get the option of going into recovery; I'm automatically redirected to the wipe data / start Fastboot protocol screen.

Now, when I plug in the tablet to my PC, it is recognized as 'Asus Android Devices', but when I type 'ADB devices' I get 'List of android devices attached' and then blank.

Pushing a CMW recovery.img failed (fastboot flash recovery recovery.img); it gets stuck in '< waiting for device >'

I tried the 'Wipe Data' option from the menu, but it did no good. It still won't boot.


TL;DR: I can't access recovery, but I (more or less) have access to fastboot



UPDATE
I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

Using that, I was able to successfully flash recovery.img

But **** me, it still won't boot into recovery.


UPDATE 2
User gerald410 suggested that I flash a new boot.blob file. Short answer: that did the trick. Long answer:

* I downloaded the latest Virtuous Prime ROM (Virtuous Prime 9.4.2.21 v1) as of this writing.
* I extracted the ZIP file and pulled the file called 'blob'
* I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
* from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
* then I typed: fastboot -i 0x0b05 reboot

This granted me access to recovery again (i.e., Brick Type 3).
From the recovery I was able to use ADB. This is what I did last time I was in brick type 3. Hopefully it'll work in your case too.

* Open a command prompt; type adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/
* Wait until you get a confirmation message (it will look something like 1279 KB/s (334733438 bytes in 255.472s))
* Flash normally as you would with any ROM.
* Profit!

Wow! this situation gave me a series of mini heart attacks, but it's over.

Now, to keep on downloading more ROMs.
 
Last edited:

hanzo001

Member
Mar 16, 2011
10
7
So 'boot.blob' uh? I'll check it out

UPDATE
That did the trick; Thanks :D

In case anyone wants to know how I did it, read the first post.
 
Last edited:

gotchi

Senior Member
Jul 6, 2007
76
4
www.feutl.com
[SOLVED!] read on to find out what happened:

Hello y'all.

I hope you are all doing well in this fine pre-summer morning.

So I'm running the latest Virtuous Prime ROM, and flashaholic I am, I decide to try something new.

A little background:

1. I download AOKP + Gapps via Goo.Manager
2. I flash goo manager's custom recovery.
3. I make a nandroid of my current ROM.
4. Flash AOKP + Gapps; everything is working fine, but whenever the screen rotates I get a black overlay. I hate it, so I try to restore.

Here's where it gets interesting:

1. From the recovery, I wipe System/Data/Dalvik Cache
2. I restore my old ROM, hit 'reboot'
3. I get the splashscreen and then... nothing
4. I try to get into the recovery (Power + Vol. Down) but
5. I don't get the option of going into recovery; I'm automatically redirected to the wipe data / start Fastboot protocol screen.

Now, when I plug in the tablet to my PC, it is recognized as 'Asus Android Devices', but when I type 'ADB devices' I get 'List of android devices attached' and then blank.

Pushing a CMW recovery.img failed (fastboot flash recovery recovery.img); it gets stuck in '< waiting for device >'

I tried the 'Wipe Data' option from the menu, but it did no good. It still won't boot.


TL;DR: I can't access recovery, but I (more or less) have access to fastboot



UPDATE
I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

Using that, I was able to successfully flash recovery.img

But **** me, it still won't boot into recovery.


UPDATE 2
User gerald410 suggested that I flash a new boot.blob file. Short answer: that did the trick. Long answer:

* I downloaded the latest Virtuous Prime ROM (Virtuous Prime 9.4.2.21 v1) as of this writing.
* I extracted the ZIP file and pulled the file called 'blob'
* I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
* from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
* then I typed: fastboot -i 0x0b05 reboot

This granted me access to recovery again (i.e., Brick Type 3).
From the recovery I was able to use ADB. This is what I did last time I was in brick type 3. Hopefully it'll work in your case too.

* Open a command prompt; type adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/
* Wait until you get a confirmation message (it will look something like 1279 KB/s (334733438 bytes in 255.472s))
* Flash normally as you would with any ROM.
* Profit!

Wow! this situation gave me a series of mini heart attacks, but it's over.

Now, to keep on downloading more ROMs.


You saved my life today :)

I found your post - tried it - worked like a charm. My prime is back on the track again :)

Thank you very much :)
 

Gage_Hero

Senior Member
Jul 22, 2010
1,423
235
Normally when I do a restore, I don't wipe anything... never ran into this particular issue. From what I have read here the wipe system could be the issue.
 

IrishSniperN

New member
Mar 13, 2013
1
0
I'm a noob, but would appreciate your help.

I am hoping that what you did will fix my problem. I have an unlocked TF300T on Ice Cream Sandwhich. I may have missed a step, but somehow I found myself with a boot loop. To try to resolve this I wiped data. All this seems to have done is delete everything on my tablet. It no longer boot loops. Instead I am stuck on initial boot screen with "This Device Is Unlocked" in the left corner of the screen. When I press volume down + power, it reboots, but no options appear. Do I need to be able to see an Icon appear in order for this to work? I am at a loss and appreciate the community's support.

---------- Post added at 10:59 PM ---------- Previous post was at 10:18 PM ----------

* I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
* from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
* then I typed: fastboot -i 0x0b05 reboot

Is this from within the fastboot folder on your PC?

Sorry Again. I'm just really frazzled and probably never should have attempted this.
 

techguy1214

Member
Sep 27, 2012
19
12
Nob her can you pleas help me!!!

[SOLVED!] read on to find out what happened:

Hello y'all.

I hope you are all doing well in this fine pre-summer morning.

So I'm running the latest Virtuous Prime ROM, and flashaholic I am, I decide to try something new.

A little background:

1. I download AOKP + Gapps via Goo.Manager
2. I flash goo manager's custom recovery.
3. I make a nandroid of my current ROM.
4. Flash AOKP + Gapps; everything is working fine, but whenever the screen rotates I get a black overlay. I hate it, so I try to restore.

Here's where it gets interesting:

1. From the recovery, I wipe System/Data/Dalvik Cache
2. I restore my old ROM, hit 'reboot'
3. I get the splashscreen and then... nothing
4. I try to get into the recovery (Power + Vol. Down) but
5. I don't get the option of going into recovery; I'm automatically redirected to the wipe data / start Fastboot protocol screen.

Now, when I plug in the tablet to my PC, it is recognized as 'Asus Android Devices', but when I type 'ADB devices' I get 'List of android devices attached' and then blank.

Pushing a CMW recovery.img failed (fastboot flash recovery recovery.img); it gets stuck in '< waiting for device >'

I tried the 'Wipe Data' option from the menu, but it did no good. It still won't boot.


TL;DR: I can't access recovery, but I (more or less) have access to fastboot



UPDATE
I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

Using that, I was able to successfully flash recovery.img

But **** me, it still won't boot into recovery.


UPDATE 2
User gerald410 suggested that I flash a new boot.blob file. Short answer: that did the trick. Long answer:

* I downloaded the latest Virtuous Prime ROM (Virtuous Prime 9.4.2.21 v1) as of this writing.
* I extracted the ZIP file and pulled the file called 'blob'
* I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
* from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
* then I typed: fastboot -i 0x0b05 reboot

This granted me access to recovery again (i.e., Brick Type 3).
From the recovery I was able to use ADB. This is what I did last time I was in brick type 3. Hopefully it'll work in your case too.

* Open a command prompt; type adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/
* Wait until you get a confirmation message (it will look something like 1279 KB/s (334733438 bytes in 255.472s))
* Flash normally as you would with any ROM.
* Profit!

Wow! this situation gave me a series of mini heart attacks, but it's over.

Now, to keep on downloading more ROMs.



i did the same thing like u but i did it in a asus tf201

will this work on it?? the only way my computer reads this is in apx mode thats it i u lost me on when u said u added the thing to the drivers??

---------- Post added at 06:46 AM ---------- Previous post was at 06:21 AM ----------

[SOLVED!] read on to find out what happened:

Hello y'all.

I hope you are all doing well in this fine pre-summer morning.

So I'm running the latest Virtuous Prime ROM, and flashaholic I am, I decide to try something new.

A little background:

1. I download AOKP + Gapps via Goo.Manager
2. I flash goo manager's custom recovery.
3. I make a nandroid of my current ROM.
4. Flash AOKP + Gapps; everything is working fine, but whenever the screen rotates I get a black overlay. I hate it, so I try to restore.

Here's where it gets interesting:

1. From the recovery, I wipe System/Data/Dalvik Cache
2. I restore my old ROM, hit 'reboot'
3. I get the splashscreen and then... nothing
4. I try to get into the recovery (Power + Vol. Down) but
5. I don't get the option of going into recovery; I'm automatically redirected to the wipe data / start Fastboot protocol screen.

Now, when I plug in the tablet to my PC, it is recognized as 'Asus Android Devices', but when I type 'ADB devices' I get 'List of android devices attached' and then blank.

Pushing a CMW recovery.img failed (fastboot flash recovery recovery.img); it gets stuck in '< waiting for device >'

I tried the 'Wipe Data' option from the menu, but it did no good. It still won't boot.


TL;DR: I can't access recovery, but I (more or less) have access to fastboot



UPDATE
I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

Using that, I was able to successfully flash recovery.img

But **** me, it still won't boot into recovery.


UPDATE 2
User gerald410 suggested that I flash a new boot.blob file. Short answer: that did the trick. Long answer:

* I downloaded the latest Virtuous Prime ROM (Virtuous Prime 9.4.2.21 v1) as of this writing.
* I extracted the ZIP file and pulled the file called 'blob'
* I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
* from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
* then I typed: fastboot -i 0x0b05 reboot

This granted me access to recovery again (i.e., Brick Type 3).
From the recovery I was able to use ADB. This is what I did last time I was in brick type 3. Hopefully it'll work in your case too.

* Open a command prompt; type adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/
* Wait until you get a confirmation message (it will look something like 1279 KB/s (334733438 bytes in 255.472s))
* Flash normally as you would with any ROM.
* Profit!

Wow! this situation gave me a series of mini heart attacks, but it's over.

Now, to keep on downloading more ROMs.


ok so how did u add the *-i 0x0b05* ???
 

binhdb

Senior Member
May 5, 2013
53
5
I read "Good" and was sure I had seen it a few times before with that avatar. Looked up your post history and half of your posts just say "Good" lol.

I think it is a translation issue but if not you should come over to reddit ;)

Oh no, I was Vietnam. That is a good praise and encouragement and all articles, it is thanks to our Vietnamese people.

---------- Post added at 07:17 PM ---------- Previous post was at 07:08 PM ----------

I read "Good" and was sure I had seen it a few times before with that avatar. Looked up your post history and half of your posts just say "Good" lol.

I think it is a translation issue but if not you should come over to reddit ;)

please help me
I've tried many times but failed, status bar forced close error
I'm using lenovo phone, android version 2.3.6. MediaTek MT6575 single-core Cortex-A9
I enclose SystemUI and framework-res files, please take some time to Help me I would be very grateful for thi
http://www.mediafire.com/download/9gmxv6in42amoqo/mod.rar
<a href='http://www.uphinh.vn/image/stream/1455859.jpg'><img src='http://www.uphinh.vn/image/stream/1455859.jpg'></a>
1455859.jpg
 
Last edited:

flumpster

Senior Member
Apr 4, 2011
2,726
2,229
Rhondda Valleys
Oh no, I was Vietnam. That is a good praise and encouragement and all articles, it is thanks to our Vietnamese people.

---------- Post added at 07:17 PM ---------- Previous post was at 07:08 PM ----------



please help me
I've tried many times but failed, status bar forced close error
I'm using lenovo phone, android version 2.3.6. MediaTek MT6575 single-core Cortex-A9
I enclose SystemUI and framework-res files, please take some time to Help me I would be very grateful for thi
http://www.mediafire.com/download/9gmxv6in42amoqo/mod.rar
<a href='http://www.uphinh.vn/image/stream/1455859.jpg'><img src='http://www.uphinh.vn/image/stream/1455859.jpg'></a>
1455859.jpg

You are in the wrong thread mate. This is for the Asus Transformer Prime tablet and I doubt anyone here would know your phone.
 

mormor83

New member
Oct 19, 2013
2
0
there is something unclear

First of all thank you very much for the help :)
second can you elaborate of this:

UPDATE
I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

Using that, I was able to successfully flash recovery.img

But **** me, it still won't boot into recovery.

what did you do here?
was it from APX mode?

my tablet can only get to apx mode and if i boot it the screen says: "this device is unlocked" +the asus logo + nvidia logo...
about to cry.....:crying:

can you help?

UPDATE:
In case i'm f****d do any one know if i can sell my very expensive bricked tf201 for parts ( keyboard included ) ?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    [SOLVED!] read on to find out what happened:

    Hello y'all.

    I hope you are all doing well in this fine pre-summer morning.

    So I'm running the latest Virtuous Prime ROM, and flashaholic I am, I decide to try something new.

    A little background:

    1. I download AOKP + Gapps via Goo.Manager
    2. I flash goo manager's custom recovery.
    3. I make a nandroid of my current ROM.
    4. Flash AOKP + Gapps; everything is working fine, but whenever the screen rotates I get a black overlay. I hate it, so I try to restore.

    Here's where it gets interesting:

    1. From the recovery, I wipe System/Data/Dalvik Cache
    2. I restore my old ROM, hit 'reboot'
    3. I get the splashscreen and then... nothing
    4. I try to get into the recovery (Power + Vol. Down) but
    5. I don't get the option of going into recovery; I'm automatically redirected to the wipe data / start Fastboot protocol screen.

    Now, when I plug in the tablet to my PC, it is recognized as 'Asus Android Devices', but when I type 'ADB devices' I get 'List of android devices attached' and then blank.

    Pushing a CMW recovery.img failed (fastboot flash recovery recovery.img); it gets stuck in '< waiting for device >'

    I tried the 'Wipe Data' option from the menu, but it did no good. It still won't boot.


    TL;DR: I can't access recovery, but I (more or less) have access to fastboot



    UPDATE
    I just noted that Fastboot doesn't work using naked drivers I grabbed from here. I have to add "-i 0x0b05" to work.

    Using that, I was able to successfully flash recovery.img

    But **** me, it still won't boot into recovery.


    UPDATE 2
    User gerald410 suggested that I flash a new boot.blob file. Short answer: that did the trick. Long answer:

    * I downloaded the latest Virtuous Prime ROM (Virtuous Prime 9.4.2.21 v1) as of this writing.
    * I extracted the ZIP file and pulled the file called 'blob'
    * I renamed the file as boot.blob and moved it to the TOOLS folder and opened a Command Prompt;
    * from inside the TOOLS folder, I typed: fastboot -i 0x0b05 flash boot boot.blob
    * then I typed: fastboot -i 0x0b05 reboot

    This granted me access to recovery again (i.e., Brick Type 3).
    From the recovery I was able to use ADB. This is what I did last time I was in brick type 3. Hopefully it'll work in your case too.

    * Open a command prompt; type adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/
    * Wait until you get a confirmation message (it will look something like 1279 KB/s (334733438 bytes in 255.472s))
    * Flash normally as you would with any ROM.
    * Profit!

    Wow! this situation gave me a series of mini heart attacks, but it's over.

    Now, to keep on downloading more ROMs.
    1
    You will need to flash a proper boot.blob to resolve the issue, checked the bricked thread for further instructions.