Related
Hi, I'm running a stock P500 and I'm a bit disappointed with its performance. I'm looking for a ROM which is feature-complete, i.e. no missing features such as Bluetooth calling, etc. and minimal to no deviation from the stock Android UI. Any suggestions?
use megatron ROM it is the closest in my opinion and has very good performance but i would suggest trying the other ROMs that have gingerbread like miks cm7 they are not missing much and what they are missing you can get back
dislplin01 said:
use megatron ROM it is the closest in my opinion and has very good performance but i would suggest trying the other ROMs that have gingerbread like miks cm7 they are not missing much and what they are missing you can get back
Click to expand...
Click to collapse
I just visited the Megatron ROM thread http://forum.xda-developers.com/showthread.php?t=870640. Why is noejn suggesting that people use void instead?
two roms.
OpenOptimus by Ciaox
OR
Nessy Rom
If you want a nice and long battery life
flash Franco kernel
take note* For 2.2 flash with CFS
Do as what you are told on their page.. I or the dev will not be responsilble.
Ok, so this is all kinda new to me so I wanted to make sure that I have the basics covered:
1. I need to root my phone. I'm running Android 2.2.2 so I guess that means I need to use gingerbreak. It's an .apk file that I need to install on my phone and then I run it to gain root access. Are there any command line actions needed for gingerbreak?
2. After rooting, I need to install a ROM manager such as CWM or AmonRA. If I'm not mistaken, the program itself will install the custom recovery, right? And how do I boot into that recovery mode?
3. After booting into recovery mode, I need to do a nandroid (?) backup of my current ROM, right? And the backup of my stock ROM is restored through the same custom recovery, yes? Would restoring the stock ROM unroot my phone and remove the custom recovery as well?
3. After backing up, I need to flash the custom ROM which should be saved as a .zip file on my SD card. Do I need to worry about the kernel as well?
Sorry if I have a lot of questions.
DigitalAnalog said:
Ok, so this is all kinda new to me so I wanted to make sure that I have the basics covered:
1. I need to root my phone. I'm running Android 2.2.2 so I guess that means I need to use gingerbreak. It's an .apk file that I need to install on my phone and then I run it to gain root access. Are there any command line actions needed for gingerbreak?
2. After rooting, I need to install a ROM manager such as CWM or AmonRA. If I'm not mistaken, the program itself will install the custom recovery, right? And how do I boot into that recovery mode?
3. After booting into recovery mode, I need to do a nandroid (?) backup of my current ROM, right? And the backup of my stock ROM is restored through the same custom recovery, yes? Would restoring the stock ROM unroot my phone and remove the custom recovery as well?
3. After backing up, I need to flash the custom ROM which should be saved as a .zip file on my SD card. Do I need to worry about the kernel as well?
Sorry if I have a lot of questions.
Click to expand...
Click to collapse
1. Install it, open it and select "Root"
2. No, the root program won't install the recovery. You need to do that; the easiest way is by Rom Manager (download from market); boot in recovery: turn off the phone and start it by pressing at the same time: home + vol down + power key and release at lg logo to enter custom recovery or just select boot into recovery from ROM Manager
3. Yes, make a backup and to restore it just select "restore" from the same place. No, you will restore the backup you just made so your phone will be exactly the way it was when you created the backup (including apps, settings etc)
4. Yes, you will enter "install zip from sdcard -> choose zip". Don't forget to wipe cache, dalvik cache, data/factory reset and format /system before you flash the rom. Other kernels are not mandatory but highly recommended (the differences are big) - also wipe just cache & dalvik cache before flashing the kernel
22VIN said:
1. Install it, open it and select "Root"
2. No, the root program won't install the recovery. You need to do that; the easiest way is by Rom Manager (download from market); boot in recovery: turn off the phone and start it by pressing at the same time: home + vol down + power key and release at lg logo to enter custom recovery or just select boot into recovery from ROM Manager
3. Yes, make a backup and to restore it just select "restore" from the same place. No, you will restore the backup you just made so your phone will be exactly the way it was when you created the backup (including apps, settings etc)
4. Yes, you will enter "install zip from sdcard -> choose zip". Don't forget to wipe cache, dalvik cache, data/factory reset and format /system before you flash the rom. Other kernels are not mandatory but highly recommended (the differences are big) - also wipe just cache & dalvik cache before flashing the kernel
Click to expand...
Click to collapse
Thank you. What are the precautions that I need to take to make sure I don't brick my phone? Also, what are the chances of my phone getting damaged and at which point during those steps is it most likely to happen?
DigitalAnalog said:
Thank you. What are the precautions that I need to take to make sure I don't brick my phone? Also, what are the chances of my phone getting damaged and at which point during those steps is it most likely to happen?
Click to expand...
Click to collapse
The chaces of bricking the phone are very small.
What can happen:
- some people reported that their phone got bricked when they installed the recovery with ROM Manager (this can be easily undone, there is a thread about this). Never happened to me, everything went smooth & fast. There are other ways to install a recovery if you don't want to use ROM Manager, just check the Development section.
- the ROM you choose can be uncompatible with your recovery (all the new roms are compatible with clockworkmod recovery (this is the recovery you will install via ROM Manager); there are some older roms which are compatible only with AmonRA)
- after flashing a custom kernel the phone might not boot (no panic, just flash the rom again or restore backup); check if your ROM is compatible with the kernel you choose
Flashing with recovery is very safe because everything can be easily undone. As long as the phone boots into recovery there is no panic.
But most of the time if your cautious and do everything as told your fine~~
hahaha.. Enjoy..
Rom manager give Cwm.. So no hassle..
22VIN said:
The chaces of bricking the phone are very small.
What can happen:
- some people reported that their phone got bricked when they installed the recovery with ROM Manager (this can be easily undone, there is a thread about this). Never happened to me, everything went smooth & fast. There are other ways to install a recovery if you don't want to use ROM Manager, just check the Development section.
- the ROM you choose can be uncompatible with your recovery (all the new roms are compatible with clockworkmod recovery (this is the recovery you will install via ROM Manager); there are some older roms which are compatible only with AmonRA)
- after flashing a custom kernel the phone might not boot (no panic, just flash the rom again or restore backup); check if your ROM is compatible with the kernel you choose
Flashing with recovery is very safe because everything can be easily undone. As long as the phone boots into recovery there is no panic.
Click to expand...
Click to collapse
Thank you. When I backup my stock ROM, the output is a .zip file which is no different from how the custom ROM zips are packaged, right? Also, would you know if Gingerbreak supports unrooting? I appreciate all of your help and I'm quite excited to root my Optimus One.
DigitalAnalog said:
Thank you. When I backup my stock ROM, the output is a .zip file which is no different from how the custom ROM zips are packaged, right? Also, would you know if Gingerbreak supports unrooting? I appreciate all of your help and I'm quite excited to root my Optimus One.
Click to expand...
Click to collapse
Your backup will appear as a folder on the root of your sdcard (/clockworkmod/folder with the date of your backup). You need to save that folder on your pc just to be safe.
Yes, gingerbread supports unrooting
No problem Just have fun )
22VIN said:
Your backup will appear as a folder on the root of your sdcard (/clockworkmod/folder with the date of your backup). You need to save that folder on your pc just to be safe.
Yes, gingerbread supports unrooting
No problem Just have fun )
Click to expand...
Click to collapse
Thanks! Is it safe to do all the flashing/work from within ROM Manager? It just seems too easy to be true.
Also, is there a 'compatibility matrix' of some sort for the different ROMS and kernels available? Since I want GB, I'm planning on flashing Mik's CM7 mod. Is Franco's kernel compatible with that?
DigitalAnalog said:
Thanks! Is it safe to do all the flashing/work from within ROM Manager? It just seems too easy to be true.
Also, is there a 'compatibility matrix' of some sort for the different ROMS and kernels available? Since I want GB, I'm planning on flashing Mik's CM7 mod. Is Franco's kernel compatible with that?
Click to expand...
Click to collapse
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
If you are interested in a froyo stock rom with just the root and a performant kernel like franco's one, I could cook a rom for you...
22VIN said:
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
Click to expand...
Click to collapse
But now rom manager doesn't let us download any Rom(Only for premium) anymore except for Gapps.
download at the Dev page at XDA is the best. cause it shows all the steps required
22VIN said:
I say it's pretty safe. As I said, worked like a charm for me.
mik_os's rom is flashable via clockworkmod recovery and compatible with franco.kernel (bfs version).
Click to expand...
Click to collapse
Thanks. I was able to gain root as well as install CWM. I'm currently backing up my current ROM. Now I'm not sure if this is a stupid question but when I install a custom ROM, wouldn't that overwrite CWM? How do I go back to recovery then, say, to reflash my original ROM?
Flashing a rom through recovery does not overwrite the recovery.
And you can always boot into recovery by pressing and holding home+volume down+power when the phone is off till the recovery menu boots.
Sent from my LG-P500 using XDA App
I'm just about to flash my first custom ROM. It's all quite clear up to this point. I'm not so sure about the kernel though. Is it all done via the Recovery console? Which options/commands should I take? And what about the ZRAM initializer?
DigitalAnalog said:
I'm just about to flash my first custom ROM. It's all quite clear up to this point. I'm not so sure about the kernel though. Is it all done via the Recovery console? Which options/commands should I take? And what about the ZRAM initializer?
Click to expand...
Click to collapse
For flashing rom : wipe everything, partition SD card only of you want to use a2sd or data2sd (check ciaox's REPO thread for more info about these two) and then choose flash from zip. If you are wiping battery stats then do it when you are fully charged.
For flashing kernel : wipe cache,dalvik cache and battery stats. No need to partition SD card.
EDIT: yes you need to flash zram initialiser. Keep in mind to flash Cfs version for froyo and bfs version for gb roms. Also always reboot between multiple flashes.
Sent from my LG-P500 using XDA App
mihir287 said:
For flashing rom : wipe everything, partition SD card only of you want to use a2sd or data2sd (check ciaox's REPO thread for more info about these two) and then choose flash from zip. If you are wiping battery stats then do it when you are fully charged.
For flashing kernel : wipe cache,dalvik cache and battery stats. No need to partition SD card.
EDIT: yes you need to flash zram initialiser. Keep in mind to flash Cfs version for froyo and bfs version for gb roms. Also always reboot between multiple flashes.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Just go to the zip rom. example franco.kernel.v17. click on it. and choose rom manager if prompt and just wipe dalvik cache..
WIPE BATT STAT ONLY WHEN YOU CHARGED AT 100%
Zram is actually up to individual.
just reminding him. Hope im not a pest to you.
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!!!
So I finally tried some AOSP, but missed my camera immensely so I went to switch back to my backup that I made in TWRP.
Unfortunately AOSP roms use CWM recovery and it won't recognize my TWRP so I've tried to redo the Dual Recovery method but since I no longer have stock kernel it fails.
Now I've also tried to use fastboot to flash a boot.img which I thought was a stock kernel....but obviously I was wrong or it didn't want to work.
Either way as of now I'm using FlashTool to flash stock image, then root, then install DualRecovery again and THEN restore backup.
Does anyone know where I went wrong and hopefully provide a faster solution in case I go back to trying ASOP again? Maybe backup in CWM next time?
Now I do have to flashable DualRecovery.zip that I did try in CWM but it didn't work either, I'm guessing since I didn't have stock kernel...
Thanks in advanced. Why didn't Sony just have a dedicated recovery partition!
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Mr.R™ said:
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Click to expand...
Click to collapse
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
ZPaul2Fresh8 said:
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
Click to expand...
Click to collapse
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Envious_Data said:
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Click to expand...
Click to collapse
Well I did try to use the dual recovery but it didn't work. It says it is only for stock kernel so I didn't expect it to, but I had to try...
@ZPaul2Fresh8
EDIT: DON'T INSTALL IF YOU STILL WANT TO USE CM!!!
It won't boot the system of cm if you flashed the twrp img, just flash it if you want to go to a backup!
"
It was very easy for me, at the end i had a twrp 2.7.0.0 in my cm11'd Z2, you need pc, and usb cable, and fastboot and adb drivers, lol its way easier than flashing .ftf, go to http://forum.xda-developers.com/showthread.php?t=2764971 and download the zip and extract it, follow this tout: http://forum.xda-developers.com/showthread.php?t=1752270 and you will be all good...
I have a few questions to ask.
Is it possible to get your stock rom from your android device?
Are there any apps that can do this?
I can't find my stock rom anywhere. If it is possible that i get my rom can I use it to downgrade a similar device to this current stock rom i have?
Arvin1989 said:
I have a few questions to ask.
Is it possible to get your stock rom from your android device?
Are there any apps that can do this?
I can't find my stock rom anywhere. If it is possible that i get my rom can I use it to downgrade a similar device to this current stock rom i have?
Click to expand...
Click to collapse
⇛It is possible to get your stock rom after rooting...
⇛None of the apps i know can do this...without root
⇛You cant flash your device stock rom in another device..... since it will definitely give you a brick...If you flash all partitions like bootloader partitions
Arvin1989 said:
I have a few questions to ask.
Is it possible to get your stock rom from your android device?
Are there any apps that can do this?
I can't find my stock rom anywhere. If it is possible that i get my rom can I use it to downgrade a similar device to this current stock rom i have?
Click to expand...
Click to collapse
You can backup stock rom using TWRP or similar other recovery. Directly boot into TWRP using fastboot, don't install it, if you want to backup or keep the stock recovery intact. That way on reboot you will boot using stock recovery as TWRP is not installed.
Not sure if it's safe to restore another device's backed up ROM on your particular model.
Yes you can use GSM Aladdin box or Miracle Box
Or you can use both without box because both have loader version and both apps are easy to use and have a similar GUI so..
1 install GSM Aladdin
2 open GSM Aladdin
3select your device type from the tabs
4 make sure you have the appropriate drivers
5 select read flash and tick on save as scatter if you want it like that(recommended if you are going to use this rom with sp flash tool). And choose wich partition you would like to save or back up (like boot,system,logo etc) and indicated where you want it to be saved
6 click on comnect then start
7 connect you phone which should be switched off
8 it will read your flash wait it may take lil bit long
9 here you go now you have a copy of your stock rom
NOTE : this does not requir root
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.