Stock 7.1.1 TWRP Issue - Sony Xperia X Compact Questions & Answers

Hi there!
Well as the title says, it is an issue...
Here, i'll explain: If i flash the 7.1.1 ftf and boot it afterwards it works. Okay, then i put the phine into fastboot mode and on my computer i flash the advanced stock kernel and twrp 3.1.1.0 afterwards. And i boot the phone and phone starts like usually, but if i boot to recovery it does boot to twrp and all is working. But if i rebooted from twrp to system it says Sony logo > reboot > (this message is there always, i unlocked the bl) this device has been unlocked and phone boots in 5 sec. > the boot image is broken and phone shuts down. But i can still boot to twrp when i use pwr vol down and pushing vol buttons like usually... And if i install a custom rom, in my case paranoid android 7.2.3 it works. I just wanted to install magisk on the stock 7.1.1 and keep the slo mo stuff and so on... I have tried 6.0.1 and did the same stuff and it worked. I want my XZ3c back so bad...

XperiaGUY47 said:
Well as the title says, it is an issue...
Here, i'll explain: If i flash the 7.1.1 ftf and boot it afterwards it works.
Click to expand...
Click to collapse
"Advanced stock kernel
-For 34.1.A.1.198"
Click to expand...
Click to collapse
That's a MM kernel, mod your own using Trim Area Proof Of Concept and try again.

SXUsr said:
That's a MM kernel, mod your own using Trim Area Proof Of Concept and try again.
Click to expand...
Click to collapse
But does the XC Genesis Kernel v. 1.06 work with it?

Related

Nexus 10 does not boot after Update

After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.

[Unlock] Zenfone2 official Android 6.0 Unlock

Two-Click Unlock for Zenfone 2 official Android 6.0
original post in Taiwan Asus Zentalk by @shakalaca
**do it at your risk**
1.Your PC must be adb environment ready.
2.You should know how to get into stock bootloader.( press Power and Volume up together)
files needed:
1. Download unlock.bat and restore.bat from here.
2. Recomended TWRP for verification.(repacked)
steps:
1.Copy unlock.bat and restore.bat on to your PC.
2.Plug your device in PC, click unlock.bat. The program will enter bootloader mode, reboot and then unlock.
3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP at the moment to enter bootloader.
4. If you miss step 3, the device will stuck in Asus logo. Don't worry. Just press POWER and VOLUME UP to enter bootloader.
5.When the device is in bootloader, click restore.bat Wait for the reboot and you are done unlock.
6.To verify unlock status, flash the recommended TWRP.
Good luck and all credits to @shakalaca
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Flynhx said:
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
samcjtsai said:
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
Click to expand...
Click to collapse
my device doesnt get to this part > 3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP
but stays on > press any key to finish...... which then closes the window
I flash twrp,says ok but reboots back to bootloader after restarting recovery.
flashed back stock recovery and factory reset for another attempt...lets see
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
cannot flash custom roms???
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
Same problem here
samcjtsai said:
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Click to expand...
Click to collapse
how can i flash a stock 5.0 rom from the recommended twrp? I tried to do that but it doesn't work. Do I have to flash a stock 6.0.1 beta rom?
It worked perfectly!Thanx a mill!
Can't flash TWRP although the splash screen became white after unlock.bat -> unlocked
After restore.bat the splash screen went black as usual. Then I flash the recommended TWRP. But when I choose recovery mode in fastboot, it reboot to fastboot. When I adb reboot recovery in Android OS, it reboot to stock recovery. Can anyone help me to solve this problem?
I'm running .69 MM beta, I replaced the .54 fastboot image in the package with .69 one. Does this effect the unlock state?
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
can i flash supersu to become root after unlock with this method?
ponnuvelpandian said:
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
Click to expand...
Click to collapse
Thanks :good: , i`ll keep that in mind when the time comes back on 5 atm
kamyk70 said:
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
Click to expand...
Click to collapse
How you root your MM beta?, please tell me, i wanna root mine too
Sent from my ASUS_Z008D using XDA-Developers mobile app
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
KarloHD said:
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
Click to expand...
Click to collapse
Are you going to post this in EVERY tread?
Sent from my ASUS_Z00A using Tapatalk
Now, if we can unlock stock 6.0, can anyone confirm me if we can directly flash custom roms without downgrading to 5.0
after running restore it worked, however when running unlock.bat, I get permission denied and the device goes tinto bootloader bootloop, and I had the device rooted and bootunlocked already in lollipop, I wonder why that happens?

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

LG G3 [D855] Custom Recovery And Rom Flashing

I have went through many tutorials but none of them were able to help me with flashing custom recovery(TWRP). My LG G3 D855 was rooted with towelroot(I think long time ago). I do not know how can I unlock my bootloader or I don't know if it is already unlocked(Picked it off craiglist long time ago). Phone is stuck in fastboot mode. I have tried to fix but I could not. There is no 'download mode'.
Could you please explain each and every step in detail? I really want to reboot my device with a custom ROM.
Phone is running Androind 4.4.2.
So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.
AtaliaKetch said:
So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.
Click to expand...
Click to collapse
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..
andi54 said:
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..
Click to expand...
Click to collapse
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.
AtaliaKetch said:
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.
Click to expand...
Click to collapse
Maybe first flash back stock, update to the latest firmware and start fresh from there?
There are some good guides in the forums here for that.
Cheers
Sent from my Google Pixel using XDA Labs
If you've to go back to firmware, don't install the newest. Rooting needs an older version. Also described in root-threads here.

Your device has been unlocked and can't be trusted. KEY: N/A

I had unlocked my bootloader and then tried to flash twrp. I was unsuccessful to do that. That softbricked my phone and I had to flash stock rom via Mfastboot. Not this is the message I get
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
I have no idea what to do. I went to the service centre and I was told that it might be motherboard problem and that would cost me Rs10,000. I can buy a new phone for that. Someone please help me. I am phone less since past 3 months.
P.S: I can boot into the recovery (the one we do wit power button + volume down, that is the best I can do with my phone right now) I SERIOUSLY NEED HELP!!!
Yes, nothing to do about it. Just flash a new picture to cover it.
If nothing works just reinstall stock or try putting a .zip rom on your device and flash that in recovery.
@clever_idiot
first of all, i think service center guy is making you fool...
If you Re-Lock bootloader again, it will disappear and that cost 1GB data for downloading Stock ROM and few Minutes.
Better than Re-Locking, (in addition to 2nd reply)
You can create your own Logo image to put over that message or you can flash available on link.
Following link contains everything you need to know.
https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Azerox said:
Yes, nothing to do about it. Just flash a new picture to cover it.
If nothing works just reinstall stock or try putting a .zip rom on your device and flash that in recovery.
Click to expand...
Click to collapse
Thanks you for the reply, I did cover it with a stock image of moto logo, still the device wint boot up, I also flashed the stock rom, yet it didnt boot up
clever_idiot said:
Thanks you for the reply, I did cover it with a stock image of moto logo, still the device wint boot up, I also flashed the stock rom, yet it didnt boot up
Click to expand...
Click to collapse
Which ROM you flashed ?
June's security update [ 7.0_NPJS25.93-14-8 ] causes many problems.
____Mdd said:
@clever_idiot
first of all, i think service center guy is making you fool...
If you Re-Lock bootloader again, it will disappear and that cost 1GB data for downloading Stock ROM and few Minutes.
Better than Re-Locking, (in addition to 2nd reply)
You can create your own Logo image to put over that message or you can flash available on link.
Following link contains everything you need to know.
https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
Click to expand...
Click to collapse
I tried everything man, I flashed the stock rom twice with two different methods, non of them worked, its just shutting down and booting and stops at "this device has been unlocked..."
____Mdd said:
Which ROM you flashed ?
June's security update [ 7.0_NPJS25.93-14-8 ] causes many problems.
Click to expand...
Click to collapse
Stock ROM
clever_idiot said:
Stock ROM
Click to expand...
Click to collapse
I mean which version of STOCK ROM ?
And also check if all things are getting installed correctly (better to skip flashing of gpt and bootloader ).
Are you able to boot into bootloader ?
____Mdd said:
I mean which version of STOCK ROM ?
And also check if all things are getting installed correctly (better to skip flashing of gpt and bootloader ).
Are you able to boot into bootloader ?
Click to expand...
Click to collapse
This version of ROM :- Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63
and yeah I can boot into the ****ty bootloader
clever_idiot said:
This version of ROM :- Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63
and yeah I can boot into the ****ty bootloader
Click to expand...
Click to collapse
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
echo92 said:
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
Click to expand...
Click to collapse
nougat
@clever_idiot echo92 is asking for version of nougat you had before flashing TWRP,
If don't remember, then simply answer this
When was you last updated your phone by OTA ?
Is it last 2 months ?
____Mdd said:
@clever_idiot echo92 is asking for version of nougat you had before flashing TWRP,
If don't remember, then simply answer this
When was you last updated your phone by OTA ?
Is it last 2 months ?
Click to expand...
Click to collapse
it was 7.0
clever_idiot said:
I tried everything man, I flashed the stock rom twice with two different methods, non of them worked, its just shutting down and booting and stops at "this device has been unlocked..."
Click to expand...
Click to collapse
First, simply flash the stock rom via. fastboot made.
Then let the phone power on fully ->enable developer option-> enable oem unlock
Then , again flash stock rom by "OEM LOCK.bat" file .
sujeet_kumar said:
First, simply flash the stock rom via. fastboot made.
Then let the phone power on fully ->enable developer option-> enable oem unlock
Then , again flash stock rom by "OEM LOCK.bat" file .
Click to expand...
Click to collapse
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
echo92 said:
So you were flashing the Marshmallow fastboot ROM? What OS did you have before when you were flashing TWRP?
Click to expand...
Click to collapse
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
clever_idiot said:
No luck bro
now the bootloader warning is gone. I am stuck with the MOTO "M' Logo in boot loop
Click to expand...
Click to collapse
How long does your device take on the 'M' logo before it bootloops? Is this with the NPJS25.93-14-8 firmware that you're running? What happens if you press the power and volume down keys together, so you boot to the bootloader and then select 'boot to recovery'? Also, do you have a SD card present in your device?
Hmm, with the re-locking, what's your plan afterwards? I'm not sure if you can unlock now, are you going to try to claim service with a re-locked bootloader?
echo92 said:
How long does your device take on the 'M' logo before it bootloops? Is this with the NPJS25.93-14-8 firmware that you're running? What happens if you press the power and volume down keys together, so you boot to the bootloader and then select 'boot to recovery'? Also, do you have a SD card present in your device?
Hmm, with the re-locking, what's your plan afterwards? I'm not sure if you can unlock now, are you going to try to claim service with a re-locked bootloader?
Click to expand...
Click to collapse
It takes around 1 second or less than that to reboot. When I select the recovery mode options it starts bootlooping. I used this ROM: ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml .zip . Yes I do have a SD card present in my phone RN. No I dont wish to go to the service centre guys they are far from my place.
clever_idiot said:
It takes around 1 second or less than that to reboot. When I select the recovery mode options it starts bootlooping. I used this ROM: ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml .zip . Yes I do have a SD card present in my phone RN. No I dont wish to go to the service centre guys they are far from my place.
Click to expand...
Click to collapse
Try taking the SD card out and see if you can boot then.
echo92 said:
Try taking the SD card out and see if you can boot then.
Click to expand...
Click to collapse
Nope, still loops till eternity

Categories

Resources