Related
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man
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
So, i was in recovery to restore to a previous backup. I was wiping my system to prevent errors but unfortunately i wiped EVERYTHING, including the backup and the OS. So, i kept it in recovery till i got home hoping to just mount my storage and transfer a ROM over and ten install..sounds easy enough. However, i plug my phone in and click mount storage and it doesn't mount with twrp, or even clock work mod.
Soo....i have no OS, can't mount my storage..and i'm stuck.
Can i flash a ROM through command line? If so, how? And why isin't my Droid DNA mounting?
Wttttfff help asap please!
Aaannd...now i'm stuck in the boot screen and it won't turn off.
Just use either adb push or adb sideload
Sent from my HTC6435LVW using xda app-developers app
Nice! forgot about those commands, however it's telling me that adb is not a recognized command. I've forgotten how to fix that? Can you help with that?
Adb sideload starts up and says daemon not running, then start's it succesfully. then says device not found. I'm pretty sure i don't have the right drivers for my DNA, can you point me in the right direction for that?
I really need help, i don't think i can even turn on usb debugging because i have no OS to boot into.
FIXED. I got this
soundofcarnage said:
FIXED. I got this
Click to expand...
Click to collapse
What steps did you take?
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
soundofcarnage said:
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
Click to expand...
Click to collapse
with no o/s and im pretty much on the same boat, how did you get adb to read your device? when i type in adb devices it gives me a blank list of devices
It worked for without ever actually listing my device.
soundofcarnage said:
It worked for without ever actually listing my device.
Click to expand...
Click to collapse
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
IceAzures said:
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
Click to expand...
Click to collapse
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
rsims26 said:
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
no ill try that
IceAzures said:
no ill try that
Click to expand...
Click to collapse
That's kinda necessary.
Sent from my HTC6435LVW using xda app-developers app
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
IceAzures said:
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
Click to expand...
Click to collapse
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
beaups said:
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
Click to expand...
Click to collapse
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
IceAzures said:
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
Click to expand...
Click to collapse
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
beaups said:
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
You did, there's 2 different threads he's posting in.
Sent from my HTC6435LVW 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?