I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the phone booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Captain Krunch said:
I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Click to expand...
Click to collapse
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
sukhwant717 said:
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
Click to expand...
Click to collapse
Screenshots posted
Captain Krunch said:
Screenshots posted
Click to expand...
Click to collapse
flash debug firmware and use intel phone tool
sukhwant717 said:
flash debug firmware and use intel phone tool
Click to expand...
Click to collapse
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Captain Krunch said:
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
Click to expand...
Click to collapse
Thank you very much, after flashing this firmware how do I proceed?, I am currently downloading it and hopefully it flashes successfully
Mods can close this thread as he helped me resolve the issue through PMs
Same issue what to do?
Sent from my AO5510 using XDA-Developers Legacy app
My problem was because of a wrong IMEI, I had to flash the debug firmware he linked above and use phone tools 191 to change the IMEI then sim1 began working.
Send me that tool
mkaraniya said:
Send me that tool
Click to expand...
Click to collapse
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Hi everybody,
I also have a problem with sim card , but it is a little bit different then these that have been described above. First of all my sim is working but not all of the time. I do calls and also I receive a lot of calls. But from time to time sim card just restarts and wants again pin code to unlock ( the phone doesn't restart). A lot of people told me that when they are trying to connect me, their phones are ringing twice and after that they heard busy signal as the call was rejected or the line is busy. In the same time my phone doesn't show any incoming call. Also it is interesting that some people told me that they can't connect me for the hole day and in the same time there is no problem with receiving other calls. From time to time I also can't dial a number. The screen stacks on dialing screen for app. 30 seconds and after that just switch to contacts list.
So what I tried till now:
1. I did a clean install of OTA WW_4.21.40.327
2. Tried to use Sim2 slot, the problems didn't disappear
3. I changed my sim card with new one with no result
4. Tried the sim card with other phone, everything works fine
May be it's time to buy a new phone, but before that I want to be sure that the problems are not caused by software bug.
Any advices and help will be appreciated.
P.S.
The phone is rooted, Magisk 13.3 is installed. The phone is ZE551ML, Z00AD
Captain Krunch said:
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Click to expand...
Click to collapse
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
dejoebad said:
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
Click to expand...
Click to collapse
Am sorry but I recently sold my ZF2 and currently awaiting a new phone. Am sure someone else on the P90 forums can help you get the files you are looking for
Related
Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
Hi xda Users,
I've been a Xiaomi for about 9 months.
It has an unlocked bootloader is rooted.
Have tested the official ROMs several times.
Well yesterday I tried the MIUI10 on the basis of China developer, everything worked fine but had no cellular network. Now I'm back in the global Stabel version, but still no mobile network connection and also no telephone network (for calling or SMS). The SIM card is detected I can also unlock.
is a SIM card from sunrise (Switzerland).
What I have tried:
-Reset to Factory setting
-Reset Network setting
-Sim in second slot
-Restart
Can anyone help me?
Thank You and love Greetings (translated with translator)
Unzip file ROM, copy file boot.img in internal memory. Go into recovery mode, flash file boot.img. reboot system. It will be ok.
bahuy2003 said:
Unzip file ROM, copy file boot.img in internal memory. Go into recovery mode, flash file boot.img. reboot system. It will be ok.
Click to expand...
Click to collapse
Thank you I try it today!
Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
does anyone enable lte bands, 4 and 28?
just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI
Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????
Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!
Does this work for s5 pro l58041?
Thanks
B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!
Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...
so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os
I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img
Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
has anyone achieved unlocking bands in this phone?
Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try
Could you plz make tutorial about getting back to stock unroot...thx
Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back
Love (how the hell can you love a machine??? - sorry, I guess I have NO imagination, maybe you can ...) this phone. BUT!! After backing up and restoring using LR TWRP a number of times, then using fastboot to flash_all the original ROM a number of times when I got into flashing problems, my cavalier approach backfired in one of these repetitive actions. Surprisingly, at least to me, I have both IMEI's listed on the status page, but a constant "unknown baseband" version. SIM setting is grayed-out, and I am only on WiFi. Flashing the original ROM (V 10.4.2.0) fixed nothing. Tried V 10.4.1.0, but I can't downgrade: luckily the phone wasn't bricked. Flashed Havoc V 2.9, hoping all partitions would be overwritten, then flashed MIUI V 10.4.2.0, but no change.
Have found no solution from Hovatek (stated flashing original ROM usually repairs the unknown baseband issue), or other sites searched from Google. Any procedure to solve this MTK issue on this phone would be most appreciated.
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Wow!! Thank you so much! I will follow each step and report what I've found.
So impressed with the detail you have given; thanks to have experts such as you willing to share.
Later ....
Crescendo Xenomorph said:
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Click to expand...
Click to collapse
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Coffeemi said:
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
ppthom said:
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
Click to expand...
Click to collapse
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Coffeemi said:
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have NOT "properly saved a backup file" with the modem partitions, and that is where my trouble lies. I am also not being reminded to set the SIM card info when booting up after flashing the stock 10.4.2.0 ROM, which is strange, because a week ago I was able to go back-and-forth between my restored backed-up files and the stock ROM. On first booting the stock ROM, I was reminded every 10 seconds that my SIM card was not correct (my card is only 3G and the default SIM setup was for LTE), interferring with setting up my WiFi for authenticating my Xiaomi account. Now, with an unknown baseband, the SIM is not recognised by the stock ROM, I can enter my WiFi account without interference; and there no entry for the baseband and nothing for the IMEI numbers.
As soon as my "not proper backup" is restored, the IMEI numbers are set correctly, but no baseband.
My goodness, I will see if anyone online can flash the stock zip file remotely and see if that corrects the problem.
Hey, thank you for paying attention to my problem, and I very much appreciate your time on this.
wang1chung said:
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Click to expand...
Click to collapse
Thank you fellow Canadian :good:; I will try this as well. So great to have all these suggestions from people who know a hell of a lot more than I do. Thank you both Coffeemi and wang1chung.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
Better to use LR TWRP, it's the best for Xiaomi phone.
Sadly it's only available for Android 10 version. Better upgrade as Android 10 still way better than their 9 (too much bug).
Link to A10 LR-TWRP: https://mega.nz/file/Ad4TUTTA#_xT16vOzYK-O8qaWEHPYxfdi4wNpK5Ang9maN5iO_-U
If no error being corrected then sadly I dunno more except for hardware issue (baseband chip is broken, I saw one case in Mi Community forum). Hope not this case. :crying:
You're welcome friend. The Move Certificate module is for AdGuard actually, its to clear those network being monitored notification when you use AdGuard's HTTPS filtering.
Thank you Coffeemi, wang1chung and of course Crescendo Xenomorph. You've all paid attention to this problem, and it is very much appreciated.
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
ppthom said:
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
Click to expand...
Click to collapse
Can you provide me the steps. Because I'm having the same vesion but with IMEI Invalid. My phone accidently got update to MIUI 11 and the Baseband got ruined.!!!
Somehow Android 10 in this phone will corrupt something in nvdata if you do modification on the fly (somehow like they unable to load it properly, thus no baseband with corrupted BT MAC).
How to know if your BT MAC is corrupted? It'll default to 00:00:46:00:00:01.
BT MAC should be one step above WIFI MAC (if your WIFI MAC is AC:1C:05:AC:43:01, your BT should be AC:1C:05:AC:43:02).
Found the culprit: any Magisk version greater than 20.3 will cause this error on MTK devices.
Solution: use Magisk 20.3 stable, it's the only fix till the devs come up with the fix.
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
exocetdj said:
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
Click to expand...
Click to collapse
We're do I get root how to for the u version
The only version that is rooted is the B version. The international, European, and North American versions are not able to be rooted.
We have root on the B variant
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
lilplanet said:
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
Click to expand...
Click to collapse
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
exocetdj said:
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
Click to expand...
Click to collapse
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
pvillasuso said:
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
Click to expand...
Click to collapse
whats your internal storage size? and have you reset device since you last managed to get this working?
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
pvillasuso said:
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
Click to expand...
Click to collapse
Ok sounds promising
Please can you provide a step by step procedure here and if i can replicate it i will amend the first post and files in the rooting thread
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
exocetdj said:
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
Click to expand...
Click to collapse
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pvillasuso said:
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
do you have stock recovery or TWRP installed now you have root?
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
Stock recovery now
I can try to flash twrp , and can go back to stock recovery if it doesnt work
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
exocetdj said:
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
Click to expand...
Click to collapse
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
pvillasuso said:
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
Click to expand...
Click to collapse
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
exocetdj said:
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
Click to expand...
Click to collapse
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Edit : Nice that you could replicate it !
"ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc "
pvillasuso said:
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Click to expand...
Click to collapse
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
exocetdj said:
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
Click to expand...
Click to collapse
Sure Bro , no problem