[Q] Can't root Mytouch 3G Slide - myTouch 3G Slide Q&A, Help & Troubleshooting

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.

Related

[Q] Returning HTC Vision to Stock

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

Htc ruu option

Has anyone thought, that when you run the RUU, it does make a temp folder for the contents..that maybe you can root the device from the RUU files and give the binaries of superuser to the OS?
Such as go to the folder, read the files needed, add the superuser binaries and apk, then continue with the ruu process which will auto apply the root?
I don't think that would work, I think if you mess with any of the files it breaks the signature and won't load on an s-on device. I think others have tried some variations of that and no dice.
sent from my locked EVO via tapatalk

phone will not boot into CWM

Hey, I flashed CWM using the SGS3 Snapdragon ToolKit and everything seemed to go fine, Odin restarted the phone after the flash was completed. I was going to install a custom ROM and tried booting into CWM and the phone would only boot into the stock recovery. Not sure what I did wrong as I followed the directions in the ToolKit application. Anyone have a clue why the phone will still only load into the stock recovery?
Happened to me as well. I managed to sort it out by installing CWM and then renaming /system/recovery-from-boot.p to recovery-from-boot.p-bak (or whatever). I read somewhere here that that script would launch on reboot and overwrite the recovery with stock.
Good luck!
I see the file there, but it won't let me edit the file name. I went back and rooted the phone just to make sure that I would have permission to edit the file name and it still won't let me. I'm trying to use ES file explorer to do it, and I have the root explorer option enabled.
Does that file explorer app have an option to flip between read-only and read/write mode? I used Root Explorer - which defaults to read-only - and switched to read-write for the rename.

[Q] Problem with superuser/superSU/rooting

This being my first post a HI EVERYBODY is in order.
On with the show.
So, I managed to unlock my bootloader via htcdev website, i slapped on the cwm recovery and managed to put a custom rom on my cell.
The rom in question is the jellyking, works fine, everything is great.
PROBLEM:
although ive tried several cm10 roms i liked jellyking the most but on all of them i had troubles getting root.
what happens is that i download es file manager, set it to give me root and mount system as RW, popup says that the preinstalled (with rom) superuser app granted those rights and that everything should be superb, but I couldnt copy files from my sd to lets say /system/media (wanted to change my bootanim) it says file copy failed, only once i did manage to copy a file but i dont know how.
The question:
when i put a custom rom, do i need to reapply the famous root.zip or maybe install busybox as my first app or maybe flash over the existing superuser app the superSU app which seems to update the root binaries sucessfully.
BOTTOM LINE:
What is the exact (if any) procedure that I need to follow to get perm root access (copy rights) to my own phone, each and every reboot.
Thanks in advance for all Your insights,
Humbly,
egr2lrn

[Q] Unable to modify the system files !!

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

Categories

Resources