Related
Guys i rooted the build GRH78C so i know how to root
i put the new build GRI40 that removes the root access by restoring it from rom manager.
but i was so stupid thinking that superboot for the build GRH78C can also root the new build GRI40. I did then it rebooted but stuck on google logo.
is there any solution?
if i tried the superboot for the new build when it comes out will it work?
does that mean my nexus s will not work forever?
please help
boot into recovery mode
then load another ROM
as a last resort you can use the Odin method, if you are unable to use fastboot methods
after flashing GRI40 by restoring from rom manager i got stuck 2.3.3 unrooted!
if i boot into recovery mode it only recognizes update.zip and passing.zip
i thought of moving update.zip into the internal memory so recovery can recognize it but i cant the phone doesn't have a sd card.
please help
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
SWEETTOOTH said:
after flashing GRI40 by restoring from rom manager i got stuck 2.3.3 unrooted!
if i boot into recovery mode it only recognizes update.zip and passing.zip
i thought of moving update.zip into the internal memory so recovery can recognize it but i cant the phone doesn't have a sd card.
please help
Click to expand...
Click to collapse
qwerp_ said:
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
Click to expand...
Click to collapse
Alternatively you can do the following:
1) Download the newest version of CWM from here (Google Nexus S, near the bottom of the list)
2) Boot your phone to the bootloader
3) Type
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
4) Go to mounts and storage and mount USB storage
5) Download a different ROM like CM and place it on the root of your SDcard
6) Flash it
7) Golden!
kenvan19 said:
Alternatively you can do the following:
1) Download the newest version of CWM from here (Google Nexus S, near the bottom of the list)
2) Boot your phone to the bootloader
3) Type
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
4) Go to mounts and storage and mount USB storage
5) Download a different ROM like CM and place it on the root of your SDcard
6) Flash it
7) Golden!
Click to expand...
Click to collapse
thanks i tried it but it says Permission denied
what i do
first i write cd the drag the tool floder to the terminal
hit enter
drag the recovery image into terminal (space) then paste fastboot boot recovery-clockwork-3.0.0.5-crespo.img
hit enter
it says
Permission denied
by the way
i have above only fastboot mode . there is no fastboot mode usb
in the bottom standard_set_configuration
does the fastboot sees my device?
is that right?
qwerp_ said:
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
Click to expand...
Click to collapse
please do you have the file of the original boot.img?
then how to push update.zip with terminal?
Odin is GOD..
SWEETTOOTH said:
Guys i rooted the build GRH78C so i know how to root
i put the new build GRI40 that removes the root access by restoring it from rom manager.
but i was so stupid thinking that superboot for the build GRH78C can also root the new build GRI40. I did then it rebooted but stuck on google logo.
is there any solution?
if i tried the superboot for the new build when it comes out will it work?
does that mean my nexus s will not work forever?
please help
Click to expand...
Click to collapse
Hi SWEETTOOTH, if your still stuck on the Google screen can I suggest Odin as a way forward (http://forum.xda-developers.com/showthread.php?t=947950) , it wll flash you back to stock 2.3.1, but it will you keep the latest baseband that ships with 2.3.3 (I9020XXKB1). I have used it twice with no problems.
You can then re root and proceed down another path?
guys please help i bought it last week now it doesnt work at all.
how to push update.zip with adb?
how to solve Permission denied problem?
help
SWEETTOOTH said:
thanks i tried it but it says Permission denied
what i do
first i write cd the drag the tool floder to the terminal
hit enter
drag the recovery image into terminal (space) then paste fastboot boot recovery-clockwork-3.0.0.5-crespo.img
hit enter
it says
Permission denied
by the way
i have above only fastboot mode . there is no fastboot mode usb
in the bottom standard_set_configuration
does the fastboot sees my device?
is that right?
Click to expand...
Click to collapse
Okay, if you want to test to see if fastboot sees your device do this:
Code:
fastboot devices
If you get an output on that, it sees your phone. Now assuming that works and assuming I understand what is happening to you correctly do exactly as I say:
1) Download and unzip this file and place on your desktop and place the recovery image into that folder.
2) Boot your phone into the bootloader
3) Type or copy the following into your terminal exactly
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
that *should* work to get you into the custom recovery. From there do this:
1) Go to mounts and storage and chose mount USB storage.
2) Go to this thread and download either of them (one of them is rooted one of them is not. If you want to be rooted, download the rooted one if not download the unrooted).
3) Unzip the file to the root of your SDcard (it should be a folder called clockworkmod).
4) Eject the drive from your computer and select unmount on your phone.
5) Go to backup and restore and select restore and select the one named GRI40-2.3.3 or something like that (can't remember exactly what its named).
6) Reboot your phone. Follow the other instructions about how to prevent the stock recovery from overwriting CWM and how to flash CWM etc.
Did it work?
it says
/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
cannot load 'recovery-clockwork-3.0.0.5-crespo.img'
i feel like giving up all i need is to install the recovery but there's something wrong
fastboot cant see my device
Did you install the Android ask and the Nexis s drivers?
Sent from my MattedBlues CM7 Google Nexus S!
yes i have the sdk , and i have mac do i need drivers to install?
SWEETTOOTH said:
yes i have the sdk , and i have mac do i need drivers to install?
Click to expand...
Click to collapse
No, no need to install drivers on a mac...Man I'm baffled...I'll send distortedloop a PM and ask him to check this out because I'm out of ideas...sorry man!
Thanks man for all the initiatives
SWEETTOOTH said:
Thanks man for all the initiatives
Click to expand...
Click to collapse
Its no problem man, everyone should be able to use their phones however they like and rooting isn't easy. Sometimes people need a little help I know I did at first! hehe
Sweet, I have one last idea actually... try this:
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.
Sweettooth, is your bootloader unlocked? Do you gave the unlocked padlock icon on the bottom of the screen when you first turn on phone and have Google logo?
If your bootloader got updated to gri40 you can't fastboot boot or fastboot flash if youre locked.
Try the fastboot oem unlock command from Mac Terminal, you can always say no to the warning that pops up if you dont want to go further. Be aware that oem unlock will wipe all data off the phone including sdcard photos and stuff.
SWEETTOOTH said:
fastboot cant see my device
Click to expand...
Click to collapse
Sorry if you answered this already, but when you type in fastboot devices on the Mac Terminal what is the response you get?
Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help
Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.
Make sure you post things like this in the Q&A section ull get better help over there then in this General section
Xavier102296 said:
Make sure you post things like this in the Q&A section ull get better help over there then in this General section
Click to expand...
Click to collapse
Thanks
You just need to flash a ROM.
Ammar115 said:
Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.
Click to expand...
Click to collapse
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.
phanitej said:
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.
Click to expand...
Click to collapse
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.
Ammar115 said:
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.
Click to expand...
Click to collapse
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.
phanitej said:
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.
Click to expand...
Click to collapse
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.
Ammar115 said:
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.
Click to expand...
Click to collapse
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
This is what I get using minimal adb and fastboot. What does it mean?
phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
I've followed all the instructions but my phone still not rebooting. When I try to reboot it, it only show me the warning of unlocked bootloader screen, black screen, warning of unlocked bootloader screen then dead android screen. What should I do now?
It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.
Few weeks back I ****ed up soft bricked my phone had kindda same issue when I switch my phone on I get a dead android logo. Gave to the service center in India and got a replacement a new xt1033
P.s I was trying to root and my warranty was void still got a new one try your luck bruhhh
Sent from my XT1033 using XDA Free mobile app
SbM_ said:
It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.
Click to expand...
Click to collapse
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.
Ammar115 said:
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.
Click to expand...
Click to collapse
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219
Zerelth said:
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Done but still, the same thing happened.
Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
Your PC will not recognize it as media transfer / storage while you are in bootloader / fastboot mode, its perfectly normal. When you type fastboot devices it should show you a number which means it working as intended. This is an old thread but it shows how to transfer your ROM to sdcard via adb push command. http://forum.xda-developers.com/showthread.php?t=1667929
Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
The output of the "fastboot devices" command clearly shows your phone is recognised by your PC. As I said all you need to do now is use the correct "fastboot flash" commands to restore recovery and system. Tutorials can be found in this forum.
Thank you.
I would like to say thank you to all peoples who help me solving my lost os problem. Thanks for all the informations. My moto G is working perfectly normal right now.
My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
TRiP_E said:
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
Click to expand...
Click to collapse
You can connect to ADB but the adb push command isn't working when you try to move the ROM.zip to the device?
Get a new OTG cable.
The nandroid backup you made should have been done in TWRP and stored on extsdcard instead of the online backup, online backup is crap because it only works in certain conditions, it's useless when the device can't connect to a network.
Sent from my SM-S903VL using Tapatalk
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
TRiP_E said:
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
Click to expand...
Click to collapse
Yeah, new cable seems to be your only option.
Sent from my SM-S903VL using Tapatalk
Alright then, I'm going to go see where I can buy one. Thanks for the confrirmation.
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
TRiP_E said:
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
Click to expand...
Click to collapse
Try rooting the device and then use the Stick Mount app, if your device has the hardware to support OTG, that should enable it, but if your device does not have the hardware to support OTG then it doesn't matter what you do softwarewise or what you modify, it has to have the hardware or it can't do it at all.
Things like this are why I'd never buy or own a ZTE device of any kind. Relatively soeakibg, they are all junk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
TRiP_E said:
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
Click to expand...
Click to collapse
If you can use adb shell or fastboot, you can try getting a copy of system.img from someone with your exact device and dd or fastboot flash the img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
After reading other pols forums, it seems that I didn't have to delete the internal storage........
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
Sideloading a ROM won't work.
Try
adb reboot bootloader
If you can boot to bootloader or fastboot you can try finding the firmware for another device that has all of the exact same hardware components that your device has then try fastboot flashing it or extract the separate .imgs from the firmware and use the fastboot commands to flash the boot.img and system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
can't get into fastboot, ADB command says error: closed, while doing the command in terminal in the TWRP menu keeps me on ZTE screen (only reboot recovery works, not as ADB command but in terminal).
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
help.
equitube said:
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
Click to expand...
Click to collapse
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
filldapipe said:
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
Click to expand...
Click to collapse
Did you ever get the TWRP for this? I have it in my dropbox pm me.
The issue were running into is that the TWRP on this model can't see the ext sd. The backup is 1.5 or 2gb which is usually too large to fit on the internal SD
Slacker is working hard at modding the Fstab file to make TWRP see that storage. Any ideas please let him or I know([email protected] or here )
I'm also working on an EquiMods custom ROM for this. Bare bones battery saver, switchable to performance when needed.
Anyone know if and how these can be overclocked?
I have a deodex rom done for this phone and also should have the working twrp recovery by morning. The cm11.0 ive been working on is almost done. I hope Everytime i flash it to phone i get white screen. Also im going to install xposed on it in the morning. I think i found the fix for that to work
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
edsfunsite said:
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
Click to expand...
Click to collapse
They obviously got something to work since there are members in this thread that have TWRP installed on their devices, that means they can at least root the device but I doubt there are any ROMs for this device.
Sent from my LGL84VL using Tapatalk
I've rooted my N817 but never made an Nandroid backup. I still have TWRP up and working but I've tried to flash the 2 roms I know of....they both "install" but when I try to boot It stays in the ZTE screen...Help!