Related
Hi, I rently bought a Galaxy S7 Edge and i wanted to install the SUPERMAN custom ROM so :
I followed the tutorial to root the phone => ok
the tutorial to install TWRP => OK
Then the tutorial to install the ROM, and thats when the problems started to appear.
When I tried backing up before the installation in TWRP, I had a couple of error message like "unable to mount data". As the phone was new, I did not have any personnal data on it I thought "Backup is not necessary (grave error?)
so I skiped and went directly to ROM installation (the ROM was on an external microSD card) => installation OK
BUT I forgot to wipe Dalvik cache before rebooting, and as i understand it, it can cause a bootloop, it apparently did!
Here, as it was late, I started to lose my cool, so I am not entirely sure about the sequence of what I have done, but I am trying my best to be precise so that you can find a way to help me.
- I went back to TWRP, I tried to wipe dalvik cache and other types of wipe, but had the same error "unable to mount data" on every try.
-I googled a little bit and found a video tutorial ecplaining that I need to wipe => advanced wipe => tick system => change file system => then choose a type (i chose exFat) => It went on for 10-15 minutes without any sign of evolution so I reached the peak of my stupidity (really lost my cool), and forced reboot (not sure if I used volume UP or DOWN
-I dont think I did anything else after this, when I tried going into TWRP, I got stuck on the TWRP presentation page
The phone starts normally in download mode (am I saved?)
But it does not completely start in TWRP mode, it gets stuck on the presentation page (where there is the name of the team and the version number)
I tried installation other versions of TWRP with Odin but I still get stuck on the presentation page, although the version number changes adequatly to the version installed.
Please help me! :crying::crying::crying::crying::crying:
thank you.
Good news, is yes you can restore your device. Download your stock rom , unzip and flash in odin.
The is a dedicated thread on XDA for TWRP, in the steps the is a no-verity-opt-encrypt.zip which you should download.
Once you reach twrp again you should swipe to allow mod, then click on wipe, format data and type in yes when prompted.
After which flash the zip mentioned above. Now you will have access to the system in twrp, and flash whatever rom you like.
trust this helps
@soka said:
Good news, is yes you can restore your device. Download your stock rom , unzip and flash in odin.
The is a dedicated thread on XDA for TWRP, in the steps the is a no-verity-opt-encrypt.zip which you should download.
Once you reach twrp again you should swipe to allow mod, then click on wipe, format data and type in yes when prompted.
After which flash the zip mentioned above. Now you will have access to the system in twrp, and flash whatever rom you like.
trust this helps
Click to expand...
Click to collapse
thank you, I will try this later today and let you know how it goes!
thanks.
lass93 said:
thank you, I will try this later today and let you know how it goes!
thanks.
Click to expand...
Click to collapse
Best of luck buddy.
It worked thanks a lot man!
Now, onto the next step, I guess the tutorial I followed initialy was not good enought. So where can I get this "no-verity-opt-encrypt.zip", and how should I install it exactly? Unless I missed something, it is not explained in the xda tutorial
http://forum.xda-developers.com/s7-edge/development/rom-s7-edge-rom-v1-1-t3356699
Thank you all
Follow these instructions, the links for the latest recovery and the zip I mentioned are all there. If you need further help. I will help.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You do have a G935F right?
@soka said:
Follow these instructions, the links for the latest recovery and the zip I mentioned are all there. If you need further help. I will help.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You do have a G935F right?
Click to expand...
Click to collapse
Yes I do
Ok Thx. Will let you know!
lass93 said:
Yes I do
Ok Thx. Will let you know!
Click to expand...
Click to collapse
I Followed the instructions of your link, then I followed the instructions of the tutorial to install SuperMan ROM bug at the last reboot (after installation) I got stuck on the "Samsung Galaxy Edge 7" screen, the starting screen...
Hope I can install this ROM, I dont want to go back to stock.
Have you updated the modem and bootloader as dev instructed?
First initial boot will take time , remember you wiped everything but you Internal storage and SD card.
"9. Reboot and wait around 10 minute's (deodexed roms need longer to boot the first time)
10. Don't interrupt the process of booting the phone, even when it restarts"
How long did you leave it on the Samsung S7 Edge screen?
@soka said:
Have you updated the modem and bootloader as dev instructed?
First initial boot will take time , remember you wiped everything but you Internal storage and SD card.
"9. Reboot and wait around 10 minute's (deodexed roms need longer to boot the first time)
10. Don't interrupt the process of booting the phone, even when it restarts"
How long did you leave it on the Samsung S7 Edge screen?
Click to expand...
Click to collapse
Yes I followed the instructions and downloaded the too exact files he said, flashed it with odin
I wiped everything (even internal storage) but micro sd card
I left it more than 30 minutes.
One thing I did I'm not sure about, during root, I followed the tutorial (the link you gave me) to root and install twrp, during this step, I flashed both superSU and dm verity... step 11 ( http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084 ) Is that ok?
My method, that works for me is as follows :
Flash my stock firmware via odin.
Boot up, select OEM and USB debugging on.
Flash latest TWRP in odin.
Boot up phone, then switch off and enter recovery.
In recovery page i swipe to allow mod, select wipe /format data and type in yes when prompted.
Then , flash the no-verity zip.
I then boot up the phone normally and let it settle for about five min, switch off and get back into TWRP.
Now there shouldn't be any red error msg's in TWRP of cant mount. ( That is important ) otherwise rom wont flash properly.
After which i will flash a rom, most custom stock roms already have SU.
@soka said:
My method, that works for me is as follows :
Flash my stock firmware via odin.
Boot up, select OEM and USB debugging on.
Flash latest TWRP in odin.
Boot up phone, then switch off and enter recovery.
In recovery page i swipe to allow mod, select wipe /format data and type in yes when prompted.
Then , flash the no-verity zip.
I then boot up the phone normally and let it settle for about five min, switch off and get back into TWRP.
Now there shouldn't be any red error msg's in TWRP of cant mount. ( That is important ) otherwise rom wont flash properly.
After which i will flash a rom, most custom stock roms already have SU.
Click to expand...
Click to collapse
Exactly what I did except for the SU part that i mentionned. i asked on another Forum, they said there might be a problem with the zip I used. So i'm gonna try downloading a new zip for this ROM, but i can't find any alternative links...
I redownloaded the zip from the link in the tutorial, it worked!! thanks for your help!
If you guys help me to go back successfully to stock, I'll make a guide to explain the process, maybe for all 3 models. I just need help on this one
I have an A2017G
So this is my fourth time trying to get back to stock. the first one resulted on a DFU brick. The second one was through MiFlash and the system had random reboots. The third, I flashed tron1's A2017G B04 Bootstack and a DrakenFX flashable zip (for the U, just wanted to try) and TWRP said that there was no system which turned out to be true... i had wiped system, data and caches before, but it seemingly installed okay...
I also tried to use MiFlash again and get B10, but it started to throw an error out of the blue (the specified cast is not valid, or something along the lines). I used it at least 4 times before.
So what zip should I use? I never tried flashing one of those update zips (I have full official B10 on the sdcard) but I believe they won't work. Please tell me if they do work...
again, if i manage to get SAFELY to stock and AVOID DFU I'll make a nice guide so that we stop asking. Most custom roms are flawed, for ex. Lineage has bad compatibility, Pure Nexus (the one I'm using now) has extreme, Galaxy Y grade lag, and RR simply works worse than stock (it's probably the best one of the bunch though).
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
satish.yarramsetti said:
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
Click to expand...
Click to collapse
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Does EDL work?
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
satish.yarramsetti said:
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
Click to expand...
Click to collapse
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Hey how to boot EDL mode
Choose an username... said:
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Click to expand...
Click to collapse
Please help, how to boot EDL mode? please help i forgot
satish.yarramsetti said:
Please help, how to boot EDL mode? please help i forgot
Click to expand...
Click to collapse
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Still had TWRP
Choose an username... said:
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Click to expand...
Click to collapse
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
Click to expand...
Click to collapse
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
Click to expand...
Click to collapse
MiFlash is that method. It only has to be in the mood to work...
restore failed
Choose an username... said:
MiFlash is that method. It only has to be in the mood to work...
Click to expand...
Click to collapse
restore failed "extracttarfork() process ended with error=255"
satish.yarramsetti said:
restore failed "extracttarfork() process ended with error=255"
Click to expand...
Click to collapse
i had that error when I was backing up. Try to wipe all the partitions but internal (not necessarily format, go to settings and tick use rm -rf) maybe it works. if not try formatting with ext4
lol deleted
No, doesnt help
Choose an username... said:
lol deleted
Click to expand...
Click to collapse
No its doesnt help wiping all partitions.. same error
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
satish.yarramsetti said:
No its doesnt help wiping all partitions.. same error
Click to expand...
Click to collapse
QuantumFluxx said:
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
It might have worked post restart. I am unable mount internal storage or fash but Post restrat it worked
QuantumFluxx said:
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Choose an username... said:
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
Click to expand...
Click to collapse
QuantumFluxx said:
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Click to expand...
Click to collapse
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
satish.yarramsetti said:
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Click to expand...
Click to collapse
QuantumFluxx said:
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
Click to expand...
Click to collapse
The restore is also not working i got some error 255 ... Strange thing is i got a warning like no OS after installing LOS but i booted.
Hi All,
Im pretty close now to throwing Nexus 6p into the wall. Im honestly desperate now.. Few weeks ago replaced battery and usb dock.. and now Im infected by malware which I cannot even remove. Trying different methods for a week now.
Ads pop up (saying Im won something most of the times) in chrome after factory reset without any apps installed, before I even log in to google or anywhere. Same happens on different wifi networks and 3g.
What I tried up to now:
1. Factory reseting through android,
2. Factory reseting and clearing system cache through bootloader
3. Flashing new image from https://developers.google.com/android/images. Im not very familiar with this so had few issues: during procedure "flash-all.sh" - it did not work - nothing happend after trying to run it. So I did (or at least tried) to use this tutorial https://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931 - Method no. 2. Managed to do almost everything apart these lines "fastboot flash userdata C:/images/userdata.img" and "fastboot flash cache C:/images/cache.img" because they are simply not in the zip file of image I got from google.
After all this, phone restarted fine, but still came up with ads as soon as I open any few pages in chrome.
Could you please help me this this to guide through what to do? I spent ages on google trying to find exact solution but some are old, some I dont get, some without clear instructions what to do...
Appreciate your time guys,
On one post I found that sequence what needs to be installed should be:
"fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache. "
What does last line mean? What is TWRP recovery, dalvik cache?
BenasJ said:
On one post I found that sequence what needs to be installed should be:
"fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache. "
What does last line mean? What is TWRP recovery, dalvik cache?
Click to expand...
Click to collapse
What you need to do is backup all your downloads , music, pictures and anything you've saved in the internal memory. Then go to wipe in twrp and select everything inc internal. That is where it's probably hiding and factory reset won't erase your storage only with internal wipe. But remember you will loose everything so do a manual backup onto desktop or thumb drive. Then you can go flash whatever you please. I'm on the latest 8.1 April and it's working flawlessly. You don't have to wipe davlick and cache after factory flash just good practice to avoid any hiccups like hanging on first boot.
Exodusche said:
What you need to do is backup all your downloads , music, pictures and anything you've saved in the internal memory. Then go to wipe in twrp and select everything inc internal. That is where it's probably hiding and factory reset won't erase your storage only with internal wipe. But remember you will loose everything so do a manual backup onto desktop or thumb drive. Then you can go flash whatever you please. I'm on the latest 8.1 April and it's working flawlessly. You don't have to wipe davlick and cache after factory flash just good practice to avoid any hiccups like hanging on first boot.
Click to expand...
Click to collapse
Is there a easier way to do this? As I understand I would need to have my phone rooted, to do this I need to to have twrp, to have it I need to install custum recovery through bootloader....
Is there a easier way to just to wipe all the internal data?
Can someone please just give quick sequence what after what needs to be done? Taking into account I got stock non rooted android 8.1. (I dont give a .. about photos and videos, whats the simplest way to make phone functioning as it supposed to again)
Thanks
BenasJ said:
Is there a easier way to do this? As I understand I would need to have my phone rooted, to do this I need to to have twrp, to have it I need to install custum recovery through bootloader....
Is there a easier way to just to wipe all the internal data?
Can someone please just give quick sequence what after what needs to be done? Taking into account I got stock non rooted android 8.1. (I dont give a .. about photos and videos, whats the simplest way to make phone functioning as it supposed to again)
Thanks
Click to expand...
Click to collapse
I suppose you can use fastboot command "fastboot format userdata". I'm not sure if it would effect your current install but shouldn't.
Hi.
Flashed image again and ran command: "fastboot format userdata".
However again no luck.. still same anoying advert after doing few clicks in browser..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
BenasJ said:
Hi.
Flashed image again and ran command: "fastboot format userdata".
However again no luck.. still same anoying advert after doing few clicks in browser..
Any ideas?
Click to expand...
Click to collapse
My opinion/idea/fix:
1. Unlock bootloader
2. Backup your recovery stock thing (Using Nexus Toolkit, google it)
2. Flash Custom Recovery (TWRP recovery zip, using adb)
3. Boot to Recovery (TWRP)
4. Wipe everything EXCEPT bootloader and recovery
5. Flash the 2nd step backed up recovery.img using TWRP recovery, to recovery partition.
.....
Procced with the stock steps you followed earlier and failed.
Not sure if I am clear.
Also not sure if you know how to do the steps.
I can help you try the solution I described tho, let me know!
Pipiou211 said:
My opinion/idea/fix:
1. Unlock bootloader
2. Backup your recovery stock thing (Using Nexus Toolkit, google it)
2. Flash Custom Recovery (TWRP recovery zip, using adb)
3. Boot to Recovery (TWRP)
4. Wipe everything EXCEPT bootloader and recovery
5. Flash the 2nd step backed up recovery.img using TWRP recovery, to recovery partition.
.....
Procced with the stock steps you followed earlier and failed.
Not sure if I am clear.
Also not sure if you know how to do the steps.
I can help you try the solution I described tho, let me know!
Click to expand...
Click to collapse
Hi, Thank you for responding!
Before you posted your message thats what I did:
1. Replaced/reflashed recovery.img with twrp
2. Inside TWRP (opened trough bootloader holding power + down...) in advanced wipe options, wiped everything possible
3. Rebooted into bootloader and using ./fastboot commands flashed bootloader, radio, boot, recovery, system, vendor with stock image
4. Replaced/reflashed recovery.img with twrp again
5. Wiped cache and dalvik cache
Still the same problem..
What I can understand I pretty much did what you suggested, correct? I dont have access to Windows pc untill Monday so cannot use Nexus Toolkit. But thanks for recomending it! I'll look into it
BenasJ said:
Hi, Thank you for responding!
Before you posted your message thats what I did:
1. Replaced/reflashed recovery.img with twrp
2. Inside TWRP (opened trough bootloader holding power + down...) in advanced wipe options, wiped everything possible
3. Rebooted into bootloader and using ./fastboot commands flashed bootloader, radio, boot, recovery, system, vendor with stock image
4. Replaced/reflashed recovery.img with twrp again
5. Wiped cache and dalvik cache
Still the same problem..
What I can understand I pretty much did what you suggested, correct? I dont have access to Windows pc untill Monday so cannot use Nexus Toolkit. But thanks for recomending it! I'll look into it
Click to expand...
Click to collapse
Yea, it's the same idea/thing.
Good luck ... Professionals of XDA community should help you clean this malware.
It is obviously a strong **** ...
It obviously can draw attention !!
---------- Post added at 07:13 PM ---------- Previous post was at 06:56 PM ----------
Worth the double post, yolo.
Is there a chance that someone is having access to your network? Manipulating the html requests? :fingers-crossed:
crying: it combined the posts )
Pipiou211 said:
Yea, it's the same idea/thing.
Good luck ... Professionals of XDA community should help you clean this malware.
It is obviously a strong **** ...
It obviously can draw attention !!
---------- Post added at 07:13 PM ---------- Previous post was at 06:56 PM ----------
Worth the double post, yolo.
Is there a chance that someone is having access to your network? Manipulating the html requests? :fingers-crossed:
crying: it combined the posts )
Click to expand...
Click to collapse
I thought of it aswell, tried at home wifi network, 3g, work wifi network, but exactly same type of ad pop-ups come up on every network. FYI it happens like I said even on completely clean/fresh factory reseted phone before putting any logins or installing anything
BenasJ said:
I thought of it aswell, tried at home wifi network, 3g, work wifi network, but exactly same type of ad pop-ups come up on every network. FYI it happens like I said even on completely clean/fresh factory reseted phone before putting any logins or installing anything
Click to expand...
Click to collapse
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?
Pipiou211 said:
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?
Click to expand...
Click to collapse
Thank you for your encouragement I'm getting more and more annoyed.. Another few days without luck and I'll be buying my first iphone if I wont find solution
Let me know if you get any other ideas
Pipiou211 said:
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?
Click to expand...
Click to collapse
Can you have a look into text file and tell am I doing everything correctly? Its copy of terminal of how I flashed image last time. After this I wipe system data inside recovery and reboot.
Are these 100% correct steps Im doing?
Thanks !!
BenasJ said:
Can you have a look into text file and tell am I doing everything correctly? Its copy of terminal of how I flashed image last time. After this I wipe system data inside recovery and reboot.
Are these 100% correct steps Im doing?
Thanks !!
Click to expand...
Click to collapse
Not in the mood, I have soo long time to flash OTA full or updates .zip(s) anyway, really.
I can give you a solution tho, preety good to go with.
1. Choose between those 2 -stock enough- custom roms:
(MY PERSONAL PREFERENCE)
--- Pure Nexus 7.1.1 (Older Android - Faster - Solid AF)
--- SuperXE 8.1.0 (Latest Android - Slower and maaaybe a little worst battery life - Still Solid, I am using it atm as main ROM)
----
Let me know If I should keep writing, so we can try from zero the attempt I previously mentioned (wiping and reflashing).
In my opinion if you follow the steps I am about to write you SHOULD not believe in your eyes if you still see the virus, or consider that the malware is actually something else, somewhere else and not in your smartphone's ROM or Storage.
(If you wanna go for it, start downloading the ROM files you choosen, it will save you/us time, find them here on XDA Nexus 6P section)
(I will edit this post)
----
2. Follow the steps @Cile381 gives on SuperXE thread, if you have any questions I will respond/help instantly, just use @Pipiou211 so I will receive the notification.
BE VERY VERY VERY CAREFUL with your bootloader, radio and recovery sections, if you leave one of them empty, flash wrong .zip/.img or unplug your smartphone while flashing you will HARDBRICK your device.
Especialy Bootloader.
Update them to be ready for Oreo Android and move to next steps (vendor and rom).
Pipiou211 said:
Not in the mood, I have soo long time to flash OTA full or updates .zip(s) anyway, really.
I can give you a solution tho, preety good to go with.
1. Choose between those 2 -stock enough- custom roms:
(MY PERSONAL PREFERENCE)
--- Pure Nexus 7.1.1 (Older Android - Faster - Solid AF)
--- SuperXE 8.1.0 (Latest Android - Slower and maaaybe a little worst battery life - Still Solid, I am using it atm as main ROM)
2. Let me know If I should keep writing, so we can try from zero the attempt I previously mentioned (wiping and reflashing).
In my opinion if you follow the steps I am about to write you SHOULD not believe in your eyes if you still see the virus, or consider that the malware is actually something else, somewhere else and not in your smartphone's ROM or Storage.
(If you wanna go for it, start downloading the ROM files you choosen, it will save you/us time, find them here on XDA Nexus 6P section)
(I will edit this post)
Click to expand...
Click to collapse
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!
BenasJ said:
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!
Click to expand...
Click to collapse
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
BenasJ said:
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!
Click to expand...
Click to collapse
1.2GB file right? (flashable zip actually) @BenasJ
Pipiou211 said:
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
1.2GB file right? (flashable zip actually) @BenasJ
Click to expand...
Click to collapse
Yes, 1.28 GB. Got it from here: https://forum.xda-developers.com/nexus-6p/development/rom-t3488519
Pipiou211 said:
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
1.2GB file right? (flashable zip actually) @BenasJ
Click to expand...
Click to collapse
@Pipiou211
Quick few question I got:
According to SuperXE instructions I need to:
- Reboot to recovery (Question 1: by recovery it means twrp? do I need to root my phone to do this or just simply replace recovery with twrp using "fastboot flash..." commend like I did before?
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
Question 2: Would these be correct - more detailed instructions how to install "Zip" not "IMG" ?
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
If Yes, Question 3: What is Gapps? Do I need it?
Found answer myself for this: Realised that it was shortening for Google apps. As I understand I need ARM64-8.1 android-stock. Correct?
Thanks
BenasJ said:
@Pipiou211
Quick few question I got:
According to SuperXE instructions I need to:
- Reboot to recovery (Question 1: by recovery it means twrp? do I need to root my phone to do this or just simply replace recovery with twrp using "fastboot flash..." commend like I did before?
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
Question 2: Would these be correct - more detailed instructions how to install "Zip" not "IMG" ?
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
If Yes, Question 3: What is Gapps? Do I need it?
Thanks
Click to expand...
Click to collapse
1. (YES to Question 1)
Flash TWRP (latest) to recovery partition.
2. PowerButton+VolumeUp and access TWRP.
3. Flash bootloader (the one cile381 "tell you" to)
4. Flash vendor (the one cile381 tells)
5. Wipe>Advanced check everything except Bootloader, Vendor and Recovery (already installed TWRP in our case)
6. Flash SuperXE ROM (chill and have fun with the Aroma Installer guidance, if unsure leave everything unticked and just NEXT, NEXT, NEXT, NEXT!!)
7. Reboot and check for the malware, after first-time-setup (wifi google account and so on).
DO NOT restore application data from previous "phone".
(8. If we get softbrick) Flash latest radio.img, will tell you the way if we get softbricked, we probably dont need that.
---
(Response to Question 2.)
Step 3. and 4. are .img flashing.
Step 6. is .zip file flashing.
To flash .zip file just tap Flash in the TWRP and tap the 1.28GB .zip file.
To flash .img file(s) tap Flash, then a button like 'Image' or something, you will see it there are just two buttons, including 'Back', then tap the .img file and tap the partition you wanna flash/install it.
Am I clear? My english is not the best sorry about that.
Pipiou211 said:
1. (YES to Question 1)
Flash TWRP (latest) to recovery partition.
2. PowerButton+VolumeUp and access TWRP.
3. Flash bootloader (the one cile381 "tell you" to)
4. Flash vendor (the one cile381 tells)
5. Wipe>Advanced check everything except Bootloader, Vendor and Recovery (already installed TWRP in our case)
6. Flash SuperXE ROM (chill and have fun with the Aroma Installer guidance, if unsure leave everything unticked and just NEXT, NEXT, NEXT, NEXT!!)
7. Reboot and check for the malware, after first-time-setup (wifi google account and so on).
DO NOT restore application data from previous "phone".
(8. If we get softbrick) Flash latest radio.img, will tell you the way if we get softbricked, we probably dont need that.
---
(Response to Question 2.)
Step 3. and 4. are .img flashing.
Step 6. is .zip file flashing.
To flash .zip file just tap Flash in the TWRP and tap the 1.28GB .zip file.
To flash .img file(s) tap Flash, then a button like 'Image' or something, you will see it there are just two buttons, including 'Back', then tap the .img file and tap the partition you wanna flash/install it.
Am I clear? My english is not the best sorry about that.
Click to expand...
Click to collapse
@Pipiou211 All clear apart section 3:
3. Flash bootloader (the one cile381 "tell you" to)
In their page cile381 provides only ROM and Vendor. Where do I get bootloader from?
Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance
1.No need to flashing blod
2.remove any passwords or screen lock before flashing
3.boot into fastboot make sure bootloader is unlocked
4.flash the twrp recovery provided in the forum u can't use the usual one
5.after installing recovery wipe everything from the advance wipe except internal storage
6.locate and install the rom don't flash the gapps its already included
7.before booting in the system make sure to wipe ur data from wipe or ur phone will not boot
8.time to enjoy!!!
varunvrk said:
Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance
Click to expand...
Click to collapse
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.
Champdroid said:
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.
Click to expand...
Click to collapse
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this
mojorisin7178 said:
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this
Click to expand...
Click to collapse
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.
Champdroid said:
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.
Click to expand...
Click to collapse
Yeah magisk is crazy the devs here at xda can do anything. They really are the best of the best. Everything I know I learned here on xda. I just read they are working on a new way to root at the kernel level so it's built in right from the when it's compiled. That's just crazy smart.
so, my phone was MIUI 10 , i decided to go 11, so i downloaded and installed via recovery.
thing is, when i rebooted and tried to flash magisk the recovery - TWRP - asked for a password, which i didn't put..
why is that?
is any ROM installation does that? is it the recovery's fault?
U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468
joke19 said:
U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468
Click to expand...
Click to collapse
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same
arik100 said:
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same
Click to expand...
Click to collapse
No, I am sure he was referring to points #6, #7, and #8.
i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..
arik100 said:
i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..
Click to expand...
Click to collapse
Same happened with me. Whatever you do your recovery is not gonna decrypt, i tried everything that i can found but nothing worked.
This is only when you flash 10.0 roms no 9.0 rom is gonna cause problem, still searching for a fix. Dont even know what causing this, maybe because it is indian variant or i dont know. Anybody....???
Same issue with an Android 10 Rom.
mr.badman said:
Same happened with me. Whatever you do your recovery is not gonna decrypt...
Click to expand...
Click to collapse
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Roster42 said:
Same issue with an Android 10 Rom.
Click to expand...
Click to collapse
Did you use OrangeFox recovery?
DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
i used TWRP
why?
arik100 said:
i used TWRP
why?
Click to expand...
Click to collapse
Because OrangeFox recovery can decrypt quite fine.
DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
I have tried everything, si yes I have tried with orangeFox
Roster42 said:
I have tried everything, si yes I have tried with orangeFox
Click to expand...
Click to collapse
I should like to see the OrangeFox logs (they will be in the /sdcard/Fox/logs/ folder), because I am yet to see a single situation where OrangeFox cannot decrypt (especially if you formatted data).
Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.
Roster42 said:
Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.
Click to expand...
Click to collapse
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"
DarthJabba9 said:
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"
Click to expand...
Click to collapse
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.
Roster42 said:
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.
Click to expand...
Click to collapse
As I have said, OrangeFox is most definitely able to decrypt. I am yet to come across a single lavender ROM where OrangeFox has not been able to decrypt (and I have tested on virtually all Q ROMs out there) - unless there is something that you are doing (or not doing) , or (which would be very strange indeed) there is something about your own specific phone that makes it particularly impervious to OrangeFox decryption in a way that the phones of several thousands of OrangeFox lavender users are not.
delete
I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?
Roster42 said:
I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?
Click to expand...
Click to collapse
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.
DarthJabba9 said:
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.
Click to expand...
Click to collapse
When ROM boot for the first time it get encrypted, when the encryption process is finished the phone reboot to system and then the android startup process is starting like a new fresh phone. So I just press volume up + shutdown to go in recovery mode and then it asking me a password.
So no I havn't done anything more, I think.
Thank you anyway for your answers.
I think I will go on others ROM, this one seems broken.
I am not the only one havn't this issue.