Hey guys, I'm only a week old with my first Android device, the Prime.
I rooted it using ViperMOD PT v4.5. Installed BusyBox, Superuser, Titanium backup.
I also installed ROM manager BUT did not install CWM.
Now after installing a font file and rebooting, my Prime is stuck on ASUS screen with a dotted circle rotating forever everytime I reboot.
In the absence of CWM what are the other ways of recovering? Does these devices do not have an ASUS recovery mode?
Kindly help knowing all this as well as Unbricking my Prime.
Regards to all helpers and non-helpers.
Fastboot and APX (nvflash). The latter is not yet available.
I'm not aware of any others
Sent from my i9250 using Forum Runner
bk201doesntexist said:
Fastboot and APX (nvflash). The latter is not yet available.
I'm not aware of any others
Sent from my i9250 using Forum Runner
Click to expand...
Click to collapse
Thanks buddy ! I managed to Unbrick my TFP. I was wondering if there is another way of recovering as I did not had CWM installed. I gathered information in pieces from this forum and managed to put the TFP back in good health.
I followed this;
Put the renamed downloaded OTA (EP201_SDUPDATE.zip) in SD card and boot to RCK and....everything went on automatically.
Thanks once again to all the lovely people here!
Didnt thought of that one though, assumed you were unlocked.
Thanks for sharing back, mate.
Edit: glad you made it and learned something in the process, i truly am.
Sent from my i9250 using Forum Runner
can you help me unbrick mine? i am locked bootloader and on .14 rooted. i edited the build prop and now it just shows a black screen after the eepad screen. i think its the boot window but i disabled boot animation so idk. thanks
fcortes626 said:
can you help me unbrick mine? i am locked bootloader and on .14 rooted. i edited the build prop and now it just shows a black screen after the eepad screen. i think its the boot window but i disabled boot animation so idk. thanks
Click to expand...
Click to collapse
I'm not sure about the "build prop"....But I think you can safely try this as you have not yet tampered with bootloader or kernel layer.
Download the build (xx_epaduser9_4_2_14UpdateLauncher.zip from an authentic source on web (google it). where xx stands for your SKU. You must be knowing that.
Once downloaded extract all and you will get another zip file (do not bother about its name; you have to rename it anyway)
Rename the extracted zip to EP201_SDUPDATE.zip
Put it on the SD card, shut down the TFP and insert the card in the slot.
Press and hold the power up while holding the Volume down button to go into recovery mode.
Once into RCK, release both buttons and press Volume up to confirm within 5 secs.
Once done, the TFP will be able to locate the zip file on the SD card and re-write the entire OS for you.
This method is safe and asus stock way of recovery.
(I assume since you have a locked bootloader you also do not have CWM installed)
Let me know what happens.
I think you cant tweak build.prop and try to ota.
If adb is available:
Get blob pack/unpack tools, grab the blob from inside that ota you flashed, unpack it, push /system/build.prop to transformer with adb shell (adb remount first or issue mount command manually to get /system with rw permissions).
Sent from my i9250
Related
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man
hello
First time, Long time. Just managed to install twrp2.2 and it is a nice ui for any sytem. But my issue is rough.
I was going to install a new rom with a Merto pcs service flashed over from Sprint. Unlocked S-om with rom manager on it
when I received it back. Read alot and many peple claim it is ok to stay with 1.50 so-on, others say to go back to 1.40.
I managed to root the device per maxs evo hacks and until I installed and accidently wiped kel/cashe, System by accident,
Anyways I even tried removing the 8 gig sd card and used a fully backed up same card to try and get recovery img file to boot into.
No luck because it goes into a screen that says (Parsing...[SD ZIP under that it says [1] RECOVERY . Then , Do you want to update
up=yes , down = No. Tried yes and continues bootloop.
Then I tried putting back the other sd card and that allows me to go onto the twrp ui but no ofixes that I know of or can do.
Can anyone help me, I will look out for you, really.
Thanks in advance. D-ACman Florida.
If I read correctly, you need to take out your SD card and put into a PC to remove the pg86100.zip img off of it. Put it back then go back to the bootloader and go to recovery. After that, flash a rom.
Sent from my PG86100 using Tapatalk 2
I cannot get anyrom to install
Cetus Corr said:
If I read correctly, you need to take out your SD card and put into a PC to remove the pg86100.zip img off of it. Put it back then go back to the bootloader and go to recovery. After that, flash a rom.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Ok I can try that but believe me I tried to do just that when thigs went crazy. So I though I should reinstall stock ruu after accidentally
wipeing my system along with cashe/kalvik/ and complete wipe, I somehow wiped the bootdrive of what it is telling me is the is no OS
installed si I'm at a loss and I k now if I can get into trwp recovery I can get a Rom either stock or other to be read and installed.
Each time I get bootloops and what I'm thinking is I should have take fastboot off when try to install an ICS rom, but that is still not the issue
I just believe I wiped eveything because of the statement on twrp ui that there is no OS installed.
I really appreciate whatever feedback and instructions you can give me. Just tell me what to try or do and I will
Thanks very much.
Download twrp recovery.img file. Put into your adb platform tools folder.
With phone off hold volume down & power.
Once in the bootloader, select fastboot.
Open a command from your platform tools folder. Then type..
fastboot boot recovery.img
Then just flash another ROM. If your sdcard is wiped , just toggle USB mass storage in recovery & transfer from computer.
Hope that helps
Sent from my PG86100 using xda premium
SketchyStunts said:
Download twrp recovery.img file. Put into your adb platform tools folder.
With phone off hold volume down & power.
Once in the bootloader, select fastboot.
Open a command from your platform tools folder. Then type..
fastboot boot recovery.img
Then just flash another ROM. If your sdcard is wiped , just toggle USB mass storage in recovery & transfer from computer.
Hope that helps
Ps...remove that PG86IMG.zip from your sd card.
If you don't & its asks...select NO
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Sent from my PG86100 using xda premium
No Go
SketchyStunts said:
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Ok woke up early today and I had seen this type of fix on another page on Q&A. SO first I had to get the file but you cant just
open prompt and type a command but I k now I had to go to the tools folder after inserting the .img file. Ok did that.
Since I have always kept my SDk in the root of my C:dr it's easier to hold shift down and right click on the tools folder then I placed the commands and brother, for lack of a better word or terminology,--- Absolutlely nothing happens.
Now am I using the right syntax commands? maybe not but the way you gave me the advice I thought it might get the img file onto the internal
drive of the phone.
Man I tried to even put the trwpzip file onto the sdcard and install it, unfortunetly that did'nt work either. So when I use the file manager
in TWRP2.2 I can see the files in the root of the phone and when I go and tap on the inner usb dr I have no files that I can see.What I might
have to do is to take snapshots of the actual menus I am seeing and perhaps I can get help that way.
I know it is difficult when you can't see exactly what is on my phone screen.
What about the DUMLOCK method within the ui of twrp. I have to digest some info on that section for I have'nt a clue about what the
dumlock does but if it's in the twrp UI it must be of some importance.
I really appreciate what you guys are doing for me and wether I get it fixed with or without your methods I will definately give U points for
taking time out to read my issues. I have not mentioned that I also have a duplicate phone (My 1st EVO) and that one came with 1.40 H-Boot
as opposed to this one with 1.50. nevertheless it is a good feeling, I know, when you can get ur **** running and installing Roms like if it was
a candy store. Im an old school type guy, as far as age is concerned and I am a Self employed Sub HVAC/R TECH and I Love to play with
ANdroid and all that goes with Flashing. I just wish I would have went to school for Computer Programming instead of AC.
But it is what it is. Sorry for the long life history and thanks again, If U can figure something else out please reply. Thanks
D-ACman
Still on Bootloop
dacman55 said:
Ok woke up early today and I had seen this type of fix on another page on Q&A. SO first I had to get the file but you cant just
Ok here I'll try again.
Phone is Evo3d Flashed to Metro PCS
phone is unlocked and S-ON
TWRP 2.2 recovery
when noticed I was low on space on my micro sd card I then replaced it witha pny 32 gig class 4 sd card
It comes already formatted 32 fat but I did another clean format on the computer
I replaced or copied everything onto the new card then installed it the working evo 3-d
I was on mikV for a few days but once I got into leedroid tweeks I then decided to just flash my nandroid recovery and go
back to stock.
At that time I was on CWM 4040 or something to that affect.
I noticed the beautiful UI for the TWRP 2.2 and decided to use that recovery.
As soon as I decided to use another custom rom the **** hit the fan.
So now I'm back where I started and I am reading many posts where I think I need to go and relock the phone
then install the stock rom and hopefully that will work.
What I need is to get step by step on the command prompts and computer to recognize the phone
when I try to place the image thats necessary to do the "fastboot lock commands and that it is seen working.
That's where I'm stuck at and am going from this dell laptop computer to my desktop and start the ADK/SDK download
put it in the C: drive and hopefully In the cprompt it will communicate to the phone.
I there a nooby guide to the step by step command procedure to do this?
Click to expand...
Click to collapse
Not so recently, I messed up my Transformer Prime. I was trying to flash a new ROM so I decided to clean all the partitions, memory card, etc. Long story short, I'm nearly sure I deleted the ROM and the recovery... When I turn it on, It won't boot past the Eee Pad splash screen, and if I turn it on holding the volume down button and power button, the white text on the splash screen doesn't go past "Booting recovery kernel image". Is there any way I can fix this? I loved my Prime and I really want to fix it from it's current paper-weight position.
HuskyHamburger said:
Not so recently, I messed up my Transformer Prime. I was trying to flash a new ROM so I decided to clean all the partitions, memory card, etc. Long story short, I'm nearly sure I deleted the ROM and the recovery... When I turn it on, It won't boot past the Eee Pad splash screen, and if I turn it on holding the volume down button and power button, the white text on the splash screen doesn't go past "Booting recovery kernel image". Is there any way I can fix this? I loved my Prime and I really want to fix it from it's current paper-weight position.
Click to expand...
Click to collapse
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Gage_Hero said:
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Click to expand...
Click to collapse
my situation is even worse. i get the twrp boot loop, but can't enter fastboot. i can only work in the twrp menu. is there a way to unbrick it?
Gage_Hero said:
Download the universal naked drivers in the dev thread and see if you can fastboot to it... then you will have to flash the recovery (through fastboot) then adb and push the rom to it....then install rom through recovery... suggest you use twrp just make sure you use an older version if you haven't used nvflash.... think you need 2.1.... I have a copy somewhere here or you can probably find it in the q&a section as I have posted it there at least once.....
Click to expand...
Click to collapse
Not to sound like a noob or anything, but I'm not entirely sure how to do all of this. Could you help me or is there a guide or something?
HuskyHamburger said:
Not to sound like a noob or anything, but I'm not entirely sure how to do all of this. Could you help me or is there a guide or something?
Click to expand...
Click to collapse
Look here, if you need more detail, pm me and let me know....
http://forum.xda-developers.com/showthread.php?p=31616679#post31616679
My system directory seems to be missing. I've installed teamwin Recovery but am unable to mount the system drive. When I install the latest Cyanogen Mod nightly it appears to install but won't boot. All I've got is Recovery and Fastboot. Help!
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
DustL82 said:
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
Click to expand...
Click to collapse
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
flumpster said:
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
Click to expand...
Click to collapse
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
DustL82 said:
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
Click to expand...
Click to collapse
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
flumpster said:
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
Click to expand...
Click to collapse
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
DustL82 said:
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
Click to expand...
Click to collapse
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
flumpster said:
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
Click to expand...
Click to collapse
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
DustL82 said:
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
Click to expand...
Click to collapse
It can be repaired by asus. Ask them how much to fix. If it's too much these will sell on eBay as people want them for the screen etc.
Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
motorom said:
Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
Click to expand...
Click to collapse
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
flumpster said:
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
Click to expand...
Click to collapse
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
motorom said:
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
Click to expand...
Click to collapse
You have now killed it completely. I said to try and fastboot the correct twrp as that was your only chance.
Don't thow it in the garbage!
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
http://rootzwiki.com/topic/35086-guide-nvflash-general-users-guide-unbrickrecoverdowngradeupgrade-tf201/
Good luck!
blade2k11 said:
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
Good luck!
Click to expand...
Click to collapse
thank you for trying to help me but it looks like my Prime is bricked forever...I'm new in this things and I didn't enable nvFlash before messing up my device, and of course I don't have the required files to unbrick it. I will wait a little bit maybe a solution will appear after a while...if not then my Prime will be sold for parts on ebay(( I still can't believe that I killed it by making a stupid little mistake...