Related
I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.
update your adb / sdk.
bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.
Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Why cant people wait..
lol
Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there
I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.
Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.
Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app
Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img
so i tried to flash twrp 2.5 instead of cwm, first through goo manager, and that didnt work. it said that the recovery was installed, but i booted into recovery and it was still cwm. then i tried it with fastboot, that didnt work either. any way to get around this? i even tried to erase revovery but that didnt work either. i checked if fastboot was working by doing the ./adb devices, and it said it was working, so idk what to do now.
thanks
NuckFuggets said:
so i tried to flash twrp 2.5 instead of cwm, first through goo manager, and that didnt work. it said that the recovery was installed, but i booted into recovery and it was still cwm. then i tried it with fastboot, that didnt work either. any way to get around this? i even tried to erase revovery but that didnt work either. i checked if fastboot was working by doing the ./adb devices, and it said it was working, so idk what to do now.
thanks
Click to expand...
Click to collapse
fastboot and adb arent the same. in fastboot its.. fastboot devices. if you did a adb devices, and it saw you, then you were using adb.
simms22 said:
fastboot and adb arent the same. in fastboot its.. fastboot devices. if you did a adb devices, and it saw you, then you were using adb.
Click to expand...
Click to collapse
oh, so what should i do for installing twrp through fastboot? i navigated to the folder i made with adb and fastboot in it, i downloaded the img for twrp, now what?
NuckFuggets said:
oh, so what should i do for installing twrp through fastboot? i navigated to the folder i made with adb and fastboot in it, i downloaded the img for twrp, now what?
Click to expand...
Click to collapse
start fastboot. then open a command window there, be sure that youre connected via usb and in the bootloader of your phone, type fastboot devices, check if you are visible, if you are type.. fastboot flash recovery recoveryname.img
if you want to delete the recovery, use the fastboot delete recovery command.
simms22 said:
start fastboot. then open a command window there, be sure that youre connected via usb and in the bootloader of your phone, type fastboot devices, check if you are visible, if you are type.. fastboot flash recovery recoveryname.img
if you want to delete the recovery, use the fastboot delete recovery command.
Click to expand...
Click to collapse
what do you mean by "start fastboot. then open a command window there"? how do i start fastboot and open a command window there? dont i just have to open a command window and navigate to the folder with adb and fastboot and the recovery img?
NuckFuggets said:
what do you mean by "start fastboot. then open a command window there"? how do i start fastboot and open a command window there? dont i just have to open a command window and navigate to the folder with adb and fastboot and the recovery img?
Click to expand...
Click to collapse
on my windows machine.. open the folder with adb and fastboot, double tap fastboot to start the executable, then press the shift/right mouse button at the same time to bring up the menu with the command window option
simms22 said:
on my windows machine.. open the folder with adb and fastboot, double tap fastboot to start the executable, then press the shift/right mouse button at the same time to bring up the menu with the command window option
Click to expand...
Click to collapse
omg.. my problem with it was that the privacy settings didnt allow installations from unidentified developers so it didnt open lol. fixed it now though, is this it?
looks like it is, but ive never seen it on a mac.
simms22 said:
looks like it is, but ive never seen it on a mac.
Click to expand...
Click to collapse
yay finally worked just a few questions, would i be able to restore my stock rom backup i made with cwm through twrp? if not, how do i restore stock rom at a later time if need be?
NuckFuggets said:
yay finally worked just a few questions, would i be able to restore my stock rom backup i made with cwm through twrp? if not, how do i restore stock rom at a later time if need be?
Click to expand...
Click to collapse
woot!
did it actually flash this time?!?
no, you wont be able to restore it via twrp. you can flash the stock factory img and become completely stock through fastboot. its 3 or four words only, and the files of course. but if you would want to restore your cwm backup, probably installing cwm recovery would do the trick.
simms22 said:
woot!
did it actually flash this time?!?
no, you wont be able to restore it via twrp. you can flash the stock factory img and become completely stock through fastboot. its 3 or four words only, and the files of course. but if you would want to restore your cwm backup, probably installing cwm recovery would do the trick.
Click to expand...
Click to collapse
yeah it did!
and oh :/ alright il figure out which path i wanna take with restoring stock if i ever need to at a later time
thanks again for all your help
anytime
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
NuckFuggets said:
yeah it did!
and oh :/ alright il figure out which path i wanna take with restoring stock if i ever need to at a later time
thanks again for all your help
Click to expand...
Click to collapse
oh, btw, some extra credit points https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!
Hi, I'm new to this phone. Just got it 1 week ago. I tried to find any related information on the bootloader unlock and custom recovery, but it is very limited. I think maybe this phone is not well known. I would appreciate if someone can provide me the way to unlock bootloader, flash TWRP and roots. I can't live without magisk and viper4android. Thanks.
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
thanks
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi, I've tried numerous timed and it always won't pick up the command of unlocking bootloader. It always stay in the fastboot menu. I've toggled the 'OEM Unlock' function in the developer setting, as well as the USB debugging. Any idea why the device won't pick up that command?
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
dantonuci said:
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
Click to expand...
Click to collapse
Nope. It doesn't respond to the command in the fastboot. It just shows the fastboot menu. My adb is written 'waiting for device.... '.
Drivers , uninstall all other drivers and try please
dantonuci said:
Drivers , uninstall all other drivers and try please
Click to expand...
Click to collapse
Okay will try again
storytellerz said:
Okay will try again
Click to expand...
Click to collapse
I am also finding this message, what is its solution ???
the same recovery
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi there, when I flashed the recovery that is always the stock recovery, why?
vins84 said:
Hi there, when I flashed the recovery that is always the stock recovery, why?
Click to expand...
Click to collapse
Not sure what you're asking, did you want to flash TWRP or stock? I was just giving tutorial for how to install TWRP
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
bmaz121 said:
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
Click to expand...
Click to collapse
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
dantonuci said:
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
Click to expand...
Click to collapse
I don't understand? Appears not locked? It is locked. Now I remember when I flashed my Star N997 the developer said that there is a unlock bit that has to be turned on in the process of unlocking. I think this may be the case here since it unlocks until a reboot. I am deep concerned that after a unlock count of 3 the phone will not boot anymore. Do you know anything about these things? Another thought is does the USB C need different drivers and should it be plugged into a USB 3.0 outlet?
TWRP will flash only when it's unlocked so even if it's saying it's locked go by what you can do with TWRP
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
I did it several times and never had a problem
i was looking for camera.apk file from Nubia Z17S phone from Stock ROM, can anyone upload it here..it should be located in system / app or app-pvt folder, you can copy using Root Explorer tool.
pls. let me know...
I'm having problems unlocking the bootloader. Has anyone got the proper TWRP for this phone? I can't find it. The one I have says FAILED (remote: Requested download size is more than max allowed). Thanks
hello links no longer works. Someone could give me back the TWRP and minimalb fastboot adb
For anyone's information, TWRP will not boot in recovery while the phone is being charged. Unplug first. You will just get a black screen.
i am also experiencing the same issue.. where can i find the drivers for this phone nx595j? or how do i uninstall the drivers for it?
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
yo can somebody help me install a custom rom on my z17s via team viewer?? im willing to pay for your time
I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....
BlackHawk580 said:
I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....
Click to expand...
Click to collapse
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone
_NikO_ said:
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone
Click to expand...
Click to collapse
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check
_NikO_ said:
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check
Click to expand...
Click to collapse
Yes, I've done that too, I've tried installing various different drivers as well, it also has Windows 10 as well
BlackHawk580 said:
Yes, I've done that too, I've tried installing various different drivers as well
Click to expand...
Click to collapse
So your phone is showing up in Adb devuces without any yellow warning or anything?
_NikO_ said:
So your phone is showing up in Adb devuces without any yellow warning or anything?
Click to expand...
Click to collapse
It doesn't show up at all on the list, yeah
BlackHawk580 said:
I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all.
Click to expand...
Click to collapse
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?
BlackHawk580 said:
It doesn't show up at all on the list, yeah
Click to expand...
Click to collapse
If there isnt your computer isnt actually seeing it as an adb device
osd_daedalus said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?
Click to expand...
Click to collapse
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume up and power doesn't enter the recovery either.
BlackHawk580 said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume down and power doesn't enter the recovery either.
Click to expand...
Click to collapse
I'm not sure you can reboot to recovery from fastboot.
Some people tell you can launch "fastboot reboot recovery" but it is not a standard command and does not work for me.
In fastboot you can boot the recovery image file with
Code:
fastboot boot recovery.img
Change recovery.img with your recovery file.
Keeping it simply, can you reboot normally and reboot to recovery via adb? With "adb reboot recovery"
Fastboot is the way to flash anything
Your phone don't have to get recognized by adb, it's more for sideload or apk installation. To flash recovery, you need fastboot.
Try fastboot flash recovery recovery.img (recovery.img should be in the same folder as fastboot.exe)
Is there any news? I have a similar problem:
I boot in fastboot mode and I run `fastboot oem device-info` to check status:
Code:
$ fastboot oem device-info [15:20:59]
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
And it seems ok.
Now I try
Code:
$ fastboot flash recovery recovery.img
and it stuck there and it don't do anything.
I tried different PCs and different cables, nothing make it works!
Normally it only lasts some seconds...
What should I try?
Thanks in advance