[Q] How to install recovery in a phone which can't start - Xperia SP Q&A, Help & Troubleshooting

Hello everyone.
I don't know what happened but my device entered in the infamous bootloop. I tried to erase cache, partition, reinstall a rom, install a different rom and nothing.
My true problem is that last night I made a horrible mistake: I erased everything including my SD card, which contained the data for boot to recovery. Right now I can only see the SONY logo when I power up my device and nothing else.
I tried to install recovery via fastboot flash boot boot.img but I can't keep my device in fastboot. I mean, I connect my device and hold Volume Up but after a few seconds it continuous to the SONY logo and stays there forever.
Am I missing something? What can I do to reintall a recovery if I can't access my phone data?
Thank you.

How to install recovery in a phone which can't start [Solved]
I just figured it out! I installed Sony's stock rom following this guide and my phone is alive again.

bbabel said:
I just figgured out! I installed Sony's stock rom following this tutorial and my phone is alive agaoin.
Click to expand...
Click to collapse
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can

kwitu said:
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
Click to expand...
Click to collapse
Thank you. I just fixed the link and now it works.

Related

Stuck in boot Please advice

Hi all you clever guys I need your help!
Yesterday I decided to try making myself a new theme for my O2X and now I'm stuck in boot.
I have flashed my phone many times before but now I feel like an idiot.
Please advice me on how to save my phone.
After making the theme using a theme generator I found here on XDA I installed the zip file via Recovery mode and booted my phone. It then looped in the LG startup image.
I wiped the phone and ran back up in Recovery mode then tried rebooting but no luck.
I have also tried to flash with my last used Custom ROM but the phone is now stuck in boot and only shows the screen with the LG logo and process bar.
Please advice me on what I can do to save my phone.
On top of it all I have a problem with my PC so I can not install the LG PC suite SW and can not connect my phone to the PC via USB.
Why on earth did I do this....
Dont worry at all, are you sure you have wiped your data and cache partition? Do this and then flash some ROM (can recommend latest CM7 build).
If its a no go, you can always flash original firmware with nvflash (there's a tutorial for this, just look it up)
Hope I helped
All you need to do is reflash the current rom you are using now without a wipe and that will fix you problem.
If you get bootloop from something you have just flashed just reflash the current rom without a wipe and that will fix ya problem, for next time hey????
Can you get in to recovery??
Hi
Thanks for your inputs and help! Currently downloading NVFlash on my PC and will try it out.
Yes I can enter recovery by pressing vol down key and power button at the same time. (thank Good for that!)
do a full wipe in recovery and flash the rom of your choice, just make sure you have the correct ext 3 or 4 or you will get bootloop

New ROM Gone Wrong!

Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
I hope you're not also flashing any of the custom kernels on here....cos they're not compatible with 4.2.2
Nope not flashing anything else but the ROM itself..
after flashing did you try "fastboot erase cache" ?
sometimes that helps when phones get stuck on the HTC logo after a rom flash.
Use the toolkit to erase cache
Sent from my HTC One using xda premium
Yeah done that several times too. Can't seem to work out why it isn't working and I too can't find the correct RUU for my device meaning I can't even take it back to stock
try to hold power + volume down to get into the bootloader to get back into recovery. Once in recovery factory reset, erase cache, erase dalvik, and reflash the rom.
also download the andorid SDK for fastboot and adb, then try "adb reboot bootloader" if you can not get back into the bootloader to get into recovery
My friend had his do this loop as well, we had trouble getting it into recovery, but held the button combo of power and vol down several times (probably 10) and it FINALLY booted into the custom Clockwork recovery, then we reflashed and it worked like a charm.
Also try redownloading... it could be a bad download
Sent from my Nexus 10 using Tapatalk HD
rilee said:
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
Click to expand...
Click to collapse
Just a word of advice. Update your profile to say your country and carrier. It helps people identify which device model and carrier you use.
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
rilee said:
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
Click to expand...
Click to collapse
I would be restoring my nandroid backup and make sure the phones that way first and then start again
Thanks again for the help guys, went to phones 4 u this afternoon and he exchanged the device for me.

[Q] My SP is now a brick. Help please!

Hi! After reading a lot of post on the Internet, I decided to install CM11. I root the SP with TowelRoot, installed CWM and create a back up, then I wipe cache, dalvick cache, and I wipe data. Everything was working fine. Now, I install CM11 from a zip, and then Google Apps, no errors were shown. I reboot the phone, and here was the problem, it shut down, but never turn on again. Even if i push the on button, it doesn't do anything. If i push vol down while I push the turn on button, i get a green light for a second, but nothing new happens. I f I do the same, but pushing vol up button, i get a blue light.
Please, Could you help me to get my phone working again?
Ivan_0013 said:
Hi! After reading a lot of post on the Internet, I decided to install CM11. I root the SP with TowelRoot, installed CWM and create a back up, then I wipe cache, dalvick cache, and I wipe data. Everything was working fine. Now, I install CM11 from a zip, and then Google Apps, no errors were shown. I reboot the phone, and here was the problem, it shut down, but never turn on again. Even if i push the on button, it doesn't do anything. If i push vol down while I push the turn on button, i get a green light for a second, but nothing new happens. I f I do the same, but pushing vol up button, i get a blue light.
Please, Could you help me to get my phone working again?
Click to expand...
Click to collapse
The ROM you flashed isn't working then. If it shows a bootlogo it means that it doesnt work but if it doesnt then it means you haven't UNLOCK you bootloader which stops installation of CM ROMs. Read the guide I created here to recover: http://forum.xda-developers.com/xperia-sp/general/root-ultimate-noobs-guide-to-rooting-t2845520
Furrydaus said:
The ROM you flashed isn't working then. If it shows a bootlogo it means that it doesnt work but if it doesnt then it means you haven't UNLOCK you bootloader which stops installation of CM ROMs. Read the guide I created here to recover: http://forum.xda-developers.com/xperia-sp/general/root-ultimate-noobs-guide-to-rooting-t2845520
Click to expand...
Click to collapse
Thank for the answer, I'm gonna check the guide. No logo is shown on the screen, it is completely black. My bootloader was unlocked.
i had the same problem once, try to flash a stock ftf rom with pc companion.. keep calm and you will fix it
edit.. not with pc companion with flash tool you do it..
Ivan_0013 said:
Thank for the answer, I'm gonna check the guide. No logo is shown on the screen, it is completely black. My bootloader was unlocked.
Click to expand...
Click to collapse
have you tried flashing boot img with fastboot if not try that it might help
Ivan_0013 said:
Hi! After reading a lot of post on the Internet, I decided to install CM11. I root the SP with TowelRoot, installed CWM and create a back up, then I wipe cache, dalvick cache, and I wipe data. Everything was working fine. Now, I install CM11 from a zip, and then Google Apps, no errors were shown. I reboot the phone, and here was the problem, it shut down, but never turn on again. Even if i push the on button, it doesn't do anything. If i push vol down while I push the turn on button, i get a green light for a second, but nothing new happens. I f I do the same, but pushing vol up button, i get a blue light.
Please, Could you help me to get my phone working again?
Click to expand...
Click to collapse
the good news is: you're able to see thr green & blue light, you can flash stock rom via flashtool, but you'll lose all data
Problem solved
Thank you all for your help, finally I could solved the problem flashing the stock rom with FlashTool
There you go.
Unless you're having hardware issues, there's no such thing as a fully bricked Xperia SP.
Hey,I would like to get back to stock.
Rom:Crystal pa 4.4.4
Bootloader;Unlocked
Kernel:The one that came with the rom.
Device:Xperia Sp C5302
Can I directly flash the update via pc companion/or do I need to use flashtool to decrypt the files?
A detailed explanation would be appreciated.Please reply ASAP.
Thanks!
Check the link
xperiaSP1995 said:
Hey,I would like to get back to stock.
Rom:Crystal pa 4.4.4
Bootloader;Unlocked
Kernel:The one that came with the rom.
Device:Xperia Sp C5302
Can I directly flash the update via pc companion/or do I need to use flashtool to decrypt the files?
A detailed explanation would be appreciated.Please reply ASAP.
Thanks!
Click to expand...
Click to collapse
You have a detailed explanation in the reply that Furrydaus made to me, at the top of the post. If you follow his guide, you will see that reparing your xperia is quite easy
Ivan_0013 said:
You have a detailed explanation in the reply that Furrydaus made to me, at the top of the post. If you follow his guide, you will see that reparing your xperia is quite easy
Click to expand...
Click to collapse
Haha yes. Thanks for the compliments!
Sent from my Xperia SP using XDA Premium 4 mobile app
stuck on bootloop
I did the following and now phone is just stuck in bootloop , Any and all help is welcome, just help
Unlocked the bootloader succesfully using fastboot
flashed cm11 boot.img using fastboot
installed cm11 using adb sideload
After all this, my phone got stuck in boot animation (arrow circling a head)
I was able to reboot in recovery and wipe cache, wipe dalvik cache but when trying to wipe data/ factory reset and got an error mounting message and skipped formatting.
Then i tried reflashing the zip as well reflashing the boot.img file.
Thankyou for reading and replying.
flash a new boot.img
defy313 said:
I did the following and now phone is just stuck in bootloop , Any and all help is welcome, just help
Unlocked the bootloader succesfully using fastboot
flashed cm11 boot.img using fastboot
installed cm11 using adb sideload
After all this, my phone got stuck in boot animation (arrow circling a head)
I was able to reboot in recovery and wipe cache, wipe dalvik cache but when trying to wipe data/ factory reset and got an error mounting message and skipped formatting.
Then i tried reflashing the zip as well reflashing the boot.img file.
Thankyou for reading and replying.
Click to expand...
Click to collapse
I got a similar error last week. To solve it, i put the phone in fastboot mode. Then, i flash the boot.img from cm11(at least, I think that was that) using flashtool. Doing this i finish the bootloop. Then i flashed the stock rom again, and all problems were solved.

[Q&A] [RECOVERY] TWP 2.7.1.0 for One Mini 2

Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!

Bootlooping

I have a Samsung galaxy note 9 sm,-n960f with TWRP 3.2.3 Cowrite unofficial recovery. I backed up my phone. But when I tried to restore the backups I got an error message. So I decided to TWRP 3.3.1. It was successfully flashed. But when I booted into recovery, the phone just keeps recycling the flash screen without going into recovery mode. It has been doing this for the past two hours. Could someone please tell me what to do. I can't stop it. Please help.
Baluki2017 said:
I have a Samsung galaxy note 9 sm,-n960f with TWRP 3.2.3 Cowrite unofficial recovery. I backed up my phone. But when I tried to restore the backups I got an error message. So I decided to TWRP 3.3.1. It was successfully flashed. But when I booted into recovery, the phone just keeps recycling the flash screen without going into recovery mode. It has been doing this for the past two hours. Could someone please tell me what to do. I can't stop it. Please help.
Click to expand...
Click to collapse
prepair to go back to dl mode to flash back twrp 3.2.3 tar with Odin.
hold bixby and vol down while plugging usb from computer in the phone.
time yourself that when see/feel the phone reboot to plug usb at that moment( while holding bxby + vol down)
btw did u flash twrp 3.3.1 using image option in twrp or did you flash it with odin?
I flashed it in trwp.
Baluki2017 said:
I flashed it in trwp.
Click to expand...
Click to collapse
dont flash it in twrp. also you might have chosen the wrong target partition... did u remember selecting recovery or boot?
A million thanks to you. I got it working again. I did exactly what you said and it worked like a charm.
The main issue that got me into this problem is the backups I created with this recovery. Whenever I tried to install them, I get an error. Is there something that I'm doing wrong?
When I had my note 3, I never had this problem. Is there a bug in this 3.3.2 i unofficial recovery. Could you tell me what to include in my backups and what to include in my restore.
Thank you for your assistance.
Baluki2017 said:
A million thanks to you. I got it working again. I did exactly what you said and it worked like a charm.
The main issue that got me into this problem is the backups I created with this recovery. Whenever I tried to install them, I get an error. Is there something that I'm doing wrong?
When I had my note 3, I never had this problem. Is there a bug in this 3.3.2 i unofficial recovery. Could you tell me what to include in my backups and what to include in my restore.
Thank you for your assistance.
Click to expand...
Click to collapse
3.3.1 based twrps are pretty much betas if you ask me . stick to good old 3.2.3-0
also when backing up various partitions. skip "system image". so check box any or all others including system but no need to select "system image" its not needed and cant be restored anyways.
Thanks again. I will try that.
Hello my friend. I need your help again. I just got myself in a big mess. I did a full wipe in recovery. Before I restored the backups , I accidentally rebooted the phone and now I am stucck in a black circle and a small white symbol inside the top side of the black circle.
I tried booting into download mode.so that I could rry to refalas the recovery please help help me.
Tank
Baluki2017 said:
Hello my friend. I need your help again. I just got myself in a big mess. I did a full wipe in recovery. Before I restored the backups , I accidentally rebooted the phone and now I am stucck in a black circle and a small white symbol inside the top side of the black circle.
I tried booting into download mode.so that I could rry to refalas the recovery please help help me.
Tank
Click to expand...
Click to collapse
hold:
vol down + power
the instant you see or feel phone shutdown really quickly hold:
vol up + bixby + power
if u miss it try again. timing is key.
Ok. I will do that.
Thanks again.

Categories

Resources