Related
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
ryantaylor16 said:
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Not a noob, but here is where i am lost
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
UltimateEnd said:
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Click to expand...
Click to collapse
ryantaylor16 said:
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
Click to expand...
Click to collapse
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Sorry, still need assist
UltimateEnd said:
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Click to expand...
Click to collapse
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
ryantaylor16 said:
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
Click to expand...
Click to collapse
after you are rooted ,
you should have nothing to do with Odin.
and also, if you were stuck on your phone trying to boot up, chances are you keep downloading a bad ROM..
happen to me before..a ROM that was suposed to be 192MB,
would finish on 158MB
someone else may be able to help you get back to stock ROM..i havent had the chance to ever wanna go back to stock so i wouldnt know for sure.
sorry and good luck .
Still Worried. Still Stuck
ryantaylor16 said:
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin to undo root. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
ryantaylor16 said:
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
Click to expand...
Click to collapse
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Use this?
JB calhoun said:
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Click to expand...
Click to collapse
Would you say this is a good tutorial to follow?
http://rootgalaxynote.com/galaxy-no...-on-att-galaxy-note-sgh-i717-belltelusrogers/
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
bump
CWM Problems
Hi,
Have you looked at these posts? Sounds like you may be using the
wrong key combo to start CWM?
http://forum.xda-developers.com/showthread.php?t=1586223
http://forum.xda-developers.com/showthread.php?t=1483113
Are you confident that your uSD card hasn't been corrupted?
Peter
ryantaylor16 said:
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
Click to expand...
Click to collapse
ryantaylor16 said:
bump
Click to expand...
Click to collapse
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Certainly I am not this dumb..... am I
froidroid said:
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Click to expand...
Click to collapse
Still having issues. Here is the deal.
I have the phone in Download mode
https://www.dropbox.com/s/dnk6ekjqp9vddev/2012-06-19 19.40.01.jpg
I load the CWM Recovery in the PDA box. Start the flash, get a pass. All looks good to me.
https://www.dropbox.com/s/5q4hayf35mm26wr/odin-success.PNG
I immediately attempt to access CWM Recovery by holding the power, vol+ and vol- and still get the default recovery
https://www.dropbox.com/s/d176blydonlvrlu/2012-06-19 20.13.42.jpg
I am so confused as to what I am doing wrong.
Unfortunately those pics aren't loading for me. Try again with the pic of recovery and the file you're flashing. Thanks. If you still have stock recovery then maybe that's what you're flashing in error.
Try volume up + down and power button. When phone vibrates, release power button but keep holding volume buttons until you are in cwm.
I would use Odin to flash cwm touch recovery from pda, then load a rom via cwm. Using that method you don't even need to root because it's all done at bootloader level and root is built in to the custom rom you flash
SGH-i717 mesosphere-remix
Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Solkrieg said:
Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Click to expand...
Click to collapse
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
roughneckboren said:
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Solkrieg said:
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Click to expand...
Click to collapse
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
roughneckboren said:
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Solkrieg said:
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Click to expand...
Click to collapse
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
Click to expand...
Click to collapse
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
Click to expand...
Click to collapse
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
EDIT: It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
Click to expand...
Click to collapse
Please do.
ROOTBOXED!
roughneckboren said:
Please do.
ROOTBOXED!
Click to expand...
Click to collapse
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Click to expand...
Click to collapse
No problem man. Not everyone here is a butthole. Its not a pain because I was there once too. Just make sure you run a backup in twrp. You can name it too! Just practice and read around. Watch YouTube videos (I learn by visual)
And I keep my backups on PC in case a memory card goes bad. If you wipe system in recovery make sure you flash a ROM because system is obviously your OS and twrp prevents it from booting and bricking your device. Good choice on the recovery. :thumbup:
If it will at least boot to something there's always hope. be sure to hit the thanks button. It always helps. Glad to have gotten you up and running. If you need more help just pm me.
ROOTBOXED!
Just tried to install TWRP (Touch) from the wrong forum on top of my existing recovery, I guess (not really sure what I did; was watching NFL simultaneously.. DANG!). And now my phone won't get past the boot screen anymore...
My International Galaxy SIII is (was) unlocked and rooted; running the U.K. (O2) version of Android 4.1.2.
Retracing my steps, it seems like I tried to install the US/Verizon recovery image of TWRP on my i9300 by mistake. When I downloaded the image from GooManager, it offered to install the image right upon completion. And thinking that I was in the correct XDA-Dev Forum section, I confirmed... Bad Mistake. (Yes... I know, I'm an idiot...).
FWIW, I've been 'messing' with my Smartphones + multiple Tablets for 6+ years now, but I never managed to brick anything thus far. Bad 1st time, as I am about to move back to Europe (from the US).
Phone does not show on Laptop (under drives/devices) anymore. I do know about ADB and some basic commands (..enough to install ROMs, boot into Recovery, Bootloader etc.), but what can I do if I don't even get passed the boot screen? What's the command I need, and how can that get me back on track? -- Tried to shut down, use "the usual" power button/volume button combinations; even pulled SD card storage and SIM (as I had read that suggestion in the i-9000 Forum)... No dice.
I would kinda stink, but if I have to wipe my phone to make it work again, so be it... I have ROM Manager backups stored on my external SD card.
-- Any help & suggestions are greatly appreciated!
Thanks
Armin
P.S.: Since I wanted to get rid of ClockworkMod, I did not take a Nandroid BU first...of course
not sure and I guess someone more qualified might be better able to help, but can you get into Download mode and re-flash correct recovery via Odin?
I'll try that first thing tomorrow morning... Thanks for your suggestion!
Sent from my Nexus 7 using xda app-developers app
YES! Was able to get into 'Download Mode'... What now? I'm not sure if simply flashing the correct recovery will do the trick...will it? Well, then again.. it can't get worse, can it?!
I'll give that a try via Odin. Stay tuned!
[SOLVED] Bricked my GT-I9300 w/ TWRP... - Help, please!
chrismast said:
not sure and I guess someone more qualified might be better able to help, but can you get into Download mode and re-flash correct recovery via Odin?
Click to expand...
Click to collapse
androidarmin said:
YES! Was able to get into 'Download Mode'... What now? I'm not sure if simply flashing the correct recovery will do the trick...will it? Well, then again.. it can't get worse, can it?!
I'll give that a try via Odin. Stay tuned!
Click to expand...
Click to collapse
AWESOME... That did the trick!!!
Here's a quick step-by-step for getting your phone back to life via Download mode (my modest contribution to the community):
1. Pull battery
2. Put battery back in and go into download mode right away (pressing POWER + Volume DOWN + HOME button)
3. Confirm that you want to continue (Volume UP)
4. Connect phone to your PC
5. Download .tar file of whatever you want/need to flash
6. Fire up Odin
7. Leave all Odin settings as they are.. don't check/uncheck anything (!!).
8. Click "PDA" button and select .tar file with app or ROM you want to flash
9. Press "Start"... and -after a quick, automatic reboot of your phone- you should be back in business... [yay!]
Thanks, guys!
Great that it worked!
Sent from my GT-I9300 using xda app-developers app
chrismast said:
Great that it worked!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
THANK YOU, Buddy!!! :good::good:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.
My work colleague is an idiot - Despite warnings from his S3 that phone memory was low he continued taking videos and pictures and he has no sd card in the phone. Now the phone boots up but the pattern unlock screen is unresponsive. I offered to try to help him as he said "The last 2 years photos of my life are on there" so clearly a factory reset will lose them all so that's not an option.
So I installed Kies, thinking I'll just grab them to my PC for him - but alas no. MTP USB driver installation fails every time and yes I've googled my socks off, tried all the regedit fixes, even tried installing Win 7 32 bit on a spare hard drive.
I've checked that the ribbon connector for the screen is attached, tried linux boot disks that don't see the phone and now I'm all out of ideas. Any help would be vastly appreciated :fingers-crossed:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
You may can flash a custom recovery or a temporary recovery(not sure because I don't know what is available for the model you're working with and what isn't), if you can get one of those recoveries then you may can use the factory reset in recovery(it wont wipe his photos) or adb to get the phone working.
Remember to create an XDA account so you can post and reply in the forums.
Droidriven said:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
Click to expand...
Click to collapse
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Azarameus said:
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Click to expand...
Click to collapse
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Droidriven said:
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Click to expand...
Click to collapse
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Azarameus said:
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Click to expand...
Click to collapse
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Azarameus said:
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Click to expand...
Click to collapse
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Azarameus said:
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Click to expand...
Click to collapse
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I showed him this thread at work earlier and although he growled somewhat at being called an idiot in my OP, he had to agree he was lol. It turns out he bought his partner the same phone around the same time so I checked and it has Automatic upgrades ticked and is on build 4.3 so we can hopefully assume the problematic one is on the same version. When I mentioned the possibility of bricking to him he became unsure as to whether I should proceed with flashing. If he was to send the phone to Samsung themselves would they be able to retrieve his data safely, albeit with some cost and waiting?
Thanks again for your input
Hawaiihemd said:
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Click to expand...
Click to collapse
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Azarameus said:
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Click to expand...
Click to collapse
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Hawaiihemd said:
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Click to expand...
Click to collapse
Ok thanks again. I am going to attempt this tonight, will update on any progress
Azarameus said:
Ok thanks again. I am going to attempt this tonight, will update on any progress
Click to expand...
Click to collapse
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Azarameus said:
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Click to expand...
Click to collapse
Nice! And were you able to get the lockscreen working again?
Hawaiihemd said:
Nice! And were you able to get the lockscreen working again?
Click to expand...
Click to collapse
Yes indeed, all is working now as it should. The village idiot actually danced off to his car when I returned his phone - he has strict orders from me to move all his stuff to the SD card and make regular backups to his PC!
Thanks again - would never have done it without you guys