Hey Guys,
So I've been playing around with SDK using adb commands.
I been successful replacing stock ROM with a custom ROM.
Rooting and Unrooting.
Semi-bricking and getting it back.
Extracting a ROM file from an RUU and flashing it successfully.
Problem: the closest I can get to stock is a stock system with clockwork mod recovery flashed. Or Android system 3e recovery with the Superuser app installed on the system.
I've read posts that say to mount the system/ folder using
mount /system, mount -o remount, rw system/ , etc
all give me permission denied when I: rm /system/app/Superuser.apk
I've read that you must be recovery mode to mount system/ folder but when in recovery mode I cannot get connected with running: adb shell. error device not found.
So can anyone help me either remove Superuser.apk from my system/app folder or flash "Android recovery system 3e" without Superuser being installed?
I wish there was an RUU for Bell Mobility 1.34.666.5 floating around.
Thanks guys
HTC Vision
1.34.666.5
I'm driving and just skimmed through your post, but have you installed a pc10img through the booatloader? That is suppost to bring everything back to stock.
Sent from my HTC Vision using XDA Premium App
I did try using a PC10IMG.zip file using bootloader. But the only PC10IMG file that I could find was software version 1.34.666.1. I actually used this method to recover from a semi-brick state. (phone would not move past HTC boot screen)
I tried replacing the system.img file from the PC10IMG.zip that worked. But I believe that having S-ON prevented the new PC10IMG file to proceed. Which was probably a good thing as substituting the system.img file probably wasn't smart.
I've read that flash PC10IMG files with S-OFF is risky. If this is my best option. Can anyone give me a heads up as to what to double check for?
Thanks again for anyones input.
did you try this?http://forum.xda-developers.com/showthread.php?t=835971
Thanks for your reply.
Not sure this will help. If I had the files that corresponds to a
Bell Mobility 1.34.666.5 Stock Factory Bootloader / Recovery / ROM / Kernel I could get it no problem.
The hex editor I believe would be something new for me to try. But I believe this would only help if I am trying to apply software that is older then the software currently installed. This is not the case here.
Has anyone ever used clockwork mod recovery files to make a working PC10IMG.zip file that I could flash at startup using hboot?
I think you need to downgrade use the hex editor n flash the PC10Img
Sent from my SGH-T959 using XDA Premium App
Flashed my own PC10IMG.zip file with the new system.img file inserted. Only had to have S-OFF to do.
Unfortunately, this did not work. Phone boots to HTC screen and freezes.
Back to my original problem. Anyway to remove Clockwork recovery without installing Superuser.apk. or Anyway to uninstall Superuser.apk
Related
My device: HTC Desire, CM7 RC1, unrevoked root, s-on
As a Chinese mainland user, I need to edit hosts to access certain websites like twitter and wordpress.(And because it seems that cm7 have some problems with vpn and ssh.)
but i tried various method (root explorer, adb, terminal), the only result is that origin hosts file come back after reboot. none of those methods mention s-off, so do I need s-off?
someone said it can be done in recovery mode,but I don't find that function in RA recovery 2.0. someone said it must be done through flashing a zip which contains new hosts file. Are they right?
Thanks
From fastboot (not recovery) without s-off OR with s-off in recovery OR with s-off with most file browsers with phone booted normal.
HTC desire has read only where hosts file reside without s-off
Sent from my HTC Desire using XDA App
From fastboot is new to me and I highly doubt that is true. From recovery means you boot in to recovery and then use a adb shell. This should work.
If it's just about the add blocking I believe this is the flashabel zip.
place the host file you want in system/etc in this zip then flash from recovery, its unsigned so you will have to turn off verification in the options first.
In Recovery you'll have read/write access to /system, regardless of your phone being S-OFF or S-ON. S-OFF is basically the ability to have the same level of access as you would have in Recovery, even when booted.
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
I had the exact same problem but I re-did it all and the file is there with all the entries. However, none of the entries are being blocked. The file format is all right, it's one of the above. Also on CM7 RC1.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Just push it to the correct position after ROM install through Recovery. It'll be there.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Here's how I'd change my hosts file:
1. Boot in recovery, load up adb shell and mount both system and sdcard partitions.
2. Push the hosts file in your sdcard.
3. Remove the old hosts file (and check with ls).
4. Copy the new hosts file (and check with ls).
5. Reboot phone.
6. ???????
7. PROFIT
My phone is rooted, Super User is running for ROM manager. I get an error every time i click "Flash ClockwordMod Recovery" HTC G2 is clicked, then i get the error "An error occured while flashing your recovery"
Help please, Im rooted and SU is running fine. I also have busybox.. not that it has anything to do with it. I just want to install a custom rom. thanks
i am having the exact same problem as well. could it be a problem with the server side?
Could be the download.
You could always use the manual method.
I all ready have CWM 3.0.0.5 installed i've just gone in to rom manager and tried to flash and older recovery and I'm getting the same error. There is a manual method, trying to find it now and will post here when I do
Sent from my HTC Vision using XDA App
Same issue, if someone can post the latest recovery file. It lives somewhere in the clockworkmod directory on the sd card. If you can also tell us what the directory is, we should be able to place the recovery in the same directory. That way rom manager will not try to download. thanks.
OK download recovery image from here http://mrcellphoneunlocker.com/recovery.img you will need to do this from your pc not your phone then transfer to your sdcard don't put in a file though and rename to recovery.img
I then open termianl emulator and type in
su
flash_image recovery /sdcard/recovery.img
I don't think this version of CWM is up todays though
Sent from my HTC Vision using XDA App
Quoted my self instead of editing
Thanks, but to get latest recovery image, can you do as I suggest and get the recovery image from the clockword mod directory on the sd card? If can also tell us what the full directory path is, we can 'trick' rom manager into not needing to download. Thanks.
I
saquib said:
Thanks, but to get latest recovery image, can you do as I suggest and get the recovery image from the clockword mod directory on the sd card? If can also tell us what the full directory path is, we can 'trick' rom manager into not needing to download. Thanks.
Click to expand...
Click to collapse
I've looked but I can't find it. I've searched the forums and I can't find a direct download for the latest recovery ill keep looking though. If not I'm sure I have a copy on my pc.
Sent from my HTC Vision using XDA App
Recoveries are here:
http://mirror.kanged.net/recoveries/
Anyone got the flash_image script?
saquib said:
Anyone got the flash_image script?
Click to expand...
Click to collapse
flash_image is a binary not a script, in any case you can get it here:
http://forum.xda-developers.com/showthread.php?t=902493
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
I been trying every single tutorial I found here and always end on the failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system. I can't pass this issue. Only been able to shell root but nothing else seems to work. Im only looking to be able to root to put a new ROM on it since I have the HBOOT 1.02.0000 and seems that cant be downgraded or set to S-OFF. Any helps on how to pass the failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system problem? Thanks.
Update - I was able to root by downgrading to 2.1. Sadly theres no way to turn off the S-OFF but I been able to install a ROM. After I get into 2.1upgrade1 I was able to push all the files needed to enter into recovery.
Update 2- I unlock the bootloader so is the same as S-OFF and flash permantly the clockwork recovery. This can be closed.
Hi Everyone,
I have 2 HTC Evo 4g with 2 different problems:->
Problem on first phone:
I root the HTC Evo 4G using the method given by the link below:
http://themikmik.com/showthread.php...-18-HBOOT-with-HTCDev-com-No-More-Watermark!-
Further i installed costum ROM and it worked good. I was wanting to edit the system folder and replace the camera apk but i see that the SYStem folder is not editable.
Is there any method to access and modify the system files.
Problem with second phone:
While rooting the phone using the link above in the step 10. which mentions:
10)Using the previously downloaded Froyo PC36IMG.zip from the OP, rename to "PC36IMG.zip", and place on root of SD Card. Reboot into Bootloader, and follow the prompts to update device (Notice in the below picture that the watermark shows as "LOCKED" again).
The file (PC36IMG.zip) worked perfect on the first phone but on the second it is not able to recognize the PC36IMG.zip. Kindly help me with this as the rooting process is incomplete.
Awaiting reply. Thanks in advance...
1st problem, you need to Mount your system as writable.
2nd problem, is the phone S-OFF?
Sent from the future
@ 1st problem How do we mount the phone system to be writable?? If there is any steps to be followed:
@2nd problem the phone is not S-OFF.. it says S-ON. Usually after the PC36IMG.zip is processed the Watermark ***Locked*** disappears along with the S-ON.
vikasraj said:
@ 1st problem How do we mount the phone system to be writable?? If there is any steps to be followed:
@2nd problem the phone is not S-OFF.. it says S-ON. Usually after the PC36IMG.zip is processed the Watermark ***Locked*** disappears along with the S-ON.
Click to expand...
Click to collapse
Download a file explorer such as es file manager and go into root settings and mount system as writable. And the phone won't read certain PC36IMG's without S-OFF.
Sent from the future
death-by-soap said:
Download a file explorer such as es file manager and go into root settings and mount system as writable. And the phone won't read certain PC36IMG's without S-OFF.
Sent from the future
Click to expand...
Click to collapse
You need to mount the system as writable like he said with a file explorer.
You do not need to be S-OFF to run a PC36IMG.zip file that is officially from HTC, as that root method does demonstrate, although it is much easier. Notice it did work on your first phone. That root method downgrades your operating system to an earlier version, because those are the only ones that you can S-OFF. The root method downgrades your misc partition to the original (Engineering) one, so that the phone will recognize all PC36IMG.zip files from HTC as being a later version than itself (so it thinks), and allow you to update (so it thinks) to a later version, but you're actually downgrading. The phone will not let you downgrade (while not rooted) unless it is S-OFF or tricked, which is the reason why it rejects the PC36IMG.zip file from HTC (It's trying to prevent you from downgrading). Obviously, something went wrong on the second phone during that rooting tutorial. Was the bootloader previously unlocked, and did the second phone have superuser permissions?
Also, depending on what you want to do with the phone (like writing to the system partition), you only need S-OFF if you plan on flashing radios, splash screens, or Hboots (which I especially don't recommend). Everything else, you could just unlock the bootloader and just follow the tutorial up until the point where you flash the superuser app (step 4). It gets kind of complicated trying to get it S-OFF as well. Some people have more difficulty that others.
Might be more helpful to post in that other thread if you have issues with that method . . . I'm just sayin' .
Also, your sdcard MUST be formatted to FAT32 for the bootloader to recognize any PC....zip files
Sent from my PG06100 using xda premium
@All i am going through the rooting process again... The phone was bootloader unlocked from htcdev.com... Will format the sdcard and update you all again..
vikasraj said:
Hi Everyone,
I have 2 HTC Evo 4g with 2 different problems:->
Problem on first phone:
I root the HTC Evo 4G using the method given by the link below:
http://themikmik.com/showthread.php...-18-HBOOT-with-HTCDev-com-No-More-Watermark!-
Further i installed costum ROM and it worked good. I was wanting to edit the system folder and replace the camera apk but i see that the SYStem folder is not editable.
Is there any method to access and modify the system files.
Problem with second phone:
While rooting the phone using the link above in the step 10. which mentions:
10)Using the previously downloaded Froyo PC36IMG.zip from the OP, rename to "PC36IMG.zip", and place on root of SD Card. Reboot into Bootloader, and follow the prompts to update device (Notice in the below picture that the watermark shows as "LOCKED" again).
The file (PC36IMG.zip) worked perfect on the first phone but on the second it is not able to recognize the PC36IMG.zip. Kindly help me with this as the rooting process is incomplete.
Awaiting reply. Thanks in advance...
Click to expand...
Click to collapse
You should donate one of your evos to the dev asking for an evo donor to work on 4G... His thread is forum.xda-developers.com/showthread.php?t=2109646 there
Sent from my PC36100 using xda app-developers app