I thought I was on the jellybean bootloader, so I flashed the jb version of twrp. Then, I stupidly tried to boot into recovery from the rom itself. Now whenever it boots, it goes straight for the recovery kernel image which, of course, does not work. I can't seem to get into adb or fastboot, but I can get into nvflash. However, I never set up nvflash, so it just says "failed to open blob file: blob.bin". Right now it just keeps rebooting and trying to get into recovery again and again unless it's in nvflash mode.
So my questions are:
-is there a way to get into fastboot and/or adb from nvflash without having properly set it up.
-is there some other way to get into fastboot/adb
-is it possible to set up nvflash without fastboot? Like, say, borrowing someone else's blob.bin.
-Is there something else that I can do?
Thank you in advance. Sorry that I'm so dumb. Please help me.
Edit:
Upon further research, I have come to the conclusion that the blob.bin is related to the Secure boot key, and thus unique to each device, so borrowing a blob.bin is out.
Is there some other way to get the secure boot key?
I am perfectly willing to take apart my device if that opens up any other possibilities.
Related
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Oh, and it'll run ICS
...or at least boot it! (can't yet post links)
youtube.com/watch?v=dUmuQULyrAk
You can Fastboot the device and only botched the system image correct? Well, in theory all you need to do is boot ClockworkMod Recovery through Fastboot and restore a dump someone has already done. I think their is one in the Dev Forum already.
ThisIsDave said:
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Click to expand...
Click to collapse
Thanks for the info, saved me at least 3 or 4 times after soft bricking my Q. One thing that I found to help is while the device is bricked type in command prompt: adb reboot-bootloader ... this will generate a waiting for device tag then once you see that unplug the Nexus Q and plug it in, within one second as soon as you see a hint of blue on the mute button put your palm over it and it typically boots right into fastboot mode. If not just unplug and repete until it goes.
FYI: Also if you try to launch clockwork from an apk and instal a rom you will almost most definitely soft brick it (tried to sideload AOSP JB ROM and some others with no luck).
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
komitaltrade said:
First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
Click to expand...
Click to collapse
I have the same problem could somebody help us?
In meantime I dumped ROM and I can upload it, but it will be useless except if somebody will not be avalable to solve following issues>
01) ROM is without recovery.img and boot.img, what mean that ROM developer used busybox to script that. It mean that most likely recovery will be unacessible except somebody is not capable to find and replace tohse scripts with some recovery and boot images.
02) ROM permissions should be fixed (AT LEAST THIS IS MOST IMPORTANT).
03) Somebody should to find the way how to enter in recovery and.or fastboot. VERY IMPRTANT and I beleive that it must be easy to find in dumped ROM for some REAL ANDROID DEVELOPER (commands are scripted inside the system image).
SOME VOLONTIERS???
PLEASE!!!
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
HuskyHamburger said:
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
Click to expand...
Click to collapse
If you can enter the bootloader, the OS, recovery or you have your nvflash backups then you have a chance.
If you can access none of these then you are hard bricked.
Tried Ubuntu Dual Boot: bootloop/brick; but fastboot, apx, and adb access OK
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
AnotherBrickInTheWall said:
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
We can get you going and than post our finding back here to help everyone out...
Thx Josh