Xperia S LT26I- nAOSProm_b26 Cannot Flash Gapps in TWRP - Sony Xperia S, Acro S, Ion

Gapps not Installing
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!

haris05 said:
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!
Click to expand...
Click to collapse
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.

Mirhawk said:
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.
Click to expand...
Click to collapse
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?

You have to say clearly step by step what you have did to flash the ROM or gapps.then only some1 can help you

same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..

haris05 said:
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?
Click to expand...
Click to collapse
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
Try the gapps I linked above.

Mirhawk is always a life saver for all new Comer's.

Mirhawk said:
Try the gapps I linked above.
Click to expand...
Click to collapse
thanks but still got no luck

nageswarswain said:
Mirhawk is always a life saver for all new Comer's.
Click to expand...
Click to collapse
Just helping out in whatever I can.
bojz said:
thanks but still got no luck
Click to expand...
Click to collapse
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.

Mirhawk said:
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.
Click to expand...
Click to collapse
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
Have u followed the procedure I sent you by message

Mirhawk said:
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
Try the gapps I linked above.
Click to expand...
Click to collapse
I guess am skipping one step of recovery.... gonna try that.

I did flash by using recovery and now I am successful in installing gapps using TWRP 2.8.5.
Now the other issue am facing and that is of unknown IMEI
after flashing 4-5 times the issue resolved but now am facing issue "Unfortunately Setup Wizard has stopped" and it is not letting me do anything with my phone
Any Suggestion what should I do now

bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
exactly the same problem I am facing

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
The same thing exactly
Got Any solution to that?

haris05 said:
The same thing exactly
Got Any solution to that?
Click to expand...
Click to collapse
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.

only in this nAOSP b26 rom im facing this problem "system wizard has stopped" after installing gapps. but i tried other rom then i dont have any problem.

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Let me try this now

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Cannot flash using this ROM. Its giving error on installing

These Steps am Following:
1) Connected Phone on flashboot mode (By Pressing VolUp+Power Key and connecting the cable and it shows blue LED)
2) Flashed with recovery.img file in nAOSProm_b26 using flashtool (Fastboot mode)
3) Flashed with boot.img file in nAOSProm_b26 using flashtool (Fastboot mode)
4) flashed with TWRP 2.8.5 using flashtool (Fastboot mode)
5) disconnected cable and open bootloader then flashed using nAOSProm.zip file
6) wipe cache and dalvik (also treid by wiping cache/dalvik/data and other option I forgot (total 4))
7) flashed using pa_Gapps (as only this Gapps are flashed on my phone, others are giving errors)
same I followed for b25b but its giving error on 5th step mentioned above.
So what wrong am doing

Related

Zip signature error - only when flashing kernels

I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install

Stuck with No ROM Installed

FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.

Help required with bricked Oneplus 3

Hi,
I have installed MIUI in my OP3 this morning, which was working fine. There was an OTA update, after installing it, device rebooted and entered into recovery mode and it was hanging there for more than an hour. Whrn I tried to reboot, it was off and never came up. Tried unbrick using MSM Download Tool and then I am able to get into boot loader screen. From there I have tried to flash TWRP, but if I reboot, I am getting this message only. Currently I have access to bootloader, if I flash TWRP and choose to boot from recovery (from pc), I have access to OTG also. But even after flashing a ROM, If I reboot, I am getting attached screen only.
I have access to TWRP, only when I chiose to reboot from All in one tool from PC.
Please help me.
you have to use method 2of unbrick not method1.it will flash whole stock rom , then reboot enable developer options etc then flash twrp recovery then go ahead.
Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Puddi_Puddin said:
Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.
Click to expand...
Click to collapse
Hi,
I am following method 2 now. I have switched off the phone and connecting to laptop, as soon as I connect to laptop, it is getting into bootloop (without pressing any button). Phone is not detected in laptop.
colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
I have tried to by wiping everything and tried to restore from OTG pendrive. Tried to flash Firmware + Modem, tried to flash different ROM. Nothing helped.
I am in travel now, having limited internet connectivity. I will reach home and then try to download official OP as you suggested.
I do not have data in phone, all the data is already copied to laptop.
colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
Finally, method 2 worked. Thanks a lot.
nagurvidyasagar said:
Finally, method 2 worked. Thanks a lot.
Click to expand...
Click to collapse
I was having the same problem like you how did you solve it ?

Phone keeps rebooting into twrp (3.2.1 official)

I've updated to the latest 3.2.1 twrp for our devices and it keeps rebooting into twrp even though i tell it to reboot to system. I've also updated to magisk 14.6
equlizer said:
I've updated to the latest 3.2.1 twrp for our devices and it keeps rebooting into twrp even though i tell it to reboot to system. I've also updated to magisk 14.6
Click to expand...
Click to collapse
Did you.....
Fastboot the stock boot.img
Then fastboot the new twrp.img
Then flash the new twrp.zip
Then custom kernel (optional)
Then flash magisk.zip?????
doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?
equlizer said:
doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?
Click to expand...
Click to collapse
I skipped the first 2 steps when upgrading and just rebooted into current twrp flashed new twrp, kernel and magisk. Profit
Dielahn said:
I skipped the first 2 steps when upgrading and just rebooted into current twrp flashed new twrp, kernel and magisk. Profit
Click to expand...
Click to collapse
That's what i normally do to but something else happened along the way. Oh well, it's fixed now
equlizer said:
doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?
Click to expand...
Click to collapse
I don't necessarily know if you need to this procedure every time. However, given the fact that recovery now resides in the boot.img, I just think it's a little more prudent to start with stock kernel/recovery before trying to modify it. :good:
Tried to root Pixel XL 2 and it keeps rebooting in twrp
I am a novice at this, but first ran "twrp-3.2.1-2-taimen.img. from cmd prompt.
Then using TWRP installed " twrp-pixel2-installer-taimen-3.2.2-0.zip" everything was fine.
Then installed "Magisk-v16.1(1610).zip" and now keeps rebooting to TWRP.
I can get to fastboot and rerun twrp-3.2.1-2-taimen.img, but then cannot find the zip files to install or flash.
any help greatly appreciated!
bsinkoff said:
I am a novice at this, but first ran "twrp-3.2.1-2-taimen.img. from cmd prompt.
Then using TWRP installed " twrp-pixel2-installer-taimen-3.2.2-0.zip" everything was fine.
Then installed "Magisk-v16.1(1610).zip" and now keeps rebooting to TWRP.
I can get to fastboot and rerun twrp-3.2.1-2-taimen.img, but then cannot find the zip files to install or flash.
any help greatly appreciated!
Click to expand...
Click to collapse
If your post is correct, it appears your using two different twrp's?? Anyways, lets try this. Make sure your screen lock is set to swipe or none. Then fastboot twrp 3.2.2-0.img. Once in twrp, flash the twrp 3.2.2-0 installer zip, then flash your magisk zip and see what happens. Flashing a custom kernel is also recommended after you flash the twrp.zip, and before you flash your magisk zip :good:
Badger50 said:
If your post is correct, it appears your using two different twrp's?? Anyways, lets try this. Make sure your screen lock is set to swipe or none. Then fastboot twrp 3.2.2-0.img. Once in twrp, flash the twrp 3.2.2-0 installer zip, then flash your magisk zip and see what happens. Flashing a custom kernel is also recommended after you flash the twrp.zip, and before you flash your magisk zip :good:
Click to expand...
Click to collapse
I just wanted to create an account to say THANK YOU! I had the same exact issue, and your solution worked. I did not realize I needed to reflash magisk zip.
So again, thank you @Badger50

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.

Categories

Resources