[SOLVED] Phone booting only to recovery after kernel update - Galaxy 3 General

Hey,
I had G3mod kernel on almost stock JPU. I wanted to try the Astrum Kernel so I flashed it. Although now my phone only seems to boot to recovery. Once it reboots it automatically goes to recovery. I tried wiping cache and dalvik. Also tried flashing the G3mod kernel again, doesn't work. Anything I could do without flashing the whole rom again? Please help.

did you try a factory reset?

Why dont you flash again?
Sent via Tapatalk from my awesome Galaxy 3

Thank you for replies. To anybody having the same problem. If you want to preserve your phone data (messages, contacts, log calls etc.) you have to flash the firmware again (in my case it was default JPU) without the 'data.rfs' file in the tar package. It will let you boot up the phone without losing your data and you will be able to backup them.

Related

[Q] CM10 Recovery enable to wipe Data

Hello! I have installed the CM10 from pershoot whit recovery,modem and bootloader .tar from droidbasement.com. Recovery is able to wipe cache but when i want to wipe data it force restart in recovery and nothing have been erased. Do i can wipe all whit Odin or something else?? :cyclops:
If i format every folder From the recovery on my tablet do i will able to flash original rom whit odin to return to stock or it will break something?
I had these experience as u described.
You likely have to flash any ICS stock rom from Odin and then root your device in order to get this resolve.

TWRP and Format Data Option !! Doh !!

In my quest to clean my Internal SD card i did a Twrp Format Data. I once done loaded a custom rom.
Worked fine until reboot.
The phone hanhs at the Galaxy S4 boot screen. Whatever i put back, backups etc once i reboot the same story.
How can i fix this gents ??
Please help
Xetalx said:
In my quest to clean my Internal SD card i did a Twrp Format Data. I once done loaded a custom rom.
Worked fine until reboot.
The phone hanhs at the Galaxy S4 boot screen. Whatever i put back, backups etc once i reboot the same story.
How can i fix this gents ??
Please help
Click to expand...
Click to collapse
try reflashing the ROM your on
hapticxchaos said:
try reflashing the ROM your on
Click to expand...
Click to collapse
I did try a clean flash of my rom... Same thing it goes well until i reboot. Stalls on Samsug Galaxy S4 screen.
It feels like TWRP Format Data screwed up something... V 2.5.0.2
Xetalx
Try reflashing twrp.
Sent from my SGH-M919 using xda premium
hmm i would probably try restoring sans odin...should fix whatever partition issues your having
I had to restore from KIES...
Wouldnt boot again.
Go in stock recovery and
Format data / factory RESET the thing...
WTH I almost tought i lost it for a sec !!
Never format data. What you should have done is odin back to stock, then factory reset through stock recovery. Kies is hit or miss when it comes to recognizing the phone in that state. You got lucky. There are a few topics on how to fix the problem you had.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I format /data every time I flash a new ROM and I experience fewer bugs because of it.
I just back up all my important files (data folder) to external SD and then restore after I install the new ROM. Works great for me. :good:
CZ Eddie said:
I format /data every time I flash a new ROM and I experience fewer bugs because of it.
I just back up all my important files (data folder) to external SD and then restore after I install the new ROM. Works great for me. :good:
Click to expand...
Click to collapse
What do you use to format data ?
Stock ?
CMW ?
TWRP ?
Thanks
I prefer to format as well . But chances are that with the issues i got i wont do it again...
Xetalx said:
What do you use to format data ?
Stock ?
CMW ?
TWRP ?
Thanks
I prefer to format as well . But chances are that with the issues i got i wont do it again...
Click to expand...
Click to collapse
I'm mostly on TWRP but I do it in CWM also.
At most, your issue (whatever it was) was due to user-error or a random system glitch.
At worst, you have to ODIN back to stock which only takes about ten minutes to do, five minutes to re-root and install TWRP and then you're good to go again.
Don't know if any further research has been done on this subject, but it's the only thread that came back with TWRP+format.
This same thing happened to me last week, I *think* it was my first internal format on my i337, was able to boot then fail.
Odin back to stock fixed issues.
Any thought why this happens? Any suggestions for best clean format approach besides an Odin? Flash CWM/Philz for the format then back to TWRP if desired?
I'm currently stuck in the same situation. Used TWRP to format /data to try and clean up the internal sdcard and now I'm bricked. Flashed 3 diff recoveries and about a billion roms, nothing works. Downloading a fresh odin flashable stock rom as we speak.
edit: so flashing stock rom via ODIN wasnt quite enough. I then had to enter stock recovery and do a factory reset. I noticed any time I tried to format /data the system would crash and reboot. The stock recovery was able to properly format data and now I'm back on a custom recovery/rom again.

[Q] Trouble With Flashing CM10.2 and Wrong Kernel

So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4

in need of some serious help asap

my lgg2 att that had optimusg3 and dori installed is stuck at twrp and just lops back to twrp. i tried restoring a backup but ti always goes right back to twrp. I cant enter download mode either . how do i fix this asap, my mother had a heart attack this morning and i need my cell working to be able to communicate with my sister who is at the hospital
What have you tried besides your backup. Did you just try reflashing the ROM without the kernel? Do you have any other ROMs on your storage? Did you wipe system data cache and davlik cache and reinstall. There just seems to be something wrong with the boot on your backup.

Fix freeze , lags etc.

Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Orangley said:
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Click to expand...
Click to collapse
Try a full factory reset. Be careful as this will wipe your internal storage.
GDReaper said:
Try a full factory reset. Be careful as this will wipe your internal storage.
Click to expand...
Click to collapse
Thank you for your answer but I did it after flash stock rom via odin. Wiped data / factory reset , cache partition , mounted cache , system , data , wiped dalvik cache..
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
GDReaper said:
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
Click to expand...
Click to collapse
Flashing stock rom is same with factory reset i think clears everything.
I don't know. Haven't flashed stock on this device yet.
But don't most guys recommend doing a wipe before going back to stock?
I dont know i'll try that when i have free time. I did research some guys saying lollipop causing these problems. I'll try wipe before flash stock rom again , if issues keep happen i'll use lates 4.4.2 custom rom. Thank you for your answers i'll report back.
Real reset
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have the PIT file downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Thank you so much i'll try this now.
AndroidInitiate said:
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have it downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Click to expand...
Click to collapse
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Orangley said:
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Click to expand...
Click to collapse
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
AndroidInitiate said:
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
Click to expand...
Click to collapse
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Orangley said:
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Click to expand...
Click to collapse
What carrier are you using, model number of the phone, etc.
Have you backed everything up? And can you flash the custom recovery through Odin if it fails?
Try it without wiping efs first just to be safe
Look here for your device you will be able to find standalone flash able versions of twrp that should work through odin.
http://twrp.me/Devices/
Using i9500. And i did what you said and works fine thank you! Mods close thread please.

Categories

Resources