Related
I was gonna install a new ROM on my HTC Hero, and I forgot to flash the recovery image, after i installed the ROM, all my old stuff were there with the new stuff, and when I tried to use Recovery Flash To Back Up and flash a recovery image but it said BACK UP Failed could not run command.! Please Help Me!!!
Moved to Q&A as not development
So what happens when you power on with HOME + POWER?
ddotpatel said:
So what happens when you power on with HOME + POWER?
Click to expand...
Click to collapse
it goes to the Android System Recovery!
kevin5fan said:
I was gonna install a new ROM on my HTC Hero, and I forgot to flash the recovery image, after i installed the ROM, all my old stuff were there with the new stuff, and when I tried to use Recovery Flash To Back Up and flash a recovery image but it said BACK UP Failed could not run command.! Please Help Me!!!
Click to expand...
Click to collapse
OK. So first of all, calm down. Second of all, can you explain clearly what you did (step by step), and what isn't working, and what you are trying to do.
I can't make head nor tail of your story, but it sounds like you installed a new ROM and didn't wipe the data, and now can't do something to do with recovery.
Have you read up on flashing etc before doing this?
pulser_g2 said:
OK. So first of all, calm down. Second of all, can you explain clearly what you did (step by step), and what isn't working, and what you are trying to do.
I can't make head nor tail of your story, but it sounds like you installed a new ROM and didn't wipe the data, and now can't do something to do with recovery.
Have you read up on flashing etc before doing this?
Click to expand...
Click to collapse
OK I Was Gonna Install A New Mod On My Old VillianROM (HTC Hero)
Second I forgot to flash the recovery image b4 installing the ROM
I installed the ROM and then all my programs on my old ROM were there with the new ones.(is that normal?)
I tried to reinstall the ROM by flashing the Recovery Image This Time but Recovery Flash had an error. Cannot Back Up!
So IDK if what i did is right or Worng Please Help!
kevin5fan said:
OK I Was Gonna Install A New Mod On My Old VillianROM (HTC Hero)
Second I forgot to flash the recovery image b4 installing the ROM
I installed the ROM and then all my programs on my old ROM were there with the new ones.(is that normal?)
I tried to reinstall the ROM by flashing the Recovery Image This Time but Recovery Flash had an error. Cannot Back Up!
So IDK if what i did is right or Worng Please Help!
Click to expand...
Click to collapse
Your apps will remain unless you did a wipe.
And there is no need to flash recovery each time. This is fixable though. If you are able to flash VR12, it will install a recovery image for you automatically.
Do you have adb set up, as if so, this is pretty easy to do?
What writting comes up?
Edit... I'll leave you in Pulsers capable hands
Sent from my HTC Hero using XDA App
pulser_g2 said:
Your apps will remain unless you did a wipe.
And there is no need to flash recovery each time. This is fixable though. If you are able to flash VR12, it will install a recovery image for you automatically.
Do you have adb set up, as if so, this is pretty easy to do?
Click to expand...
Click to collapse
I did a factory wipe and IDK what a ADP set up is? I want to install another ROM called Madaco Custom Rom or w.e yea so can u add me on msn pm me your address
kevin5fan said:
I did a factory wipe and IDK what a ADP set up is? I want to install another ROM called Madaco Custom Rom or w.e yea so can u add me on msn pm me your address
Click to expand...
Click to collapse
Don't use MSN, I'm afraid, but if you go to www.villainrom.co.uk and go to "Follow us" and then click IRC, you can come to the instant chat and explain what's happened there, and you'll get it sorted It's like a group MSN
I need some help.
I recently purchased a ATT GS2 I have it rooted and recently flashed Unnamed v1.0.1. My issue is every time i want to flash a new rom its pain in my butt. Like now, I am thinking of putting CM7 on and playing a round a while with that but I know I will not be able to just download the rom and put on sd card, boot into recovery, do a data wipe, then flash rom. It always gives me an message that the install has aborted. Unverified signature or some crap like that. So what I have to do to flash a rom is the following. Run odin and flash back to stock with root. Then run odin again and flash the clock work mod recovery kernal SGH-I777_ClockworkMod-Recovery_X.X.X.X.tar. Finally at that point i am able to flash a new rom from my recovery menu. I love the galaxy series and I do remember on the original having to revert to stock using Odin one click before flashing a new rom. Is it going to be the same with the SGS2? I had an att inspire 4g for a while and it was super easy. Download rom, boot recovery, wipe data, flash rom, DONE>
If anyone can help me out with a suggestion of what I may be doing wrong I would appreciate it so much. If you need more details please let me know.
Chris...
re: Flash CM7
taterdog2 said:
I need some help.
I recently purchased a ATT GS2 I have it rooted and recently flashed Unnamed v1.0.1. My issue is every time i want to flash a new rom its pain in my butt. Like now, I am thinking of putting CM7 on and playing a round a while with that but I know I will not be able to just download the rom and put on sd card, boot into recovery, do a data wipe, then flash rom. It always gives me an message that the install has aborted. Unverified signature or some crap like that. So what I have to do to flash a rom is the following. Run odin and flash back to stock with root. Then run odin again and flash the clock work mod recovery kernal SGH-I777_ClockworkMod-Recovery_X.X.X.X.tar. Finally at that point i am able to flash a new rom from my recovery menu. I love the galaxy series and I do remember on the original having to revert to stock using Odin one click before flashing a new rom. Is it going to be the same with the SGS2? I had an att inspire 4g for a while and it was super easy. Download rom, boot recovery, wipe data, flash rom, DONE>
If anyone can help me out with a suggestion of what I may be doing wrong I would appreciate it so much. If you need more details please let me know.
Chris...
Click to expand...
Click to collapse
If you follow these instructions to a "TEE" you will be able to flash CM7
without erroring out.
#1: delete the unnamed 1.01 and cyanogenmod zipfiles from your sdcard
(if they exist)
#2: download a fresh copy of CyanogenMod zipfile
#3: download a fresh copy of unnamed v1.01 zipfile
#4: copy both the newly downloaded zipfiles to your internal sdcard
#5: flash the unnamed v1.01 rom using cwm (not rom manager)
#6: after flashing before reboot select "wipe data/factory reset" in CWM
#7: reboot the phone into a useable state
#8: press power button and select "reboot recovery"
#9: flash the cyanogenmod zipfile (it will not fully boot yet)
#10: wait about 30 seconds after you see black screen with Samsung text
#11: remove and replace battery and reboot into CWM recovery
#12: select "wipe data/factory reset"
#13: flash the cyanogenmod rom once again
#14: select reboot in CWM
#15: in less than 2 minutes the phone will be ready to use!!!!
NOTE: if the above method fails you will need to start from scratch
"ultimate unbrick"
Good luck and I will be waiting for you to click the big THANKS button
I had a few problems with that, I had to download the CM file several times before I got a good copy. you should probably try running an MD5 on the zip file.
Excuse me for being a newbie but I am having a hard time understanding the difference between Rom manager and clock work mod recovery. I always thought they were the same. Can u give me a quick run down of the difference. When you say flash using CWM recovery do you mean from off position boot into revcovery mode and then flash? Not selecting flash rom from Rom Manager, right?
Here is where I am confused. At any given time I should be able to download a new ROM zip file. Place it on my internal sd card. Reboot into rocovery mode, wipe data, flash using CWM Recovery and be done. I have never been able to do it like that with my SGS2 unlike I was able to on my HTC inspire 4g. Whats the difference?
Sent from my SAMSUNG-SGH-I777 using xda premium
taterdog2 said:
Excuse me for being a newbie but I am having a hard time understanding the difference between Rom manager and clock work mod recovery. I always thought they were the same. Can u give me a quick run down of the difference. When you say flash using CWM recovery do you mean from off position boot into revcovery mode and then flash? Not selecting flash rom from Rom Manager, right?
Here is where I am confused. At any given time I should be able to download a new ROM zip file. Place it on my internal sd card. Reboot into rocovery mode, wipe data, flash using CWM Recovery and be done. I have never been able to do it like that with my SGS2 unlike I was able to on my HTC inspire 4g. Whats the difference?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Forget about Rom Manager please.. Rom Manager and CWM are
two entirely different things.
Just follow the instructions to a "TEE" and note that I have not mentioned
anything about rom manager in my previous post with all the step by step
instructions........ For now, forget that rom manager even exists.
taterdog2 said:
Excuse me for being a newbie but I am having a hard time understanding the difference between Rom manager and clock work mod recovery. I always thought they were the same. Can u give me a quick run down of the difference. When you say flash using CWM recovery do you mean from off position boot into revcovery mode and then flash? Not selecting flash rom from Rom Manager, right?
Here is where I am confused. At any given time I should be able to download a new ROM zip file. Place it on my internal sd card. Reboot into rocovery mode, wipe data, flash using CWM Recovery and be done. I have never been able to do it like that with my SGS2 unlike I was able to on my HTC inspire 4g. Whats the difference?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
ROM Manager seems to insist on using its own CWM implementation, which has been broken on every device I've ever owned. For example, everyone who used ROM Manager on this device had signature verification problems, and anyone who used ROM Manager's CWM on the Infuse wound up softbricking their device if Voodo Lagfix was enabled, forcing them to Odin/Heimdall back to stock.
In-kernel CWM is the most tested and most reliable way to use CWM.
Three finger salute is the only way to be sure when you're trying to enter CWM.
So would u suggest uninstalling rom manager all together?
Sent from my SAMSUNG-SGH-I777 using xda premium
Do fresh install
Sent from my Xperia.X8 using Tapatalk
Hello.
I'd like to give MIUI a try, but, of course, I'd also like to switch back to my stock ROM if things go wrong or if I don't like MIUI.
How can I backup my entire phone (rooting, Recovery Mode capability and other on-power key-combination-activated features etc etc) and 100% failsafe restore it at any time?
Thanks in advance.
Rooted stock = do a nandroid (CWM) backup which is essentially an 'image' of the phone at the time you make the backup. Try MIUI; don't like it ? Restore the nandroid you took of your rooted stock setup. Sorted (You will need to ensure you backup the contents of your external SD card separately if you have one).
Be careful you don't 'overthink' this, it's really very simple both ways (backup/restore).
My Recovery Mode doesn't have a backup option
MistahBungle said:
Rooted stock = do a nandroid (CWM) backup which is essentially an 'image' of the phone at the time you make the backup. Try MIUI; don't like it ? Restore the nandroid you took of your rooted stock setup. Sorted (You will need to ensure you backup the contents of your external SD card separately if you have one).
Be careful you don't 'overthink' this, it's really very simple both ways (backup/restore).
Click to expand...
Click to collapse
Thanks for prompt response. I took a look at current Recovery Mode menu and it doesn't include a backup/restore option like in http://forum.xda-developers.com/wiki/ClockworkMod_Recovery. It shows only the above:
Code:
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
test redbend fota[FS]
-----------------------------------
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ZVV
Successfully applied multi-CSC.
I've already downloaded Recovery from clockworkmod.com but didn't do anything with it yet.
Sorry if it has already been detailed in another thread, but I didn't find it and I don't know how to make such nandroid backup.
Thanks.
OBackup
I've just downloaded OBackup app from Play store and am doing my backup.
My question is: after I flash MIUI, what are the tools/steps I'll need to restore my backup?
Thank you very much.
That's the stock Android recovery.
OK...
What you need to do is not install CWM separately. That will only persist until you reboot & is designed to allow you to flash whatever rom/kernel you want which will have it's own version of CWM baked into the kernel.
That backup program you're using; no idea as I've never used it.
What I recommend you do is find a custom kernel you like (actually, any custom kernel will do given you're going to flash Miui) which will have CWM. Flash that into your stock setup, then make a nandroid (CWM) backup of your stock setup so you can go back to it if you don't like Miui/whatever else you try (If you restored this & wanted to go back completely stock/unrooted/etc, all you'd need to do is flash a stock kernel). This is what you asked for in your OP. I warned you not to start overcomplicating things, and this is exactly what you're doing.
The kernel supplied with Miui should have CWM, so if you find you don't like it, you should be able to simply restore the backup you made of your stock setup in CWRecovery.
I also very strongly recommend you learn 'the basics' as you seem to be lacking in this knowledge. Flashing stuff/etc without knowing these things leads to busted phones. Read the tutorials/guides stickied near the top of the General section; there's a wealth of information in those.
Hi!
I've a similiar problem with my GT-i9100!
Can I do a restore of my stock ROM (that have android 4.1) if I've install a costum ROM like RootBox that have a different version of android (4.2.2)?
Can my phone brick because there are a differents kernel?
Tnx you all! ^^
Rox666 said:
Hi!
I've a similiar problem with my GT-i9100!
Can I do a restore of my stock ROM (that have android 4.1) if I've install a costum ROM like RootBox that have a different version of android (4.2.2)?
Can my phone brick because there are a differents kernel?
Tnx you all! ^^
Click to expand...
Click to collapse
No it won't brick.
sadekmefti said:
No it won't brick.
Click to expand...
Click to collapse
Hi and tnx for reply!
I've try to do a restore of my sock rom from recovery but it's says to me that there is an error on md5 check sum...
I've install the RootBox ROM in my gt-i9100...but I can't come back to sock from recovery because the stock kernel dosen't work with RootBox's Kernel...
so I've to use odin to flash the stock firmware.......at the origin, my idea didn't comprised use odin because of download mode counter (so that why I did a backup!)...but now I don't have any other way...!
...what a sad story.. XD
Rox666 said:
Hi and tnx for reply!
I've try to do a restore of my sock rom from recovery but it's says to me that there is an error on md5 check sum...
I've install the RootBox ROM in my gt-i9100...but I can't come back to sock from recovery because the stock kernel dosen't work with RootBox's Kernel...
so I've to use odin to flash the stock firmware.......at the origin, my idea didn't comprised use odin because of download mode counter (so that why I did a backup!)...but now I don't have any other way...!
...what a sad story.. XD
Click to expand...
Click to collapse
You can't restore your backup because of a different MD5 SUM which means that your backup has been corrupted.
Flashing a stock ROM or Kernel via ODIN will not increase your flash counter.
Flash NeatROM Lite, this is the best ROM ever, it like stock with additional things.
Sent from GT-I9100 using Tapatalk 4
sadekmefti said:
You can't restore your backmyf a different MD5 SUM which means that your backup has been corrupted.
Flashing a stock ROM or Kernel via ODIN will not increase your flash counter.
Flash NeatROM Lite, this is the best ROM ever, it like stock with additional things.
Sent from GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
DIO *******************
I will cry...... :'( so the recovery hadn't save well my backup..I read about similar error and I hoped that was thet...
My last chance is use Odin..
Only a question: can I flash the stock rom from recovery renaming the file .tar.md5 in .zip?
Tnx for you for the counsel! I will try thet rom after solving this problem! For now I have changed rom and I'm using MIUI and it works really well!!
Rox666 said:
DIO *******************
I will cry...... :'( so the recovery hadn't save well my backup..I read about similar error and I hoped that was thet...
My last chance is use Odin..
Only a question: can I flash the stock rom from recovery renaming the file .tar.md5 in .zip?
Tnx for you for the counsel! I will try thet rom after solving this problem! For now I have changed rom and I'm using MIUI and it works really well!!
Click to expand...
Click to collapse
You can't flash a stock ROM from recovery by changing .tar.md5 to .zip .
You want to change ROM to Stock, use Mobile Odin to flash a Stock ROM or Flash NeatROM v4.8 Lite.
sadekmefti said:
You can't flash a stock ROM from recovery by changing .tar.md5 to .zip .
You want to change ROM to Stock, use Mobile Odin to flash a Stock ROM or Flash NeatROM v4.8 Lite.
Click to expand...
Click to collapse
Tnx you! I understand what I have to do! I'll try your rom today
Tnx again!!!
Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file
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.