I want to revert everything but unlock. ROM root recovery the works. Can if be done? Thanks!
Sent from my Desire HD using Tapatalk 2
???
Sent from my HTC One V using Tapatalk 2
No. You need a computer to do it.
Sent from my Nexus 4 using Tapatalk 2
Can I unroot at least?
Sent from my Desire HD using Tapatalk 2
unroot is easy.
find under /system/xbin/su and remove it and also remove supersu.apk via the normal front end.
How about removing recovery?
Sent from my HTC One V using Tapatalk 2
Does anyone have a as stock ROM seeing as I'm on cm10.1 nkghtlies
Sent from my Nexus 7 using Tapatalk 2
cammykool said:
How about removing recovery?
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
You cant do it from tablet itself. You need a computer to do it em all. If you do not have access to a personal computer, let a friend do it and use their PC and do it yourself.
Sent from my Nexus 4 using Tapatalk 2
My USB port is broken. Computers don't recognise it
Sent from my Desire HD using Tapatalk 2
scream4cheese said:
You cant do it from tablet itself. You need a computer to do it em all. If you do not have access to a personal computer, let a friend do it and use their PC and do it yourself.
Click to expand...
Click to collapse
100% wrong answer.
The recovery can be flashed with the recovery booted. That partition is only read once during the boot process - it is no longer in use once the boot has completed (everything is running out of RAM). Same thing for the boot partition. So long as the ROM is rooted, you can flash either from the running OS, too.
The only thing the OP cannot do is relock the bootloader. But he has been told all of this multiple times now - this is something like his 3rd thread on the same topic.
cheers
And my last. I just need this done
Sent from my Desire HD using Tapatalk 2
Sounds like you are looking for a spoon-feeding.
I mean, how hard is it to locate a flashable Stock ROM over in the Dev forum?
Same goes for stock recovery images - just download them from Google.
http://lmgtfy.com/?q=Google+Nexus+factory+images
all they are are upgrade images.... not the full os to go from CM
okay maybe not.. but okay how will i flash the stock recovery?
You could try to backdoor a nandroid restore operation by manually creating a "fake" nandroid backup folder (containing only the recovery.img file and md5 files) alongside your other Nandroid backups. Think of this as doing a nandroid restore where the only component present in the backup is the recovery image.
I don't think you would want to try and hand-create a blob-style CWM backup, but I thought that CWM honors old-style backups if they exist alongside the blob backups (in the correct format). TWRP might be easier because it uses old-style (not blob-style) backups.
The touch version of TWRP allows you to restore individual components of a nandroid backup - for instance the recovery image only.
OK, that's one way, how about another? Use the "dd" command to flash the recovery image - either from a touch-interface recovery, or from a "rooted but unrooted" ROM.
What I mean by that is that from a root-shell command prompt, you can unroot the ROM by hand/command line... even though that terminal session still has root privileges. But don't exit that terminal session before you flash the stock recovery, because that will be the last opportunity to use root with the ROM booted!
for example (flash Stock rooted ROM first, the usual/normal way, download a terminal emulator app, verify that it can get root with "su" command, and then)
Code:
$ su
# mount -t ext4 -o remount,rw /system
# rm -f /system/xbin/su /system/bin/su /system/app/SuperSU.apk /system/app/Superuser.apk
# sync
# mount -t ext4 -o remount,ro /system
# dd bs=4096 if=/sdcard/stock-recovery.img of=/dev/block/mmcblk0p1
Reboot into stock recovery and perform a factory reset.
You can also do the very same set of instructions from touch-version TWRP's command line interface (preceding everything above with a "mount /system" command)
One last thing. Think about the above sequences carefully. For one, you should verify the MD5 signature of the recovery image of the copies(s) you transfer to the tablet is identical tho the MD5 of the copy you extracted from the Google factory image set.
Since you will be giving up root in the ROM (w/ the "rm" command), the only other privilege that will remain is via a custom recovery. If you blow that last step so that the stock rcovery won't boot, the ROM will still boot but you will have no way to perform a final factory reset.
Once you have unrooted the ROM, and flashed the stock recovery, there will be no path back to root for your device (never say never though, kernel exploits might appear).
good luck and take your time with this.
If you are jumping through all these hoops to get a USB connector repaired, I'm not sure why you are going to the trouble - flashing ROMs are wholly unrelated to physical damage to a USB connector. If you thought Google/Asus were going to repair the connector under warranty, it would be chicken-$hit for them to say "we won't repair a connector because you've been flashing". In any event, there's nothing to be done about your unlocked boot loader status, and that's going to be plain as day.
Want a log of the email? Lol. This experience has left a bad taste in my mouth with nexus devices
Sent from my HTC One V using Tapatalk 2
Related
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
mumbo101 said:
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
Click to expand...
Click to collapse
You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse
Just for preventive measures of a follow up question. I did the same thing you did, and when you try to flash CM7 again (because that is basically your only option) you might get stuck on the boot screen. In the recovery screen, go to advanced and clear your davlik cache before you flash it. Worked fine after that.
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
mumbo101 said:
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Well use my old instructions on howto as you can manually flash it via terminal. Just put the 3.0.0.6 recovery.img in SDCard and flash it.
HKM said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
You will need flash_recovery file along with 3.0.0.6.img for this meth to work so I provided you with everything as you just download it and unzip them in root of your /sdcard so you will have standalone flash_recovery and recovery.img in it.
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
So I downloaded new kernels and CM10 for my newly rooted N4. I did a backup before flashing the kernel and didn't pay attention to the error message saying cache was not found or whatever. But the kernel flashed fine and it booted up, nothing out of the whack. When I went back to flash CM10 it said the MD5 sum didn't match so the flashing processes didn't finish. Since my backup was ****ed up and the MD5 didn't match I couldn't restore the system either. Device will boot and will go into fastboot and recovery. Currently using CWM. If I turn on the device normally it will stay on the GOOGLE screen and it will not go into the boot screen. What do?
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
El Daddy said:
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
Click to expand...
Click to collapse
The CM10 zip itself is bad. How can I get another one on the phone? Or can I flash the CM zip without the file being on the phone? Thanks
Also, the error message popped up when flashing the CM zip was set_perm: some changes failed
E: Error in /sdcard/0/cmblahblahc zip
(status 7)
installation aborted
Should I turn off the signature verification anyway?
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
El Daddy said:
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
3 years of rooting and flashing stuff on 3 of my previous phones, there wasn't a time when I had to do this, or had to ask for help. Damn it.
Could you be a little more detailed in how do I go about doing so? As you can see my post count I am a bit of a noob Despite those 3 years. I just don't wanna mess up again, you know?
Thanks for everything dude
What screen should my phone be on? Just type that into the command prompt and it should work?
_thunderchild_ said:
What screen should my phone be on? Just type that into the command prompt and it should work?
Click to expand...
Click to collapse
Sorry I was out and about the past few hours.
You want to be in recovery. Custom recoveries allow you to use adb.
Rename the ROM something easy like CMrom.zip
Then put the CMrom.zip in the same location as adb on your computer.
Open the command window from that directory. (hold shift and right click; then choose open command window here)
Type the command: adb push CMrom.zip /sdcard/
It will push the file to the root of /sdcard/
Then you can flash it.
If that fails, use toolkit to download factory image and flash it through fastboot.
Oh man you guys saved my life. I cannot thank you guys enough. You won't believe how happy I was when I saw the bootscreen. Glad that was dealt with. Again thanks guys
Hey everyone I don't know if this is the right place to be posting this but I had the same problem as OP a few hours ago. I flashed LiquidROM and it got stuck on a boot loop. Needless to say, I panicked and used the adb push method since I decided to delete my AOKP ROM from my folder. Anyway, while panicking what I did was is before flashing, I backed up my entire SD card onto my laptop as ADB backup wasn't working and I pushed the entire folder using "adb push sdcard /sdcard/. Next thing I'm in recovery (CWM) and when I go through the flash from sdcard option, usually there were 3 options name 0/ and 2 others, however since I pushed the sdcard folder to /sdcard/ I get a 0/ at the top of the list which is where I would usually go but then underneath that I get all the folders I pushed! Is there any way to sort this out? I could attach pictures at some point for those of you who find it hard to picture what I'm describing Thanks in advance for any help!
Edit: just to add a couple of other things, my NANdroid had a checksum error so I cannot revert to stock without having to manually flash it which I cannot do at the moment due to a lack of WiFi, is there any way to sort this out? And the other thing was that for some reason sdcard cannot be unmounted at all in cwm, is it meant to be like that or am I missing something? Afaik its supposed to toggle.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Hello all, Im caught in a pickle.
I decided to test out a new ROM and wandered off to the "mounts and storage" option while in ClockworkMod Recovery v6.0.2.3. I've regrettably went ahead and performed the format /sdcard /system /data /cache /sdcard option and now i am unable to instal a custom ROM ... for my computer doesnt recognize the device. elp would be greatly appreciated!
Hope i have provided enough information. Any h
I did something similar with my nexus 7. Get the nexus toolkit and you'll have to reflash back to stock then re root
Sent from my Nexus 4 using xda premium
So I've recently run into a similar problem, except I had this problem BEFORE, then performed the format /sdcard /system /data /cache /sdcard option in cwm in order to correct it, as I thought I did a bad flash. I tried flashing stock but the problem persisted. How would one use the nexus toolkit if the nexus isn't recognized properly by the computer in the first place?
does fastboot still work and get recognized with PC ?
Absent Crysis said:
So I've recently run into a similar problem, except I had this problem BEFORE, then performed the format /sdcard /system /data /cache /sdcard option in cwm in order to correct it, as I thought I did a bad flash. I tried flashing stock but the problem persisted. How would one use the nexus toolkit if the nexus isn't recognized properly by the computer in the first place?
Click to expand...
Click to collapse
Did you use a toolkit when you tried to flash stock before? I would suggest not relying on a toolkit and handle this manually.
If you can get into your bootloader you can flash the stock images using fastboot. Efrant has a great guide on how to do that... http://forum.xda-developers.com/showthread.php?p=34552123
Edit...There is a second option I forgot to mention.
I use TWRP and I know I can do this so you might (should?) be able to do this using CWM as well (someone who uses CWM please correct me if I'm wrong).
If you don't want to go right back to stock as I suggested above and you can boot into a custom recovery, you can push a nandroid backup if you've got one or a custom ROM .zip using adb commands from your computer. Once the nandroid or zip is copied to your phone you can install it using the custom recovery.
Sent from my Nexus 4 using xda app-developers app
i deleted my rom so my nexus 4 just boots up and google image loads how do i install back my stock rom and also usb connection is also not possible as it does load any rom please help me
Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4
spaceman860 said:
Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4
Click to expand...
Click to collapse
can you explain indetail since im just a beginner
How did you root your phone did you install the drivers on your computer or did you use a toolkit
Sent from my Nexus 4
sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
Do you have a computer? You said something about usb support. You need to plug your usb cord into the computer and connect your nexus 4. It gets a lot more complicated in the next few steps so let me know if you can plug in your nexus 4.
sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).
Read this thread - http://forum.xda-developers.com/showthread.php?t=2010312
how to push rom file inside the intenal momery
kbeezie said:
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).
Click to expand...
Click to collapse
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive
sum93 said:
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive
Click to expand...
Click to collapse
This is why you shouldn't use toolkits without knowing the process behind it read this guide it will show you how to fix it
http://forum.xda-developers.com/showthread.php?t=2010312
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Sent from my Nexus 4