[Q] Bricked? - Asus Eee Pad Transformer Prime

Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all

Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.

Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.

Related

[Q] Can't boot into recovery. . . ever.

Hey All, hope this is the right area. I got my Prime and love it, but being an old
computer geek I wanted a better ROM. I let it update to .21 and regretted it of coarse.So I used the stock Asus unlocking tool, then Wolf's ultimate flash and downgrade(worked, took it back to .15) ViperBoy's newly updated PrimeTool 4.6 to root and installed TWRP 2.1. Everything seemed to be fine and I was ready for Android Open Kang
Project - Build 35. Yes it was awhile ago, AOKP looks great and I was drooling to get it in, but recovery didn't work. I have tried to flash different CWM's in, nothing seems to change my problem, I go into recovery and my Android guy is working for just few seconds, then keels over with the dreaded red exclamation mark sign, Dead. Yes my Asus still works with all it's bloatware and plods along but I really want to fix this and am just about desperate to try anything.
My computer has ADB access, and I have a novice's novice level of skills, can anyone,
anywhere help?
06-25-12
Just went through the rooting thing again. My device IS rooted, but NOTHING will get me in the recovery, now have also tried GooManager and ROM toolbox to attempt to install CWM over existing one(?) >sigh< Does anyone think using ADB to push another CWM would be for helpful then dangerous? Help?

Bought a rooted & unlocked TF201, but want to restore it to factory settings

Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
androidbrownie said:
Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
Click to expand...
Click to collapse
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
flumpster said:
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
Click to expand...
Click to collapse
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
androidbrownie said:
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
Click to expand...
Click to collapse
The way people normally hard brick is by flashing a version of twrp or cwm not meant for their bootloader (ie. flashing a Jellybean Twrp onto an ICS bootloader.)
I can tell by your numbers you posted that you are on the Jellybean bootloader and if you want to make 100 percent sure look at where the nvidia logo is when you turn it on. If it is down the bottom center it is ICS, If it is bottom right it is Jellybean.
The Twrp I linked you to on that page is for Jellybean only.
The only thing that might stay with you is the chinese bootloader but I don't think that will effect anything in the rom. If you really wanted to get rid of that also, after you flash twrp and have it working you could follow the instructions in that second post for "Upgrade instructions for ICS"
Even tho you are on Jellybean now those instructions just flash a version of the Jellybean bootloader that I took out of the world wide release, but I wouldn't do that unless there is some unforeseen problem with having the chinese bootloader.
Thanks! Tablet is all good to go now.

[Q] Stuck on boot screen, no recovery, and now just stock 4.4.2

I have a massive issue...
Somehow I lost my TWRP recovery and when I tried to reflash it, I got the "software unauthorized by Verizon error" each time I started my phone.
I thought, no biggy, I'll just reflash back to VRALJB and all will be well with the world. Did it. No problem.
I then tried to unlock the bootloader. This is when all hell broke loose. I had to reflash VRALJB again and since then, I started getting stuck on the "Samsung Galaxy Note 2" screen (the first one, immediately after the phone turns on). I could not enter recovery using the (Volume UP + PWR + HOME) key combo. I could only enter download mode and use odin.
I tried everything. The only thing that worked was downloading the stock 4.4.2 Verizon image released a few days ago from sammobile.com
(I605VRUFND7_I605VZWFND7_VZW).
Now, I do not have root and my bootloader is locked, but at least I have a working phone and KitKat.
Hopefully the above helps someone, but, my question is, where do I go from here?
How do I go about installing a custom recovery and getting root? I would like to keep stock 4.4.2 as well and before anyone asks why, I want custom recovery for the sole purpose of managing my TWRP backups. Stock OS though.
Since you updated to 4.4.2, there isn't much you can do. No root, no recovery, no safestrap...yet. The only thing you can do is wait for developers to find a way to root this version of android.
Hi my friend, I have met the same problem, so could you tell me how to get that I605VZWFND7_VZW rom~
Please~~

[Q] Samsung Galaxy Tab 2 7.0 [gt-p3113][os deleted][stuck on old cwm recovery]

I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
EvilPenguin42 said:
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
Click to expand...
Click to collapse
Well, I would say that may be a bigger problem ! Now what I think better for you would be trying to flash the stock ROM over to the device again I am sure you have your hands over the flashing. So head over to the sammobile/firmware section and try getting the stock ROM downloaded and flash it over your device.

[Q] Nabi 2 bricked?

Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
mgd014 said:
Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
Click to expand...
Click to collapse
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Awesome respone
aicjofs said:
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Click to expand...
Click to collapse
Man, that worked perfect. Thanks so much. You rock.

Categories

Resources