Related
First of all, I am sorry for posting this here, but I am kind of in a bind, and hope someone can help me out..
EVO, rooted with new unrevoked, running stock everything, on a mac
I downloaded and installed LCD Density Changer today, and changed my number form 240 to 200, as everyone suggested.
When I rebooted, my boot screen started, but then the display went blank, and I keep hearing the Sprint music, but the phone's display wont come up..
I can get into recovery mode, so I am thinking of just doing a wipe data/factory reset, and starting all over, which wont be a problem, since I am all backed up.
someone suggested doing an ADB push, but I am on a mac, and cant find detailed instructions on how to do that..
Can someone give me a idea on which way to go?
I am fine with wiping data/factory reset, if it gets my phone started again..
Again, sorry if I posted this in the wrong place, but I know there are some great people here that will give me some direction
thanks so much!
i don't know what this has to do with development... but restore the backup that you made before you did the patch. didn't backup? wipe.
yup... no back up... shame on you..
your only choice is to wipe.
i dont know why people use this app, just edit the build.prop file yourself with rootexplorer or what ever app you have that can browse and edit the phones files.
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
good news; got it to work with a zip file that a great member of this board gave to to flash; sorry if this post was placed in the wrong spot, and mods you are welcome to delete /lock it now..
BTW, doing a nandroid backup IMMEDIATELY!
you guys are the best, and SHAME on me for not doing that the minute I was rooted...
illogic6 said:
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
Click to expand...
Click to collapse
can you do ADB on a mac computer?
thanks
wase4711 said:
can you do ADB on a mac computer?
thanks
Click to expand...
Click to collapse
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
illogic6 said:
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
thank you, it is an Intel!
I appreciate the link
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.
Hi All,
My Gnex with specs
Product Name : Tuna
Variant - : Maguro
HW Version : 9
Bootloader : PRIMELA03
Baseband : I9250XXlF1
Carrier : None
Signing : Production
Lock State : Locked
is stuck at boot screen, i noted that it used to restart when i connect it to my Jabra EasyGo. I have tried to wipe clean the cache and tried turning on/off many times, but of no use. It had Jellybean 4.1.1 OTA update. I am newbie to android flashing/rooting, the problem is i need to restore my data, i have not done any backup other than just apps.
Kindly help me recover my data. Awaiting response.
Well at this point I usually recommend flashing stock using efrant's guide in the sticky, but since your bootloader is locked, I can't see how would you do it without potentially losing all of your data. Although for some reason it doesn't wipe my data when I unlocked mine, I wouldn't gamble it if your data is important.
Have you tried factory reset from the stock recovery? That shouldn't wipe your /sdcard partition.
What happened that you are now stuck at boot screen? What did you do with the phone immediately before this issue?
You could adb pull /sdcard/..
Hi
reysonance said:
Well at this point I usually recommend flashing stock using efrant's guide in the sticky, but since your bootloader is locked, I can't see how would you do it without potentially losing all of your data. Although for some reason it doesn't wipe my data when I unlocked mine, I wouldn't gamble it if your data is important.
Have you tried factory reset from the stock recovery? That shouldn't wipe your /sdcard partition.
Click to expand...
Click to collapse
How to stock recover? I did using the volume keys +power hold, but the factory reset has Data/factory reset written over it... don't wana loose the data .... please guide me
your bootloader is locked and you cant boot into android.
as far as i know, there is NO way to get your data back.
Is it must to have it unlocked? any links or threads you could reccommend?
bodh said:
What happened that you are now stuck at boot screen? What did you do with the phone immediately before this issue?
You could adb pull /sdcard/..
Click to expand...
Click to collapse
I did nothing at all, i use jabra easyGo, n usually it restarted and came back normal, it happend only when ever i started the jabra and Gnex's bluetooth at same time, i can grasp it was some issue during bluetooth pairing, but it i started bluetooth at Gnex first, it went ok and paired and talked hours. can you help me recover my data?
I think zepius may be right. With a locked bootloader, you cannot boot custom recovery to enable adb, and without custom recovery and no boot, you cannot use adb pull. My mistake, i always assume everybody is unlocked. Looks like that factory reset is beckoning.
Are you rooted?
bodh said:
I think zepius may be right. With a locked bootloader, you cannot boot custom recovery to enable adb, and without custom recovery and no boot, you cannot use adb pull. My mistake, i always assume everybody is unlocked. Looks like that factory reset is beckoning.
Are you rooted?
Click to expand...
Click to collapse
nooo... never rooted.
the_nauman said:
nooo... never rooted.
Click to expand...
Click to collapse
Could this thread be useful for me?
http://forum.xda-developers.com/showthread.php?t=1894717
the_nauman said:
Could this thread be useful for me?
http://forum.xda-developers.com/showthread.php?t=1894717
Click to expand...
Click to collapse
your phone doesnt boot into android... so no.
you're SOL with your data. sorry.
Zepius said:
your phone doesnt boot into android... so no.
you're SOL with your data. sorry.
Click to expand...
Click to collapse
what about this method? possible?
the_nauman said:
what about this method? possible?
Click to expand...
Click to collapse
your phone has to boot into android for that to work. yours, does not. what do you think the answer is?
Zepius said:
your phone has to boot into android for that to work. yours, does not. what do you think the answer is?
Click to expand...
Click to collapse
Oh sorry, forgot to paste the link. i meant this one....
http://forum.xda-developers.com/showthread.php?t=1994705
the_nauman said:
Oh sorry, forgot to paste the link. i meant this one....
http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
it should, ive never done it however.
Zepius said:
it should, ive never done it however.
Click to expand...
Click to collapse
should i go ahead with factory reset than? need a word of trust
you're going to have to wipe anyways so...
Zepius said:
you're going to have to wipe anyways so...
Click to expand...
Click to collapse
WIPED... n its like a clean slate. i had soo many pictures.... i used to flash windows mobile phones so much, but i left doing that, n today it has come that i got lost data.... from now i will flash it so much that this cell's gonna remember...gonna start with the memory get back with this
http://forum.xda-developers.com/showthread.php?t=1994705 link....
its heart breaking, Android loosing value, i always defended it in front of iOS.
To be fair, if iOS doesn't boot, hard reset by pressing power+home button will also wipe your data clean.
Let me start by saying I've read through several other threads with a similar issue, but they all have a common connectivity problem that I'm NOT experiencing so I thought I'd ask this in a new thread. I was using AOKP build 5, and I decided to try out a more TW stock rom to see how devs have modified it. I chose Intergalactic v 2.8, wiped data/cache and installed like ya do. Almost immediately I got the pop up saying, "Unfortunately, Factory Test has stopped." I didn't think much of it, even though I had never seen it before. I restored my app data via Titanium Backup and starting fiddling with my settings. Made a couple calls, a few texts. Put my phone down to go about my morning. Later when I went to unlock my phone I realized I don't have a lockscreen. Thought that was funny so I went to boot into recovery but punching the power button just turned the phone off; So I investigated and I realize I'm in factory mode. and I can't seem to get out of it. I've tried running the terminal commands to turn it off, but that didn't work. It looks like my ESF folder is empty or doesn't exist.
So here's what I know after all of my research: My IMEI somehow seems to be intact since I can make calls and get on the network, but because my ESF is empty or gone can't turn off factory mode, which is causing all kinds of other buggy issues such as no lockscreen, no power menu, and the annoying Factory Test pop-up. If there is a thread out there that had a similar problem, I apologize that I couldn't find it. is there any way to recover this info, since the IMEI is still intact? Thanks.
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
did that, no dice
peneoark said:
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Tried to restore the stock JB with Odin and it didn't fix the problem. I'm attempting to flash the stock ICS, then attempt an OTA update to see if that does the trick. Will keep you posted.
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
drunkenscholar said:
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
DamageSource said:
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
Click to expand...
Click to collapse
How would I extract it from the EFS folder from the stock image? I figured I would need to do with through ADB, but I have no idea what commands I would have to execute.
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
Click to expand...
Click to collapse
Is your efs folder completely gone ?
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
Is your efs folder completely gone ?
Click to expand...
Click to collapse
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
drunkenscholar said:
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
Click to expand...
Click to collapse
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
hednik said:
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
Click to expand...
Click to collapse
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
I hate to ask but did yo factory reset the phone...like in stock recovery ?
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
xBeerdroiDx said:
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
Click to expand...
Click to collapse
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Odia said:
# echo -n ON > /efs/FactoryApp/factorymode
(and yes ON is the correct setting to turn it off)
Click to expand...
Click to collapse
hednik said:
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Click to expand...
Click to collapse
you are correct. i looked back over the thread. i had thought he posted something yesterday about having an EFS backup.
your find seems like it should do the trick
hednik said:
I hate to ask but did yo factory reset the phone...like in stock recovery ?
Click to expand...
Click to collapse
Yessir. When the phone booted back up it didn't go through the setup process. Just goes straight to the homescreen. Also when I boot into restore mode I see this under the menu options:
E:failed to mount /efs (Invalid Argument)
E:failed to mount /efs (Invalid Argument)
# MANUAL MODE #
--Applying Multi-CSC...
Applied CSC-code : unknown
Successfully applied multi-CSC.
I tried turning it off with terminal emulator at one point last night, but it didn't seem to work, I THINK because the EFS folder is empty. I'll have to re-root tonight and try it again since I've restored my stock firmware.
It may seem like I'm shooting down every suggestion you guys throw at me, but I really appreciate the input. XDA is a big place and I tried to be very thorough when searcing for a solution before posting this thread, but I'm sure there's something out there I've missed. Thank you for your efforts.
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
drunkenscholar said:
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
Click to expand...
Click to collapse
Ah exactly what I have been looking for on this one for you. I found a few that explained how to push your old EFS folder with ADB but none about making another. How crazy it was yesterday it popped up on a post. That looks like your best shot as you folder seems to be corrupted and although IMEI is intact you need a new one folder that is intact. Let us know how it turns out
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
drunkenscholar said:
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
Click to expand...
Click to collapse
Here is one I had found earlier:
http://forum.xda-developers.com/showthread.php?t=1169805
xaurion said:
[/COLOR]Problem fixed!! give read write permissions for user/group/others to the keystr file.[/QUOT
Have you looked at this ? (or is this just the same thing as turning it off)
- One more thing, what file explorer are you looking at the efs folder with ?
Click to expand...
Click to collapse