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
I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.
Is this a GSM GNex (i9250)?
i9250
To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.
BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.
aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.
j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.
DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html
If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.
DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
cyaiphone said:
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
Click to expand...
Click to collapse
Nexus line.
have you tried reflashing cwm recovery via fastboot?
flash CWM via fastboot.
and why do you need a backup of stock? You can always re-flash the stock images to go back to completely stock. Restoring a rooted nandroid backup won't put you back to stock anyways...
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
cyaiphone said:
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
Click to expand...
Click to collapse
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
martonikaj said:
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
Click to expand...
Click to collapse
Crap is there a how to any how to do this? I've never used adb or command prompts.
cyaiphone said:
Crap is there a how to anywherebonnhow to do this? I've never used adb or command prompts.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1529058
And look for the "Setting up ADB for our device:" then "Obtaining Root Access and Custom Recovery:".
Can you boot into the OS? If you can, download Rom Manager from the Play Store and use that to install CWM Recovery.
Did you delete recovery-from-boot.p from /system? I had to do this to "permanently" install the recovery. My first Samsung phone, my first Nexus device, so not sure if this has been a regular thing ... never had to "permanently" install a recovery up until then. That fixed my issue as my recovery was only sticking once per boot ... was blowing my mind for a couple hours.
Not sure if root via toolkit solves this, but I did a manny root and had to do this. Hope it helps.
edit-
- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
Click to expand...
Click to collapse
Could also, apparently, rename it. I just reinstalled recovery, deleted, and haven't had a single problem since.
What bleedblue said; now go into fastboot, and reflash cwm.
Sent from my i9250
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Have you tried twrp?
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see
+1 for twrp
athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.
aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help
xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.
athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks
xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.