As title, i restarted my phone and it just bootloop and i went into recovery and reflashed but still same. please advice.
Holding down power button and volume down simultaneously, during powering up.
Do not just turn off and turn on your phone because it will new HTC Sense, you will not enable the recovery mode.
Once you entered the recovery mode launch the tool, which we called update.zip.
amplister said:
As title, i restarted my phone and it just bootloop and i went into recovery and reflashed but still same. please advice.
Click to expand...
Click to collapse
You get bootloops right after you reflash and reboot? Or did you restore any apks and got the bootloop afterwards?
Get into CWM, wipe everything (system/data/cache/dalvik cache) and reflash the rom. This will certainly help And you should also check if the md5 sum of the downloaded file matches with the one Mike has posted.
Are you errased a cache ? Else, wippe it, and reboot..
I rooted my phone using ODIN. And tried to backup efs by using an app called efs backup.
the phone randomly restarted and kept reeboting..I went into the recovery and it said e:unable to mount /efs
I did a factory reset
Installed stock rom using odin
NOthing seems to be working..
What can I do?
raddums said:
I rooted my phone using ODIN. And tried to backup efs by using an app called efs backup.
the phone randomly restarted and kept reeboting..I went into the recovery and it said e:unable to mount /efs
I did a factory reset
Installed stock rom using odin
NOthing seems to be working..
What can I do?
Click to expand...
Click to collapse
DO you have a custom Recovery installed? If so, there might be a conflict between the stock ROM and I backup. Try going to recovery, wipe cache and then wipe data(factory reset) and reboot. The first boot takes A lot of time, so as long as the boot animation doesn't loop but does indeed stay n the Samsung text, you are OK
idealisti said:
DO you have a custom Recovery installed? If so, there might be a conflict between the stock ROM and I backup. Try going to recovery, wipe cache and then wipe data(factory reset) and reboot. The first boot takes A lot of time, so as long as the boot animation doesn't loop but does indeed stay n the Samsung text, you are OK
Click to expand...
Click to collapse
NO i had the stock recovery..
When I reflashed the stock rom it stayed on the samsung logo.. how much time does it take?
The stock recover shows the error in red E:unable to mount /efs (invalid argument)
Maybe something went wrong on your backup. So it had some residue instructions it was doing on boot up. I had a similar problem when triangle away crashed while hacking. I did a 'adb reboot' command which I think cleared any nasty commabd and let it reboot normally.
Think of these as those please reboot to apply chances updates on winfows
Sent from my GT-N7100 using XDA Premium 4 mobile app
raddums said:
NO i had the stock recovery..
When I reflashed the stock rom it stayed on the samsung logo.. how much time does it take?
The stock recover shows the error in red E:unable to mount /efs (invalid argument)
Click to expand...
Click to collapse
your solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
but now since u dont have custom recovery i blv u need other way out rather flash the pit partition file first before flashing the stock rom post 4 has the pit file http://forum.xda-developers.com/showthread.php?t=1896696
shhbz said:
your solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
but now since u dont have custom recovery i blv u need other way out rather flash the pit partition file first before flashing the stock rom post 4 has the pit file http://forum.xda-developers.com/showthread.php?t=1896696
Click to expand...
Click to collapse
It says the device should be rooted..I have reflashed the stock firmware..Its not rooted..
is my phone dead?
Any Solutions guys?? please
raddums said:
Any Solutions guys?? please
Click to expand...
Click to collapse
follow the other way out after flashing pit then the stock rom if u still cant just take it to sc instead screwing it more instead falling into any big isuues
Please Help....
I have a GSM galaxy nexus with the latest Slimbean 4.3 custom ROM. Recently my phone randomly started bootlooping. I was reading something on Flipboard when suddenly it rebooted for no apparent reason. When my phone restarted I was waiting for my widgets to load and after about 30s it rebooted again and now for the past two days it doesnt work for for more than 30s before it reboots. I tried to get into Trickster MOD to disable set on boot but I don't have enough time. I've tried everything suggested in all the threads without success.
Here's what I tried so far to fix my phone:
1. I have custom recovery TWRP 2.6.0.0 installed on my phone. I rebooted into recovery and tried to dirty flash Slimbean 4.3 build.1 and GAPPs again. But it continued to boot loop
2. Next I went to the wipe menu and did a factory reset wiping cache, dalvik and data (not data/media) then I reinstalled Slimbean 4.3 and GAPPs. surprisingly when I rebooted it was as if the factory reset did not work. All my apps my widgets and my customizations were still there. I didn't go through the android initial setup process that you normally go through when you do a clean wipe, and my phone again started to boot loop.
3. I decided to forego any data that I have on my phone so I rebooted back into recovery and this time from the TWRP wipe menu I did a Format Data in the hope that it would wipe my phone completely. I expected it to wipe all my data, the ROM, everything except the bootloader and the recovery. Nothing was wiped. Even though I got a message saying success, when I rebooted the phone it booted back into Slimbean and all my apps and widgets and customizations were still there and it started to boot loop again!!
4. so I moved on to the next step. Using Nexus Root Toolkit v1.7.2 by WugFresh I decided to flash a Factory image on my phone first I tried to flash a TAKJU 4.3 JWR66Y factory image in bootloader mode using fastboot. Everything seem to succeed normally... radio.img, recovery.img, boot.img and userdata.img all seemd to proceed normally. After about 10 minutes of going through this I rebooted my phone and still nothing had changed. My phone booted back into Slimbean with all my apps and my widgets and my customization intact and it continued to bootloop again.
5. I repeated the above with a TAKJU 4.2.2 JDQ39 factory image. Again it seemed to complete successfully but when I rebooted it went back into Slimbean and I still had all my apps and my data and my customizations intact. My phone continued to boot loop.
6. I decided to try Odin to flash a factory image. I used ODIN3 v1.87 and loaded the i9250 PIT file to repartition my phone and I loaded a TAKJU 4.3 md5 file under PDA. The process completed successfully showing a bright green pass. When I rebooted my phone keeping my fingers crossed nothing had changed. Slimbean, all my apps, all my widgets, my data and the bootloop were all still there!!
7. I tried the same process with ODIN3 v3.07 however each time halfway through flashing system.img the process would fail and nothing would change.
Right now I'm completely flabbergasted and I don't know what else to try I wish there was a way to completely wipe my phone so that It would have no OS, no partitions, no data, a fresh clean slate that I could repartition and flash a factory image and proceed from there. I'm wondering if there is any tool out there that can do a low level format of the NAND so no trace of any OS or any data remains. Perhaps then I can flash a bootloader and a recovery and factory image. Even if someone could help me softbrick my phone so that it wouldn't boot up, it would be welcome change from this frustration that I'm experiencing. Any suggestions and any help would be much appreciated.
Thanks,
iMethodZ
Have you tried using fastboot?
Sent from my Galaxy Nexus using Tapatalk 4
fried emmc...
try to lock the bootloader, it will still unlocked
Zepius said:
Have you tried using fastboot?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I have tried fastboot erase userdata
erase system
erase boot
erase recovery
erase cache
format userdata
format system
format cache
all commands succeed but they don't seem to have any effect at all... nothing gets erased... all my data is still there
samersh72 said:
fried emmc...
try to lock the bootloader, it will still unlocked
Click to expand...
Click to collapse
How can I attempt to lock the boot loader?
My phone is still under warranty is there anything I can do to completely brick it so I can get a replacement device?
fastboot oem lock
locks the bootloader. if that fails, your emmc is fried.
Zepius said:
fastboot oem lock
locks the bootloader. if that fails, your emmc is fried.
Click to expand...
Click to collapse
well I tried that and the message says "okay" but the bootloader is still unlocked... I guess that means the emmc is fried
Any ideas on how to fry the phone even further so it wont even turn on ... perhaps I'll be able to get a replacement device LOL
Hi, I've managed to use Odin to install the bell with root image, phone now working with I747MVLUEMK5..downloaded clockworkmod recovery manager and used the att recovery image. Downloaded custom Roms, factory reset the phone, wiped cache and dalvik then installed the custom ROM. It installed properly but when I reboot, it won't turn on, I have to do the download mode to recover it back using the Odin. Tried different custom ROM and I made sure they are for this image MVLUEMK5... But same result, it won't boot up... Help...did I miss a step?
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
audit13 said:
Copy a ROM to your SD card, install a custom recovery (I prefer CWM), boot into recovery, wipe cache, Dalvik, data, and system, install the custom ROM, reboot the phone.
Every 4.4.2 ROM I have tried (Valudus, Cyanfox, CM11) will boot with a stock 4.1.2 bootloader or newer so you should be fine.
Do you have any warranty left on your phone? Does your phone have Knox installed?
Click to expand...
Click to collapse
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Too much work for me. There is no need to have root before installing a custom ROM.
Do this:
Use Odin to install Philz Touch Recovery from here (use the tar version in PDA, do not check auto reboot): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Once it flashes and you see Reset in the windows, pull the battery, disconnect the phone from computer, boot into recovery, wipe cache, dalvik, system, data, flash rom, reboot.
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
snyph3r said:
Thanks for the help...I'll try this tonight...when you say pull the battery, you mean literally take the battery out of the phone? Would it boot to recovery when I put the battery back? or will it normally boot then I would reboot to recovery.
Thanks!
Click to expand...
Click to collapse
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
audit13 said:
Yes, remove the battery. Disconnect the USB cable, replace the battery, press volume +, home, and power to get into recovery. Wipe cache, Dalvik, system, data, and flash your custom ROM.
Click to expand...
Click to collapse
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Most of the 4.3 roms take a long time at the first boot once you flash it (when I flashed S3Rx it took 3 minutes 32 seconds, I timed it because most people say I waited a long time but have no recollection of how much time) it will stay at one of the boot image screens for several minutes then it should vibrate once the blue led should illuminate and then it will finish booting.
If the wait is too much for you turn it on, set it down, walk away, find something to do, 10 minutes later come back, if it hasn't booted now make sure you followed all the instructions correctly and flashed the right stuff for the phone model you have.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
To make sure we are on the same page, is it just stuck at a boot screen or is it getting to a screen turning off and going back to the same screen repeatedly?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
snyph3r said:
Okay, installed Philz recovery using Odin, pulled bttery, unplug usb then boot to recovery...Philz recovery booted, was able to set to factory, wipe cache,dalvik and flash beanstalk rom,...rebooted the system and still shows samsung logo for a sec and phone turned off....I was still able to go back to phils recovery and tried a different rom and it did the same...just not booting up after flashing...
One thing I noticed is when flashing the rom it doesnt take long (less than 2 minutes) then it completed withoiut error....could it be the zip file or the SD card where i copied them?
Click to expand...
Click to collapse
Try a different ROM. I use validus and it installed without a problem.
audit13 said:
Try a different ROM. I use validus and it installed without a problem.
Click to expand...
Click to collapse
I was able to flash Validus and And Candykat but could not flash Omni and Beanstalk....flashes with no error but just wont boot up...
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
snyph3r said:
I quickly checked the difference between validus/candy Kat vs omni/beanstalk...I looked at the updater-script and found that both validus and candykat doesn't have "assert((getprop...." lines in the beginning of the script, they start at mount ("ext4","EMMC.... line...I wonder if I take the assert lines on the Omni and Beanstalk updater-script if it is going to work..
Click to expand...
Click to collapse
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
audit13 said:
You can remove the asserts and try, but the phone still may not boot. Any particular reason you want Omni or Beanstalk? I personally prefer Validus.
Click to expand...
Click to collapse
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
snyph3r said:
didn't work without the assert either....just wanted to try different Roms...I'm on Validuz now but having a couple of issues...WiFi is not turning on, have to reboot to turn it on and reboot doesn't work either. It won't turn on unless I pulled the battery which is a pain....
Click to expand...
Click to collapse
That is strange. I run validus on mine and WiFi is fine. Calls and data ate fine as well.
snyph3r said:
Here’s the Steps I went through:
*
I have a Bell S3 with 4.3 JB from OTA
*
1.******Downloaded Odin to my PC
2.******Downloaded the image from* 66 CF Root….
3.******Loaded it to my phone (Using Odin)
4.******Made sure the phone is rooted after and it is
5.******Downloaded CWM Manager from Playstore
6.******Changed the Recovery image using the Manager to Samsung Galaxy S3 for AT&T (d2att)
7.******Downloaded Omni Rom then moved it to the SD card using My File app
8.******Rebooted to Recovery
9.******Backed up my phone
10.***Did a Factory reset
11.***Did a Wipe Cache
12.***Did a Wipe Davlik
13.***Flashed the Rom with no error
14.***Rebooted to System
15.***Samsung Logo showed up for a sec then the phone is dead
16.***Tried to turn it on by pressing the power button but not working, I thought the battery was drained when I rebooted, I plugged it in for half an hour but still not turning on. Was able to press the power_
17.***Vol down and home and it booted to Download mode
18.***Used Odin to load the image frok step 2 above and tried the same steps using different rom (Beanstalk-4.4) and the result is the same
Click to expand...
Click to collapse
Just curious... are you going into mounts and storage to format system along with the factory reset and dalvik / cache wipes ??
Hi everybody,
some time ago I flashed my ace II with cm 11 build 20141118 by ace2nutzer. Installation was ok and it worked properly. However, it had some minor problems, one of which was that battery wouldn't charge while booting the phone. One day it happened that my phone arrived at 0% battery and shut down. I couldn't find a way to turn it on because of the too-low battery, so I tried to see if during recovery mode maybe the battery would charge... but, instead of going to recovery, I pressed the wrong buttons and entered into download mode. There, the phone wouldn't charge and at one point it shut down. After some days I discovered that I could charge the phone by simply connecting it to a computer... But now it won't start. It gets bootloop (more precisely it keeps restarting) at the samsung logo. I tried to reflash the build I had before, but I keep getting status 7 error (even after deleting asserts).
Soo, is my phone bricked? Is there anything I could do to make it work?
Thanks to anyone that will help me
tl;dr: phone shut down during download mode, now bootloops and gives Status 7 error (even after deleting asserts) while trying to flash the same ROM it had before.
Anyone?
I forgot to say that I had a nandroid backup, but I can't restore it: it says "error while restoring /system!".
Ascan said:
I forgot to say that I had a nandroid backup, but I can't restore it: it says "error while restoring /system!".
Click to expand...
Click to collapse
Just install the stock firmware using ODIN and start from scratch
LS.xD said:
Just install the stock firmware using ODIN and start from scratch
Click to expand...
Click to collapse
Doesn't work. Odin doesn't give any error, but the phone keeps bootlooping.
Ascan said:
Doesn't work. Odin doesn't give any error, but the phone keeps bootlooping.
Click to expand...
Click to collapse
Try to enter stock recovery and clear cache + perform factory reset .
LS.xD said:
Try to enter stock recovery and clear cache + perform factory reset .
Click to expand...
Click to collapse
CWM recovery is the same? Btw still bootloop...
Ascan said:
CWM recovery is the same? Btw still bootloop...
Click to expand...
Click to collapse
CWM is a custom recovery. stock recovery is the one you have installed with the stock firmware.
LS.xD said:
CWM is a custom recovery. stock recovery is the one you have installed with the stock firmware.
Click to expand...
Click to collapse
Ok, how to access it then? If I press volume up + power + home, CWM starts.