[Q] Another bricked (and wiped) device stuck at TWRP password page - Asus Eee Pad Transformer Prime

Well I did what the developers specifically warned against. I wanted to try a few ROMS and then decide on one to settle with but obviously nothing is ever that simple. I can't remember which version of which software I installed, but after installing and reinstalling a mix of ROMS and TWRP versions I made a mistake somewhere and suddenly I got TWRP asking for a password. I panicked at first but when I clicked 'cancel' and went to the usual TWRP page, I thought all is normal again and continued to attempt installing a new ROM beginning with formatting all the data off the tablet! Lo and behold, after formating I learn that TWRP wont allow me to install any new ROMs (why does it allow me to format but not install?)! So now I'm stuck with a tablet that has no OS and boots straight to TWRP's password page.
How bad is my situation? Is the tablet redeemable?
For what it's worth I tried setting up the ADB thing as per the tutorial but whenever I type in "adb shell" I get something to the effect of "adb is not a recognizable command". I don't know if that even matters but it seems to be mentioned alot whenever a bricked Prime is brought up. :\
Thank you
Edit: Sorry mods! I just noticed that questions aren't allowed on this forum. I want to delete this and post it elsewhere but the "Edit/Delete" button is only showing the edit screen and no delete buttons! Terribly sorry!

Related

LY-F1/Allwinner A10/Versus Touchpad 7 Bricked?

Hi there, i'm only really posting this out of desperation, I'm at my absolute wit's end with this tablet and i honestly can't suss out what's wrong with it anymore
I followed http://forum.xda-developers.com/showpost.php?p=20032494&postcount=2 to try and install CWM and it worked, CWM is running and uses 6.0.12 i believe the version is without looking.
UNFORTUNATELY now i can't access anything via CWM, i can't mount, open or format any of the internal stuff like system, cache, log, emmc ect. I've tried reflashing different versions of CWM with no success via ADB, they just quite simply don't seem to be taking hold no matter how many times i reboot or reflash and also i can't boot into the OS anymore, which really sucks since it won't accept anything i try flash to it.
Now here's the real slap in the testes, The original firmware recovery seems to be now gone meaning i can't put the device into software update or firmware recovery or anything to try flashing with Livesuit, i'm sure there's something i'm missing somewhere can anybody help? Livesuit definately detects SOMETHING is going on when i hold the volume buttons and hammer the power button, my system beeps and LiveSuit pops up, but it only displays a blank error message which i'll take a screenie of, from there it refuses to do anything else.
I've also tried using USBDeview or whatever it's called to remove every trace of a driver related to anything remotely Android and gone that route but no luck again.
I've looked into and read (and re-re-re-re-read) every single post i can find about this but the threads have either gone or died out
EDIT - Another quick think i forgot to mention was that if i try to view the partitions or hardware info via ADB i get extremely limited info back which i'll post in as well when i get chance

[Q] Another bricked (and wiped) device stuck at TWRP password page

Well I did what the developers specifically warned against. I wanted to try a few ROMS and then decide on one to settle with but obviously nothing is ever that simple. I can't remember which version of which software I installed, but after installing and reinstalling a mix of ROMS and TWRP versions I made a mistake somewhere and suddenly I got TWRP asking for a password. I panicked at first but when I clicked 'cancel' and went to the usual TWRP page, I thought all is normal again and continued to attempt installing a new ROM beginning with formatting all the data off the tablet! Lo and behold, after formating I learn that TWRP wont allow me to install any new ROMs (why does it allow me to format but not install?)! So now I'm stuck with a tablet that has no OS and boots straight to TWRP's password page.
How bad is my situation? Is the tablet redeemable?
For what it's worth I tried setting up the ADB thing as per the tutorial but whenever I type in "adb shell" I get something to the effect of "adb is not a recognizable command". I don't know if that even matters but it seems to be mentioned alot whenever a bricked Prime is brought up. :\
Thank you

[Q] Please please help this noob out!

As previously stated I am a complete noob when it comes to flashing android devices.
Here is the problem I am faced with: I recently rooted, and unlocked the bootloader on my atrix hd (ATT)
Since then I tried installing cm10.1 multiple times on the secondary "Rom slots" within the bootloader, without any success. So I finally decided to go for it and install cm10.1 in the "stock rom" slot, Prior to doing this I did a back-up using Rom manager. Aand now I seemingly can't even boot into recovery mode, every time I restart my device it simply goes to the cyanogenmod blue ring thingy and gets stuck! (I have left it for 15-20 mins thinking it might be some kind of installation process..) But apparently it's not and i've broken my smartphone lol. Anyway i'd really appreciate some help fixing this problem, a step-by step guide would probably work best..!!! I have both windows 8 and Ubuntu installed on my pc, just saying..Don't know if it's relevant information and may simplify fixing my problem...Thanks in advance guys and girls
i've even tried holding down all three physical buttons and it simply takes me back to the same screen!!!
you could try something like this:
http://forum.xda-developers.com/showthread.php?t=2434726
.. and you are sure, that you can not enter the recovery menu??
official motorola guide, how to enter recovery menu:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620/action/auth
.. adb could be your last possibility, if everything else fails, google it, you'll find many answer

Y300 completely wiped

Here is my full story
I have a huawei y300 with no Os, how did the OS got wiped? I was in twrp and was doing a factory reset where i select advance reset and end up wiping the entire system alone with my files, Os, apps etc... after which when i turn on the phone it wont boot up.
I then realise that i could still access twrp so i search everyone it but could not find away to restore my OS and solve the problem, bare in mine that i rooted the phone.
At that point when i plugged in the phone and search for adb devices my phone was shown after a few research and attends i failed in fixing the problem. I then did something while using the push function to send clockwork recovery to the phone or something like that after which i realise that twrp stop showing on the phone i then realised that i was not seeing my devices on the list of adb. after a few attempts and i kept on trying i saw it came up as offline but now its not showing again.
Hope you all understand the issue now
So like wat i need is a software that can program the OS straight to the phone is such software does exist but in fact should because how the OS came on in the first place, i dont know a thing about phones but i know a little to help myself but i have reached my limit
Please help

Installing Custom ROM Lots of issues and nothing really works anymore.

Hello XDA Forum,
so in order to get rid of all the garbage Samsung pre-installed stuff I wanted to install a custom ROM like LineageOS. To do this (since I'm a complete layman) I used this guide for the most part: https://forum.xda-developers.com/t/...fn-ds-lineageos-19-too.4431737/#post-86951249
First Issue arrived at point 12, when despite "swiping to allow writing" TWRP would not allow me to copy filed onto the phone. So I read somewhere else to reinstall TWRP, which I then did after a lot of back and forth. Sadly when leaving TWRP it seems almost impossible to get back into TWRP, the phone just loops around a recovery screen telling me that bootloader is unlocked. It's also no longer being recognized by ADB and Fastboot, or Odin for that matter. And even reinstalling the USB Driver did not help.
So I read somewhere to reblock the bootloading and then enabling it again. So I did, and now I cannot unblock it anymore either. It just sits in the "Downloading Mode" and when I hold Volume Down and Power it goes into the Recovery Screen and then IMMEDIATELY back into Downloading. I can't even turn it off because it's basically stuck in Downloading.
If I could make it work again and findable by ADB I might be able to just use a different Version of TWRP (not the one advertised in the thread linked above) and maybe try again. But then I also don't know why it was so hard to get into TWRP to begin with. Or is there now no escape from this loop and the phone is essentially bricked?
{Mod edit: Post adjusted to the language required by the forum rules! - Oswald Boelcke}
so you can not flash stock?

Categories

Resources