can somebody tell me what is the function of the "recovery image" when rooting a nexus s 4G
im asking because in other site say if you don't do the following the recovery image won't load everytime u reboot your nexus s
---------------
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh
that will mount the system as writable and rename the file that overwrites the recovery image on reboot so that our custom recovery will stay
--------------
thanks
When you install clock work recovery the first time and than flash super user and try to go back to recovery it will load the stock recovery and have an android and exclamation mark. I take it your using the unlocker method. For clock work to stick every time you go into recovery, most people download rom manager and flash from there. Personally I just flash clock work from fastboot again because I don't like rom manager. Btw here is a tip when you first flash clock work from fastboot make a backup before you install super user so that you can have a backup with stock everything and all you have to do is OEM lock.
Sent from my Nexus S 4G using XDA App
Another way to stop the recovery from disappearing each reboot is:
flash recovery
flash superuser
boot into android
download "super manager" app, set it to read/write access (needs superuser), move to system/etc folder and rename install-recovery.sh to something else
then flash recovery again
done
---
Basically what I described is the same the lines in OP do via adb shell.
chewbz said:
When you install clock work recovery the first time and than flash super user and try to go back to recovery it will load the stock recovery and have an android and exclamation mark. I take it your using the unlocker method. For clock work to stick every time you go into recovery, most people download rom manager and flash from there. Personally I just flash clock work from fastboot again because I don't like rom manager. Btw here is a tip when you first flash clock work from fastboot make a backup before you install super user so that you can have a backup with stock everything and all you have to do is OEM lock.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
i think now i get it, if we don't install the "custom recovery" , we can not install the "superuser.zip". and the phone can't be rooted, right ?
and if i go back to the stock recovery after flashing the "superuser.zip" the phone will stay rooted ?
thanks
agel1 said:
i think now i get it, if we don't install the "custom recovery" , we can not install the "superuser.zip". and the phone can't be rooted, right ?
and if i go back to the stock recovery after flashing the "superuser.zip" the phone will stay rooted ?
thanks
Click to expand...
Click to collapse
Well flashing the superuser.zip through recovery is the easiest way. That is why. Recovery is needed mainly ro flash roms radios kernels.... just for root,recovery is not mandatory. you can also use adb, if you know how to do it.
Sent from my Nexus S using Tapatalk
anyone had success with using KFU to install CWM? Seems like you would just replace the TWRP image with the CWM image...or I could be wrong and brick my fire
Sent from my VS910 4G using XDA App
you can replace twrp with cwm but not with kfu
you have to install it manually as described in the op of cwm
http://forum.xda-developers.com/showthread.php?t=1454241
edit: just realized what you are tying to do ! don't think that this will work cause the install command is different
twrp starts a install routine with the "boot" command - cwm will be directly flashed with the "flash" command
Well I tried it before I read your response and now I'm stuck at fff boot logo...kfu is at "waiting for device"...I'm sure there's a thread for that somewhere
Sent from my VS910 4G using XDA App
http://forum.xda-developers.com/showthread.php?t=1490719
future refference, use this to install cwm directly, no fastboot required.
http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium
I tried to change the DPI, now I'm on boot loop. I have no backup. I have TWRP recovery, but trying to side load a new ROM via abd says "* cannot read 'sideload' *". I've tried to use the file explorer in TWRP to fine build.prop to edit it manually but that's not working either..
What can I do? Thank you so much!
Sent from my GT-I9100 using xda app-developers app
As a last resort you could always back up your data and flash stock/whatever rom you want on your phone then restore the data.
wipe and flash a new ROM or the same one again.
Sent from my Nexus 4 using xda app-developers app
Reflash your ROM & it will resore the default build.prop. I've never messed with the sideload option in TWRP but if you're booted into TWRP you should have adb access (no sideload function needed)
Hi everyone,
So I have never ran across this issue before. I haven't had any problems with my device and yesterday I wanted to test out the new Jelly Bam update rom from their site. The rom would not boot pasted the "Google" spash screen so I rebooted in to recovery and did a full wipe and restored via backup to my previous rom just like normal. Well then I noticed that normally when I connect my phone to my computer I see my internal memory drive pop up which I am able to click on and then access my files, but this time when I accessed it I have a hand full or folders like 0, twrp, android, etc and I had to double click on o folder to access my memory with all my files. I thought that was weird so I went on about my day. Later I tried to do a fresh install of my current rom PACman but even after doing a fresh install the phone will not boot passed the Google spash screen, and now twrp doesn't even see my backup file because its being directed to this new partition with all the folders I was talking about. I even tried using the file manager in twrp to move the backup to that twrp folder but twrp doesn't even see it.
So as of right now I can get in to twrp but I can not boot my device pasted the google splash screen. I also can't access my memory through my pc since nexus does not allow it with twrp. What do I do? My thoughts are that something got screwed up with the partitions when I flashed the Jelly Bam rom so I will need to go back to stock, does that sound about right? I was thinking of following these instructions to go back to stock and then move on from there, any thoughts or alternatives? http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Thank you
Trying this method to return to stock: http://www.wugfresh.com/nrt/
If no one has any input I will assume I am following the right path.
I flashed factory images a couple weeks ago and in order for TWRP to see the nandroids I copied back to my phone I put them in the following path: /sdcard/TWRP/BACKUPS/stringofrandomnumbersandletters/
Are your TWRP backups in a similar location?
If you've decided to go back to stock, I'd suggest using the following guide by efrant... http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
It looks like twrp is now looking at my twrp folder in my sd card 1 not sd card 0 where I have had my backups and all my files. After trying again, I moved the TWRP backup to the sd card 1 twrp folder, twrp recognized it and I restored from backup....but when I reboot I am still stuck on the Google screen. Not sure what to do.
Underground_XI said:
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Since I can't move anything to my memory, any suggestions?
If you've got adb and the proper drivers installed on your PC you could try:
Code:
adb push ROM.zip /sdcard/ROM.zip
from the command prompt. Obviously use the name of the actual ROM.
Edit: ignore that, just read the post where you managed to restore! D'oh!
Have you tried clearing both caches?
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
synergeticink said:
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
Click to expand...
Click to collapse
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that's were I am stuck right now. I am not a pro at using adb commands, never used it till I got my nexus 4. Right now when I launch the cmd it shows "C:\Users\My User Name\Desktop>", not sure where to go next. I guess I am not sure what I should be pushing at this point either.
Oops...it seems I was editing my post at the same time you were responding to it...take a look at my previous response again
I'm fairly new around here but I can help with the adb commands if you need. Hang in there
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I tried wiping cache/dalvik/system/factory reset and then both restoring from backup or flashing the latest PACman rom which is in my sd card. Right now I am reading the http://forum.xda-developers.com/showthread.php?t=2018179 guide to see if I can use adb to flash my rom or another recovery. Makes sense if its the recovery not letting me flash anything, but i'm not a dev. At least I am able to get in to recovery to begin with, good sign I guess.
If you can boot into bootloader and recovery there are many options to help get you up and running again. That guide by Jubakuba is really good but if wiping and restoring your backup from within TWRP didn't work I would highly suggest reading efrant's guide on returning to stock...I posted the link in an earlier reply.
Sent from my Nexus 4 using xda app-developers app
I was able to flash cwm using adb, now trying to do a fresh install
Nope, doing a fresh install didn't work. Now its time to restore to stock. ......
One problem:
"
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;"
UPDATE; Got it, instructions were not clear.
synergeticink said:
UPDATE; Got it, instructions were not clear.
Click to expand...
Click to collapse
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its weird adb will not work on the computer unless the files are in the platform-tools folder in androi sdk. trial and error, just finished flashing system....
should I do this command, I really don't want to lose my stuff:
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Well, I didn't and finished the process...did a reboot when I was done...now its on the Google screen...just waiting....I'm seeing a Nexus X splash screen!!!...
Update: Its taking a very long time, hopefully it works...going to give it another 10 mins
And we have BOOT... thank you everyone! Now I have to root this sucker!
So, I wiped my phone and didn't realize that the rom I was about to install was corrupted (I think the download didn't finish) and I forgot to do a backup, what can I do to recover from this disaster?
Use Nexus toolkit.
Two easy options:
1. Use adb to push a rom to your sdcard from your recovery then install like normal
2. Use fastboot to flash a stock image your system partition
Download a ROM that's not corrupted and place it in platform tools folder (where you have your adb is located) and just go to your phones recovery and sideload
Sent from my Nexus 4 using xda app-developers app
CellPhish said:
Download a ROM that's not corrupted and place it in platform tools folder (where you have your adb is located) and just go to your phones recovery and sideload
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thank you to all of you, I used Wug's Toolkit (NRT) and it worked.
Similar Problem
My problem is similar but a bit different.
I flashed CWM over the top TWRP and when I re-entered custom recovery and I went in to install a zip from sd not all my folders where showing including the folder I keep all my roms in.
When I try to boot back in to system it just takes me back to recovery.
Am I being a noob or is it something gone wrong?
Thanks in advance!