Related
I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob
Describe steps you have taken to root in detail.
i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob
any one can help me?
Vbob
Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...
vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot
[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?
hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, (i selected option 1 intall in /boot, i assume this is where i screwed up) this too went fine. but i couldn't install the new rom as it was no longer there, and now i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.
SemnteX said:
hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, this too went fine. but i couldn't install the new rom as it was no longer there, and no i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.
Click to expand...
Click to collapse
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy
simms22 said:
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy
Click to expand...
Click to collapse
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium
marty331 said:
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
yes i do, but i get confused using those, which is why i used the toolkit to unlock and root my device. unfortunately i got a little carried away and installed cwm into the wrong directory and overwrote the boot img.
SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.
simms22 said:
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.
Click to expand...
Click to collapse
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up
SemnteX said:
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up
Click to expand...
Click to collapse
No sir, how about reading this link!
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm sure there is something similar on xda but I have this link handy.
Sent from my Nexus 7 using xda premium
Changing the title of this post to problem solved doesn't help anybody in the future with a similar problem
Sent from my Nexus 7
Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help
Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.
Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium
Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL
Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse
Are you installing loki doki after the rom ?
Hi guys..
Few of you guys might already know me from around the forums. I know my ins and outs of android but today i am kinda stuck and i have not got a clue what to do. Here is the story.
Currently on my device i have a clear sd card. Only things i have on there is a slimkat build and gapps ready to flash. Problem is when i tried to make a backup it failed. Running TWRP recovery 2.6.0.0. Tried different things to get it working and nothing.
Now i tried to use a toolkit to be able to push the files to flash and get my phone going and still nothing it just goes back into recovery and nothing...Anyways another thing is adb is not working as it should...in recovery it recognizes my phone as connected but when in bootloader it does not
any help would be appreciated
Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)
wcn said:
Just some ideas here:
On device:
Try other version of TWRP or Multirom TWRP or CWM.
On PC:
Reinstall driver (Universal Naked Driver)
Click to expand...
Click to collapse
kinda in the process reflashing stock factory settings again and see what happens..many thanks anyway...
is there anything wrong with TWRP? cause anything i do it fails and i have not got a clue why
There are mixtures of results of peoples using different versions of TWRP/MultiromTWRP/CWM and nobody had a dam* clue what/why causes the incompatibility. Btw, I'm on latest MultiromTWRP which works great for me flashing variants of roms. Anyway, happy reflashing.
why dont you update twrp to 2.6.3.3
rakludnet said:
why dont you update twrp to 2.6.3.3
Click to expand...
Click to collapse
i have..but even that one has given me troubles..the thing that seems to work is when you go into mounts just untick the system and everything seems to work okay..am just surprised that this is an issue though
Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers
considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle
bachera said:
considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle
Click to expand...
Click to collapse
Thank you for your answer Bachera. I am not sure I understand what you mean by "via zip flashable distro of kitkat."
Plus my kitkat version of android is rooted, why would you think kitkat has no root yet?
Light_Addict said:
Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers
Click to expand...
Click to collapse
I encountered something similar on my phone. However, i was on 4.2.2 but this worked for me. Give it a shot, it might work for you too
http://forum.xda-developers.com/showthread.php?t=2500441
Good luck
Try Flashify from the Play store to flash a working recovery for your phone. I had the same issue with philz latest version. I had to use an older version of philz to get it to work on my phone.
Sent from my LG-D803 using xda app-developers app
Yeah I misread, I thought you went to a official kitkat. Only way to get root on kitkat is if lucky its maintained with a ota update. or a special made kitkat, thats what I mean with special distribution (distro) one via recovery flashable.
kitkat rooting directly at the moment of writing is not possible due to lg bootloader.
send from the jungle
Thank you all for the help and suggestions. I tried flashify and I did not work.
However freegee worked very well and managed to go back to CMW.
All functional now!
Thanks