okay so here it is: (1) I changed a market sms app to a system file and changed to hw message app to user app
(2) Battery ran out this evening and I plugged phone up to charge
(3) Went to use phone, showed 93%, powered on while still plugged in, screen acted finnicky
(was using a different charge cable)
(4) Attempted to change system font with a market app and rebooted, screen froze, hard rebooted
(5) Tried several times to reboot, no go, finally resorted to booting to recovery and doing factory reset (successful)
(6) Even after factory reset phone won't boot. Does splash logo then goes black screen.
(7) Power button causes vibrate when touched, but screen doesn't come back on
(8) I can boot to fastboot or recovery but I'm not sure what else to try. I welcome any suggestions.
I'm freaking out.
Thanks to @xordos and @Modding.MyMind I'm back to enjoying the best device I've ever owned.
If anyone else runs into similar soft brick issues please see the thread xordos started to solve.
does anybody have the factory image from the HAM2 that I could try to flash from my SD card in recovery?
Help may be on the way tonight as TWRP might be released! If you can adb access these files might help:
P.S., regarding the System partition, I do have a system file uploaded, it is taken after it is rooted, it is file level zip, not dd image:
https://drive.google.com/file/d/0B-n...it?usp=
These were provided XORDOS who is helping with the TWRP project,
this was from this thread post 105 if the above link didn't work!
http://forum.xda-developers.com/asc...st-cwm-twrp-customer-recovery-t2868933/page11
Did you get this fixed? I have the same problem
good_apollo said:
Did you get this fixed? I have the same problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55647061
Related
hello, my name is shahrukh and i need some help. i downloaded animmod (from 4shared) and then i donwloaded busybox. then i pressed blur and then it asked me if i want to reboot it. i pressed yes. this is when the problem starts. It turned off and then it turned on half way and then it turned off. it kept doing that and then i just left it for the night. in the morning it was not doing anything. when i held the power button it turned off and on for like two times and then turned off. i cant even start it up so i have no idea what to do.
i don"t know what to do
please help!!!!
Okay, we need details, describe exactly when "halfway on" is. We need your full model number and rom version (if you know it). Have you tried plugging it in to charge? Does it show anything now that you try to boot it? try holding volume up and powering on to enter recovery menu.
details
ok so when it turns on it says samsung. then after like 10 seconds it turns off. it does that for a few times and then it just goes in a black screen. the model number is YP-G7OC/NAW. when i plug it in to charge it goes on and off two times and then off. if it has low battery it just shows the sign. as for the rom i don't think i have any. i just rooted it using superoneclick. if it goes to recovery mode what do i do?
thanks!
(you got me really fired up when i saw the recovery menu!)
If you can get to recovery menu, try a factory reset, and clear cache. I am not sure if there is a recovery rom for your device, you should check samfirmware.com
tried both of them...no luck. and i couldn't find a recovery rom on samfrimware.com.
Your device has capacitive or mechanical home button?
it has a capacitive home button...the usa version
shahrukhraza said:
it has a capacitive home button...the usa version
Click to expand...
Click to collapse
The phone boots in recovery?
If so, I can investigate a little more what's happening.
I'll try to post a return-to-stock image soon... The problem is that mine is cluttered with crap that the zergRush exploit added (it insisted on installing busybox instead of just rooting...)
(I'm not sure, but I think someone else already posted a stock zImage and system image...)
Here is the post about fixing capacitive buttons. A quick search of forum should have found it.
http://forum.xda-developers.com/showthread.php?t=1421797
Sent from my YP-G70 using Tapatalk
nooooooo!!! you guys have all got it wrong. first of all it doesnt boot in recovery. the only way to get in recovery mode is when it shows the battery sign i hold "up volume"+ power button.and the capaciative button is completely fine. im just stuck in a bootloop (i think) and it has nothing to do with a broken capacitive button! i will try to post a video today to show you guys exactly whats happening.
i kind of had the same problem, one time i thought i had entropy's kernel on and i had CWM well i didn't but i still thought i had so i tried rebooting into recovery using the terminal:
su
reboot recovery
then i turned off and went to this weird recovery menu it had four options, reboot system, apply update from SD card, wipe data partition, and power off and it had a ton of red letters and words saying like, couldn't access data partition or cache partition and couldn't access /data/media, or system, and then i just turned it off because i wouldn't let me choose an option, and then i got stuck in a loop but not during when it says SAMSUNG mine happened during the animation music part that look like fireworks and then SAMSUNG would light up blue then go through it again and 2 more times then go black and i tried flashing the US stock ROM in download mode but still would go through the loop and it doesn't even charge so i got nothing
so did you somehow fix yours? and i never got a recovery menu that showed something about shut down.:confused
Before brick
xxxxxxxxxxxxxxxxx
wait....are you asking me those questions? just to tell you im no developer or something. im just a 12 year old who has his galaxy player stuck in a boot loop. you have to make another thread if you have a problem.
sorry!
Ok. : ) You got it wrong. No problem. His case is different from mine. Just wanted to use her Brick in case. Nothing more. good luck.
I resolve my doubts alone. Nothing that Google does not respond. haha
At least before brick.
ok. let me ask google too xD
anyways..anyone have any idea of how to fix this boot loop?
im trying to do the Linux thing by running the ressurector ans the VM windows the forum is posted under development called hard brick recovery for galaxy 5.0
ok.(i have no idea what you are saying...just saying!)
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
My phone model is Micromax Knight 2 E471.
It was working fine but it all happened all of a sudden. I was trying to connect my phone to the computer to access some file. Suddenly, I got a message on my screen that Encryption interrupted with some text and a button to reset. I rebooted the phone but it had the same message and I had no option but to click on the Reset button. From that time until now... it does not want to boot.
Then I searched for it on google and tried to start with two key combinations Power+VolumeUp and Power+VolumeDown. Power+VolumeDown. does not do anything but Power+VolumeUp get me to a recovery screen that says failed to mount /system, /sdcard, /cache and so many things (screenshot attached).
From the recovery option, I tried
1. wipe data/factory reset - doesnt do anything
2. wipe cache partition - doesnt do anything
Then I took it to Micromax service center. They said, OS needs to be reloaded. I paid 250/- and got it reloaded but still the issue was not resolved. Now there is a new problem. When I start the phone, it appears that it is rebooting but there is absolutely nothing on the screen. The screen is completely blank and black. The strange part is that, it keep vibrating after every minute or so which makes me feel that it is caught in a boot loop but nothing is displayed on the screen. The Service center guys says that there could either be a display issue or motherboard issue and in both cases, the hardware cost would be more. But I feel it is a software issue.
I again googled it and got to a page https://firmwarefile.com/micromax-e471 where I downloaded the firmware. The firmware folder had a file "8939_fastboot_all_images" which is a windows batch file. I installed the driver, executed the 8939_fastboot_all_images batchfile and went to the recovery screen I got from Power+VolumeUp key combination. Selected reboot to bootloader. I got lot of things in the ms-dos window but still the problem is unresolved.
I appreciate if someone here could help me what to do next.
Thanks
Something wrong with the mount points, maybe? Have you tried flashing a custom recovery like TWRP?
Adithya FRK said:
Something wrong with the mount points, maybe? Have you tried flashing a custom recovery like TWRP?
Click to expand...
Click to collapse
I cannot do anything with a screen with no display.
Can you tell me how to flash a custom recovery when the phone is in boot loop
Thanks
Your phone seems to have a Snapdragon SOC. Sorry but I'm pretty much useless with that. If it was an mtk you could have removed the battery and use SP Flash tool. Maybe someone else can help you with this.
Good luck.
bump
ACFH said:
First, dont post something like "bump", you can get ban.
2nd, if you cant flash, this tool may have. https://forum.xda-developers.com/showpost.php?p=71705583&postcount=5
This is only one tool can flash rom in this situation. If it not work, it could be hardware issue, not software.
Edit: after install qualcomn usb driver, make sure your phone is turn off, hold volume down button while plug usb cable (some phone need volume up, some need both of them, some doesnt need any button). Remember dont touch power button. If pc detect your phone like Qualcomm HS-USB QDLoader, you can using emmc.
Click to expand...
Click to collapse
Sorry for that!
First of all ToolStudio eMMC Download Tool link does not work. I downloaded the 50MB+ zip file and extracted, it asks for a password which I already put but it doesnt do anything.
Then I downloaded a downgraded version from here https://drive.google.com/drive/folders/0B7SVwjaFGLv_by1OSlMtaU9tQVE but it does not work. mMMC Download or Multil Download does not show RAM, Boot Image etc. The comments on that page also shows that there are so many people who are unable to do it. Do you know of a reliable download source for ToolStudio eMMC Download Tool?
Or do you have any other solution?
Thanks
AM also facing that problem with e471
Always showing flashing successfully .
But booting into recovery mode..
Need solution dear