Prime is soft bricked - Help? - Asus Eee Pad Transformer Prime

I recently purchased an Asus Transformer Prime TF201 from ebay with a custom rom preinstalled. I was not a fan of said rom so I decided I would do a factory reset and thought that the previous owner would back up the original OS. Now every time I boot up my prime it goes to CWM... I have tried every option but I am stuck in a boot loop with CWM. I tried to restore from a backup, when it is complete it says it was successful but I am still stuck in this loop. I have downloaded ADB and when I write "adb devices" it comes back with nothing. When I write "adb logcat" it comes back with "-waiting on device-". So I assume the drivers were not set up. I have downloaded the drivers but I cannot get them to install properly through my Windows XP system. It just says failed every time. I'm guessing it is not recognizing it since it has no operating system. What should I do? I feel like I have exhausted all resources. I can give any detailed information that you want, but just be specific about what you want from me. Thank you in advance, I am pulling my hair out at the moment.

cjoconne said:
I recently purchased an Asus Transformer Prime TF201 from ebay with a custom rom preinstalled. I was not a fan of said rom so I decided I would do a factory reset and thought that the previous owner would back up the original OS. Now every time I boot up my prime it goes to CWM... I have tried every option but I am stuck in a boot loop with CWM. I tried to restore from a backup, when it is complete it says it was successful but I am still stuck in this loop. I have downloaded ADB and when I write "adb devices" it comes back with nothing. When I write "adb logcat" it comes back with "-waiting on device-". So I assume the drivers were not set up. I have downloaded the drivers but I cannot get them to install properly through my Windows XP system. It just says failed every time. I'm guessing it is not recognizing it since it has no operating system. What should I do? I feel like I have exhausted all resources. I can give any detailed information that you want, but just be specific about what you want from me. Thank you in advance, I am pulling my hair out at the moment.
Click to expand...
Click to collapse
You try to just flash a new rom? Also follow these steps?
http://forum.xda-developers.com/showthread.php?t=1514088

I cannot flash a new rom since i can not move any file onto the internal memory since my computer does not recognize my tablet. I also cannot follow those steps since I cannot access my tablet.

anyone?

Use a micro-sd card?
Or SD card if you have the dock...

I don't have an SD card, I will have to pick one up tonight. I figured that was my only option. But if my computer cannot recognize my tablet, will it once it is in my tablet? I could always put a rom on the sd card with another computer and than move it over and try to flash. Is there anyway I could find the stock rom, I have searched high and low.

cjoconne said:
I don't have an SD card, I will have to pick one up tonight. I figured that was my only option. But if my computer cannot recognize my tablet, will it once it is in my tablet? I could always put a rom on the sd card with another computer and than move it over and try to flash. Is there anyway I could find the stock rom, I have searched high and low.
Click to expand...
Click to collapse
Getting an sd card is not going to fix your problem. You are stuck in a cwm bootloop which is called brick type 1a and you need to sort that first.
The link in the post above takes you to the page that shows you how to get out of brick type 1a but without adb you are not going to be able to do it so you need to get drivers working on your machine or go onto another machine and get drivers installed then fix that first.
Once that is fixed you have 3 options. You can either restore your backup and it should now work or you can adb push a new rom to the internal sd and flash that or you can flash TWRP thru fastboot and that will give you access to an external sd once you have bought one and flash that way.
Either way you are going to have to fix brick type 1a first.
HTH

Related

[Q] Help returning to stock

Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.

[Q] Restore bootloader on Chinese tablet (BC1003), Superpad 8, Flytouch VIII

Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
Click to expand...
Click to collapse
Is youre problem solved??
cejean said:
Is youre problem solved??
Click to expand...
Click to collapse
Hi Have the same problem if anyone can help Please. I'm still new to all this
same problem any ideas
any ideas to fit the problem?
Hello, I had a very similar problem which I had which might help with a BC1003 user.
first was the internal LCD cable came loose.. common problem...
Another was it would not boot at all. So I used Livesuit with "sun4i_crane_bc1003.img" dated August 2012... November 2012 did not work!.
It does appear to matter which .img file you use (unfortunately), because the WiFi does not work with the November version.
hi ... same tablet, some problem...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
hi ... same tablet, some problem...
after 3 days trying every possible firmware, and booting them from external sd card
all i could do was change de logo at boot start from (mapan to kosaco, to oem etc..)
than i had the idea of removing the internal sd card to look at it ...
and guess what it still runs the same with out no sd card in or out
so i thought ... the sd card was never read in the first place cause is damage or corrupted...
so on the 4th day im trying to format and partition the new internal sd card... hoping for the best.
by know u may not even have that tablet anymore but is food for thought for a next android promblems.
:good:
Click to expand...
Click to collapse

accidently formatted. no rom...need help!

Im faily new to the android world. please forgive me of any stupid questions that i may ask.
I was trying to reinstall a new version of maximus 7 on my htc one .
i had the CM 10 installed and was having wifi issues. read that i should clear data and what not and instead of doing a factory reset....i did a format...
now i have no rom on the phone and cant figure out how to do this.
ill upload a video on what i currently have going on...
when i plug it in to the computer...i head the noise from the computer saying that it connected..but nothing popped up.
please help.
heres the youtube video of whats going on with the phone. take a look and suggest any fixes . thanks.
youtube.com/watch?v=NCSJPpLuQiE
adb sideload. you should search this thread there are many that will help you
i searched what i could. didnt find much because im not familiar with terms much.
andrey64 said:
i searched what i could. didnt find much because im not familiar with terms much.
Click to expand...
Click to collapse
you should download all in one toolkit and use the sideload feature. read the on screen directions as you go through the process and you should have no problems
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery

[Q] Need some help on rom install

Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
combsco said:
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
Click to expand...
Click to collapse
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
.torrented said:
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
Click to expand...
Click to collapse
It made the file location, I'm waiting to see if it finishes copying it, as it's just sitting still at the moment.
Got it to work. Mods, you can delete this thread.

Alcatel One Touch Pixi 7 9006w tmoble help

I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol

Categories

Resources