Related
Hopefully someone can help me here. I flashed this onto my quad-core GSM HTC One X and it seemed to work but now my battery says it's not charged and no matter how long I charge it, no matter what cable I use, no matter the charging source, my device says I have no power and it immediately restarts and goes into this horrible loop.
I tried fastboot erase cache while in recovery but that didn't work.
Then I decided to go back to the stock ROM and the exact same problem is occurring. The phone thinks the battery is completely drained and shuts down. Even if the phone is plugged in.
Now before you say something like "your battery must be bad," this EXACT thing happened to me with my Sony Xperia Arc. Thinking I had a bad battery or bad connector I tried to send it in for warranty repair and Sony refused to look at it due to the unlocked bootloader. So I replaced it with this phone and now I'm thinking I have 2 perfectly good phones, there's just some issue in ROM loading where the battery detection went bye-bye.
Has ANYONE come across this anywhere? Is there hope? Or a fix?
have you tried full data wipe?
Yes. I've tried to go all the way back to the beginning. In Recovery, I've tried to wipe everything. All caches, all battery info, everything.
Phone boots and it looks like the problem is fixed, battery shows at roughly 90% and green. Then quickly jumps to 0% and shuts off.
freicook said:
Yes. I've tried to go all the way back to the beginning. In Recovery, I've tried to wipe everything. All caches, all battery info, everything.
Phone boots and it looks like the problem is fixed, battery shows at roughly 90% and green. Then quickly jumps to 0% and shuts off.
Click to expand...
Click to collapse
that's weird... but i think it's not the device, try installing other ROM, give CHARMELEON a shot... not advertising, but they have this settings to change, like auto full wipe... etc... there might be a miracle, just have a good feeling about it.. no harm in trying.. Good luck!
mikey0105 said:
that's weird... but i think it's not the device, try installing other ROM, give CHARMELEON a shot... not advertising, but they have this settings to change, like auto full wipe... etc... there might be a miracle, just have a good feeling about it.. no harm in trying.. Good luck!
Click to expand...
Click to collapse
I think you're 100% correct. In fact, I have this feeling that I had an old version of ClockworkMod recovery and that somehow, that's what is wrong.
Here's my issue now. How do I flash a new recovery image onto the device when the only way I can get onto the device is through the fastboot?
(using Mac) ./fastboot recovery.img recovery.img isn't working
sending 'recovery.img' (5732 KB)... OKAY
writing 'recovery.img'... FAILED (remote: not allowed)
freicook said:
I think you're 100% correct. In fact, I have this feeling that I had an old version of ClockworkMod recovery and that somehow, that's what is wrong.
Here's my issue now. How do I flash a new recovery image onto the device when the only way I can get onto the device is through the fastboot?
(using Mac) ./fastboot recovery.img recovery.img isn't working
sending 'recovery.img' (5732 KB)... OKAY
writing 'recovery.img'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
that happened to me before, my phone won't open, i just forgot what i did, but it's possible. from what i remember, its ADB PUSH, it's like you're going to flash or push a file into your SD card by using "CMD" that's possible, well lets start searching for that forum...
hey buddy, is it all okay now? if not i made a thread about this, check it HERE
I was using the wrong command to try to write the recovery.img to the phone. Once I got the latest and greatest CWM recovery and correctly sent it to the phone, the battery issue was resolved. However, I've had some issues getting back into recovery since then and I think there were some steps missing from what I did that I seen in your post. Thanks for putting that together.
freicook said:
I was using the wrong command to try to write the recovery.img to the phone. Once I got the latest and greatest CWM recovery and correctly sent it to the phone, the battery issue was resolved. However, I've had some issues getting back into recovery since then and I think there were some steps missing from what I did that I seen in your post. Thanks for putting that together.
Click to expand...
Click to collapse
no worries
freicook said:
I was using the wrong command to try to write the recovery.img to the phone. Once I got the latest and greatest CWM recovery and correctly sent it to the phone, the battery issue was resolved. However, I've had some issues getting back into recovery since then and I think there were some steps missing from what I did that I seen in your post. Thanks for putting that together.
Click to expand...
Click to collapse
Seeing AT&T as your carrier, can you confirm that you have the international HTC One X with tegra 3 and not HTC One XL with S4 ? This recovery will not work with HTC One XL.
Long story short, I flashed an alleged gps fix file for liquid and it bootlooped the phone to the point of killing the battery within 5 minutes. Now really stuck..
Tried to flash a google image, nothing would "write" on the phone.
Tried Odin. There, it gets stuck stuck at "NAND write start" and phone gets really really hot. Phone didn't boot to Download mode when pressing volume down-power. I have a picture of phone-yellow exclamation-computer on the screen.
Stuck..
Check the box to replace the bootloader and try odin again.
Then see if you can boot into fastboot (both volume buttons and power from an off state).
Also try (and this is a direct quote from a user who supposedly found success)
"Open CF_ODIN_YAKJU_IMM76D_full and remove the radio.img file that it is failing on"
Jubakuba said:
Check the box to replace the bootloader and try odin again.
Then see if you can boot into fastboot (both volume buttons and power from an off state).
Also try (and this is a direct quote from a user who supposedly found success)
"Open CF_ODIN_YAKJU_IMM76D_full and remove the radio.img file that it is failing on"
Click to expand...
Click to collapse
THANK YOU!!!
Green bar started moving & I thought it was over; now it's stuck at about 30% (<ID:0/003> system.img), at least it showed life. It did bootloader, boot & recovery.img
Do I need to perhaps check Phone and CSC as well?
Vangelis13 said:
THANK YOU!!!
Green bar started moving & I thought it was over; now it's stuck at about 30% (<ID:0/003> system.img), at least it showed life. It did bootloader, boot & recovery.img
Do I need to perhaps check Phone and CSC as well?
Click to expand...
Click to collapse
Am at total loss right now, nothing works..
Called Samsung Germany and will send it in for repair unless anyone has a work around.
If you can, boot into recovery. Wipe cache, dalvik cache, factory reset, and battery stats. If you were rooted, then don't send it in. Rooting does violate you agreement to use the device. It will also void your warrenty. Do everything you can your self, and send it in at a complete last resort.
Vangelis13 said:
Am at total loss right now, nothing works..
Called Samsung Germany and will send it in for repair unless anyone has a work around.
Click to expand...
Click to collapse
if odin wrote to the bootloader, try using fastboot at this point. see if it can get you anywhere.
Can't get into anything, all I see on the screen is the attached...
Odin doesn't do anything either anymore, stops at "NAND write start".
Sent from my Nexus S using xda premium
gregory99mar said:
If you can, boot into recovery. Wipe cache, dalvik cache, factory reset, and battery stats. If you were rooted, then don't send it in. Rooting does violate you agreement to use the device. It will also void your warrenty. Do everything you can your self, and send it in at a complete last resort.
Click to expand...
Click to collapse
Hopefully they'll oversee that if I have to send it in; I did however manage before all this to lock & unlock the bootloader so everything must be gone..
Any ideas guys?
Sent from my Nexus S using xda premium
Vangelis13 said:
Any ideas guys?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Try running odin again, but this time, only leave the bootloader, boot and recovery images in the .tar. As well, try clicking "start" on odin first, then plugging your device into your PC. Hopefully that will restore your bootloader and you'll be able to use fastboot to flash the system image.
efrant said:
Try running odin again, but this time, only leave the bootloader, boot and recovery images in the .tar. As well, try clicking "start" on odin first, then plugging your device into your PC. Hopefully that will restore your bootloader and you'll be able to use fastboot to flash the system image.
Click to expand...
Click to collapse
Thank you efrant!
It gets stuck at "NAND Write Start!!". Yesterday, when I was trying to send through fastboot, it wouldn't write anything either. It kept returning "too many links". Something got really borked, what ever the fck I did..
Service it is then probably.
Hi
Really need some advice here. After (successfully) flashing ROMs on my HTC Desire and a couple of LG / Samsung units, I decided I was fed up with the stock ICS ROM on my Arc S so found one I liked called Jelly Sandwich v6.2.
So, I rooted, no probs, unlocked the bootloader, no probs. Installed CWM and did a nandroid backup to my SD card. So far, so good.
I then used CWM to install the JS ROM and the phone is now stuck on the SONY screen, presumably the boot is looping and I have to pull the battery to shut it back down.
I can't get it into recovery, tried every combination of buttons I can think of. I can get it into fastboot by holding the menu button and inserting the USB cable and if I do a CMD line fastboot.exe -i 0x0fce getvar version I get the expected response, but if I try adb shell I get 'device not found'.
I am rubbish at best with command line stuff but I think this is my only way forward.
Have tried flashtool and I get the phone into Flashmode but it finishes with an error.... 04/048/2012 00:48:51 - INFO - Ending flash session
04/048/2012 00:48:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed".
Have also tried SuS and that fails with an error along the lines of "The phone has got modified software that cannot be upgraded" or similar.
Anyone tell me specifically what to try? and exactly what I need to be doing with commands etc.
Would appreciate any help no matter how small
Use the Flashtool instead of SEUS.
XperienceD said:
Use the Flashtool instead of SEUS.
Click to expand...
Click to collapse
he's saying he used flashtool but nothings working..
Sent from my AT100 using xda app-developers app
SORTED!!!
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
yorkiepudd said:
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
Click to expand...
Click to collapse
I have the exact same problem but I don't know how to solve this. Please help me.
lance26 said:
I have the exact same problem but I don't know how to solve this. Please help me.
Click to expand...
Click to collapse
Try reading the post you've quoted.
Sent from myushi
have you tried to flash a specif kernel for this rom or just redownloaded the rom? maybe there was a problem with the download
Since these problems I have installed both CynogenMod 10 and UltimateHD without any problems what so ever.
Here's my info:
Android version: 2.3.4
S-ON
Kernel: 2.6.35.9-gb5330gc
Radio: 1.09.01-1111
hboot: 0.98
I tried to root my DINC2 using the directions here: http://forum.xda-developers.com/showthread.php?t=1751796. In TACOROOT, I got stuck on the step that said it was going to take a long time (fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip). After an hour of it not doing anything (and needing to catch a flight) I unplugged and ran out the door. Later the phone booted up fine and seemed to act like it was going to work and let me start over.
So I start over at the beginning and go through the list of instructions for TACOROOT. When I get to that same step again the command prompt says waiting for the phone, the phone reboots... gets through the loading screens... I unlock the screen and it says "loading..." like it does when you first turn it on. Then, right after the SD card is loaded, right as the sense widgets load, it turns off and starts again.
This loops continuously for a very long time and the step never finishes. Now that seems to be all it does.
I've tried restoring stock everything via hboot, clearing the cache, factory reset. Each time, I can activate the phone and it lives, but as soon as I reboot once it's stuck in the loop again.
In truth, I'd be happy just to get it usable again. Any help is appreciated!
I'd really love to give this phone as a present, but it looks like it'll have to wait until after I'm able to get it up and running again. Any help at all is appreciated!
Thank you in advance and Merry Christmas!
Bump? I'm still stuck and not sure what else to try. Do you need more information?
You're still s-on?
Sent from PAC-nation
Rushead said:
You're still s-on?
Sent from PAC-nation
Click to expand...
Click to collapse
yes, still s-on
unrealnighthawk said:
yes, still s-on
Click to expand...
Click to collapse
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?
Rushead said:
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?
Click to expand...
Click to collapse
I've went through this process a few different times (checking the md5 checksum each time), but iI can try again. I was sure to fix that radio space too.
I'm virtualizing windows on my mac via virtualBox. would that make a difference? I've also tried it on a Windows computer I borrowed, it's just harder to get ahold of. Is there a decent osx solution? I wasn't able to find one that worked any better. I could also burn a Linux boot disk if that would work better.
Thank you!
Windows user here. Not sure about a mac, but probably that's where the issue is. Try a Linux boot & see if that works.
Sent from my Incredible 2 using xda app-developers app
Progress!... ?
Okay, so I think I've been able to make some progress. When I got home on my PC I was able to follow the instructions again and actually get past the step that had taken so long before (the don't forget to fix 'radio' in fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip step). It didn't take quite so long this time and finished successfully, so woot!
So I continued on and got to the next 'long' step: fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip. I get the error message "FAILED (remote: 12 signature verify fail)". I re-ran the MP5 checksum and it matches. To verify, the prompts for the last two commands are below.
Code:
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.262s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.529s
I'm worried now that one of the other solutions for restoring the phone to stock or rooting in a different manner changed something else. What debugging can I do to troubleshoot this? Is there an alternative file I should download to flash for the radio?
Thanks again!
I don't know if this is helpful, but here's what it shows on my phone
Code:
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-BOOT
Apr 13 2011, 21:20:09
Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Sent from my Incredible 2 using xda app-developers app
Rushead said:
Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Click to expand...
Click to collapse
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!
unrealnighthawk said:
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!
Click to expand...
Click to collapse
Make sure fast boot is disabled under settings -> power and then reboot phone. When the capacitive lights go out hold volume down. Or you could turn off phone and then power up holding the volume down button.
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!
unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!
Click to expand...
Click to collapse
No worries! Do you have superuser installed? If not, you need to push it via adb. The file should be available in the download package you downloaded initially.
Sent from my Incredible 2 using xda app-developers app
unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root?
Click to expand...
Click to collapse
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!
jncryer said:
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!
Click to expand...
Click to collapse
Yup. It failed on my first go, but I continued. Later I was able to go back and flash the radio. It worked that time. Good luck!
Phone boots after flash but stuck in reboot afterwards
hey guys i need a little help with my Di2. Ive had it rooted for the past almost year ive been flashing roms and whatnot i have basic common knowledge of what im doing with the phone however i seen the ics 4.0.4 rom that was released for the incredible 2 and after flashing that i then decided to flash back the stock gingerbread ruu i did this via the bootloader not recovery and now my phone will boot up perfectly the first time i flashed the file (PG32IMG) but when i reboot the phone it will load all the way up and turn on about long enough for me to pull down the lock screen slider and bam cuts off doing the exact same thing from then on out.. I am able to get to the bootloader screen however with all the latest attempts of wiping the data and and cache and whatnot i still have this exact same outcome i would really appreciate some help guys it would be much appreciated ive looked on the internet and in these forums and cant find any thing that quite helps yet ive downloaded so many PG32IMG files and tried to flash them via bootloader it is not even funny >.>... aha anyways thank you guys id like to turn this brick i had for the last few days back into the phone i love i dont even care if its rooted anymore i just want the thing working.. aha ive replaced the screen charging port and bought plenty of accessories id hate to see all that money down the drain. Thanks guys. Any replys are appreciated.
Have you tried flashing back to one of the older radios ? The ICS firmware maby boot looping your phone
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
Are you s-off?
Sent from my ADR6350 using xda app-developers app
Hi!
I think I search in all threads but cant find anything.
I have stock GSM Galaxy Nexus on Android 4.2.2(All update was recived OTA)(Baseband I9250XXLJ1 Build Number JDQ39). One day it lost internet connection and I try to turn on Airplane mode. It was hold and dont answer on anything. I pull out battery and put it back. And GNex start sometimes randomly sometymes loop rebboting. Then I went to XDA, read all threads, bricked phone, repair it with ODIN mode(with repairing file system, if I correctly understand what I did) and then it works good for two or three weeks.
And one day(about one week ago) I try to pull down upper bar and it didnt work(but icons worked). I try to reboot and it start rebooting again. I turn on debugging and I have kernel log(see attached files). Also I tryed turn on in safe mode, but problem is the same.
I tryed with SIM card and without-everything is the same:reboot.
[Q]estion: Can someone read kmessage and say what is the problem? Or say me, where i can find more information. Especially how to read kmessage log.
Last words in kmessage log:
[59601.884368] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
[59601.884368] ---[ end trace a98b16ed251b279f ]---
[59601.884368] Reboot failed -- System halted
Click to expand...
Click to collapse
Logcat in attachments(sorry for zip-txt didnt fit in 512 KBytes)
Dmesg write in file "klogctl: Operation not permitted"
kmsg attached(kmesg2. Sorry for zip. txt didnt fit in 512 KBytes)
sippelin said:
Hi!
I think I search in all threads but cant find anything.
I have stock GSM Galaxy Nexus on Android 4.2.2(All update was recived OTA)(Baseband I9250XXLJ1 Build Number JDQ39). One day it lost internet connection and I try to turn on Airplane mode. It was hold and dont answer on anything. I pull out battery and put it back. And GNex start sometimes randomly sometymes loop rebboting. Then I went to XDA, read all threads, bricked phone, repair it with ODIN mode(with repairing file system, if I correctly understand what I did) and then it works good for two or three weeks.
And one day(about one week ago) I try to pull down upper bar and it didnt work(but icons worked). I try to reboot and it start rebooting again. I turn on debugging and I have kernel log(see attached files). Also I tryed turn on in safe mode, but problem is the same.
I tryed with SIM card and without-everything is the same:reboot.
[Q]estion: Can someone read kmessage and say what is the problem? Or say me, where i can find more information. Especially how to read kmessage log.
Last words in kmessage log:
Logcat in attachments(sorry for zip-txt didnt fit in 512 KBytes)
Dmesg write in file "klogctl: Operation not permitted"
kmsg attached(kmesg2. Sorry for zip. txt didnt fit in 512 KBytes)
Click to expand...
Click to collapse
Have you tried to pull the battery and let it out for a while before putting it back in? And have you tried OMAP flash?
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Have you tried to pull the battery and let it out for a while before putting it back in? And have you tried OMAP flash?
Click to expand...
Click to collapse
Thank you for answering!
No, I dont try OMAP flash. If I correctly understand using this flash i will flash CPU? OMAP it is name of a processor, yes? Or in this context it is not the same?
I will try flash it.
Yesterday I did hard reset(from the restore menu in bootloader). After that I didnt connect it to Wi-Fi, or GSM network(pull out SIM). I didnt use it, it just laying. In this state it work without reboot about 14 hours, but then when I connect it to the Wi-Fi and open browser it rebooted again. So i don`t know what I can do more. And the worth problem - I don`t understand WHY it rebooting.
I try to pull out battery for some hours, but it doesnt help. How battery can help?
sippelin said:
Thank you for answering!
No, I dont try OMAP flash. If I correctly understand using this flash i will flash CPU? OMAP it is name of a processor, yes? Or in this context it is not the same?
I will try flash it.
Yesterday I did hard reset(from the restore menu in bootloader). After that I didnt connect it to Wi-Fi, or GSM network(pull out SIM). I didnt use it, it just laying. In this state it work without reboot about 14 hours, but then when I connect it to the Wi-Fi and open browser it rebooted again. So i don`t know what I can do more. And the worth problem - I don`t understand WHY it rebooting.
I try to pull out battery for some hours, but it doesnt help. How battery can help?
Click to expand...
Click to collapse
Sorry I don't really know what omap flash is but I know it is a beautiful saving method where you don't even have to insert a battery. As far as I know it just flashes stock kernel and ROM on your device. If you want more information you should try google . I don't know how the battery can help but it works for some people. It's worth trying. Maybe you can try an other radio. It is a sticky thread. Just flash the right one and see if it works.. Hope this helps.
Sent from my Galaxy Nexus using XDA Premium HD app