Related
Hi there,
I am new to xda and new to Android hacking.
What I wanna ask is, (I guess it's of most newbies concern as well), can we have a 100% backup of our system (stock ROM)? Obviously, it is important because:
If we perform an official (OTA) update to a new Android version. And we don't like it. It is possible to get back to the old original one which we are used to. (not everybody likes new things, and/or not every new thing is good)
If our phones are having some problems. And we have to give it back to the company for a fix. In most cases they will flash a new ROM for us. If we wanna keep using the old one (explained in #1), we have to keep a copy of it by ourselves.
If we want to try new custom ROMs, we may want to switch it back after trying.
Whenever we do any modifications, it's always better to keep a backup/roll-back point. In case anything goes wrong, we have a safeguard.
For the official warranty issue.
Yup I do see there are some official stock ROMs downloads for some particular phones. But those are not really a backup of our original ROMs. And it's always hard to verify if those downloads are the original official releases. And, if those downloads are 100% stock ROMs, this means some guys out there could make it, so what is the way to do so?
Or, how those mobile phone companies do it in their labs?
I have been doing researches on this topic for a few days. Some posts claim that their methods are "backup stock ROM" or "backup before rooting". But after digging into it, they requires rooting and/or flashing CWM. Here comes a few questions:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
In addition, I have found some related pieces. which could be useful to anyone viewing this post, and might be useful for you to solve this (my) question. :fingers-crossed:
* as I'm a new user, I can't post links directly. Please delete the blank spaces in between.
ht tp://www .modaco .com/topic/351269-backup-original-rom/
In reply #5, user C3C0 raised a method of backing up the original stock ROM without root. But it seems he is flashing CWM and that method is only for ZTE Skate.
adb backup tool of Android SDK
At the first sight i came across this approach, I thought it is the official method to do whole system (ROM) backup (WOW - how nice!). But after studying for a few more posts, I think adb backup can only backup app+app_data, and possibly some system settings only. Am I correct? And also, adb backup is only for ICS (Android 4.0), isn't it?
adb backup usage: ht tp://forum.xda-developers .com/showthread.php?t=1420351
(But mentioned in the bottom of #1 the poster is having some issues on using adb backup. Perhaps there are some bugs and not reliable(?)
One more question on adb backup: Can it backup just one app+app_data, and restore just one app+app_data, without affecting other things? If yes, we don't need to root and don't need Titanium Backup (which requires root) for backup app+app_data. Isn't it?
** In case I have said anything or any terms wrongly in this thread, please DO correct me, for helping me and helping others.
P.S. i am using LG Optimus 3D.
Thanks a lot, wholeheartedly,
midnite_
Download CWM recovery img for your device. Start your phone in bootloader mode and connect to PC. Be sure to drivers installed correctly. Type in command line:
fastboot reboot <downloaded img>
Now, the phone will reboot and starting recovery. Make backup, that's all.
Tapatalk 2-vel küldve az én U8655-1-ről
Thanks for your reply R2D2. Would you explain a bit more about the steps? When I flash CWM to my phone, will it change the ROM and that is not a stock ROM anymore? Where should I type the "fastboot reboot <downloaded img>" command?
Thanks,
midnite_
r2d2-andras said:
Download CWM recovery img for your device. Start your phone in bootloader mode and connect to PC. Be sure to drivers installed correctly. Type in command line:
fastboot reboot <downloaded img>
Now, the phone will reboot and starting recovery. Make backup, that's all.
Tapatalk 2-vel küldve az én U8655-1-ről
Click to expand...
Click to collapse
r2d2-andras said:
Download CWM recovery img for your device. Start your phone in bootloader mode and connect to PC. Be sure to drivers installed correctly. Type in command line:
fastboot reboot <downloaded img>
Now, the phone will reboot and starting recovery. Make backup, that's all.
Tapatalk 2-vel küldve az én U8655-1-ről
Click to expand...
Click to collapse
Doesn't this operation require rooting of the phone, or root the phone?
No it doesnt
Sent from my Xperia Neo V using xda app-developers app
no it won't
midnite_ said:
Thanks for your reply R2D2. Would you explain a bit more about the steps? When I flash CWM to my phone, will it change the ROM and that is not a stock ROM anymore? Where should I type the "fastboot reboot <downloaded img>" command?
Thanks,
midnite_
Click to expand...
Click to collapse
If you flash CWM, you will retain your stock rom unless you try to flash custom rom or updating kernel from CWM recovery or from ROM Manager. if you are using samsung android device, you can check your rom in odin mode
Hit thanks if I helped you!
Just install CWM....it won't affect your rom....in CWM choose backup in backup and restore option....it will create the backup of your current rom on sd card
Hit thanks on help
Using XDA premium through A5
My themes - http://forum.xda-developers.com/showthread.php?p=36747522#post36747522
coolprateek.kumar said:
Just install CWM....it won't affect your rom....in CWM choose backup in backup and restore option....it will create the backup of your current rom on sd card
Hit thanks on help
Using XDA premium through A5
My themes - http://forum.xda-developers.com/showthread.php?p=36747522#post36747522
Click to expand...
Click to collapse
One issue: my phone is not listed as being supported by ROM Manager. (HW-T18, a Cat B10)
Is there any other way to get a full ROM backup before rooting, etc.?
needs help with the HW-T18 (cat B10)
nashton said:
One issue: my phone is not listed as being supported by ROM Manager. (HW-T18, a Cat B10)
Is there any other way to get a full ROM backup before rooting, etc.?
Click to expand...
Click to collapse
I'm in the same issue here, looking for a way to backup/extract the stock rom of the HW-T18, cat B10 model, for the purpose of flashing it to other B10's since several of the cat b10's we bought here is without danish and a few has the danish system language.
so i want to take the rom from the b10 with danish and flash to the ones without.
if there is a better way of adding a system language to the phone please let me know (apk maybe ? or flashing an update.zip containing the danish lang) but do remember i'm not a dev i just have ORD.
cwm recovery backup flash new flash back delete cwm recovery servis
Hi Guys,
I understand that cwm recovery will not affect my stock rom. Here is an example what could I need:
I have new galaxy chat with ICS, I will install cwm recovery, create backup of stock (slovak) rom improve rom to some 4.1.2 spain rom and if it won't be good or have some hardware problem I will install again my stock rom but what with cwm recovery. Will it work this way?
Return To Stock Recovery
1. Download StockRecovery.zip
2. Place StockRecovery.zip on your SD Card
3. Boot into CWM Recovery
4. Tap on Install
5. Find StockRecovery.zip file on your SD card.
6. Slide to Flash
7. Reboot System & Enjoy Stock Recovery Again!
or not
thank you
johnoo said:
Hi Guys,
I understand that cwm recovery will not affect my stock rom. Here is an example what could I need:
I have new galaxy chat with ICS, I will install cwm recovery, create backup of stock (slovak) rom improve rom to some 4.1.2 spain rom and if it won't be good or have some hardware problem I will install again my stock rom but what with cwm recovery. Will it work this way?
Return To Stock Recovery
1. Download StockRecovery.zip
2. Place StockRecovery.zip on your SD Card
3. Boot into CWM Recovery
4. Tap on Install
5. Find StockRecovery.zip file on your SD card.
6. Slide to Flash
7. Reboot System & Enjoy Stock Recovery Again!
or not
thank you
Click to expand...
Click to collapse
Why would you need stock recovery back anyway?
send mobile for repairing
If something will crash in future like repro or mic. I will need stock rom and recovery.
johnoo said:
If something will crash in future like repro or mic. I will need stock rom and recovery.
Click to expand...
Click to collapse
Your warranty won't void on custom recovery ....it gets void only on root
Any Android?
coolprateek.kumar said:
Your warranty won't void on custom recovery ....it gets void only on root
Click to expand...
Click to collapse
Will ClockworkMod Recovery install on any android phone? I have a,
HDC Galaxy S4 I9500- Exynos Quad Core 1.7GHz 5.0inch HD IPS Screen Android 4.2.3
in the mail. Will it install no problem? If not, any alternative solution?
bupbup777 said:
Will ClockworkMod Recovery install on any android phone? I have a,
HDC Galaxy S4 I9500- Exynos Quad Core 1.7GHz 5.0inch HD IPS Screen Android 4.2.3
in the mail. Will it install no problem? If not, any alternative solution?
Click to expand...
Click to collapse
Every device has it's own cwm or twrp recovery....google "cwm for .........(your phone)
reply and request
I want to know how to backup full rom because me too have an a103 sc6820 mt6515 android 4.0.1 clone SIII dual sim and trying to root then its bricked. So i have found an another phone which have the same system like for mine and i would try to backup the rom for the new and to restore this to the bricked.
coolprateek.kumar said:
Every device has it's own cwm or twrp recovery....google "cwm for .........(your phone)
Click to expand...
Click to collapse
That's not correct, not every phone has a clockworkmod built for it, my phone is a alcatel authority, and not only is there no clockworkmod, but the newest update.zip, unroots it, and sorceforge only has the the stock update. In any case the manufacturer has put the wrong id's into their usb drivers for it. You can't even use the clockworkmod builder, for it. The only phones that get support, are the more popular models.
does the bootloader need to be unlocked for this to work
reggjoo said:
That's not correct, not every phone has a clockworkmod built for it, my phone is a alcatel authority, and not only is there no clockworkmod, but the newest update.zip, unroots it, and sorceforge only has the the stock update. In any case the manufacturer has put the wrong id's into their usb drivers for it. You can't even use the clockworkmod builder, for it. The only phones that get support, are the more popular models.
Click to expand...
Click to collapse
I meant that every phone who HAS a cwm has it for that particular phone.
Hit thanks for help
r2d2-andras said:
Download CWM recovery img for your device. Start your phone in bootloader mode and connect to PC. Be sure to drivers installed correctly. Type in command line:
fastboot reboot <downloaded img>
Now, the phone will reboot and starting recovery. Make backup, that's all.
Tapatalk 2-vel küldve az én U8655-1-ről
Click to expand...
Click to collapse
How to start phone in bootloader mode and where to type that command?
Hi,
I am new to this forum, but I have solved many of my issues thanks to xda in the past, but now it's time to beg for your direct help.
I have recently rooted my phone, and today I was changing some system fonts (with ROM Toolbox Pro), rebooted the device (app asked me if I wanted to reboot now or wait) and then my phone was stuck in the post-bootanimation screen (gif). I can go to recovery (already tried to delete cache partition and reboot) and to download mode. It is very important for me to save the data on the phone. How can I get back to use my phone without losing my data? I thought I could flash some custom recovery and do some backup (this is only one of my wretched ideas, probably I'm wrong and it isn't possible).
Stock rom (touchwiz). Android 4.3 build MK6. I don't have a custom recovery.
Thank you.
EDIT: Moreover, when I pull out the battery (only way to power off) and put it back in, it automatically boots up (I don't need hold the power button as usual).
Flash philz recovery then use aroma file manager to save data to external sd.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Flash philz recovery then use aroma file manager to save data to external sd.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I'm gonna try it immediately, thank you.
Is there any other way to fix this bootloop or to backup my data without installing Philz (the guide says to have a backup before installing the custom recovery, and I can't create one)?
Thank you.
No, the guide is giving good advice but no use in your case -you should have done a backup before you flashed.
Fanaticism said:
Is there any other way to fix this bootloop or to backup my data without installing Philz (the guide says to have a backup before installing the custom recovery, and I can't create one)?
Thank you.
Click to expand...
Click to collapse
You made to many treats about the same thing.
It looks like you are spamming the treats.
Look at this where I also answered your question.
http://forum.xda-developers.com/showthread.php?t=2738849
Send From A Devil3 - f2fs - Dualboot Jb4.3/cm11 Powered Machine
EDIT on Jan 18,2015
Please see post #9 for a flashable zip of the stock ROM with root that is taken after updated to B148.
Below original post has version B126.
******** ORIGINAL *********
Fix soft-bricked Mate 2 (MT2-L03) phone using TWRP
If you messed up the phone and it came to a state that phone can not boot into android, if you have TWRP installed and have a backup, then you know how to fix that easily.
But if you don't have your own backup, I have upload my system partition so hopefully you can use this to restore your phone. The backup is taken very close to stock, and it is rooted with SuperSU installed.
BTW, there is a "safe mode" boot method, so try that before using twrp recovery:
http://forum.xda-developers.com/asc...ted-amazon-app-store-stuck-boot-loop-t2872628 (post 6 and 7)
Steps to Restore you phone if all other ways failed:1. Your MT2-L03 need have bootloader unlocked, and TWRP recovery installed properly. Even your phone is soft bricked, as long as you can boot into bootloader mode, you can still unlock bootloader and install twrp recovery.Unlock bootloader: http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Install twrp: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t28851442. Boot into twrp recovery and select "System" partition only, and backup it to your external storage (yes, I know your system partition is bad, this step is to create proper twrp backup directory)
3. Download following file to your PC, unzip it.http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip4. Turn off phone and take out your SD card out and plug into PC, then navigate to following directory under the SDCARD: \TWRP\BACKUPS\xxxxx, the xxxxx is a string that different in each phone
5. Copy all the files unzipped from step 3 to above location. overwrite any files with same name.
6. Put back the SDcard to the phone, and boot into TWRP recovery.
7. Choose restore, select the only entry that you did the backup, and select "System" only, perform the restore.
8. Wipe your dalvik cache, cache.
9. Then reboot.
10. If you still have problem, boot into recovery again, and wipe /data parition as well (Factory Reset).Download the MT2-L03 backup here:
http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip
And thanks @dbmj unlock bootloader, @Modding.MyMind build twrp recovery, and @D33PTHAWTE confirmation that this fixed his phone.
Glad you got this posted. This will be very vital to many people down the road. And great work on giving instructions to create a backup for the simplicity of automating the needed directories for usage of the actual shared backup. Thumbs up bro.
@D33PTHAWTE, welcome back
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
superbass311 said:
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
Click to expand...
Click to collapse
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
What button combination are you using? And did you have unlocked bootloader?
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
aragon257 said:
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
Click to expand...
Click to collapse
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
xordos said:
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
Click to expand...
Click to collapse
Thank you so much!
Please try install this zip from recovery:
http://tinyurl.com/q62m68x
MT2L03_B148_Stock_ROM.zip
File Size: 670,252,615 md5: 684bcb2674367814b96eadfa0debe846
Click to expand...
Click to collapse
This is a clean Stock ROM (flashable zip) with Root after upgrade to B148 for MT2L03.
It should only be used for plain carrier unlocked Huawei MT2-L03. Other varies (carrier locked) MT2L03 is un-tested and may brick your phone.
This ROM include /cust, /firmware, /system and /boot partition.
The official B148 update also contains update to SBL1/ABoot/TZ/RPM partition, they are not included due to risk concern.
I didn't fully test this ROM, I just pickup the image from my early backups. I installed it to my already updated phone and boot up fine. So please try it and let me know if you see any problems.
Working great for me! thank you, fixed all my problems.
aragon257 said:
Working great for me! thank you, fixed all my problems.
Click to expand...
Click to collapse
Imei is correct after flashing this?
Moody66 said:
Imei is correct after flashing this?
Click to expand...
Click to collapse
A little confused on what you mean... My sim card works fine in my phone now
aragon257 said:
A little confused on what you mean... My sim card works fine in my phone now
Click to expand...
Click to collapse
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Moody66 said:
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Click to expand...
Click to collapse
Oh I dont think I did, I havent noticed anything. I do have the standard mate and not a consumer cellular mate.
standard ham2 bought from gethuawei
just testing your stock rom zip and everything works fine.
thank you for your effort and time.
after flashing i have no toggles and i dont have LTE so far
thugmafia said:
after flashing i have no toggles and i dont have LTE so far
Click to expand...
Click to collapse
toggle is set in settings -- notif panel, lte pls check apn settings.
xordos said:
toggle is set in settings -- notif panel, lte pls check apn settings.
Click to expand...
Click to collapse
its all gray out meaning i cant turn it on and the APN is set i used to get LTE on tmobile but now it juz 3G H 4G
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
xordos said:
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
Click to expand...
Click to collapse
yes i did i returned to the back up but still no LTE but the speed is the some
and one more thing i notice was the not home screen style to be able to hide the nar bar
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
amn1987 said:
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
Click to expand...
Click to collapse
dirty flash i dunno wat dirty mean here but yea iwas flashing kernel over kernel, also iam using miui offical rom no custom roms! if i need to flash rom zip everytime then its useless, i dont need to wipe my data everytime!
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
khanhlinh said:
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
Click to expand...
Click to collapse
i have nerver whined over this as you can see above, iwas clueless, that is why i asked in the first place, the thing iam bothered about it now is, if i need to (dirty?) flash my rom then i need to reset and delete allmy data again, never expected the need to do that, thx for ur reply and be assure i won't whine since i knew the issue and it's consequences!
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Nasrk said:
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Click to expand...
Click to collapse
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
callmebutcher101 said:
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
Click to expand...
Click to collapse
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Nasrk said:
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Click to expand...
Click to collapse
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Nasrk said:
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Click to expand...
Click to collapse
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
varunsngh786 said:
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Click to expand...
Click to collapse
i will try ur kernel but ur way of publishing kernel name is fishy!!
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
Nasrk said:
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
Click to expand...
Click to collapse
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
crazy_4_and1 said:
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
Click to expand...
Click to collapse
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Nasrk said:
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Click to expand...
Click to collapse
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
crazy_4_and1 said:
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
Click to expand...
Click to collapse
iam waiting for your response about root if it get earsed or not
Nasrk said:
iam waiting for your response about root if it get earsed or not
Click to expand...
Click to collapse
With flashing the stock kernel, it does.
Newer custom kernels apply a patch so magisk stays intact
Stock ones do not.
Hi guys, I have a Samsung A50 of my dad which he recently bought from a store. He works on a financial company and while being there he used
this phone to keep his company data which in some cases are also costumer data which he doesn't afford to lose. On an evening night m mischievous little cousin got his phone
and on the try to open the phone to find games he entered a pattern wrong multiple times which made to lock the phone. I have been searching for things to get this phone unlocked but I don't seem
to find any successful methods.
I get to see a `Lockscreen_FIXER.zip` (from 2014, 8 years ago) but I seem to not be able to flash it. I can successfully boot into recovery mode but can not flash it for some reason, I also put the `.zip` file to the `sd card` or tried `adb` with `adb solidate Lockscreen_FIXER.zip` but either that didn't work out as I clicked "apply update with adb" on recovery mode.
Is there any method to bypass this lockscreen only for once at last?! Thanks so much!!
Hey
Im not an expert i want to point out first
But i anyway want to give my opinion in hopes i can help a little bit
First: this isn't the correct place to post troubles like so, you have a safer bet on posting this on "Question & answers"
Second: If its only data and not apps
You can try properly flashing Twrp because unless the file is no longer supported to get past Android 11 lockscreen
Then its the Twrp you installed
Then connect your phone to your pc
If you have the correct drivers you should be able to see your files in file explorer then copy and paste everything important to your desktop
Then in Twrp just Factory reset so you can use your phone once again
If you cant afford to lose your apps as well
Then you're out of luck on that one buddy
Nashiro10 said:
Hey
Im not an expert i want to point out first
But i anyway want to give my opinion in hopes i can help a little bit
First: this isn't the correct place to post troubles like so, you have a safer bet on posting this on "Question & answers"
Second: If its only data and not apps
You can try properly flashing Twrp because unless the file is no longer supported to get past Android 11 lockscreen
Then its the Twrp you installed
Then connect your phone to your pc
If you have the correct drivers you should be able to see your files in file explorer then copy and paste everything important to your desktop
Then in Twrp just Factory reset so you can use your phone once again
If you cant afford to lose your apps as well
Then you're out of luck on that one buddy
Click to expand...
Click to collapse
Hello @Nashiro10, thanks for your reply. Okay I will ask in the proper place next time.
I see, at this point I care much more about data inside the phone rather than apps. I have a question when it comes to flash ".zip" files. How do I do it? In my recovery mode I got only "Apply Update with adb and sd card" and these two options needs an OTAPACKAGE as an update. Or I can do the flash using Odin while phone is in the "downloading mode"?
Thank you for your time!
thecowmilk said:
Hello @Nashiro10, thanks for your reply. Okay I will ask in the proper place next time.
I see, at this point I care much more about data inside the phone rather than apps. I have a question when it comes to flash ".zip" files. How do I do it? In my recovery mode I got only "Apply Update with adb and sd card" and these two options needs an OTAPACKAGE as an update. Or I can do the flash using Odin while phone is in the "downloading mode"?
Thank you for your time!
Click to expand...
Click to collapse
If you want to flash Zip files then you have to do it through Twrp (Twrp being a custom recovery which you can find on this section) since its easier and you have a higher chance that if something goes wrong with the install you'll have an error code
And It know hows to handle more custom style of Files so its probably the stock recovery you're using doesn't know how yo work with the zip file you're giving it
And as far as im aware Odin only works to install system important files (STOCK SYSTEM, recoveries, Data, internal data, etc)
And also used to flash Twrp via Odin
BUT!
What i forgot to ask is that if you have OEM unlock activated in developer settings?
If you dont then you're out of choices because you wont be able to flash your zip file and you wont be able to flash twrp
Which leaves you to restoring your phone with Odin
Dont know if you can access your phone's data through the stock recovery
But if you can then do what i said in the first post then factory reset the phone through recovery
Nashiro10 said:
If you want to flash Zip files then you have to do it through Twrp (Twrp being a custom recovery which you can find on this section) since its easier and you have a higher chance that if something goes wrong with the install you'll have an error code
And It know hows to handle more custom style of Files so its probably the stock recovery you're using doesn't know how yo work with the zip file you're giving it
And as far as im aware Odin only works to install system important files (STOCK SYSTEM, recoveries, Data, internal data, etc)
And also used to flash Twrp via Odin
BUT!
What i forgot to ask is that if you have OEM unlock activated in developer settings?
If you dont then you're out of choices because you wont be able to flash your zip file and you wont be able to flash twrp
Which leaves you to restoring your phone with Odin
Dont know if you can access your phone's data through the stock recovery
But if you can then do what i said in the first post then factory reset the phone through recovery
Click to expand...
Click to collapse
No, I don't have OEM unlocked because my dad populated the phone with data in a short time and to do the OEM unlocking you have to factory reset the phone and OEM Unlock. Idk either if I can recover data using adb because I cannot connect the phone with adb(unless I select "apply update using adb").
It seems I don't have so much choices and if I'm forced to do the factory reset then I will do it...
I don't know how some phone service stations can unlock the phone... what do they do lol magic? Because I had another phone which couldn't boot and they fixed it.