Hi, everyone, I bricked my nothing phone when flashing pixel experience GSI. Now, it only boot to fastboot mode and I can not flash super partition, such as system, vendor, product, system_ext, odm, vendor_dlkm (other is OK). But when I set active slot to A, it boot successfully. So, any one can share the backup of super partition of Globle nothingOS 1.1.3, I want to fix my broken slot B partition. Thanks a lot!
banyam said:
Hi, everyone, I bricked my nothing phone when flashing pixel experience GSI. Now, it only boot to fastboot mode and I can not flash super partition, such as system, vendor, product, system_ext, odm, vendor_dlkm (other is OK). But when I set active slot to A, it boot successfully. So, any one can share the backup of super partition of Globle nothingOS 1.1.3, I want to fix my broken slot B partition. Thanks a lot!
Click to expand...
Click to collapse
Did you unlock the bootloader with fastboot flashing unlock and fastboot flashing unlock_critical?
Did you try to flash the missing partitions in fastbootd mode? (Enter fastbootd with fastboot reboot fastboot)
This tutorial helped me with my bricked phone:
Unbrick Nothing Phone 1: Flash Stock Firmware via Fastboot Commands
In this tutorial, we will show you the steps to unbrick your Nothing Phone 1 by flashing the stock firmware via Fastboot Commands.
www.droidwin.com
Possible to get rw after root?
Android Orange said:
Did you unlock the bootloader with fastboot flashing unlock and fastboot flashing unlock_critical?
Did you try to flash the missing partitions in fastbootd mode? (Enter fastbootd with fastboot reboot fastboot)
This tutorial helped me with my bricked phone:
Unbrick Nothing Phone 1: Flash Stock Firmware via Fastboot Commands
In this tutorial, we will show you the steps to unbrick your Nothing Phone 1 by flashing the stock firmware via Fastboot Commands.
www.droidwin.com
Click to expand...
Click to collapse
Thanks a lot. Both bootloader and critical are unlocked. I will try this tutorial you provided.
Android Orange said:
Did you unlock the bootloader with fastboot flashing unlock and fastboot flashing unlock_critical?
Did you try to flash the missing partitions in fastbootd mode? (Enter fastbootd with fastboot reboot fastboot)
This tutorial helped me with my bricked phone:
Unbrick Nothing Phone 1: Flash Stock Firmware via Fastboot Commands
In this tutorial, we will show you the steps to unbrick your Nothing Phone 1 by flashing the stock firmware via Fastboot Commands.
www.droidwin.com
Click to expand...
Click to collapse
I have follwing the tutorial to flash in both slot A and slot B. When flashing to slot A, all steps is OK, but to slot B, some img, such as "odm.img, system.img" failed to flash, it display "no such file or directory". I don't know why.
banyam said:
I have follwing the tutorial to flash in both slot A and slot B. When flashing to slot A, all steps is OK, but to slot B, some img, such as "odm.img, system.img" failed to flash, it display "no such file or directory". I don't know why.
Click to expand...
Click to collapse
And your phone is in fastbootD?
If yes, i have no idea how to fix that.
Android Orange said:
And your phone is in fastbootD?
If yes, i have no idea how to fix that.
Click to expand...
Click to collapse
Fix has already been found, I don't know if super partition from global or EEA matters, try with the one already out, that's just to recreate all the fcked partitions. They will be erased again with the script anyway
banyam said:
I have follwing the tutorial to flash in both slot A and slot B. When flashing to slot A, all steps is OK, but to slot B, some img, such as "odm.img, system.img" failed to flash, it display "no such file or directory". I don't know why.
Click to expand...
Click to collapse
you should flash a super partiton backup (region doesn't matter) reboot into fastbootd and (if you want) use my tool to flash all the partitions in fastbootd mode https://github.com/sh4tteredd/nothing-phone-1-tools
EDIT: @AntoXik72 knows
sh4tteredd said:
you should flash a super partiton backup (region doesn't matter) reboot into fastbootd and (if you want) use my tool to flash all the partitions in fastbootd mode https://github.com/sh4tteredd/nothing-phone-1-tools
EDIT: @AntoXik72 knows
Click to expand...
Click to collapse
sh4tteredd said:
you should flash a super partiton backup (region doesn't matter) reboot into fastbootd and (if you want) use my tool to flash all the partitions in fastbootd mode https://github.com/sh4tteredd/nothing-phone-1-tools
EDIT: @AntoXik72 knows
Click to expand...
Click to collapse
Ok, thanks. You mean I can also flash super partition of EEA 1.1.3?
Android Orange said:
And your phone is in fastbootD?
If yes, i have no idea how to fix that.
Click to expand...
Click to collapse
Yes, It is in fastbootD mode.
Mr Hassan said:
Possible to get rw after root?
Click to expand...
Click to collapse
Sorry, you mean system rw?
AntoXik72 said:
Fix has already been found, I don't know if super partition from global or EEA matters, try with the one already out, that's just to recreate all the fcked partitions. They will be erased again with the script anyway
Click to expand...
Click to collapse
OK, I will try to flash the super partition of EEA 1.1.3 already out. Thanks.
banyam said:
Sorry, you mean system rw?
Click to expand...
Click to collapse
Yes
sh4tteredd said:
you should flash a super partiton backup (region doesn't matter) reboot into fastbootd and (if you want) use my tool to flash all the partitions in fastbootd mode https://github.com/sh4tteredd/nothing-phone-1-tools
Click to expand...
Click to collapse
banyam said:
Ok, thanks. You mean I can also flash super partition of EEA 1.1.3?
Click to expand...
Click to collapse
Yes, after the flash just reboot directly in the bootloader and start my tool
Code:
fastboot reboot bootloader
If slot A is working why don't you sideload the latest Full OTA ? It should flash the B partition and boot from there.
gm007 said:
If slot A is working why don't you sideload the latest Full OTA ? It should flash the B partition and boot from there.
Click to expand...
Click to collapse
if you have a corrupted b slot some features won't work (ex: you'll probably get in problems trying to install an OTA)
Probably possible to craft an empty super.img by extracting the EEA one, replacing the image contents with ones that are zeroed out, and recompressed with the same metadata.
Just a theory though.
A game theory.
btw, try this command to backup the super partition:
Code:
adb pull /dev/block/by-name/super super.img
hahagu said:
btw, try this command to backup the super partition:
Code:
adb pull /dev/block/by-name/super super.img
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=de_AT&gl=US just use this app, root is needed
I will also like to fix a broken partition, but no idea how to do it. So my current slot A is unbootable
Related
Today I got a message saying that SuperSU needs to be updated on my rooted Nexus 10 with stock Android 5.1. Then it booted into TWRP and flashed the zip file, but now it's stuck with the bootloop forever. How can I get out this mess without losing anything? Step-by-step instruction with fastboot would be highly appreciated.
Would reflashing 5.1 with the following commands be good enough to restore the system without losing userdata once I boot into fastboot mode?
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
Do I need those erase steps such as
fastboot erase boot
fastboot erase cache
fastboot erase system
Thanks in advance!
mj56gt said:
Today I got a message saying that SuperSU needs to be updated on my rooted Nexus 10 with stock Android 5.1. Then it booted into TWRP and flashed the zip file, but now it's stuck with the bootloop forever. How can I get out this mess without losing anything? Step-by-step instruction with fastboot would be highly appreciated.
Would reflashing 5.1 with the following commands be good enough to restore the system without losing userdata once I boot into fastboot mode?
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
Do I need those erase steps such as
fastboot erase boot
fastboot erase cache
fastboot erase system
Thanks in advance!
Click to expand...
Click to collapse
Don't you have the nandroid backup?
Your steps look right. I check them on here: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
See the last part of step 11. It says:
Code:
If going for a complete back to stock using the manual flashing of the zip file, execute the following commands after the above 4:
fastboot erase userdata
fastboot flash userdata userdata.img
So if you DON"T do this step, user data should be there. But I do not own this tablet and not 100% sure about that. Do that on your own risk :fingers-crossed:
Many thanks for checking the steps for me!
nitin.chobhe said:
Don't you have the nandroid backup?
Click to expand...
Click to collapse
No, I don't have a recent nandroid backup. I can still run adb, and have managed to pull out those photos on the tablet. Do you think that I could boot into the recovery mode and perform the nandroid backup?
nitin.chobhe said:
Code:
If going for a complete back to stock using the manual flashing of the zip file, execute the following commands after the above 4:
fastboot erase userdata
fastboot flash userdata userdata.img
So if you DON"T do this step, user data should be there. But I do not own this tablet and not 100% sure about that. Do that on your own risk :fingers-crossed:
Click to expand...
Click to collapse
What's the worst scenario if I don't erase the userdata?
mj56gt said:
Many thanks for checking the steps for me!
No, I don't have a recent nandroid backup. I can still run adb, and have managed to pull out those photos on the tablet. Do you think that I could boot into the recovery mode and perform the nandroid backup?
What's the worst scenario if I don't erase the userdata?
Click to expand...
Click to collapse
1. Even if you do nandroid, it would be exact replica of your current state i.e. boot loop
2. Worst scenario is bootloop
nitin.chobhe said:
1. Even if you do nandroid, it would be exact replica of your current state i.e. boot loop
2. Worst scenario is bootloop
Click to expand...
Click to collapse
I've fully restored the system without losing any data! Really appreciate your help!
mj56gt said:
I've fully restored the system without losing any data! Really appreciate your help!
Click to expand...
Click to collapse
What steps did you follow... Happy that it worked out for you! :good:
mj56gt said:
I've fully restored the system without losing any data! Really appreciate your help!
Click to expand...
Click to collapse
Just the steps in my original post, and also the same steps mentioned in the link you mentioned. Thanks again for your kind help!
mj56gt said:
Just the steps in my original post, and also the same steps mentioned in the link you mentioned. Thanks again for your kind help!
Click to expand...
Click to collapse
You can just press that thanks button ?
Sent from my Nexus 4 using XDA Free mobile app
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?
thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes
acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.
thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!
hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.
Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
emmanueldlauron said:
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
and post results.
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
emmanueldlauron said:
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
Okay, last question - single SIM or dual SIM?
Dual Sim
emmanueldlauron said:
flash my device to official stock rom
Click to expand...
Click to collapse
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download Service ROM
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
I don't have sd card on me right now. is there any way I can flash service rom without sd card?
Edit: and also this device is C636xxx.
neverming the first paragraph I said. I'm confused with CUST.img thing, I donwloaded the C635 update but there's no second archive on what I had downloaded
emmanueldlauron said:
flash service rom without sd card?
Click to expand...
Click to collapse
Nope.
emmanueldlauron said:
this device is C636xxx.
Click to expand...
Click to collapse
Okay, then download C636
-Alf- said:
Nope.
Okay, then download C636
Click to expand...
Click to collapse
Thanks for the tips and ideas, I somehow understand something new today.
emmanueldlauron said:
there's no second archive on what I had downloaded
Click to expand...
Click to collapse
VNS-L31_hw_xxxxx
-Alf- said:
VNS-L31_hw_meafnaf
Click to expand...
Click to collapse
Oh yeah. I just figured it out but had to rename that to update.app so update extractor can accept the file. Thanks by the way.
for now SYSTEM and CUST takes time to finish extracting.
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
emmanueldlauron said:
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
Click to expand...
Click to collapse
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
-Alf- said:
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
Click to expand...
Click to collapse
emmanueldlauron said:
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
still the same with these
emmanueldlauron said:
still the same with these
Click to expand...
Click to collapse
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
-Alf- said:
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
B361 firmware is a fullOTA-MF-PV version, download and instructions here
Click to expand...
Click to collapse
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
emmanueldlauron said:
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
Click to expand...
Click to collapse
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
-Alf- said:
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
Click to expand...
Click to collapse
No problem. I think I hard bricked my phone, I just got boot logo and fastboot but I can't find any fix or solution or anything to do with this.
Flashing recovery or recovery2 finished w/o any errors but I can't boot to recovery.
Thanks for your help by the way. I appreciate it! Kudos and have a nice day. Keep safe.
emmanueldlauron said:
I think I hard bricked my phone,
Click to expand...
Click to collapse
IMO you only need an SD card and flash the Service ROM.
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery