Related
*Copied mostly from my topic on AndroidForums*
/*from June 27th, thread start*/
So I found out that on the 25th or 26th there was an update for the Verizon GS3. Every time I try to update, it gives me this error (see below) after it reboots. I should also probably note that when it reboots, you briefly see "Booting into recovery" in the top left corner, though it doesn't actually boot into recovery. I was rooted, but I did a full unroot with SuperSU, and it still doesn't work. I dont want to flash a stock image because of all my app data that I do not want to lose.
Here is what the update screen looks like: i . imgur. com/oC04moq.png
And after the "update": i . imgur. com/oC04moq.png
Scroll down a little bit on that same box: i . imgur. com/iSqwQl0.jpg
Please someone help me! This is driving me crazy!
/End post 1\
Click to expand...
Click to collapse
/revive post October 6th\
So its been about 3 months now. Problem still persists. Again, I can not flash anything with ODIN(307), or update the phone. I have tried with Kies and in the phone. I can boot into download mode and recovery mode fine. Any help would again be greatly appreciated. I don't have access to my pc atm but any suggestions are still appreciated.
*The phone runs flawlessly, I just want to be able to root again *
/end post
Click to expand...
Click to collapse
/suggestion from user
"I would wind this back to the start.
It may not be just a phone issue. Uninstal kies and any android drivers and reboot.
Try this first:
★[8/27] [Casual] [Root, Unlock, Recovery] Vzw S3 Toolkit or 1-Click!! [ALL OTA's]★ - xda-developers
For the Verizion only. Anyone else thinking of using this start a new thread!!"
Click to expand...
Click to collapse
and my respose after trying: gyazo . com/3827e1487bf8cb3aeb0871b946fde785.png
Been on this for about 10mins, videos I have seen have done nearly instantly. I don't want to disconnect anything...
EDIT: I tried again twice. Same issue. I'm going to uninstall all drivers etc and try again.
Nup, still not working. Any more suggestions?
So far I have tried:
Odin(for root)
Kies(for updating)
Casual
Uninstalling kies/drivers and reinstalling and retrying all
All recognize the device, but nothing happens.
Click to expand...
Click to collapse
Now I'm here. I've never seen or heard anything like this before. Please post any suggestions you might have. I am down to try almost anything.
Sorry if I'm breaking any rules or anything. I just want this resolved.
And sorry for long post.
I'm assuming you've done all this with the same USB cable? Try a different cable (preferably the included one), different usb port, and also a different computer.
Sent from my SCH-I535 using Tapatalk 4
I can't even tell what is going on, this post is very confusing. Is Odin giving a fail message?
1. Odin should work, if it doesn't in a normal circumstance, then this method will work http://forum.xda-developers.com/showthread.php?t=1840030. This is will wipe all your data, but you'll be good to go from there.
2. Why did you unroot through super su? What rom are you running right now?
3. You can try using this image:
http://forum.xda-developers.com/showthread.php?t=1974114, then after you do this method you can run casual and root from there, while preserving your data.
Sent from my SCH-I535 using Tapatalk 2
Thanks to both of you!!!!!! I used a different port on my PC, and used the nowipe image BadUsername posted, and now I'm rooted, custom recovery, unlocked bootloader, and no data loss!! Again, thank you so much.
:highfive: yea teamwork! And last thing I'll suggest is to backup your IMEI if you haven't done so before.
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Edit:
HEY, YOU. YEAH YOU. READ THIS BEFORE YOU POST:
We figured out the solution quite a while back, but I know no one wants to read the entire thread, so here's a summary c/p'd from the end:
But to summarize, we've been able to get root by flashing CF auto root, letting it fail, then immediately flashing TWRP. To fix any issues encountered with xposed framework (stock sms not working, lagginess, installations taking forever, etc.), freeze with titanium/delete data for shealth, health services, and private mode, install securestorage module in xposed or use the equivalent option in Wanam, reboot, and unfreeze.
Click to expand...
Click to collapse
Now if you've tried this and you're still having issues, then post ahead. If you haven't tried this, or need help with specifics, read the thread. There's a post by me halfway through or so with 4 XDA links in it. If you want more info on the problem with xposed, check out those links.
jooniloh said:
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Click to expand...
Click to collapse
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Does TWRP fully support the note edge yet? Some of those steps (disabling screen timeout) make it seem otherwise. I'm usually hesitant to go for workarounds rather than actual fixes... :/ tell me if you do try it out though.
Next1776 said:
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Click to expand...
Click to collapse
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Next1776 said:
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Click to expand...
Click to collapse
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
z31k said:
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
Click to expand...
Click to collapse
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
jooniloh said:
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
Click to expand...
Click to collapse
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
z31k said:
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
Click to expand...
Click to collapse
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
jooniloh said:
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
Click to expand...
Click to collapse
Lmfao!!
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
jooniloh said:
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
Click to expand...
Click to collapse
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
beejmeister said:
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
Click to expand...
Click to collapse
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
EDIT: See my post here : http://forum.xda-developers.com/note-edge/general/info-galaxy-note-edge-sm-n915-t2945942 for more details on what worked for me
jooniloh said:
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
Click to expand...
Click to collapse
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
beejmeister said:
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Click to expand...
Click to collapse
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
jooniloh said:
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
Click to expand...
Click to collapse
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Next1776 said:
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Click to expand...
Click to collapse
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
BUt just to confirm, jooniloh.... you do have confirmable root? Guess my clue should be that you are using xposed.... but just wanted to confirm before I went down the rabbit hole....
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
Awesome. Glad you are able to join the party!
I'm not having any issues right now. I have installed Xposed and Wanam without any issues so far. I did disable Knox and Secure storage with Wanam (under security hacks) as another poster suggested. Maybe also try wiping Cache and dalvik in recovery ? Hopefully we will have a stable custom recovery available soon. I say stable, but I guess this one is "stable" - its just not real pretty...
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.
Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.
Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?
Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.
Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]
ON: Galaxy S3 4.4.2 Verizon(d2vzw) -->OK, I know you all may think I didn't read the other debrick threads, your wrong. I made this new thread because i HAVE tried endlessy every method of debrick on this forum and the internet, and no success. I was messing around with safestrap and decided to try and flash a rom called flashingdroid: for some reason. So i did as usual, boot into recovery(safestrap 3.75) and wipe current os and flash the new one. So i wiped my stock rom(after making a backup) and installed/flashed the new one(flashingdroid) and after seemingly a successful flash, i pressed reboot. Then it went downhill. One second after i pressed reboot, the screen flashed quickly, then shutoff, for good. I couldn't boot it or get into recovery or odin or ANYTHING. I tried the microsd method of debricking with minimal success. It will only give me one vibration, then black scree with that method. Nothing else has worked. I know this was a noob mistake somehow, but does anyone know any special tricks or something? Will a good jig maybe work? I have doubt verizon or samsung will accept it back(it was well rooted!). Please anything/anybody help! I really don't want to buy a new phone or jtag it. Thanks!:crying:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Ok...Thanks
landshark68 said:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Click to expand...
Click to collapse
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Root Wizard said:
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Click to expand...
Click to collapse
I'd be very careful with eBay, they tend to be junk. I've been an eBay member over 10 years and ran into a lot of it
Sent from my Nexus 5
Try MicroSD 16GB (2GB not work)
Confused About What's Possible for Modding a Stock Verizon S3
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
straykat said:
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
Click to expand...
Click to collapse
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
ShapesBlue said:
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
straykat said:
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
Click to expand...
Click to collapse
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
XDA Forum - the best place for learning...
ShapesBlue said:
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
straykat said:
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
Click to expand...
Click to collapse
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Can't Believe What I - did! - - - Need Help Rebooting Phone
ShapesBlue said:
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
straykat said:
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
Click to expand...
Click to collapse
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
ShapesBlue said:
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Try kies
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
ShapesBlue said:
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Click to expand...
Click to collapse
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
straykat said:
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
Click to expand...
Click to collapse
I'm 100% sure the last update on the VZW S3 was 4.4.2 NE1. As long as you can root the phone you should be able to run xposed without an issue
And no you cannot downgrade to anything other than what your currently on
Sent from my Nexus 5
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Root Wizard said:
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
Click to expand...
Click to collapse
Kies won't always work as it should
Sent from my Nexus 5
Still Not Up & Running...
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
I can't open it. It's in the newest word format docx. I personally haven't had to do this myself and it's been awhile since I've used Odin. Damn MS having to have all files in there own format
Edit: trying to download docs by Google and seeing if it opens
Sent from my Nexus 5
---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
Can you get into recovery?
I was able to open it once I downloaded docs by google. It's been so long since I used it though. I can't recall off hand how to use it to be honest
Sent from my Nexus 5
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Hi,
Can you boot into bootloader?
Press power button until phone reboots while keeping volume down pressed.
From there you can install a factory image.
What version are you actually on?
Good luck,
Sébastien.
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
Flash the stock kernel (partitions) via Fastboot.
most users having issues like this end up getting it up and running using Google's official Android Flash Tool . It takes a lot of guesswork and/or misfires that a lot of users end up hitting the wall at...
I suggest making sure to check "don't wipe" or "keep data" (sorry, I've only used it twice, so going off of memory is foggy) so it doesn't return the device to stock...
niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
did you disable Verity and verification before flashing the kernel?
It's frustrating when someone posts a problem then never follows up
HipKat said:
It's frustrating when someone posts a problem then never follows up
Click to expand...
Click to collapse
It's why I've relegated myself to editing the title "SOLVED" for members on their threads, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
simplepinoi177 said:
It's why I've relegated myself to editing the title "SOLVED" for members, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
Click to expand...
Click to collapse
Hey,
Most likely solved it by himself, since he didn't show up since 5 minutes after his post
Anyways, hopefully, people's experiencing the same issue will find this thread with possible solutions (before opening a new thread).
Cheers,
Sébastien.