I flashed asian latest firmware, when i tried to revert back to indian version , the gpt flash failed and from that my phone doest not boot correctly
1. reboot - goes to bootloader and again i have press start button in bootloader menu to boot.
2. power off - goes to bootloader and again i have press power off button in boot loader menu.
is it software or hardware issue.
It's clearly software issue. Did you make a nandroid backup before upgrading to asian firmware? If so... Did you apply a factory reset before and after restoring it?
Related
My stock Nexus 7 (4.4, kot49h)'s volume down button is not working. Not even in bootloader (4.23) . Because of that, everytime i reboot it goes in the bootloader, not in system. And from bootloader I'm only able to go to safe-mode. I tried flashing a newer version of bootloader, and re-flashing the stock ROM. I can only use safe-mode.
Any solutions? Should I take it to the service and wait or there is a faster method of solving this problem?
Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this message "Verification failed unable to restart your device the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.
I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.
True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.
Hi. Having a issue with my girlfriends phone. Don't know what happened, but it got stuck in bootloop. So I did a Odin flash, phone had custom Rom before this.
Now it's stuck on bootloop, and some times ends up like pictured.
Can enter download mode, but not recovery. I guess this has something to do with it having twrp before I flash stock on Odin?
That no command screen is shown first when recovery is booted. You either have to wait a bit for it to show or need to play around with a combination of keys to unhide the recovery menu.
Also when you go back to stock firmware from custom Rom firmware you have to factory reset your phone to boot it up again.
Finally, after about 3 hours I finally got access to recovery menu. First time I could not make any selection, 2nd time I got to factory reset and wipe clean. Now it's booting normally!
Key combination
Hi, which key combination did you use to get access into recovery menu?
josersab said:
Hi, which key combination did you use to get access into recovery menu?
Click to expand...
Click to collapse
Hold power button and press volume up once , should get you into recovery
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
TTR6214 said:
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
Click to expand...
Click to collapse
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Predatorhaze said:
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Click to expand...
Click to collapse
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try
Code:
fastboot boot recovery.img
, phone will never boot into recovery.
TTR6214 said:
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try , phone will never boot into recovery.
Click to expand...
Click to collapse
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Predatorhaze said:
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Click to expand...
Click to collapse
Ok thanks for your answer and explanation
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand