Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
SlimJ87D said:
Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
Click to expand...
Click to collapse
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
BWolf56 said:
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
Click to expand...
Click to collapse
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Could Fix Permissions fix the problem? It seems that the phone boots up to the home screen. While loading files, something at this point is causing it to bootloop. It will freeze after a few seconds and then reboot and repeat the problem.
Something is definitely conflicting within the first 30 seconds of booting up to the home screen. Any ideas?
SlimJ87D said:
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Click to expand...
Click to collapse
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
BWolf56 said:
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
Click to expand...
Click to collapse
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
SlimJ87D said:
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
Click to expand...
Click to collapse
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
BWolf56 said:
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
Click to expand...
Click to collapse
Thanks. Yes she's using an external SD card. I will have to get a hold of her phone and see what's going on. The first time it happened was because we upgraded to Jellybean. it happened right after so I don't think it was a rogue app. This time she just pulled her phone out of her purse and noticed it boot looping. Something sounds wrong with her phone... I think we might need to send it back for warranty repair.
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Now that I put fresh rom and cleared everything her phone was working. But the moment I rooted the phone itboddly didn't come with SU, so upon installing SU nothing could access SU for some odd reason. So I found out you need a SU for Jelly Bean, upon installing this version of SU is when everything went to he'll and the same boot loop came back.
Sent from my GT-I9300 using xda app-developers app
SlimJ87D said:
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Click to expand...
Click to collapse
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Alexandre-P said:
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Click to expand...
Click to collapse
Perhaps, I will try and fix the problem again. We just got back from a movie. Thank you.
if everything doesn't work
here's what you should do
first go look for AT&T 4.1.1 stock rom
download ODIN
go to recovery by vol up + power + home
clear cache, data and dalvik
flash stock rom thru odin.
that should fix soft brick
Related
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse
re: rebooting into Google Edition Rom
razorj7 said:
Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse
Click to expand...
Click to collapse
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!
Misterjunky said:
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!
Click to expand...
Click to collapse
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
Have you tried holding the power button, home key and the volume up key all at the same time to boot in recovery? If not do a battery pull and do it when turning the phone back on
Sent from my SGH-M919 using xda premium
razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
If you already tried to Odin flash the STOCK rom and formatted your internal sdcard and you still find "0 MB"
in your internal storage then it must be a hardware issue and if I were you I would return/exchange the phone.
Good luck!
It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.
teshxx said:
It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.
Click to expand...
Click to collapse
Thanks, I'll try that. How do I get rid of the bug after writing the new recovery? Format data?
Thanks!
Hello, any progress please? I have exactly the same issue.
I found here http://forum.xda-developers.com/showthread.php?t=2265588&page=23 this solution:
I wanted to clean my internal SD card before flashing Omega ROM, so I used Format Data option from Wipe section in TWRP.
After that I lost almost two days trying to fix my phone. Flashed stock ROM, TWRP and Omega ROM endless times without success after that.
My phone became randomly unbootable on reboot or power on! It was stuck on i9505 logo that is shown before boot animation forever. It was same for both stock and Omega ROM, with or without external micro SD.
After endless tries, I figured out that my phone works fine if I do factory reset and wipe from original recovery. Worked fine before and after flashing TWRP.
I tired to Format Data from TWRP again and my phone again was stuck on boot.
So I did everything once more. Flashed stock, did factory reset and wipe from original recovery and then installed TWRP and in the end I flashed Omega without wiping anything.
Everything works just fine now and I will not try to use Format data option from TWRP on this device in near time! Please fix this.
First I used TWRP 2.5.0.1 and then 2.5.0.2, but it is same in both of them.
Click to expand...
Click to collapse
Now I'm downloading stock rom so I'll try it in next 2 hours.
bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.
TheAxman said:
bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.
Click to expand...
Click to collapse
It says so in the OP... going between TW and Google Edition 2.0.. Out of curiosity though, what difference would that make? I have flashed and have backups of two versions of TW and quite a few AOSP variants... I can move between them seamlessly and haven't encountered any such problems as the OP. I use TWRP as well.
It was TWRP problem. I have flashed the stock ROM with stock recovery. I have done full wipe and my phone works well again. This is bug in TWRP. Don't push "format data" button!
I acidentaly formated data, so I had to LGNSPT to stock jellybean. I re-rooted and unlocked the bootloader. Later I decided I wanted to flash the venum rom so I booted into TWRP and I wiped both cache and dalvik-cache and factory rested by mistake because I wanted to make a backup. So when the wipe finished I did. I backed up the boot and system. Then I formated system and flashed the rom. Everything went smoothly, so I rebooted the phone and got stuck at the LG screen. I thought it was a bad flash, butI re-did the process multiple times. I did a restore which was the boot and system and that didn't work. While I was running out of options I just decided to reboot the recovery and it said I have to fix permissions for root and I thought that was the problem so I tried again. But it didn't workand everytime I tried I reboot the recovery it said I had to fix permissions over and over again. Is there a way I can fix this without a computer? Plz help.
If I have no other way of fixing the problem without a pc then tell me how I can fix my phone with one plz
Cjay1518 said:
I acidentaly formated data, so I had to LGNSPT to stock jellybean. I re-rooted and unlocked the bootloader. Later I decided I wanted to flash the venum rom so I booted into TWRP and I wiped both cache and dalvik-cache and factory rested by mistake because I wanted to make a backup. So when the wipe finished I did. I backed up the boot and system. Then I formated system and flashed the rom. Everything went smoothly, so I rebooted the phone and got stuck at the LG screen. I thought it was a bad flash, butI re-did the process multiple times. I did a restore which was the boot and system and that didn't work. While I was running out of options I just decided to reboot the recovery and it said I have to fix permissions for root and I thought that was the problem so I tried again. But it didn't workand everytime I tried I reboot the recovery it said I had to fix permissions over and over again. Is there a way I can fix this without a computer? Plz help.
If I have no other way of fixing the problem without a pc then tell me how I can fix my phone with one plz
Click to expand...
Click to collapse
LGNPST ZVB or teeny bins. Factory reset shouldn't wipe data.
Edit. My brain cramp. Without computer try another backup. Or., factory reset, then in advanced, tick all 4. Then do your restore.
Sent from my LG-LS970 using xda premium
format data
engine95 said:
LGNPST ZVB or teeny bins. Factory reset shouldn't wipe data.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I know I actually hit the option "format data" and wiped out my entire internal storage.
Cjay1518 said:
I know I actually hit the option "format data" and wiped out my entire internal storage.
Click to expand...
Click to collapse
Well... if you wiped /system and had already formatted /data, i don't think you can get it to boot without a computer. I didn't see /recovery listed in your restore and i think might be the issue.
Sent from my LG-LS970 using xda premium
---------- Post added at 09:51 PM ---------- Previous post was at 09:42 PM ----------
If you still have Twrp, try reflashing it. 2.6.0.0 just came out and octhrope made a flashable zip for it in the TWRP thread.
Sent from my LG-LS970 using xda premium
I just had a similar problem but for a different reason. My rooted and unlocked started acting funny by asking me to turn on GPS when it was already on. I rebooted and got the LG screen, never, never to get better. Sprint couldn't do anything so I got a new phone. I suspect it may be a battery issue, or a power issue where the handset does not have enough power to power up. I paid $50 for Sprint to fix my first one since I did not carry insurance. Might try working something similar.
Hey,
So im currently on holiday and dont get back home until the 13th aug.
I was on my phone last night until i ran out of battery and the phone inevitably died. I charge it this morning and the phone is stuck on the boot animation and has a slowly flashing blue led. I do get past the lg bootloader unlocked screen too and the android boot animation runs fine, just never completes. My phone is running bootloader unlocked, twrp recovery and the imperium rom. My model is h815 and s/n is 512 prefix. The battery was running pretty bad so it might be that. Either way it is stuck in bootloop and i am not sure how to approach it. I also have some internal storage that would need backing up if possible.
Cheers for any help
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
Thats interesting, never thought of that. I should be able to backup any files etc from the internal storage using adb right?
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
MattheewHun said:
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
Click to expand...
Click to collapse
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
jet399 said:
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
Click to expand...
Click to collapse
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
htr5 said:
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
Click to expand...
Click to collapse
Yeah i saw that post and was reluctant to do so as im on my holiday. Dont want to lose my pics either, even when im very sure twrp is installed correctly as i use the quick boot app to go into recovery quite often.