I seemed to have screwed over my One...
While attempting to install a custom rom I seem to have gotten stuck in TWRP. I successfully installed SU and TWRP but when I went to install the custom rom, it would not install. This was after I wiped the other data from the phone so it just keeps booting me into recovery. I have a backup made of the stock rom but it is on my computer and being the HTC One and not having a removable sd...I have no way of getting the file to the phone. When the phone is connected to the computer and in fastboot USB in the bootloader, the computer makes the noise that the phone is connected, but does not show the phone in windows explorer. I have NO IDEA how to get the phone to boot past recovery or get the computer to recognize the device... HELP
You should still be able to salvage this situation.
When connected to your PC you could push the file via ADB. Another option, if you have no problem getting back into TWRP is to go into the advanced menu and flash a ROM with ADB Sideload.
Most important, stay calm, take a few deep breaths, and things should right themselves.
Sent from my HTC One using Tapatalk
If you are unable to use adb another option is to save a rom onto a flash drive and connect it to your phone with a otg cable. Then when in twrp go to install you can select the external drive and flash from there. I use this method when I format my device and it works perfectly. I hope you sort your problem out, good luck.
sent from my one using tapatalk
Phones: Htc one s-off & supercid running omni rom nightlys & teamseven kernel.
Nexus 4 running cm 11 nightlys & stock cm kernel.
Moto g stock
Tablet:Nexus 7 2013 running omni rom nightlys & stock omni kernel
Take deep breaths, don't panic... I did the same thing and freaked out, but I used adb sideload. Open up the cmd window on the pc, boot into recovery, type adb side rom.zip(whatever the name of the rom is. Wait for the file to transfer and install your rom. Hope this helps
Related
Hi, i'm new to this forum and i need help to fix my phone. I tried to mod my phone and I end up brinking it (I think) and here is what I did:
1- Unlock my bootloader. Successfully
2-Flash TWRP recovery image. Successfully
3-Rooted with Android_Revolution_HD_Root_and_BusyBox. Successfully
4-Here is where everything started... I tried to flash a rom (Bulletproof-m7-3.2) and everything went wrong and please do not ask what because i do not know :crying:
now I do not have no OS and my internal storage is not working or missing or it being wipe off I do not know. I can access bootloader and TWRP recovery image but i can't install another rom because of the problem with the storage that do not let me copy files into it. Well hopefully somebody could help me with this and here is a picture from the bootloader.
Can you boot into your twrp recovery? You can always install the rom through side load. Some one correct me if I'm wrong with that because I'm not very experienced with that but I'll look around for a thread for it.
However I use a method I feel is very simple, but you just need a otg usb adapter. Put your custom rom zip on a flash drive and plug it in the otg before booting into recovery. Make sure you have the latest twrp too (2.6.0.0). The n you can install from external SD.
Again though, I think you can install from a side load method or adb.
Sent from my HTC One using xda app-developers app
Jmarv said:
Can you boot into your twrp recovery? You can always install the rom through side load. Some one correct me if I'm wrong with that because I'm not very experienced with that but I'll look around for a thread for it.
However I use a method I feel is very simple, but you just need a otg usb adapter. Put your custom rom zip on a flash drive and plug it in the otg before booting into recovery. Make sure you have the latest twrp too (2.6.0.0). The n you can install from external SD.
Again though, I think you can install from a side load method or adb.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
ADB Sideload and ADB Push should both work with that recovery. I have issues with my Asus Windows 8 machine, even on the Ubuntu side, but the old faithful wife keeps a Gateway POS around with Windows 7 on it. I've used both commands successfully in Windows 7 every time.
Humbly Sent from my HTC One running Stock+GE UI
ajbanks said:
Hi, i'm new to this forum and i need help to fix my phone. I tried to mod my phone and I end up brinking it (I think) and here is what I did:
1- Unlock my bootloader. Successfully
2-Flash TWRP recovery image. Successfully
3-Rooted with Android_Revolution_HD_Root_and_BusyBox. Successfully
4-Here is where everything started... I tried to flash a rom (Bulletproof-m7-3.2) and everything went wrong and please do not ask what because i do not know :crying:
now I do not have no OS and my internal storage is not working or missing or it being wipe off I do not know. I can access bootloader and TWRP recovery image but i can't install another rom because of the problem with the storage that do not let me copy files into it. Well hopefully somebody could help me with this and here is a picture from the bootloader.
Click to expand...
Click to collapse
Bulletproof-m7-3.2 = kernel, just to clarify.
Sounds like you have to sideload a rom on there
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
erkui said:
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
Click to expand...
Click to collapse
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
backb0ne5p1d0r said:
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
Click to expand...
Click to collapse
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Even if you don't have an OS installed ADB should work while in recovery.
Well I'm glad you could solve your problems. I knew about the toolkit but trying the harder way is always better for gaining more knowledge.
Sent from my One X+ using XDA Premium 4 mobile app
Stable ROM for HTC One XL Telus Version
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Sujitkundar999 said:
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Click to expand...
Click to collapse
you probably forgot to flash the boot.img (the kernel). That's probably why it's not booting
Just reboot into bootloader (fastboot mode) connect it to your computer and use "fastboot flash boot boot.img" then fastboot erase cache then fastboot reboot
This should get it working
Please press the thanks button if I helped
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for reply.
I have already tried that option.:crying:
erkui said:
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Click to expand...
Click to collapse
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Sujitkundar999 said:
Thanks for reply.
I have already tried that option.:crying:
Click to expand...
Click to collapse
Then flash another kernel. Other than the one that comes with the ROM. Flash a kernel compatible with viperx and it might work.
Cuz when i installed ViperX+ on my phone the kernel that came with the ROM didn't work so i used elite kernel instead. I honestly don't knkw if there's Elite kernel for your phone.. Just flash any other kernel compatible
Sent from my HTC One X+ using XDA Premium 4 mobile app
AndroHero said:
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
if your trying to flash a 4.2.2 X+ sense 5 rom it is recomended that you be at hboot 1.40 im not 100% sure of the compatibility with 1.32 but any of the custom roms should flash fine without regard to the newest hboot
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas
Hi there!
I tried to flash my Moto G back to the stock ROM it came with after rooting it (I was having issues with the flash and wanted it back to normal), but accidently flashed a different model's ROM, which meant that I couldn't get any mobile signal.
I've tried going into the Bootloader and using adb to reflash, however, the phone is only recognised as a device when it is turned on normally, and is not detected when the phone is in Boodloader. As is stands:
Windows
Tried pretty much every variant of Device Management/manually installing drivers
Ran under administrator
Linux
Set up udev etc. and checked meticulously, since the phone is detected as USB connected
Ran with sudo
Is there anything I can do?
(Yes, I have all the drivers installed and phone is in USB debugging etc, only stopped working when I flashed the wrong ROM :/)
Adb will work in os and recovery only, in bootloader use must use fastboot.
If Motorola has distributed a stock ROM that can be flashed through bootloader than that is the way
If they have distributed a stock ROM to be flashed in recovery than that is the way
If you have a custom recovery than life is easy and just wipe clean and flash custom ROM of choice there
See your device specific thread for more detail
Best of luck!
That has sorted it. I feel like an idiot - thanks a lot man ^^
Hello folks,
I tried following a root/flash tutorial online. This was my first experience. I have a Samsung Galaxy S5 SM-G900w (canadian version). I was running Marshmallow stock.
Rooted phone using Odin.
The tutorial called for recovery using Philz recovery, but it seemed it was outdated or updated, so I tried using Cyanogenmode Recovery.
After rebooting, I used what I believed to be close enough to the next step: Wipe data and erase everything option.
After that, I did not have a 'install from sd card' sort of option and ended up with a reboot of the phone.
At this point, I have option for ODIN or recovery mode. I can point to the SD card or adb.
Each time I try to point to a ROM using SD card option it fails to validate the signature and I cannot complete it. I have tried using different ROMs to no avail.
When I power on the phone normally I get the Samsung Galaxy S5 screen powered by Android with the following in top-left corner of the screen, yellow font.
"Set Waranty Bit: kernel"
By all means I am a newb here.
Would anybody mind lending a hand to get me headed in the right direction? Would like to try using a Cyanogen mod 13 ROM to start.
Kind Regards,
Lonely without a phone
side note: It would be nice to know what I may have done wrong and where to go from here.
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Update
es0tericcha0s said:
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Click to expand...
Click to collapse
Hey es0tericcha0s,
Thanks so much for your help. I focused on switching up the recovery img. I used TWRP and it was SOOOOOO much better/easier, so thank you.
After that, the roms were able to show up and be applied and everything was smooth.
You da man.
You're welcome. I love TWRP. ?