Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?
TheSpecificOcean said:
Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905
Click to expand...
Click to collapse
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try
TheSpecificOcean said:
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try
Click to expand...
Click to collapse
Post all the details!!
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
Use this http://forum.xda-developers.com/showthread.php?t=2246081
The original not my vzw workaround.
aviwdoowks said:
Post all the details!!
Click to expand...
Click to collapse
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.
TheSpecificOcean said:
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.
Click to expand...
Click to collapse
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.
aviwdoowks said:
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.
Click to expand...
Click to collapse
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.
TheSpecificOcean said:
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.
Click to expand...
Click to collapse
Get rsd 615.
aviwdoowks said:
Get rsd 615.
Click to expand...
Click to collapse
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work
TheSpecificOcean said:
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work
Click to expand...
Click to collapse
I use w7.
aviwdoowks said:
I use w7.
Click to expand...
Click to collapse
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken
TheSpecificOcean said:
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken
Click to expand...
Click to collapse
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.
aviwdoowks said:
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.
Click to expand...
Click to collapse
no i haven't i am going to try the ose 4.3 with a 4.3 gsm fix and if that fails i will try that one it will respond with results maybe if i have time
EDIT: OSE didn't work gonna try the link u posted
Edit: Finally got the rom u posted above to work but no improvement the service didnt improve however i noticed i was unable to select any other band types from the mobile networks menu
I'm a bit off topic after all this but what i'm effectively looking for is a backup that can be flashed via CWM or installed via zip. I cannot for the life of me get fastboot or rdslite to work. The files from the http://forum.xda-developers.com/show...ighlight=xt905 are all fastboot files and can't be installed by CWM from zip. Or alternatively a working xt905 rom because at the moment all unofficial or official versions with gsm fixes are unable to find any cellular in Australia. I'm currently with Telstra through ALDImobile at the moment if it helps, not looking for lte just h+ or 3g if possible. At the moment i'm stuck with a glorified mp3 player.
I thought i might post the log from the fastboot attempts when im using the fastboot that comes with the retail stock firmware. I noticed some that looked out of place and have searched them but found nothing that helped main culprits being
(bootloader) Variable not supported!
(bootloader) Preflash validation failed
Invalid sparse file format at header magi
Code:
Flashing bootloader images ...
So as to use latest flash capabilities
< waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.284s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.559s]
finished. total time: 0.578s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl2' (126 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.929s]
finished. total time: 0.948s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl3' (512 KB)...
OKAY [ 0.049s]
writing 'sbl3'...
OKAY [ 1.111s]
finished. total time: 1.160s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'rpm' (140 KB)...
OKAY [ 0.017s]
writing 'rpm'...
OKAY [ 0.552s]
finished. total time: 0.570s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'tz' (192 KB)...
OKAY [ 0.023s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.319s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'aboot' (256 KB)...
OKAY [ 0.025s]
writing 'aboot'...
OKAY [ 0.827s]
finished. total time: 0.853s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
Flashing modem SW...
error: < waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'fsg' (2825 KB)...
OKAY [ 0.221s]
writing 'fsg'...
OKAY [ 1.169s]
finished. total time: 1.391s
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.617s]
finished. total time: 0.618s
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.613s]
finished. total time: 0.613s
Flashing AP Images...
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'logo' (854 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 1.120s]
finished. total time: 1.190s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.348s]
finished. total time: 0.395s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.789s]
writing 'boot'...
OKAY [ 2.806s]
finished. total time: 3.595s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.790s]
writing 'recovery'...
OKAY [ 2.002s]
finished. total time: 2.794s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
erasing 'tombstones'...
OKAY [ 0.801s]
finished. total time: 0.801s
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 1.045s]
finished. total time: 1.045s
Erasing userdata...
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 4.423s]
finished. total time: 4.423s
All images flashed. Check logs for errors!
Press any key to continue . . .
http://forum.xda-developers.com/showthread.php?t=2169220&page=2 just found this which solves half my problem any ideas on getting rdslite to work is it a win 8 issue maybe
FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.
TheSpecificOcean said:
FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.
Click to expand...
Click to collapse
Would you post a screen shot of the bottom half of your about phone page?
aviwdoowks said:
Would you post a screen shot of the bottom half of your about phone page?
Click to expand...
Click to collapse
yeah sure
Related
I manage to relock my XT925 Bootloader.
Process is very simple
THIS IS FOR WINDOWS ONLY!!!! Thanks @skeevydude
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Please feel free to Edit/Delete the thread
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C6802 using Tapatalk
kumeipark said:
I manage to relock my XT925 Bootloader.
Process is very simple
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Click to expand...
Click to collapse
so all that's necessary to type "mfastboot oem lock", or is the flash back to stock for safety reasons....listing steps isn't that helpful if the reasons aren't posted.
and have you tested "mfastboot oem unlock" or does the exploit need to be ran again to unlock the bootloader?
....shouldn't post about locking the bootloader without saying if it can be unlocked again or not.
EDIT:
And label or mention that this is for Windows Only
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
kumeipark said:
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
skeevydude said:
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
Click to expand...
Click to collapse
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
kumeipark said:
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
Click to expand...
Click to collapse
So basically this method should only be done by phones that can officially be unlocked by Motorola? Personally, I don't want to be the one that finds out a hack unlocked phone can't go from status 2 to status 3...but that's what random idiots who flash anything they see are for...(un)fortunately for us, there's a lot of them...
Seeing as how a ton of us are running hacked unlocked phones, including myself, and how not everyone here actually has a RAZR HD, including myself...anything discussing bootloaders and locking them needs to be well documented, if only to cover your ass when some dipcrap does this and screws their self. Though it does say XT925 in the thread title and don't do this on a 926 in the thread...
To clear all doubts I took the liberty to unlock my bootloader after relocking it
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem get_unlock_data
...
(bootloader) 3A24528415225372#54413234303032
(bootloader) 49523300000000000000000000#2144
(bootloader) 9FCE87F32A6179FAAA0D23AD8BCCF85
(bootloader) E5675#1660910902000100000011110
(bootloader) 0000000
OKAY [ 0.272s]
finished. total time: 0.273s
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem unlock VZJUGTAYKHYZA5KXXXXX
...
(bootloader) Unlock completed! Wait to reboot
Now relocking again!
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>XT925_erase_userdata.bat
Flashing bootloader images ...
So as to use latest flash capabilities
...
(bootloader) Ready to flash signed images
OKAY [ 0.273s]
finished. total time: 0.274s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.349s]
finished. total time: 0.364s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.482s]
finished. total time: 0.500s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl2' (127 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.892s]
finished. total time: 0.913s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl3' (512 KB)...
OKAY [ 0.046s]
writing 'sbl3'...
OKAY [ 1.076s]
finished. total time: 1.124s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.472s]
finished. total time: 0.496s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'tz' (192 KB)...
OKAY [ 0.024s]
writing 'tz'...
OKAY [ 0.495s]
finished. total time: 0.521s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'aboot' (256 KB)...
OKAY [ 0.029s]
writing 'aboot'...
OKAY [ 0.773s]
finished. total time: 0.804s
Flashing modem SW...
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'modem' (30720 KB)...
OKAY [ 2.278s]
writing 'modem'...
OKAY [ 1.160s]
sending 'modem' (17412 KB)...
OKAY [ 4.233s]
writing 'modem'...
OKAY [ 1.190s]
finished. total time: 8.865s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'fsg' (2852 KB)...
OKAY [ 0.218s]
writing 'fsg'...
OKAY [ 1.371s]
finished. total time: 1.591s
erasing 'modemst1'...
OKAY [ 0.770s]
finished. total time: 0.770s
erasing 'modemst2'...
OKAY [ 0.749s]
finished. total time: 0.750s
Flashing AP Images...
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'logo' (1709 KB)...
OKAY [ 0.134s]
writing 'logo'...
OKAY [ 1.429s]
finished. total time: 1.565s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.515s]
finished. total time: 0.564s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'boot' (10240 KB)...
OKAY [ 0.762s]
writing 'boot'...
OKAY [ 4.136s]
finished. total time: 4.900s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'recovery' (10240 KB)...
OKAY [ 0.762s]
writing 'recovery'...
OKAY [ 3.165s]
finished. total time: 3.928s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.275s]
writing 'system'...
OKAY [ 3.718s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.225s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.257s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.235s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.227s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.246s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.256s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.365s]
sending 'system' (30720 KB)...
OKAY [ 5.085s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.210s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.245s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.230s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.238s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.241s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.259s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.247s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.248s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.219s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (4659 KB)...
OKAY [ 3.300s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 174.838s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'cdrom' (30720 KB)...
OKAY [ 2.274s]
writing 'cdrom'...
OKAY [ 3.178s]
sending 'cdrom' (22538 KB)...
OKAY [ 4.625s]
writing 'cdrom'...
OKAY [ 2.594s]
finished. total time: 12.675s
erasing 'tombstones'...
OKAY [ 0.905s]
finished. total time: 0.906s
erasing 'cache'...
OKAY [ 1.223s]
finished. total time: 1.224s
Erasing userdata...
erasing 'userdata'...
OKAY [ 4.437s]
finished. total time: 4.438s
Locking Bootloader...
...
FAILED (status read failed (Too many links))
finished. total time: 21.883s
All images flashed. Check logs for errors!
Press any key to continue . . .
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>
While relocking bootloader it says
Code:
Locking Bootloader...
...
FAILED (status read failed (Too many links))
But the device will locked
Please note: Some text are altered for privacy concern
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
peladoro said:
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I read in another forum about an user has "discovered this re-lock method", and asked in Motorola's forum about the status code and the meanings and the answer was something like this
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= relocked but also without warranty
And I don't remember very well if status code 1 is for developers edition phones and it means relocked but with warranty..
Enviado desde mi RAZR HD mediante Tapatalk
Thanks!
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
joaomanobrown said:
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
Click to expand...
Click to collapse
kumeipark said:
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Thanks!
Thank's guy's!
nice
Please, how do I unlock again ... at the motorola site was unable
HugoTJB said:
Please, how do I unlock again ... at the motorola site was unable
Click to expand...
Click to collapse
Previously how you unlock your BL??
Is your model XT925??
iBolski said:
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Click to expand...
Click to collapse
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Graf Schmidt said:
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Click to expand...
Click to collapse
Uh, reflashing doesn't lock the boot loader. Also, I never said you can't take an OTA with an unlocked bootloader. I said you won't be able to take an OTA if you are rooted, since that messes with the system files.
As you know, you unlock the XT925 via the Moto tools. As for relocking it, I have no idea. I do know with the Nexus 7, flashing a new image doesn't relock it. I have to actually do it via the ADB command, so I believe it's the same thing with the XT925. You get an unlock code from Motorola and you use that to unlock the bootloader and have to use the command to relock it.
Doing a factory reset won't relock it.
Looks like mfastboot check patitions checksum/size with GPT partition (patition_signed)
Sent from my XT925 using Tapatalk
Hi ,
after an day of searching on the web, i found out the Redmi Note 3 Pro Test ROM (AOSP)
Video: https://www.youtube.com/watch?v=xI6lNYEcgS8
Disclaimer:
Do it on your own risk
Steps for flashing:
0 DOWNLOAD ALL
1 UNZIP SYSTEM.ZIP
2 MOVE ALL ON THE SAME FOLDER
3 PUT THE PHONE IN FASTBOOT MODE
4 OPEN "PROMPT COMMANDS" ON THE FOLDER
5 MOVE "8976_fastboot_all_images.bat" ON PROMPT
4 PLUG IN THE PHONE
5 PUSH ENTER
6 WAIT...
7 ENJOY!!
Video: https://www.youtube.com/watch?v=ZI7v8Rv_-5w
What works?
All works fine but missing only the fingerprint voice on settings.
Is multilanguage?
Yes.
Is for normal use?
Yes and not, you need to clean the ROM from some developing apps,
install OpenGapps arm x64 5.1.1 (only pico works).
Can i install custom recovery?
Yes you can. No patch on boot needed.
FINGERPRINT ON SETTINGS IS MISSING.
FASTBOOT ROM:
https://mega.nz/#F!g5kUgILY!60ZoAWdCtY7LPABO4IMpvw
RECOVERY ROM
(for the work thx to @xinkonging ,for the upload thx to @DrWillz ):
https://mega.nz/#!bldGhI7b!PMiMnZCYSwXpdfTouuuE2F9MZPbPUqCNjfuz4FIP3ts
OK, tried it and its pretty good, especially if like me you like a bare bones Android experience that you can customise.
I rooted it, installed gapps, installed the xposed framework, gravity-box, greenify, adaway etc all working pretty well. Changed the DPI settings also as I like less zoomed in experience. Nova launcher is looking pretty well !!!
I will see what the battery life is like overnight and decide if I will keep using it until we get a decent CM12.1 (or ideally CM13).
Only negatives are as OP said are the fingerprint reader cannot be enabled and in a few places it definitely looks like a 'test ROM'. There are some minimal test apps, but faced with a choice of lots of MIUI apps or a few test apps I would rather the few tests app. The camara App is pretty good IMO also.
jeromeof said:
OK, tried it and its pretty good, especially if like me you like a bare bones Android experience that you can customise.
I rooted it, installed gapps, installed the xposed framework, gravity-box, greenify, adaway etc all working pretty well. Changed the DPI settings also as I like less zoomed in experience. Nova launcher is looking pretty well !!!
I will see what the battery life is like overnight and decide if I will keep using it until we get a decent CM12.1 (or ideally CM13).
Only negatives are as OP said are the fingerprint reader cannot be enabled and in a few places it definitely looks like a 'test ROM'. There are some minimal test apps, but faced with a choice of lots of MIUI apps or a few test apps I would rather the few tests app. The camara App is pretty good IMO also.
Click to expand...
Click to collapse
Thx for the feedback )
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Do I need to unlock the bootloader first ?
borg79 said:
Do I need to unlock the bootloader first ?
Click to expand...
Click to collapse
no
Does this work on redmi note 3 pro with 2gb ram and 16gb internal?
thanks for AOSP
asdafdasdaf said:
Does this work on redmi note 3 pro with 2gb ram and 16gb internal?
thanks for AOSP
Click to expand...
Click to collapse
Yep
Overall I've got the following impression of this firmware:
1. Switching from 3G -> 4G is more reliable than on any MIUI rom. First of all I don't loose internet connectivity during the switch (with MIUI I always do) and secondly it founds 4G networks almost instantly, and for MIUI it took minutes.
2. I've tried to flash open gapps stock - it basically made them unusable (was unable to create account), but open gapps mini worked ok for me. Though got a problem with black home screen and very slow phone until I've changed home launcher back to trebuschet.
3. Battery usage also increased in my use cases. I usually got 25% battery/8h, but now it's more like 35%/8h. Though it may be related to the fact that all messangers, etc syncs as often as they want, and with MIUI I never was able to properly receive all push notifications, etc for most of the apps.
4. According to some benchmarks, it seems that this rom is a tiny bit faster. (geekbench results increased by 7% for example). Though that doesn't really matter for me.
5. I usually have more RAM available and apps killed less aggressively.
Civilus said:
Overall I've got the following impression of this firmware:
1. Switching from 3G -> 4G is more reliable than on any MIUI rom. First of all I don't loose internet connectivity during the switch (with MIUI I always do) and secondly it founds 4G networks almost instantly, and for MIUI it took minutes.
2. I've tried to flash open gapps stock - it basically made them unusable (was unable to create account), but open gapps mini worked ok for me. Though got a problem with black home screen and very slow phone until I've changed home launcher back to trebuschet.
3. Battery usage also increased in my use cases. I usually got 25% battery/8h, but now it's more like 35%/8h. Though it may be related to the fact that all messangers, etc syncs as often as they want, and with MIUI I never was able to properly receive all push notifications, etc for most of the apps.
4. According to some benchmarks, it seems that this rom is a tiny bit faster. (geekbench results increased by 7% for example). Though that doesn't really matter for me.
5. I usually have more RAM available and apps killed less aggressively.
Click to expand...
Click to collapse
And camera? http://en.miui.com/thread-251822-1-1.html loook this
Inviato dal mio kenzo utilizzando Tapatalk
Naphtha said:
And camera? http://en.miui.com/thread-251822-1-1.html loook this
Inviato dal mio kenzo utilizzando Tapatalk
Click to expand...
Click to collapse
There is a strange focal distance thing...
Why are the focal distances not the same? I mean, it should be 2.0 on PRO for both MIUI and SD ROMs...
Kenzo and 2.2?? Completely strange...
masseselsev said:
There is a strange focal distance thing...
Why are the focal distances not the same? I mean, it should be 2.0 on PRO for both MIUI and SD ROMs...
Kenzo and 2.2?? Completely strange...
Click to expand...
Click to collapse
2.2 and 2.0 is the iris
Inviato dal mio kenzo utilizzando Tapatalk
I have unlocked the bootloader. Can i flash this rom?
Gửi từ Redmi Note 3 của tôi bằng cách sử dụng Tapatalk
HoaPham98 said:
I have unlocked the bootloader. Can i flash this rom?
Gửi từ Redmi Note 3 của tôi bằng cách sử dụng Tapatalk
Click to expand...
Click to collapse
Yep!! :highfive:
device locked
Hi Bro,
I'm facing device locked issue please help
here is the error from promt
G:\Fastboot ROM>"G:\Fastboot ROM\8976_fastboot_all_images.bat"
error: device not found
for not erase modemst1 and modemst2
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (629 KB)...
OKAY [ 0.020s]
writing 'tz'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'sbl1' (346 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'rpm' (161 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'aboot' (560 KB)...
OKAY [ 0.020s]
writing 'aboot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'hyp' (72 KB)...
OKAY [ 0.000s]
writing 'hyp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'tzbak' (629 KB)...
OKAY [ 0.020s]
writing 'tzbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'sbl1bak' (346 KB)...
OKAY [ 0.010s]
writing 'sbl1bak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'rpmbak' (161 KB)...
OKAY [ 0.010s]
writing 'rpmbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'abootbak' (560 KB)...
OKAY [ 0.020s]
writing 'abootbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'hypbak' (72 KB)...
OKAY [ -0.000s]
writing 'hypbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
erasing 'boot'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'modem' (83542 KB)...
OKAY [ 2.734s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.734s
error: cannot load 'system.img'
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'recovery' (32663 KB)...
OKAY [ 1.061s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'boot' (32015 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.030s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.530s]
writing 'dsp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.540s
target reported max download size of 536870912 bytes
sending 'mdtp' (3684 KB)...
OKAY [ 0.122s]
writing 'mdtp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.122s
erasing 'splash'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'splash' (633 KB)...
OKAY [ 0.030s]
writing 'splash'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
erasing 'DDR'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.020s
rebooting...
finished. total time: -0.000s
G:\Fastboot ROM>
D!nnU said:
Hi Bro,
I'm facing device locked issue please help
here is the error from promt
G:\Fastboot ROM>"G:\Fastboot ROM\8976_fastboot_all_images.bat"
error: device not found
for not erase modemst1 and modemst2
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (629 KB)...
OKAY [ 0.020s]
writing 'tz'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'sbl1' (346 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'rpm' (161 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'aboot' (560 KB)...
OKAY [ 0.020s]
writing 'aboot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'hyp' (72 KB)...
OKAY [ 0.000s]
writing 'hyp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'tzbak' (629 KB)...
OKAY [ 0.020s]
writing 'tzbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'sbl1bak' (346 KB)...
OKAY [ 0.010s]
writing 'sbl1bak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'rpmbak' (161 KB)...
OKAY [ 0.010s]
writing 'rpmbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'abootbak' (560 KB)...
OKAY [ 0.020s]
writing 'abootbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'hypbak' (72 KB)...
OKAY [ -0.000s]
writing 'hypbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
erasing 'boot'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'modem' (83542 KB)...
OKAY [ 2.734s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.734s
error: cannot load 'system.img'
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'recovery' (32663 KB)...
OKAY [ 1.061s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'boot' (32015 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.030s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.530s]
writing 'dsp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.540s
target reported max download size of 536870912 bytes
sending 'mdtp' (3684 KB)...
OKAY [ 0.122s]
writing 'mdtp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.122s
erasing 'splash'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'splash' (633 KB)...
OKAY [ 0.030s]
writing 'splash'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
erasing 'DDR'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.020s
rebooting...
finished. total time: -0.000s
G:\Fastboot ROM>
Click to expand...
Click to collapse
I'm on 7.1.8.0 stable rom
D!nnU said:
I'm on 7.1.8.0 stable rom
Click to expand...
Click to collapse
You need to unlock bootloader before flashing the ROM
Thank you i had submited for bootloader unlock code.
Sent from my Redmi Note 3 using XDA Free mobile app
how to flash this rom on locked bootloader?
how to flash this rom on locked bootloader? and its flashed how to root it and install Twrp?
Unlock bootloader first . is better.
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.
draga said:
Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.
Click to expand...
Click to collapse
I am having the exact same problem. I have to send the phone back for warranty.
I have been trying to use the ALL IN ONE Tool for ZUK and ZUK Tool Beta. Below is the message after which nothing happens. I will post more details and if someone can help me that will be great.
Flashing your Zuk Z1 back to stock. Please wait...
-----------------------------------------------
target reported max download size of 1610612736 bytes
sending 'persist' (4664 KB)...
OKAY [ 0.149s]
writing 'persist'...
OKAY [ 0.090s]
finished. total time: 0.239s
target reported max download size of 1610612736 bytes
sending 'modem' (58545 KB)...
OKAY [ 1.849s]
writing 'modem'...
OKAY [ 0.837s]
finished. total time: 2.686s
target reported max download size of 1610612736 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.012s]
writing 'sbl1'...
OKAY [ 0.010s]
finished. total time: 0.022s
target reported max download size of 1610612736 bytes
sending 'dbi' (17 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
target reported max download size of 1610612736 bytes
sending 'aboot' (414 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.017s]
finished. total time: 0.033s
target reported max download size of 1610612736 bytes
sending 'rpm' (189 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 1610612736 bytes
sending 'splash' (562 KB)...
OKAY [ 0.021s]
writing 'splash'...
OKAY [ 0.013s]
finished. total time: 0.034s
target reported max download size of 1610612736 bytes
sending 'tz' (339 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.026s
target reported max download size of 1610612736 bytes
sending 'boot' (6538 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 0.097s]
finished. total time: 0.305s
target reported max download size of 1610612736 bytes
sending 'recovery' (9168 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.427s
target reported max download size of 1610612736 bytes
erasing 'system'...
OKAY [ 0.086s]
sending 'system' (1546759 KB)...
hi,
i already posted this, 3 days ago in another root thread,
a friend of mine tried to flash his phone after bootloader unlocked ok, but after the flash phone bricked, and ask me for help, now I'm asking as well,
tried:
IMAGE Download Software - IDTML01Ver1001 and CAML00LMAA001063_Board_Software_null_null_Android_ 6.0_EMUI_4.1_05021XEW, it always gives error but it seems to flash the fastboot at least, so the phone from: huawei usb com 1.0 goes to fastboot, so in adb i try:
C:\SDK\platform-tools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (455490 KB)...
OKAY [ 62.178s]
writing 'system' 1/6...
OKAY [ 30.954s]
sending sparse 'system' 2/6 (447920 KB)...
OKAY [ 25.925s]
writing 'system' 2/6...
OKAY [ 30.355s]
sending sparse 'system' 3/6 (460685 KB)...
OKAY [ 20.218s]
writing 'system' 3/6...
OKAY [ 31.334s]
sending sparse 'system' 4/6 (454527 KB)...
OKAY [ 19.641s]
writing 'system' 4/6...
OKAY [ 30.797s]
sending sparse 'system' 5/6 (458441 KB)...
OKAY [ 19.465s]
writing 'system' 5/6...
OKAY [ 30.925s]
sending sparse 'system' 6/6 (20484 KB)...
OKAY [ 0.859s]
writing 'system' 6/6...
OKAY [ 1.406s]
finished. total time: 304.135s
C:\SDK\platform-tools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (253973 KB)...
OKAY [ 10.453s]
writing 'cust'...
OKAY [ 17.159s]
finished. total time: 27.612s
C:\SDK\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 471859200 bytes
sending 'userdata' (44124 KB)...
OKAY [ 1.770s]
writing 'userdata'...
OKAY [ 3.053s]
finished. total time: 4.838s
C:\SDK\platform-tools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23514 KB)...
OKAY [ 1.188s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.531s
C:\SDK\platform-tools>fastboot flash fastboot1 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot1' (2194 KB)...
OKAY [ 0.141s]
writing 'fastboot1'...
FAILED (remote: image verification error)
finished. total time: 0.188s
C:\SDK\platform-tools>fastboot flash fastboot2 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot2' (2194 KB)...
OKAY [ 0.063s]
writing 'fastboot2'...
FAILED (remote: partition does not exist)
finished. total time: 0.078s
C:\SDK\platform-tools>fastboot flash fastboot fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot' (2194 KB)...
OKAY [ 0.062s]
writing 'fastboot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.156s
C:\SDK\platform-tools>fastboot flash cache cache.img
target reported max download size of 471859200 bytes
sending 'cache' (6248 KB)...
OKAY [ 0.312s]
writing 'cache'...
OKAY [ 0.453s]
finished. total time: 0.766s
C:\SDK\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (37966 KB)...
OKAY [ 1.531s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 2.031s
--------------------------------------------------------------------------------------------------
so I'm able to flash successfully
system, cust, cache and userdata
but not able:
recovery, fastboot or boot, and after i fastboot reboot,
again only red and green led and huawei usb com 1.0, to start again
thank you very much indeed, for any guide or help, or maybe a cam-l23 board software to try
Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.
hi
persona78 said:
Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.
Click to expand...
Click to collapse
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention
atv said:
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention
Click to expand...
Click to collapse
Hi!
Can you provid me that files and a litle tut how to use it?
.
On fastboot, can you unlock bootloader?
-
alguien con el board software
Welcome to this unbrick tutorial
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
fastboot devices
Click to expand...
Click to collapse
If a line appears, your phone is correctly connected.
Type the command :
fastboot flash super super.img
Click to expand...
Click to collapse
If it flashed correctly, you should see something like this :
C:\Users\Alex\Desktop\platform-tools>fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/9 (786428 KB) OKAY [ 19.574s]
Writing 'super' OKAY [ 0.013s]
Sending sparse 'super' 2/9 (786428 KB) OKAY [ 19.587s]
Writing 'super' OKAY [ 0.018s]
Sending sparse 'super' 3/9 (786428 KB) OKAY [ 19.609s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 4/9 (698716 KB) OKAY [ 17.393s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 5/9 (765968 KB) OKAY [ 19.103s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 6/9 (763420 KB) OKAY [ 19.074s]
Writing 'super' OKAY [ 0.017s]
Sending sparse 'super' 7/9 (786097 KB) OKAY [ 19.636s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 8/9 (786089 KB) OKAY [ 19.745s]
Writing 'super' OKAY [ 0.029s]
Sending sparse 'super' 9/9 (102406 KB) OKAY [ 2.853s]
Writing 'super' OKAY [ 6.798s]
Finished. Total time: 167.087s
Click to expand...
Click to collapse
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
fastboot reboot fastboot
Click to expand...
Click to collapse
You should reboot into fastbootd.
Then use :
fastboot getvar all
Click to expand...
Click to collapse
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
fastboot set_active b
Click to expand...
Click to collapse
If you're on a slot, or :
fastboot set_active a
Click to expand...
Click to collapse
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Update :
Here are listed all the Super Partitions available for us to fix our Nothing :
1.1.3 EEA : Link
1.1.4 Global : Link
More to come...
Remember that you have to download the Sh4ttered tool version according to the version you are trying to restore.
Again, feel free to share a backup of yours that is not listed here to help other in need
Reserved 2
i have super img latest 1.14 global
ayed78 said:
i have super img latest 1.14 global
Click to expand...
Click to collapse
Can you upload it and share the link?
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
arinc9 said:
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
Click to expand...
Click to collapse
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty for now.
On Xiaomi forum, they solved the issue by flashing the persist partition from a stock fastboot rom, can't tell if it'll work with yours but you Can Always give it a try if you can find a persist partition backup
For the B slot, I think I had errors too, but switching slots fixed mine.
AntoXik72 said:
Can you upload it and share the link?
Click to expand...
Click to collapse
2.98 GB file on MEGA
mega.nz
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
ayed78 said:
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
arinc9 said:
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
Click to expand...
Click to collapse
yes...
ayed78 said:
yes...
Click to expand...
Click to collapse
What's the name of the app?
arinc9 said:
What's the name of the app?
Click to expand...
Click to collapse
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
This one for example.
ayed78 said:
2.98 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
That's perfect, thanks, i'll update the post tonight
AntoXik72 said:
That's perfect, thanks, i'll update the post tonight
Click to expand...
Click to collapse
AntoXik72 said:
Welcome to this unbrick tutorial
This tutorial is EEA only at the moment
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
Unlocked bootloader both classic and critical unlock Link
Sh4ttered Tool (the 1.1.3 update!! for now as I don't have a super partition backup for both 1.1.4 or 1.1.3 Global) Link
1.1.3 super partition (EEA Only at the moment, feel free to share a Global one in the comments) Link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, Run the Download.ps1 with powershell and download the 1.1.3 EEA made by Sh4ttered and downloaded earlier.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
very good man, I'm busy rn so it's sooo good that you wrote this for everyone, thanks!
AntoXik72 said:
Welcome to this unbrick tutorial
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
pankspoo said:
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
Click to expand...
Click to collapse
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
AntoXik72 said:
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
Click to expand...
Click to collapse
Actullly the term you use must be revive phone from bootloop like that.
Any way thanks
mine still stuck at fastboot...nothing tool not update....it detect lower version update on mine 1.1.4 global