Hi everybody!
(Sorry for my english )
I up rom cook for HOX+ but failed. It can't boot to room cook. I can boot to recovery, fastboot. All things in sdcard are lost.(backup rom ship). How can I restore my phone? Please.
When I run rom guu RUU_ENRC2B_U_JB_45_Vodafone_UK_1.14.161.13.....exe it failed because my phone is x.17.161.x.
My phone: HBoot: 1.40, version x.17.161.x.
Thanks all!
macarong35 said:
Hi everybody!
(Sorry for my english )
I up rom cook for HOX+ but failed. It can't boot to room cook. I can boot to recovery, fastboot. All things in sdcard are lost.(backup rom ship). How can I restore my phone? Please.
When I run rom guu RUU_ENRC2B_U_JB_45_Vodafone_UK_1.14.161.13.....exe it failed because my phone is x.17.161.x.
My phone: HBoot: 1.40, version x.17.161.x.
Thanks all!
Click to expand...
Click to collapse
Did you install TWRP or are you on stock recovery?
When you enter bootloader, does it show unlocked or locked at top of the screen?
Addicted2xda said:
Did you install TWRP or are you on stock recovery?
When you enter bootloader, does it show unlocked or locked at top of the screen?
Click to expand...
Click to collapse
I installed CWM-base Recovery v6.0.2.7 and bootloader unlocked.
macarong35 said:
I installed CWM-base Recovery v6.0.2.7 and bootloader unlocked.
Click to expand...
Click to collapse
Install TWRP 2.5 and get a ROM sideloaded ...
( adb sideload blahblahblah.zip )
Of course you need to flash the kernel too
AFAIK CWM does not support ADB Sideload and is practically dead.. or at least in hibernation...
Addicted2xda said:
Install TWRP 2.5 and get a ROM sideloaded ...
( adb sideload blahblahblah.zip )
Of course you need to flash the kernel too
AFAIK CWM does not support ADB Sideload and is practically dead.. or at least in hibernation...
Click to expand...
Click to collapse
Could you please detail step by step to sideload zip file. I installed TWRP2.5. I goto recovery and select ABD sideload, them run command on PC but error:
D:\IDE\AndroidSDK\sdk\platform-tools>adb sideload d:\Elegancia_6.1.0.zip
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
D:\IDE\AndroidSDK\sdk\platform-tools>
macarong35 said:
Could you please detail step by step to sideload zip file. I installed TWRP2.5. I goto recovery and select ABD sideload, them run command on PC but error:
D:\IDE\AndroidSDK\sdk\platform-tools>adb sideload d:\Elegancia_6.1.0.zip
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
D:\IDE\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
Try this command a few times...
Copy the rom to same folder as adb tools
rename the ROM file to .. say ROM.zip
The ADB sideload needs some time to detect...
yrgeryi Bosher
Addicted2xda said:
Try this command a few times...
Copy the rom to same folder as adb tools
rename the ROM file to .. say ROM.zip
The ADB sideload needs some time to detect...
Click to expand...
Click to collapse
Hi, I send file successfull. But after my phone don't display anything. Black screen. What must I do next?
Update: uprom success. Thank so much.
Related
Unofficial Clockworkmod Recovery version 6.0.4.4 for the Nexus 5
Current Build Not Booting I Will be Looking into a Solution. Thank you to everyone who has tested these!
Nexus 5 Stock Recovery Image
Downloads
Click to expand...
Click to collapse
Flashing Instructions
1. Download the above file.
2. Move the downloaded recovery file into the directory where you have ADB and Fastboot setup on your computer.
3. Navigate into the directory where you have ADB and Fastboot setup on your computer and run the following commands from the command prompt on your computer:
Code:
adb reboot bootloader
fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
Congratulations you now have Clockworkmod Recovery running on your Nexus 5.
Credits: Koush for developing Clockworkmod Recovery
Cyanogenmod Team for their development of Clockworkmod Recovery
F.A.Q
Q. Is this the touch version of Clockworkmod Recovery?
A. No, this is the non-touch version of Clockworkmod Recovery once any bugs have been worked out and the non-touch has been properly tested I will look into compiling a touch version unless an official version of Clockworkmod for the Nexus 5 is released.
Click to expand...
Click to collapse
Perfect, thanks
Awesome! Thanks!
Here we go.. awesome!
That was fast. :good:
That was quick, Wow!
Great! ))
wow, great!
Gesendet von meinem GT-I9100 mit Tapatalk
Thank you for your work :good:
Let the flashing begin!!!
Thanks man
Silly stupid noob question:
How to install it?
I dont understand how to do it xD
nad4321 said:
Silly stupid noob question:
How to install it?
I dont understand how to do it xD
Click to expand...
Click to collapse
You have to boot into fastboot mode to install this custom recovery on your device. Do you have fastboot and ADB setup on your computer and the device drivers installer for the Nexus 5? If you don't have fastboot and ADB setup on your computer I would recommend taking a look at this simple fastboot and ADB installer . Once you have fastboot and adb setup, and the device drivers installed follow the following steps:
1. Download this file.
2. Move the downloaded recovery file into the directory where you have ADB and Fastboot setup on your computer.
3. Navigate into the directory where you have ADB and Fastboot setup on your computer and run the following commands from the command prompt on your computer:
Code:
adb reboot bootloader
fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
After following this procedure you will then have Clockworkmod Recovery installed on your device. Let me know if you still have questions.
And make sure you
Code:
fastboot oem unlock
first!
I installed the recovery via fastboot.
When i try to boot into recovery i'm stuck at google screen.
I'm able to reboot the device.
Whats wrong?
Birba said:
I installed the recovery via fastboot.
When i try to boot into recovery i'm stuck at google screen.
I'm able to reboot the device.
Whats wrong?
Click to expand...
Click to collapse
Thats happening to me also.
Birba said:
I installed the recovery via fastboot.
When i try to boot into recovery i'm stuck at google screen.
I'm able to reboot the device.
Whats wrong?
Click to expand...
Click to collapse
Batfink33 said:
Thats happening to me also.
Click to expand...
Click to collapse
Are you too able to access recovery all? But you can reboot the device and still get into the bootloader for fastboot mode correct?
shimp208 said:
Are you too able to access recovery all? But you can reboot the device and still get into the bootloader for fastboot mode correct?
Click to expand...
Click to collapse
I can get into the bootloader,and flash the recovery but if i restart into recovery it sits at the Google screen. I then have to press the power button and restart the whole phone, Ive also tried booting into recovery using quickboot but again it sits at the Google screen.
sorry if this is a stupid question, but how do i boot into CWM? I have installed it correctly
shimp208 said:
You have to boot into fastboot mode to install this custom recovery on your device. Do you have fastboot and ADB setup on your computer and the device drivers installer for the Nexus 5? If you don't have fastboot and ADB setup on your computer I would recommend taking a look at this simple fastboot and ADB installer . Once you have fastboot and adb setup, and the device drivers installed follow the following steps:
1. Download this file.
2. Move the downloaded recovery file into the directory where you have ADB and Fastboot setup on your computer.
3. Navigate into the directory where you have ADB and Fastboot setup on your computer and run the following commands from the command prompt on your computer:
Code:
adb reboot bootloader
fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
After following this procedure you will then have Clockworkmod Recovery installed on your device. Let me know if you still have questions.
Click to expand...
Click to collapse
Do i first have to root it? Or does it do it automatically?
Would my data be deleted too?
Batfink33 said:
I can get into the bootloader,and flash the recovery but if i restart into recovery it sits at the Google screen. I then have to press the power button and restart the whole phone, Ive also tried booting into recovery using quickboot but again it sits at the Google screen.
Click to expand...
Click to collapse
Interesting I'm curious to know if the TWRP build I posted does the same any hints from dmesg or last_kmsg would also be beneficial, is it possible for you use Android Debug Monitor (DDMS and Monitor in Android SDK tools folder if you have the sdk installed) and upload a log?
Okay so here is propably another noob question: On my HTC Sensation I had 4ext as recovery. What are the differences between this and 4ext or TWRP? Is there a thread somewhere I couldn't find!?
[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?
Hello,
I have successfully unlocked my AT&T HTC One M9 and I am now trying to flash the recovery and root device. I am currently getting a error when attempting to flash that it cannot open file. I have renamed 'twrp-2.8.6.1_CPTB-B1-hima' to 'recovery.img'.
I currently have the file located where my ADB is located.
I am using command 'fastboot flash recovery recovery.img' with no success.
Any help would be appreciated.
Thank you.
dgub said:
Hello,
I have successfully unlocked my AT&T HTC One M9 and I am now trying to flash the recovery and root device. I am currently getting a error when attempting to flash that it cannot open file. I have renamed 'twrp-2.8.6.1_CPTB-B1-hima' to 'recovery.img'.
I currently have the file located where my ADB is located.
I am using command 'fastboot flash recovery recovery.img' with no success.
Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
You have to put your phone into download mode, either load boot loader and choose download mode or "adb reboot download" Also the official 2.8.6.1 is working great now, I would recommend it. https://dl.twrp.me/hima/ You don't have to rename the file either
Thank you for you reply.
That unfortunately will not work.
This is what I receive during command:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT53RYJ08038 device
C:\adb>adb reboot download
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>adb devices
List of devices attached
C:\adb>adb reboot bootloader
error: device not found
C:\adb>
I believe my phone is no longer available once it goes into bootloader and/or download mode. My commands no longer work in that state. I have tried to reinstall HTC drivers, but that does not work. I don't know if it is an issue but I can uninstall HTC Driver Install from my computer to install the latest which I believe is HTCDriver_4.2.0.001. If I try to install this with the current driver installed, it will not install.
dgub said:
Thank you for you reply.
That unfortunately will not work.
This is what I receive during command:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT53RYJ08038 device
C:\adb>adb reboot download
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>fastboot flash recovery recovery.img
error: cannot open 'recovery.img'
C:\adb>adb devices
List of devices attached
C:\adb>adb reboot bootloader
error: device not found
C:\adb>
I believe my phone is no longer available once it goes into bootloader and/or download mode. My commands no longer work in that state. I have tried to reinstall HTC drivers, but that does not work. I don't know if it is an issue but I can uninstall HTC Driver Install from my computer to install the latest which I believe is HTCDriver_4.2.0.001. If I try to install this with the current driver installed, it will not install.
Click to expand...
Click to collapse
adb does not work in boot loader mode. It says cannot open recovery.img. something is wrong with your image, or your not in the right directory, or your fastboot isn't working correctly. Nothing is wrong with your phone. Just install htc sync if you are worried about correct driver
Again thank you for your response. I have the image in the same file where I open on the command prompt. I have it on download screen, but it will not work. I will be trying this on a different computer, and hopefully it will work.
I have successfully flashed and rooted my phone. The issue is with computer I was using and I am unable to get Fastboot working properly even after re-install.
The subject of this thread has been resolved and I greatly appreciate your help.
Sent from my HTC One M9 using XDA Free mobile app
dgub said:
I have successfully flashed and rooted my phone. The issue is with computer I was using and I am unable to get Fastboot working properly even after re-install.
The subject of this thread has been resolved and I greatly appreciate your help.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Can you specify what the problem with the computer was? cause i have the same problem
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
sudo fastboot -i 0x19d2 boot recovery.img
sudo command not recognized in windows
anish.mvj said:
sudo fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
teji007 said:
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
Click to expand...
Click to collapse
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Thanks and a little more help
anish.mvj said:
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
teji007 said:
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
Click to expand...
Click to collapse
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Failed
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
It says wiping failed(please wipe again or do it after reboot) everytime.
and nothing is working even app wipe or data wipe, only cache wiped works and choose from phone storage is also n ot working and sd card is also being not dtetected.
even in TWRP
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
teji007 said:
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
Click to expand...
Click to collapse
Dude please be clear what you want to do? Stock rom or custom?
Custom
anish.mvj said:
Dude please be clear what you want to do? Stock rom or custom?
Click to expand...
Click to collapse
.
Sir i want custom Rom. and sir now i am bricked
teji007 said:
.
Sir i want custom Rom. and sir now i am bricked
Click to expand...
Click to collapse
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Thanks going to try
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
teji007 said:
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
Click to expand...
Click to collapse
Check your private message
adb sideload not working
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Sir, its been 5 mins its "starting ADB sideload feature" but nothing
adb sideload failed
anish.mvj said:
Check your private message
Click to expand...
Click to collapse
Sir ,
ADB sideload failed
teji007 said:
Sir ,
ADB sideload failed
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
akram0010 said:
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
Click to expand...
Click to collapse
Assuming that the bootloader is unlocked.
aIecxs said:
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
Click to expand...
Click to collapse
Sorry i forgot to mention, but still unlocking bootloader doesn't root device.
I think the question is still valid
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Is root needed
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Can you please tell me what is this recovery.img, and where would i get it (in Fastboot rom or recovery rom).
As i said earlier i am a newbie in this field and very much confused with these terms.
no root required click on the first link above and download TWRP for your device (TWRP-3.4.2.b_lancelot.zip)
I assume you are running windows?
extract zip file and place recovery.img on your PC in platform-tools directory. connect phone in fastboot mode, install android_winusb.inf "Android Bootloader Interface" drivers and from cmd.exe check fastboot devices
if you can see device serialno you are ready to boot TWRP from fastboot with above first command.
for linux just install android-tools-fastboot
As i am using Ubuntu i installed ADB, FASTBOOT using the APT :
Code:
sudo apt install android-tools-adb android-tools-fastboot
.
Therefore i don't have the platform-tools directory.
Also I am unable to quote reply, its showing error (Oops, we broke the Matrix, someone call Neo)
yes that's right. it doesn't matter which directory files are placed. that way you installed fastboot binary is already in PATH. linux is far more easier and doesn't require additional drivers. it might require additional udev rules to make fastboot work, but you can simply by-pass with sudo fastboot for now...