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?
Related
Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Keep up with the awesome work brotha.
You're a maniac!!
<insert witty signature here>
I wake up to this! Nice! I cant wait for proper CWM.
Tomorrow will be a great day as I'm holding mine
Sent from my MB860 using xda premium
telus galaxy note
hi, i tried to back up the kernel for the canadian telus galaxy note with the adb root you have there but when i use adb to run the commands i get an error message saying permission denied. does it work with the canadian version?
Hi, I haven't tested with anything other than the AT&T GNote. Do you get the # root prompt in adb? You likely wouldn't even have adb without the mod working, what error do you get for what command exactly?
when i run
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
i get
/dev/block/mmcblk0p8: cannot open for read: Permission denied
then again do i have to be in recovery mode fir before i run adb? just figured out how to get into recovery.
Since I'm in Canada with the Rogers variant I was going to upload the stock kernel, but somehow I just cannot get into recovery to pull it, I've tried vol up+power, both volumes+power, and obviously vol down+ power is download mode. It's almost embarrassing haha.
I've always made good use of what the dev's have done for us since my N1, I figured I could give back at least a little
looks like i had to be in recovery mode. how big is the kernel suppose to be mine shows about 10MB
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
to get into recovery mode hold vol + and vol - and turn on the phone holding the volume keys and release the power key
Da_G...
I have been a big fan of yours for a long time... You had the BEST Windows 6.5 ROMS I ever used and have always done a lot for the community...
I cannot tell you how happy I was to see that you have this phone and are working on it!
Just wanted to sing your praises
Can't wait to see your new stuff!
Da_G said:
Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Click to expand...
Click to collapse
Thank you for the fantastic work.. Do you have a github or other place we can fetch sources?
Guess this is my cue to get in for the Bell variant.
I'm guessing flashing this will also hit the counter too? Right...
Sent from my Galaxy Nexus using Tapatalk
Ignore me. I goofed up.
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Da_G said:
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Click to expand...
Click to collapse
F***. I've already got your kernel back installed again, and started debloating the Bell one. Tell ya what, if nobody hops on it by tomorrow evening, I'll nuke and reboot back in and pull the larger ROM file. I've just run out of time tonight and have to get back to working on work related stuff.
Edit: As a funny aside, my counter's gonna be in the double digits at this rate. I REALLY hope I don't have to send this thing back lol
I'm already in the 20s myself Can't concern yourself about such things as a dev!
Sent from my SAMSUNG-SGH-I717 using Tapatalk
http://www.mediafire.com/?6atiy1dddr42hp3
telus kernel
G, if i pull the whole rom from the device does that include all the stuff i have put on it already? or just the factory image?
Thanks for the stock TELUS kernel
I've incorporated some of the ramdisk components into my ramdisk for the next version (I used ramdisk from Skyrocket there) - differences are minor.
I'll get an odin-to-stock-TELUS-kernel image up tomorrow!
I have done searches and come up with nothing, I also cant post links so any help in that regard (post links for me etc) would be helpful until I hit 10 posts.
Ok so I started reading the "[GUIDE] Fix Mainver Error" Thread and I followed theses instructions.
1.Connect phone to computer, enable charge mode
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. x.xx.xxx.x
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p24
14.Reboot and you are READY TO ROLL!
This all worked with NO problems. However after following these next steps.
Once your done. And you wanna flash the new radio and hboot and all that fun stuff. Do a backup of your Rom (deleted since I cant post links)(Was a link to ph98img) click that. Then relock your hboot, then flash that file in hboot and you let it update.
This is the part I am now, My phone is stuck at the HTC screen and I can no longer reboot using ADB and if I try holding vol down + power then it simply goes straight to HBOOT to try and update the ph98img again and I can not get to fastboot OR use adb commands.
Id be happy to buy someone a beer to fix this mistake
then unlock once done installing. Then reflash your recovery.. and restore your Rom and your golden
I had the same problem. Put your SD card in another android device, go to a file manager and delete the ph98img. It should work, try it!
polovash said:
I have done searches and come up with nothing, I also cant post links so any help in that regard (post links for me etc) would be helpful until I hit 10 posts.
Ok so I started reading the "[GUIDE] Fix Mainver Error" Thread and I followed theses instructions.
1.Connect phone to computer, enable charge mode
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. x.xx.xxx.x
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p24
14.Reboot and you are READY TO ROLL!
This all worked with NO problems. However after following these next steps.
Once your done. And you wanna flash the new radio and hboot and all that fun stuff. Do a backup of your Rom (deleted since I cant post links)(Was a link to ph98img) click that. Then relock your hboot, then flash that file in hboot and you let it update.
This is the part I am now, My phone is stuck at the HTC screen and I can no longer reboot using ADB and if I try holding vol down + power then it simply goes straight to HBOOT to try and update the ph98img again and I can not get to fastboot OR use adb commands.
Id be happy to buy someone a beer to fix this mistake
then unlock once done installing. Then reflash your recovery.. and restore your Rom and your golden
Click to expand...
Click to collapse
dude this is not a brick, please read before making these threads!!!
andybones said:
dude this is not a brick, please read before making these threads!!!
Click to expand...
Click to collapse
Thanks derp, been reading derp, havent found any answers derp, possible brick doesnt imply a true brick derp.
Can only remove the card, dont have any other devices that can be used to read my sd card. Can get into fastboot without the sd card but from there I am stuck, custom recovery is removed and I am relocked. Looking for information on re unlocking is a little god damn frustrating.
Take your SD card out
Get into h boot, if you can, then go to recovery.
Then, pull back the battery just enough so you can slip your sd card into the phone, make sure the 4 golden sensors (don't know what they are called) are in contact so the phone is still on.
This tricks your phone, or being sneaky. Try that.
polovash said:
Thanks derp, been reading derp, havent found any answers derp, possible brick doesnt imply a true brick derp.
Can only remove the card, dont have any other devices that can be used to read my sd card. Can get into fastboot without the sd card but from there I am stuck, custom recovery is removed and I am relocked. Looking for information on re unlocking is a little god damn frustrating.
Click to expand...
Click to collapse
maybe if you had read more before unlocking your phone, then you wouldn't be in this situation...
Gotta love noobs who complain when someone tells you to read.
con247 said:
What you can do is put the card in almost all the way. Then hold the battery at an angle pressing the contacts on the device so it can get power, but you can still move the memory card. Then (you might need a 2nd person to help you with this) boot into hboot. Since the card is partially slid out, it won't see the PH98 image on there. Once it does it's check, push the card the rest of the way in then snap the battery the rest of the way in. It can be done. I have done it several times while I was attempting to change my cid so HTC Dev.com unlock would work before it did officially.
Click to expand...
Click to collapse
I posted this in several other threads before.. hopefully it helps you. I don't expect you to find it via a search lol so I am posting it here.
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
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
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Thank you! I'll update my guides now you made some folks very happy today.
Sent from my VS980 4G using Tapatalk 4
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
WACOMalt said:
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
Click to expand...
Click to collapse
I am too LOL Thanks for all your help
I had nothing to do with it, all thanks go to thecubed/IOMonster
Sent from my VS980 4G using Tapatalk 4
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
jspradling7 said:
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
Click to expand...
Click to collapse
Yeah that's what I did yesterday as well used my s4 glad I didn't sell it yet
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
I could swear I said just nuke the FOTA partition sometime yesterday as usual awesome job.
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
Thank you!! Where do I send the beer money?
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
Click to expand...
Click to collapse
Nevermind I found it, not used terminal before in recovery, phone back up and running
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
I was upset yesterday worrying about you guys. I am happy to see you happy. Thanks much OP for the fix.
I am rooted and installed TWRP recovery but reverted back to the stock recovery before accepting the VZW OTA update. I'm now stuck in a boot loop and I can't get ADB to recognize my device when plugged in via USB. When I plug in my phone it shows the following:
Fastboot mode started
udc_start()
-reset-
-portcharge-
-reset-
-portcharge-
fastboot: processing comands
Any idea why this is happening and how I can get my phone to boot normally?
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Nevermind I found it, not used terminal before in recovery, phone back up and running
Click to expand...
Click to collapse
I too get the file folder. How do i get the terminal command in TWRP?
synplex said:
I too get the file folder. How do i get the terminal command in TWRP?
Click to expand...
Click to collapse
When you see the file folder just ignore that and hit "select "on the bottom right and that will bring it up. Just type the command from there
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
synplex said:
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
Click to expand...
Click to collapse
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Walter21026 said:
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Click to expand...
Click to collapse
Yea, let's just wait for a ROM worth flashing and "F OTA"
How can we get the OTA if we have TWRP installed?
Can we falsh stock recovery and then accept the Update?
If so can someone please post the Stock Recovery IMG?
My phone is at the LG screen and the notification light is blinking but thats it. How can I adb anything or get into twrp?