Related
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
point here.
phorcus said:
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
Click to expand...
Click to collapse
Same happened with me phone doesn't boot... Can't install recovery...
Nothing works tried all possible ways like hard reset
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
zipalign said:
point here.
Click to expand...
Click to collapse
thank you for your help so i was on mokee 7.1 when i flashed only this hydrogen modem v1.1 and when i booted i did not find any volte option, so i went back to latest twrp recovery and tried flashing h2os v2.5 but since 20 minutes i was seeing this ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png ) so i switched off my phone midway and then i installed oxygen os v3.1.0 although it got into a boot loop but when it booted there was no wifi, no imei no, no baseband and many more and when i tried installing mokee or cm14.1 again although they got flashed but when i booted my device i saw oneplus logo and for a few seconds i also saw cm logo and the device continuously kept rebooting in a loop also i am only able to flash oxygen os v3.1.0 that too with no wifi, no imei etc. whereas cm14.1 and mokee wouldnt even boot but they do get flashed and h2os wouldnt even flash , please help :crying:
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Rohandd said:
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
Click to expand...
Click to collapse
i am using twrp-3.0.2-2-oneplus2.img but h2os takes forever to install, but i did flash h2os v2.5's modem v1.1 before flashing h2os v2.5.
i am also seeing this message in twrp " Failed to mount /system (invalid argument) " please help guys
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
I didnt try the seraph build.. Will try it! Thank you
phorcus said:
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Click to expand...
Click to collapse
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
can you please check this screenshot ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
shravansp24 said:
I didnt try the seraph build.. Will try it! Thank you
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Click to expand...
Click to collapse
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
phorcus said:
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
Click to expand...
Click to collapse
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
shravansp24 said:
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
Click to expand...
Click to collapse
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
phorcus said:
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
Click to expand...
Click to collapse
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
shravansp24 said:
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
Click to expand...
Click to collapse
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
phorcus said:
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
Click to expand...
Click to collapse
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
shravansp24 said:
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
Click to expand...
Click to collapse
everything is back to normal on my phone, actually i visited the service center today and they told me that my phone is dead and that i would need to pay 17k to change the motherboard :laugh:
problem here is that H2OS 2.5 messed up all our modems, and who has not made OOS EFS backup via terminal is in trouble now.
when problem popped up in all forums [XDA, and OnePlus one mainly] there have been proposed several solutions, like flashing H2OS modem .zip via recovery, after installing OOS.
so now many users have different scenarios to approach, and a working allwide solution seems not to be found 'til now.
personally I have official TWRP 3.0.2-2 and all my flashings have been made with it.
started from OOS 3.1.0 I had on my phone in the last week, 100% working, then flashed H2OS 2.5. seen the new ROM, decided to get back to something more familiar, so I wiped all and flashed latest nightly of CM13. it was working like a charm, but I had bluetooth issues with my xiaomi mi band [like I always had with OP2 and CM13], so I decided to flash back OOS 3.1.0 wiping data.
OOS 3.1.0 booted up, but without connectivity.
then I realized my modems have been messed up, and started looking for a solution.
the only one I'd try is to fastboot flash OOS 3.0.2 .zip [kindly uploaded by Spannaa], and see if my phone starts working again like it should.
'til now, I will stay with H2OS 2.5 which works perfectly. but when I have time, I'll empty my phone backupping all my stuff [fastboot flashing the .zip mentioned above will wipe userdata too, so I'd lose all my stuff] and try the fastboot thing [I already did it a few months ago, no issues at all].
for those who are in big trouble, that cannot flash anything from recovery, I'd suggest to try to fastoboot flash OOS 3.0.2 with the .zip linked above.
if this solution still doesn't come to an happy ending, then you have to try with the unbrick tool from Qualcomm and see what will happen.
the most important thing is and always will be: don't do anything until you are not aware of what you're actually doing to your phone.
First of all, backup your EFS.
Once done, proceed to the process.
1.Download the files below. Download the MIUI rom you want to flash and get it on your device.
2.Go to recovery. Wipe cache,dalvik cache,system and data.
3. Install the rom along with lazyflasher(link below).
Voila! You flashed it but unfortunately when you reboot it, it will vibrate once and turn off. Being in this state you can't go back to recovery too. So lets fix it.
4. Extract the RN3_unlockblonly and fastboot_edl on your pc.
5.Connect the device to pc and click on edl.cmd from the fastboot _edl.7z. Tge device screen will become black. Let it be.
6.Open Miflash tool and select RN3_unlock_only. Refresh. And then click on flash. Once done remove the device and go to recovery. Wipe cache and dalvik cache and done.
Happy MIUIing!
RN3_unlockblonly.rar https://forum.xda-developers.com/attachment.php?attachmentid=4057737&d=1488316339
Lazy falsher https://www.androidfilehost.com/?fid=529152257862700328
Fastboot_edl.7z https://forum.xda-developers.com/attachment.php?attachmentid=3775693&d=1465328762
Credits:
emuzychenko
AlexCleric
The [email protected]
Hmm... I always Just Flash official Global dev through zcx twrp and it Works without a problem.
Denis:) said:
Hmm... I always Just Flash official Global dev through zcx twrp and it Works without a problem.
Click to expand...
Click to collapse
For me,even zcx throws up the same error so i figured out this method.
Sent from my Redmi Note 3 using XDA-Developers Legacy app
deepjyoti30 said:
For me,even zcx throws up the same error so i figured out this method.
Sent from my Redmi Note 3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
What error do you get?
You must flash latest miui fastboot rom, if you are still on LP bootloader.
I can flash now migrate between miui and N custom roms without problem with ZCX 0917
But thank you anyway
Denis:) said:
What error do you get?
You must flash latest miui fastboot rom, if you are still on LP bootloader.
I can flash now migrate between miui and N custom roms without problem with ZCX 0917
But thank you anyway
Click to expand...
Click to collapse
Every time i flash miui with lazy flasher just from any N custom rom i get the vibrate and turn off error. I have flashed the fastboot roms ton of times and my device had out of the box mm. I have also tried it with zcx but got the same error
deepjyoti30 said:
Every time i flash miui with lazy flasher just from any N custom rom i get the vibrate and turn off error. I have flashed the fastboot roms ton of times and my device had out of the box mm. I have also tried it with zcx but got the same error
Click to expand...
Click to collapse
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot
Denis:) said:
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot
Click to expand...
Click to collapse
I tried exactly that but it always ends up with the error
Denis:) said:
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot
Click to expand...
Click to collapse
I'm using MIUI Global beta latest 7.4.13
I want to try Nougat ROM but I'm afraid of getting bootloop.
So pls tell me exact procedure for Switching back to MIUI from Lineage OS using Recovery method (zcx TWRP)...
I'm using ZCX TWRP, Officially Unlocked Bootloader.
Will my Bootloader Locked after Revert back to MIUI??
Thanks
Ajendra25 said:
I'm using MIUI Global beta latest 7.4.13
I want to try Nougat ROM but I'm afraid of getting bootloop.
So pls tell me exact procedure for Switching back to MIUI from Lineage OS using Recovery method (zcx TWRP)...
I'm using ZCX TWRP, Officially Unlocked Bootloader.
Will my Bootloader Locked after Revert back to MIUI??
Thanks
Click to expand...
Click to collapse
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.
JLius said:
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.
Click to expand...
Click to collapse
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom
Denis:) said:
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom
Click to expand...
Click to collapse
@Denis:) So If I just flash MIUI Global dev using ZCX TWRP reverting from Lineage OS it should work smoothly?
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Denis:) said:
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom
Click to expand...
Click to collapse
@Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS, it should work smoothly right?
Ajendra25 said:
@Denis:) So If I just flash MIUI Global dev using ZCX TWRP reverting from Lineage OS it should work smoothly?
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
@Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS, it should work smoothly right?
---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------
[/COLOR @Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS it should work smoothly right?
Click to expand...
Click to collapse
If you ever flashed MM fastboot miui on this device before, then yes. If you didnt you are still on LP bootloader, which will result in BL relock and you will have to boot to fastboot and then unlock it officialy via miunlock.
Ptocedure in twrp:
Format data (type yes)
Advanced wipe (wipe everyhing, except microSD)
Flash Recovery miui ROM, reboot:good:
Denis:) said:
If you ever flashed MM fastboot miui on this device before, then yes. If you didnt you are still on LP bootloader, which will result in BL relock and you will have to boot to fastboot and then unlock it officialy via miunlock.
Ptocedure in twrp:
Format data (type yes)
Advanced wipe (wipe everyhing, except microSD)
Flash Recovery miui ROM, reboot:good:
Click to expand...
Click to collapse
No, still I haven't flashed MM Fastboot Rom. I've checked Bootloader version in CPU-Z App but it says Bootloader - Unknown!
& Is it necessary to wipe Internal storage, bcz I don't want to remove all that my stuff!?
You told me that procedure it's for Reverting to MIUI right?
Ajendra25 said:
No, still I haven't flashed MM Fastboot Rom. I've checked Bootloader version in CPU-Z App but it says Bootloader - Unknown!
& Is it necessary to wipe Internal storage, bcz I don't want to remove all that my stuff!?
You told me that procedure it's for Reverting to MIUI right?
Click to expand...
Click to collapse
I think its neccesary to wipe data aswell...do a backup on microSD...
You will lock your BL if you flash official rom...so you will have to unlock it via fatbooot.
JLius said:
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.
Click to expand...
Click to collapse
Xiaomi Eu roms having a problem its not bypassing mi account page
Thank You U helped me really Every time when i reverting back to miui same problem occurs like no recovery access nd then i am installing custom rom again now i am successfully reverted back to miui
Good Morning everybody,
so yesterday was a rough day and when it eventually end i recive the october security update on the phone, without thinking i installed it and the phone does not boot up , instead i face my recovery (TWRP 3.1.1-0).
Of course i've made a mess because i was on stock rooted 7.0 on my retEU XT1572 phone with unlocked bootloader and status 3
i've tryed to restore a previous nandroid backup wihtout success, so today i downloaded the new RESURRECTION REMIX v5.8.4 (4 december wich is based on stock android 7) but i have no luck even with that...
Do i miss something?is there any rom to try with now? or i have to make a downgrade of my firmware to make it work again?
thanks in advice!
UPDATE:
phone boot now but always in recovery and after rebooting in bootloader i can reboot system from there.. it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
LAST UPDATE:
boot fixed by using this command in twrp recovery
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work (the rom is the same that you linked page40 post #397 )
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
dzidexx said:
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
Click to expand...
Click to collapse
Husky34 said:
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
Click to expand...
Click to collapse
1. I think so. 3.2.x will be needed for future builds.
1a. You flashed RR for MM modem.
2. No, but this is only way to get ota update.
"swearing in italian" it was a twrp bug.. after a backup restore if you hit restart the phone restart in recovery, you need to boot into bootloader and reboot system from there -.-
thanks to all of you guys!!
strange fact, now if i turn off the phone and again on i'm still on recovery, i have to reboot bootloader and system from there.
i think something is pointing at the recovery instead system..
edit: it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
dzidexx said:
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
Click to expand...
Click to collapse
just tried but wihout luck.. maybe i can wait someone make the flashable update but i don't think this fix the issue
Flash uploaded stock.
dzidexx said:
Flash uploaded stock.
Click to expand...
Click to collapse
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Husky34 said:
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Click to expand...
Click to collapse
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
pshadoww said:
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
Click to expand...
Click to collapse
you can also use link2sd to disable the update app so it doesn't bother you,
or wait untill someone create a zip of the update and flash it into recovery.
thanks, that worked for me as well.
File was located at /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc
Hey guys just wondering what Treble roms have been tested on our essential. Additionally, i want to start testing some myself and wanted to know if twrp actually allows us to make backups and if we copy to an external source if we can successfully restore later on. Thanks! I want to test bootleggers and others but wanna keep my data.
GuestK0010 said:
Hey guys just wondering what Treble roms have been tested on our essential. Additionally, i want to start testing some myself and wanted to know if twrp actually allows us to make backups and if we copy to an external source if we can successfully restore later on. Thanks! I want to test bootleggers and others but wanna keep my data.
Click to expand...
Click to collapse
Are there set instructions for flashing GSIs to the Essential, My last 4 devices had all separate commands, and modified vbmeta. I am yet to see solid flashing instructions, whether it be via Fastboot or TWRP....
*edit*
I ordered this device last night and due to receive it on Thursday. Just trying to figure out whats different from the Pixel 2 XL, Pixel XL, OnePlus6 and now my Essential. So im new to these parts of XDA, please dont be an ***.
I couldn't find a TWRP that supported Treble. Which is something you need to access the vendor partition.
Ascertion said:
I couldn't find a TWRP that supported Treble. Which is something you need to access the vendor partition.
Click to expand...
Click to collapse
Thats when Fastboot comes into play... There are no Fastboot commands for Essential to be able to flash a GSI on A/B?
U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.
Benzo 9.0 gsi rom works amazing and has every customization one can think of
jacksummers said:
Benzo 9.0 gsi rom works amazing and has every customization one can think of
Click to expand...
Click to collapse
I'm currently on stock pie. Do I have to downgrade to Oreo before I can flash benzo gsi? Is there any other steps that are required to get it to work? Thanks for your help.
Joylesstuna said:
I'm currently on stock pie. Do I have to downgrade to Oreo before I can flash benzo gsi? Is there any other steps that are required to get it to work? Thanks for your help.
Click to expand...
Click to collapse
Yes last Oreo firmware. Then after setup back to boot loader, fastboot erase system, flash the gsi, switch to other slot, do same thing, reboot.after u get it setup, back to boot loader then recovery, factory reset, then set it up flash twrp, mount system, flash phhhsuperuser ab zip, then reboot
Is there a reason we can't flash a 9.0 GSI from stock Pie? Just curious as to why we need to downgrade to 8.1 to flash something on 9.0..
MoistPicklez said:
Is there a reason we can't flash a 9.0 GSI from stock Pie? Just curious as to why we need to downgrade to 8.1 to flash something on 9.0..
Click to expand...
Click to collapse
U need the vendor files from 8.1 with the 9.0 pie gsi's. I tried to go from pie and just wipe everything and then before flashing the gsi flashing a vendor.img from 8.1, but it had weird issues, so maybe the firmware needs to directly place the vendor files where they go directly with a proper flash
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Only had that once or twice, make sure u aren't rooting before setup, and try to use gsi's with gapps in built.the newer builds have them included and phhhsuperuser is the only rooting method that truly works without issues
---------- Post added at 03:31 PM ---------- Previous post was at 02:54 PM ----------
MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Benzo rom is the best, at least until havoc p gets fixed. It's the only one I can't get to go
MoistPicklez said:
Hmm, I've tried many GSI's, and had quite a few of them spit back the "Device is Uncertified" screen and couldn't pass the setup. Would anyone know a way around this? It's a pain trying to install a GSI only to have to go BTS right away.
Click to expand...
Click to collapse
Device is Uncertified on stock Pie with Magisk on OP6...
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
jacksummers said:
U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.
Click to expand...
Click to collapse
Thanks for all your information, PM sent...
jacksummers said:
Only had that once or twice, make sure u aren't rooting before setup, and try to use gsi's with gapps in built.the newer builds have them included and phhhsuperuser is the only rooting method that truly works without issues
---------- Post added at 03:31 PM ---------- Previous post was at 02:54 PM ----------
Benzo rom is the best, at least until havoc p gets fixed. It's the only one I can't get to go
Click to expand...
Click to collapse
So no Magisk then?
governmentissuejoe said:
So no Magisk then?
Click to expand...
Click to collapse
Correct no magisk. Search for phhhsuperuser ab zip flash in twrp
governmentissuejoe said:
So no Magisk then?
Click to expand...
Click to collapse
On my OP6, I have NOT been able to get Magisk to flash properly on ANY P GSIs....
---------- Post added at 05:00 PM ---------- Previous post was at 04:45 PM ----------
jacksummers said:
Correct no magisk. Search for phhhsuperuser ab zip flash in twrp
Click to expand...
Click to collapse
So you didnt have to use ANY cmds to disable Verity or Decryption on Fastboot? That was a BIG deal on OP6 and Pixel 2 XL. I'm guessing the Essential TWRP build decrypts instead?
---------- Post added at 05:04 PM ---------- Previous post was at 05:00 PM ----------
jacksummers said:
U can flash gsi's via fastboot. And u can install them with our twrp. Every a/b gsi on the treble threads boot, except for havoc P . It bootlooped. Some are better than others. Oreo havoc works great. I am running pixel experience P right now. To flash them and get them to work, just have to fastboot -w then install via fastboot stock Oreo (firmware ending 267) then wipe system only, and flash gsi. Boot. Some of the older gsi's u have to flash the gsi system image to both slots. And regarding twrp nandroid backups, make your backup, then copy to external. After testing, fastboot -w again, flash android P (firmware 091) then after setup, copy backup back to phone, boot back to twrp, and restore. Oh yeah be sure to flash the kernel u use with regular use in twrp before making the nandroid or u will just backup twrp as your kernel... there are some issues, but if u can fix them, its a fun experiment.
Click to expand...
Click to collapse
Firmware ending in 267 is for Sprint, FYI
So I thought I'd get the flashies and attempt more then a few GSI's.
I had some varying results. I installed all the GSI's in the same manor:
- Flash latest stock O
- Wipe "fastboot -w".
- Install "fastboot flash system example.img". This also wipes System before flashing.
Benzo 9.0 - Success!
Bootleggers 3.0/8.1 - Uncertified and unable to complete setup.
DU 8.1 - Uncertified and unable to complete setup.
Pixel Exp 9.0 - Success!
Pixel Exp 8.1 - Uncertified and unable to complete setup.
RR 8.1 - Success!
Benzo is by far my favorite so far. Give it a shot!
Did you do anything to the benzo rom after downloading it? And by latest stock o is 267?
martinezs89 said:
Did you do anything to the benzo rom after downloading it? And by latest stock o is 267?
Click to expand...
Click to collapse
No, maybe unzipped it, but otherwise I just used the steps in my other post, and yes I used stock O 267.
I can't seem to get it to flash on fastboot. Idk what I am doing wrong
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Nothing will be lost from a regular OTA Just check around for any bugs or problems that other people are having if any? And update if you like.
rockerduck said:
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Click to expand...
Click to collapse
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
rockerduck said:
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
Click to expand...
Click to collapse
You're welcome. I don't think it's needed the disable_dm-verity (but also i don't think that's a bad thing if you reflash it). If you want to thanks somebody in xda forum just press the thanks button (the ok button).
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
wheelnut said:
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
Click to expand...
Click to collapse
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
wheelnut said:
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
Click to expand...
Click to collapse
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
darhma said:
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
Click to expand...
Click to collapse
I'm using Windows and WinRAR. Will try after I download recovery rom (my dl speed is ****ty so it wont be soon)
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
thelastprime said:
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
Click to expand...
Click to collapse
Are you sure you downloaded the right rom? Error 7 is a mismatch of the firmware
Just come to say that everything went fine.
I didn't need to wait for unlock bootloader. I bought phone 2 weeks ago and using it normally and when I start unlock procedure it unlock without waiting time (I saw that someone must wait 720 hours!!).
I flash twrp and magisk (I had fingerprint lock so after flashing I did data erase) and now I have rooted phone
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
kaplanfa said:
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
Click to expand...
Click to collapse
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Is updating ota with full recovery rom via twrp erase internal data or installed app?
darhma said:
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Click to expand...
Click to collapse
Is installed app or data lost?
m.nav7854 said:
Is installed app or data lost?
Click to expand...
Click to collapse
If you do an update there should be no data loss however it is always recommended to have a backup of your data