Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
me176c-boot is a custom, unlocked bootloader for the ASUS MeMO Pad 7 (ME176C(X)). Designed to be simple and flexible, it can boot into Android and/or Linux.
me176c-boot is a combination of systemd-boot (a simple UEFI boot manager) and android-efi (a simple Android bootloader).
Features
Boot into Android, Recovery and Fastboot
Unlocked bootloader, can boot into custom ROMs
Completely open-source and custom built for ASUS MeMO Pad (ME176C(X))
Flexible configuration to add further boot targets (e.g. Linux dual boot)
Download
Latest release: esp-0.3.0.zip
Older releases: Available on GitHub
Installation
Make sure that you are running Android 5.0 (Lollipop).
Download and unpack "esp.zip" from the latest release.
Make sure you have Fastboot installed.
Boot the tablet into Fastboot mode: On the stock ROM, press "Volume Down" + "Power", and release the "Power" button once the backlight turns on.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Flash the new EFI System Partition (ESP) extracted from the downloaded ZIP: "fastboot flash ESP esp.img"
Recommended: Configure the bootloader to use the stock charger for offline mode charging
Usage
By default, the bootloader will boot into the main Android system. You can recognize the bootloader by the green Android robot that is shown on boot.
Press "Volume Down" while booting to show the boot menu. Navigate through the menu with the "Volume Down" key. Press "Volume Up" to select an option. The "Power" button is not working inside the boot menu.
Configuration
You can access the (systemd-boot) configuration files from Recovery: go to "Mount" and select "EFI System Partiton (ESP)". Then you can access the ESP using ADB at "/esp".
Here are some links with more information how to configure the bootloader:
"systemd-boot" on ArchLinux Wiki
android-efi README ("android" boot type is supported in me176c-boot)
Booting from other partitions
There is an additional "volume" option in me176c-boot that allows booting from other partitions on the internal storage, based on their GPT partition UUID. The partition needs to be formatted as FAT32.
Examples
Using the stock charger (recommended)
Booting into main OS on charger insertion
Dual/multi boot (e.g. Android and Linux)
Limitations
The "BIOS" of the tablet can boot from the internal storage and USB(-OTG). It does not seem to be able to boot directly from external SD cards. However, it is possible to keep most of the system on the external SD card by placing only the kernel (the boot partition) on the internal storage.
The EFI System Partition (ESP) is severely limited in its size (only 16 MiB), which is usually not enough to keep more than one Linux kernel. That’s why me176c-boot supports booting from other partitions on the internal storage.
Setting up an additional ESP partition
There is an unneeded APD (ASUS Product Demo) partition on the tablet, which has a reasonable amount of storage (~300 MiB) and is therefore ideal as additional ESP partition. It contains a few demo product images/media files that are only used for the "demo mode" on the stock ROM.
Boot into TWRP recovery and make a backup of the "APD (ASUS Product Demo)" partition. Store in it a safe place in case you want to restore it.
Wipe the APD partition, and change its file system to FAT32.
Place the EFI application (e.g. Linux) on the APD partition, and use it in a boot target using the "volume" option:
Code:
# Partition UUID of the APD partition
volume 80868086-8086-8086-8086-000000000007
Troubleshooting
In some cases booting may fail or you make a mistake during the installation. In this case, first power off the tablet by holding the "Power" button until it turns off.
Recovery
Even with the bootloader entirely broken, you can still boot into Fastboot mode using the rescue mode ("DNX mode").
Download the stock ROM ("UL-K013-WW-12.10.1.36-user.zip")
Extract "esp.zip" and "droidboot.img" from the downloaded ZIP.
Extract "EFI/Intel/efilinux.efi" from "esp.zip".
Press "Volume Up" + "Volume Down" + "Power" until "Fastboot starting…" shows up on the display.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
XDA:DevDB Information
me176c-boot - Custom, unlocked bootloader for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev/me176c-boot
Version Information
Status: Stable
Created 2018-04-20
Last Updated 2019-07-19
Version History
me176c-boot 0.3.0
lambdadroid said:
Tip: Using the ASUS stock charger for offline mode charging is a great way to be able to charge at any time, even when the current ROM is in a non-bootable state. It also charges a bit more efficiently than the LineageOS ROM.
me176c-boot 0.3.0 contains major improvements and new features in all three of its components. Some of the new features will be required for future versions of the LineageOS ROM, however, booting the stock ROM is still supported.
me176c-bootstrap 0.3.0:
Moved some device specific code from the kernel to the bootloader
Technical details: https://github.com/me176c-dev/me176c-acpi#global-nvs-area
android-efi 0.3.0:
Added option to load additional init ramdisks (initrd)
systemd-boot-me176c 241.0:
Updated to systemd-boot v241
Added custom "android" loader type that makes it possible to write nicer boot configurations using android-efi
Example: https://github.com/me176c-dev/android-efi#systemd-boot
Download: esp-0.3.0.zip
Note: Upgrading wipes all custom boot configurations. For example, if you have been using the stock offline charger option, you will need to re-install it after installing this update.
Click to expand...
Click to collapse
me176c-boot 0.2.0
lambdadroid said:
Redesigned charger detection: There is now an additional charger boot option that is automatically selected when the device is started due to charger insertion.
This allows customizing the boot target in this situation. Examples:
Boot into charger from stock ROM while having a custom ROM installed (in my experience it still charges slightly better with less heat): See "Using the stock charger".
Always boot into main OS: See "Booting into main OS on charger insertion"
android-efi 0.2.0:
Boot Android images from files instead of just partitions.
Pass additional kernel parameters
systemd-boot-me176c 239.0:
Boot images from other partitions on the internal storage.
This is mainly useful for dual booting, because the main EFI System Partition (ESP) is very limited in its size (only 16 MB).
Download: esp-0.2.0.zip
Note: Upgrading wipes all custom boot configurations. (You don't need to worry about this unless you have manually made changes to the bootloader configuration...)
Click to expand...
Click to collapse
me176c-boot 0.1.0
Download: esp-0.1.0.zip
Succesfully flashed the new bootloader.
The android logo is showing up and booting after that.
Scrolling throught the boot menu is also working!
Thanks for doing this!
wow. You have really outdone yourself here..... Considering this device didn't even had an untethered recovery at one point this is BIG!.... this opens up a lot more possibilities now for this tablet.... buddy you deserve recognition here
n30wav3 said:
wow. You have really outdone yourself here..... Considering this device didn't even had an untethered recovery at one point this is BIG!.... this opens up a lot more possibilities now for this tablet.... buddy you deserve recognition here
Click to expand...
Click to collapse
It really is impressive how far this device has come. For a long while I was willing to accept that despite the unlocked bootloader, we would be stuck with ZenUI for the future.
Hi, i try boot in TWRP - error Failed to execute recovery (\android.efi): Unsupported, reinstall TWRP - it s work
Skyrimus said:
Hi, i try boot in TWRP - error Failed to execute recovery (\android.efi): Unsupported, reinstall TWRP - it s work
Click to expand...
Click to collapse
So is everything working now? This could happen if you use a really old recovery and/or your (recovery) partition is corrupted.
will be possible to boot windows on the go (portable windows 10) from micro sd or a usb? maybe with a powered hub? (I made one with a normal hub, a diode and a usb cable and works as a charm)
f35suarezj said:
will be possible to boot windows on the go (portable windows 10) from micro sd or a usb? maybe with a powered hub? (I made one with a normal hub, a diode and a usb cable and works as a charm)
Click to expand...
Click to collapse
It's very much possible, but it won't work well at all due to the missing drivers.
errors flashing
I have root access on the tablet but believe the bootloader is still locked & i was trying to load your bootloader.
I am having issues.
When I press Volume Down & Power I do not get a recovery menu but rather the tablet boots in an Android Safe mode. There are a limited number of apps available and the table has the word "Safe mode" at the bottom of the screen.
If instead I press Volume Up & power i get a different menu that includes Normal Boot, Power Off, Reovery Mode then Restart Recovery
At the bottom of the tablet in Normal Boot it says "FASTBOOT CMD WAITING...."
I can see the tablet with fastboot devices but get errors when I try "fastboot flash ESP esp.img"
D:\Asus Memo Pad 7>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.601s]
writing 'ESP'...
FAILED (remote: flash_cmds error!
)
finished. total time: 2.401s
On the tablet it says :
NORMAL BOOT
FASTBOOT MODE
PRODUCT_NAME - K01A
VARIANT - K01A
HW_VERSION - (blank)
BOOTLOADER VERSION - unknown
IFWI VERSION - 64.33
SERIAL NUMBER - 0123456789012345678
SIGNING - ?
SECURE_BOOT - ?
FASTBOOT CMD WAITING.......
I do not remember how I rooted the tablet but obviously it cleared the serial number and input a new one.
Is there anything else I might provide that might allow you to assist me?
jziggy101 said:
I have root access on the tablet but believe the bootloader is still locked & i was trying to load your bootloader.
I am having issues.
When I press Volume Down & Power I do not get a recovery menu but rather the tablet boots in an Android Safe mode. There are a limited number of apps available and the table has the word "Safe mode" at the bottom of the screen.
If instead I press Volume Up & power i get a different menu that includes Normal Boot, Power Off, Reovery Mode then Restart Recovery
At the bottom of the tablet in Normal Boot it says "FASTBOOT CMD WAITING...."
I can see the tablet with fastboot devices but get errors when I try "fastboot flash ESP esp.img"
D:\Asus Memo Pad 7>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.601s]
writing 'ESP'...
FAILED (remote: flash_cmds error!
)
finished. total time: 2.401s
On the tablet it says :
NORMAL BOOT
FASTBOOT MODE
PRODUCT_NAME - K01A
VARIANT - K01A
HW_VERSION - (blank)
BOOTLOADER VERSION - unknown
IFWI VERSION - 64.33
SERIAL NUMBER - 0123456789012345678
SIGNING - ?
SECURE_BOOT - ?
FASTBOOT CMD WAITING.......
I do not remember how I rooted the tablet but obviously it cleared the serial number and input a new one.
Is there anything else I might provide that might allow you to assist me?
Click to expand...
Click to collapse
I'm afraid this package is for the ME176C (also named K013), not for the K01A. Now theoretically this doesn't mean anything, because the bootloader itself does not have any device specific code.
But given that you get an error trying to flash the "ESP" partition it is possible that your tablet never received the UEFI update (usually introduced with the update to Android 5.0). The bootloader only works on UEFI systems.
I've been having an overheating device and serious battery drain lately, is there any possibility it's related to this new bootloader? It's unlikely I know, just trying to eliminate all possible causes.
seamo123 said:
I've been having an overheating device and serious battery drain lately, is there any possibility it's related to this new bootloader? It's unlikely I know, just trying to eliminate all possible causes.
Click to expand...
Click to collapse
That's unlikely. The bootloader doesn't do much except load the kernel and then hands over all control to it. It doesn't run except very early in the boot process.
Wow, kudos. It's really nice how painless this was to install (and then to install the LineageOS you also provided)!
me176c-boot 0.2.0
Redesigned charger detection: There is now an additional charger boot option that is automatically selected when the device is started due to charger insertion.
This allows customizing the boot target in this situation. Examples:
Boot into charger from stock ROM while having a custom ROM installed (in my experience it still charges slightly better with less heat): See "Using the stock charger".
Always boot into main OS: See "Booting into main OS on charger insertion"
android-efi 0.2.0:
Boot Android images from files instead of just partitions.
Pass additional kernel parameters
systemd-boot-me176c 239.0:
Boot images from other partitions on the internal storage.
This is mainly useful for dual booting, because the main EFI System Partition (ESP) is very limited in its size (only 16 MB).
Download: esp-0.2.0.zip
Note: Upgrading wipes all custom boot configurations. (You don't need to worry about this unless you have manually made changes to the bootloader configuration...)
lambdadroid said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
me176c-boot is a custom, unlocked bootloader for the ASUS MeMO Pad 7 (ME176C/X). Designed to be simple and flexible, it can boot into Android and/or Linux (coming soon).
me176c-boot is a combination of systemd-boot (a simple UEFI boot manager) and android-efi (a simple Android bootloader).
Features
Boot into Android, Recovery and Fastboot
Unlocked bootloader, can boot into custom ROMs
Completely open-source and custom built for ASUS MeMO Pad (ME176C/X)
Flexible configuration to add further boot targets (e.g. Linux dual boot - coming soon)
Download
Latest release: esp-0.2.0.zip
Older releases: Available on GitHub
Installation
Make sure you are running Android Lollipop (5.0).
Extract esp.img from the downloaded ZIP.
Make sure you have Fastboot installed.
Boot the tablet into Fastboot mode: On the stock ROM, press "Volume Down" + "Power", and release the "Power" button once the backlight turns on.
Connect the tablet to your PC, and verify that it shows up when running "fastboot devices"
Flash the new EFI system partition extracted from the downloaded ZIP: "fastboot flash ESP esp.img"
Usage
By default, the bootloader will boot into the main Android system. You can recognize the bootloader by the green Android robot that is shown on boot.
Press "Volume Down" while booting to show the boot menu. Navigate through the menu with the "Volume Down" key. Press "Volume Up" to select an option. The "Power" button is not working inside the boot menu.
Configuration
It is possible to add additional boot targets using additional configuration files. You can access the configuration files from Recovery, go to "Mount" and select "EFI System Partiton (ESP)". Then you can access the ESP using ADB at /esp.
Here are some links with more information how to configure the bootloader:
systemd-boot on ArchLinux Wiki
android-efi README
Using the stock charger
You may want to use the stock ROM for (offline) charging since it charges a bit more efficiently (withless heat being generated). Ideally, this would be fixed directly in the custom ROM, but until then itis possible to configure the bootloader to use the stock boot image when booting into charging mode:
Download the stock ROM (UL-K013-WW-12.10.1.36-user.zip) and the updated charger boot configuration (charger.conf)
Extract boot.img from the downloaded ZIP.
Boot into Recovery, go to Mount and select EFI System Partition (ESP).
Connect the tablet to your PC, and verify that it shows up in adb devices.
Code:
adb push boot.img /esp/asus-charger.img
adb push charger.conf /esp/loader/entries/charger.conf
That’s it! When you plug in the charger the next time it should boot into the stock charger UI. Yay!
Booting into main OS on charger insertion
If you want to disable the separate charging mode on your tablet and always boot into the main OS,you can simply copy the primary boot configuration, and use it for the charger as well:
Boot into Recovery, go to Mount and select EFI System Partition (ESP).
Connect the tablet to your PC, and verify that it shows up in adb devices.
Download the configuration for your primary boot configuration (e.g. android.conf):
Code:
adb pull /esp/loader/entries/android.conf
Rename it to charger.conf.
Open it in a text editor and change the title to Charger.
Copy it back to your device:
Code:
adb push charger.conf /esp/loader/entries/charger.conf
Troubleshooting
In some cases booting may fail or you make a mistake during the installation. In this case, first power off the tablet by holding the "Power" button until it turns off.
Recovery
Even with the bootloader entirely broken, you can still boot into Fastboot mode using the rescue mode ("DNX mode").
Download the stock ROM (UL-K013-WW-12.10.1.36-user.zip)
Extract "esp.zip" and "droidboot.img" from the downloaded ZIP.
Extract "EFI/Intel/efilinux.efi" from "esp.zip".
Press "Volume Up" + "Volume Down" + "Power" until "Fastboot starting..." shows up on the display.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
XDA:DevDB Information
me176c-boot - Custom, unlocked bootloader for ASUS MeMO Pad 7 (ME176C/X), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev/me176c-boot
Version Information
Status: Beta
Created 2018-04-20
Last Updated 2018-09-24
Click to expand...
Click to collapse
For more than a week, I have been trying to reverse from lineage 14 to the asus firmware .36 whit TWRP 3.02.-0
. I get this error:
Could not find META-INF/com/google/android/update-binary in the zip file.
What im doing wrong?
RichardCooper said:
For more than a week, I have been trying to reverse from lineage 14 to the asus firmware .36 whit TWRP 3.02.-0
. I get this error:
Could not find META-INF/com/google/android/update-binary in the zip file.
What im doing wrong?
Click to expand...
Click to collapse
This is not related to me176c-boot, and it seems like you are not using one my TWRP builds either. Please open a separate thread here: https://forum.xda-developers.com/memo-pad-7/help
me176c-boot 0.3.0
Tip: Using the ASUS stock charger for offline mode charging is a great way to be able to charge at any time, even when the current ROM is in a non-bootable state. It also charges a bit more efficiently than the LineageOS ROM.
me176c-boot 0.3.0 contains major improvements and new features in all three of its components. Some of the new features will be required for future versions of the LineageOS ROM, however, booting the stock ROM is still supported.
me176c-bootstrap 0.3.0:
Moved some device specific code from the kernel to the bootloader
Technical details: https://github.com/me176c-dev/me176c-acpi#global-nvs-area
android-efi 0.3.0:
Added option to load additional init ramdisks (initrd)
systemd-boot-me176c 241.0:
Updated to systemd-boot v241
Added custom "android" loader type that makes it possible to write nicer boot configurations using android-efi
Example: https://github.com/me176c-dev/android-efi#systemd-boot
Download: esp-0.3.0.zip
Note: Upgrading wipes all custom boot configurations. For example, if you have been using the stock offline charger option, you will need to re-install it after installing this update.
Had zero issues getting it installed on my tablet. I look forward to seeing how linux runs on this as well! thanks
Succesfully flashed the latest esp and re-installed stock charging.
Thx!
I'd appropriate it, if anyone would be willing to help me out with my issue.
I have a LG G2 D801, 32GB.
Had it ROOTED, TWRP Recovery, and Lineage OS 14.1 running perfectly just fine. Until I recently tried to Flash Lineage OS 15.1, which then caused my phone to completely go into a black screen with a dead Android Robot having a exclamation point in a red triangle coming out of it's belly.
Yes, I'm able to get into: Android System Recovery <3e> LRXX22G
- Tried, Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Data/Factory Reset, then Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Last but not least, leaving me with the only real option I have left to help fix my phone is the, Apply Update From ADB. (Yes, I tried that one too) Which is why I need your help!
Here's a quick scenario of what happens after trying that last option. (Apply Update From ADB)
-Basically my phone then asks me to ADB Sideload files.
-I connect my phone to my PC. (Windows 7, x64)
-Check my Device Manager to see if it's fully connected, but my D801 connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface. (which I know has to be wrong)
-I go into my CMD Prompt, to access my installed ADB Shell, to search for attached ADB Devices. (Yes, it sees my phone as: LGD801cb55c4e4 sideload)
-I proceed to try to sideload a ROM and after about 30% Signature Verification, Fails causing my D801 to Abort Installation. (no matter what I throw at it, IMG/KDZ/TOT files fail as well.)
Now when it comes to trying the methods listed in: https://forum.xda-developers.com/showthread.php?t=2432476 to Flash Stock Firmware, I simply can't because my D801 doesn't connect to my PC in Device Manager under Ports or QHSUSB_BULK. (it connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface.
I've also tried SRKtool_2.1_droidth which ends up leaving me at another dead end.
If you have the time please help, and or point me in the right direction.
I've already installed the needed drivers:
qualcomm-driver
adb-setup-1.4.3
LGMobileDriver_WHQL_Ver_4.2.0
Downloaded all the corresponding files to my PC for my D801:
Firmware Files (KDZ & TOT also Extracted)
LG Flash Tool 2014 & 2015
SRKtool_2.1_droidth
Megalock DLL File
D801 DLL File
LGUP
Silly suggestion perhaps, but after freaking out for about an hour when this happened to me I ended up realizing I could reboot to TWRP using the hard keys. Honestly, I only mention it because I was trying everything else too. If you didn't already try it (I didn't see it in your description) I think it's the power key and volume down key while it's off and as soon as you see the splash screen, release them both and immediately repress and hold them both until you see TWRP. Just a thought.
I loved that phone!
Sent from my [device_name] using XDA-Developers Legacy app
Just tried your technique @C-Tec. Thank you. But that only brings up the Factory Data Reset Screen (to Erase all user data & Restore default settings) instead of the TWRP Recovery screen. (so that's a dead end)
Because, after selecting Yes, Erasing data and Restoring default settings, my phone reboots in to the same loop I started from, as if I never did anything to remedy the situation.
Update on my progress:
-So I was able to get in to Download Mode. (holding the VOLUME UP button, while the phone is off)
-Followed by the Firmware Update Screen after plugging my phone in to my PC via USB. (which then read my phone as - LG Mobile USB Serial Port. (COM8) under Ports in Device Manger)
-I then Flashed the D801 Stock Lollipop KDZ. (by using the LG Flash Tool 2014)
-Waited for the progress bar to completely fill to 100% and BOOM! I fixed my problem.
-Android Lollipop running like NEW. (that's 2014 NEW :crying
-Now to retry Lineage OS 15.1.
Here's a helpful Video Clip, to understand how to use the Flash Tool. -
Just search for: LG G2 - Fix LG Logo Stuck/ Boot Loop Fix / Flash Firmware - EASY METHOD in YouTube.
Being that I'm low ranked I cant post any links just yet, sorry.
I even went out of my way and ordered a LG V20 off of Swappa, which arrives tomorrow. Due to this issue.
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
DOWNLOAD
TWRP 3.2.3.0
Flashing Instructions
Make sure you have fastboot drivers installed and your bootloader is unlocked
Download the file
In fastboot open the directory of downloaded file and type
fastboot flash recovery recovery.img, after that type
fastboot oem reboot-recovery, You'll have a black screen on your display wait for 5-10s you'll be greeted with TWRP screen if you still didn't get the screen then press power button 2-3 times
BUGS
Data decryption ( For this you need to select Wipe -> format data (You'll lose all your data in this process) )
No Battery% ( I purposefully disabled it as the battery% always stays at 50% so I'll find the battery% path and fix this in the next build)
Flash force encrypt disabler in recovery to fix magisk module installation and other data partition related issues.
Source Code: TWRP source, Device Tree and Kernel Source
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
pankajyadav_18 said:
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
Click to expand...
Click to collapse
By reboot problem if you mean, the phone getting restarted randomly in loop then the only way to fix it is to go to the service center.