Hello,
As the title suggests, I'm looking for a way to completely backup my stock device without root.
This would include firmware and stock recoveries, basically system files - as I'm not really too terribly worried with saving personal data.
I've searched through various threads but I think I'm in one of those "in-over-my-head" situations, so let me explain why I haven't just flashed a custom recovery and made a nandroid backup.
My device is the C-Spire Note 5, SM-N920R7, running 5.1.1 - recognized by Smart Switch with no updates available.
I received this device in the mail today - because I somehow managed to brick my old device with the "custom binary blocked" FRP.
There is no stock firmware available for download to flash in Odin, and it was impossible to boot the device in regular or recovery mode, leaving me with Download mode.
In order to root my old device, I had to unlock the OEM in Developer Settings and flash the "Beastmode" kernel via Odin:
http://forum.xda-developers.com/spr...rnel-beastmode-modified-stock-1-0-sm-t3196174
Then, I flashed a TWRP recovery and used it to install SuperSU - and voila! I had rooted my device.
Fast forward a few months... My battery died one day and it somehow triggered the FRP lock - with only Download mode available and no C-Spire stock firmware to flash.
Naturally, I want to root my device again, but first I want to create a complete backup of my device that would be flashable in Odin even with the FRP lock on.
So ladies and gentlemen, any help or advice would be appreciated.
I would of course, upload my firmware publicly so that anyone else using this device doesn't brick their phone like I did.
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
theophile2 said:
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
Click to expand...
Click to collapse
The only way I've seen involves capturing temporary files during an update through Kies or Smart Switch.
Being on C-Spire, that probably will not ever happen.
Maybe C-Spire will get it together and push out 6.0.1 OTA like the rest of the world - as well as actually providing an alternate (non-OTA) download method.
Apparently some guy on the C-Spire Dev forums paid for a ROM on a Chinese site that works with our phones - which would serve as a nice backup if he would ever upload it.
I asked him to - and apparently he contacted the admins asking for a way to upload the file to the forums.
After they responded to him, he must have never uploaded the file.
[SOLVED]
My device: OnePlus5 A5000
First of all I want to mention that I am kind of a novice on rooting so please do not go hard on me, mistakes happen. So I was running the lastest version of Android on my phone (Version 5.1.7) and decided to root my phone and use Magisk. So I unlocked my bootloader and I was going to work with TWRP. But I did a terrible mistake and wiped the system while experimenting. I know this is a very stupid mistake but it sadly happened. So my phone is basicly empty and has no OS running everytime with a black screen whenever I enter the system . The only thing I am able of doing is transfering files from my PC to my phone and using TWRP. I downloaded the original and latest OS version from OnePlus' site and moved it inside my phone. I then went on to install it via TWRP but I faced "Error 7". I did a research on that and I found out that it happens because it detects if it is a compatible ROM with the whole "assert" thing in META-INF in the "updater-script". I went on to unzip it and edit it with NotePad++to remove "assert" but "assert" was no where to be found since it was the original version. I then went on to try installing the lineage version for OnePLus 5 not knowing if it was going to work and it turned out to not work at all. I also want to mention that whenever I tried removing the "assert" from the lineage version I got an error of "Invalid zip file format!". Finally I want to mention that in order for me to view the files I worked by repairing the partition and converting it to FAT and exFAT(I did NOT convert it back to EXT4 yet). In case I am missing something or there is a way of solving it please let me know, I would really appreciate it! Also if you do not mind be as decscriptive as possible since I am a novice and I do not know everything like other individuals. I will though make a deep research on every single comment I get, I am not waiting for an easy solution on such a subject. I hope I can fix my phone with your help in the near future. Thanks in advance!
Files that I have downloaded (if necessary):
1)ADB Files
2)Original version of latest OnePlus 5 Update (5.1.7) (.zip file)
3)Lineage ROM for One Plus 5 (15.1-20181127-nightly-cheeseburger-signed)
4)TWRP (3.2.3-0-cheeseburger)
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
This is weird and boggles my mind. I updated to the latest update for my pixel 6, Everything went fine.
When I try to flash the patched boot.img the phone just bootloops and I have to reflash the stock boot.img. I feel like I've tried everything flashed the patch img to both slots tried reinstalling the update, tried flashing stock boot to both slots and retrying the process again.
Everything is normal i.e. bootloader unlocked, that Verity thing dealt with. I just can't get my head around it. I tried following that post with the guide but still the same result.
Any help would be great, it's not about achieving root anymore tbh, I just want to beat it as I've been at it for hours and it's annoyed me now haha.
Thanks in advanced
This has to be a joke, right?
Okay, I give up.
What's the punch line?
I wish it was mate maybe I've been trying for ages now that the obvious is escaping me. Scared to know the answer now haha.
@Newrooter22 Ask in the guide you looked at. They know all. Yep, it's under "guides".
will you try following through adb ?
- boot to bootloader
- from fastboot try to boot with the patched img yuo made with command : fastboot boot patched -image-you-made.img
- see if your phone boot.
- if not, get a copy of patched boot img with your img version on this forum.
i used to have same issue, turned out patched img wasn't good.
hope will help.
Thanks everyone for the replies, I've posted the situation under the "guides" as I'm starting to think it's something wrong with the patched boot.img that I'm getting from Magisk.
@mailistman I thought that could've worked as well hopefully just booting the patched img but never worked so hopefully if someone on the other thread has a copy, the second thing you mentioned might work.
Thanks again
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Try MSM Tool
@Princess007 I've got the newest ROMt2Box .. if you need it.
@ScarletWizard
Firmware - https://mega.nz/file/EDwAAAIB#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
romtoolboxpro - https://mega.nz/file/tTBSGagI#nYvCwk_prTrkM2E3VGk7Sh9qqw5NCn1PZhc73oxrl6U
Samsung Touch sensitivity is very Awesome..
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
I can pull a rooted super and should have those already actually but if your system is not already magisk patched then you will not be able to boot. I have lost the stock July somewhere in all my backups but I'm willing to pull the boot and super for you if you need it. It is already RW system
Princess007 said:
I was trying to bypass Google FRP lock on this phone, after having no success, I went online looking and downloaded Rom2Box to try to bypass frp.. When I was trying to get the program to discover my device, nothing happened, it never discovered it, but while it was attempting to discover it, my phone had a black screen with a red dot and 2 smaller white dots moving around the red dot in a circle pattern while bumping off of each other.. I don't know what it means, I never saw it before.. .. Now it won't turn on, or show that it's being charged so I think this program bricked my phone..?
I guess I'd like to give Odin a shot at fixing it for me.. But I don't know Odin, I never messed with phone's like this.. Is, this my best or only option?
Click to expand...
Click to collapse
this usually happens because some component of your device is not loading due to either mismatched security pacthes, some system partition has been altered and cannot load or one of many other reasons. i have a device that works perfectly fine and boots with this oneplus logo rather than the tmobile splash that it used to boot with. for me this was caused by mixing components from different systems. i had to flash matching radios, boot, and system, vbmeta disabled to get the device to function with mismatched partitions but the only thing thats still not working is the tmobile splash, which i dont miss and have no desire to try to fix that so i have been running this device in that state for months with 0 problems other than when one of my mods breaks the system and i just have to undo whatever i modified and im back to a functioning state. thedot with 2 dots bouncing around it is fine so long as everything else works, just means that something in vendor is probably different than what it expects so that part doesnt load or some other partition..... disabling verity and verification can usually get me booting again if this happens whether everything else works and is important to you is your decision to fix it or not. going back stock should fix it all. best thing to do if ur gonna mod is make sure u pull backups of EVERY single partition on the device so you have matching images. would suck to lose efs partitions because they are unique and the only people that can get those back for you is the manufacturer
i recommend using partitions backup & restore from playstore. its free and you can pull all of your partitions for restoring in the future. i recommend setting the options to save as raw(.img) rather than archives and then after it pulls all of them, compress them all into one archive. this will save you from having to extract each image from 100 different archives if you need to do a full restore in the future. best of luck and thanks for your contribution
Glitchmob2640 said:
Where can i find the firmware for oneplus nord n20 5g T-Mobile, current build number is GN2200_11_A.07?
Trying to extract boot.img and patch with Magisk
Click to expand...
Click to collapse
theres alread an a.07 boot image posted thats already been patched. best to pull your own but if your gonna use one thats not pulled directly from your device you may as well just use the one thats already patched. i have attached the magisk-delta patched boot image that i use on my july device GN2200_11_A.07
magisk-delta patched boot image that i use on my july device GN2200_11_A.07
T-Mobile MSM tool
File folder on MEGA
mega.nz
DrScrad said:
T-Mobile MSM tool
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
can someone post a link for the msmtool for the N20 from T-Mobile, this link is dead
Is there an MSM tool for the Metro version of the Nord N20 5G? I can't seem to find one anywhere.
ScarletWizard said:
Download MSM Download Tool: Unbrick any OnePlus Device [Video]
From this guide, you could download the MSM Download Tool for every OnePlus device and then use it to unbrick your OnePlus device.
www.droidwin.com
Click to expand...
Click to collapse
That one ain't gonna work.. you've gotta download the newest tool..
NewVersion_2.exe
drive.google.com
Does anyone have a link to just the msm tool without the rom?
I've got the rom, but no working tool, and I don't have the internet to download a whole other rom