Last night was trying to flash a rom, BUT I was actually half asleep while i was flashing.
So from what i remember before falling dead asleep is, i flashed the rom successfully but Cant be sure whether i rebooted after flashing or not.
and now my phone is actually not turning on, dead battery is for sure the reason, i've searched for the problem, and found 60% of my problem to be the same as others but no one mentioned whether they were flashing rom or what :/
So please could any one help me turning my device on or tell me any other way ?
The solution they've mentioned in the forum i've found is a bit confusing :/
Has anyone else been in this situation as well ?
Plug it in for a few hours and then try again.
Transmitted via Bacon
Related
Hii......All...
My G1 can't boot.....
I already try Hard,soft,snd factory reset but still don't working.......
I buy 2 batteries but still don't work.....
Please Help Me......
Have you tried booting into recovery mode and flashing the RC29 NBH? How did you manage to get it to this state?
How booting into recovery mode and flashing ?
Device not respon all command....
One red blip flash if change a batteries...but it never on...
http://forum.xda-developers.com/showthread.php?t=442480
Follow the instructions for downgrading from RC30/RC8 or higher. After your phone is reset, it will be on RC29 (or RC7 if you have UK phone) with all previous data wiped.
But i don't know latest RC in my G1.....
I plug my G1 to my comp but nothing happen....
it look like already totally dead.....
Would you mind telling us what you were doing on the phone before this happened? It might help us help you better.
All normal before happen.....
I get up for sleep and just off...
I try turn on.....but nothing...
My friend say the problem is software....need flashing....
It doesn't matter what the latest RC in your phone is. Just follow the instructions for downgrading from RC30/RC7 and your phone will be RC29 (they will actually work for any RC) and hopefully recovered.
aloners89 said:
All normal before happen.....
I get up for sleep and just off...
I try turn on.....but nothing...
My friend say the problem is software....need flashing....
Click to expand...
Click to collapse
It could be a hardware failure if you didn't make any software changes and the device died.
I actually had the same issue with my first G1, went to bed and everything was fine, when i woke up the phone was dead, would not turn on, only blue blinking led on top, tried another battery and nothing. wasn't even rooted. I ended up sending it back to tmo for a new one.
Yeah, if you're getting no response from anything it sounds like a hardware issue. Send it in for a replacement.
I'm Indonesian.....
How i can replacement????? That impossible......
Sorry i little upset......
Just share my problem....
Thanks for comment.....
Ok I have searched and found no answer to the problem I am having. So hopefully someone can help me out since there are alot of very intelligent people on here. So here is what im experiencing... I recently modded my phone to the CM10.1 and used it for a while and it was very nice to have but there were a few issuse that botherd me and im not complaining very good work. The thing that was bothering me was the audio glitch. I listen to music all the time and no matter what I used ie. IHeart Radio, Pandora, or my own audio files the audio was just to glitchy for me so I decided to flash it back to stock using Odin. Everything went great in that respect but now at random points my phone just shuts off and then goes into a boot loop with the samsung logo. Now I can get it to stop by pressing the power button a few times and it stops and boots right up as normal. It almost seems like it does it when I have a few things going on at the same time like listening to music and texting but i cant pin point what it actually making it do this. I also notice that I can have a full battery and once it boot loops sometimes the battery is the same and sometimes it comes back showing next to nothing. Just today it went from 100% battery, went to the boot loop, got it to boot back up but now the battery is at 11%. I have been dealing with this for a few days now and was wondering if anyone has heard of this problem and if so does anyone know of a solution? I thougth about flashing back to stock again using Odin but I dont want to mess the phone up even more. Thanks for your time.
You might have a bad flash or download.I'd try doing the 3 wipes and flash again it won't hurt it.I have had mine do some strange stuff before doing this always fixed my problems.Good luck.
Sent from my SGH-I997 using Tapatalk 2
similar problem
hello I didn't want to start a new thread... I'm a noob and am worried you guys might flame me for it haha. anyway so ive been trying to fix my infuse for 2 days now. it wont load past the Samsung intro screen. It wont do anything other than to boot into download mode. I tried using odin as suggested in http://forum.xda-developers.com/showthread.php?t=1116251 i tried it several times and it didn't seem to work. I followed the steps and when I'm done i have the same problem it wont ever make it past the Samsung logo Maybe I'm going about this the wrong way. please help me or refer me to the correct thread
Thanks
gaijin90 said:
hello I didn't want to start a new thread... I'm a noob and am worried you guys might flame me for it haha. anyway so ive been trying to fix my infuse for 2 days now. it wont load past the Samsung intro screen. It wont do anything other than to boot into download mode. I tried using odin as suggested in http://forum.xda-developers.com/showthread.php?t=1116251 i tried it several times and it didn't seem to work. I followed the steps and when I'm done i have the same problem it wont ever make it past the Samsung logo Maybe I'm going about this the wrong way. please help me or refer me to the correct thread
Thanks
Click to expand...
Click to collapse
Your intentions are good, but I think that all will be better served with a brand new thread. Otherwise, it gets confusing who's symptoms we're talking about. It might help to describe what you see when you try to use Odin. (And describe if you can get to recovery mode and to download mode.)
I had a hell of a time but I think I finally got it. I first formatted the internal and external SD cards. I flashed back to stock using Odin and did that about 3 times. Everything worked. But was having a problem with the Google play store I couldn't download any apparently I kept getting an error so I cleared the data and cache from the play store and the Google framework and rebooted the phone. I have been testing it out all day and so far no problems. I will keep posted of any changes problems... thanks again
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
yes, also a faulty or non-OEM cable would be the culprit.
SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.
This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...
Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app
I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol
Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.
Hi
Yesterday I was flashing some custom roms, but then I decided to install Magisk, it completely failed but everything was fine until I unplugged the phone, It only lasted 30 seconds when it suddenly turned off, the battery was working fine and 90% charged, but a curious thing is that if I enter in Recovery Mode, the Mi 4i can stay on all the time without the charger, it happens just when is trying to enter into the system, so Idk what can solve the problem, I already flashed the stock ROM but it's happening exactly the same, I hope if one person knows what to do or if it is a problem with the battery, the software...whatever it is, just tell me so I can solve it (I don't know if this topic was covered before but I tried to search the forums and it seems like this topic wasn't covered) (aaand sorry, my English is not perfect so I hope I have explained the problem and if you want more details, just let me know )
AithonML said:
Hi
Yesterday I was flashing some custom roms, but then I decided to install Magisk, it completely failed but everything was fine until I unplugged the phone, It only lasted 30 seconds when it suddenly turned off, the battery was working fine and 90% charged, but a curious thing is that if I enter in Recovery Mode, the Mi 4i can stay on all the time without the charger, it happens just when is trying to enter into the system, so Idk what can solve the problem, I already flashed the stock ROM but it's happening exactly the same, I hope if one person knows what to do or if it is a problem with the battery, the software...whatever it is, just tell me so I can solve it (I don't know if this topic was covered before but I tried to search the forums and it seems like this topic wasn't covered) (aaand sorry, my English is not perfect so I hope I have explained the problem and if you want more details, just let me know )
Click to expand...
Click to collapse
were this your 1st time flashing rom?
if not im suggesting u revert back to stock rom using fastboot and miflash tool
after that try to see your battery working or not, if not its hardware default u gotta change new battery
if battery ok reflash your custom rom
im sorry but i dont quite understand your full problem
in twrp u can save log
click advance then copy log to sd card with that developer can help u easily