[Q] ZTE Flash help (N9500) - Android Q&A, Help & Troubleshooting

I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls

Really no one can help???

bamp

cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk

If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:

CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up

Related

Phone stuck on boot screen

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

trying to adb sideload on a mac

After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
allhailcardiel said:
Hopefully this thread can be moved then.
Yes, I have the phone in recovery when searching.
that is really all I can do with the phone currently is boot to recovery.
Click to expand...
Click to collapse
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
xcrazydx said:
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
allhailcardiel said:
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
Click to expand...
Click to collapse
I doubt you will ever wipe your internals again after this experience, but its always good to have an OTG cable that you can buy online for like $3.. You can install from usb flash using this cable in twrp recovery like its an external sd card. Its also useful for other simple transfer type of work.
Thread has been moved to Q&A. :good:
Help me
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Hey man, I am on the same boat right now. Can you please tell me the exact steps you took to recover?
I am fairly new at this and kinda freaking out.
Thanks.
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
lankyboy29 said:
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
Click to expand...
Click to collapse
Just the sdk. At least for me it worked ok
Danvid113 said:
Just the sdk. At least for me it worked ok
Click to expand...
Click to collapse
PHP:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
Do you know what mount does? because only data and cache were selected. do i need system checked as well?
lankyboy29 said:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
Click to expand...
Click to collapse
ok, so what should happen is that your computer shows that it is transferred. After it is done, your phone should install the program. Sometimes it doesn't show anything for me. These times i just wait until something happens, if still nothing either hit cancel or back. It worked for me every time; if you still have problems, you should upload a video of the whole procedure, so I can have some idea of what is going wrong (send a youtube link in pm)
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
Thank you so much for this ,,i tried everything with no success. This worked for me.You are the best. Im bookmarking this so if it happens again. Bang I know where to look.
I'm also using Mac (10.9.x) and had the same problem - accidentally wiped my HTC One sdcard and had no ROM, nothing and sideload didn't work (when I give the adb sideload command in terminal, it exits within a few secs and nothing changes on the phone).
The quickest solution for me was to just stay in TWRP with USB connected and....
1) Manually copy the ROM binary in terminal ie. :
adb push <path_to_ROM> /sdcard/
2) After above completes, in TWRP, just select "Install zip from sdcard" and select the file copied above from /sdcard/
Your description worked for me. Thanks you!
But I also had issues with adb . If anyone ever looking for a solution go to stackoverflow and search "Installing ADB on MAC OS X"
and then apply Danvid113s solution.
xcrazydx said:
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Im on the same boat. what did you do exactly?

[Q] my HTC fails to switch on... How to install a new rom?

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

Steps of unlocking BL(Explain or video tutorial please)

Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
You need to have USB debugging enabled on your phone, adb installed on your computer and the LG drivers installed. If you have all that the steps to unlock are quite clear.
Also your phone needs to be on and you need to keep an eye on it as you will have to enable a couple of things when they pop up on your phone, one is to allow your computer to see your phone in debugging mode and the other is to Grant super user permission.
batsup606 said:
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
Click to expand...
Click to collapse
You need to be able to get the phone operating in Ethernet mode; otherwise the computer cannot pass it commands. Alternatively, you can use a terminal emulator ON your phone itself. That's what I did as I didn't want to boot my desktop rig up before I left. It works exactly the same, except you don't type "adb shell", just open the term emu and start with the SU line.
It works fine if you do it from a terminal emulator on ur phone just fyi
laxattack said:
It works fine if you do it from a terminal emulator on ur phone just fyi
Click to expand...
Click to collapse
Can confirm. This is the way I did it since I don't have access to a computer until later tonight. Just type the exact commands (except for adb shell) in a terminal emulator and you are done.
I can also confirm this is working.
I had to download the LG updater or whatever (when you first plug the phone in; says installer) despite Win7 saying it had autoinstalled the drivers then ADB could see the device when in ethernet mode.
Also the last command didn't work (guess I didn't have the TWRP in the right place) and was forced to do a battery pull after the Factory Reset (didn't erase my data or settings), booted fine and then I just flashed the recovery with Flashify (and now can get into recovery) but YMMV.
FLASHIFY
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
airintak25 said:
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
Click to expand...
Click to collapse
+1

Stuck in bootloader/fastboot and can't get ADB to recognize, but fastboot does..

So I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.

Categories

Resources