Hey guys, I've had this question for some time. If you're gonna flash a Rom over another without wiping, like I'm doing now, Energy Aug 1 over 6th, I have 27% right now, is it safe to flash?
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
eggydrums said:
Hey guys, I've had this question for some time. If you're gonna flash a Rom over another without wiping, like I'm doing now, Energy Aug 1 over 6th, I have 27% right now, is it safe to flash?
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
if you mean with 26% battery, then yea it should be ok. i flashed a rom with 12% battery before. and as long as you go from ics to ics rom you will be ok.
(the flashing process is so fast that you dont have to worry about battery too much)
eggydrums said:
Hey guys, I've had this question for some time. If you're gonna flash a Rom over another without wiping, like I'm doing now, Energy Aug 1 over 6th, I have 27% right now, is it safe to flash?
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
You cannot brick a device if you're flashing ROMs with low battery. Heck, I've done it with 5% battery. Worst case scenario: Battery dies during flash. Phone probably won't boot due to no system (or corrupt system) installation. Solution: Charge it and then flash it again when there is enough battery. That is, if the ROM doesn't flash another radio/hboot.
For RUUs, radios, and hboots that is a COMPLETELY different story. Your battery dies while flashing a RUU, radio, or hboot, and you're probably screwed. (Not always, but a good chance)
yea i forgot to add the RUU part...
you definatly want at least 50% when flashing an RUU so that there is no possible way for a brick during that
Ahh awesome thanks for quick answers guys!!
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
I'd still flash a rom with full battery
read somewhere if you don't flash with full battery, the ICS set-up during initial boot might screw things up battery wise
I know that my first flash with the energy rom was at 70% battery, and had problems with battery life
flashed the (RUU) and Speed Rom with 100% battery, currently with no problems
EDIT: http://forum.xda-developers.com/showpost.php?p=25978764&postcount=34
some more info, useful i hope?
paperWastage said:
I'd still flash a rom with full battery
read somewhere if you don't flash with full battery, the ICS set-up during initial boot might screw things up battery wise
I know that my first flash with the energy rom was at 70% battery, and had problems with battery life
flashed the (RUU) and Speed Rom with 100% battery, currently with no problems
EDIT: http://forum.xda-developers.com/showpost.php?p=25978764&postcount=34
some more info, useful i hope?
Click to expand...
Click to collapse
When flashing with the RUU you know you are replacing EVERY system file on the phone.. so the ultimate "battery calibration"(since wiping battery stats is a proven myth) is having full battery when replacing system files.
As for the original question, if your battery dies after wiping ALL partitions you can completely wipe your device. When flashing a ruu it is accessing all partitions, but when flashing a normal rom it typically only wipes the system and data partition. As long as you have a recovery partition you can reflash any bad flash. As long as you can access boot loader you should be able to flash any ruu. But anytime you are messing with system files I think it is safe to say you don't want your phone to actually die and kill the process at some incomplete point.
When flashing roms I've never had it use more than 7%, so I'd say starting at 15% or more should be pretty safe.. but flashing at 100% will obviously write any system file that tells the phone what the battery capacity is, so I will always recommend it. If there is such a thing as the system checking battery capacity at all.
Sent from my HTC_Amaze_4G using xda app-developers app
Ruu I would get full battery
Sent from my MyTouch 4G Slide
Yes girls know about XDA
you can thank a girl on here
Samsung Galaxy Y bricked.Help!!!
Keylogger_0 said:
You cannot brick a device if you're flashing ROMs with low battery. Heck, I've done it with 5% battery. Worst case scenario: Battery dies during flash. Phone probably won't boot due to no system (or corrupt system) installation. Solution: Charge it and then flash it again when there is enough battery. That is, if the ROM doesn't flash another radio/hboot.
For RUUs, radios, and hboots that is a COMPLETELY different story. Your battery dies while flashing a RUU, radio, or hboot, and you're probably screwed. (Not always, but a good chance)
Click to expand...
Click to collapse
I was flashing stock ROOM on my Galaxy Y using Odin but i forgot to charge the phone to at least 80% and it failed to flash the ROM.Because the phone was in downlod mod I wanted to go to recovery mod so I removed the battery and reattached it and pressed volume up + home bottom + power on and nothing appeard on the screen.I tried to power it on nothing yust a black screen.I tried to go to download mod still nothing.I connect it on my pc but it doesnt reconize it.I tried evry solution that I found on the inthernet but nothing works.Please help me!!!:crying:
I flash roms even at 5% I just leave it on the charger never had issues
Sent from my HTC_Amaze_4G using xda app-developers app
davidrupnik1234 said:
I was flashing stock ROOM on my Galaxy Y using Odin but i forgot to charge the phone to at least 80% and it failed to flash the ROM.Because the phone was in downlod mod I wanted to go to recovery mod so I removed the battery and reattached it and pressed volume up + home bottom + power on and nothing appeard on the screen.I tried to power it on nothing yust a black screen.I tried to go to download mod still nothing.I connect it on my pc but it doesnt reconize it.I tried evry solution that I found on the inthernet but nothing works.Please help me!!!:crying:
Click to expand...
Click to collapse
You know this thread is for an htc device right?
Class_of_punk26 said:
I flash roms even at 5% I just leave it on the charger never had issues
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
No one ever said it would cause any problems....
davidrupnik1234 said:
I was flashing stock ROOM on my Galaxy Y using Odin but i forgot to charge the phone to at least 80% and it failed to flash the ROM.Because the phone was in downlod mod I wanted to go to recovery mod so I removed the battery and reattached it and pressed volume up + home bottom + power on and nothing appeard on the screen.I tried to power it on nothing yust a black screen.I tried to go to download mod still nothing.I connect it on my pc but it doesnt reconize it.I tried evry solution that I found on the inthernet but nothing works.Please help me!!!:crying:
Click to expand...
Click to collapse
You're in the wrong forum. They might have better help for you in the galaxy forum.
Sent from my HTC_Amaze_4G using xda app-developers app
i have flashed my panasoni p55 but it does not have battery charged .it is showing no response what should i do now?????
Related
hello and thank you for taking the time to read my post and your efforts to help.
my rebooting problem is really frustrating because it seems to inconsistent to really describe. i'll try my best.
gsm evo 3d Rogers Canada
unlocked, rooted using revolutionary, s-off
now it reads hboot 1.49.1107, radio 10.13.9020.08_2m
ive tried several roms and kernels (king cobra, ROMeOS, LeeDroid) -nothing solves my problem. Im currently on ROMeOS with the stock kernel he provided.
I've done SEVERAL full wipes by clearing cache, dalvik, full wipes and used superwipe. still no good.
1) it tends to do a lot of rebooting in the morning after charging all night. ill wake up, use it for a while and it'll reboot in my hands or seconds after i put it down.
2) the only thing that seems to help prevent reboots sometimes is turning it off and leaving it off for a few hours. but even this only works inconsistently.
3) Ive often noticed a huge battery drain (roughly 20% in 30 mins) on those mornings when it then proceeds to reboot.
sometimes, after leaving it off for a few hours and turning it on again, it reads a higher battery level and then works well the rest of the day. in fact, once it begins to work well, it tends to drain nice and slowly and not give any problems until the next morning after another night of charging.
Ive noticed that often, if i get the big drains in the morning, i can unplug it and immediately replug it until it reaches full and it then works well with no reboots and good battery life that day.
it also takes forever to go from 99% to 100% charged.
4) another thing that bothers me is that i can do all the wipes and clean install a rom and it'll will work fine for a few weeks until all this starts happening again. OR it can begin repeating these problems right after a clean rom install.
5) another weird thing is that often, i cannot turn the phone on without using volume up and down and power at the same time.
I wanted to return to the stock rom without losing root so and i downloaded the rogers stock RUU thinking it would be a ZIP file that i could just flash through CWM but i keep reading contradicting instructions on how to do that. some just said "download the RUU, plug into PC and install" but that sounds really vague. In other posts it says i have to relock bootloader and extract the zip etc -which seems so much more complicated than just flashing a new zip file. so im stuck not knowing what to do.
have mercy on me guys...
highflying10 said:
hello and thank you for taking the time to read my post and your efforts to help.
my rebooting problem is really frustrating because it seems to inconsistent to really describe. i'll try my best.
gsm evo 3d Rogers Canada
unlocked, rooted using revolutionary, s-off
now it reads hboot 1.49.1107, radio 10.13.9020.08_2m
ive tried several roms and kernels (king cobra, ROMeOS, LeeDroid) -nothing solves my problem. Im currently on ROMeOS with the stock kernel he provided.
I've done SEVERAL full wipes by clearing cache, dalvik, full wipes and used superwipe. still no good.
1) it tends to do a lot of rebooting in the morning after charging all night. ill wake up, use it for a while and it'll reboot in my hands or seconds after i put it down.
2) the only thing that seems to help prevent reboots sometimes is turning it off and leaving it off for a few hours. but even this only works inconsistently.
3) Ive often noticed a huge battery drain (roughly 20% in 30 mins) on those mornings when it then proceeds to reboot.
sometimes, after leaving it off for a few hours and turning it on again, it reads a higher battery level and then works well the rest of the day. in fact, once it begins to work well, it tends to drain nice and slowly and not give any problems until the next morning after another night of charging.
Ive noticed that often, if i get the big drains in the morning, i can unplug it and immediately replug it until it reaches full and it then works well with no reboots and good battery life that day.
it also takes forever to go from 99% to 100% charged.
4) another thing that bothers me is that i can do all the wipes and clean install a rom and it'll will work fine for a few weeks until all this starts happening again. OR it can begin repeating these problems right after a clean rom install.
5) another weird thing is that often, i cannot turn the phone on without using volume up and down and power at the same time.
I wanted to return to the stock rom without losing root so and i downloaded the rogers stock RUU thinking it would be a ZIP file that i could just flash through CWM but i keep reading contradicting instructions on how to do that. some just said "download the RUU, plug into PC and install" but that sounds really vague. In other posts it says i have to relock bootloader and extract the zip etc -which seems so much more complicated than just flashing a new zip file. so im stuck not knowing what to do.
have mercy on me guys...
Click to expand...
Click to collapse
these links provide stock rooted ruu "NO RELOCK REQIRED FLASHABLE THOUGH RECOVERY"http://forum.xda-developers.com/showthread.php?t=1420206
thanks but all those say they're for Sprint but mine is from Rogers Canada.
Link for roger if still neededhttp://www.filefactory.com/f/4ef0ef536face67a/
Sent from my PG86100 using XDA Premium App
thanks (if only that link would work! it always claim to have no slots available.)
will that stock rom be a flashable zip!?
also, do my problems sound familiar? does this happen to others? any reason why all the wipes i did didnt correct it?
highflying10 said:
thanks (if only that link would work! it always claim to have no slots available.)
will that stock rom be a flashable zip!?
also, do my problems sound familiar? does this happen to others? any reason why all the wipes i did didnt correct it?
Click to expand...
Click to collapse
This is happening to mt wifes 3d ,but the problem is that everytime it goes to sleepit will lock up and the reboot ,it does it ill say every 15 minutes or so ,i think os only on aosp roms ,running miui and any ics roms,is cdma btw,any help????
It is quite common to se the 3vo haveing random reboots:but try under clocking it worked on over 3 different 3vos I've worked on
Sent from my PG86100 using XDA Premium App
aleksis2010 said:
This is happening to mt wifes 3d ,but the problem is that everytime it goes to sleepit will lock up and the reboot ,it does it ill say every 15 minutes or so ,i think os only on aosp roms ,running miui and any ics roms,is cdma btw,any help????
Click to expand...
Click to collapse
Have you tried going completely stock kernel&actual rom
Sent from my PG86100 using XDA Premium App
jwolf1 said:
Have you tried going completely stock kernel&actual rom
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Yes ,and the problem disappears,i think is only with aosp,the problem is that is my wifes phone and she loves miui ,so i have to try and find a way to fix this .
aleksis2010 said:
Yes ,and the problem disappears,i think is only with aosp,the problem is that is my wifes phone and she loves miui ,so i have to try and find a way to fix this .
Click to expand...
Click to collapse
Ways ur system info hboot etc
Sent from my PG86100 using XDA Premium App
jwolf1 said:
Ways ur system info hboot etc
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Hboot 1.40 and i flashed freezas aio zip trying to fix it.
aleksis2010 said:
Hboot 1.40 and i flashed freezas aio zip trying to fix it.
Click to expand...
Click to collapse
Flash this rom its miui an it works perfectly on my 3vo;this Rom should be perfect only problem no 4G&3d camera besides that it perfect an its ics
Sent from my PG86100 using XDA Premium App
jwolf1 said:
Flash this rom its miui an it works perfectly on my 3vo;this Rom should be perfect only problem no 4G&3d camera besides that it perfect an its ics
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Wich one ?
http://forum.xda-developers.com/showthread.php?t=1504916this one
Sent from my PG86100 using XDA Premium App
jwolf1 said:
http://forum.xda-developers.com/showthread.php?t=1504916this one
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Tried that one too and its having the same issue ,hopefully its not a hardware issue ,i dont wamt to unroot ! And idk if it happens on sense too cause i flashed it bit didnt run it long wnough to see ,because it happens right away with any aosp rom :-(
Edit: Fixed it! I think I just needed to do a super wipe!
i havnt tried going stock rom and kernel. as i said earlier, i am using stdock kernel provided by monx who makes the ROMeOS.
ive been trying at different times to download from the filefactory link provided in this thread but its always full.
does anyone know of it being hosted anywhere else?
how do i use this .exe file?
jwolf1 said:
Link for roger if still neededhttp://www.filefactory.com/f/4ef0ef536face67a/
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
i finally got to download it but its an exe file and i havnt found clear instructions for how to use it. i'm used to flashing zip files from CWM.
can you please advise?
i read its just a matter of plugging the phone to the pc with usb debugging and running the exe file. with this method, will i lose superuser permissions, s-off, or root?
I'm a Sprint user but I had a huge issue with random reboots after upgrading to the latest OTA from sprint. I have s-off through revolutionary. It sounds exactly like the issues the OP described so I'm just going to say that the only way I got rid of my random reboots was to use the latest RUU.exe file from my PC to restore my phone to completely stock (but you keep s-off after using the RUU). Every time I tried to upgrade to the newest OTA from Sprint using a PG86IMG.zip file, I would have the random reboot issue. After the RUU, no more random reboots on any ROM, whether it was MIUI, Sense 3.0, 3.5, or AOSP/ICS
Also, I sent some detailed instructions via PM to a few sprint XDAers who asked for help getting rid of random reboots. The replies I got all said the reboot issue went away. Idk if it's the same sort of underlying issue for everyone on the GSM EVO 3D, just thought I'd share my experiences
---------- Post added at 06:43 PM ---------- Previous post was at 06:38 PM ----------
highflying10 said:
i finally got to download it but its an exe file and i havnt found clear instructions for how to use it. i'm used to flashing zip files from CWM.
can you please advise?
i read its just a matter of plugging the phone to the pc with usb debugging and running the exe file. with this method, will i lose superuser permissions, s-off, or root?
Click to expand...
Click to collapse
Put the exe on your computer, not your phone. boot into fastboot (hold vol down and press power on, then choose fastboot), then plug your phone in and run the exe on your computer.
EDIT: just noticed I didn't answer everything you said. You keep s-off, but lose the custom recovery, and root/superuser (same thing essentially). Getting root back is really simple though, all you have to do is add superuser back to the stock ROM (RUU puts you on completely stock ROM/kernel) or flash a custom recovery again and then any ROM from recovery, and you'll get superuser/root back in that ROM
Try this its helps with reboots. A lot of useres tend to neglect cleaning there sd and it can cause major reboots on all kind of roms and kernels
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
Hope this helps
#Root-Hack_Mod*Always\
Have you tryed a super wipe tool use just before you flash the ROM
Sent from my HTC EVO 3D X515m using xda premium
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
xX760Xx said:
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
Click to expand...
Click to collapse
Won't boot to bootloader? If not I'd leave the battery out overnight and try to boot to bootloader in the morning
Sent from my ADR6425LVW using xda app-developers app
xX760Xx said:
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
Click to expand...
Click to collapse
What recovery are you on?
Sent from my ADR6425LVW using Tapatalk 2
I'm using Clockwork Touch Recovery. I'm able to get into HBOOT now, but when it tries to flash PH98IMG.zip, it just says "Battery voltage is too low! Please change a battery..." And I can press power to continue. I'm assuming it's actually trying to flash PH98IMG.zip, but it can't because the battery is too low? This wouldn't be much of a problem if I could charge it, but it refuses to charge either my stock battery or my extended battery.
xX760Xx said:
I'm using Clockwork Touch Recovery. I'm able to get into HBOOT now, but when it tries to flash PH98IMG.zip, it just says "Battery voltage is too low! Please change a battery..." And I can press power to continue. I'm assuming it's actually trying to flash PH98IMG.zip, but it can't because the battery is too low? This wouldn't be much of a problem if I could charge it, but it refuses to charge either my stock battery or my extended battery.
Click to expand...
Click to collapse
The recharging issue with Clockwork Touch Recovery is a known issue and is discussed in several different places in Rezound forums. You need to flash TWRP or better still Amon Ra which are more reliable and don't have this issue. You need to get a different, fully charged battery, reboot to BOOTLOADER and flash a different recovery. You should then be able to get back to a normal boot if you flashed the kernel after flashing the ROM (you did say you were S-ON, right?) If not, you can either reflash the ROM (the Aroma installer will reboo to bootloader to flash the kernel) or RUU back to stock, reflash Amon Ra, then reflash Nils' ROM. The latter approach shouldn't be required unless you really borked your system.
Ok, so apprently I am running cwm, I thought I was running amon ra to be honest but here is my problem:
Ok, I had cleanrom on my phone, lost 4g so started messing around. When I go into CWM Recover v5.8.1.4 and try to reinstall a rom or anything I just get the little CWM icon, It will not go into any option I choose. I have to pull the battery to restart. But the screen will not turn on when I push the power. Only think I can do is boot into bootloader. VZW rep said they can replace it, but was afraid I would get charged from HTC since its prob my fault. Any suggestions?
Hmm. Boot into bootloader, plug in via usb. Flash Ruu or new recovery (probably RUU)
I think that should work.
Sent from my ADR6425LVW using xda app-developers app
Reaper0294 said:
Hmm. Boot into bootloader, plug in via usb. Flash Ruu or new recovery (probably RUU)
I think that should work.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks reaper, now I cannot even get into bootloader.........some people arent suppose to mess with this stuff...and Im one of them Back to the pre for a few days.
Your battery is probably too low to boot you need to charge it or look for the cwm boot problem thread to get it to boot
Sent from my Dinc... I mean Rezound
yojoe600 said:
Your battery is probably too low to boot you need to charge it or look for the cwm boot problem thread to get it to boot
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
alright I have discovered what I've done wrong....the phone still isnt working but heres how it happened.
I did flash amon ra, and clean rom. Once I got it all setup, I downloaded ROM Manager, this has killed the phone. Like I said everything I try to flash a new rom from zip on sd, the little rom manager dude blocks me. Any suggestions on how to get rid of him so I can reflash. When I plug the phone into my computer to adb device it is not found. I have download HTC Sync.
you need to be in fastboot for it to be found
Ah the old charging problems. That's right. This guide should work. http://forum.xda-developers.com/showthread.php?t=1722989&highlight=clockwork+boot
Your phone isn't bricked, relax. For some reason none of us quite know, when any rezound with clockworkmod on it reaches fully low low battery and turns off it no longer charges correctly.
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Also have a look at CyanogenMod, they have a good post with instructions on here.
Sent from my GT-I9100 using xda premium
x
Dorbian said:
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
no, phone doesn.t response on anything, even if i'm charging the battery.
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
.
Dorbian said:
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Did it and still nothing, do you think that maybe JIG plug could be a good idea?
You could always give it a go, havent had any experience with i myself tho so hopefully someone else here can give you a hand
Sent from my GT-I9100 using xda premium
I had a similar issue with sgs1 back in the day. I built a jig and got it working so give it a shot if you can. Its worth it for the cost of a jig surely?
Sent from my GT-I9100 using xda app-developers app
.
ok, i'll try to do it. but i have to ask if that will not work, can i save my phone by changing main board on warranty in service?
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
pawlo130 said:
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Click to expand...
Click to collapse
On some occasions flashing a device can use 40-50% of battery to prep and flash device which is why its advised to never flash your phone unless you have at least 50-60% battery.
If power cuts out during flashing procedure it can damage nand/ic chip, corrupt bootloader, corrupt sdcards etc.
After leaving it plugged into to charger overnight try a USB jig to see if you can get it to wake up in download mode, If you can re-flash rom and go from there.
gastonw said:
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
Click to expand...
Click to collapse
battery was about 70%, so it should not have turned off
pawlo130 said:
battery was about 70%, so it should not have turned off
Click to expand...
Click to collapse
then I was right with the fishy wipes.
pray for the jig.
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
xdanoober said:
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
while i was installing new rom, process was like 0% for about 5 minutes, and then phone just turned off. When i did flashing and installing CWM everything was ok. I rooted it with CF root.
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Your phone have got super brick, and the JIG nothing to do.... You must go to service.
The reason for this is stock kernel who has kode cause brick.
Sorry for my english!
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Don't worry will be fine. JTAG must be repair all
Wysyłane z mojego GT-S6500D za pomocą Tapatalk 2