Related
Hey everyone.
Yesterday I was trying to flash Fugumod over the G3mod (2.2.2) and sadly I failed. My phone seemed to keep getting stuck at i5800 boot logo. I have Kyrillos 7.1 so it's pretty much the same kernel it came with but as I'm facing some battery issues with G3mod I wanted to try the default again. Anybody tried the same kind of flash lately? Am I forgetting something? Maybe it's connected with app2sd, but I tried booting without the microSD card and it didn't work either. Recovery worked fine. G3mod boots without any issues. I wouldn't want to flash the whole ROM again as it's quite modded or make a complete wipe. Thanks for any idea given.
testcik said:
Hey everyone.
Yesterday I was trying to flash Fugumod over the G3mod (2.2.2) and sadly I failed. My phone seemed to keep getting stuck at i5800 boot logo. I have Kyrillos 7.1 so it's pretty much the same kernel it came with but as I'm facing some battery issues with G3mod I wanted to try the default again. Anybody tried the same kind of flash lately? Am I forgetting something? Maybe it's connected with app2sd, but I tried booting without the microSD card and it didn't work either. Recovery worked fine. G3mod boots without any issues. I wouldn't want to flash the whole ROM again as it's quite modded or make a complete wipe. Thanks for any idea given.
Click to expand...
Click to collapse
did you try to wipe dalvik-cache and cache...that may help...
Sent fom Galaxy
Kyrillos' 9.3 powered by
G3mod 2.1 OC
Did you try flashing through odin? Maybe there is a problem with update.zip.
And yeah, wipe cache and dalvik cache. And also it may convert the file system, so it takes some time!
Sent from my amazing 10.1 galaxy tab
Me had same problem so had to stuck with g3mod
Sent from my GT-I5800 using xda premium
Thank you for your answers. Yes, I am flashing through Odin. I tried wiping cache and dalvik cache and there is a progress - now my phone loops at the boot animation. Either with or without microSD. Still the G3mod boots fine. Any other suggestions? Good to see that I am not the only one, maybe we could solve it also for other people. I just hope it's worth trying. Thanks for your time and help.
testcik said:
Hey everyone.
Yesterday I was trying to flash Fugumod over the G3mod (2.2.2) and sadly I failed. My phone seemed to keep getting stuck at i5800 boot logo. I have Kyrillos 7.1 so it's pretty much the same kernel it came with but as I'm facing some battery issues with G3mod I wanted to try the default again. Anybody tried the same kind of flash lately? Am I forgetting something? Maybe it's connected with app2sd, but I tried booting without the microSD card and it didn't work either. Recovery worked fine. G3mod boots without any issues. I wouldn't want to flash the whole ROM again as it's quite modded or make a complete wipe. Thanks for any idea given.
Click to expand...
Click to collapse
Wait for 15 minutes,fugumod converts filesystem after flashing
Thank you for your suggestion. I tried leaving it for about 15-20 minutes, there was the boot sound coming on and off. After that I cleared cache and dalvik cache again, but still the phone was stuck in a bootloop. Should I give it more time or maybe there is a way to convert filesystem for Fugumod manually without losing data?
testcik said:
Thank you for your suggestion. I tried leaving it for about 15-20 minutes, there was the boot sound coming on and off. After that I cleared cache and dalvik cache again, but still the phone was stuck in a bootloop. Should I give it more time or maybe there is a way to convert filesystem for Fugumod manually without losing data?
Click to expand...
Click to collapse
From where u are clearing dalvik cache after flashing fugumod, fugumod has stock recovery and u can only clear cache not dalvic cache, which recovery option is coming after fugumod flash, stock or custom g3mod
Just try to incorporate fugumod (i mean zImage )into the custom rom using Total Commander and then flashing it again to be certain that everything works.
I use G3mod 2.2.2 and i love it , fugumod, i believe to be old.(that is my opinion)
Good luck!
iuli2011 said:
Just try to incorporate fugumod (i mean zImage )into the custom rom using Total Commander and then flashing it again to be certain that everything works.
I use G3mod 2.2.2 and i love it , fugumod, i believe to be old.(that is my opinion)
Good luck!
Click to expand...
Click to collapse
Old is golf
---------- Post added at 04:59 AM ---------- Previous post was at 04:57 AM ----------
Mohanshbhr said:
Old is golf
Click to expand...
Click to collapse
F¤¤ck slide it
means old is gold.
Clearing dalvik cache is available under 'Advanced' tab in Fugumod's clockwork recovery, if I recall correctly. I am flashing the alpha 19 version from the last pages of kernel's thread. Maybe I should try an earlier release. Although I would like the most functional one. Could anybody suggest a version I could try? The only reason I want to change my current G3mod is the battery life with 3G/HSDPA data. And, I'm not running any kind of 3G TurboCharging scripts. Also, I don't want to go through the process of flashing and modding the whole ROM again, as it's my main and the only phone at this moment. Thanks.
Me had same problem so had to stuck with g3mod
Hello everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
You will probably have flash a stock rom via odin and go through the whole rooting and flashing process again. I did a similar thing to you and thats what I ended up having to do. Having a nandroid doesn't fix the problem either, I tried, so don't kick yourself. Just start again
Chileno4Live said:
Hello everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
Click to expand...
Click to collapse
Flash stock ROM using Odin.
You have no other choice.
Livewings said:
Flash stock ROM using Odin.
You have no other choice.
Click to expand...
Click to collapse
No other choice?? If he can enter CWM, he could just use nstools reset zip from nstools thread: http://forum.xda-developers.com/showthread.php?t=1333696 and problem probably solved.
Edit: I'm assuming he's using nstools to liveOC (as I don't even know other apps for that ATM).
Edit 2: I just examined that reset script and it might not work since mounting should be little different (at least in my phone ).
But you could also just mount data in CWM and use adb shell to delete that preferences file (look correct directory from that reset.sh)
Sent from my sandwiched SGS
Or if you have glitch kernel on your phone flash that.
It has built in ns tools cleaner
Sent from my GT-I9000 using XDA App
Het Guys thanks for replying. I fixed IT myself by reflashing The devils kernel. I got to the installation wizard but IT kept force closing so i couldn't Get in. I tapped The four corners toe skip The installation wizard, reflashed onecosmic rc3.1 and then devil kernel. Now it is working
Thanks for the solution via odin though. I Will keep IT in mind.
Thanks
Verstuurd van mijn GT-I9000 met Tapatalk
So i've have tried several times to install checkrom and have had some issues myself with boot loops, being a noob to andriod, (I just got the phone in january), first thing i wanted to do with my £400 handset was void the warranty and root the bugger.
OK, so i have managed to flash NEAK and checkrom and get my phone in such a nice sweet stable daily usage that i thought i would post this as i see many people have close to or the same problems i had flashing this rom and or kernal.
1) back up all your data using titanium or some other app that allows you to do this.
2) Transfer your data off your phone\SD card to PC IE pictures\music\videos\app back ups.
3) Once all the data you want saved is backed up to PC, you can proceed to format both SD and USB on the phone.
4) Reboot phone to recovery and wipe 'EVERYTHING' this means wipe cache partition\ wipe Dalvik cache \ wipe battery stats \ Factory reset.
5) Turn off phone
6) Boot into download mode IE odin mode
7) Flash via ODIN a rooted stock kernel
8) Boot into recovery again and wipe EVERYTHING
9) Flash checkrom V6
10) reboot into recovery and wipe 'EVERYTHING'
11) Flash N.E.A.K 1.3.3x
12) reboot phone and you should have a stable phone with checkrom as your rom and NEAK as your kernal
NOTE:
As a note i have also got JKAY deluxe setting app installed, i installed this separate which i found on the checkrom page and its working just fine.
Also uninstall the kitchen app that comes with checkrom BEFORE installing the new one from off the market, now i dont know if V6 comes with the new kitchen app as i had flashed V4 before hand then NEAK then to V6.
This took me many tries to get this just right and the key i think to it is the formatting of the USB and SD card.
Good luck to you people, and i hope you have the success i've had enjoying these wonderful tweaks i can now use on my phone.
Between the S1 and now the S2 I have flashed all sorts of roms and never had to format SD card/s. Btw I'm on Checkrom as well.
Sent from my GT-I9100T
Me too
I've had bootloops too. But i cleared a clean wipe of my data and flashed the stock rom and installed the ROM back. Now, it's working perfectly fine. I was thinking whether the N.E.A.K kernel was the one causing the problem. And now, after seeing that the others are having nearly the same problem with me, I am positive that there's some problem with the kernel and will not flash the same one again. Thanks!
cwh1996 said:
I've had bootloops too. But i cleared a clean wipe of my data and flashed the stock rom and installed the ROM back. Now, it's working perfectly fine. I was thinking whether the N.E.A.K kernel was the one causing the problem. And now, after seeing that the others are having nearly the same problem with me, I am positive that there's some problem with the kernel and will not flash the same one again. Thanks!
Click to expand...
Click to collapse
There is nothing wrong with the kernel. I also am on checkrom v6 and i have flashed that bugger so many times my tits are getting cold from the amount of times of flashing anyway it depends on the way you flash something and if you follow the proper procedures.
Sometimes it could be because of a bad download that sometimes you get bootloops or sometimes you just not flashed a file properly. But to blame a kernel or a rom in general 99% of times is a mistake as most bugs or errors are user inflicted. i still would recommend to flash NEAK as it is a sweet kernel and tomorrow their will be a new updated version. Anyway hope you guys enjoy checkrom and in general your android experience has a more enjoyable going
From the Moderator... Please read my Caution in post #27-thanks
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Edit: Shorty66 just posted he bricked his note by doing factory reset from within the os. So far he's the only one at the moment. But numerous members reported bricking their device using CWM recovery & stock recovery. Just to be safe, use the os factory reset rather than recovery. Me myself have used the os factory reset at least 6-7 times as we speak without any issue for the time being.
Nice guide, perhaps you could also add the steps to safely go to a 'safe' kernel/rom if one is already using LPY?
Sent from my GT-N7000 using xda premium
+1
Would also like to know the go back to b/cm9 etc steps
Sent from my GT-N7000 using xda premium
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there to get to any custom roms or rooted gb.
Ashren81 said:
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there get to any custom roms or rooted gb.
Click to expand...
Click to collapse
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
MamaSaidWhat? said:
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
Click to expand...
Click to collapse
flash using pc odin or heimdall. get to recovery and flash/wipe or install gb backup from there. but i advise u to get back to stock gb to get a clean start and move from there.
Ashren81 said:
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Click to expand...
Click to collapse
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
sehooo said:
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
Click to expand...
Click to collapse
apex launcher FTW!
nice guide!
Ashren81 said:
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Click to expand...
Click to collapse
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
The post I referenced: http://forum.xda-developers.com/showthread.php?p=26086599#post26086599
k1ng617 said:
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
Click to expand...
Click to collapse
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Ashren81 said:
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Click to expand...
Click to collapse
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
hgberry said:
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
Click to expand...
Click to collapse
yes that should be the way like i've post earlier. just use the safe-kernel of ur choice. but dont restore nandroid backup from any previous ics, nandroid from previous gb is fine. nice to see ur note safely back on gb. /thumbsup
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Goodm7sn said:
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.
to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?
djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
You might just be in the lucky position to have a phone which doesn't have the error.
But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...
I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.
Do you still know your flash history?
Hi Shorty66,
Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it.
Sent from my GT-N7000 using xda premium
Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
Sent from my GT-N7000 using xda premium
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped