Dear friends,
I have a recovery bootloop problem with my Op6t European version.
On this week I made an OTA update (11.1.1.1 version) with magisk app. I made with install to inactive slot (after OTA) version.
After this process my phone was reboot and got a recovery bootloop. I have never been in this situation although I made more update with this process.
After that I tried to make wipe cache and reset system settings but it was not succes.
I tried to read forum threads where somebody also has this problem. I found a thread where somebody use fastboot and change slot to use phone temporaly. It's also working for me on but I would like to repair that.
Can I get back my old system with my data? How can I make some solution?
Sorry for my bad english.
UPDATE:
Yesterday I tried to reflash the stock rom with adb sideload , but absolutely does nothing in this case.
I am also having this issue. Can someone point me in the right place for a fix?
Related
I have a LG G2 D802 international SIM unlocked version. I purchased it from Amazon UK and currently I was using it in INDIA.
The phone came with KITKAT 4.4.2 pre-installed in it. I rooted the phone using Cloudy's method of Autorec by downgrading my kernel.
The phone was rooted successfully and I was on stock rom. I also installed TWRP recovery successfully.
The problem arose when the phone automatically started updating today. It downloaded a new software version of size 139MB(approx) and promised to enhance APPS(only). I was not aware of the fact that this shall not be done and I agreed to update the phone. As soon as the phone restarted it automatically booted into TWRP recovery. Since then it keeps on rebooting into TWRP recovery mode, whenever I reboot it from TWRP recovery.
I tried wiping data, formatting data, system everything I could get my hands on. Nothing worked. The sad part is I did not take a back up of my stock rom. Now, I have lost all my data and the phone just wont boot into system. What do I do now? Can anyone please suggest me something? I would be really really grateful.
If I have posted this in the wrong section or violated any of the rules in the forum, I beg moderator's pardon.
Update: I am extremely sorry for not searching the forum (Since I was not aware of the term OTA) . I found this guide and it helped me. I finally can boot into my phone
Link to Guide : http://forum.xda-developers.com/showthread.php?t=2451696 [Credits: thecubed]
I finally can rest in peace.
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
A short history:
I had been using my phone on B20 rooted/locked with tenfar's tool for about 3 months now, and decided I would try and update it finally before the new year.
To update it, after reading it seemed I would need to unlock the bootloader to keep root on B29 so I decided first step would be to unlock the bootloader and then update to B29. I did the following steps today
1) Unlock bootloader using DrakenFX's guide here http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 The unlocked proved successful and I was able to boot back into B20 after all the data was wiped, and I followed the instruction to backup the Boot in TWRP. All good.
2) I then decided to follow another of DrakenFX's guides (https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2) to update from B20 to B29. I followed the instructions exactly again, but then the phone just hangs on the ZTE logo on boot infinitely. I wondered if I made a mistake when re-initializing TWRP after unlocking the bootloader. I did a search and found in "Mount" to uncheck "Mount system partition read-only" and unchecked it. The System partition however is unmounted, I'm not sure if that's normal now or not. Even when I check it, after rebooting it goes away. I've checked the MD5 of the ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip file and it's good. I then flashed through fastboot to the new 3.0.3-0 TWRP which I'm now using, and still nothing. It appears I don't have an OS installed. I'm going to guess here the issue is with a setting in TWRP but I've tried everything I could find. Unfortunately I don't seem to have a copy of my stock recovery right now to flash either. I've tried several times to flash ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip and reboot but to no avail. I even tried this tip from rczrazor to delete DATA first and others one by one (https://forum.xda-developers.com/showpost.php?p=69428659&postcount=136) but no such luck for me. Still stuck on the ZTE logo.
tl;dr - I have access to fastboot and TWRP, but apparently no ROM installed even though have flashed now multiple times.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
shyguy88 said:
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
A short history:
I had been using my phone on B20 rooted/locked with tenfar's tool for about 3 months now, and decided I would try and update it finally before the new year.
To update it, after reading it seemed I would need to unlock the bootloader to keep root on B29 so I decided first step would be to unlock the bootloader and then update to B29. I did the following steps today
1) Unlock bootloader using DrakenFX's guide here http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 The unlocked proved successful and I was able to boot back into B20 after all the data was wiped, and I followed the instruction to backup the Boot in TWRP. All good.
2) I then decided to follow another of DrakenFX's guides (https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2) to update from B20 to B29. I followed the instructions exactly again, but then the phone just hangs on the ZTE logo on boot infinitely. I wondered if I made a mistake when re-initializing TWRP after unlocking the bootloader. I did a search and found in "Mount" to uncheck "Mount system partition read-only" and unchecked it. The System partition however is unmounted, I'm not sure if that's normal now or not. Even when I check it, after rebooting it goes away. I've checked the MD5 of the ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip file and it's good. I then flashed through fastboot to the new 3.0.3-0 TWRP which I'm now using, and still nothing. It appears I don't have an OS installed. I'm going to guess here the issue is with a setting in TWRP but I've tried everything I could find. Unfortunately I don't seem to have a copy of my stock recovery right now to flash either. I've tried several times to flash ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip and reboot but to no avail. I even tried this tip from rczrazor to delete DATA first and others one by one (https://forum.xda-developers.com/showpost.php?p=69428659&postcount=136) but no such luck for me. Still stuck on the ZTE logo.
tl;dr - I have access to fastboot and TWRP, but apparently no ROM installed even though have flashed now multiple times.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
Click to expand...
Click to collapse
This happened to me once - boot to TWRP, format data, reboot to TWRP, advanced wipe everything but the external SD card,reboot to TWRP, flash DrakenFX B29 bootstack, reboot to TWRP, flash DrakenFX B29 system.
shyguy88 said:
Hi everyone, sorry for a noob problem but I seemed to have soft bricked my phone and was hoping that somebody here would be able to help me out. I have an A2017U in the US.
If anybody could help me I would greatly appreciate it. I'm even willing to pay a few bucks in Paypal to help get me going again.
Thank you all in advance.
Click to expand...
Click to collapse
I have bricked my AXON 7 many times during the last week. The Zip files from DrakenFX are very good. But in case those were still failling...
First, check for corrupted downloads, just check the zip file integrity using 7zip, winRAR or any other tool.
Use TWRP 3.0.3
Try a different ROM such as ZADMix or even CM13.
If everything fails:
Flash TWRP 3.0.2 signed.
Flash the original Stock B29 Boot partition and reboot to recovery
Flash again the verified DrakenFX files.
I was from LineageOS 14.1 and I saw a post where the Nougat update has been pushed. Decided to flash A2017U B29 and it worked fine but when I tried to update, it said failed to update. So decided to reinstall the B29 rom again, and it still failed. So I decided to flash back to my stock rom which is A2017G and my phone is now stuck at the ZTE Boot logo. Waited for more than 40 minutes, still stuck there. Decided to go back to recovery and it seems that my TWRP recovery is no longer there. Only able to go back to stock recovery. Tried factory reset, wipe cache and reboot, still stuck on boot logo. Is there any way to fix this? Basically new to Android so dont really know what I'm doing. Just following tutorials that are in this forum. Pretty much f*cked up right now. Would really appreciate if anyone could help in details as Im new to this Android scene.
MahathirMohamad_ said:
I was from LineageOS 14.1 and I saw a post where the Nougat update has been pushed. Decided to flash A2017U B29 and it worked fine but when I tried to update, it said failed to update. So decided to reinstall the B29 rom again, and it still failed. So I decided to flash back to my stock rom which is A2017G and my phone is now stuck at the ZTE Boot logo. Waited for more than 40 minutes, still stuck there. Decided to go back to recovery and it seems that my TWRP recovery is no longer there. Only able to go back to stock recovery. Tried factory reset, wipe cache and reboot, still stuck on boot logo. Is there any way to fix this? Basically new to Android so dont really know what I'm doing. Just following tutorials that are in this forum. Pretty much f*cked up right now. Would really appreciate if anyone could help in details as Im new to this Android scene.
Its 12.29am now from where Im from. Hopefully someone can help me fix this issue before I go to work later in the morning ( Need to wake up at 5.30am ).
Click to expand...
Click to collapse
Join this hangouts goypr, someone is going to help you there for sure
Join the conversation on Hangouts: https://hangouts.google.com/group/QJg5USoboVbcA7eE2
Did you get this resolved?
I think the problem is caused by flashing the US version bootstack to a none US version phone. It's relatively ok to flash the system/kernel, but flashing other partitions is asking for trouble.
gpz1100 said:
Did you get this resolved?
I think the problem is caused by flashing the US version bootstack to a none US version phone. It's relatively ok to flash the system/kernel, but flashing other partitions is asking for trouble.
Click to expand...
Click to collapse
So do you know how to fix it?
Did you try to flash twrp recovery?
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Check this thread can help you to restore to stock firmwares anytime and even update ur phone.https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page44
jkrz said:
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Click to expand...
Click to collapse
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
So i've gotten my phone working again (with the chinese ROM) but since TWRP won't work there's no way for me to rebrand it. My phone has eMMC 5.0 if that's any help.
MosquitoByte said:
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
Click to expand...
Click to collapse
can you share the TWRP works in eMMC plz . many thanks
Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Misce said:
Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Click to expand...
Click to collapse
Bro stick with stock you got a nice expensive phone you don't need to chance messing it up
Thot Conqueror
Misce said:
Greetings everyone,
today I purchased a new G950F S8. Immediately I wanted to root the device, and in order to do so - installed TWRP via Odin 3.13.3 (flashed the newest version for Exynos models downloaded from their web-site). The flashing process went through fine - everything checked out, at least seemingly.
When I first restarted my phone (followed the instruction), it booted up in it's default recovery, NOT TWRP recovery. That seemed strange, so I double checked the instruction - which claimed I need to quickly boot into recovery, as soon as the flashing process is done and the phone is first restarted. Maybe I was slow.. I re-flashed TWRP, and this time it booted into TWRP. Now, this is when the problem started.
I didn't touch anything within TWRP, I was just satisfied to see it installed. When I tried to restart into System, I got the Samsung logo bootloop. I couldn't power off the phone, nor could I boot it up. I could, however, alternate between download mode and TWRP. I tried changing System format and then changing it back to original (saw that somewhere), but it didn't help. Tried factory reset without results.
Finally I downloaded official stock ROM for Italy, flashed via Odin and everything works fine.
Thing is - I really want to root my phone. Had no issues with my Note 3 previously. I wouldn't want to get into more trouble, so I'm kindly asking for some advice, or a useful link (I searched all over but didn't find anything that would make me feel confident enough not to screw it up again) to how I can do this safely.
I'm using Android 9, official stock ROM for Italy.
Click to expand...
Click to collapse
When you first flash twrp and boot into twrp you have to format phone from within twrp, then flash no Verity zip and rmm bypass zip. If you reboot system before you format then you get bootloop. There is full instructions in a thread here on XDA.