So i accidently killed my OS,
i can boot to twrp but it tells me its unable to mount storage and the lock pattern i try is wrong (it is not wrong.).
now i did something and it tells me there is no OS present.
what are the adb commands i need to push a new rom/zim on my phone and install it?
please help....
Kyrok said:
So i accidently killed my OS,
i can boot to twrp but it tells me its unable to mount storage and the lock pattern i try is wrong (it is not wrong.).
now i did something and it tells me there is no OS present.
what are the adb commands i need to push a new rom/zim on my phone and install it?
please help....
Click to expand...
Click to collapse
In TWRP use sideload, google it...
https://www.google.pt/search?q=twrp.....69i57j0l5.5091j0j7&sourceid=chrome&ie=UTF-8
hackerpower said:
In TWRP use sideload, google it...
https://www.google.pt/search?q=twrp.....69i57j0l5.5091j0j7&sourceid=chrome&ie=UTF-8
Click to expand...
Click to collapse
i pushed the zip with adb because i coulndn't get sideload to work,
thank you anyways
Exactly same thing happened with me also.
It can be fixed by reflashing twrp from bootloader after that opening in recovery mount the system and do a format.
This worked for me.
Related
Ok, so I was flashing a rom with TWRP.... somehow I deleted my whole internal storage...... So I can access TWRP and fastboot it shows up on my pc win7 but it will not adb. My nexus works just fine. I tried pdanet and naked drivers but no dice. What am I doing wrong?
Thanks,
Danny
i am also have the same problem, please help!
Danny80y said:
Ok, so I was flashing a rom with TWRP.... somehow I deleted my whole internal storage...... So I can access TWRP and fastboot it shows up on my pc win7 but it will not adb. My nexus works just fine. I tried pdanet and naked drivers but no dice. What am I doing wrong?
Thanks,
Danny
Click to expand...
Click to collapse
got to the folder you have adb.exe in, press and hold shift, rightclick and select open command prompt here, then type adb devices if your tab shows up you have adb. Put rom in same directory (folder) as adb.exe. do adb push /name of rom/ sdcard after that you "should" be able to install rom alternately, if you have an external sd card, load rom on card, latest twrp can use external sdcards....
Ok, can't get adb to pickup the tablet in recovery or fastboot. If its just trying to boot it shows up in adb... but when I try to push anything it fails. I think I am on the latest twrp but its not seeing the external sd.
Danny80y said:
Ok, can't get adb to pickup the tablet in recovery or fastboot. If its just trying to boot it shows up in adb... but when I try to push anything it fails. I think I am on the latest twrp but its not seeing the external sd.
Click to expand...
Click to collapse
So when the tab is connected to the pc and it is in recovery, does it show up correctly in device manager?
Gage_Hero said:
So when the tab is connected to the pc and it is in recovery, does it show up correctly in device manager?
Click to expand...
Click to collapse
Yes, It says transformer prime in device manager when its in bootloader and twrp but I cant get adb to see it unless its trying to boot.
Danny80y said:
Yes, It says transformer prime in device manager when its in bootloader and twrp but I cant get adb to see it unless its trying to boot.
Click to expand...
Click to collapse
You have to be running twrp when you are trying to adb... I don't think you can adb while android is running though I have never tried it.
Ok, so adb would not work in recovery at all with twrp 2.0. I could acess fastboot so i just flashed the latest twrp recovery. Once that was done I just mounted the sd card and tada..... I don't know whats up with adb but its a problem if your not running the latest twrp. Just scraped by this time...thank god recovery can now mount sd cards......
Flashed TWRP 2.6.3.0 on my tf201 and now I cant boot to my OS. Unlocked jb bootloader using the Asus method. After booting to recovery TWRP kept asking for a PW. If I press cancel im able to bypass the screen but I cant mount any partitions to flash a rom. I booted back to my OS tried to flash the rom using goomanager but when the tablet restarted it entered a recovery loop. I cant access my OS, cant mount partitions, and ADB sideload keeps failing to start. any help?
http://forum.xda-developers.com/showthread.php?t=1514088 checked out this link but solutions require ADB. none talk about twrp or passwords
lun7200 said:
Flashed TWRP 2.6.3.0 on my tf201 and now I cant boot to my OS. Unlocked jb bootloader using the Asus method. After booting to recovery TWRP kept asking for a PW. If I press cancel im able to bypass the screen but I cant mount any partitions to flash a rom. I booted back to my OS tried to flash the rom using goomanager but when the tablet restarted it entered a recovery loop. I cant access my OS, cant mount partitions, and ADB sideload keeps failing to start. any help?
http://forum.xda-developers.com/showthread.php?t=1514088 checked out this link but solutions require ADB. none talk about twrp or passwords
Click to expand...
Click to collapse
You have flashed the wrong TWRP for the bootloader you are on.
Try the following.
http://forum.xda-developers.com/showthread.php?t=2409602
I know you are bootlooping to TWRP so type adb reboot bootloader to get into the bootloader menu.
flumpster said:
You have flashed the wrong TWRP for the bootloader you are on.
Try the following.
http://forum.xda-developers.com/showthread.php?t=2409602
I know you are bootlooping to TWRP so type adb reboot bootloader to get into the bootloader menu.
Click to expand...
Click to collapse
Hi, thanks for the response. I tried to run adb reboot bootloader but all I get back is error: insufficient permissions for device and in the link you sent they get the device into fastboot mode using the paperclip reset button. His was on the TF300, is it any different for the TF201? How can I get it into fastboot mode since it keeps looping to TWRP with no access to the rest of the system. Im running this on Ubuntu so its definetly not a drivers issue.
lun7200 said:
Hi, thanks for the response. I tried to run adb reboot bootloader but all I get back is error: insufficient permissions for device and in the link you sent they get the device into fastboot mode using the paperclip reset button. His was on the TF300, is it any different for the TF201? How can I get it into fastboot mode since it keeps looping to TWRP with no access to the rest of the system. Im running this on Ubuntu so its definetly not a drivers issue.
Click to expand...
Click to collapse
Where are you trying to run that command from?
You do not go into adb sideload while in twrp. You are already in full adb mode as soon as you load into twrp and you just type the command while there.
flumpster said:
Where are you trying to run that command from?
You do not go into adb sideload while in twrp. You are already in full adb mode as soon as you load into twrp and you just type the command while there.
Click to expand...
Click to collapse
Initially tried to run from ADB sideload but it didnt work obviously. When I run it at the "TWRP Password" screen is when I get the error: insufficient permission for device message. I run the commands after pressing cancel on the password prompt and i get the same message.
*****@******:~$ adb reboot bootloader
error: insufficient permissions for device
[email protected]*******:/home/***# adb reboot bootloader
error: insufficient permissions for device
lun7200 said:
Initially tried to run from ADB sideload but it didnt work obviously. When I run it at the "TWRP Password" screen is when I get the error: insufficient permission for device message. I run the commands after pressing cancel on the password prompt and i get the same message.
Click to expand...
Click to collapse
Hmm, I have never failed to get that command to work but I also have never tried it from linux.
flumpster said:
Hmm, I have never failed to get that command to work but I also have never tried it from linux.
Click to expand...
Click to collapse
will try with a windows machine and report back findings
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?