I have tried everything i could think of to no avail. It just keeps telling me FAILED: Remote Unknown Command. Ive googled this to find any solution but nothing is working. I'm using the H830 running 20a.
TristanE17 said:
I have tried everything i could think of to no avail. It just keeps telling me FAILED: Remote Unknown Command. Ive googled this to find any solution but nothing is working. I'm using the H830 running 20a.
Click to expand...
Click to collapse
did you follow the instructions correctly? you must (always) have a copy of twrp image on your internal memory.
Yes I followed everything to the tee and I have a copy on internal memory and still no luck
I'm having the same issue, wondering what's wrong. I was trying to get LineageOS on my G5, and was following the instructions exactly as it said (it's not the first time I've unlocked a bootloader), and then I encountered this error when trying to flash TWRP. It's possible that you may have to root your phone before you can actually do this, although I haven't tried that yet. If anyone can link me to a way to get TWRP without having to do this, please do.
Related
I did a factory reset on my LG Revolution and now its stuck in a clockworkMod Recovery boot loop. I Can't put anything on my SD card because my phone doesnt show up in my computer. What can I do to fix this help please! If this is in the wrong section I'm sorry it's my first time posting.
Use adb to push files from your computer to your phone.
Could you provide a link if it's not to much trouble I don't really know what I'm looking for. Thanks.
post-mortem said:
Use adb to push files from your computer to your phone.
Click to expand...
Click to collapse
Here are a few guides, pick the one you like:
http://forum.xda-developers.com/showthread.php?t=879701
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=502010
post-mortem said:
Here are a few guides, pick the one you like:
http://forum.xda-developers.com/showthread.php?t=879701
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=502010
Click to expand...
Click to collapse
I am really sorry but i don't understand how to do any of these guides i can't download adb in the first guide because of a DNS failure. I've tried all of them and i just get so lost trying to figure out what i'm doing. I don't know if there's a way you could help me anymore but if you can't then it's okay.
I had this same problem. Am also illiterate when it comes to programming. I tried a factory reset and now it only comes up in CMR. I assumed it had uninstalled the factory and CMR interrupted it when it went to reinstall because it overrides the stock recovery mode. So I thought I was looking at a case of having no operating system on there at all and installing a ROM would help. I put the sdcard in a different phone so I could put the new ROM on there. Still doesn't work. The problem is that it appears all the ROMs need the original ROM on there to install over top of. Even after it says they are installed, it still only boots up in CMR.
Had I known rooting the phone would put CMR on there, I wouldn't have done it. I only rooted so I could do the android tether. Anybody been able to figure out his problem yet?
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
Click to expand...
Click to collapse
what that is its most likely the rom you downloaded is for a different phone, are you sure it was your phone specificly? check model no. if not theres a option in CWM to uncheck signature verification and it will sorta force flash what you wanted to flash.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Click to expand...
Click to collapse
Read the Question before posting stupid Answers, this shows that you didnt even read it...
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Klowdz said:
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Click to expand...
Click to collapse
have you tired factory reseting it again? the setup wizard crash is really werid at a stock rom.
I have. Same result.
Perhaps I deleted some file needed for the wizard to function properly.
I don't mind flashing a new ROM into the phone, or do whatever else in order for it to work properly.
Klowdz said:
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
Click to expand...
Click to collapse
Try installing the ROM again, doing the correct wipe. After installing the ROM give the fix permission option.
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Klowdz said:
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Click to expand...
Click to collapse
If phone boots, is rooted and setup wizard stops just remove setup wizard app via adb.
Code:
adb shell rm /system/app/<name-of-setup-wizard-app>.apk
Cheers,
AJ
How do I do that? I have the SDK and everything installed, but that's it.
Klowdz said:
How do I do that? I have the SDK and everything installed, but that's it.
Click to expand...
Click to collapse
Following steps are for Windows PC
U need to find a file called adb in the folder of SDK
I use an older version of SDK and it's in folder named 'platform-tools'
Open the folder which contains this file
Then u need to open command prompt window there
( Do that by holding shift while right clicking in the folder then select 'open command window here' option)
Then u can type the following code
in the window.
Abhinav2 said:
adb shell rm /system/app/<name of setup wizard>.apk
Click to expand...
Click to collapse
Sent from my GT-I9000
It says it's a read-only file system.
Maybe It only works if your phone is rooted
If u r rooted U can try adding su command before it
su adb shell rm /system/app/<name of setup wizard>.apk
.
Sent from my GT-I9000
"Su" isn't recognized, but I clearly have it since whenever I try to access adb shell it asks me for permission (not for this task, but for another).
Wouldn't it be simpler to just install the setup wizard again? The problem is where to find that .apk.
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?
I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon
1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh
Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I still have bootloop issue on my oneplus one, running on Cyanogen.
First, I know nothing about developping, I have been self teaching myself over the past 2 days to solve this frustrating bootlopp issue on my oneplus one.
2 days ago I didn't know what was TWRP and adb and fastboot, I have downloaded Android SDK for developpers, Java plateform in between because it was (uselessly) needed, I have flashed images (TWRP), not knowing what flashing was about and not knowing TWRP, randomly following up scattered (and uncomplete) tutorials of forumers writing mysterious and random terms of totally unknown notions for me as a normal user.
This been written, please be clear in your answers, honestly please, maybe some readers may understand how frustrating it can be to read so called tutorials in vocabulary that only developpers can get.
So here what I did so far
1) flash TWRP with fastboot
2) Then I tried entering "make_ext4fs /dev/block/mmcblk0p15". Many posts refer to this as the ultimate solution. (I cannot post link since I am new forumer)
a) First from command, shift+right click in my "adb" folder:
"adb shell" + "make_ext4fs /dev/block/mmcblk0p15"
Didn't work
b)Then I retried in TWRP directly on my phone, going in Advanced>Terminal Command>Select, then type: make_ext4fs /dev/block/mmcblk0p15
Didin't work
3) update the system
Also, I have an update available in my android system, hoping that it could solve the bootloop. When I update, it reboots and goes to TWRP boot mode, is that normal ? If yes what am I suppose to do ? Can an update system actually solve this bootloop issue ?
So far it doesn't solve my bootlopp issue.
What do you think ? What else can we do ?
Have you tried installing (flashing) custom firmware? Go to Cyanogenmod.org, or google "Cyanogenmod 12.1 for oneplusone download", look around, download the custom firmware (Rom) should be a .zip file, move it to your phone, then install it. I can help you more if you need.
Sent from my iPhone using Tapatalk
Hey, thanks for your answer. I ll try later this week and I ll keep you informed.
Just one detail: when flashing cyanogen 12.1, does it mean I completely wipe out my phone to reinstall the rom? (As far as I understand it's like formating a computer and reinstalling window )
there after an cyanigen update. I tried and wiped out my data and so far It works. Very simple, no more than 5min (I spent hours on this problem up to now)
For other readers try this.
If not well try MeowDude advice.
Special note : it looks like update doesn't work though, when it reboots I end up on TWRP and get a message at the end of the update "file md5 not found ". A future problem oncoming? Hope not
So far everything works anyway.
And thanks to MeiwDude
Hi there,
I know this is probably redundant but I've been searching these forums and I'm a bit overwhelmed. Mainly I am trying to discern whether I need to factory reset my phone before I root it or not. If anyone would be kind enough to break it down for a rooting noob, but fairly tech savvy chick, I would really appreciate it. Or just direct me to the most applicable thread for my situation. I have a PC running Windows 8.1 also, if that helps.
Thanks!!!
http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916
Factory reset is not necessary.
stuck
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?
never mind
fabuliz said:
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?
Click to expand...
Click to collapse
i figured it out, thanks for your guidance
dammit
I swear I did everything right but now my phone is on LG screen and I cant do anything
fabuliz said:
I swear I did everything right but now my phone is on LG screen and I cant do anything
Click to expand...
Click to collapse
I think there is a typo in this set of directions.
Try this one:
http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/
(Step 7 is correct here)