Related
Guys, i have a slight problem here. I want to install a custom rom on my dell streak. The guide that i am following is from Benny's blog (http://leemn.wordpress.com/2011/02/...from-eclair-2-1-build-6941-to-stephens-1-5-1/)
What I've done:
1. Installed Android SDK (Updated the given updates, as in the screenshot. SCREENSHOT
2. Installed Dell's Windows Drivers from here (ftp://ftp.dell.com/Handheld/R288920.exe)
3. Installed Dell Mobile Sync
4. Downloaded the Fastboot tool from here (http://download143.mediafire.com/pcxqstv8scfg/yd21znuyj14/1.8.1.7-streak-clockworkrecovery.zip) , Renamed the fastboot-windows.exe to fastboot.exe .
5. Downloaded SteakDroid 1.9.0 and renamed it to Update.zip and copied it to the root of my SD card.
6. Downloaded the current version of the baseband as recomended.
7. Made a folder in C drive named Streak and extracted the clockworkrecovery.zip there. Copied the baseband into the same folder as well.
I believe these steps were all correct.
Now however, i am stuck .
8. After my streak is in the FASTBOOT_MODE , waiting for the usb connection, i connected the USB cable to my computer.
9. It said that a new device Android 1.0 has been found.
10. I choose to choose the drivers by my own, and The only drivers that were available is Android ADB interface and Android Composite ADB interface. If i were to click show compatible hardware, then only the Android ADB interface driver would be shown. SCREENSHOT
11. If i were to choose any 2, the drivers would install fine, and FASTBOOT_MODE would show up in my streak.
12. I entered into the commandline (run > cmd) and went to the C:\streak directory. Once i ran the command, fastboot devices, nothing is listed. When i ran the command fastboot reboot, all it says is waiting for device and that is it. SCREENSHOT
I tried this on a second computer, and its the same thing. I believe i should see the "ANDROID BOOTLOADER INTERFACE" driver, to proceed with the flashing. SCREENSHOT
However, i am not seeing such options on both computers, that are running Windows XP SP3.
What should i do?
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
asianftw said:
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
Click to expand...
Click to collapse
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Switch off the phone
Boot the phone into recovery mode by holding vol up + vol down + power simultaneously
You will see a black screen with white writing (vol buttons are up/down, camera button is enter/ok)
Select* ”Software upgrade via Update.pkg on SD Card”
You will now be on a black screen with green writing
Select* ”apply sdcard:update.zip”
Scroll* down to “Yes – Install /sdcard/update.zip)
This will load and install the update
Click to expand...
Click to collapse
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
1 - u need to install CWM via fastboot
2 - press on 2nd option will bring u to another new menu ...... if it start to install from update , means u failed ..... After installing CWM , DO NOT reboot into your ori 2.2 or else the CWM will get replaced by original recovery . Which means once u install the CWM , key in " -fastboot -0x413c reboot " and hold the 2 volume button while it reboot ..... it will take u to recovery straight after restart
3 - Choose option ( 2 ) which u bring to u to CWM
4 - Select Steven's zip file from there ....option 4 i think , cant remember correctly which is " install zip from sdcard "
Click to expand...
Click to collapse
arvin2212 said:
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
Click to expand...
Click to collapse
Glad to hear Clockworkmod works for you!
Clockwork mod working
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
cdzo72 said:
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
Click to expand...
Click to collapse
Did you do a full factory reset?
Did you use the clear cache / dalvik cache option from the cwm menu?
I have done all those and have not had any random reboots.
**Just so you know, i've never experienced any random reboots with the streak.
Random reboots
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
cdzo72 said:
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
Click to expand...
Click to collapse
I believe i've read somewhere that the older versions of the streakdroid roms <1.9.1 has the sensors disabled for rebooting once the cover is loose. Try that
used Flash Image GUI to flash Viper rom and when it boot into boot loader my custom TWRP Recovery is gone. so now im stuck in HBOOT screen..so i tried to ADB CMD and it says (no device detected) tried multi times and nothing.. is my 3D bricked or is there something that im over looking during this frustration..thanks for any help.
im Hboot 1.5
and did a search and nothing with this situation
Your phone would be brick if it doesnt turn on . Try to do a backup
Sent from my PG86100 using XDA Premium App
First flashing again recovery.
Sent from my PG86100 using XDA Premium App
Efrencalvario said:
First flashing again recovery.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
i tried to fastboot useing ADB cmd but i cant get it to recognize the phone, it keeps saying device not detect or found... thats what got me going crazy
if i could get it to recognize the phone i was thinking of trying to reflas recovery
bricked phone?
If you can still get your phone to boot up into HBOOT then your device is not bricked to say the least. The next thing I would try is to remove all the drivers on your, WIN/MAC/LINUX?? computer and reload those to see if the device can be noticed again through your computer. ALL HOPE IS NOT LOST, hang in there!
malignant098 said:
If you can still get your phone to boot up into HBOOT then your device is not bricked to say the least. The next thing I would try is to remove all the drivers on your, WIN/MAC/LINUX?? computer and reload those to see if the device can be noticed again through your computer. ALL HOPE IS NOT LOST, hang in there!
Click to expand...
Click to collapse
i uninstalled SDK and HTC Drivers restarted comp then installed HTC Drivers and SDK Tool and restarted comp then i opened up CMD Window and tried again and same thing.. (device not found) windows detects the phone when in Fastboot usb mode b/c windows make that sound when connecting a device..
im trying to keep faith..this is what the CMD window says
C:\Android new\android-sdk\platform-tools>adb push recovery.img /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
If worst comes to worse you may need to wipe and relock use the a RUU exe 2.17 If your CDMA..
Then make sure debug is on and unlock and flash a recovery fasboot boot recovery.img and wipe and flash rom...
Debug isn't on that is why ADB isn't finding your phone man..
ok i got it going..lol.. what a relief i did these 2 steps from a diff thread and it worked once it booted the recovery i knew what to do from that point
6. Open the command prompt on your PC (press START and type cmd) In the command window, type: \cd\rootevo3dnew to get to C:\rootevo3dnew).
7. Type the following command in the command prompt: fastboot boot cwm-4.0.1.4-shooter.img and press enter.
just wanted to thank everyone for their help
now i can call Sprint and cancel my replacement
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.
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
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "