I installed R3 rom but my wifi cant be turned on. Latest I found that also my USB internet passthrough is not working. I got hint from one member but I absolutely dont know how to perform this.
flash the boot.img inside the R3's zip file using fastboot.
Commands:
fastboot erase cache
fastboot flash boot boot.img
How to flash something inside zip file? do I have to extract it and put it into root?
How to execute commands at all? Where to put them? What do I need to perform? I am total noob and every simple step I ever done took me a day. Now I am stuck. IF someone knows how to make this, please help.
Thank you.
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
nlooooo said:
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
Click to expand...
Click to collapse
I should have ADB, because I was rooting my phone month ago and ADB was required. How do I find out? I have SDK tools and i have adb.exe, adbwinapi.dll, fastboot.exe, recovery.img in C\Android. Actually I was trying to connect phone through USB and start adb.exe but it just popped out, scrolled down fast and closed (it was looking like command prompt- black window).
And I unpacked boot.img from R3.zip to my sdcard
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
janickonajkrajsi said:
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
Click to expand...
Click to collapse
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
I'm just wandering how did you manage to unlock bootloader at all.
MaartenXDA said:
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
Click to expand...
Click to collapse
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Isnt there a way to perform this "boot.img flashing" through recovery mod? I mean without the usb connection and without the cmd black hole
janickonajkrajsi said:
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Click to expand...
Click to collapse
First use the command "cd C:\Android"
After that do the commands again.
Be sure you've uninstalled HTC Sync (NOT the drivers) before doing this.
Sent from my awesome fridge
nlooooo said:
I'm just wandering how did you manage to unlock bootloader at all.
Click to expand...
Click to collapse
He didn't get your point...
Sent from my toaster using TapaToast HD
Thank you guys, now it is working.
Quote:
Originally Posted by nlooooo View Post
I'm just wandering how did you manage to unlock bootloader at all.
He didn't get your point...
Yeah it was meant like "hod did this stupid noob even managed to unlock bootloader at all. I got his point, and the right answer was "step by step guide" so actually You didnt got my point.
Dont forget that things that are automatic and obvious to you, are not obvious to everyone. My grandma is learning to work with computers and when she asks me how to send an email, I have to tell her "grab a mouse, then move it there........"
)))))))
Does not matter, thank you guys!
Once you learn to use adb and fastboot it's always the same, so my point was that you've never learned how to use it, you just typed what you saw, without any wish to learn.
Point is to try and learn, not to ask again.
Nobody said you're stupid, just lazy.
Cant get the R3 working. HTC Sense UI crashed error at lock screen
I flashed the sense revolution r3 today but could not get it working.
The following are the issues faced.
1) It starts without installing the mods package, but lacks the full sense widgets like htccontacts, htc calender etc.
2) when i flashed the r3 mod package, it gets stuck at the lock screen. The Sense UI crashes.
3) Without the mods, i faced another bug in people widget. it crashes when i click the phone dialer from it.
I am currently on sense r3.
Please help me install it in full.
Related
I have bricked or atleast semi bricked my Folio and i dont know if it can be fixed. It began with damaged internal sd, so i try the format zip but no luck. May device have been like this 3 days now. I NEED HELP, AND YES I HAVE ASKED IN GENERAL SECTION. but i didnt get an answer for days. I need help by someone who can tell me how to set up fastboot. My folio boots i can get to clockwork recovery and i can get in to fastboot mode. I have working ADB on my computer. The install fails when recovery is writing boot.img iget this message: assert failed
write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
It installs system.img fine. So i was thinking i could fastboot boot.img to the device and maybe it boots. So i put Folio in Fastboot mode,insert usb, and update driver, go to command prompt and write fastboot devices all i get is:
? fastboot
Is there anything special i have to keep in mind to setup fastboot for Folio. I used the fastboot that came with SDK. Do i have to add something more to .inf file for fastboot? Do have to use any special fastboot just for Tegra2 devices? Is my fastboot mode damaged? Please i need help i have waited for days in general section not one answer. Hoping on better luck here in the dev section
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
mblaster said:
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
Click to expand...
Click to collapse
I had entered the part to .inf file but havent done the echo part in command prompt, will try now. Its weird as hell all i get when writing fastboot devices is a ? fastboot. Its a windows Vista 32 im using and SDK 08. And when i enter this echo 0x955 i just get that its the wrong path.
I got fastboot working didnt know it could be ? fastboot when it was connected. I kept getting it so i tryed to send some commands and it got thru. **** so i have had it working for days. I have flashed the boot.img via fastboot and am now trying to do an advanced restore of a nandroid. Will see how it goes. If its not working can i flash system.img and boot.img? Will that work? Well atleast now i can flash standard recovery and send it to toshiba
Probleem Solved Thank you mblaster, you wrote it could look like this when writing fastboot devices: ?????? or atleast something like it so i thought maybe i am connected as my said: ? fastboot . So i tryed some commands and they got thru. So to anyone who tryes to install fastboot try commands. I was waiting for days(dumb, i know). So now im back and kickin, watch out
Moved to proper forum
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
I've already unlocked the bootloader and am about to flash cwd but my computer won't recognize the phone in the bootloader while plugged into USB. So when I try to enter the command "fastboot flash recovery <recovery.img>", the command prompt comes back with an error. I bet I'm missing something simple here, but it's getting pretty frustrating.
I have the HTC drivers installed and I'm using bootcamp, if that matters.
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
jonesin said:
Are you positive that you are in fastboot mode. Does it say fastboot USB on your phones screen in red? Uninstall the HTC sync drivers its like a 150mb package. All you need is the regular HTC android drivers. As far as bootcamp I'm unfamiliar with it so can't really say but the good old original ways are always reliable. If bootcamp is some sort of interface for fastboot and adb then I reccomend you read up a little on how to operate the two and simply do things the way they were originally implemented. It will benefit you in the long run. If I'm way off then sorry just trying to cover all the bases.
Good luck!
Click to expand...
Click to collapse
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
feperlman51 said:
Haha i meant bootcamp for the mac. Allows you to run windows. I highly doubt this has anything to do with it, just thought I might throw it out there. I deleted the HTC sync drivers and the phone is still not recognized in the bootloader. It is recognized when the phone is on the homescreen, though.
My phone says "FASTBOOT USB" highlighted in red. The way I know it's not connected is entering "adb devices" into the command prompt and the response comes up as "List of devices attached" and doesn't display the serial number like it does when the phone is on the homescreen.
Click to expand...
Click to collapse
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
jonesin said:
Thats because adb is not functional during fastboot mode so it shouldnt be showing up. Try fastboot flash recovery recovery.img again it should run this time.
also try another usb port but it sounds like everything is set up correctly as long as you have fastboot in your platform tools folder and the device is in fastboot mode which it seams to be you should be good to go.
Click to expand...
Click to collapse
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
feperlman51 said:
I got it this time! Didn't change anything, really, just ran the "fastboot flash recovery" command again. FWIW, twrp worked but cwd didn't. I had tried both initially, but twrp worked this time. I would bet that it was all human error. From what others have said this isn't actually an issue.
Either way, thanks for replying and trying to help!
Click to expand...
Click to collapse
"just ran the "fastboot flash recovery" command again"
Lol thats what I said man! Glad it worked! CWM and TWRP should both work, I bet a nickel to a dime you werent actually in fastboot mode the first time! anyway happy flashing! Get comfortable with ADB and Fastboot because they will be our primary utilities for the foreseeable future!
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD