Recently I was using the phone normally , when the system locks up completely and gives reboot . He calls usually only that Android does not charge. When finished booting it restarts again.
I've tried to restore the recovery by the factory defaults, but it seems that is a problem because it does not restore .
I've tried also install another ROM , but the process takes more than 40 minutes and the old ROM is still there .
I'm using a ROM (for about 4 months) I downloaded from the site of sammobile.com
If anyone can help me , I would be grateful.
Related
Hello all hope you will be able to help me.
Device : Nexus S I 9020
So basicly iam kinda new to whole this world of "android" former Iphone user.
last mounth i got my nexus S wich is my first android phone.
As soon as i got it i started to read guids and etc.
Root the device and ofc the nexy step was trying Rom`s.
but then a problem , every time i try to flash a rom i get status 7 error.
tryed every possible combination of restore / wipe etc...
nothing helped , so i came back to the stock one (backup i made before i started)
after a while i discovered the app Rom mananger , wich install rom update recovery etc...
so i updated my recovery and installed CM7 using it.
used it for a while and went back to the stock.
after cople of days tryed to install MIUI using rom manger every thing went clear and after the intall device reboot it self and then stuck on the Google logo with the lock in the botom of the screen.
and nothing helped since then restore , factory reset/restore / wipe`s etc.
as last resort i tryed Odin and it worked like a charm got my device back and runing.
today i tryed to install a new rom AOASP(i think , or some thing like that) in the first time from the recovery (several times) with every possible wipe.
all the time status 7 error , then went to rom mananger and again same thing.
stuck on the google logo.
now iam gonna use Odin again hope it will work this time too.
Any idea how to resolve it , or why this is happen ?
and how can i resolve the status 7 error and what does it mean ?
Thank you all.
(sorry for this been so long , wanted to give as much details as possible)
Contact this guy. Looks like the same problem. If you can't get it going, I can also fix it so just PM me...
http://forum.xda-developers.com/showthread.php?t=1091789
doesnt seem to be the same problem like i had.
Any way at this point i was able to restore my phone using Odin , and then restore it into my stock backup (including all my data and etc...)
but the problem remain the same.
cant install any rom (status 7 error).
and when i try to install any rom using Rom mananger iam stuck on the google logo after the reboot.
so what can i do ?
Problem solved by using Odin ro restore it and after that flash Nanbackup and finally updating the CWM recovery.
If any one get the problem try this
Btw SuperAOSP is GREAT !!!!
gl all.
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?
I really hope someone here can help me. I'm running an SGH-1337M (Rogers). I rooted the device a number of months ago with Motochopper and installed Foxhound ROM GT-i9505 (which every guide says works with the SGH-1337M). I've been running this rom for quite a while without issues. Yesterday I I installed Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1-jfltecan) which worked, until I rebooted the device. When I reboot the phone gets stuck on the Samsung Galaxy S4 boot logo. I've booted into TWRP and tried to reinstall the Foxhound rom which was working but end up with the same results. I've used Kies Firmware upgrade to try and set everything back to default without sucess. Using Odin I tried to reinstall a factory image of my phone, which is sucessfull except nothing changes.
Currently, if using TWRP I do a full wipe of my phone and then install Cyanogenmod it'll work, so long as I don't reboot. If I reboot I need to do a full wipe, reinstall the rom and start all over.
I'm at a complete loss here. I've spent the last 5 hours looking for a solution to this problem without success. Any help is greatly appriciated.
Thanks
jer007 said:
I really hope someone here can help me. I'm running an SGH-1337M (Rogers). I rooted the device a number of months ago with Motochopper and installed Foxhound ROM GT-i9505 (which every guide says works with the SGH-1337M). I've been running this rom for quite a while without issues. Yesterday I I installed Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1-jfltecan) which worked, until I rebooted the device. When I reboot the phone gets stuck on the Samsung Galaxy S4 boot logo. I've booted into TWRP and tried to reinstall the Foxhound rom which was working but end up with the same results. I've used Kies Firmware upgrade to try and set everything back to default without sucess. Using Odin I tried to reinstall a factory image of my phone, which is sucessfull except nothing changes.
Currently, if using TWRP I do a full wipe of my phone and then install Cyanogenmod it'll work, so long as I don't reboot. If I reboot I need to do a full wipe, reinstall the rom and start all over.
I'm at a complete loss here. I've spent the last 5 hours looking for a solution to this problem without success. Any help is greatly appriciated.
Thanks
Click to expand...
Click to collapse
After you did odin, you must do a factory reset. This should clear up the problem. And, are you using the correct kernel for cyan?
My g2 d801 was running a lg g flex rom, i removed all the bloatware like com.google books ect and it was smooth 4 up to 3 weeks . Untill i got tired of having 2 reboot my phone to update the video player every time i download 1 . So i decided to search up media refresh and came across the app devastated me called force media scan . Its an app with 1 button and it took up 2 4 minutes to scan . Then after that everything in my video played doubled so i tried going into storage to see how much was used up then the phone freezed and rebooted . Now everytime i turn on the phone it doesnt load a signal nor can i turn on wifi . I tried restoring all my backups across 3 roms i had in the past including the stock 1 wich just says error at the bottom of the screen nothing helped i even tried reseting on the unoficial cwm no good . Then i had the recovery image of twrp backed up on stock so i tried reseting that way still no good then all my backups were gone but today i tried returning to stock it was smooth it really is stock again but sadley whatever that app did didnt get erased . Somthing like this happened b4 on my first android but when i flashed that 1 back 2 stock it had an option 2 factory reset on the cpu like from factory. i was just wishing someone reads this and has a solution because i was planning on getting the gflex and ps4 but 1 of them will be replaced with a new g2
I was using the Cyanogen 13 ROM for about 20 days it was working fine, however it did not load off, so far so good. When these days he stopped loading and kept rebooting alone on the boot screen of note 4 910C. I thought it was a problem in rom I restored my nano backup complete restoration however it did not work either, I tried to flash a rom via twrp the complete installation however it did not work too ... I tried other two rom custom too and it did not work. That's when I decided to use Odin I downloaded the original ROM and did the flash. Flash completed successfully, when the cell phone was to start its first boot. I have the message on the phone saying ... Install DRK files first. Does anyone know how I can solve this problem. I took in the technical assistance of my city after more than a week of waiting the boy said that the phone has no concert.