I don't know how i did this but as i was going to revert back to my stock rom via twrp recovery, my phone couldn't find the file. Somewhere along the way i ended up wiping my phone and now im stuck in recovery with no backup to restore, no zip to flash, and cant even get back to my rom. I can open recovery, and i can go into the boot-loader. Im guessing what i mainly need to do is somehow flash the stock rom using fastboot open window command from my computer, but i still cant seem to find the stock rom.
Im pretty sure the answer is somewhere in these forums but the search isn't working and iv been going through tons of pages with no answer.
Well the good thing is that you're not bricked. If you are S-OFF and know how to use adb go to the link below. Saved my life when I flashed TWRP over my boot img. I'm sorry I can't give you instructions. I just don't feel I could give you clear ones as I know just enough to get around lol. Hopefully that points you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2437436
Sent from my HTC6500LVW using Tapatalk
In this situation all you should have to do is adb sideload the ROM of your choice from your computer and you'll be back in business.
projektorboy said:
In this situation all you should have to do is adb sideload the ROM of your choice from your computer and you'll be back in business.
Click to expand...
Click to collapse
what exactly is adb sideload? is that when i do the open command from adb file and do
fastboot flash zip (Rom.zip) ?
You can also use the Meenova Sd card reader to flash a rom in recovery. Once you flash the. zip you are back up and ready to go. Google Meenova and they have a thread on XDA.
Sent from my Galaxy Tab 10.1
blkoutt8 said:
I don't know how i did this but as i was going to revert back to my stock rom via twrp recovery, my phone couldn't find the file. Somewhere along the way i ended up wiping my phone and now im stuck in recovery with no backup to restore, no zip to flash, and cant even get back to my rom. I can open recovery, and i can go into the boot-loader. Im guessing what i mainly need to do is somehow flash the stock rom using fastboot open window command from my computer, but i still cant seem to find the stock rom.
Im pretty sure the answer is somewhere in these forums but the search isn't working and iv been going through tons of pages with no answer.
Click to expand...
Click to collapse
I did this the first week I bought the phone.
No S-OFF, no RUU. Very scary, but luckily I had @hawknest to guide and save me.
First thing to do is relax, and know your phone is not damaged in anyway and can be recovered quite easily.
The HTC DNA users experienced this as well, so this is nothing new to them.
TWRP houses an "adb sideload" option and it's very easy to use.
or you can adb push the ROM.zip to your internal memory.
I prefer the adb sideload.
If you need help, I will teamview with you (which means I can basically control your computer so I can run the commands) you just need to be there doing what I say.
Hope you get this fixed, it's really dumb how TWRP has it set up for failure like this, and I've tried bringing to their attention but that's a story I will not get into. PM me for help.
andybones said:
I did this the first week I bought the phone.
No S-OFF, no RUU. Very scary, but luckily I had @hawknest to guide and save me.
First thing to do is relax, and know your phone is not damaged in anyway and can be recovered quite easily.
The HTC DNA users experienced this as well, so this is nothing new to them.
TWRP houses an "adb sideload" option and it's very easy to use.
or you can adb push the ROM.zip to your internal memory.
I prefer the adb sideload.
If you need help, I will teamview with you (which means I can basically control your computer so I can run the commands) you just need to be there doing what I say.
Hope you get this fixed, it's really dumb how TWRP has it set up for failure like this, and I've tried bringing to their attention but that's a story I will not get into. PM me for help.
Click to expand...
Click to collapse
I think I pretty much got it. Except just trying to figure out how exactly adb sideload works...is that when I'm in the adb folder doing the open command window to flash my zip?
blkoutt8 said:
I think I pretty much got it. Except just trying to figure out how exactly adb sideload works...is that when I'm in the adb folder doing the open command window to flash my zip?
Click to expand...
Click to collapse
Yes I do believe that sounds correct.
If you don't already know, here is the command
adb sideload /path/to/rom.zip - (rename whatever ROM you are moving over to rom.zip)
Hope to hear you are out of that mess soon, it should never of been set up like that anyway with system where it is.
I have been SOO careful ever since, haha.
blkoutt8 said:
what exactly is adb sideload? is that when i do the open command from adb file and do
fastboot flash zip (Rom.zip) ?
Click to expand...
Click to collapse
No!
adb commands are performed in completely separate places than fastboot commands. adb.exe is completely separate from fastboot.exe. They both help to modify the phone but they depend on completely different conditions to function correctly.
adb.exe commands = when booted into Android & when enabled in recovery
fastboot.exe commands = when fastboot mode is chosen after you've booted to the bootloader (HBOOT screen).
Assuming you're able to install a custom recovery via fastboot, you can boot into that recovery and perform the adb sideload.
Also the "fastboot flash zip" command can only be invoked after you get to the bootloader, go to fastboot mode, and then do 'fastboot oem rebootruu' which is definitely not the typical way for modifying recovery unless you're pushing in a new radio, hboot, or an entire RUU.
projektorboy said:
No!
adb commands are performed in completely separate places than fastboot commands. adb.exe is completely separate from fastboot.exe. They both help to modify the phone but they depend on completely different conditions to function correctly.
adb.exe commands = when booted into Android & when enabled in recovery
fastboot.exe commands = when fastboot mode is chosen after you've booted to the bootloader (HBOOT screen).
Assuming you're able to install a custom recovery via fastboot, you can boot into that recovery and perform the adb sideload.
Also the "fastboot flash zip" command can only be invoked after you get to the bootloader, go to fastboot mode, and then do 'fastboot oem rebootruu' which is definitely not the typical way for modifying recovery unless you're pushing in a new radio, hboot, or an entire RUU.
Click to expand...
Click to collapse
Ok, so how can I flash a .zip or ROM to my phone now through adb sideload? or push a ROM to my internal memory. I just relocked thevbootloader tho in an attempt to flash the RUU .zip that did not work for me.
Which RUU zip did you try using? There are two versions of the RUU that have been posted. Decrypted and Encrypted. Since you re-locked your bootloader I hope you went for the Encrypted version.
blkoutt8 said:
Ok, so how can I flash a .zip or ROM to my phone now through adb sideload?
Click to expand...
Click to collapse
If you have CWM or TWRP installed, you'll have an option for ADB Sideload for a ROM. You don't even have to push a ZIP to the phone. The phone will take the ZIP on the fly.
In CWM, while connected to your computer" you just choose "Install ZIP" > "Install ZIP from Sideload" which will make the device present in ADB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After doing the sideload command from your command prompt the phone will start flashing the ZIP as if it were locally stored.
projektorboy said:
If you have CWM or TWRP installed, you'll have an option for ADB Sideload for a ROM. You don't even have to push a ZIP to the phone. The phone will take the ZIP on the fly.
In CWM, while connected to your computer" you just choose "Install ZIP" > "Install ZIP from Sideload" which will make the device present in ADB
After doing the sideload command from your command prompt the phone will start flashing the ZIP as if it were locally stored.
Click to expand...
Click to collapse
Well that helps! Because I am using the decrypted version. I can't find an encrypted one. I found this other file called
PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
and also I am using TWRP
Being you have TWRP, just boot into recovery and select Advanced->Sideload ADB. Now plug your phone into your computer, run adb, and run: adb sideload (zip file name). It should copy the zip to your internal storage.
If you can get into Recovery. You can mount your internal storage and just copy/paste the ROM through your PC to your phone.
blkoutt8 said:
Well that helps! Because I am using the decrypted version. I can't find an encrypted one. I found this other file called
PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
and also I am using TWRP
Click to expand...
Click to collapse
just to be clear. if you're using adb sideload or adb push - as per everyone's instructions - you want to use a rom zip, NOT the RUU zip!
(correct me if i'm wrong here)
so if you want to flash stock get santod's stock rom from the first post here:
http://forum.xda-developers.com/showthread.php?t=2485319
otherwise use any of the roms from the verizon htc forums
XPEric said:
Being you have TWRP, just boot into recovery and select Advanced->Sideload ADB. Now plug your phone into your computer, run adb, and run: adb sideload (zip file name). It should copy the zip to your internal storage.
Click to expand...
Click to collapse
Cares said:
If you can get into Recovery. You can mount your internal storage and just copy/paste the ROM through your PC to your phone.
Click to expand...
Click to collapse
Well, I was on the wrong forum and I relocked my bootloader. I can still go into recovery tho, but my computer seems to freeze. ugh this is crazy, Ive about had it. I wish my windows 8.1 would just recognize the phone, I'm stuck using my moms old laptop
One could also flash santods stock rom through fastboot.
Fastboot oem rebootRUU
Fastboot flash zip nameoffile.zip
It will fail the first time and say something about flushing the image. Just repeat the process and it will work on second round.
Once it's finished just type
Fastboot reboot
Related
Majorly failed..
It seems i have completely "deleted" some system partitions and i'm currently unable to figure out how to repair them. (This is my hypothesis)
I have CWM v5.5.04
FFF 1.4
I have tried to install TWRP via fastboot and it just freezes on the TWRP splash screen and locks up.
This issue started when i saw the release of CWM v5.5.04 and flashed it using TWRP.
I' read that kindle fire for beginners thread and googled for hours unfortunately i'm unable to find any similar issue.
Any help will be appreciate it.
Also, i am able to fastboot via FFF and can't seem to adb (there's a chance i'm doing something wrong)
Also when i try to install a custom rom via CWM it locks up restarts and then unmounts the SD card. Not allowing me to remount, i have to restart CWM in order for it to read the SD card.
I have a ROM on the sd card, i can't mount SD card via CWM. The option is there i enable it but it doesn't actually mount.
Code:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jsantiago.antonio said:
Majorly failed..
It seems i have completely "deleted" some system partitions and i'm currently unable to figure out how to repair them. (This is my hypothesis)
I have CWM v5.5.04
FFF 1.4
I have tried to install TWRP via fastboot and it just freezes on the splash screen and locks up.
This issue started when i saw the release of CWM v5.5.04 and flashed it using TWRP.
I' read that kindle fire for beginners thread and googled for hours unfortunately i'm unable to find any similar issue.
Any help will be appreciate it.
Also, i am able to fastboot via FFF and can't seem to adb (there's a chance i'm doing something wrong)
Also when i try to install a custom rom via CWM it locks up restarts and then unmounts the SD card. Not allowing me to remount, i have to restart CWM in order for it to read the SD card.
I have a ROM on the sd card, i can't mount SD card via CWM. The option is there i enable it but it doesn't actually mount.
Code:
Click to expand...
Click to collapse
Get into fastboot mode through the bootloader and flash whichever recovery you want.
You cannot use adb while in fastboot mode. You must be booted into recovery or the system software to use adb. Alternatively, you must be in fastboot mode via the bootloader to use fastboot.
To flash a ROM, you would not "mount" the /sdcard partition through recovery. That would make /sdcard available to the host computer and unavailable to the recovery.
EDIT: If you think you've screwed up your partition table, you can use FFF's...
Code:
fastboot oem format
To see if your partitions have valid filesystems, you can use parted through adb while you are in recovery...
Code:
adb shell
parted /dev/block/mmcblk0
Be careful with both of those.
In my experience, most ROMs will repair partitions like /cache and rebuild the filesystems automatically when you boot them.
kinfauns said:
Get into fastboot mode through the bootloader and flash whichever recovery you want.
You cannot use adb while in fastboot mode. You must be booted into recovery or the system software to use adb. Alternatively, you must be in fastboot mode via the bootloader to use fastboot.
To flash a ROM, you would not "mount" the /sdcard partition through recovery. That would make /sdcard available to the host computer and unavailable to the recovery.
Click to expand...
Click to collapse
I apologize for my spelling, i wrote in rush because i just got home from work and want to repair my kindle as fast i can. Haha.
I can't seem to adb on recover via CWM, it seems to either be "not working" or my drivers aren't working correctly. But i been able to adb from my kindle on recovery so i'm not so certain it's a driver problem.
I have tried to flash CWM via fastboot "successfully" but when it boots, you see the errors on the image above. And when i try to install TWRP via fastboot "succesfully" it locks up when you see the splash screen.
jsantiago.antonio said:
I apologize for my spelling, i wrote in rush because i just got home from work and want to repair my kindle as fast i can. Haha.
I can't seem to adb on recover via CWM, it seems to either be "not working" or my drivers aren't working correctly. But i been able to adb from my kindle on recovery so i'm not so certain it's a driver problem.
I have tried to flash CWM via fastboot "successfully" but when it boots, you see the errors on the image above. And when i try to install TWRP via fastboot "succesfully" it locks up when you see the splash screen.
Click to expand...
Click to collapse
See if TWRP will let you drop into a shell through adb... even if you are stuck on the splash screen.
Run parted like I noted in the previous post and get it to "print" the partition table layout (I believe 'print' is the command, but you can also use 'help' for more info). Your /cache partition should have an ext4 filesystem. If it doesn't show that, you'll have to make it... I don't remember the command offhand, but it should be pretty self-explanatory in the help.
EDIT: If that doesn't work, I'll get an output of my partition table and you can compare to what you have.
kinfauns said:
See if TWRP will let you drop into a shell through adb... even if you are stuck on the splash screen.
Run parted like I noted in the previous post and get it to "print" the partition table layout (I believe 'print' is the command, but you can also use 'help' for more info). Your /cache partition should have an ext4 filesystem. If it doesn't show that, you'll have to make it... I don't remember the command offhand, but it should be pretty self-explanatory in the help.
EDIT: If that doesn't work, I'll get an output of my partition table and you can compare to what you have.
Click to expand...
Click to collapse
I just flashed TWRP via fastboot and it's stuck on the splash screen, windows is picking up the drivers but i can't seem to run adb shell, i'm gonna try to play around with drivers and see if i can fix adb.
Edit: I'm unable to adb, just tried to adb via two different systems i keep getting device not found even though drivers seem to be working as they should. I also uninstalled and re-installed drivers about 3 times now hoping that i'm doing something wrong, and still do.
jsantiago.antonio said:
I just flashed TWRP via fastboot and it's stuck on the splash screen, windows is picking up the drivers but i can't seem to run adb shell, i'm gonna try to play around with drivers and see if i can fix adb.
Edit: I'm unable to adb, just tried to adb via two different systems i keep getting device not found even though drivers seem to be working as they should. I also uninstalled and re-installed drivers about 3 times now hoping that i'm doing something wrong, and still do.
Click to expand...
Click to collapse
"Android Phone -> Android ADB Interface" is typically loaded when the device is in fastboot mode. When you are booted into the recovery, you should be seeing "Android Phone -> Android Composite ADB Interface" in the device manager.
Take a look at this...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and see if you can uninstall/remove/reinstall the drivers.
If that doesn't work, go into properties for the device and look at the Hardware IDs list. Let's see what you've got.
kinfauns said:
"Android Phone -> Android ADB Interface" is typically loaded when the device is in fastboot mode. When you are booted into the recovery, you should be seeing "Android Phone -> Android Composite ADB Interface" in the device manager.
Take a look at this...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and see if you can uninstall/remove/reinstall the drivers.
If that doesn't work, go into properties for the device and look at the Hardware IDs list. Let's see what you've got.
Click to expand...
Click to collapse
Okay, i uninstalled and adb drivers seem to be loading correctly? when i'm on recovery i see "Android Composite ADB Interface" i'm guessing it's installed correctly this is the hardware id.
EDIT: My hunch that the error lies on the SD card, i can't mount/format/partition the SD Card & Cache partition. And CWM reboots when i try to mount anything.
PS. Thank you for making the effort to help, i deeply appreciate it.
jsantiago.antonio said:
Okay, i uninstalled and adb drivers seem to be loading correctly? when i'm on recovery i see "Android Composite ADB Interface" i'm guessing it's installed correctly this is the hardware id.
EDIT: My hunch that the error lies on the SD card, i can't mount/format/partition the SD Card & Cache partition. And CWM reboots when i try to mount anything.
PS. Thank you for making the effort to help, i deeply appreciate it.
Click to expand...
Click to collapse
That looks right to me. Can you get to an adb shell prompt? I don't think you'd have issues booting to recovery just because the /sdcard partition is inaccessible. Maybe the /cache partition because the recovery is trying to write its log file there. I don't know that I've run into that exact problem.
Have you tried both the new/old versions of CWMR? TWRP?
Have you edited the partition table at any time?
Do you have critical data on the KF somewhere that you just can't afford to lose?
CWM 5.5.04 was just released a few days ago and not all of the bugs are known/fixed yet. Personally I would use something that has more of a reputation when you're trying to troubleshoot something like this.
From what I've seen, when a rom stalls or freezes at the boot animation, the problem usually happens at the recovery level.
kinfauns said:
That looks right to me. Can you get to an adb shell prompt? I don't think you'd have issues booting to recovery just because the /sdcard partition is inaccessible. Maybe the /cache partition because the recovery is trying to write its log file there. I don't know that I've run into that exact problem.
Have you tried both the new/old versions of CWMR? TWRP?
Have you edited the partition table at any time?
Do you have critical data on the KF somewhere that you just can't afford to lose?
Click to expand...
Click to collapse
I never touch partitions because of fear to things like this happening (Oh sweet irony), i just wipe through recovery and format.
CWM v5.5.0.4: I can access the SD card, see some files including a .zip with a kernel 3.0 rom when i try to flash the rom it freezes and goes back into the "install zip from sd card" options but this time it cant find any files on the SD card. Adb drivers load of from windows, but unable to adb shell.
CWM Previous Version (Currently the one KFU installs, i forgot the version number): Doesn't mount SD Card at all. Adb drivers load of from windows, but unable to adb shell.
TWRP 2.1.1: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
TWRP 2.0.0 RC0: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
----------------
I don't have any data that i honestly worry about, i just wan't my kindle back alive. lol.
I also tried downgrading FFF from 1.3 to 1.4 just for the heck of it, no luck.
that error, is a broken emmc. I hope I'm wrong but my last android phone that did that was the emmc. Google it
Sent from my HTC Glacier using xda premium
jsantiago.antonio said:
I never touch partitions because of fear to things like this happening (Oh sweet irony), i just wipe through recovery and format.
CWM v5.5.0.4: I can access the SD card, see some files including a .zip with a kernel 3.0 rom when i try to flash the rom it freezes and goes back into the "install zip from sd card" options but this time it cant find any files on the SD card. Adb drivers load of from windows, but unable to adb shell.
CWM Previous Version (Currently the one KFU installs, i forgot the version number): Doesn't mount SD Card at all. Adb drivers load of from windows, but unable to adb shell.
TWRP 2.1.1: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
TWRP 2.0.0 RC0: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
----------------
I don't have any data that i honestly worry about, i just wan't my kindle back alive. lol.
I also tried downgrading FFF from 1.3 to 1.4 just for the heck of it, no luck.
Click to expand...
Click to collapse
Yeah, well... if it's your storage device that's busted, that's obviously not going to end well.
Your bootloader is obviously still working. You might as well try the 'fastboot oem format' because it's not going to affect anything negatively if you've never edited the partition table before. Might want to reflash your bootloader right after that though... just in case.
Do you ever get any errors when you 'fastboot flash' any partitions? I don't think it's going to help, but it wouldn't hurt to 'fastboot erase recovery' before you 'fastboot flash recovery recovery.img'. Getting a parted output would really help to see what's going on with your partitions.
I have a couple of other ideas...
Try using
Code:
fastboot boot recovery.img
to upload a recovery straight into memory and boot from that and see what happens. I'd try sticking to TWRP for now. See if that helps matters.
There's also a ICS ROM out there called 'nipad' with the boot and system partitions in fastboot flashable images. You might want to just give that a whirl and see if you can actually get it to boot.
did u fix this yet?
Sent from my HTC Glacier using xda premium
I have not, i am getting back to work from it had to go to bed last night because i had work in the morning. I just got home, gonna try what was suggested i'll give an updated in a bit.
kinfauns said:
There's also a ICS ROM out there called 'nipad' with the boot and system partitions in fastboot flashable images. You might want to just give that a whirl and see if you can actually get it to boot.
Click to expand...
Click to collapse
Do you have any links for nipad by any chance? I am google searching and not finding anything.
Edit: Is there any way i could force flash a rom via fastboot? Or perhaps do system.img etc OR find a edited recovery with a scrip that formats partitions initially?
jsantiago.antonio said:
Do you have any links for nipad by any chance? I am google searching and not finding anything.
Edit: Is there any way i could force flash a rom via fastboot? Or perhaps do system.img etc OR find a edited recovery with a scrip that formats partitions initially?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1506859
Version 4.0.3 near the bottom of the OP. Get your google translate ready unless you're fluent in chinese.
Update; It's most definitely a screwed up partition i tried every suggestion given i'm researching trying to find a solution to do anything via fastboot? I know fastboot has the ability to fastboot update from a update.zip can i somehow flash stock from this?
jsantiago.antonio said:
Update; It's most definitely a screwed up partition i tried every suggestion given i'm researching trying to find a solution to do anything via fastboot? I know fastboot has the ability to fastboot update from a update.zip can i somehow flash stock from this?
Click to expand...
Click to collapse
If you figure that one out, let me know. I've looked around for some documentation or examples, but I came up empty.
I been trying things left and right, to no avail i'm starting to accept my kindles death lol. But i do feel i'm probably doing something wrong with the ADB drivers, gonna refresh my windows install and see if i could potentially have something wrong on my end (i hope).
If i had access to ADB i could fix it i'm sure, gonna search around maybe there's a script that can be preloaded to recovery that could create/repair partions instead of doing so via adb and do it within recovery.
jsantiago.antonio said:
I been trying things left and right, to no avail i'm starting to accept my kindles death lol. But i do feel i'm probably doing something wrong with the ADB drivers, gonna refresh my windows install and see if i could potentially have something wrong on my end (i hope).
If i had access to ADB i could fix it i'm sure, gonna search around maybe there's a script that can be preloaded to recovery that could create/repair partions instead of doing so via adb and do it within recovery.
Click to expand...
Click to collapse
You can install the nipad ROM I told you about earlier. Then you can use smirkit to flash a recovery while booted into the ROM.
Hello, how can i boot in recovery without hardware buttons they are broken? and another thing i dont have any rom instaled, the phone i s-off with 4ext touch recovery. please help. THX:crying:
turn on the phone (u should just get stuck at white htc splash screen) then plug in to pc and open command window and type
adb devices
if ur device shows up then type
adb reboot recovery
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
oh rite, thats a balls. Dont think theres any other way. Try taking the phone apart and cleaning the buttons. ul be surprised at the dust there. Hopefully that will work. If it dont then the only other way is to flash an ruu via bootloader. What does ur phone say in bootloader?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
Did you try running the adb commands that jmcclue listed above while in hboot?
Maybe try running fastboot commands such as "fastboot devices" to see if its recognized.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try "fastboot devices"
capone5 said:
http://img40.imageshack.us/img40/3765/desireintrouble.jpg[/IMG ]i have install adb and when start the process i cant find device as you can see from the picture...i get in fastboot and hboot menu but i cant navigate any futher, is there a way to flash rom threw windows beyond recovery? because i do a full wipe and i dont have any rom instaled on my precious desire :(...[/QUOTE]
Hi Capone5,
One way to do it, is by downloading a recovery img ([url]http://forum.xda-developers.com/showthread.php?t=1791371[/url] or [url]http://forum.xda-developers.com/showthread.php?t=1474327[/url]) unzip and put it in the fasboot folder, plug phone in fastboot mode and type 'fastboot boot [filename].img'
Hope this helps
Click to expand...
Click to collapse
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
capone5 said:
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
Click to expand...
Click to collapse
You dont do "adb fastboot devices". You do "fastboot devices"
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
Would fastboot work without selecting it in hboot? If fastboot is able to detect the phone, then he can use "fastboot boot recovery.img" to boot into a touch based recovery like 4ext (without actually flashing it).
Heres his bootloader:
this i get when just trying fastboot devices
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
the buttons of volume are broken and i try everything to just press - and nothing hapened...how can i load a new recovery threw fastboot?
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
capone5 said:
this i get when just trying fastboot devices
Click to expand...
Click to collapse
have u got the fastboot drivers installed on ur computer?
follow this guide to install them. u cant use fastboot unless u do.
ADB & Fastboot
chromium96 said:
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
Click to expand...
Click to collapse
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
heres a pic
jmcclue said:
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
Click to expand...
Click to collapse
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
chromium96 said:
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
Click to expand...
Click to collapse
its handy to know coz im pretty sure hardly anyone knows that and i bet u cant find it on the old interweb lol
So, I bought a HTC Desire a few days ago and as I've got a ROM I do not like and I've got problems with my SD card I wanted to do some reflashes but I unfortunately cannot. I'm new in the whole Android world but have read a bit already.
When I start the phone with vol. down + power I've got the following info:
Code:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
The problem that 'showed' even more problems after some research:
My phone doesn't recognize my new Adata microSDHC card.
I cannot mount it through recovery, got this error:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
Tried this as well: http://forum.xda-developers.com/showpost.php?p=17874798&postcount=3
The freaking problem is that I always receive such error:
Code:
FAILED (status malformed (1 bytes))
I found out that my USB is bricked, read this thread: http://forum.xda-developers.com/showthread.php?t=691639
But again, I cannot even check my CID using fastboot oem boot, I'm all the time getting this 'status malformed' thing.
Any ideas folks?
EDIT:
My ROM is: Oxygen-2.3.2-Brave
And kernel: 2.6.35.14_r3-stable [email protected] #1
What recovery do you currently have installed?
If you dont have 4ext, i would recommend installing it. It has a usb unbrick feature, which may solve your problem.
Since the sd card isnt recognized the best way to install it would be through fastboot.
Setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Boot the phone into bootloader (volume down and power), then go into fastboot mode
-From your computer open command prompt and run the following command:
Code:
fastboot flash recovery recovery.img
If it succesfully installs, boot into the bootloader and then go into recovery. Next go into the Tools section and select USB unbrick
chromium96 said:
Since the sd card isnt recognized the best way to install it would be through fastboot.
Setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Click to expand...
Click to collapse
I've got all of these already. If I didn't I wouldn't be able to write fastboot doesn't work.
chromium96 said:
What recovery do you currently have installed?
If you dont have 4ext, i would recommend installing it. It has a usb unbrick feature, which may solve your problem.
(...)
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Boot the phone into bootloader (volume down and power), then go into fastboot mode
-From your computer open command prompt and run the following command:
Code:
fastboot flash recovery recovery.img
If it succesfully installs, boot into the bootloader and then go into recovery. Next go into the Tools section and select USB unbrick
Click to expand...
Click to collapse
I've got RA-desire-v2.0.1 recovery software.
When I tried flashing your recovery I received "Program fastboot has stopped working." Windows message.
Dragonji said:
I've got RA-desire-v2.0.1 recovery
When I tried flashing your recovery I received "Program fastboot has stopped working." Windows message.
Click to expand...
Click to collapse
Install the 4ext app and install the recovery. No need for fastboot if your rom is rooted.
abaaaabbbb63 said:
Install the 4ext app and install the recovery. No need for fastboot if your rom is rooted.
Click to expand...
Click to collapse
Yep, sorry. For some reason i thought that he couldnt boot into the rom.
abaaaabbbb63 said:
Install the 4ext app and install the recovery. No need for fastboot if your rom is rooted.
Click to expand...
Click to collapse
There goes the next problem:
To download 4EXTRecoveryUpdater.apk an SD card is needed.
Click to expand...
Click to collapse
You can use adb to install apks. Download the 4ext recovery app, place it in the platform tools directory and run the following command while the rom is booted up:
Code:
adb install 4EXTRecoveryUpdater.apk
Installed the app, however, when I try to start it I'm getting a message that my SD card has to be mounted to use the app. :crying:
Dragonji said:
Installed the app, however, when I try to start it I'm getting a message that my SD card has to be mounted to use the app. :crying:
Click to expand...
Click to collapse
Ok so if that doesnt work i think your only option is fastboot. You cant use PB99IMG cause you have to put that on the sd card.
I dont think usb brick should affect the use of fastboot. Try redownloading the sdk, and try different usb ports.
re
just download the flashable recovery zip and inside ull get recovery img. then start the phone into fastboot (back+power) and flash the recovery with "fastboot flash recovery recovery.img then reboot bootloader, get to recovery and try in the tools the usb unbrick options. first time recovery will start really sllow it will count to 60 trying to mount the sd card but dont worry will start even when it fails to mount it. after the usb unbrick ull restart the recovery and ull be able to mount the sd card if the sd brick was the problem. u dont have to try with apk just download the flashable version of 4ext here: http://www.4ext.net/download.php?f=PB99IMG_2.1.3_RC2.zip&device=bravo and inside the archive u have the recovery.img
aliensk said:
just download the flashable recovery zip and inside ull get recovery img. then start the phone into fastboot (back+power) and flash the recovery with "fastboot flash recovery recovery.img then reboot bootloader, get to recovery and try in the tools the usb unbrick options. first time recovery will start really sllow it will count to 60 trying to mount the sd card but dont worry will start even when it fails to mount it. after the usb unbrick ull restart the recovery and ull be able to mount the sd card if the sd brick was the problem. u dont have to try with apk just download the flashable version of 4ext here: http://www.4ext.net/download.php?f=PB99IMG_2.1.3_RC2.zip&device=bravo and inside the archive u have the recovery.img
Click to expand...
Click to collapse
You just repeated everything i said.
lol i guess i did it wasnt on purpose guess i missed your post no harm to repeat though
I wanted to try on another computer, however, when I connect my phone in fastboot mode I'm getting unrecognized device in Windows (see attachments).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installing HTCDriver3.0.0.007.exe didn't do the trick.
Dragonji said:
I wanted to try on another computer, however, when I connect my phone in fastboot mode I'm getting unrecognized device in Windows (see attachments).
Installing HTCDriver3.0.0.007.exe didn't do the trick.
Click to expand...
Click to collapse
U need to install fastboot drivers (google it) once u have downloaded the drivers, extract the zip file and where it says android 1.0 in that pic, right click it then update driver and navigate to the fastboot driver u downloaded and install it.
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
Edit: here u go
http://androidforums.com/desire-all...ing-unrevoked-windows-updated-14-04-11-a.html
Something new, when I tried to flash recovery in fastboot, cmd said right after executing the command:
Code:
error: out of memory
Any ideas?
OK guys, I managed to flash 4EXT recovery via fastboot! What a newbie's mistake, I didn't opened 'fastboot' option when phone was running in vol. down + power mode and that was a cause of problem! Now gotta fix memory card problem...
In 4ext under tools run 'usb unbrick' or similar. Make sure you reboot into recovery. If it worked then 4ext will load faster and copy some configuration files to the SD. On some occasions I've had to run usb unbrick more than once to get it to work.
Sent from my HTC Desire using Tapatalk 2
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
Nice job in getting adb and fastboot going, btw. I'm guessing you have experience with another Android phone?
Sent from my HTC Desire using Tapatalk 2
genseng said:
In 4ext under tools run 'usb unbrick' or similar. Make sure you reboot into recovery. If it worked then 4ext will load faster and copy some configuration files to the SD. On some occasions I've had to run usb unbrick more than once to get it to work.
Click to expand...
Click to collapse
Does not work.
genseng said:
Nice job in getting adb and fastboot going, btw. I'm guessing you have experience with another Android phone?
Click to expand...
Click to collapse
Nope, no experience.
I tried many things, tested another NOKIA 64MB SD card, doesn't work as well. My Adata works under another phone and I even managed to format it using GParted. Do you guys have any other ideas? Is there any chance it's software problem or do I need to change card slot of my phone?
Hello again, just wanted to inform you guys that I managed to fix my problem, I had to change SD/SIM module to a new one because it was broken. Thank you all for help.
hi XDA'ers
i have accidently deleted everything on my phone including operating system and i wish to restore it again
i have access to TWRP and my phone have S-on
my pc doesnt recognize my phone when its plugged in. But i have a SDcard i can plug to my pc just incase
i have Sdk tools and Adb on my pc
Thanks in advance
Killer2205 said:
hi XDA'ers
i have accidently deleted everything on my phone including operating system and i wish to restore it again
i have access to TWRP and my phone have S-on
my pc doesnt recognize my phone when its plugged in. But i have a SDcard i can plug to my pc just incase
i have Sdk tools and Adb on my pc
Thanks in advance
Click to expand...
Click to collapse
if you usb otg cable, just copy any 4.4.3 custom rom to any usb drive provided your previous os is 4.4.3 ok..go to twrp and flash from otg. you will see the aptions in twrp. Just try.
ferdie553 said:
if you usb otg cable, just copy any 4.4.3 custom rom to any usb drive provided your previous os is 4.4.3 ok..go to twrp and flash from otg. you will see the aptions in twrp. Just try.
Click to expand...
Click to collapse
is it possible to put it on my sdcard cause i cant seem to figure out how to use the usb cable in this state ?
Killer2205 said:
is it possible to put it on my sdcard cause i cant seem to figure out how to use the usb cable in this state ?
Click to expand...
Click to collapse
Yes, either take out the SD card and put it in the adapter like the one shown in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Place it in your computer and then put the ROM onto it, just put back into phone when finished, or:
2) If you're in recovery, connect phone to PC(ADB must be installed) open a terminal in adb/fastboot folder, and type adb push ROM.zip /sdcard2/ of course ROM.zip would be the name of the ROM .zip file you wish to push there. Just make sure you have the "ROM.zip" file in your local adb/fastboot folder, else if it is in a different folder you need to show the path to that folder for example: adb push c:\blahblah\blah\rom.zip it'll just be easier to place the rom in the local folder where adb is...
/sdcard2/ should work but you can also try to push it to /storage/ext_sd/
Killer2205 said:
is it possible to put it on my sdcard cause i cant seem to figure out how to use the usb cable in this state ?
Click to expand...
Click to collapse
it's simple,use any memery card reader to transfer the file and afterwords insert memery card in your device to flash the rom.....
mangesh hotkar said:
it's simple,use any memery card reader to transfer the file and afterwords insert memery card in your device to flash the rom.....
Click to expand...
Click to collapse
it just gives me error it is this rom im supposed to flash right ? http://www.htcdev.com/devcenter/downloads/P00
when i install ViperOne without OS on it says Installation was successful but nothing happens after reboot it just goes into Fastboot everytime i turn it on
Killer2205 said:
it just gives me error it is this rom im supposed to flash right ? http://www.htcdev.com/devcenter/downloads/P00
when i install ViperOne without OS on it says Installation was successful but nothing happens after reboot it just goes into Fastboot everytime i turn it on
Click to expand...
Click to collapse
For some reason I can't open the link you linked to but even then...If it's from the htcdev downloads page, I wouldn't go for downloads there...Most of them are just Kernel Source code for the various regions, some RUUs but not a lot of "ROMs" you'll end up doing something that shouldn't be done, perhaps.
If you're going with Viper, first extract the boot.img file then flash it via fastboot flash boot boot.img then install the ROM. Just make sure you have the correct version. If you're still on 4.4.2 don't download a 4.4.3 Viper ROM as you'll have bootup times close to 10mins as a result of outdated firmware.
BerndM14 said:
For some reason I can't open the link you linked to but even then...If it's from the htcdev downloads page, I wouldn't go for downloads there...Most of them are just Kernel Source code for the various regions, some RUUs but not a lot of "ROMs" you'll end up doing something that shouldn't be done, perhaps.
If you're going with Viper, first extract the boot.img file then flash it via fastboot flash boot boot.img then install the ROM. Just make sure you have the correct version. If you're still on 4.4.2 don't download a 4.4.3 Viper ROM as you'll have bootup times close to 10mins as a result of outdated firmware.
Click to expand...
Click to collapse
im trying to download ViperOne again when i double click the Boot.img file in the Zip it says the file is corrupted so i cant open it
Okay i have now opened boot.img and theres a file called Track 1 in there am i supposed to take that out and put it in the sdcard ?
Killer2205 said:
im trying to download ViperOne again when i double click the Boot.img file in the Zip it says the file is corrupted so i cant open it
Okay i have now opened boot.img and theres a file called Track 1 in there am i supposed to take that out and put it in the sdcard ?
Click to expand...
Click to collapse
the problem is i dont know if there is any Android installed on the phone at all right now i think i wiped everything except for TWRP
cause when i i turn on the phone i dont even see the Android logo it just goes straight to Fastboot
Killer2205 said:
im trying to download ViperOne again when i double click the Boot.img file in the Zip it says the file is corrupted so i cant open it
Okay i have now opened boot.img and theres a file called Track 1 in there am i supposed to take that out and put it in the sdcard ?
Click to expand...
Click to collapse
What?
Just extract the boot.img file from the .zip place it in your adb folder, boot into bootloader and flash with the command I gave. No need to try and extract anything in the .img file. Just the whole boot.img <<<as is and place it in folder.
That way you can flash the boot.img before flashing the ROM. You can place the whole ROM.zip file on your SD card and flash it like normal through custom recovery.
do you have teamviewer? i just dont get it have the Boot.img in a Adb folder on my pc now and ViperOne on my sdcard and what do i do now ?
how do i flash the Boot.img ? when u say flash you mean click install in TWRP right? or else i dont know what flashing is
Killer2205 said:
do you have teamviewer? i just dont get it have the Boot.img in a Adb folder on my pc now and ViperOne on my sdcard and what do i do now ?
how do i flash the Boot.img ? when u say flash you mean click install in TWRP right? or else i dont know what flashing is
Click to expand...
Click to collapse
No, I don't mean that.
I don't have teamviewer unfortunately.
Hopefully you didn't go and just made a folder named "adb" on your computer. Perhaps it's just the way I read it when you say "have the boot.img in a adb folder on my pc" instead of perhaps "have the boot.img in the adb folder. Just want to make sure you we cut out all possible issues.
When you're in your adb folder(adb.exe and fastboot.exe inside folder), hold shift and then right click, you'll see a pop up, just go to "open command window here" or "open command prompt here" can't recall which it is but it's one of those two. It'll then open a command terminal already in the directory where you're at. Start your phone up(You said it goes straight to fastboot so it's fine then). When your phone is started up, type in the command prompt:
fastboot flash boot boot.img <<<That'll flash(hence fastboot flash) the boot.img file onto the boot partition. That's what that command means. Then type:
fastboot erase cache <<<Probably not needed but we can do it anyway.
Then go into TWRP recovery and flash the ROM that you downloaded like you normally would i.e Install zip, change directory to where your downloaded .zip file is on external SD card select it and flash as per usual. Follow installation through Aroma installer as per usual.
BerndM14 said:
What?
Just extract the boot.img file from the .zip place it in your adb folder, boot into bootloader and flash with the command I gave. No need to try and extract anything in the .img file. Just the whole boot.img <<<as is and place it in folder.
That way you can flash the boot.img before flashing the ROM. You can place the whole ROM.zip file on your SD card and flash it like normal through custom recovery.
Click to expand...
Click to collapse
ignore this thought #11 didnt get posted
i had to open Adb thought Cmd right ? or fastboot ?
Killer2205 said:
i had to open Adb thought Cmd right ? or fastboot ?
Click to expand...
Click to collapse
Just open a command prompt like I showed you. Hold shift in the folder, right click and select open command prompt/window here. That's it... It'll open the command terminal in the folder. Have your phone in fastboot mode and use the fastboot commands like I showed you.
BerndM14 said:
Just open a command prompt like I showed you. Hold shift in the folder, right click and select open command prompt/window here. That's it... It'll open the command terminal in the folder. Have your phone in fastboot mode and use the fastboot commands like I showed you.
Click to expand...
Click to collapse
What now it installed ViperOne and Rebooted into Fastboot again ?
it should be installed but i dont know why it enters Fastboot first thing when i turn the phone it on
Killer2205 said:
What now it installed ViperOne and Rebooted into Fastboot again ?
it should be installed but i dont know why it enters Fastboot first thing when i turn the phone it on
Click to expand...
Click to collapse
hm The only time I recall on here of someone with similar problems it was because of an outdated TWRP. I'm not sure if that would be the problem for you though
BerndM14 said:
hm The only time I recall on here of someone with similar problems it was because of an outdated TWRP. I'm not sure if that would be the problem for you though
Click to expand...
Click to collapse
im running TWRP 2.7.0.2 ? :s
Killer2205 said:
im running TWRP 2.7.0.2 ? :s
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/m8
Yeah try the newest 2.8.0.3. Wipe everything again and reinstall and let's check what it does. I also found the thread that I spoke about.
[Q] ViperOne M8 won't boot Post 5 and post 10 was the solution to their problem, both of which was outdated/corrupt TWRP version. It's worth a shot.
BerndM14 said:
http://techerrata.com/browse/twrp2/m8
Yeah try the newest 2.8.0.3. Wipe everything again and reinstall and let's check what it does. I also found the thread that I spoke about.
[Q] ViperOne M8 won't boot Post 5 and post 10 was the solution to their problem, both of which was outdated/corrupt TWRP version. It's worth a shot.
Click to expand...
Click to collapse
How do i replace the old TWRP with the new one ? if possible. or uninstall it
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!