Hi all I’m kinda a newb to this scene but I’d like you get some info and possibly some help rooting it and building my own custom firmware.
I’d like to know exactly how to back the entire system up so I can try to possibly deplor it on an emulator etc. I’m interested in learning everything there is to know about android as well as how the systems are setup and how they run. I’ve done some modding in the past PSP Nook kindle fire etc but I’ve never gotten fully involved with the android os as I’d like to. Other then building and running automation scripts for software testing i lack the full knowledge on the os. I’m looking to learn as I said and possibly help build a root method and cfw for the onn 100003562. Thanks for any information and help in advanced.
Anyone out there?
Looking for some direction here. If anyone can point me in the right direction for this subject that would be great
Ok fellas lol I know I’m a newb but I would like some keen insight.
Is there any info out there for these Walmart tablets the 100005362? I was able to pull the bin directory with adb pull. Some how I bricked the first one I was attempting to modify so I went out and bought a new one as well as a 8 inch for my daughter. They are only 28 bucks Walmart special right now they call them gen 2 so I’m not sure if that is helpful at all. Anyway. I was thinking since what I was able to extract has some SeLinux folders with some type of commands, is there any way to modify them and inject them back in and some how initiate theme to run an a su installer? Or some kind of modification or even trick the damn thing to dump the images needed to root with magisk. I can’t seem to dump the .img files to make a stock backup nor can I seem to find where the ota update is downloaded and stored for install. I’ve been working on this and reading all of NSA software information about SeLinux and how it can controls pretty much most of the system above the uid. Now is it a possibility that one could modify the SeLinux files from bin and execute them in a way to grant the uid user superpermissions over everything including the SELinux. The more I’ve read the more suspicious I get on the whole NSA subject of SeLinux anyway and wonder why that type of govnmt made software is in public civilian hands but that’s a whole other subject. Anyway can somebody please advise me as to what can be done so I can back this up and modify for su. I don’t care what I have to do I want this thing as my test subject to build my own android rom. I’d like to build something a bit more secure and in a state that is anonymous to the web 100%. Like run the system under a Tor setup etc. I’m kinda one of those people who thinks everyone is watching and listening so I just prefer to build this myself or with like minded individuals. Again please any advise or any knowledge partaining to these devices and android 10 that can help me would be greatly appreciated thanks again.
backups
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.
will160628 said:
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.
Click to expand...
Click to collapse
thanks but i need the MT8768WA chipset.
Ok I'm finally able to report I have successfully Unbricked the Walmart ONN 100003562.
Using various bits of information scattered throughout the Walmart ONN general threads section so If anyone else runs into this issue i have the fix.
Step 1
Download both the FULL FACTORY firmware and the Update firmware from this awesome guys google drive. here's the link https://drive.google.com/drive/folde...5k?usp=sharing.
Starting with the Full stock flash all available .img .bin into the proper locations via fastboot.
when flashing the vbmetas use "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" you should get a result like this if done properly.
"Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8192 KB) OKAY [ 0.190s]
Writing 'vbmeta' OKAY [ 0.127s]
Finished. Total time: 0.379s"
also take note that there are a few .bin and .img locations that aren't the same location as the name. I used the scatter file in wwrmtk 2.51 to get the proper locations however I will copy and paste all my commands and results here.
after you rewrite all .img .bin you have to start over with the update .img and .bin.
here are the commands and results I used to successfully unbrick the device.
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 0.782s]
Writing 'boot' OKAY [ 0.503s]
Finished. Total time: 1.293s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash cache cache.img
Sending 'cache' (8832 KB) OKAY [ 0.202s]
Writing 'cache' OKAY [ 0.192s]
Finished. Total time: 0.414s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.197s]
Writing 'dtbo' OKAY [ 0.129s]
Finished. Total time: 0.335s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash lk lk.bin
Sending 'lk' (1024 KB) OKAY [ 0.035s]
Writing 'lk' OKAY [ 0.018s]
Finished. Total time: 0.066s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash lk2 lk2.bin
Sending 'lk2' (1024 KB) OKAY [ 0.034s]
Writing 'lk2' OKAY [ 0.018s]
Finished. Total time: 0.068s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash logo logo.bin
Sending 'logo' (8192 KB) OKAY [ 0.199s]
Writing 'logo' OKAY [ 0.128s]
Finished. Total time: 0.343s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash preloader preloader_mid1035_mq.bin
Sending 'preloader' (233 KB) OKAY [ 0.016s]
Writing 'preloader' OKAY [ 0.158s]
Finished. Total time: 0.192s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 0.792s]
Writing 'recovery' OKAY [ 0.498s]
Finished. Total time: 1.298s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash spmfw spmfw.img
Sending 'spmfw' (1024 KB) OKAY [ 0.033s]
Writing 'spmfw' OKAY [ 0.018s]
Finished. Total time: 0.060s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/23 (129916 KB) OKAY [ 3.023s]
Writing 'super' OKAY [ 2.051s]
Sending sparse 'super' 2/23 (131068 KB) OKAY [ 3.065s]
Writing 'super' OKAY [ 3.812s]
Sending sparse 'super' 3/23 (131069 KB) OKAY [ 3.121s]
Writing 'super' OKAY [ 5.405s]
Sending sparse 'super' 4/23 (131068 KB) OKAY [ 3.074s]
Writing 'super' OKAY [ 5.470s]
Sending sparse 'super' 5/23 (131068 KB) OKAY [ 3.084s]
Writing 'super' OKAY [ 7.373s]
Sending sparse 'super' 6/23 (130593 KB) OKAY [ 3.139s]
Writing 'super' OKAY [ 8.220s]
Sending sparse 'super' 7/23 (131068 KB) OKAY [ 3.000s]
Writing 'super' OKAY [ 5.070s]
Sending sparse 'super' 8/23 (128774 KB) OKAY [ 3.143s]
Writing 'super' OKAY [ 8.107s]
Sending sparse 'super' 9/23 (129432 KB) OKAY [ 3.080s]
Writing 'super' OKAY [ 6.766s]
Sending sparse 'super' 10/23 (127084 KB) OKAY [ 2.943s]
Writing 'super' OKAY [ 5.197s]
Sending sparse 'super' 11/23 (130712 KB) OKAY [ 3.060s]
Writing 'super' OKAY [ 5.269s]
Sending sparse 'super' 12/23 (130612 KB) OKAY [ 3.102s]
Writing 'super' OKAY [ 6.239s]
Sending sparse 'super' 13/23 (131068 KB) OKAY [ 3.151s]
Writing 'super' OKAY [ 5.530s]
Sending sparse 'super' 14/23 (130648 KB) OKAY [ 3.141s]
Writing 'super' OKAY [ 5.893s]
Sending sparse 'super' 15/23 (130936 KB) OKAY [ 3.109s]
Writing 'super' OKAY [ 5.011s]
Sending sparse 'super' 16/23 (130720 KB) OKAY [ 3.106s]
Writing 'super' OKAY [ 4.640s]
Sending sparse 'super' 17/23 (128867 KB) OKAY [ 3.163s]
Writing 'super' OKAY [ 11.114s]
Sending sparse 'super' 18/23 (130500 KB) OKAY [ 3.038s]
Writing 'super' OKAY [ 6.164s]
Sending sparse 'super' 19/23 (131020 KB) OKAY [ 3.061s]
Writing 'super' OKAY [ 4.301s]
Sending sparse 'super' 20/23 (130632 KB) OKAY [ 3.072s]
Writing 'super' OKAY [ 3.810s]
Sending sparse 'super' 21/23 (131069 KB) OKAY [ 3.073s]
Writing 'super' OKAY [ 8.454s]
Sending sparse 'super' 22/23 (129608 KB) OKAY [ 3.061s]
Writing 'super' OKAY [ 2.942s]
Sending sparse 'super' 23/23 (107620 KB) OKAY [ 2.573s]
Writing 'super' OKAY [107.503s]
Finished. Total time: 328.236s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash scp1 tinysys-scp1.bin
Sending 'scp1' (1024 KB) OKAY [ 0.033s]
Writing 'scp1' OKAY [ 0.018s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash scp2 tinysys-scp2.bin
Sending 'scp2' (1024 KB) OKAY [ 0.033s]
Writing 'scp2' OKAY [ 0.018s]
Finished. Total time: 0.064s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8192 KB) OKAY [ 0.190s]
Writing 'vbmeta' OKAY [ 0.127s]
Finished. Total time: 0.379s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (8192 KB) OKAY [ 0.199s]
Writing 'vbmeta_system' OKAY [ 0.128s]
Finished. Total time: 0.340s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Sending 'vbmeta_vendor' (8192 KB) OKAY [ 0.195s]
Writing 'vbmeta_vendor' OKAY [ 0.127s]
Finished. Total time: 0.334s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm 1 sspm.img
fastboot: error: cannot load '1': No such file or directory
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm_1 sspm.img
Sending 'sspm_1' (1024 KB) OKAY [ 0.033s]
Writing 'sspm_1' OKAY [ 0.018s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm_2 sspm.img
Sending 'sspm_2' (1024 KB) OKAY [ 0.034s]
Writing 'sspm_2' OKAY [ 0.019s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash tee1 trustzone1.bin
Sending 'tee1' (5120 KB) OKAY [ 0.122s]
Writing 'tee1' OKAY [ 0.088s]
Finished. Total time: 0.218s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash tee2 trustzone2.bin
Sending 'tee2' (11264 KB) OKAY [ 0.265s]
Writing 'tee2' OKAY [ 0.167s]
Finished. Total time: 0.449s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash userdata userdata.img
Sending sparse 'userdata' 1/2 (131068 KB) OKAY [ 2.963s]
Writing 'userdata' OKAY [ 2.007s]
Sending sparse 'userdata' 2/2 (7840 KB) OKAY [ 0.246s]
Writing 'userdata' OKAY [ 0.985s]
NOTE rebooting takes quite awhile its not stuck on the boot logo walk away for a bit if need be. mine took about 5 minutes on the boot logo before it fully loaded.
I have successfully Rooted the Walmart ONN 100003562 preloaded with android 10 SAR.
I had to Flash both a Magisked patched recovery.img and a magisk patched boot.img as well as re flash the vbmeta using the disable varity and verify commands.
Step one:
Download files here.
Step 2
Install magisk_manager8.0.apk and update
adb install command
adb install magisk_manager_8.0.apk
Either patch the files yourself using magisk manager or use the ones provided here. I have provided both patched and unpatched .img as well as vbmeta.img
step 3
Flash .img's
boot flash command.
fastboot flash boot magisk_patched_boot.img
recovery flash command.
fastboot flash recovery magisk_patched_recover.img
vbmeta flash command.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
NOTE .img names may differ adjust accordingly.
reboot command.
fastboot reboot
YOU ARE NOW ROOTED WITH MAGISK!!!!!!!
HAVE AN AWESOME DAY AND DONT FORGET TO DONATE link to paypal in bio.
Here's a screenshot of magisk with successful root.
will160628 said:
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.
Click to expand...
Click to collapse
I was able to successfully Unbrick from a full on hard brick and also was successful in obtaining root access. Now a new update downloaded on the device so I am going to attempt updating an re rooting if needed. read through. Thanks again so much for having and sharing the backed up. will be rooting the 28 dollar 8 inch next.
Can I get a mod to rename this thread to "How to successful unbrick and root Walmart ONN 10.1 100003562"
Sp tool
KaosKreationz said:
thanks but i need the MT8768WA chipset.
Click to expand...
Click to collapse
Sorry about that. I should have mentioned most 876x... processors seem to be basically a rebrand of the 6765 with minor updates mostly coming in the clock speed area. Using the 6765 listing in sp tool & wwr tends to work fine for devices using the "updated" processors. That said there is a scatter in all my backups that can be loaded in sp tool to do all the heavy lifting instead of using fastboot. Using sp tool will be a lot easier than fastboot for the majority of people that will hit these forums from google. There is a main backup thread all about that which covers sp tool for all onn tablets. At least nothing changed on that front with the latest gen walmart devices.
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
Now all that said, I don't think anyone has done a full write-up for unbricking with fastboot for the new partitioning. I'm hoping this gets stickied for people that can't get sp tool to detect their devices. I believe your process should be the same on the 8” pro tablets released just before the 10.1. It should be usefull for quite a few people that get either device this holiday season.
I did start the upload for the 10-22 update but apparently my gdrive laptop crashed and I just had to restart the upload. Wish drive resumed uploads like it does downloads. Hoping I'll get it posted some time this week but no telling. I'm too lazy to look through and just upload the changes.
I'll try your root method once I get to my desktop and post back to verify for other people.
Oh before I forget, at that price the 8" you mention sounds like one of the earlier walmart tablets that runs 9. I believe magisk detects those so you shouldn't have to manually disable verity and just the boot.img is enough to root. Not sure how new you are to the walmart tablet line so thought I'd mention it just in case.
Verified
Just ran through and disabling verity was the one thing I didn't try before but it worked. I've done the same procedure on other devices but it didn't even occur to me. My attention span is worse than a 2 year old at this point so I can't say I tried all that hard before. Anyway thanks for the write up and good job. Jrummy's root browser pro gives write access to ./ Directories so this seems to be a proper root method.
Did you have any issues with the ota update after you rooted? I've heard talk of errors on devices running 10. Either the update won't work or it bricks the device. Just wondering if thats something people need to be on the lookout for.
Btw you wrote recover.img instead of recovery.img in your write up. I wouldn't have noticed but I copy/paste a lot. Did I mention I'm lazy?
will160628 said:
Sorry about that. I should have mentioned most 876x... processors seem to be basically a rebrand of the 6765 with minor updates mostly coming in the clock speed area. Using the 6765 listing in sp tool & wwr tends to work fine for devices using the "updated" processors. That said there is a scatter in all my backups that can be loaded in sp tool to do all the heavy lifting instead of using fastboot. Using sp tool will be a lot easier than fastboot for the majority of people that will hit these forums from google. There is a main backup thread all about that which covers sp tool for all onn tablets. At least nothing changed on that front with the latest gen walmart devices.
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
Now all that said, I don't think anyone has done a full write-up for unbricking with fastboot for the new partitioning. I'm hoping this gets stickied for people that can't get sp tool to detect their devices. I believe your process should be the same on the 8” pro tablets released just before the 10.1. It should be usefull for quite a few people that get either device this holiday season.
I did start the upload for the 10-22 update but apparently my gdrive laptop crashed and I just had to restart the upload. Wish drive resumed uploads like it does downloads. Hoping I'll get it posted some time this week but no telling. I'm too lazy to look through and just upload the changes.
I'll try your root method once I get to my desktop and post back to verify for other people.
Oh before I forget, at that price the 8" you mention sounds like one of the earlier walmart tablets that runs 9. I believe magisk detects those so you shouldn't have to manually disable verity and just the boot.img is enough to root. Not sure how new you are to the walmart tablet line so thought I'd mention it just in case.
Click to expand...
Click to collapse
No surprisingly enough the 8 inch or 7.2 inch rather is a newer one with android 10 preinstalled they only had one show case filled with them as a black friday special i honestly shoulda grabbed a bunch and modded and handed em out for xmas. anyway its the MT8162B chipset.
KaosKreationz said:
No surprisingly enough the 8 inch or 7.2 inch rather is a newer one with android 10 preinstalled they only had one show case filled with them as a black friday special i honestly shoulda grabbed a bunch and modded and handed em out for xmas. anyway its the MT8162B chipset.
Click to expand...
Click to collapse
Okay. By that processor and OS it sounds like the 7" surf pro that went on sale a few days ago. I think there's a thread about rooting those somewhere on xda. I haven't had the chance to check that model out yet so I don't know much beyond what I've read. I have heard they can be a bit sluggish though. I think they actually run android 10 go which doesn't seem to get much love from google. I have seen some talk about roming them since the hardware should be more capable than it lets on. If it were the 8" pro with the mt8768 similar to the 10.1 I'd be interested in getting one at that price. I'm looking into one of those for my mom this Christmas but they continually run $99. I don't think she'd tolerate anything with less than 2gb of ram for long considering she just bought an 8" previous gen and already wants to trash it. Some of her games are memory hogs.
onn 7 inch pro gen 2 100015685 models.
step 1
Download files from the google drive link.
https://drive.google.com/drive/folders/14DUU4uyRdKO2lUdkjOH1zETdAqjOWQun?usp=sharing
Step 2
Open the containing folder.
Step 3
Right shift + right click and select powershell
Step 4
Run these commands in order.
fastboot commands.
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Step 5
Wait till it boots and todahhhh you are now rooted with Magisk.
enjoy and dont forget to donate paypal email is on my info.
KaosKreationz said:
onn 7 inch pro gen 2 100015685 models.
step 1
Download files from the google drive link.
https://drive.google.com/drive/folders/14DUU4uyRdKO2lUdkjOH1zETdAqjOWQun?usp=sharing
Step 2
Open the containing folder.
Step 3
Right shift + right click and select powershell
Step 4
Run these commands in order.
fastboot commands.
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Step 5
Wait till it boots and todahhhh you are now rooted with Magisk.
enjoy and dont forget to donate paypal email is on my info.
Click to expand...
Click to collapse
hi, do you know if this will work with the 100015685-A model? thanks
jason7246 said:
hi, do you know if this will work with the 100015685-A model? thanks
Click to expand...
Click to collapse
Yes it will there is a thread on here regarding the a model it’s labeled 7 inch gen 2. I happenned to run see it the other day when I was researching. I used there scatter file to pull my software being that I can’t seem to get the wwr software working on my windows 10. Every time I try to create a scatter it results with only the bootloader found.
KaosKreationz said:
Yes it will there is a thread on here regarding the a model it’s labeled 7 inch gen 2. I happenned to run see it the other day when I was researching. I used there scatter file to pull my software being that I can’t seem to get the wwr software working on my windows 10. Every time I try to create a scatter it results with only the bootloader found.
Click to expand...
Click to collapse
if u mean preloader(probably me being confused), then ya im having the same issue, im trying some of these files now to see if i can get mine back to working, i had tryed some files for the -E version a few days ago, the boot.img being the major one, to find it bootlooping my -A model, so fingers crossed.
jason7246 said:
hi, do you know if this will work with the 100015685-A model? thanks
Click to expand...
Click to collapse
jason7246 said:
if u mean preloader(probably me being confused), then ya im having the same issue, im trying some of these files now to see if i can get mine back to working, i had tryed some files for the -E version a few days ago, the boot.img being the major one, to find it bootlooping my -A model, so fingers crossed.
Click to expand...
Click to collapse
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Use the vbmeta and use this command u should be able to get out of bootloop on the other device.
@KaosKreationz Wow 28$ for this tablet model : 100003562? Thats a steal. My local WM has it for 129 + taxes. Even refurb units on Ebay are like 75$.
Also thanks for your efforts on this thread.
Before buying, I came here looking to see if anyone has a custom ROM for this tablet.
Related
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot-bootlo
ader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloa
der bootloader-grouper-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.408s]
writing 'bootloader'...
OKAY [ 1.267s]
finished. total time: 1.679s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -w update ima
ge-nakasi-jop40d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015###***##f80a
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.017s]
sending 'boot' (4942 KB)...
OKAY [ 1.058s]
writing 'boot'...
OKAY [ 0.332s]
sending 'recovery' (5444 KB)...
OKAY [ 1.144s]
writing 'recovery'...
OKAY [ 0.335s]
erasing 'system'...
OKAY [ 0.125s]
sending 'system' (477136 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 107.320s
Please some one help.... I already deleted boot,cache,recovery,system, user data... Now My device not stating... it just open till bootloader
Usually you would boot into the new bootloader after having flashed a new one in place, and then continue (your steps #1 and #2 are reversed).
But, I'm not sure that is the cause of the problem here, and I wouldn't keep flashing the bootloader over and over when no errors are given, as a bootloader flash is the single most dangerous thing you can do. Just make sure you restart the tab.
Whenever you see a communications failure you should try a different cable or a different USB port on your PC. Communication failures are most likely with the system image simply because it is the largest - there are more opportunity for errors. FWIW, poor quality or damaged cables are the most likely cause of USB data transfer problems.
It could be some other problem with the tab, but those are two easy things to try.
good luck
Try using the flash-all.bat in the factory image.
Actually the only difference is in the wait of 10 seconds between reboot and -w update.
Give it i try.:fingers-crossed:
bye
Problem Solved... Problem with my usb Port....
Thanks bftb0
hirenvasani said:
Problem Solved... Problem with my usb Port....
Thanks bftb0
Click to expand...
Click to collapse
Good news! Glad something I said helped.
Please edit your thread title to include the token "[SOLVED]" - that might help others or let them skip over.
enjoy your tablet - it is a fantastic little device.
I have a sudden and strange problem with my Nexus 10 bought about two months ago. The ROM is stock Android 4.4.2 (automatic OTA update from original 4.2), not rooted. It seems that its internal storage became read-only. First, the tablet started to reboot every 10 minutes or so and tried to update some of the installed applications after every restart. I have tried to uninstall them and found that after reboot they are back and that writing to internal storage does not work. Installing, uninstalling and updating applications, saving application settings, deleting and copying files, both using a file manager on the tablet and through MTP - nothing works. After restart everything is back to the state before writing. Resetting to factory defaults from the Settings menu and from recovery (factory reset/data wipe) also does not work (in the latter case the tablet freezes on a screen showing that formatting /data is in progress). Any ideas? At least, I would like to delete some personal documents from the tablet before sending it for repair or replacement.
I'm in the same position. Was running CM 11 nightlies... running fine for weeks. Starting last week it's stuck in this mode i.e. every time I do a reload, it's as if it doesn't remember anything that was previously done (like app updates). Any attempt to do a factory reset, copy a new image etc. just gets ignored - device just reboots and goes back to it's previous state.
I would suggest using fastboot to wipe all partitions, this would involve unlocking bootloader. Then I would flash the factory image through fastboot as well
(Just Google : android factory images)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the suggestion. So I tried following:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system -w
> fastboot erase userdata
> fastboot flash bootloader bootloader-manta-mantalj12.img
> fastboot reboot-bootloader
> fastboot -w update image-mantaray-jdq39.zip
Had to use 4.2.2 factory image since that's the version of bootloader I had. All the commands seems to complete OK.. at the end, device reboots... but CM 11 loads again as if nothing had been changed! It's as if the erase commands have no affect.
So the output in cmd/terminal says successful for each command but at the end nothing happened? This is very strange to me... Can you try again and post the input/output from terminal?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So the output in cmd/terminal says successful for each command but at the end nothing happened? This is very strange to me... Can you try again and post the input/output from terminal?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried with "fastboot flash" steps too... but same issue. After reboot, goes right back to CM.
S:\android\wugs\data>fastboot devices
R32CB03R8KW fastboot
S:\android\wugs\data>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.095s]
finished. total time: 0.259s
S:\android\wugs\data>fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.020s]
erasing 'userdata'...
OKAY [ 0.019s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14273216512
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3484672
Block groups: 107
Reserved block group size: 855
Created filesystem with 11/871408 inodes and 96018/3484672 blocks
sending 'userdata' (137478 KB)...
writing 'userdata'...
OKAY [ 19.662s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.465s]
finished. total time: 21.186s
S:\android\wugs\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
S:\android\wugs\data>fastboot erase boot
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.019s
S:\android\wugs\data>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.019s]
sending 'system' (522703 KB)...
OKAY [ 65.509s]
writing 'system'...
OKAY [ 4.250s]
finished. total time: 69.778s
S:\android\wugs\data>fastboot flash boot boot.img
sending 'boot' (4608 KB)...
OKAY [ 0.580s]
writing 'boot'...
OKAY [ 0.018s]
finished. total time: 0.598s
S:\android\wugs\data>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (10372 KB)...
OKAY [ 1.301s]
writing 'cache'...
OKAY [ 0.088s]
finished. total time: 1.411s
S:\android\wugs\data>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 0.019s]
sending 'userdata' (137478 KB)...
OKAY [ 17.234s]
writing 'userdata'...
OKAY [ 0.588s]
finished. total time: 17.842s
S:\android\wugs\data>fastboot flash recovery recovery-clockwork-touch-6.0.2.3-ma
nta.img
sending 'recovery' (6296 KB)...
OKAY [ 0.792s]
writing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.812s
S:\android\wugs\data>fastboot reboot
rebooting...
finished. total time: 0.001s
S:\android\wugs\data>
...this I have never encountered. I assume these are all manually entered commands and the wugs is just the name of the folder the factory images are in correct? As in you aren't using a toolkit to do this? If not then it appears you are doing everything correct and I can not see why it isn't erasing or flashing the new images
The only other suggestions I have would be try a different PC, maybe a Linux live disc or something, or try another USB cable. But its unlikely to help but nonetheless worth a shot.
Or if you can find the proper images to be used in Odin or hiemdal you could try going into download mode and see if a factory flash this way will help. Note I haven't used download mode on my n10 before but many times on other Sammy devices
Try any of the above and if I can think of more I'll post back
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yep.. indeed it is very strange. The wugs directory is just where adb/fastboot are located (I'm using the adb/fastboot that wugs creates vs. downloading the sdk)... and the factory image is unzipped in the same dir. All commands are being manually entered. Using a windows 8 laptop with OEM USB cable.
I haven't used odin or hiemdal before... but will search and see how.
I've had this N10 since it launched... and it's had some sort of custom rom ever since... never had a problem. I switched to CM11 back in december, and it has been fine... even doing updates. But now it's stuck in this state. I can copy a new rom to the device, but when I reboot and go into recovery and try to install it, the rom file has been removed. Every time it reboots it goes and re-downloads app updates that came in the past week or two... installs them without issue.. and functions fairly normally. But if a reboot is triggered, it goes back to its old state. I also have to re-enable Developer mode and USB debugging every time after reboot.
Anyway, I'll keep digging.
well being this stroked my curiosity i figured i would spend a few minuets looking into this, and it appears others have indeed had this issue. most commonly with samsung devices.
I feel there must be a fix of sorts out there, but i dont have time to dig more, but i thought i would through up a few links that summarize what i found
http://forum.xda-developers.com/showthread.php?t=2627703&page=4
http://forum.xda-developers.com/showthread.php?t=1704646
http://androidforums.com/incredible...internal-phone-storage-becomes-read-only.html
http://forum.xda-developers.com/showthread.php?t=2193499
there were many more i looked at but these were just the tabs i have opened.
Ill dig some more tonight but it what is being said is true, your internal sd is failing you. if you still have a warranty im not sure if they will except it as there is a custom rom/recovery on there but many have said RMA works fine even with this on a nexus. otherwise it may be possible to do a full brick with dd commands if you want to send it back completely bricked... any way hope you find some way of getting working again!
Useful links... I'll go through them. Hopefully something there will work.
My warranty is out though.. it's over a year since I bought it
Maybe of interest for you with root
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
This is also an issue on some galaxy nexus'. It is a fried EMMC chip im afraid. The internal storage is ruined and needs to be replaced. I didnt know this was possible on the Nexus 10 and maybe im wrong but it has all the signs..
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks for all the links guys... I think this appears to be some sort of hardware issue. I'm reluctant to tinker further in case I make it worse. Right now it is usable as long as I don't try to update the rom or run certain apps. I'll keep stumbling along until the N10 replacement (N11?) comes out... gives me an excuse to buy it
Hi,
For more it looks like a dead end (even fastboot didn't work!), I think you should try one more thing, I'm highly skeptical that it will work, but now I guess every little bit will be something.
First reboot to your recovery. Then plug it to your PC and go to your and folder, now type:
Code:
adb shell
su
touch /sdcard/null
cd /dev/block/platform/dw_mmc.0/by-name/
dd if=/sdcard/null of=system
dd if=/sdcard/null of=userdata
dd if=/sdcard/null of=boot
If the command went trough rightly, it will format your system, kernel (boot) and data. If this doesn't work I'm out of ideas, I was going to suggest things that were already suggested here, so it only left me with this. I just want to tell you that if something goes wrong and it stops working, I'm not responsible for it. If the command works, then it's all about flashing a new ROM.
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
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
Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s
Have you tried to change USB ports/ cables?
Bouncer5 said:
Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s
Click to expand...
Click to collapse
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.
ariesgodofwar said:
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.
Click to expand...
Click to collapse
Yea it is quite large, I have tried flashing the system.img on its own, It also eventually times out. I have also tried different system.img files. I have tried different USB cables, different USB ports, heck last night I even tried a different computer and OS! Still always fails.
At this point the only thing I was able to do with my phone was get Ubuntu Touch on it so it is just slightly more useful than a paperweight.
With Ubuntu Touch I have managed to get Cyanogenmod.zip onto the phone reflash the recovery and install the .zip I am now back on android, I cannot however get back to a stock image.
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