Related
Hello, I made a very foolish decision today. I just recently rooted my phone (i747), and i am still not familiar with roms or flashing or any of that. I installed the Rom Manage app by clockworkmod onto my phone. I did no other preperation other than creating a backup through that app on my phone. Then using that app, i downloaded the CyanogenMod 10.1, directly onto my phone. It then gave me the option to wipe data which i chose not to do. It then started the installation of the rom. Everything started off okay and it looked like it installed. When it rebooted it got stuck on the CyanogenMod circle boot and no matter what i try i cannot fix it.
I cannot stress this enough. I am very new to this stuff and am not exactly sure how everything works. It is my mistake and i understand it was the outcome of my stupidity. However, all I am trying to do is fix my phone. When i try to boot into recovery mode (power, home, and up vol) it just restarts still in the boot logo. Whenever i press power, home, and volume down it says "booting a custom rom can harm your device are you sure?" but whether i choose yes or no it is still stuck.
Sorry about all the text, but can somebody please explain to me in the most noob friendly way possible how i can just get my phone in working condition? Thanks for your time
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
I would suggest to download the CM10 ROM from their thread, and copy it to an external sd card. You can reflash it from the sd card in the recovery menu.
ya, now that you know how to successfully get into recovery, i would flash a rom and gapps again via that route. check out the link in my signature. its got some stuff to look over for a safe and smooth backup & installation
Thanks!
xBeerdroiDx said:
Try booting into recovery this way, in this button pressing order: Vol up + home + power. When your phone vibrates and you see the blue text in the top left corner of the screen, release just the power button.
If this gets you into recovery, you can wipe data, cache and dalvik (under advanced) to see if this clears your issue.
For future reference, don't flash ROMs in rom manager. Only use that app to update or install recovery.
Click to expand...
Click to collapse
Thanks! I couldn't get it to boot into Recovery until I saw your post.....
Thanks. I was stuck in CM11 loop.
Is this also applicable to HTC Desire 816. sorry for crushing, I am just getting frustrated on this matter. tried using my computer to boot from fastboot and tried also pressing the power button while pressing the -Volume. But still on the same cycling LOGO. Please help me if anyone knows how to fix this. Iv also tried to open the back of my unit. but the battery is embedded to the phone.
....
wrong post
how to fix
crayonslayer said:
Thanks, that got me into recovery mode. I wiped the dalvic cache, and did a factory reset, but I am still stuck in the boot
Click to expand...
Click to collapse
maybe you tried to make an advanced data wipe and selected internal storage, dalvic, cache, etc.
what you need to do is put the phone in recovery mode again, select install and then scroll down to find the OS zip that was broke when wiping, after flashing be sucessful reboot system. then turn off the phone again o get it in recovy once more, select install, scroll down but this time you must to install Gapps. to conclude you need to flash OS and Gapps again through recovery mode.
hope this help
Hey all,
Hoping you guys can help me with an issue I'm having...
I was running the Dirty Unicorns new rom for my sgh-t989d and it was working awesome until I decided to backup my rom via recovery using rom manager. The rom failed to update, so I hit reboot and then it wouldn't boot just a black screen, but could still access download mode.
Have been trying to flash back to stock with odin but every stock rom is hanging up at the S animation in the boot. It just loops the colour animation.
My guess is because I need to wipe the cache and factory reset, but can't try that as I can't access CWM, only download mode for some reason.
Tried a few different versions of odin and different Telus and Koodo roms, nothing working yet.
Any tips are much appreciated, thanks in advance!
can you adb reboot recovery?
Try to reboot in recovery by pressing the Vol up, Vol down and power button. When you see samsung logo release power button while continuing to hold both the vol buttons. The phone should reboot into recovery.
Then wipe data, cache, dalvik and flash any rom of your choice.
Hope this helps.
:laughbviously you are responsible if your device blasts or something.:laugh:
SOLVED! I can get into manual mode now. Always held the buttons too ling until it would reboot, thanks for the suggestion.
Cleared the cache and reset a few times and now it's working. Thanks! Now back to re rooting and installing the rom again.
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, my S4 mini entered a boot loop and pressing volume up+home+power doesn't enter recovery mode.
I haven't been playing anything strange with it, it has stock rom.
I just boarded a plane, put it to plane mode and when I landed it was like this.
Please help, I don't know what to do.:crying:
Thanks
Flash stock firmware using odin.
Or you can try flashing a custom recovery and making factory reset. You will lose data but phone will recover.
Stock rom odın flash, recovery wipe data ve cache and reboot
Sorry bad for English
Sent from my GT-I9190 using XDA Free mobile app
Thank you, but Odin is only for windows and I don't have it.
Any other program for Mac that could do that?
If possible I would not want to have the phone factory reset, I haven't done anything to justify this.
With my previous galaxy I had been playing and I could understand something similar,
but with this one I did absolutely nothing, do you understand why it happened?
I think you can not solve without turning to factory settings
Data are data without opening the phone what I will do if you can work something yok.he half of
Sorry Bad For English
Ok, I managed to get a windows PC and flashed the rom again with Odin.
It turned out that is not the problem. The problem is that after that (as much as before), when I start in recovery mode it shows the dead android and says "no command", after which it enters the boot loop again.
Now the phone has a freshly flashed stock rom, so what could it be???
I also flashed CWM-recovery and stil I can't get into recovery.
Kinda desperate now!
yukdav said:
I also flashed CWM-recovery and stil I can't get into recovery.
Kinda desperate now!
Click to expand...
Click to collapse
Just grab a latest build of any custom recovery for your device and flash it via odin.
Use TWRP or CWM latest builds. Once they flash successfully and the screen turns off
as device reboots, press and hold home and vol up keys which takes u to recovery.
Now go to advanced wipe and choose cache, data, dalvik AND INTERNAL STORAGE.
It is recommended to wipe internal storage this time. Just in case. Then reboot.
Thanks, but in which way is your suggestion different from what I just did?
yukdav said:
Thanks, but in which way is your suggestion different from what I just did?
Click to expand...
Click to collapse
Oh sorry. So it does not work even with custom recovery....
Did you try to flash it with a pit file earlier ? I mean did you do any re-partition ?
This is indeed really strange.
I tried CWM, not TWRP.
I don't know what a pit file is, I didn't repartition it, I did absolutely nothing to it.
I boarded a plane, put it in plane mode (I think) and when I landed 9h later it was off.
When I started it, it boot looped and no recovery.
Ok, now I tried also TWRP, nothing new
Does anybody have any further suggestion? I'm totally stuck and without phone almost a week now.
yukdav said:
Ok, now I tried also TWRP, nothing new
Does anybody have any further suggestion? I'm totally stuck and without phone almost a week now.
Click to expand...
Click to collapse
Better to take the phone to service center.
They will solve it.
even better I'll buy an iphone next time
I can get my one plus 3 into fastboot mode but that is it, I have tried wiping the cache and user data from there, I have tried flashing both the stock recovery and TWRP, everytime I try to boot into recovery I get a few seconds of the boot screen and then nothing?
Any help would be wonderful, if you need more info let me know,
Mac
I had a similar problem as you, managed to get into fastboot, but no recovery at all, neither stock nor TWRP. Flashing TWRP again didn't help, although process ended successfully.
Same thing for flashing the whole ROM.
What saved me from getting remote support from OnePlus was this wonderful HOW TO:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I lost all data, but it's a price I payed gladly in order to get my OP3 back
Good luck
McreativeH said:
I can get my one plus 3 into fastboot mode but that is it, I have tried wiping the cache and user data from there, I have tried flashing both the stock recovery and TWRP, everytime I try to boot into recovery I get a few seconds of the boot screen and then nothing?
Any help would be wonderful, if you need more info let me know,
Mac
Click to expand...
Click to collapse
After flashing, try to boot directly to recovery by pressing the button combination.
I got it to work in the end by flashing CM recovery and then working my way from there