Related
**THE USUAL WARNINGS APPLY**
1/11/11: Updated CWR to 3.0.0.5. Now installs properly through ROM Manager. Nandroid backup works, don't know about restore. Not sure if partition wiping is working I would assume it is. Flashable zips from SD card are working, tested with Quickie OC kernel (HIGHLY RECOMMEND!!!). Attached the CWR 3.0.0.5 image to this post, it is not a flashable zip just the image file zipped. So we have some real progress. w00t!!!
1/2/11: Looks like CWR has been released for NC. I didn't see it up see here you go. Easiest way to get it installed is by downloading ROM Manager in the market and flashing it through the apk. Attached is the .zip, I believe you just rename it "update.zip" and put it on the root of your SD card. Then reboot into recovery. Again your best bet is to use ROM Manager. Link to website: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Awesome, will try this later today, thanks for bringing it to attention
Afraid i cant thank you from my nook, but rest assured i eil soon
install failed here, too.
Failed for me too....
Sent from my Nooted Rook XDA App
Not ready for prime time yet. You need to install uRecRam to use it. give it a day put so for out to be automated. At least that is where it was last night when I went to sleep.
Sent from my rooted droid x
As per the previous post. This is not ready yet and could result in a bricked NC.
http://nookdevs.com/NookColor:Building_Clockwork_Recovery
Unable to post url's
Also I don't think it is backing up all partitions.
Sent from my rooted droid x
Failed me too. Started the process and then failed. Looks like it is close though. Pretty exciting.
WOW, this is great news. Seems like real soon we will be able to make backups.
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Here are the steps to actually making this work if you are the adventurous type. This may brick your device blah blah. I am not responsible, etc. You should only attempt this if you genuinely understand the commands you are performing.
Make sure neither /media or /sdcard are mounted in your OS!
Save this:
http://koush.tandtgaming.com/test/clockwork-b3-nook-uRecRam
adb push clockwork-b3-nook-uRecRam /media/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /system/boot/uRecRam > /system/boot/uRecRam.bak
cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Now do the three fingered salute to get into CWM Recovery. VolUp/Down are up/down, respectively. The Nook/home button is Select and the power button is Back.
@Mistar Muffin
worked for me
starkruzr said:
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Click to expand...
Click to collapse
That would be awesome!
Great job,
I tried to compile a scrip with the following but it doesn't work if i put it in a batch file but it works if I run it from DOS. Go figure...
Code:
adb push clockwork-b3-nook-uRecRam /media/
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mkdir /system/boot/
adb shell mount -t vfat /dev/block/mmcblk0p1 /system/boot
adb shell "cat /system/boot/uRecRam > /system/boot/uRecRam.bak"
adb shell "cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam"
adb shell umount /system/boot
adb shell rmdir /system/boot
I will work on the batch for the community to run so it make it easy for noobs...no ETA
Would installing this hose the ability to factory reset (the 8 failed boots/bootcnt method)?
Flashed and it works.
Yes you will loose that ability in it's current state.
I do not recommend using this until it has the capability to backup all of your data. At this point an error can still leave you with no return path, you have been warned!
Edit: Scratch that. I see what I did.
Even if it might not be wise for most to use this yet, very happy to see this available. Looking forward to nandroid . . .
I saw that the nook color comes up in rom manager, does this mean we don't need to install that other file uRecRam.
Sent from my LogicPD Zoom2 using XDA App
I want to unroot my phone, obviously i deleted everything needed to go back to stock so i was hoping someone could tell me the best method.
I want to unroot it because I have a feeling my phone has some sort of defect a ota/root won't fix. IT will NOT download MMS messages at all, it was working two weeks ago but since all download messages fail, my moms blackberry and sisters iphone work fine but mine will not.
My phone was rooted a long time ago, like in october but I never installed any rom's or anyhting, it has superuser and clockworkmod/rom manger. Awhile ago I tried to install things on rom manager but never noticed any difference. I also did the fix permissions thing.
Just wondering if its safe to use http://forum.xda-developers.com/showthread.php?t=867648
and if i decide to just keep the phone how would i go about updating the phone to newer roms?
The easiest way is to odin the DL09 stock rom to your phone. It will install the OTA to the latest firmware after you boot up.
There is also a thread started by Adrynalyne that has the EA28 and ED01 update.zips, do you don't have to OTA the updates (which takes forever to download). The thread is about how to get the most updated radio.
Of course, using Odin will wipe everything off your phone.
P.S. Rom manager is borked on our phones, so don't use it
Sent from my SCH-I500 using XDA Premium App
Yes it is safe to use that DL01 Odin file, that is what I use. I would do that, then see if MMS works.
You could do it manually through adb:
adb shell
su (its going to ask you for permission on your phone so hit allow)
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
rm /system/bin/su
rm /system/bin/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit
OhioYJ said:
Yes it is safe to use that DL01 Odin file, that is what I use. I would do that, then see if MMS works.
Click to expand...
Click to collapse
I think you mean DI01 or DL09. There is no DL01
--THIS IS FOR THE VERIZON DROID RAZR--
Go here for the test files for international version: http://forum.xda-developers.com/showpost.php?p=19900530&postcount=11
I have enough confirmations that I can now confirm this is working, However the on screen controls appear not to be launching currently, but webtop launches.
What this mod does:
It removes the device ID string check from PortalApp, and enables the webtop option in DockService. Replacing these two apk files effectively allows the webtop to launch without proprietary hardware.
Click to expand...
Click to collapse
What this means to you:
Webtop mode over any HDMI without an expensive dock.
Click to expand...
Click to collapse
Installation:
Method 1: Flashable ZIP
Flash THIS zip.
Click to expand...
Click to collapse
Method 2: ADB install
Download the attached apk files.
First Get the files to the device and remount /system as rw:
Code:
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o remount,rw /system
Backup the original files:
Code:
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
Copy the modded files over fix permissions and reboot:
Code:
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
chmod 644 /system/app/DockService.apk
chmod 644 /system/app/PortalApp.apk
reboot
Click to expand...
Click to collapse
Appreciate my work? Buy Me a Beer:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
love you.
10<3
ah jeeze... just noticed it's for the Verizon RAZR, will it by any chance work on a GSM version?
Just installed it, and on the bionic after connecting to the tv, the phone became a mouse. Here the screen goes black and doesn't respond to touch.
You on a Verizon device? Did the webtop or dock option list come up at all?
Yes, Verizon phone. Everything comes up great on the tv, The webtop option comes up on the list to choise from, when i hit webtop the tv comes on, the phone goes black, but no control of pointer at all.
That's a good sign at least. Did you install via the flash method or the adb method?
Flash. I flashed BigDX ics theme yesterday, maybe it has something to do with it, so restoring a nandroid backup of before and will flash the webtop hack again.
---------- Post added at 10:41 PM ---------- Previous post was at 10:12 PM ----------
Nope. Same. Phone screen goes black, no control of pointer.
That sucks stevessvt, maybe try installing via adb instead and see what happens.
I really want to try it on my GSM RAZR... Don't know what the difference would be. Anyone...?
EDIT:
My stock DockService.apk is 109kb - odex is 173kb, the PortalApp.apk is 1.21mb - odex is 591kb
Can anyone confirm the Verizon file sizes for me?
opensourcefan said:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
Click to expand...
Click to collapse
Try this one with method 2 for the international version: http://www.cheatersedge.org/android/RazrWebtopMod.rar
I'll try to look into the on screen mouse/keyboard issue. It may be slow going seeing as I don't actually have one of these devices to test on.
Sent from my SGH-I777 using XDA App
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
oh now i just got mad since the OTA i lost root so no Webtop for me. i don't wanna loose the OTA so i'm just gonna wait for somebody to find a way to get root again.. since i don't know how to do that.
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You can change the permissions with Root Explorer: Long hold on each file, and set RW- R-- R--, and then reboot, that ought to go it.
As for the command for the adb method it might be "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" Where "/dev/block/mtdblock3" is replaced with the actual block device for /system. You can check this by just typing "mount" and looking at the entry for /system.
only Verizon? not for EU GSM devices?
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
shady_lanem said:
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
Click to expand...
Click to collapse
you have a Vaarizon?
9100_it said:
you have a Vaarizon?
Click to expand...
Click to collapse
Download link for international version is posted on top of this page
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You have to do
su
To login as root before.
Sent from my awsome Motorola RAZR
Perfect!
I've asked to teach me how to make it, but it's the same. The important thing is that it is available, even if my curiosity reaches an unknown level.
Thanks!
P.S.: Please, edit the thread title to reflect this section rules!
Hi all,
I just did a System Level root here http://forum.xda-developers.com/showthread.php?t=1505062 and it was successful. It didn't add flash counters which is why I chose this method.
I was able to install Superuser and Titanium Backup.
However I need to return the phone for exchange because this one is currently defective (charger issues).
Now I'm trying to unroot and restore to defaults. First I uninstall Titanium backup which was easy. Then now I can't UNinstall Superuser.apk. I look for guides and found that I need to download Terminal Emulator, enable root then run these commands:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
However, when I run this it gives me this error:
Code:
#rm -r /system app Superuser.apk
rm failed for Superuser.apk, Read-only file system
So yeah, it won't delete and I can't return it with Superuser installed in there
Is there a different method to just download the official restore .tar file from Samsung and just restore it that way using odin. If there is, where can I find that .tar file?
Please help, I only have a few hours before I can return this
Thanks!
Just an update (I'll just reply to myself since I found a solution)
I was able to delete the Superuser.apk,busybox,su by following this guide: http://forum.xda-developers.com/showpost.php?p=7386761&postcount=2
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
However my device is still rooted. Although Bestbuy/AT&T might not detect it, Samsung probably will .. so warranty can still be voided.
Anyway, is there way to unroot easily?
I'm guessing that using the official .tar file from samsung ... will fix this.
Where can I find that file?
THanks again!
How is Samsung going to link your Best Buy return back to you? Since you are within 30 days, your return will be fine. I think the concern is the flash counter when sending in for warranty repairs after the 30 day return window.
jpeg42 said:
How is Samsung going to link your Best Buy return back to you? Since you are within 30 days, your return will be fine. I think the concern is the flash counter when sending in for warranty repairs after the 30 day return window.
Click to expand...
Click to collapse
Thanks! Point taken. But yup .. I guess I was talking about future issues when I will have to deal with Samsung (hopefully not).
So .. is there a restore .tar file that samsung provides?
Thanks again.
Not sure if it will work but i would assume just flashing the stock att tar would remove root
jdphilly said:
Not sure if it will work but i would assume just flashing the stock att tar would remove root
Click to expand...
Click to collapse
Or just do a reset under settings>Privacy.
droidal said:
Or just do a reset under settings>Privacy.
Click to expand...
Click to collapse
will that actually "unroot" it?
spec2323 said:
will that actually "unroot" it?
Click to expand...
Click to collapse
No. 2 ways to unroot. Remount r/w, and remove said binaries, or flash system.img with stock the same way you flashed the rooted system.img.
lastdeadmouse said:
No. 2 ways to unroot. Remount r/w, and remove said binaries, or flash system.img with stock the same way you flashed the rooted system.img.
Click to expand...
Click to collapse
do you have a link for a real/safe ATT stock system.img we can flash?
http://forum.xda-developers.com/showthread.php?t=1506330
There is a stock system here. I'm pretty sure since it is the stock signed kernal it shouldn't trip the counter either. Maybe someone with an already tripped counter can try it and report.
thanks alot
keplenk said:
Just an update (I'll just reply to myself since I found a solution)
I was able to delete the Superuser.apk,busybox,su by following this guide: http://forum.xda-developers.com/showpost.php?p=7386761&postcount=2
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
However my device is still rooted. Although Bestbuy/AT&T might not detect it, Samsung probably will .. so warranty can still be voided.
Anyway, is there way to unroot easily?
I'm guessing that using the official .tar file from samsung ... will fix this.
Where can I find that file?
THanks again!
Click to expand...
Click to collapse
it worked for me.. thanks a lot
Another way to return to stock is with Kies. I have used this method a couple of times with no problems. Once Kies wouldn't recognize my note, so I had to flash a stock ics rom from the super everything thread, then hook it up so kies would recognize. There is also a flash counter reset in the super everything if you are worried about that.
Did you get the insurance from Best Buy? Or just worried about warranty from Samsung? If you have BB insurance, just run over the thing with your car before taking it back. That's what I plan to do. Just before my contract is up I always return for a new phone. They can't check the flash counter if it is snapped in half
Sanjay Kumar
I will say a simple method to uninstall superuser.
First you root your phone again
Download clean master which is free.
Now open it. And allow superuser permission. Now open app manager.
It shows uninstall-backup -move options.
Select pre installed apps . Click superuser and click uninstall.
Hurray u have uninstalled superuser . My what's app number 7401660083. Message me I you have any doubt:good:
problem..
hello, i have i9505 phone and i had superuser with error. i tried to restore with odin just as you said, and i put pit file that was on the folder. i put pda file too. it was too long time to install and i close the connection. after that my phone remains to samsung logo. what can i do?pls help
ok, i think i played with this too much and im stuck!
have a droid xt912, was running ICS, i rooted it, saved root via voodoo, applied the JB Leak, recovered root, and installed safestrap 3.11
i went into safe strap, made a system backup, and then F'ed up... i forgot to make a new rom slot and switch to it, so i cleared out the stock system folder, and attempted to install a rom... it didnt boot, but i could still get back into safe strap...
i recovered the stock system, but it didnt fully recover.. it gets past the boot logo, makes the boot sound but doesnt boot?
i should of stopped there but didnt, and i reapplied the JB leak... now safe strap is gone, and phone doesnt boot correctly...
i can turn it on, i can still connect via ADB, and even access shell root...
figured i messed it up enough... lol... and should probably stop and look around, found the droid utility 1.82, but thats only if i was still on ICS, since my last install was JB, probably dont want to try and install anything ICS related...
looking for ideas...
ok, i was able to do wipes via stock recovery, and it now brings back up safe strap 3.11, stock rom still will not boot, but im installing a custom rom right now...
hope, i guess now that this is kinda back, how do i fix my stock rom?
You could try and get hold of a system back up from somebody running JB restore that back to stock slot..just an idea
Sent from my XT910 using xda app-developers app
This must be my issue
NOTE: - Do NOT make a backup while su is protected by VooDoo. This will cause an incomplete restore of your system and result in booting to a black screen. Remove the su backup from within VooDoo prior to creating any backup.
Going to try the following:
http://www.droidrzr.com/index.php/topic/7701-how-to-recover-the-stock-slot-on-xt912-running-jb-ota/
Sent from my MB886 using xda premium
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
This helped me out not being by a computer. Downloaded the backup. And all is good
Sent from my DROID RAZR using xda premium
Helped me recover OTA JB 98.72.16.XT912
yoyurik said:
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
Click to expand...
Click to collapse
After receiving the latest JB soak, I immediately made a safestrap 3.11 backup while root was protected with VooDoo. After messing with some system files, I decided to just do a restore back to stock. The phone booted up and hung at a black screen. I was able to restore the backup to another slot and boot from there, but not unto the stock slot.
So I tried using the above instructions using ADB to restore /system while excluding the su-backup file but got permission errors. So I decided to use 7-Zip, open system.ext3.win and delete su-backup file from there. Then copied the "new" modified backup folder to external SD, boot into safestrap 3.11 and restore that backup into the stock slot. I was pleasantly surprised that it worked!!! And I didn't lose root either!
This will teach me never to do a safestrap backup while root is protected with VooDoo.
Thank you so much for the idea! I just implemented it a bit differently when ADB didn't cooperate.