Related
I have successfully rooted my Telus desire (Superuser app is available) , however everytime I try to flash a custom rom with rom manager it hangs when booting into recovery.
I get the HTC boot screen then a black bar appears at the top then the device shuts off. The only way to get it back is to remove the battery.
The first time I flashed just the regular unrevoked clockwork recovery but if I booted into recovery with that one I would have to clear storage to even get it to boot up again.
I just flashed Amon RA's and while I get the same black bar problem I still cant' boot into recovery.
I have tried to install older kernels and amon ra to no avail.
Please help!
Thanks!
I'm also thinking maybe I need to reflash back to stock and then try re-rooting again. I can't find a Telus stock rom as it is so new, can I flash any other carrier's?
Edit: it even freezes when I run unrevoked again, it goes through the process, says its done but the phone freezes.
I know exactly what your problem is. It's not that you are unable to boot into recovery, but that you cannot see the recovery options because you flash a clockwork recovery ROM that has no SLCD support.
I had this exact same problem. You can try the following steps. Leave the phone unplugged via USB as it may throw off the timing:
1. Hold volume down, then press and hold power for 5 seconds. This will get you to the HBOOT menu.
2. Wait 20 seconds so that the phone can complete the SD card check.
3. Press volume down once, then press the power button. This will select the Recovery option.
4. Volume down 5x. This should have you on the Nandroid option.
5. Optical button in. I'll call this 'enter' for the time being.
6. Volume down once, and press enter. This will select the Restore option.
7. Enter again to select the Nandroid restore point previously created by unrevoked3.
8. Volume down 7x and enter to confirm restoration.
9. Wait 7 minutes (I timed this) for the copying to complete, and press enter to reboot.
If all goes according to plan, this will have restored your original Telus ROM.
Now, to set up your Telus Desire properly:
1. Connect your phone to PC in mass storage mode or use a MicroSD reader. Download ROM and radio .zip to root directory of your SD card. DO NOT run unrevoked3 yet. DO NOT use the OpenDesire ROMs that are current at time of writing. They do not support SLCD at this time.
2. Download SLCD-specific recovery img from hxxp://forum.xda-developers.com/showthread.php?t=748618
3. Open unrevoked3, direct the program to use the image you just downloaded, and connect your Desire.
4. After some time, the phone will reboot into recovery mode.
5. Wipe the device
6. Use the update from .zip option to select ROM. After that's done, do the same with the radio zip file.
7. Reboot and you should boot properly into your new ROM.
YOU MUST use the updated SLCD Clockwork Recovery.
YOU MUSTN'T use ROM Manager from the Market. The recovery file it automatically downloads does not support SLCD.
Thank you so much that makes sense.
Its weird because other people with the Telus Desire have been able to flash leeroid. I failed your instructions the first time, but I will try again and keep you updated.
Thanks!!
I don't have a Desire but allow me to ask: If the phone is rooted (and boots up properly otherwise) but just has an inaccessible recovery, can you use flash_image to flash the recovery with SLCD support? This would reduce the bumbling-around-on-a-blank-screen factor.
cmstlist said:
I don't have a Desire but allow me to ask: If the phone is rooted (and boots up properly otherwise) but just has an inaccessible recovery, can you use flash_image to flash the recovery with SLCD support? This would reduce the bumbling-around-on-a-blank-screen factor.
Click to expand...
Click to collapse
This is what I did and I got it to work somehow.
What I did was I flashed the custom image, then it still didn't work.
Then I flashed the clockwork image from rom manager and then it worked for some reason!
Thanks guys, weird though!
Did you root your Telus Desire with these steps? I did and no problems at all!
http://forum.xda-developers.com/showthread.php?t=748618
h46it said:
Did you root your Telus Desire with these steps? I did and no problems at all!
http://forum.xda-developers.com/showthread.php?t=748618
Click to expand...
Click to collapse
No I didn't, thats why I had a problem, I solved it though with that custom recovery after all.
I HAVE A NEW PROBLEM THOUGH GUYS.
I partitioned my SD card through rom manager and now when I boot with the two partitions it stays stuck on the HTC boot screen. I removed the SD card and it booted fine, i erased my ext3 partition in windows and now it boots but I wanted to reinstall froyo with a2sd+ .
Also, I now get a triangle when I try to do things in rom manager saying that the update.zip can't be found.
This program is really pissing me off.
Help!
what i did that i think worked, was boot into fastboot,
Then through the android sdk fast boot
just pushed the SLCD recovery (renamed to recovery.img)
fastboot flash recovery recovery.img
reboot bootloader
then go to recovery
it should work, it worked for me
THanks for the reply,
I'm all good.
Reflashed the custom image and all is well.
I had this exact same problem. You can try the following steps. Leave the phone unplugged via USB as it may throw off the timing:
1. Hold volume down, then press and hold power for 5 seconds. This will get you to the HBOOT menu.
2. Wait 20 seconds so that the phone can complete the SD card check.
3. Press volume down once, then press the power button. This will select the Recovery option.
4. Volume down 5x. This should have you on the Nandroid option.
am I doing the above #4 on the white HTC screen? becausethat's what comes up after I select recovery option?
Don't bother with those steps. Just re-root with the custom SLCD image with unrevoked.
Thank you !
Sent from my HTC Desire using XDA App
is there a fix to prevent this from happening?
i can randomly get into my recovery (it is the proper SLCD recovery image)
and i can install cyanogens rom.
however as soon, as i reboot or for example wipe my battery stats in the recovery, my phone just sticks at the HTC screen
Hi,
I fixed this problem when I reinstalled the Flash CloclworkMod Recovery in ROM Manager.
Sent from my HTC Desire using XDA App
Sgt.EddieWinslow said:
is there a fix to prevent this from happening?
i can randomly get into my recovery (it is the proper SLCD recovery image)
and i can install cyanogens rom.
however as soon, as i reboot or for example wipe my battery stats in the recovery, my phone just sticks at the HTC screen
Click to expand...
Click to collapse
This is what happens to me as well. I dont know what Telus is but im on 3 (uk) with hboot 0.83 slcd.
this sticking at the htc screen has only started for me since i first wiped battery stats....although i was only running for 2 days previous it worked and rebooted fine before this wipe and now it is sporidic to say the least.
When i boot up with power+vol down, it checks my sd card and says something like cannot find img.
If i remove my sd card after it hangs and reboot, i can get past the htc screen everytime.
Perhaps the "wipe battery stats" option is broken on Telus Desires. What if it's looking to wipe some particular values in memory but it hits the wrong one?
dferg said:
This is what happens to me as well. I dont know what Telus is but im on 3 (uk) with hboot 0.83 slcd.
this sticking at the htc screen has only started for me since i first wiped battery stats....although i was only running for 2 days previous it worked and rebooted fine before this wipe and now it is sporidic to say the least.
When i boot up with power+vol down, it checks my sd card and says something like cannot find img.
If i remove my sd card after it hangs and reboot, i can get past the htc screen everytime.
Click to expand...
Click to collapse
my solution was to flash pb99img zip file and access recovery to reflash a new rom
dash4g said:
my solution was to flash pb99img zip file and access recovery to reflash a new rom
Click to expand...
Click to collapse
Any chance for you to explain that a bit better? Not sure what you mean there. :/
Flash the file...then go into recovery to reflash a rom? Is that what you did?
After flashing the pb99img file, can you boot into recovery every time without that white screen of death?
Sgt.EddieWinslow said:
however as soon, as i reboot or for example wipe my battery stats in the recovery, my phone just sticks at the HTC screen
Click to expand...
Click to collapse
Update you're Radio. You wont have that problem again.
Sent from my HTC Desire using XDA App
hello all, my first post.
I have incredible, rooted, with cyanogenmod 7. it has been working as normal for months and months. the other day, it just got stuck in the boot animation. i hadn't changed anything, system tweaks, etc, right before this.
i hold volume down and press power, and it goes to bootloader mode. normally here, i can select RECOVERY, and then goes to the black screen, where i could do many things, drastic as wipe the phone, reinstall cyanogenmod, g-apps, etc.
whats my problem now, is that when i hold power down and power and get to the white recovery screen, if i select RECOVERY, it doesnt go where it used to. it goes to the OTHER white screen where choices are, REBOOT, POWER DOWN, etc. So i select to go into recovery mode (the black screen) but it never goes there now. Always did before. Just goes to that next white screen, letting me reboot and start the cycle over again. I've tried with no SC card, no difference.
I found a post someone giving specific directions to format sd card, put radio update only on card, and boot with that in phone. I did, and it successfully said it updated, but still nothing has changed.
I cant get into recovery mode, to reformat, wipe, run any updates, nothing. I've tried so many times i can't even guess. I think it has become a brick. But I finally posted here hoping i may find some advice.
Anyone have any ideas of what i can do, if i can get into recovery mode?
if this helps, this all the info on the white screen - holding power down and powering on:
HBOOT-0.92.0000
MICORP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0000
Jul 23 2010, 10:06:51
thanks,
ben
Have you tried installing the latest recovery through ROM manager? I've no idea why this would have happened but if we can get you there. We can fix it
Sent from my ADR6300 using xda premium
i cant boot fully, so i cant access ROM manager.
bluedimensional123 said:
i cant boot fully, so i cant access ROM manager.
Click to expand...
Click to collapse
Flash this thru hboot. It the latest cwm recovery. You are s-off right?
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Also the radio version you posted above 2.15.00.0000, is that a typo? I have never seen that radio version before.
cmlusco said:
Flash this thru hboot. It the latest cwm recovery. You are s-off right?Also the radio version you posted above 2.15.00.0000, is that a typo? I have never seen that radio version before.
Click to expand...
Click to collapse
excuse my noob-ness, term-wise, i don't know what s-off means.
i will try the link to latest cwm recovery zip, next.
and thats not a typo, 2.15.00.0000 is what it says!
bluedimensional123 said:
excuse my noob-ness, term-wise, i don't know what s-off means.
i will try the link to latest cwm recovery zip, next.
and thats not a typo, 2.15.00.0000 is what it says!
Click to expand...
Click to collapse
ok that update worked! because its been a minute, and i'm so hyped to fix this, i am proceeding with extra extra caution; so, remind me what to choose here - i just don't want to get back into that loop. If i need to wipe phone's data, that's fine. My phone will be working and that makes me ecstatic!
bluedimensional123 said:
ok that update worked! because its been a minute, and i'm so hyped to fix this, i am proceeding with extra extra caution; so, remind me what to choose here - i just don't want to get back into that loop. If i need to wipe phone's data, that's fine. My phone will be working and that makes me ecstatic!
Click to expand...
Click to collapse
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
i assume choose apply update from sdcard, and run latest cyanogenmod zip, then g-apps, etc...am i right?
bluedimensional123 said:
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
i assume choose apply update from sdcard, and run latest cyanogenmod zip, then g-apps, etc...am i right?
Click to expand...
Click to collapse
S-off is security off. It allows you to flash images not signed by HTC. At the top of the hboot screen it should say either s-on or s-off. If it let tou flash cwm recovery you are s-off.
Yes enter recovery, wipe everything in mounts and storage and either flash a stock ruu thru hboot, or flash a rom of your choosing. Do not choose aply update.zip choose install from sdcard, and select your roms zip file.
I would also flash a new radio thru hboot, as i have never seen that version of radio for the incredible. http://dinc.does-it.net/Radios.
cmlusco said:
S-off is security off. It allows you to flash images not signed by HTC. At the top of the hboot screen it should say either s-on or s-off. If it let tou flash cwm recovery you are s-off.
Yes enter recovery, wipe everything in mounts and storage and either flash a stock ruu thru hboot, or flash a rom of your choosing. Do not choose aply update.zip choose install from sdcard, and select your roms zip file.
I would also flash a new radio thru hboot, as i have never seen that version of radio for the incredible. http://dinc.does-it.net/Radios.
Click to expand...
Click to collapse
ok, so here's where I'm at now:
updated radio via hboot via last link posted. i can now get to recovery screen, which is awesome, but - i can select any of the options and select one, and then it goes to a black screen with the ROM manager hat logo, with a yellow arrow under it. The arrow does not move or rotate, as if it was processing my command. it just sits idle on that logo forever.
i can hit power to go back to the recovery menu, and selecting nothing, well, does anything!
any ideas? just far your replies have gotten me past the loop i was in, so i eagerly hope there's more input for me now as to why none of the options in recovery screen process when i select them, they just go to a logo with the hat and an arrow (remember, the arrow isn't moving at all).
btw its ClockworkMod Recovery v 5.0.2.0
thanks again,
ben
p.s. - my updated radio is 2.05.00.06.11 now, if that is important.
bluedimensional123 said:
ok, so here's where I'm at now:
updated radio via hboot via last link posted. i can now get to recovery screen, which is awesome, but - i can select any of the options and select one, and then it goes to a black screen with the ROM manager hat logo, with a yellow arrow under it. The arrow does not move or rotate, as if it was processing my command. it just sits idle on that logo forever.
i can hit power to go back to the recovery menu, and selecting nothing, well, does anything!
any ideas? just far your replies have gotten me past the loop i was in, so i eagerly hope there's more input for me now as to why none of the options in recovery screen process when i select them, they just go to a logo with the hat and an arrow (remember, the arrow isn't moving at all).
btw its ClockworkMod Recovery v 5.0.2.0
thanks again,
ben
Click to expand...
Click to collapse
Do not use the power button to select items in recovery. Use the vol keys to navigate, the trackball to select, and the power button goes back.
same thing
i had the exact same thing just last week - stuck on bootloop with cyanogen 7. I tried some stuff for a little but ended up just switching to an ICS rom. which I am much happier with and would highly recommend.
right now im using ICS-Deck AOKP "Ice Cream Sandwich"
(http://forum.xda-developers.com/showthread.php?t=1475936)
and just for your own resource, this page is pretty useful! list of roms and radios and kernals and all sorts of other goodies
(http://forum.xda-developers.com/showthread.php?t=969371)
thank you for helping me out. every post helped, and i got my old faithful incredible up and running!
completely awesome.
thanks.
p.s. in recovery, pressing trackball to select, i would never have tried. amazing sometimes the simplest things can slow us down. many thanks!
ben
htc incredible stuck in cyanogenmod 7 boot loop
My Htc incredible is stuck in cyanogenmod 7 boot loop at first my apps kept saying failed force close then when i went to send a txt it said messaging app failed force close so i tried shutting my phone off and pulling the battery but it still wouldn't work so reset my phone but that's when it got stuck in cyanogenmod 7 boot loop and now i cant get it to do anything at all its just keeps repeating the cyanogen mod 7 boot screen is there anyway to fix this
allyboo93 said:
My Htc incredible is stuck in cyanogenmod 7 boot loop at first my apps kept saying failed force close then when i went to send a txt it said messaging app failed force close so i tried shutting my phone off and pulling the battery but it still wouldn't work so reset my phone but that's when it got stuck in cyanogenmod 7 boot loop and now i cant get it to do anything at all its just keeps repeating the cyanogen mod 7 boot screen is there anyway to fix this
Click to expand...
Click to collapse
Can you enter recovery? If so wipe everything in mounts and storrage except emmc and sdcard, and then restore a known good backup or flash a rom fresh. If that dosent work i would do an ruu.
Can he do a ruu from Fastboot or hboot or cwmi thought he had to be able fully boot to use ruu.
mmyers35 said:
Can he do a ruu from Fastboot or hboot or cwmi thought he had to be able fully boot to use ruu.
Click to expand...
Click to collapse
He can do a PB31IMG.zip ruu through hboot. To do the ruu.exe with a pc you need to be able to boot to enable usb debuging i think.
i was able to do all the listed in this thread. but after 2 days of searching i still can't find a good solution for formatting /data, I get an error everytime and cm7 is the only rom that I can boot on my dinc. however when i think i have fresh flash, some of my old apps are still there.
if i ruu i get stuck on the red eye screen and the phone reboots.
I'm at a loss
eidt
i am root with s-off
cwm 5.0.2.0
Never pull the battery. Always use as last resort....
Sent from my ADR6300 using xda premium
I was using charmeleon 5 with franco r10 kernel when I decided to switch roms to ARHD. I realized i flashed the kernel without first copying over the ARHD zip and am stuck in a bootloop. Is there anyway to remedy this? I have a backup of stock rom in cwm.
Flash the franco r10 boot image, not the modules, whipe (factory reset, cache & dalvik in Advanced in CWM) and flash the backup of your original ROM. Should be fine then
Sent from my HTC One X using xda premium
I had a similar problem, but when connecting the phone to the computer it wouldn't recognise it in the ADB, so I had to use an RUU to bring my phone back to life! That worked, but I had to root it again and then install the rom!
This was all because I earlier wiped my phone so couldn't flash the rom as nothing was on my SD card, or whatever it is called! So morale of the story, make sure you have backups . Was a schoolboy error!
Don't need adb, just fastboot. Can you boot into fastboot? Of not, search the forums for 'back to stock'. Plenty of info.
I learned the hard way too...
Sent from my HTC One X using xda premium
If you bootloop, hold the power button down, youll see the buttons at the bottom flash about 4 times and then the phone will shut off. After that press volume down and hold in until you get into the bootloader. The select recovery and then fix it. Problem solved
Sent from my HTC One X using Tapatalk 2
but...
stumpyz9 said:
If you bootloop, hold the power button down, youll see the buttons at the bottom flash about 4 times and then the phone will shut off. After that press volume down and hold in until you get into the bootloader. The select recovery and then fix it. Problem solved
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You need to flash the boot.img in fastboot first if you want to recover your previous ROM. Unless the USB-mount in CWM recovery is functional (in previous version it wasn't, haven't tried in current version). In that case you can mount your SD from recovery, copy the ARHD ROM to your SD, flash it and you are good to go!
i just rooted with s on and i flashed a custom recovery then rebooted. htc logo came up, and then a black screen its been like an hour with the black screen and it wont boot. i know that normally its takes a long time to boot a fresh rom but this is ridiculous. and i made sure that i flashed a cdma rom marvelc. what do i do!!
i can still boot into the boot loader though
Dude im no expert in HTC phones but you had to turn s-off when rooting your phone. If you made a nandroid backup your in luck reflash your stock rom back and this time root with s-off and enjoy flashing plz hit the thanks button if i helped.
Sent from my Nexus S 4G using XDA
jvill100 said:
i just rooted with s on and i flashed a custom recovery then rebooted. htc logo came up, and then a black screen its been like an hour with the black screen and it wont boot. i know that normally its takes a long time to boot a fresh rom but this is ridiculous. and i made sure that i flashed a cdma rom marvelc. what do i do!!
i can still boot into the boot loader though
Click to expand...
Click to collapse
Boot into hboot with volume down + power. Scroll down to recovery and push power to enter it. All going well you should go into your recovery. If you get a red triangle with an ! Then you still have the stock recovery.
OK now scroll down and make a back UP!!! After that factory reset the device, wipe cache, dalvik cache. Data. Everything aside from your sdcard. Then reboot the device. This should get your device operational again. Reboot should take no longer than 15 minutes.
After that choose a custom rom to flash, or just go about setting up the phone as you want.
When you go to flash a new rom make sure you back up first, then wipe everything bar SD card. Then install the rom and reboot.
Good luck pal
Sent from my HTC Sensation XE using xda premium
still
heavy_metal_man said:
Boot into hboot with volume down + power. Scroll down to recovery and push power to enter it. All going well you should go into your recovery. If you get a red triangle with an ! Then you still have the stock recovery.
OK now scroll down and make a back UP!!! After that factory reset the device, wipe cache, dalvik cache. Data. Everything aside from your sdcard. Then reboot the device. This should get your device operational again. Reboot should take no longer than 15 minutes.
After that choose a custom rom to flash, or just go about setting up the phone as you want.
When you go to flash a new rom make sure you back up first, then wipe everything bar SD card. Then install the rom and reboot.
Good luck pal
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
actually when i was rooting the recovery wasnt working for me the tool tried to made me go into recovery but i was stuck at the htc logo. but the tool also offered to install twrp or clockworkmod i installed clock and still wont stuck at the htc logo so i tried twrp and it worked and then i got rooted.
i think i might be twrp that doesnt install roms right.
also i installed a rom it worked but no wifi and wifi was the most important tool for me so the rom is ussless to me
jvill100 said:
actually when i was rooting the recovery wasnt working for me the tool tried to made me go into recovery but i was stuck at the htc logo. but the tool also offered to install twrp or clockworkmod i installed clock and still wont stuck at the htc logo so i tried twrp and it worked and then i got rooted.
i think i might be twrp that doesnt install roms right.
also i installed a rom it worked but no wifi and wifi was the most important tool for me so the rom is ussless to me
Click to expand...
Click to collapse
ok your recovery is a beta. and as such i dont know if it is fully working. so, we shall try to give you a properl.y working clockworkmod recovery
download this http://www.mediafire.com/?p2p88udo32m9xcg and then put it on to the root of your sd card. boot into hboot and allow it to run the update. then Remove the sd card from the phone then boot back into hboot and scroll into recovery. once their out back in your sd card and then follow my above post .
good luck
fixed!
T
heavy_metal_man said:
ok your recovery is a beta. and as such i dont know if it is fully working. so, we shall try to give you a properl.y working clockworkmod recovery
download this and then put it on to the root of your sd card. boot into hboot and allow it to run the update. then Remove the sd card from the phone then boot back into hboot and scroll into recovery. once their out back in your sd card and then follow my above post .
good luck
Click to expand...
Click to collapse
Thank you you for replying but I did some experimenting around and I found out that the clockwork mod was a marvel recovery
I have a marvelc wildfire so I went to rezo609 folder and found the recovery img and replaced it with a clockwork marvelc img.
Then I opened the prompt selected install clockwork mod, it installed
Then I went to recovery, worked and installed the cm9 rom (marvelc) and gapps and It successfully worked
You were probably right its beta so it has some bugs
But thank you all who tried to help me I really appreciate it
Sorry I just started so I deleted the URL
no problem buddy always happy to help.
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 ??