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 ??
Related
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
i think that flash a new rom would solve this
patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
I wanted to do this... but with my root toolkit it looks like my phone doesn't have usb debugging on (which it was before I tried to flash this kernel). And I can't turn my phone on to turn it on... so hmm.
RMarkwald said:
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
Click to expand...
Click to collapse
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
patriot95 said:
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
Click to expand...
Click to collapse
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
This is KIND of what I'm doing. I can't access my phone from the computer because of the damn usb thing... but I'm going to try to flash back to stock and see if that works.
It's booting now and it's been on the start screen for a minute or two. How long should it take on a stock flash? Just curious how long to wait before yanking the battery and trying again.
How did you flash stock, using fastboot or a zip? These are the stock images correct?
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
patriot95 said:
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
Click to expand...
Click to collapse
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
EDIT 2: You'll want to download and put the zip file in your SDK - Platform-tools folder before you use ADB to push it there.
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
RMarkwald said:
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
Click to expand...
Click to collapse
It makes sense... but I'm a little new so I will try this. Might take me a while.
By the way... these captcha images suck.
Thank you for the help... I am re-rooting my phone now. I was able to get back to stock.
Good job, glad to help!
RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
I LOVE YOU!
(I did the same thing with the auto-flash kernel and was stuck. I totally forgot that you had to hold BOTH up/down with the power button.)
Franco's app SUCKS!
Thanks my man!!! :good:
BTW...Jelly Bean rocks!
Hello guys i have tha same problem with patriot95 (black screen Google and one small lock lower) ... my device is optimus 3d p920 and i cant reboot it .
can you help me ? PLz
This is a problem with the toolkit...
Do you have any adb and fastboot downloaded? No? Download it. There's more than enough instructions on that.
You didn't need to factory reset AT ALL. All you needed to do was just re-flash your ROM and you would've been good to go.
Next time learn how to use adb and fastboot command please. Then, there will be less chance of messing it up and not being able to fixing it.
Hi, sorry this thread is kinda old already but I don't really want to start new thread about same problem. So, similar to OP, I stupidly use the 'autoflash' option from franco app, and I'm stuck now. But I can still have access to CWM recovery. I was using the stock 4.2.2 takju before. I already tried to re-flash stock kernel -> fail. Tried re-flash stock rom - fail. Tried wipe cache and dalvik then flash deodexed 4.2.2 -> also fail. Please help me, I really need to use my phone right now.
Are you flashing a 4.2.2 kernel with a 4.2.2 ROM?
What ROM and kernel?
Sent from my Galaxy Nexus using xda premium
I flashed the stock 4.2.2 rom from the google website but it doesn't work. Then I tried the stock 4.2.2 from this link,
http://forum.xda-developers.com/showthread.php?t=1737849 but also failed.
I also flashed the stock kernel from this link
http://forum.xda-developers.com/showthread.php?t=2151154
Earlier this morning I was trying out a new rom and I didn't like it. I went back into recovery and wiped the cache dalvik and system and flashed a different rom, I think it was paranoidkangdroid. After it booted up I went to the playstore to download TitaniumBackup. It finished downloading but when I went to the app drawer it wasn't there. I just did the steps from http://forum.xda-developers.com/showthread.php?t=1739426 to put a rooted stock image of the phone onto the phone. Odin says that it passed but now my phone is stuck at the Samsung logo. It makes the noise and does the whole ATT splash screen business but it just sits there. It's been like this for about 15 minutes. The phone is still connected to my PC if that makes a difference. Anyone have any idea on what to do?
Edit: I've also posted in their thread.
DynamiteRave said:
Earlier this morning I was trying out a new rom and I didn't like it. I went back into recovery and wiped the cache dalvik and system and flashed a different rom, I think it was paranoidkangdroid. After it booted up I went to the playstore to download TitaniumBackup. It finished downloading but when I went to the app drawer it wasn't there. I just did the steps from http://forum.xda-developers.com/showthread.php?t=1739426 to put a rooted stock image of the phone onto the phone. Odin says that it passed but now my phone is stuck at the Samsung logo. It makes the noise and does the whole ATT splash screen business but it just sits there. It's been like this for about 15 minutes. The phone is still connected to my PC if that makes a difference. Anyone have any idea on what to do?
Edit: I've also posted in their thread.
Click to expand...
Click to collapse
Did you clear data/cache before/after flashing the stock ROM?
If you didn't, boot to recovery (Vol Up + Home + Power) and do so.
smelenchuk said:
Did you clear data/cache before/after flashing the stock ROM?
If you didn't, boot to recovery (Vol Up + Home + Power) and do so.
Click to expand...
Click to collapse
I did it before flashing the new rom. Now the only recovery I have on the phone is what I think is stock recovery. I had teamwin recovery on it and now it looks more like clockworkmod, so I'm assuming that's stock. I went into that recovery and did a factory reset which apparently worked. (As I'm typing this it's fixed)
Mods can delete this thread.
I was going to flash a new ROM on my DHD and did the usual steps: backup using TB, reboot to recovery, factory reset and then go find zip to install on SDCARD. But this time instead of finding my zips I had already transferred, I found none. So I mounted the SDCARD through the recovery menu and transferred the zip using my laptop.
I still couldn't see the zips, so I chose to reboot the phone from the recovery menu. Booted into old ROM, completed the setup wizard and rebooted to recovery again. Still no zips! So I turned the phone off and was just going to boot straight to recovery using VOL UP and POWER but then I only got three short vibrations and nothing happened, so I booted again to ROM and rebooted to recovery from there.
This time nothing happend, nothing at all. And now I'm stuck where I cant boot it, not to recovery, not to HBOOT and not to ROM. Tried taking out the battery and putting it back in. Tried turning it on using just POWER, using VOL UP and POWER, using VOL DOWN and POWER - and in different time length combinations. adb reboot bootloader cant find the phone. The LED doesn't light up when plugged to USB.
ROM: JELLYTIME for DHD/Inspire4g - 4.2.2 R4
Recovery: ClockworkMod
I'm guessing my DHD is completely bricked, right?
benregn said:
I was going to flash a new ROM on my DHD and did the usual steps: backup using TB, reboot to recovery, factory reset and then go find zip to install on SDCARD. But this time instead of finding my zips I had already transferred, I found none. So I mounted the SDCARD through the recovery menu and transferred the zip using my laptop.
I still couldn't see the zips, so I chose to reboot the phone from the recovery menu. Booted into old ROM, completed the setup wizard and rebooted to recovery again. Still no zips! So I turned the phone off and was just going to boot straight to recovery using VOL UP and POWER but then I only got three short vibrations and nothing happened, so I booted again to ROM and rebooted to recovery from there.
This time nothing happend, nothing at all. And now I'm stuck where I cant boot it, not to recovery, not to HBOOT and not to ROM. Tried taking out the battery and putting it back in. Tried turning it on using just POWER, using VOL UP and POWER, using VOL DOWN and POWER - and in different time length combinations. adb reboot bootloader cant find the phone. The LED doesn't light up when plugged to USB.
ROM: JELLYTIME for DHD/Inspire4g - 4.2.2 R4
Recovery: ClockworkMod
I'm guessing my DHD is completely bricked, right?
Click to expand...
Click to collapse
Oh dear poor you, I'm no expert, but unless your battery is dead, I'd say you killed your phone. Can't even get into recovery yikes.
Sent from my HTC Desire HD using xda app-developers app
If your battery is dead you may need to ask a friend to charge it for you? If your phone still boots into recovery you havent killed your phone, if you go to the htc web site & look for the correct software for your phone you may have to apply that to reboot your phone again, but after you will need to root again? But first try another rom a stable one & try doing this - factory reset/full wipe, then wipe cache, then wipe dev cache, then fash the new rom. Hope this helps
sent via my super modded Foxhnd 2.2 with Tapatalk 2
ranger4740 said:
Oh dear poor you, I'm no expert, but unless your battery is dead, I'd say you killed your phone. Can't even get into recovery yikes.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Unfortunately my battery is not dead, confirmed using a working DHD
deanr1977 said:
If your battery is dead you may need to ask a friend to charge it for you? If your phone still boots into recovery you havent killed your phone, if you go to the htc web site & look for the correct software for your phone you may have to apply that to reboot your phone again, but after you will need to root again? But first try another rom a stable one & try doing this - factory reset/full wipe, then wipe cache, then wipe dev cache, then fash the new rom. Hope this helps
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Click to expand...
Click to collapse
I can't boot it at all, not even to recovery.
Unless u can use adb it sounds like your in trouble mate
sent via my super modded Foxhnd 2.2 with Tapatalk 2
I've been having some trouble trying to boot the latest AOKP for some reason, clean install didn't work so I restored a backup from recovery. After that, TWRP asked me for a password soon as I got into recovery. This is the first time I've seen this..and I figure that reflashing the recovery should be all I need to do, then I should be able to reflash AOKP and enjoy, right? Problem is, I can't find a .tar file as goo.im doesn't appear to want to give me the file. :crying:
So before I spend the rest of my day off on a wild chase for a simple file, can anyone tell me if I'm going about this the right way? My searching the issue hasn't yielded much in the way of results. Just want to get my phone back up and running!
EDIT:
I wasn't being clear enough. Despite restoring my backup, it force closed one thing or another every few seconds so I went to recovery to reflash. That's when things failed because of this password. I'm limited to download and recovery modes now, which isn't bad except for I still can't find a .tar to flash via Odin.
Reflashing TWRP hasn't resolved the password issue. Looks like I need to find a new angle..
what version are you on? did you just flash that same version?
Was at 2.5.0.0, and yes I reflashed the same one. I can't remember which version I was on before this one. Any recommendations?
perhaps revert to the previous release. if you're d2att, here's the link to the 2.4.4.0 tar
This version throws the same password prompt. I never set a password for this..didn't even know it was an option
Medlock87 said:
This version throws the same password prompt. I never set a password for this..didn't even know it was an option
Click to expand...
Click to collapse
Just went through trying different versions all the way back to 2.3.3.1 which I know I used for quite a while without any trouble. I want to try CWM but I can't find it in .tar form, just .img
WOW!! I found CWM version 5.8.4.7 on my computer's HDD, and so I flashed it. CWM wouldn't mount my external sd card where my ROM zips are. Got tired of messing with that and so I flashed back TWRP and it came back with the same password prompt. Great... Guess I'm flashing back to stock and starting over.
Medlock87 said:
Just went through trying different versions all the way back to 2.3.3.1 which I know I used for quite a while without any trouble. I want to try CWM but I can't find it in .tar form, just .img
Click to expand...
Click to collapse
follow this link to the root from recovery thread. download the root kit and flash the recovery.tar.md5 file. its an older cwm so after flashing, you have the option to download and flash a recovery flashable twrp zip (to see if that fixed the password issue) or remain on cwm and download/flash a new release
follow the link in my signature. at the bottom of post #2 are the download links for the latest releases to both cwm and twrp. flash in recovery, go to advanced and reboot recovery. presto
---------- Post added at 02:30 PM ---------- Previous post was at 01:48 PM ----------
that resolve your issue? cheers
xBeerdroiDx said:
follow this link to the root from recovery thread. download the root kit and flash the recovery.tar.md5 file. its an older cwm so after flashing, you have the option to download and flash a recovery flashable twrp zip (to see if that fixed the password issue) or remain on cwm and download/flash a new release
follow the link in my signature. at the bottom of post #2 are the download links for the latest releases to both cwm and twrp. flash in recovery, go to advanced and reboot recovery. presto
Click to expand...
Click to collapse
Thanks for that. Flashed a CWM 6.0.3.1 flashable zip after that, and now it's giving me an error trying to flash my ROM zip.. Status 7. Going to try redownloading it..
Update: "Install from sdcard complete." Was starting to think I'd never see those words. I'm sure it'll work now. Thanks so much for your time!
Grrr...It's still doing the same thing that started this adventure. Gets stuck at the underwear kernel loading screen and won't boot up.
CWM and TWRP nandroids are different. If you make a backup with TWRP you cant restore with CWM, and vice versa.
if you're still getting stuck on the loading screen, wipe data/factory reset in recovery and wipe cache. reboot and see if that fixes your issue
xBeerdroiDx said:
if you're still getting stuck on the loading screen, wipe data/factory reset in recovery and wipe cache. reboot and see if that fixes your issue
Click to expand...
Click to collapse
I've tried this many times, nothing's working. I got fed up and used ODIN to go back to stock, and now even THAT won't boot. Went to download, again flashed CWM and tried wiping cache, did a factory reset and fixed permissions. It STILL won't boot. I can't figure out what I did wrong to save my life. This all started with the same wipe procedures I always take when updating AOKP. I'm completely lost right now..
Maybe I spoke too soon. It went from the Samsung GSIII logo to the AT&T logo with startup sound after a long time..now it's sitting here at Samsung for..a long time. Maybe I haven't been giving it enough time.
When you use ODIN to flash back to stock, you usually have to boot into stock (not custom) recovery to wipe data and wipe cache. Otherwise the phone sits at the Samsung logo.
xBeerdroiDx said:
When you use ODIN to flash back to stock, you usually have to boot into stock (not custom) recovery to wipe data and wipe cache. Otherwise the phone sits at the Samsung logo.
Click to expand...
Click to collapse
So, boot into download mode and that will wipe cache? I'm not sure I understand. And you were right, it hasn't progressed past the samsun logo.
No, boot into the stock recovery mode that comes on the device. Don't flash the stock firmware and then flash cwm in order to wipe data and wipe cache. Just flash stock in ODIN with the auto reboot box unticked, when you get the PASS, unplug, pull battery, replace and immediately press the recovery mode button combo. This will place you in stock (Samsung) recovery. That's when you wipe data/factory reset and wipe cache. Reboot. It will take a few minutes to boot initially
xBeerdroiDx said:
No, boot into the stock recovery mode that comes on the device. Don't flash the stock firmware and then flash cwm in order to wipe data and wipe cache. Just flash stock in ODIN with the auto reboot box unticked, when you get the PASS, unplug, pull battery, replace and immediately press the recovery mode button combo. This will place you in stock (Samsung) recovery. That's when you wipe data/factory reset and wipe cache. Reboot. It will take a few minutes to boot initially
Click to expand...
Click to collapse
Will report in a few minutes. Thanks again for taking the time to help =)
When I went to recovery it showed the android guy with the little gearboxes. I guess that's what I was looking for? It rebooted by itself and now I'm just waiting for it.
Yup, that's what stock recovery looks like. Were you able to wipe data and cache before the reboot?
I just installed liquidsmooth 4.2.2 official and googleapps i cleared cache etc before i installed too. Everything installed fine but when I went to reboot the device it wont boot up. I can get back into recovery mode but I unfortunately forgot to make a back up. What can I do? Also my father has the exact same phone as me. If need be can I use his SD card to make a backup and then put it in my phone?
Factory reset.
Aerowinder said:
Factory reset.
Click to expand...
Click to collapse
How do I go about doing that? Sorry I'm very new to this.
Go to wipe in TWRP recovery. Factory reset should be in your options. Then flash again
Sent from my SGH-I747 using Tapatalk 2
rani9990 said:
Go to wipe in TWRP recovery. Factory reset should be in your options. Then flash again
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I;m using clockworkmod recovery v6 .0 .3 .1 and I do not see that option
jakeryan760 said:
I;m using clockworkmod recovery v6 .0 .3 .1 and I do not see that option
Click to expand...
Click to collapse
Wipe data/factory reset.....its the 4th option
Sent from my SGH-T999 using xda premium
707BeastMode707 said:
Wipe data/factory reset.....its the 4th option
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work. Nothing will boot. I tried wipe data factory reset and rebooted nothing, tried it with flash after as well and nothing.
I have the SGH T999
jakeryan760 said:
I tried that and it didn't work. Nothing will boot. I tried wipe data factory reset and rebooted nothing, tried it with flash after as well and nothing.
I have the SGH T999
Click to expand...
Click to collapse
Did you factory reset, wipe cache, and reflash the rom? If that fails I guess at least you can Odin.
Sent from my SGH-T999 using xda app-developers app
Wipe cache
Wipe dalvik cache
Wipe data/factory reset
Flash ROM
Flash gapps
Wipe cache
Wipe dalvik cache
Reboot device
↑if that fails, get to a computer and download another ROM, place it on the SD card, pull the battery out of your phone and insert the SD card. Put the battery back into the phone and boot into recovery and try the steps above, but instead try flashing the new ROM and only flash the gapps if needed (usually stated in the op of the ROMs thread).
↑if it still fails then Odin back to stock and I guess try rooting again.
Sent from my SGH-T999 using xda premium
re: flashing roms
jakeryan760 said:
I just installed liquidsmooth 4.2.2 official and googleapps i cleared cache etc before i installed too. Everything installed fine but when I went to reboot the device it wont boot up. I can get back into recovery mode but I unfortunately forgot to make a back up. What can I do? Also my father has the exact same phone as me. If need be can I use his SD card to make a backup and then put it in my phone?
Click to expand...
Click to collapse
If you are not sure what happened and why it happened and just want to fix the phone so it boots normally into
the stock-rooted Samsung Jellybean v4.1.1 rom so you can start over again or if you decided that Liquidsmooth
is not for you then here is the step by step guide to get your phone working again.
After getting the phone working properly, I suggest that you flash the Wicked v10 custom rom. (it's excellent)
P.S. there is no OFFICIAL Samsung v4.2.2 roms for out phones yet, the liquidsmooth is the official CM10/AOKP Android rom.
Easy and sure way to to get your phone back up and running properly with this step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benefit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!