Related
Alright, I'm going out on a limb here, I have no other options, I've tried everything..
I'm locked out, on my Evo.. "To unlock, sign in with your Google account" however, I don't have the credentials for this phone.. The data on this phone I need.. I'm trying to execute the commands
"> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot"
through the phone's stock recovery console (You know, the one that doesn't exist?) This phone is not rooted, it is completely stock, I can't access the desktop of the phone to enable USB debugging as I am locked out..
Nor can I use Unrevok3d to root and flash a recovery, so as you can see, as of now I'm at a stalemate..
My question: Is there something out there? Like a script of some sort, that I can put on the root of the SD card and boot the phone back on, and have this script/app execute itself FOR me to ENABLE USB debugging? So that I can run these commands and disable the lockscreen? I'm going through all this trouble just to backup the data so I can wipe the phone, but I'm unwilling to wipe the phone if I don't backup this data. The phone will be a paperweight otherwise, and what a waste would that be..
LOL sounds sketchy....
anyway try the Q&A forum
http://forum.xda-developers.com/forumdisplay.php?f=652
put a pc136 zip on the card from shipped roms and reflash the phone?
if you can't figure it out i'll give you $50 for the phone
Mudkip said:
put a pc136 zip on the card from shipped roms and reflash the phone?
Click to expand...
Click to collapse
that would wipe the data
Yes, I'm trying to keep the data intact since I need it.. But I am locked out?
Nobody can compile some sort of script? Something that'll run itself? or a script that will disable this perma-lock status? There has got to be something like that, that can be done?
IF this exploit did exist wouldn't that defeat the point of pattern unlock? i mean, anyone could run this script and get around pattern unlock.
so, what i'm getting at is if someone knows this i hope to god they dont post it because every asshole will use it to spy on their girlfriend ect ect.
adamantypants said:
LOL sounds sketchy....
anyway try the Q&A forum
http://forum.xda-developers.com/forumdisplay.php?f=652
Click to expand...
Click to collapse
Really though. How did you acquire said phone? If its legit take it to Sprint?
SubatomicGenome said:
Alright, I'm going out on a limb here, I have no other options, I've tried everything..
I'm locked out, on my Evo.. "To unlock, sign in with your Google account" however, I don't have the credentials for this phone.. The data on this phone I need.. I'm trying to execute the commands
"> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
> adb reboot"
through the phone's stock recovery console (You know, the one that doesn't exist?) This phone is not rooted, it is completely stock, I can't access the desktop of the phone to enable USB debugging as I am locked out..
Nor can I use Unrevok3d to root and flash a recovery, so as you can see, as of now I'm at a stalemate..
My question: Is there something out there? Like a script of some sort, that I can put on the root of the SD card and boot the phone back on, and have this script/app execute itself FOR me to ENABLE USB debugging? So that I can run these commands and disable the lockscreen? I'm going through all this trouble just to backup the data so I can wipe the phone, but I'm unwilling to wipe the phone if I don't backup this data. The phone will be a paperweight otherwise, and what a waste would that be..
Click to expand...
Click to collapse
"404 error" sense was not found in this post.
These threads are always funny. I am guessing stolen, lost and found or a significant other trying to get info off the others phone.
Tipharet said:
These threads are always funny. I am guessing stolen, lost and found or a significant other trying to get info off the others phone.
Click to expand...
Click to collapse
my friend download androidcommander and see if it recognizes your phone save what you need and then put a PC36IMG on the sd card and flash to stock then restore with android commander..... Oh yea I think they are going to get you for the wrong forum...lol
thedudejdog said:
IF this exploit did exist wouldn't that defeat the point of pattern unlock? i mean, anyone could run this script and get around pattern unlock.
so, what i'm getting at is if someone knows this i hope to god they dont post it because every asshole will use it to spy on their girlfriend ect ect.
Click to expand...
Click to collapse
How many people (Average users) are going to know about something like this if it DID exist? Your average user doesn't know about ADB nor do they know how to use ANY of the commands or how to debug a phone using the SDK..
So... What I am getting at.. Is if there is a no-way-out scenario (Like the one I'm having) Is there a way AROUND it? Like the previous question I just posted? I'm not looking to spy on girls, I'm not paranoid nor do I have a wife/girlfriend and nor do I care. I just want back into my phone. I know there is a way to do it, I've enabled ADB with my G1 from being locked out before, but this isn't my G1..
SubatomicGenome said:
How many people (Average users) are going to know about something like this if it DID exist? Your average user doesn't know about ADB nor do they know how to use ANY of the commands or how to debug a phone using the SDK..
So... What I am getting at.. Is if there is a no-way-out scenario (Like the one I'm having) Is there a way AROUND it? Like the previous question I just posted? I'm not looking to spy on girls, I'm not paranoid nor do I have a wife/girlfriend and nor do I care. I just want back into my phone. I know there is a way to do it, I've enabled ADB with my G1 from being locked out before, but this isn't my G1..
Click to expand...
Click to collapse
how do you not know your gmail address and password?
the thing is, if i or anyone tells you how to get out of your totally-believable scenario then that would rape the children of every person that relies in the pattern-unlock for security.
pattern-unlock or not, you should know your own email password
playya said:
my friend download androidcommander and see if it recognizes your phone save what you need and then put a PC36IMG on the sd card and flash to stock then restore with android commander..... Oh yea I think they are going to get you for the wrong forum...lol
Click to expand...
Click to collapse
That's actually a fantastic suggestion, however that only works with USB Debugging enabled.. And that's the problem I'm having, I do not have USB debugging enabled and I am LOCKED outta the phone, hence, I cannot turn it on or off as I see fit.
This is why I want some script that will automatically either, disable the perma-lock, or enable USB Debugging mode so I can run the shell commands to disable the pattern lock myself...
thedudejdog said:
how do you not know your gmail address and password?
the thing is, if i or anyone tells you how to get out of your totally-believable scenario then that would rape the children of every person that relies in the pattern-unlock for security.
pattern-unlock or not, you should know your own email password
Click to expand...
Click to collapse
Amen! 10chars suck.
thedudejdog said:
how do you not know your gmail address and password?
the thing is, if i or anyone tells you how to get out of your totally-believable scenario then that would rape the children of every person that relies in the pattern-unlock for security.
pattern-unlock or not, you should know your own email password
Click to expand...
Click to collapse
Indeed, which I do...
....It's not working, I've tried all my passwords, caps, no caps, letters and special characters (I have a ton of passwords I use) But for this specific account, none of the passwords I have tried are working and google account recovery doesn't seem to be too reliable..
This isn't my first rodeo, I've had problems like this before where I just log in and change my pattern, but what if that possibility is out the window and the only thing left is an Android Guru that can ninja hack my Debug settings?? I'll grab my data and wipe the phone and re-register it to a password that won't tell me I'm lame.
If anyone is paranoid about this whole thing, or someone hacking their pattern lock just PM me so I can fix my situation, and not have to worry about this again.. I don't want to break into any phone but my own. Someone has to know how stressful this is..
SubatomicGenome said:
Indeed, which I do...
....It's not working, I've tried all my passwords, caps, no caps, letters and special characters (I have a ton of passwords I use) But for this specific account, none of the passwords I have tried are working and google account recovery doesn't seem to be too reliable..
This isn't my first rodeo, I've had problems like this before where I just log in and change my pattern, but what if that possibility is out the window and the only thing left is an Android Guru that can ninja hack my Debug settings?? I'll grab my data and wipe the phone and re-register it to a password that won't tell me I'm lame.
If anyone is paranoid about this whole thing, just PM me so I can fix my situation, and not have to worry about this again.. Someone has to know how stressful this is..
Click to expand...
Click to collapse
the reason i am following this thread, is because i myself was just in this situation a few weeks ago. there is no way around it, you will have to RUU to use this phone. period. that is if it is a valid ESN
thedudejdog said:
the reason i am following this thread, is because i myself was just in this situation a few weeks ago. there is no way around it, you will have to RUU to use this phone. period. that is if it is a valid ESN
Click to expand...
Click to collapse
RUU the phone?? Won't that wipe it?
SubatomicGenome said:
RUU the phone??
Click to expand...
Click to collapse
what i'm saying is, a few weeks ago i tried the pattern-lock and ended up locked out. no one will help thinking its a stolen phone or whatever and i ended up ruu'ing the phone.
edit: yess it wipes it. no way around it
thedudejdog said:
what i'm saying is, a few weeks ago i tried the pattern-lock and ended up locked out. no one will help thinking its a stolen phone or whatever and i ended up ruu'ing the phone.
edit: yess it wipes it. no way around it
Click to expand...
Click to collapse
I can't wipe the phone. I'll keep the phone on my desk and wait if I have to. There is data on this phone I CAN NOT LOSE, and the gmail account I used I never accessed from my browser, ever. I just made one when I got my 2nd number.
You're sayin that people are out there that CAN help? And WON'T cause they THINK it's stolen? IT'S MY PHONE! All I did was make a stupid mistake. That was letting my sister touch it, nosy little ****.. hahah
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.
[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.
Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.
crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.
Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?
Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?
Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.
not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.
Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.
i just did this and it saved my phone!!!! thank you so much
DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome
crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it
This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse
older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot
Cool, cant wait to walk a friend thru this.
Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk
JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.
Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.
I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.
JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.
I thought you posted that Samsung Pay worked for you in the OP.
CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk
Hey all
I very recently made the mistake of upgrading my phone, not realising that it was a complete overhaul from 8.0 to 9.0. I absolutely hate it. There are a dozen downsides and, as far as I have noticed, not a single benefit to this upgrade. I have gotten frustrated many times already due to the stupid little changes and have spent a good portion of my day attempting to figure out how to reverse it.
Now I'm not that tech-savvy, and the only method to get back the phone I knew and loved is to 'flash' it (?) using a software which I have acquired. I must also apparently make sure to back up my data because downgrading in this manner apparently does not ensure any of your personal data is protected.
So my question here is twofold:
1. Does anybody have the UK version for the latest 47.1.A.16.20 firmware as an appropriate file (FTF?) for me to get back the phone I paid for as opposed to this crap?
2. What would be an appropriate method of backing up my phone such that I can recover it all post-flash with all of my settings and user data intact?
Thank you all so very much for your help!
PCBearington said:
Thank you all so very much for your help!
Click to expand...
Click to collapse
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Here is a copy of 47.1.A.16.20, It's not the UK version, but that makes no difference
Download Newflasher and put it in the same folder as the firmware you downloaded
Delete persist*.sin to avoid losing android attest key.
Turn phone off completely. Then start newflasher.exe and follow instrctions. Plug the phone into the pc whilst holding volume up(+), then no & no in the newfalsher dialog box, then you should be away.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, you can't keep your data when you downgrade, so this would be the easiest way of keeping the important stuff. Back up onto your sdcard, then restore once the flash has completed.
Didgesteve said:
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Here is a copy of 47.1.A.16.20, It's not the UK version, but that makes no difference
Download Newflasher and put it in the same folder as the firmware you downloaded
Delete persist*.sin to avoid losing android attest key.
Turn phone off completely. Then start newflasher.exe and follow instrctions. Plug the phone into the pc whilst holding volume up(+), then no & no in the newfalsher dialog box, then you should be away.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, you can't keep your data when you downgrade, so this would be the easiest way of keeping the important stuff. Back up onto your sdcard, then restore once the flash has completed.
Click to expand...
Click to collapse
Hi Steve, I accidentally installed the update today and I wish to revert too. Apparently the Xperia XZ1c has DRM keys for things like the camera and video processing which if custom firmware is flashed will be lost. Is this an issue when flashing an older version of a stock xperia rom like you are suggesting? Thanks
Joecalone said:
Hi Steve, I accidentally installed the update today and I wish to revert too. Apparently the Xperia XZ1c has DRM keys for things like the camera and video processing which if custom firmware is flashed will be lost. Is this an issue when flashing an older version of a stock xperia rom like you are suggesting? Thanks
Click to expand...
Click to collapse
No unlocking the bootloader is an entirely seperate procces and can't be done accidently flashing firmwares. You have to get an unlock code from Sony and do some ADB magic.
There is another tools called Flashtool, that does the same thing as Newflasher, but has the power to delete your DRM, if driven improperly, so I don't recomend that.
Newflasher is safe to use and won't damage your TA partition (DRM keys), just note the persistxx.sin removal, that stops damage to one of the partitions.
You can't keep you data when retro-grading, you must wipe the phone to factory, there isn't any other way.
Didgesteve said:
No unlocking the bootloader is an entirely seperate procces and can't be done accidently flashing firmwares. You have to get an unlock code from Sony and do some ADB magic.
There is another tools called Flashtool, that does the same thing as Newflasher, but has the power to delete your DRM, if driven improperly, so I don't recomend that.
Newflasher is safe to use and won't damage your TA partition (DRM keys), just note the persistxx.sin removal, that stops damage to one of the partitions.
You can't keep you data when retro-grading, you must wipe the phone to factory, there isn't any other way.
Click to expand...
Click to collapse
Thanks for the quick response! I'm backing up my phone right now. You mentioned the persistxx.sin removal, sorry if the answer is obvious but I'm a bit new to all this, does Newflasher do this automatically or do I need to do it myself? If so, how does one go about removing it?
Joecalone said:
Thanks for the quick response! I'm backing up my phone right now. You mentioned the persistxx.sin removal, sorry if the answer is obvious but I'm a bit new to all this, does Newflasher do this automatically or do I need to do it myself? If so, how does one go about removing it?
Click to expand...
Click to collapse
It'll be in the firmware folder that download
Didgesteve said:
It'll be in the firmware folder that download
Click to expand...
Click to collapse
Ah right I think I understand you, I opened the ftf file with 7zip and deleted the file named "persist.sin". I'll be flashing it tomorrow so I'll let you know how it went. Really appreciate the tips
PCBearington said:
I absolutely hate it. There are a dozen downsides and, as far as I have noticed, not a single benefit to this upgrade.
Click to expand...
Click to collapse
Hey PCB! Could you tell me more about all those downsides? I'd like to know more before/if I (ever) decide to upgrade.
I know that clock on the left-hand side would irritate me. Also, volume buttons defaulting to media is something I don't like.
But you mentioned "a dozen" so I'm curious.
Tnx!
komer said:
Hey PCB! Could you tell me more about all those downsides? I'd like to know more before/if I (ever) decide to upgrade.
I know that clock on the left-hand side would irritate me. Also, volume buttons defaulting to media is something I don't like.
But you mentioned "a dozen" so I'm curious.
Tnx!
Click to expand...
Click to collapse
Hey man! I wrote up a few reasons on a Reddit post earlier so I'm just going to paste that if that's okay!
Volume button now always does media volume instead of a sliding scale for normal stuff ie ringtone
Lots of irritatingly unnecessary changes such as the time now being in the top right so my muscle memory has me checking the time and I'm momentarily confused.
They've changed the overall aesthetic to be more Apple-y resulting in a really weird look, making the text in most places look larger than usual (especially the notifications).
The pull-down-from-the-top menu now shows two rows of enlarged buttons instead of three like before.
The WiFi and Bluetooth drop down menus have gone, so now if you want to quickly switch between two networks instead of being able to do it all in one screen you have to go to the settings page for WiFi and Bluetooth.
(this one is very minor) the colour of the keyboard has gone from black and orange (which I liked) to black and blue.
I know it sounds like I'm being awfully nitpicky but honestly the few bits of functionality that were removed were things I relied on a lot; I just don't appreciate such ****ty unnecessary changes for no apparent reason.
As far as I can see, there are absolutely no improvements or upgrades or anything at all that I can point to and go "yeah that's worth it."
I've been using this update for only a little while and I'm sure that there are other things which'll pop out at me over time as well!
Hope this helps mate
PCBearington said:
The pull-down-from-the-top menu now shows two rows of enlarged buttons instead of three like before.
The WiFi and Bluetooth drop down menus have gone, so now if you want to quickly switch between two networks instead of being able to do it all in one screen you have to go to the settings page for WiFi and Bluetooth.
Click to expand...
Click to collapse
These two are absolutely unacceptable. An update should never remove features or make previous things harder to do, this update is an absolute joke. Now once again I have to go through the arduous process of factory resetting my phone to downgrade simply because Sony couldn't put out a competent update to save their lives.
Thanks mate! I agree with you 100%. The phone is "perfect" just the way it is and some changes, that Google and Sony made, should totally have been optional. I would upgrade it just for curiosity.... but I don't wanna regret it later.
Cheers!
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
I've just updated and am I wrong or the recent app switcher and the navigation bar are still the same and not the Pie version?
Dark Emotion said:
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
Click to expand...
Click to collapse
I can only have two rows shown at a time on mine! I looked in the settings as well, any other buttons now have to be swiped across to access because of how ludicrously large they made them.
bexem said:
I've just updated and am I wrong or the recent app switcher and the navigation bar are still the same and not the Pie version?
Click to expand...
Click to collapse
You're not wrong. It's the same. Sony removed Google's gesture navigation.
PCBearington said:
I can only have two rows shown at a time on mine! I looked in the settings as well, any other buttons now have to be swiped across to access because of how ludicrously large they made them.
Click to expand...
Click to collapse
Sorry man, I forgot that I changed dpi in settings. Take a look at the screenshot I attached.
Didgesteve said:
It'll be in the firmware folder that download
Click to expand...
Click to collapse
Hi, me again :laugh:
I tried flashing the phone today with newflasher but to no avail. I downloaded those xperia drivers, added them using device manager, and the hardware wizard gave the following message
"The following hardware was installed:
Sony sa0117 ADB Interface Driver
The software for this device is now installed but may not work correctly.
This device cannot start (Code 10)"
I tried flashing anyway after the phone had been put into debug mode but newflasher simply prompts whether or not I need GordonGate flash driver. If I type "n" to skip, it throws the error
"No usb device with vid:0x0fce pid:0xb00b !"
Joecalone said:
Hi, me again :laugh:
I tried flashing the phone today with newflasher but to no avail. I downloaded those xperia drivers, added them using device manager, and the hardware wizard gave the following message
"The following hardware was installed:
Sony sa0117 ADB Interface Driver
The software for this device is now installed but may not work correctly.
This device cannot start (Code 10)"
I tried flashing anyway after the phone had been put into debug mode but newflasher simply prompts whether or not I need GordonGate flash driver. If I type "n" to skip, it throws the error
"No usb device with vid:0x0fce pid:0xb00b !"
Click to expand...
Click to collapse
If you're using Windows 10 it would have completly failed to install your driver and didn't bother telling you. Restart Windows 10 in safe mode and look for 'driver signing disabled', then try again.
Edit: or click 'Yes' to first question in Newflasher and it will prodice a zip file of the drivers you need, then apply as above.
Didgesteve said:
If you're using Windows 10 it would have completly failed to install your driver and didn't bother telling you. Restart Windows 10 in safe mode and look for 'driver signing disabled', then try again.
Edit: or click 'Yes' to first question in Newflasher and it will prodice a zip file of the drivers you need, then apply as above.
Click to expand...
Click to collapse
No luck with either of these unfortunately. I'll try doing it on my Windows 7 PC at home, hopefully I'll get better results with that :fingers-crossed:
Dark Emotion said:
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
Click to expand...
Click to collapse
Dark Emotion said:
Sorry man, I forgot that I changed dpi in settings. Take a look at the screenshot I attached.
Click to expand...
Click to collapse
Would you mind telling me how you did that? I trawled through the settings briefly but couldn't see anything applicable!
Would really appreciate it!