Ok... I dont consider myself a competely noob but I am screwed on this one...
So I had Virtuous Prime installed on my Prime and since it was getting slow I decided to do a factory reset (first mistake)
I didnt have a backup of my current settings (second mistake)
So after restore, I got surprised when my Prime rebooted on clockwork...when I rebooted back to recovery again.
So I started googling it and at the same time, I put the virtuous rom in a sd and tryed to flash on clockwork... but, even more surprised, that version of recovery wouldnt read my SD... I just have an option to install zip from sdcard and that will open my internal (clockworkmod "touch" 5.8.1.8)
So after googling all I could, I am now asking for the help of the forum.
In short: Apparently I have no rom installed, clockworkmod wont read my sd for the virtuous rom, and i dont have the rom on the internal.
How can I get out of recovery now?
Solutions I thought about but couldnt find any resort:
-push the rom to internal? how?
-flash any other rom with odin? which?
-flash a clockworkmod (via odin) that would read my sd? how?
Thanks guys
A factory reset would not remove you ROM. I had same issue whit EOS ROM after I updated GAPPs. Prime would always boot into Recovery. Run the following command from your PC then reboot and any new recovery should be flashed by the bootloader and then android should boot.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
musa13 said:
A factory reset would not remove you ROM. I had same issue whit EOS ROM after I updated GAPPs. Prime would always boot into Recovery. Run the following command from your PC then reboot and any new recovery should be flashed by the bootloader and then android should boot.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
Musa13 thanks for the reply.
The thing is... I never used adb before... when I type the command on cmd it wont work cuz i dont have adb... neither on my computer or prime...
I tried with prime connected to the computer with the recovery screen on it. But the computer doesnt say anything about the prime being connected....
do I still have any chance?
You will have to use ADB to fix this. Get ADB from here:
http://forum.xda-developers.com/showthread.php?t=1387527
You will need Windows Drives for Prime from here:
http://forum.xda-developers.com/showthread.php?t=1426502
If Windows give you warning that driver is from untrusted source just ignore it (install anyway).
After you done all of this use Command Prompt and navigate to you ADB folder and then run command:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Thanks for the walkthrough Musa13. First I will read a bit more about adb and will try it when I get home.
I confess I have little knowledge on adb. My experience on flashing/rooting didnt make adb necessary so far (cyanogenmod 7 and 9 on my old galaxy s. thats all).
If you can just answer me some curious questions in the meantime:
-Is that right that theres no CWR that reads SD cards on prime?
-Theres no rom flashable via Odin on the prime?
Thanks again and I will update that later.
diogofmaciel said:
Thanks for the walkthrough Musa13. First I will read a bit more about adb and will try it when I get home.
I confess I have little knowledge on adb. My experience on flashing/rooting didnt make adb necessary so far (cyanogenmod 7 and 9 on my old galaxy s. thats all).
If you can just answer me some curious questions in the meantime:
-Is that right that theres no CWR that reads SD cards on prime?
-Theres no rom flashable via Odin on the prime?
Thanks again and I will update that later.
Click to expand...
Click to collapse
Odin is only for Samsung devices
rogeriok said:
Odin is only for Samsung devices
Click to expand...
Click to collapse
yea... I should have guessed that...
anyway, I got adb running... but it wont see my device...
I have Asus Transformer Prime ADB Interface sucessfully installed on Device Manager...
when I run adb and run "adb devices" it gives me
"list of devices attached" with nothing in it.
When I try to run the comand that Musa13 gave, it says "device not found"...
What may be wrong now?
Thanks
diogofmaciel said:
yea... I should have guessed that...
anyway, I got adb running... but it wont see my device...
I have Asus Transformer Prime ADB Interface sucessfully installed on Device Manager...
when I run adb and run "adb devices" it gives me
"list of devices attached" with nothing in it.
When I try to run the comand that Musa13 gave, it says "device not found"...
What may be wrong now?
Thanks
Click to expand...
Click to collapse
try to uinstall all your's prime drivers from your computer and install 0nly adb naked drivers;this should works...
Ok guys, I am doing some progress....
I wasnt able to figure out why adb wasnt seeing my device, but when I tried this http://forum.xda-developers.com/showthread.php?t=1539352 and changed adb to recovery it worked.
so I put the command above in adb and.... now I am stuck in the splashscreen... no errors
still resarching.... i think i saw something about it in another post.... but any help here will be greatly appreciated
diogofmaciel said:
Ok guys, I am doing some progress....
I wasnt able to figure out why adb wasnt seeing my device, but when I tried this http://forum.xda-developers.com/showthread.php?t=1539352 and changed adb to recovery it worked.
so I put the command above in adb and.... now I am stuck in the splashscreen... no errors
still resarching.... i think i saw something about it in another post.... but any help here will be greatly appreciated
Click to expand...
Click to collapse
Trying to fastboot, but laptop will install drivers for ASUS Android Bootloader Interface but no sdcard...
anything I can do from here?
diogofmaciel said:
Trying to fastboot, but laptop will install drivers for ASUS Android Bootloader Interface but no sdcard...
anything I can do from here?
Click to expand...
Click to collapse
GOT IT!!
so, I realized I wouldnt be able to do anything on Fastboot (or nothing that my noobish knowledge can tell) so I tried boot into CWM again and it worked
so back to adb:
adb push C:\ROM.zip /sdcard/
after the push, i could see the rom in cwm and that was that!!
So lesson learned: DONT FACTORY RESET INSIDE SETTINGS IF YOU HAVE A CUSTOM ROM!
thanks for the fast intro to adb musa13! It really saved my TP!
Valeu Rogerio!
diogofmaciel said:
GOT IT!!
so, I realized I wouldnt be able to do anything on Fastboot (or nothing that my noobish knowledge can tell) so I tried boot into CWM again and it worked
so back to adb:
adb push C:\ROM.zip /sdcard/
after the push, i could see the rom in cwm and that was that!!
So lesson learned: DONT FACTORY RESET INSIDE SETTINGS IF YOU HAVE A CUSTOM ROM!
thanks for the fast intro to adb musa13! It really saved my TP!
Valeu Rogerio!
Click to expand...
Click to collapse
I was the first that hard bricked my prime,hard brick number 2 ,I was unable to fix it; but my my warranty payed a new motherboard for me and this time I will not unlock my bootloader...
rogeriok said:
I was the first that hard bricked my prime,hard brick number 2 ,I was unable to fix it; but my my warranty payed a new motherboard for me and this time I will not unlock my bootloader...
Click to expand...
Click to collapse
Yeah... actually when I saw the spashscreen hang I was like "I read some thread about this..." so I updated here and went to search for that thread... and It was the "How to unbrick (or not) your TP" and then it was the time for me to freeze... but I was thinking "It can't be... I don't get any error... so it can't be hard brick... so I rebooted with the recovery combo Vol_down + Power and I could go to recovery and my heart started beating again.
I am sorry about your brick... but I am wondering how ASUS covered your unlocked bootloader?
diogofmaciel said:
Yeah... actually when I saw the spashscreen hang I was like "I read some thread about this..." so I updated here and went to search for that thread... and It was the "How to unbrick (or not) your TP" and then it was the time for me to freeze... but I was thinking "It can't be... I don't get any error... so it can't be hard brick... so I rebooted with the recovery combo Vol_down + Power and I could go to recovery and my heart started beating again.
I am sorry about your brick... but I am wondering how ASUS covered your unlocked bootloader?
Click to expand...
Click to collapse
the store that I boucht has covered everything,I did not pay anything and
my gps is much better now
i had the same problem.
rogeriok said:
the store that I boucht has covered everything,I did not pay anything and
my gps is much better now
Click to expand...
Click to collapse
Thats interesting... cuz bootloader unlock should void your warranty..... at least is what they say....
Anyways good for you
Hey Folks,
Were you guys able to boot into CWM afterwards ? After I've done dd if=/ ... of=/ i couldn't boot into CWM anymore ... I tried to install CWM by the Rom Manager app and it didint work... tried to install via pc but didnt work .... tried to install via shell but guess what... didint work (i guess it is installed just doesnt work) Always when I try to boot into recovery (Vol DOWN then Vol up) i end up in a android picture with a red ?? triangle plus exclamation on it
Any thoughts on that??
Thanks
Related
I don't know what I did but after install the CWM successfully using PrimeTime 4.5, I couldn't get back into the system, but instead it keep boot back into Recovery mode after every single reboot. I have tried everything within my knowledge include: install the original zip file extracted from US_epaduser9_4_2_14UpdateLauncher.zip using recovery mod, and it stated successfully, but yeah still in a recovery loop; then I tried to install the Virtuous Prime Beta 1 through the CWM, it was also successfully but, guess what, still in the loop again, so I hope if anyone out there has this problem or know the solution, please help me, I am really appreciated... (I can get in to use adb in recovery mode also)...
SMH. Try this
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
I just knew several people were gonna brick device today once unlock tool came out. Already there has been alot..lol
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
shinichikey said:
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
Click to expand...
Click to collapse
If what I linked doesn't work, try looking in developement section in unlock bootloader thread. Someone else had something similar happen, his name Doktaplex. Post in that thread n they can help you. Or send him a pm to ask the method that helped him recover. He knows what to do. Check the unlock threads in general and especially developement section.
demandarin said:
If what I linked doesn't work, try looking in developement section in unlock bootloader thread. Someone else had something similar happen, his name Doktaplex. Post in that thread n they can help you. Or send him a pm to ask the method that helped him recover. He knows what to do. Check the unlock threads in general and especially developement section.
Click to expand...
Click to collapse
thanks, i stalked all the posts by Doktaplex and finally was able to boot out of the cwm...
http://forum.xda-developers.com/showpost.php?p=22850227&postcount=41
theprateik said:
thanks, i stalked all the posts by Doktaplex and finally was able to boot out of the cwm...
http://forum.xda-developers.com/showpost.php?p=22850227&postcount=41
Click to expand...
Click to collapse
Glad to hear the good news. Other guy in other thread might need your help applying this fix. He not sure how to implement it.
If someone who had success with this solution:
kmdm: right, in CWM recovery: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius
and knows how to execute it in CWM, please explain. I'm in the CWM menu on my prime, but I have no idea as to how to implement this solution. If someone could explain this to someone new like me step by step via navigating through screens on CWM, it would be appreciated.
richteratmosphere said:
If someone who had success with this solution:
kmdm: right, in CWM recovery: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius
and knows how to execute it in CWM, please explain. I'm in the CWM menu on my prime, but I have no idea as to how to implement this solution. If someone could explain this to someone new like me step by step via navigating through screens on CWM, it would be appreciated.
Click to expand...
Click to collapse
well, considering you have all the required drivers installed and u know general ideas (like i do) in ADB, then, type in followings in commands (hit ENTER after each line)
adb shell & su
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and then reboot.
and remember u r in cwm while doing this.....
if you still can't get it going, pm me and hopefully we can solve it....
I think commands are pushed with adb from a computer. You'll have first to install and configure adb (must be a thread on this in Prime General section), and then connect your prime to your computer, open cmd, and type: adb shell [enter] then su [enter] the commands from previous posts.
Edit: not fast enough.....
I installed android sdk appropriately to be able to use adb as far as I know. I rebooted the PC. Now I see a device "Full Android On Emulator" under other devices. Is this my prime? When I try the adb commands as suggested, I'm getting error device not found messages.
How do I get adb / my pc to recognize my prime? Since the firmware update messed everything up, my prime is no longer recognized by my pc. Thanks for anyone who is able to walk me through this.
You must have Adb drivers for prime, links must be in the thread about Adb (sticky in general section), and if you run windows 7 try to run cmd as administrator.
Test your connection by typing 'adb devices' first.
you need to download the driver package and install it, and then you can use adb
http://forum.xda-developers.com/showthread.php?t=1426502
i am manage to fix the recovery loop, i can see the logo from the Vicious rom, but when it booted into the OS, I got this message: Encryption Unsuccessful, and the only option there is to reset the tablet... and when i pressed that button, here you go, back to the recovery loop... can someone help me with this?
shinichikey said:
i am manage to fix the recovery loop, i can see the logo from the Vicious rom, but when it booted into the OS, I got this message: Encryption Unsuccessful, and the only option there is to reset the tablet... and when i pressed that button, here you go, back to the recovery loop... can someone help me with this?
Click to expand...
Click to collapse
I'd say do a complete data wipe from recovery. Then try flashing the rom again. Once it works and boots up into OS, give it like 5-10 mins to get settled. Then everything should be fast n smooth.
i did a complete data wipe and everything but same problem still, sigh.... I wonder what i am doing wrong....
Thank goodness. Came home from work today and was able to install the drivers and use the adb commands with success. Rebooted, and my prime was back to rooted .14 Asus firmware. I did a CWM backup of the now functional ROM, did a batch Titanium Backup job, flashed the current version of Virtuous Prime, restored some app data with Titanium Backup, and everything appears to be running fine now. Thanks to everyone who helped despite my critical blunder. Man, last night was a major bummer. Didn't get much sleep. Really glad its all been resolved.
We need to get a sticky going with these directions on how to get semi-bricked TP out of this predicament. Someone please do it soon. Otherwise there is gonna be a FLOOD of threads asking/stating the same things.
Sent from my Transformer Prime TF201 using xda premium
how did you do it, i still got stuck?
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 everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
cficklin31 said:
Hello everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
Click to expand...
Click to collapse
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
flumpster said:
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
Click to expand...
Click to collapse
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
cficklin31 said:
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
Click to expand...
Click to collapse
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
flumpster said:
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
Click to expand...
Click to collapse
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
cficklin31 said:
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
Click to expand...
Click to collapse
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
flumpster said:
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
Click to expand...
Click to collapse
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
cficklin31 said:
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
Click to expand...
Click to collapse
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
flumpster said:
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
Click to expand...
Click to collapse
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
cficklin31 said:
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
Click to expand...
Click to collapse
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
flumpster said:
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
Click to expand...
Click to collapse
Thanks,
Just to make sure I know what I'm doing. I have put the blob file in my ADB directory. Now are these the commands? :
adb shell
fastboot -i 0x0b05 flash recovery twrp.blob
Then if that doesn't work, I try:
adb shell
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
In that post you say to reboot normally, not to recovery. But since I have no rom installed, I need to go back to recovery and try to flash the Hairybean 2.11 rom again. Is that correct?
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
cficklin31 said:
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
Click to expand...
Click to collapse
Fastboot is not adb. You need the Fastboot.exe
---------- Post added at 08:11 PM ---------- Previous post was at 08:04 PM ----------
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
I am going to brick my tablet like yours to try and get out of it.
Try the Fastboot method for now from bootlader.
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
cficklin31 said:
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
Click to expand...
Click to collapse
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
flumpster said:
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
Click to expand...
Click to collapse
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
cficklin31 said:
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
Click to expand...
Click to collapse
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
flumpster said:
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
Click to expand...
Click to collapse
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
cficklin31 said:
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
Click to expand...
Click to collapse
You can only use nvflash if you created backups with it while on ICS.
You know when it says that sending recovery/writing recovery in fastboot, do you see a blue line filling?
No, there is no blue line. Nothing on the bootloader screen seems to change at all.
Sent from my SCH-I535 using xda app-developers app
So I clearly screwed something up. Was running Viper 2.0.3 but went to reset/wipe and think i accidnetly formatted the sdcard then system also in CWM. Now i can't get anything to boot. I can get into CWM but am struggling to figure out how to flash something so a ROM will load. I'm clearly a newby with this. Pretty sure I have adb setup right,as it apprears to recognize the device with adb devices, but this was my first foray into adb so i'm struggling with this. Any help from the community would be more than appreciated, as I'm trying to set this up for my mother's first smart phone.
davescarp said:
So I clearly screwed something up. Was running Viper 2.0.3 but went to reset/wipe and think i accidnetly formatted the sdcard then system also in CWM. Now i can't get anything to boot. I can get into CWM but am struggling to figure out how to flash something so a ROM will load. I'm clearly a newby with this. Pretty sure I have adb setup right,as it apprears to recognize the device with adb devices, but this was my first foray into adb so i'm struggling with this. Any help from the community would be more than appreciated, as I'm trying to set this up for my mother's first smart phone.
Click to expand...
Click to collapse
In CWM select sideload, use the sideload command from the command prompt on your PC to get a rom on the DNA
RLGL said:
In CWM select sideload, use the sideload command from the command prompt on your PC to get a rom on the DNA
Click to expand...
Click to collapse
ok, i was messing with that... so "adb sideload ViperDNA_2.0.3.zip" where the viper zip is in the adb folder? just tried that and is says it * can not read ViperDNA_2.0.3.zip * ?? Appreciate the resonse, i think this is easily solveable since i can boot to recovery and still have CWM.. just need a nudge to get over the top...
EDIT: figured it out... thanks to xda and all for providing a resource so useful.
Adb push Rom.zip /sdcard/Rom.zip
Sent from my dlx using XDA Premium 4 mobile app
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Sorry, also, I have checked through xda and I cant seem to find anything that would explain why I am stuck!
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Fastboot
Lloir said:
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
ryutnm said:
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
Click to expand...
Click to collapse
you tried fulling wiping? then just flashing the rom + bootimage after
thanks
Lloir said:
you tried fulling wiping? then just flashing the rom + bootimage after
Click to expand...
Click to collapse
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
ryutnm said:
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
Click to expand...
Click to collapse
Unless you mean the user data and cache wipe.
Then yeah i did that
ryutnm said:
Unless you mean the user data and cache wipe.
Then yeah i did that
Click to expand...
Click to collapse
Data/system/cache
Sent from my Nexus 5 using Tapatalk
ryutnm said:
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Click to expand...
Click to collapse
Well the bootlooping has something to do with not flashing the boot.img stated by yourself and lloir. About that bug of "Sending boot.img", it happens to me but I fix it by running CMD as administrator , If that doesnt work, try using a different usb port. Preferably one directly to pc/laptop rather than using a hub. Try a 3.0usb port first, if that doesnt work then 2.0usb port.
P.S Without S-Off you can't become hardbricked. Till now I didn't see a single person who bricked their HOX+ unless he received an S-Off developer phone..
Lloir said:
Data/system/cache
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
ryutnm said:
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
Click to expand...
Click to collapse
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Lloir said:
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Click to expand...
Click to collapse
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Edt - just tried the sideload using the cmd, and i had error: device not found
so windows isnt recognising my phone...it was working this morning
ryutnm said:
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Click to expand...
Click to collapse
Why am i being ignored you guys lol. Did you try my solution ?
Terribly Sorry
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
dude, im so sorry - i didnt even see the post!
i will try now!
sorry again
edt - still no joy as for some reason my phone is no longer being recognised by my pc =[
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
*edit the above is assuming you are in recovery
IF NOT in recovery, but fastboot_usb mode
then fastboot devices (but you cannot do jack apart from flash boot image)
IF in recovery, you got a few choices
wait 5-10minutes (don't ask, it's a common issue with the X+ and CWM\TWRP)
put the device in adb sideload for a minute or so (^ see above reason)
i have adb issues in CWM\TWRP myself, especially when i have no rom and so on, so i know your frustration, patience young padwan
looking good so far
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
Lloir said:
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
Click to expand...
Click to collapse
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
ryutnm said:
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
Click to expand...
Click to collapse
might be because of where you have the adb tools. and i'am 100% male
thanks
Lloir said:
might be because of where you have the adb tools. and i'am 100% male
Click to expand...
Click to collapse
well dude, thank you for your help!
I dont understand why though, ive been using this pc the whole time to flash recovery images and boot images and never had to use admin
Thank you
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
ryutnm said:
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
Click to expand...
Click to collapse
Glad you got it working. Just always try those common solutions:
-Restart PC
-Run as admin
-unplug replug
-reboot phone
-try different usb port
-try different usb cable.