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
Related
My first post but I've been lurking for years. Pretty good with search, etc.
If anyone could help I would really appreciate it. I've been working on this for 12 hours!
I updated to Cyanogen 4.1.999
I successfully installed the new radio and fastboot confirms 2.22.19.261
Here's where I made the mistake in the following directions:
I have CMRecovery Image 1.4
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-4.1.99
http://n0rp.chemlab.org/android/expe....99-signed.zip
-put them both on your SD card
-Boot up into CM recovery image 1.4 by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
I mistakenly rebooted normally instead of applying the update in the next step. This is when the black screen began.
-Then update any zip usig CyanogenMod-4.1.99 (update-cm-4.1.99-signed.zip)
-Then power on the phone
I am stuck at the black screen of death.
I can fastboot and I've fastbooted the pimp recovery and still can't access recovery. Just get the triangle.
So, during update after new radio I rebooted normally instead of updating with the final build update got a black screen and have no recovery.
I've tried fastboot flash recovery and fastboot update.
fastboot flash recovery is succesful
fastboot update or fastboot flashall give me the "archive does not contain android-info.text and android-product.text" errors.
Any ideas would be greatly appreciated.
this should be posted in Q/A not development.
cingall said:
this should be posted in Q/A not development.
Click to expand...
Click to collapse
Sorry!
Mod please move. Thanks!
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
theomajigga said:
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
Click to expand...
Click to collapse
any ideas on the commands to flash them as flashall? HTC's site has them as separate files so I can only flash the "recovery" file.
I'm sorry to be somewhat of a noob with the actual codes. Could you be more specifc with which files to flash with which commands?
TIA!
Using the HTC website 1.6 "recovery" with fastboot update I get the following:
Error: update package has no android-info.txt or android-product.txt
I can't figure out how to flash the radio or system files in any other way than update in fastboot.
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Also remove your SD card while booting, as prior stuff in your ext3 partition can cause black screens during boot. If that fixes it, you need to reformat your ext3.
The triangle you see is the standard recovery, to access it you need to do alt-L?or alt-x cant remember. To fix you need to flash cm-recovery to do this reboot into the boot loader (power + camera) plug in usb and hit the back button you should see "fastboot" then run
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
seehttp://forum.xda-developers.com/showthread.php?t=523558
then install rom as normal
okay this happened to me as well. I just made sure that I wiped, then started allover again. i had to do it a couple of times but it worked. just make sure that you still have the files on your SD card.
Good Luck!!!!
brnbock said:
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Click to expand...
Click to collapse
You are a STAR!! Thank you, thank you, thank you!! I knew it was something stupid!
Back at the recovery console! woot!!!
Mods please close this thread!
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
took 30 min to post a re.. sorry i was late
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
That should fix it.
ugh, now I am stuck at the g1 screen after a reboot of a successful update.
reformatted sd and all probs are solved!
mghtyred said:
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
Click to expand...
Click to collapse
Hi mghtyred (of tmobile forums) welcome to XDA
Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance
You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.
1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot
You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.
Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.
my phoe is broken i need to flash twrp and i cant to do it ,i setup cyanogenmod recovery by mistake and this recovery is fault because i cant even transfer any files form computer to mobile .. i try to flash with sp tool but it give me error because my phone is broken ,i try also dirtycow v11 on my phone to try flash twrp but it cant read phone on the computer and i setup V21 rom ??
sorry for bad english
any HElp plaese?
meroher said:
any HElp plaese?
Click to expand...
Click to collapse
How you mean broken?
Can it boot to fastboot mode?
YEP IT CAN BOOT TO FASTBOOT ?! then what?
mrmazak said:
how you mean broken?
Can it boot to fastboot mode?
Click to expand...
Click to collapse
plaese man help me my mob is still broken ineed it now
meroher said:
plaese man help me my mob is still broken ineed it now
Click to expand...
Click to collapse
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
mrmazak said:
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
Click to expand...
Click to collapse
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
meroher said:
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
Click to expand...
Click to collapse
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
mrmazak said:
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
Click to expand...
Click to collapse
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
meroher said:
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
Click to expand...
Click to collapse
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
mrmazak said:
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
Click to expand...
Click to collapse
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
meroher said:
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
Click to expand...
Click to collapse
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
oki i try install recovery but it same thing it go to white screen and restart again and again
i will wait for you to help me more thanks ><
mrmazak said:
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
Click to expand...
Click to collapse
oki i will wait you thanks for your time
meroher said:
oki i will wait you thanks for your time
Click to expand...
Click to collapse
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
mrmazak said:
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
Click to expand...
Click to collapse
it works fine finally thanks very much for help :]:]:laugh::laugh:
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
Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
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 reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
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 reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.