Related
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
NOTE: Noob is not a really good word. kinda discriminating. newbie better.
THIS will GUIDE how to get on foot if your just starting on Galaxy Y, most probably, ANDROID
1. First Things first. Know your Phone. before doing anything, just be on the stock for a while. Know all the things, settings, install some app and alike. This way, you'll know your way through. See apps like market, Maps and others, check bugs etc.
2. Second part is knowing a basic tweak of your phone, to be exact: BATTERY SAVINGS. Know your way from this apps. See how they handle your battery life. The purpose of this is to know the performance of your phone
3. So you feel much better knowing your phone, you can start rooting or installing some replacement apps Go, ADW, Pansi, Popups, keyboards its up to you. But i dont recommend instant rooting when your just getting on foot.
Rooting wont brick the phone, maybe but its in the least.
(I wont be giving links for many threads here are available already. Its hard just to give you everything when researching can't kill one)
WHAT IS ROOTING?
rooting gives you access to the system of your phone. thats it
Soft ROOT-stated in the above
Hard ROOT-gives you access to the commander of the system which allows you to access the device via shell extensions and ADBs
4. Same as step 1. See how does root work for you. Dont just access the system right away using an explorer. look for apps that can help you achieve your desired goal that requires root access. a good start would be RAM tweaks.
5. Removing apps that you dont need. Its the power of Rooting that grants you this. basically, it improves RAM usage and speed of the device especially when "app-example.apk" initiates on its own. ofcourse it increases the capacity of your device.
6. KITCHENS. for a start you can use the UOT kitchen which allows you to modify some parts of the device. as far as i know, mods like transparency, lockscreen and bootanimation wont work on stock dont ask why coz i dunno sorry. so using this kitchen can allow you to change statusbar appearance pull down notif bar, etc.
but, the MAIN concern of a KITCHEN is ROMS.
ROM is the thing that the device reads for it to run properly.
ROM development are for making a benefit that can help a device achieve its fullest performance. Speeding it up, etc.
You can see the Development Page for it
**EXTRAS:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
PARTITIONING.
since SGY got a small memory for internal, u can use partitions in the SDcard to let it handle some memory for you.
BOOT recovery:
it is where you flash mini updates like rooting CWMod, UOT kitchen mods and others
**Clockworkmod recovery / CWM is a custom CWM it has additional features moreover see for yourself
i guess thats it ill just edit it if somethings new comes
THIS IS FOR NEWBIES, no noob persons exist: ONLY NEWBIES.
hoped this helps you can just PM me for assistance but for now please bear with this simple guide thanks
PS: im no dev but as soon as i got my laptop ill start im just using a netbook and my phone for learning. so thanks
good tutorial for newbies and i try to make a rom,but i dont if can i brick my phone from errors.I read many things before make a rom.
JuSt pReSs THANKS if i HeLLpeD yOu
Yap. Rom manager is not yet working for G-Y dont be afraid. Ive bricked my phone a dozen times alrready.
-- [email protected]
what happens if sm1 bricks his phone??
If soft, phone wouldnt boot properly though can go to download mode
Hard, cant open even boot recovery
-- [email protected]
nice post there man or rather master? hehehe ( you are now my master ) , i really think this thread should be sticky.
very informative for the newbies out there as a head start, keep on posting and helping here master
if they will be needing another moderator here i will surely vote for you
thanks you so much!
it would be nice to include how to make a hard bricked phone to soft brick
ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
Theres a thread already so i cant make one im just here for those who really want to get on their foot
-- [email protected]
[Guide Lines] HARD / SOFT BRICKS FOR GALAXY Y GT-S5360 MOBILE
musashihatred said:
Theres a thread already so i cant make one im just here for those who really want to get on their foot
-- [email protected]
Click to expand...
Click to collapse
ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
Guidelines for how to solve HARD / SOFT BRICKS problems FOR GALAXY Y GT-S5360 MOBILE
http://forum.xda-developers.com/showthread.php?t=1498327
musashihatred said:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
Click to expand...
Click to collapse
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?
jayem123 said:
nice post there man or rather master? hehehe ( you are now my master ) , i really think this thread should be sticky.
very informative for the newbies out there as a head start, keep on posting and helping here master
if they will be needing another moderator here i will surely vote for you
Click to expand...
Click to collapse
aw ) my masteR!!!! long time! D hehe tnx. ^^
ronnieryan said:
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?
Click to expand...
Click to collapse
sure thing but it would be really better if you read some threads here. a lot of those stuffs are already here
1. download the rom you needed/wanted
2. download odin v1.85 w/ totoro.pit
3. turnoff phone remove sim + sdcard
4. open odin and put the files into:
boot
pda
csc
modem
something like that. put there the files you downloaded.
check if re partition etc are checked
then now get the data cable, and put the phone into DL-mode
(HOME+VOL-DOWN+POWER) hold till it boots into DL-Mode
pressing VOL UP- continue
VOL DOWN- Cancel
press the vol up so and youll be on DL mode
connect the cable wait for it to be recognized by the Odin, if ok pray and start.
just takes around a min to do so. the phone then reboots automatically. do a hard rest and boot again.
voila
since your a filipino you can check symbianize.com for infos. reading some guides there by our masters will surely help you
*so as the rules say here read threads first before asking though its ok for me. it would be nice if i'd helped you bro
ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
JTAG-ging is only solution to resurrect
a hard bricked phone..
musashihatred said:
NOTE: Noob is not a really good word. kinda discriminating. newbie better.
THIS will GUIDE how to get on foot if your just starting on Galaxy Y, most probably, ANDROID
1. First Things first. Know your Phone. before doing anything, just be on the stock for a while. Know all the things, settings, install some app and alike. This way, you'll know your way through. See apps like market, Maps and others, check bugs etc.
2. Second part is knowing a basic tweak of your phone, to be exact: BATTERY SAVINGS. Know your way from this apps. See how they handle your battery life. The purpose of this is to know the performance of your phone
3. So you feel much better knowing your phone, you can start rooting or installing some replacement apps Go, ADW, Pansi, Popups, keyboards its up to you. But i dont recommend instant rooting when your just getting on foot.
Rooting wont brick the phone, maybe but its in the least.
(I wont be giving links for many threads here are available already. Its hard just to give you everything when researching can't kill one)
WHAT IS ROOTING?
rooting gives you access to the system of your phone. thats it
Soft ROOT-stated in the above
Hard ROOT-gives you access to the commander of the system which allows you to access the device via shell extensions and ADBs
4. Same as step 1. See how does root work for you. Dont just access the system right away using an explorer. look for apps that can help you achieve your desired goal that requires root access. a good start would be RAM tweaks.
5. Removing apps that you dont need. Its the power of Rooting that grants you this. basically, it improves RAM usage and speed of the device especially when "app-example.apk" initiates on its own. ofcourse it increases the capacity of your device.
6. KITCHENS. for a start you can use the UOT kitchen which allows you to modify some parts of the device. as far as i know, mods like transparency, lockscreen and bootanimation wont work on stock dont ask why coz i dunno sorry. so using this kitchen can allow you to change statusbar appearance pull down notif bar, etc.
but, the MAIN concern of a KITCHEN is ROMS.
ROM is the thing that the device reads for it to run properly.
ROM development are for making a benefit that can help a device achieve its fullest performance. Speeding it up, etc.
You can see the Development Page for it
**EXTRAS:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
PARTITIONING.
since SGY got a small memory for internal, u can use partitions in the SDcard to let it handle some memory for you.
BOOT recovery:
it is where you flash mini updates like rooting CWMod, UOT kitchen mods and others
**Clockworkmod recovery / CWM is a custom CWM it has additional features moreover see for yourself
i guess thats it ill just edit it if somethings new comes
THIS IS FOR NEWBIES, no noob persons exist: ONLY NEWBIES.
hoped this helps you can just PM me for assistance but for now please bear with this simple guide thanks
PS: im no dev but as soon as i got my laptop ill start im just using a netbook and my phone for learning. so thanks
Click to expand...
Click to collapse
I always like this musashihatred guy.
Very active in SGY development issues.
Keep encourage us (the NEWBIES) to learn.
Sent from my GT-S5360 using Tapatalk
bydefault said:
I always like this musashihatred guy.
Very active in SGY development issues.
Keep encourage us (the NEWBIES) to learn.
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
THANKS MAN
i just dont like some here that, Hey not for noobs or what. not for this.
but ill be selling my phone in the ff day but i wont leave this forum. ill still develop galaxy y ill be getting galaxy s =="
Video tutorial
ronnieryan said:
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?
Click to expand...
Click to collapse
http://galaxyygaming.blogspot.in/2012/02/flashing-with-odin.html
Thanks.. really helpful..
I just sold my galaxy y.
i sold it earlier. but pls dont stop sending questions and some guides. ill always be free to answer. ill be getting M130k tom. but i will always be here :d
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 guys. So my GF has this Samsung Galaxy S (Sprint Epic SPH-D700) ... I think I've got the right section. (EDIT: nope. ty kennyglass123. sorry about that :/)
She drops her phone, display stops functioning. However, the device still works - touchscreen is responsive, boots well, etc. The only thing she needs from it is her contacts. "Easy, Google has it, right babe?" ... "No, when it asked me if I wanted to sync with Google I said 'no'" ...
So, I'm wondering if there's a way to grab the contacts that are theoretically stored on internal memory without seeing the screen. Can't connect to PC because device requires input on it, which I can't see. Cell stores can't help because their transfer machines require the same input. Basically I'm wondering if it's possible to do 1 of 2 things before going ahead with an LCD replacement (which I'm comfortable with doing, just a question of money given that she has a different device she can use and she's off-contract now).
Is there a way to extract using something like ODIN or some command-line tool that forgoes the need for too much device-screen input?
Can anyone possibly provide screenshots of the usb-plugin process as it looks on the device? (once USB cable is plugged in and my PC makes the connected ding, if I could see the relative location of the necessary selections I could just hit it blind). My device is a SGS3 and the process is very different, I just have no clue what parts of her screen to touch. This is only helpful if I can use something (Like KIES) on the PC-end to extract something from the device.
Any other ideas would be phenomenal
Please post questions in Q&A
Thread moved
FNM
Sent from my SPH-L710 using xda premium
Got an idea. Suppose you have USB debugging already on. Connect to PC (make sure driver's installed) and use ADB to copy the contact database out for use on other Android devices (maybe it'll work, maybe it won't)
I'll get you some detailed commands and operations if you need more help.
Sent from Nokia N900 w/ Android 2.3.7
Export to SD card
Well, simple way would be to work off of screenshots from a stock Epic, then export the contacts to the SD card. This way you could work blindly on the touchscreen itself, but orient your finger via the screenshots.
I used stock FC09 multiboot, since I'm on AOKP M6.
Step 1: View attachment 1481544
Step 2: View attachment 1481545
Step 3: View attachment 1481546
Step 4: View attachment 1481547
Step 5: View attachment 1481551
you guys rock ty so much for replying.
USB debugging is apparently not enabled . this is probably the most ideal way to go though.
Very awesome of you to provide screenshots. i've tried this a number of times and i have a feeling she doesn't actually know where here contacts icon is. and no touch feedback. any chance you would be so kind as to provide screenshots for enabling USB debugging? assuming menu key from homescreen allows for settings, you can start from there. I would then be able to use the ADB method. if i'm asking for too much please don't feel obligated or anything.
Got an idea. You're on stock ROM? Then flash CWM via Odin download mode, reboot into recovery. CWM has ADB enabled by default. Try it. I may not be able to provide further details but I think this will work if you're familiar with the steps of Odin
Oh yeah, and you may have to manually mount /system and /data to access files... If you need to know how to use CWM in the blind I could flash back to CM7 (recovery's almost the same) and tell ya how you should navigate to the correct items with the directional keys on the QWERTY keyboard.
Would like to be of help
Sent from Nokia N900 w/ Android 2.3.7
Stock roms have keyboard short cuts and I'm pretty sure one of them is to open contacts. If someone can tell u what that shortcut is then u can use it along with the screenshots to export them to ur sd card.
Sent from my SPH-D700 using xda app-developers app
:highfive: ooh that's perfect! i'm still with you guys, really appreciate the advice. going through some other heavy stuff atm, don't want you guys to think i'm abandoning this thread. will update this post when the madness ends
AndyYan said:
Got an idea. You're on stock ROM? Then flash CWM via Odin download mode, reboot into recovery. CWM has ADB enabled by default. Try it. I may not be able to provide further details but I think this will work if you're familiar with the steps of Odin
Oh yeah, and you may have to manually mount /system and /data to access files... If you need to know how to use CWM in the blind I could flash back to CM7 (recovery's almost the same) and tell ya how you should navigate to the correct items with the directional keys on the QWERTY keyboard.
Would like to be of help
Sent from Nokia N900 w/ Android 2.3.7
Click to expand...
Click to collapse
Hey, I have a similar situation to the OP as my Epic 4G also has a broken display. If I follow your advice, then would I be able to somehow get the phone into diag/modem mode without seeing the dialer on the screen?
KillerFurby said:
Hey, I have a similar situation to the OP as my Epic 4G also has a broken display. If I follow your advice, then would I be able to somehow get the phone into diag/modem mode without seeing the dialer on the screen?
Click to expand...
Click to collapse
Huh? My suggestion is for times when you want your system files backed up without display... And you maybe trying to use it normally as a phone? Rethink.
However if you know what your ROM looks like after boot (requires you to be VERY familiar with the phone) you should be able to blind operate well. Best of luck to ya.
Sent from my Incredible S using xda premium
AndyYan said:
Huh? My suggestion is for times when you want your system files backed up without display... And you maybe trying to use it normally as a phone? Rethink.
However if you know what your ROM looks like after boot (requires you to be VERY familiar with the phone) you should be able to blind operate well. Best of luck to ya.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
No, actually I am trying to read the profile information in CDMA Workshop.
KillerFurby said:
No, actually I am trying to read the profile information in CDMA Workshop.
Click to expand...
Click to collapse
Tough then... From what I understand you're trying to grab modem-related info for use on other phones? No good idea, but anyway it's possible if you post your ROM, version, we flash it and give ya screenshots. See for yaself and good luck
Sent from my Incredible S using xda premium
Huawei Ascend Y H866C ROOTED!!!
If you have been lurking the posts on google for a root for the phone, you are just like me, so i
decided to learn some things. I contacted GiantPune and we worked together applying this root:
http://www.sendspace.com/file/k9b3ks
download poot, install it let it download and install ministro,
start poot,it will then start ministro
Ministro will create some libraries,thats ok.
Poot will then start, make sure to press the poot button and then it will give you some code
At the end of the code somewhere in there it should say sucessfully found and wrote su.
press the built in rootcheck to see if you are rooted
restart the phone go to the playstore and download Superuser.
You are now fully rooted!
All the thanks goes out to GiantPune for his awesome and funny creation.
Let me know if this works and if I helped you,please press the thank you button!
It worked great, I've been watching the forums for a root for almost 3 months. I'm new to this, but I believe I could write a book over the things I've read. I do have one question what is the next thing I need to do? Once again thank y'all for making a flawless way to root. Billy
Sent from my H866C using xda app-developers app
billyv said:
It worked great, I've been watching the forums for a root for almost 3 months. I'm new to this, but I believe I could write a book over the things I've read. I do have one question what is the next thing I need to do? Once again thank y'all for making a flawless way to root. Billy
Sent from my H866C using xda app-developers app
Click to expand...
Click to collapse
install some cool root apps from the market including wireless tether =)
here is a list of rooted apps you can download right from your phone in the browser
http://forum.xda-developers.com/showthread.php?t=1781500
check it out and enjoy your rooted device!
i am making a ROM NOW~! so be sure to check back
This failed to root my H866c, here is the info the apk returned.
2012 giantpune
[+]opened device
[+]Set logging mode
[+]Resolved Symbols
[+]Mapped 0x1000000
[+]Hooked mask_request_validate()
[-]Error running kernel-mode code
[-]Failed to clean up our mess
[-]current && current != last + 1 0000ffff 0000ffff
[-]Haxx has run its coarse. Reboot the device to play again.
A demon materialized while pooting. Error code: 87
su binary was not written
You need to restart your device
Any ideas?
Worked perfect! Thanks!
Sent from my Rooted H866c Ascend Y via XDA.
Help
sketchscarz said:
install some cool root apps from the market including wireless tether =)
here is a list of rooted apps you can download right from your phone in the browser
http://forum.xda-developers.com/showthread.php?t=1781500
check it out and enjoy your rooted device!
i am making a ROM NOW~! so be sure to check back
Click to expand...
Click to collapse
Please help. My phone froze , so i had to take my battery out to restart. Well it restarted but iit would not load the system, so i shut it down and it druid three same thing. Then I tried to do a factory restore and now when ii boot it stays in the Huawei screen and that's it. I can get to my restore screen and Go nto my SD Card but i can't load any backups or packages because of the signature verification. Please let me knowthe steps to take to get my phone up and running l... thank you in advanced.
ETAnever said:
This failed to root my H866c, here is the info the apk returned.
2012 giantpune
[+]opened device
[+]Set logging mode
[+]Resolved Symbols
[+]Mapped 0x1000000
[+]Hooked mask_request_validate()
[-]Error running kernel-mode code
[-]Failed to clean up our mess
[-]current && current != last + 1 0000ffff 0000ffff
[-]Haxx has run its coarse. Reboot the device to play again.
A demon materialized while pooting. Error code: 87
su binary was not written
You need to restart your device
Any ideas?
Click to expand...
Click to collapse
Hard reset the device install it again
Sent from my SPH-D600 using Tapatalk 2
No luck with the exact same debugging.
Everything is running smooth and fast. Now we need a custom Rom...
Sent from my H866C using xda premium
Thanks!~
sketchscarz said:
Huawei Ascend Y H866C ROOTED!!!
If you have been lurking the posts on google for a root for the phone, you are just like me, so i
decided to learn some things. I contacted GiantPune and we worked together applying this root:
http://www.sendspace.com/file/k9b3ks
download poot, install it let it download and install ministro,
start poot,it will then start ministro
Ministro will create some libraries,thats ok.
Poot will then start, make sure to press the poot button and then it will give you some code
At the end of the code somewhere in there it should say sucessfully found and wrote su.
press the built in rootcheck to see if you are rooted
restart the phone go to the playstore and download Superuser.
You are now fully rooted!
All the thanks goes out to GiantPune for his awesome and funny creation.
Let me know if this works and if I helped you,please press the thank you button!
Click to expand...
Click to collapse
Works great been looking for this my friend really needed this!
So has anybody looked into a custom recovery for this phone. I would love to see some Rom development.
Sent from my Rooted H866C using xda premium
few questions
Now i have read that many have achived root on the ascend Y H866C. What I have not seen if its there a way to go back if you mess up.
#1 Just for example.. i use dto own a galaxy precedent.. and if i messed up i could just go back and do a clean stock restore.. is that possible with the ascend Y?
#2 Once i achieve root.. is it possible to create a partition to install more apps and remove blotware apps ? and what apps or programs i need to create the partitions?
#3 many have mentioned about holding the up and down volume while holding the power button.. what does that doo? and do you do that once you are rooted or before? I have tried while the phone is off and on but nothing happens.
I really want to root my phone but if i brick i just want to know i can restore back to stock at least.
Thanks in advance to all the great devs and the smart people that make this possible.
Regards,
Pryma
Bump?? can anyone please help the ascend Y H866C community!
---------- Post added at 08:58 PM ---------- Previous post was at 08:15 PM ----------
anathematized1 said:
It's not very difficult.
Go to the previous page (page 4). Download the Poot posted by that guy that I still need to send a donation to (I promise I will, I have to wait until the first of Feb. when I have money).
1. Save Poot to the SD card.
2. Download and install SuperUser (or SuperUser Elite if you want, but it's not necessary to pay for SU Elite).
3. Run Poot. It will need to download Ministro II. Accept the download and just let Ministro II download/install.
4. Let Ministro II install the QT packages it needs.
5. If you want, Reboot the phone (press and hold power button, select restart), but I don't think it's necessary.
6. Run Poot again, it will give you a success or failure message. If you did everything right, it will give you a success.
SuperUser or SuperUser Elite is necessary just for the root. I don't know about ClockWorkMod other than that CWM does NOT (the last time I checked) have a mod that supports Huawei H866c. Now if you do get a mod on there, you don't need SU or SU Elite (most of the time).
Click to expand...
Click to collapse
Now I followed the above exactly and it appears to have worked. Here is what my screen looked like once done.
I tried to rotate the pics but could not do it had to retake. if its really necessary ill rotate them for ya.
It wont let me put links for the images or for other posts. I will update the post when i have the ability to
Hope this helps others in know that it does work. Now all we need if someone is willing to assist in making a stock recovery so we can go back to stock and make partitions for more space for more apps. Anyone out there can assist the H866C community please?
I'm fairly new to the android scene but have become very interested quite quickly once I started to learn more. I have managed to root my phone & get rid of google+, google maps, etc. I actually even uninstalled Google Play at one time & managed to get a version I found on KAT to load off of sd card with no problems so far, but still quite small internal memory. I read in my research about possibly being able to "trick" the phone into thinking the sd card were part of internal memory, is this real? Using Root All To SD I've managed to create and mount a 512mb external SD memory but can't get anything to move to it. Still never seems like I can get internal memory above 30. Any suggestions on how I could better unlock my phone to it's full potential?
hi ditch. Im on ths asme boat with you man. I saw your post on the other forum as well. Its frustratin to think that the H866C is not thriving as a great phone which i think it is! Im really hoping that other developers come to our rescue.
Im willing to pay someone to get a ROM going so we can partition and recover back to stock. Please PM me devs!! we really need your help!
Thanks in advanced
Regards,
Pryma
I couldn't agree more, the phone seems to be a really good phone (except the internal memory problem). It's just getting to the point now that I feel I must ask if it's something I should wait around on or if it would be in my best interest to get my money back and try to get a different phone instead.
Sent from my H866C using xda app-developers app
Right now it seems like things are not looking good. For now im keeping my phone which is still functioning very well. Im keeping it in the hopes that someone comes and helps us resolve this issue.
TO ALL XDA DEVS! PLEASE HELP US OUT WITH THIS PROJECT. WE CAN WORK OUR A MONETARY DONATION TO THE SITE OR WORK OUT THE DETAILS! PLEASE HEAR OUR CRY FOR HELP.
that might be overkill and some might not like it but I just feel that they gave up on us. maybe because the phone is too hard or difficult to crack. I could not say or even imagine since im not proeffcient in this sort of things. However i think something could be arranged if they are willing for work with us. would you be willing to assist in payment or donation if they work on this for us ditch?
regards,
pryma
I posted questions on a couple sites & on one I got this is return:
Apps/scripts such as A2SD and Link2SD would work for you to accomplish that, however, I believe you'd have to have a custom recovery, as A2SD is a script that must be flashed from recovery, and while Link2SD doesn't need to be flashed, both require you to also partition the SD card and use one of the partitions for app storage. You might be able to use Link2SD without recovery though, if you partition your SD card on a PC.
As a matter of fact, I just found a guide that will probably get you through with little or no fuss:
(there was a link for a Link2SD tut here but I'm a noob so no outside links yet)
from BlastGT1 at UnleashedPrePaids
I've gotten a second partition made but still am having some trouble with linking apps to it. Hope this helps us on our journey somehow.
To all xda devs! Please help us out with this project. We can work our a monetary donation to the site or work out the details! Please hear our cry for help.
Using Link2SD I've managed to install about 70 apps and still have roughly about 60mb of internal storage left as long as I keep my cache cleaned up. So for now I'm doing much better than before. Custom ROMS would be great (don't get me wrong) but defeating the internal memory problem is a win for me. Thank you everyone for the help so far.
Sent from my H866C using xda app-developers app