Related
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Willem Kloppenburg said:
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Click to expand...
Click to collapse
thats just the default android boot screen, looks like the theme messed up your framework... hold on i'll make a .zip you can flash from recovery to fix it
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Willem Kloppenburg said:
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Click to expand...
Click to collapse
im just downloading the rom for you now so i can extract the framework, if you pull your battery out, you can either plug in your charger while its off, this will bring up recovery, or while its off, hold vol down and press power, that will take you to bootloader, and just pick recovery from the list, now when in recovery, if you navigate to the mounts and storage menu, choose the option mount usb storage, you can now connect to a pc as a disk drive and copy stuff to your sd card
im having trouble uploading attachments to xda at the min dya want me to upload it to megaupload for you?
AndroHero,
Thank you for helping me out. I didn't know about the vol down press power option which allows you to acces the sd card and intall a new rom. I had the revolution rom 2.0.9 already. It's installing as we speak. Much thanks for the tips!
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Everything is resolved. revolution is up and running again. I had to un the fullwipe.zip and that did it!
THANKS a lot for all the tips....again
Willem Kloppenburg said:
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Click to expand...
Click to collapse
Did you do a full wipe before re-flashing your ROM? even if you did just repeat the process , full wipe /cache, /dalvik-cache, /system and then re-flash the rom fingers crossed it should work
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
boot into recovery do a full wipe (system, data, cache and dalvik-cache) then re-flash your rom
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
Could it be possible that you installed cwm 3005 and tried a restore with that. I had the same problem. Went back to cwm 2.5.x and then restore worked.
Sent from my Desire HD
I think there will be a lot of scare because of this CWM 3x...
Same happened to me the other day, stupidly accecpted the update prompt from Rom Manager, did my backup and went to install Cyanogen 6... Got stuck at HTC logo next boot.
Thankfuly, had Leedroid 2.0 on the SD, too, and that one flashed properly
Thing is that when I try to downgrade the Recovery to 2.5x I get an error and really can't be bothered with ADB pushing stuff around, so using Cyanogen 7 for the time beeing
Anyhow, CWM 3.x is likely your problem, easy to fix ^^
Wanting to change my theme on the Samsung spica I had theexact problem on cyanogen mod. Had to redo the whole rooting and installing the Rom again to get to work.
Sent from my Desire HD using XDA App
yes, is some script...back to recovery 2.x
im having some serious issues, that render my phone essentially unusable. at this point, i just want a working phone. right now, i can get into bootloader/hboot/fastboot but when i select recovery, it reboots to the white htc evo screen, then sits there looping. the only way for me to get into recovery is if i flash a recovery via adb with fastboot, and then i can get in, and ive tried flashing a rom, which says is successful, then i tell it to reboot, it made it into the rom. but then i needed to reboot, and then it just kept looping the bootanimation. battery pull and try again, still loops animation. then i try to get into recovery via bootloader, and im back to square one, looping htc evo white screen.
any ideas??? thanks
-Alex
What recovery were you using?
What recovery are you using?
Damn beat me to it lol
amon-ra
thanks for quick replies
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
aadcrasher said:
okay, i got myself booted into miui, using it because it is very small and flashes quickly. what should i do? should i try to boot into recovery?
Click to expand...
Click to collapse
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
roids87 said:
You may as well, if you can wipe everything, except your SD card. Try and reflash the ROM then. The only reason I asked about your recovery is it seems like the same problem people have been having with TWRP2.
Click to expand...
Click to collapse
Same thing I was thinking, get outta my head lol
lol, so goto recovery, then just go down the list of things to wipe and reflash rom?
Yup wipe it all 3-5x just don't wipe sdcard or batt stats wipe: factory reset/data 5x then everything else at least 3x I always wipe everything 5x if I'm changing roms or restoring a backup
got into recovery wiped, flashed rom, and its all looking good. confused as to why it started working out of nowhere, but it seems to be good, and im fine with that lol. thanks!!
Hey guys,
this is my first post and my problem is as follows:
I had ICS 4.0.x on my galaxy tab 10,1 P7500, I then installed CWM 5.5.0.4. but had a rolling window. I then continued to install a bootloader (here: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41) with the appropriate bootloader for the p4. This fixed the rolling recovery and allowed me to install CM10 using CWM.
But my current problem is when the device goes on sleep mode and I wake the device up the screen is scrambled, can anyone tell me how to fix this?
Thank you in advance
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
Edit:
I fixed the rolling screen issue after screen unlock with pershoot's help, thanks again pershoot!
Maybe it will also work for you , here we go:
If you have installed the latest cm10 build, there is only one issue for the p4wifi , you must be on the US ICS Bootloader .
So download the recovery.tar.md5 from here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/recovery.tar.md5
Than go into download mode and flash this recovery using ODIN, (select pda and look for this file where you safed it, than click start)
Than, download the right US ICS Bootloader here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/US_LPL_4.0.4_bootloader.zip
Flash this also via ODIN in the PDA section, this may take a little longer, don't panic...
After that, the tablet will reboot and it should work... don't blame me if it didn't, but i had this rolling screen on almost every rom, and everything is fixed now...
I wish you good luck because i know it IS very annoying..
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
DefQoN_BE said:
I have EXACT the same issue, i'm running the latest cm10 build from droidbasement.com, if anyone can please help us???
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
I wish you good luck because i know it IS very annoying..
Click to expand...
Click to collapse
I have tried this method and works perfectly!
Thank you sooo much!!!
I am afraid to put a rom on my 10.1, i love it though!
blacks10 said:
I am afraid to put a rom on my 10.1, i love it though!
Click to expand...
Click to collapse
There's nothing you should be afraid of there is a fix for everything, and if you can't find it? There are nice poeple out there who wants to solve your problrm on xda developers forum
@drefcom: you're welcome
Please help - When turning off the Screen Android 4.1.1 will not come back on
I have the following problem.
When I install one of the latest rom e.g.
[ROM] [JB] [P4--P4WIFI--P4VZW]
4.1.2 AOKP for the Galaxy Tab 10.1
or
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview
then I have this problem:
When I turn off with the "Power"-Hardbutton, then it turns off, but it does not turn back on. The screen stays black.
With the Rom ...
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview "cm-10-20120814-EXPERIMENTAL-p4.zip" from August everything works fine.
Since I had this flickering problem I flashed the bootloader before I installed all these Roms.
But one works and all new ones don't.
Anyone has a idea what to do?
thx
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Hi guys.
speersie said:
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Click to expand...
Click to collapse
i tried this method, but at second flashing (bootloader.zip) i get "0 succeed/0 failed" and still i get that scramble, and have to reboot all the time.
Any ideas?
Thanks in advance.
Cheers!:good:
Problems solved
I solved my problems. I installed the "custom" bootloader for each Rom and the "black screen" problem is now gone.
Thanx anyway.
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
drefcom said:
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
Click to expand...
Click to collapse
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
drefcom said:
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
Click to expand...
Click to collapse
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
DefQoN_BE said:
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
Click to expand...
Click to collapse
The thing is it is the exact same file I used to flash the previous time.. I first updated my recovery and bootloader before flashing and still get the error. Thanx for the thought though.
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great
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