Related
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
Hi everyone!
I am trying to make Ad Free from the Market work but it won't. My HTC Desire is rooted with unrevoked (so, not S-OFF, but I've read that it's not necessary. Is it?).
I have tried two different things:
1) Run the program WITHOUT the symlink option enabled. The phone automatically reboots and nothing happens, adds are still shown in all the apps.
2) Run the program WITH the symlink option enabled. The program seems to work and a message appears saying that my phone should now be add free. But, in fact, it is not, adds are still visible everywhere.
I have been looking for solutions in this forum and in Google but I have seen a lot of different procedures suggested by users and I am not sure it would be safe for the phone to try them one by one.
It would be great if someone has been in the same situation and could tell me how to solve my problem.
Thank you in advance.
You either have to be s-off in order for the app to place the modified "hosts" file in /system/etc/ Otherwise you have to have the file symlinked to a specific place on the data-position(this is the place the app places the "hosts" file if you check the option for symlink.)
You can also just push the modified hosts file from recovery
edit: my suggestion is to s-off it, as it makes everything so much easier, and if you screw something up, you can almost always recover your phone without running a ruu.
mortenmhp said:
You can also just push the modified hosts file from recovery
Click to expand...
Click to collapse
I have been trying to do that before opening this thread but I didin't manage to do it successfully. Could you please help me through the process?
Anyway, how could I do the "you have to have the file symlinked to a specific place on the data-position(this is the place the app places the "hosts" file if you check the option for symlink.)" part?
You need to edit the ROM to symlink the hosts file to the /data partition
EddyOS said:
You need to edit the ROM to symlink the hosts file to the /data partition
Click to expand...
Click to collapse
Is there any place where I can get info to do that? I am kind of inexperienced...
don't do it just push the goddamn file in recovery or for god sake please just run s-off.
If you want help pushing it, pm me.
edit: host file added
You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App
Have been suggested(twice by me), but as you might get from reading his replies, he doesn't want to do that. I guided him through pushing the file though, so the problem have been resolved.
Willem Mulder said:
You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
With some help from mortenmhp by private messaging I got it to work without s-off. Anyway, I tried alfarev this morning and it detects my phone but gets stuck in the next step...
By the moment is one thing I don't need, but it would be fine to know what the problem is...
Willem Mulder said:
You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
S-OFF doesn't work with all kinds of desire phones ...
some PVT-4 (like mine) cant be S-OFF u may brick it trying so just push files its safer using terminal emulator from market or using ADB
this may help u with commands http://forum.xda-developers.com/showthread.php?t=688820
Well, in alfarev web site they say their software is compatible with PTV4 HTC Desire, but anyway mine is PTV3, so the problem can't be that.
Xgeda said:
S-OFF doesn't work with all kinds of desire phones ...
some PVT-4 (like mine) cant be S-OFF u may brick it trying so just push files its safer using terminal emulator from market or using ADB
this may help u with commands http://forum.xda-developers.com/showthread.php?t=688820
Click to expand...
Click to collapse
Yes it does, or at least it works with all gsm ones for now. From their website:
Supported devices:
HTC Desire GSM (Bravo), all hardware models (PVT4 too)
Click to expand...
Click to collapse
Also no you cannot use terminal emulator to push files, and you most certainly cannot use it to manage files on the /system partition without s-off.
Dj Telo: the most common problems with alpharev is connected to the computer the software is run on. Are you using an emulator to boot the disk, or are you actually booting it?
If the first one is the case, you will need to burn the image and boot it, however, if that doesn't work, you might need to try another computer. Just borrow one, as it is a onetime thing, and it only takes a couple of minutes.
Also make sure your current rom is not using d2sd, d2ext or something similar, as the tool uses the data-partition and may not work with the ext-partition,
I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?
MatDrOiD said:
I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?
Click to expand...
Click to collapse
Well as already explained the relevant file (/system/etc/hosts) is placed on the system partition(obviously). And as such it cannot be edited while the system is booted without s-off, so an app won't be able to do so.
So unless the system has been edited to load the file from the data-partition(as in the symlink option i referred to earlier) yes you do indeed need s-off to use the app. However as you might get from actually reading through the thread, the actual problem has been resolved, and currently he is just trying to gain s-off.
mortenmhp said:
If the first one is the case, you will need to burn the image and boot it, however, if that doesn't work, you might need to try another computer. Just borrow one, as it is a onetime thing, and it only takes a couple of minutes.
Click to expand...
Click to collapse
I did burn a CD but it did not work. I will borrow a computer, as you suggest. There's a busy week for me coming but I'll try that afterwards. I'll insist on this thread in case I can't succeed.
MatDrOiD said:
I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?
Click to expand...
Click to collapse
I did exactly what you say, but adds would still appear. The IP used was the default one.
Anyway, I already managed to make it work.
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks
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
So, i don't want any custom ROM or anything, i just need to access some app's hidden files (Steam), more specifically, i need to edit some XML files that are stuck somewhere in /data.
KingoRoot doesn't work, the APK just says Root Failed, and tells me to try the desktop variant, the desktop variant doesn't work either.
I would've rooted it, but i don't want to unlock the bootloader and lose my files. So i am at a bit of a loss here.