my phone is moto g2 xt1068
i flash it with fastboot very much because after 3 days restarting and hang in boot but after flash it is work for 3-5 days
now i want to flash it but have this error fastboot
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.979s]
writing 'partition'...
FAILED (status read failed (Too many links))
finished. total time: 1.778
please help me
thanks
Do you have twrp?
Have you tried flashing twrp if you don't have it installed?
Which ROM are you flashing?
It looks like you don't have enough space if I'm reading that error correctly
We need to know so we can help you
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
This is stock firmware, yes?
Are all your Moto G drivers up to date?
There are a number of different ways to install depending on the package type.
Some packages are flashable zips. Needs Twrp (Team Win Recovery Project)
Some are sideload packages installed via Fastboot.
Some are OTA packages (OTA, over the air) installed via phone update.
amir58hz said:
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
Click to expand...
Click to collapse
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
bejunk said:
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
Click to expand...
Click to collapse
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
amir58hz said:
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
Click to expand...
Click to collapse
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
bejunk said:
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
Click to expand...
Click to collapse
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
amir58hz said:
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
Click to expand...
Click to collapse
Thx. But i need a picture of bootloader screen, see my picture!
-> hmm in your case i would try it now with formatting internal completly.. But even better would be full formating, so when you have TWRP:
- format Internal storage
- then tick system + data + cache and format them.
- You have to reflash stock then OR (i recommend) try it with a custom rom, like you said allready tried stock many times...
To install custom rom, get these files
ROM: https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-15-1-t3786749 get latest build
GApps: https://opengapps.org/ choose ARM -> 8.1 -> nano version
put everything in sdcard or storage (after wiping it)
Then in TWRP -> factory reset in wipe menu -> install ROM zip -> install GApps -> reboot. 1st boot can take some time. Test & report.
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
bejunk said:
Thx. But i need a picture of bootloader screen, see my picture!
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
Click to expand...
Click to collapse
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
amir58hz said:
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
Click to expand...
Click to collapse
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
Thanks very much
I dont have custom rom can you advise me to download it
I flashed it if is not have problem is very good but it crash and dont work i send here my problem
Thanks again good luck
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
hi man
after one day mobile is work true thanks alot
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
amir58hz said:
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
Click to expand...
Click to collapse
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
bejunk said:
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
Click to expand...
Click to collapse
No i flash it with same my frimware
Now for flashing with custom rom it need download rom android8?
i have this error in wipping and installing rombut instal it
my error is:
e:recv error on uevent
But now flashed to 8.1 android
Thanks
Related
Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.
Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s
cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip
Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?
waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.
Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
hollywood_jack said:
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
Click to expand...
Click to collapse
Or do it manualy with adb, look here as a guide http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504 method 2. Toolkits will always bite you in the ass at some point in the future
gee2012 said:
Toolkits will always bite you in the ass at some point in the future
Click to expand...
Click to collapse
Sorry but I not have understood this
hollywood_jack said:
Sorry but I not have understood this
Click to expand...
Click to collapse
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
gee2012 said:
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
Click to expand...
Click to collapse
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
hollywood_jack said:
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
Click to expand...
Click to collapse
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
gee2012 said:
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
Click to expand...
Click to collapse
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
hollywood_jack said:
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
Click to expand...
Click to collapse
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
gee2012 said:
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
Click to expand...
Click to collapse
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
hollywood_jack said:
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
Click to expand...
Click to collapse
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
gee2012 said:
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
Click to expand...
Click to collapse
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop with the following flash (always method 2)?
hollywood_jack said:
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop?
Click to expand...
Click to collapse
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
gee2012 said:
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
Click to expand...
Click to collapse
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
hollywood_jack said:
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
Click to expand...
Click to collapse
Extract the rom and flash the bootloader first (fastboot flash bootloader namebootloader.img) and fastboot reboot-bootloader, then the radio and also reboot and then the rest in one go. Good luck an if you have doubts/problems post it here. Plenty of helpfull members around
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
hollywood_jack said:
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the BL it stays unlocked unless you lock it manualy. Even if you flash a new bootloader.
Thanks my friend...thanks alot
with my Nexus 6
hollywood_jack said:
Thanks my friend...thanks alot
with my Nexus 6
Click to expand...
Click to collapse
Good luck, its only a bit stressfull the first time
gee2012 said:
Good luck, its only a bit stressfull the first time
Click to expand...
Click to collapse
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
hollywood_jack said:
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
Click to expand...
Click to collapse
- You don`t have to erase boot and recovery
- Yes you can flash a non encryped kernel but you`ll have to factory reset after you flashed and the N6 is booting or your storage will say its 32GB.
- Rooting is easiest by placing the latest 2.8.7.1 TWRP recovery in the sdk-platform-tools folder, reboot in bootloadermode and fastboot boot namerecovery.img and boot up and flash the latest superSU.zip (Beta 2.49 afaik) or use a toolkit if want to.
Hello everybody,
I was trying to reinstall the factory image on my Nexus 6 with a script and everything went wrong. Now when I reboot in recovery I have a menu (restart bootloader, recovery.....) but I can't see with my phone on my computer (ubuntu). I tried every mode on the phone menu : bootloader, recovery, factory mode, bar codes, bptools....but the phone doesn't mount on the computer.
So I'm not able to do anything on it. Any clues ?
Thanks.
Martin
Well, I made some progress. I found this and the command ''adb sideload''. But now, I'm stuck with ''you need adb 1.0.32 or newer'' to install a recovery on my Nexus.
Can't find an easy way to install a ''newer'' adb tools on my Ubuntu...
Now, i managed to update the adb version to 1.0.32. But I got the message when I ''adb sideload'' twrp-2.8.7.1-shamu.img:
E:footer is wrong
E:Signature verification failed
Installation aborted
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
mchenier said:
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
Click to expand...
Click to collapse
your answer..
thats not your recovery that youre booting into, thats your bootloader. and the only thing that works in the bootloader is fastboot. adb does not work in the bootloader. and you need to use fastboot to flash a factory image, not adb.
Ok, thanks. I just figure that out couple of minutes ago. I'm almost there. I was able to install TWRP on my Nexus 6. The problem now is when i tried to install ''image-shamu-mmb29q.zip'' with TWRP, it failed even if I wipe the cache and Dalvik cache before. And I don't know why.
It's says ''Error flashing zip
Ok, I have done it. Find that web page to help me: http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I thought I had to install the zip file with TWRP. The right action was that:
First, flash the bootloader and the radio, and then reboot the bootloader (radio only applies to some devices):
fastboot flash bootloader <bootloader file name here>.img fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader
Flash the recovery, boot, system, and vendor images (vendor only applies to some devices):
fastboot flash recovery recovery.img fastboot flash boot boot.img fastboot flash system system.img fastboot flash vendor vendor.img
Recommended: For a full wipe, flash cache and userdata as well (userdata only applies to some devices):
fastboot flash cache cache.img fastboot flash userdata userdata.img
Reboot your device:
fastboot reboot
Thanks. I'm done.
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
simms22 said:
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
Click to expand...
Click to collapse
Don't know what the stickies are.
mchenier said:
Don't know what the stickies are.
Click to expand...
Click to collapse
this is a helpful sticky from the general thread http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066
they are important threads stuck, or stickied, to the top of the general section
Ok, thanks. I'll keep it for future references.
mchenier said:
Ok, thanks. I'll keep it for future references.
Click to expand...
Click to collapse
also, if your stuck somewhere, pm me. i would be happy to help.
simms22 said:
also, if your stuck somewhere, pm me. i would be happy to help.
Click to expand...
Click to collapse
Eh! thanks a lot.
I just installed Cyanogenmod on a Nexus 4. I have a collection to work with. Someday I might be good at it
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好,我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img(adb >> fastboot flash system system.img中的命令)
2. boot.img(adb 中的命令,如#1,更改 img 文件的名称)直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img(选择twrp与你要安装的rom兼容)
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Can't even fastboot flash boot recovery system...and thats all folks...waste of money.
Failed attempt to unlock the bootloader and instal TWRP ?
Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Just flash the ROM again..It will be back lm
mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first
SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?
mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone
Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it
Hows your phone?..Did it work.