Here are all of the procedures I followed to see if you can help me any. Believe me, I've tried searching everywhere.
1. I downloaded the latest version of the Windroid toolkit, found here (http://forum.xda-developers.com/showthread.php?t=2499926). I saw it worked with HTC Vivid on 4.0.3, which was an old shattered phone I had lying around. That tool is pretty old, so I had no idea what the TWRP version it flashed for me, nor the version of the SuperSU it tried installing. (it downloaded it onto the device but can't install it.)
2. I unlocked the bootloader via the tool, then proceeded to flash the TWRP version it had to the device, it currently works fine (loading into recovery). But I opted not to create a backup for the stock ROM, so that's gone forever. And at this point I can't install the SuperSU because of an error in TWRP "Error executing updater binary in zip" (which I googled extensively to no avail, none of the fixes worked). And for some reason, my computer recognizes when the device is connected, but I can't adb push or fastboot flash recovery "file".img to the phone. I am exasperated and stuck.
Takeaway notes: No stock ROM, Unknown TWRP and Supersu versions. I can't install the SuperSu zip because of "Error executing updater binary in zip". I am not sure how to--if i can--push any other ROMs to my device, because it seems like I can't communicate at all with my device through my PC. Although the fastboot does say "FASTBOOT USB"
This is the stage I'm at. I tried flashing a new image of TWRP, the most recent version that works on my phone, via fastboot. So I have a folder with the adb crap and fastboot crap and the image. I type "fastboot flash recovery twrp.img" and it just goes to the next line without doing anything.
I know this information was all over the place, but I'm not really sure what information you guys need to help point me in the right direction.
Thanks.
Related
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this
Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver
Hi.
I was trying to flash LiquidSmooth ROM, installed TWRP recovery, formatted /data and /cache to F2FS and installed the rom, an custom kernel by mourta and PA Gapps.
The phone stucked in LiquidSmooth bootlogo. I tried to boot in recovery unsuccessfully (my Vol - key is kinda broken), the command adb reboot recovery didn't work.
After many tries, I could flash the LG Stock rom, the Kdz program didn't finish the process and the phone rebooted, don't know why.
Tried many other times to flash.
To sum up, I could flash the original firmware, the phone is booting up normally and aparently is working properly, the problem is: I still can't go to recovery to restore my old rom. (The adb reboot recovery comand just reboot the phone). So, I can't root it or flash another custom recovery.
I wish you guys can help me. Sorry if I written something wrong or if the text is too long, I haven't finished my English course yet.
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
ViniLima said:
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
Click to expand...
Click to collapse
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
ssgabriel said:
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
Click to expand...
Click to collapse
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
ViniLima said:
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
Click to expand...
Click to collapse
I figued out about the error: "Error: more than one device and emulator."
It's an incompatibility with Bluestacks, after close it, it works, but I had to turn off the phone and couldn't flash.
And about fastboot, I could acess this too (Didn't knew that I needed to be on Bootloader mode). But I can't flash the recovery, it says that my bootloader is locked (using fastboot reboot bootloader).
It isn't, or at least wasn't before it all happen. Using ADB command to reboot in bootloader mode (adb reboot oem-unlock I guess), I can flash the .img of clockwork mod and TWRP without error messages, but I still can't boot into it by adb reboot recovery.
Thanks for trying. Today I could acess Android original recovery by hardware keys and install another recovery and ROM.
Having an issue with the unified rooting tool (http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053). Paid for the pro version because i enjoy supporting quality work.
Went to do the all-in-one unlock/recovery/root, however it's not rooting for me. The final step of rooting gets stuck in TWRP and nothing happens. The program says 'Recovery mode not detected' and just hangs asking me to try again, ask for help, or abort.
I have ADB and everything on and working as unified can connect to my phone, just can't get root going.
The phone is now unlocked with TWRP, but I can't achieve root. I flashed 5.0.1 via the app. Anyone have any clues?
edit: did it manually (before reading simms22's post). was hoping for lazy-automated as i paid money for the app and all.
If you have twrp installed just flash SuperSU. The newest version of SuperSU (2.37 or something I think) can be flashed like old days.
lol, learn to root a nexus the right way. its easier than using a toolkit..
1. fastboot oem unlock
2. fastboot flash yourself a recovery
3. flash the latest supersu with that new recovery
4. reboot and profit
root
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
Hi guys.
I hope someone is still reading these forums and able to help me out.
I have this Z1 C6903 (if I remember the type correctly, it's the standard European version) and I once managed to install Carbon ROM 5.1 on there succesfully. It has TWRP for recovery. It's at 3.0.2
So I guess the bootloader is already unlocked, though I don't remember that.
Now I wanted to install Carbon ROM 6.1 and first tried tha standard reflashing from the Settings. Buit that failed. So I tried from TWRP. Failed again.
Then I did a full wipe and tried to flash the ROM. Failed again of course. So now I'm kind of stuck with a device that has only TWRP and no OS....
So then I read that TWRP has to be updated. I found TWRP 3.2.1 for Honami and loaded the img on my SDCard. I tried to flash it from TWRP, but somehow it returns an error....
I tried hooking it up to my pc. When in TWRP, I find the device when I type "adb devices". It returns the device. When I then type "adb reboot bootloader" the screen turns black and nothing else. "fastboot devices" returns "waiting for devices". Screen black.
Anyone got any suggestions here? I still have the recovery. So I should be able to get somewhere, but I'm at the end of my talent...
Thanks!
Liebaart said:
Hi guys.
I hope someone is still reading these forums and able to help me out.
I have this Z1 C6903 (if I remember the type correctly, it's the standard European version) and I once managed to install Carbon ROM 5.1 on there succesfully. It has TWRP for recovery. It's at 3.0.2
So I guess the bootloader is already unlocked, though I don't remember that.
Now I wanted to install Carbon ROM 6.1 and first tried tha standard reflashing from the Settings. Buit that failed. So I tried from TWRP. Failed again.
Then I did a full wipe and tried to flash the ROM. Failed again of course. So now I'm kind of stuck with a device that has only TWRP and no OS....
So then I read that TWRP has to be updated. I found TWRP 3.2.1 for Honami and loaded the img on my SDCard. I tried to flash it from TWRP, but somehow it returns an error....
I tried hooking it up to my pc. When in TWRP, I find the device when I type "adb devices". It returns the device. When I then type "adb reboot bootloader" the screen turns black and nothing else. "fastboot devices" returns "waiting for devices". Screen black.
Anyone got any suggestions here? I still have the recovery. So I should be able to get somewhere, but I'm at the end of my talent...
Thanks!
Click to expand...
Click to collapse
I have the same problem and I hope someone can help
same issue, cant update to 3.0.2 or any newer. 5.1.1, unlocked BL, rooted, dualrecovery 2.8.7
only difference, i dont have an sdcard plugged in, so im sideloading through ADB running from PC.
It gives an "ok" during installation - should be working. But reloading into recovery, its not there (just the old version).
The same thing happened previously to me...
Using Rashr might help. But u need to install the oldest version of twrp official 2.8.7-0 then only u can smoothly upgrade to new one 3.0.2-0 and upgrading again to the latest (i think) unofficial twrp 3.2.2-0 (if u wanna upgrade to Nougat or Oreo).
If the Rashr or TWRP Manager didn't work, try XZ Dual Recovery https://forum.xda-developers.com/showthread.php?t=2261606
But once u upgrade the twrp after tht... It won't be dual anymore...
Hope it might help...
(If anyone else got a simplest way... Pls share ya..)
Just an update. I was able to find a solution after I hadn't touched the device for several months now.
So I could only boot into recovery TWRP 3.0. The Fastboot procedure didn't work anymore for some strange reason. So volume up and connecting to the pc did give me the blue LED, but the "fastboot devices" command did nothing. Only when the device came into recovery by pressing volume down and on/off and then connecting to the pc gave a result on "adb devices".
Getting out of this was fairly simple in the end. Luckily I could still flash an older 6.0 ROM on the device with TWRP. After gapps I could then install the TWRP app from the Play Store and update TWRP to 3.2 after which I could finally install the ROM I liked.
Phew....