My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?
http://forum.xda-developers.com/showthread.php?t=2745257
This may or may not help you lol hopefully it does though.
Sent from my HTC6525LVW using Tapatalk
mfungah said:
My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?
Click to expand...
Click to collapse
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked (if you can still see on the screen?)
Then you may do "fastboot oem writesecureflag 3" to put S-ON
andybones said:
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
Click to expand...
Click to collapse
So at the moment I need to figure out how to obtain su, at least shell then. Seeing as I just flashed the ruu and the LCD is completely black/blank, do you have any suggestions?
And thank you very much for the detailed reply step by step.
Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.
mfungah said:
Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.
Click to expand...
Click to collapse
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.
andybones said:
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.
Click to expand...
Click to collapse
That's correct andy....The ruu I made does have su. I'm not sure how he would be able to answer the su prompts for adb access though. Maybe hdmi out?
For what it's worth this device is pretty hard to truly brick. I tried once to help brick one and even with bootloader wiped it still went straight to ruu mode.
Sent from my SM-T320 using Tapatalk
I suppose that adb debugging isn't enabled by default, I'm booted up but that's about it. Any specific information that could be helpful or as I'm assuming, theres nothing much i can do except fastboot to S-ON. I mean it is getting sent in, I just really hope it gets accepted.
He got a new device for him all sorted out. I really appreciate your time and help, I did find your step by step very easy to understand.
Related
Ok friend just got his new one x on att just moments ago.. wanted it rooted.. so i did i think.
installed Rom toolbox and tried to add that Twrp or what ever its caled custoer recovery (ot Clockwork mod)
Then selected boot to recover and its now stuck on a boot loader screen and will no go anwehere other than that pretty mch,, if i reboot it has the htc logo a warning about this beinga dev and then back to bootloader witch says s-on tampered and locked..
Im trying everyting and i got my boot loader key thing but i cant submit it to htc cause im guessing att wants it to sstay locked..
I cannot boot into the rom or anything i have a downloaded folder of http://www.mediafire.com/?d41k2x8sm9gesup
and tried to flash the fastboot cache still... notta..
What do i do to get out of this.. to unlock it and et back to root or even back to 1.85.. anything
Have you tried an ruu?
Sent from my One X using xda app-developers app
Mortland said:
Ok friend just got his new one x on att just moments ago.. wanted it rooted.. so i did i think.
installed Rom toolbox and tried to add that Twrp or what ever its caled custoer recovery (ot Clockwork mod)
Then selected boot to recover and its now stuck on a boot loader screen and will no go anwehere other than that pretty mch,, if i reboot it has the htc logo a warning about this beinga dev and then back to bootloader witch says s-on tampered and locked..
Im trying everyting and i got my boot loader key thing but i cant submit it to htc cause im guessing att wants it to sstay locked..
I cannot boot into the rom or anything i have a downloaded folder of http://www.mediafire.com/?d41k2x8sm9gesup
and tried to flash the fastboot cache still... notta..
What do i do to get out of this.. to unlock it and et back to root or even back to 1.85.. anything
Click to expand...
Click to collapse
Hold the power button until the phone shuts off, then try booting it up and see if it actually boots
EDIT: Just seen you did try to reboot...my bad. Like guy above me said try an RUU
after googling to death the only one i could find is a exe that needs to be dont via the phone being in the on working state, got any links for a ruu to flash?
The sticky at the top of the forum has the links:
http://forum.xda-developers.com/showthread.php?t=1671237
You can flash an RUU while in bootloader mode.
Your problem is that you didn't unlock the bootloader and you are running a third party recovery. The security "features" of the bootloader being locked and you being S-ON prevent the phone from booting.
Well you would have had to have rooted it first before installing a custom recovery like twrp.
To get back, you'll want to:
Download the RUU file from this link
http://forum.xda-developers.com/showthread.php?t=1670238
Download the HTC driver from this link
HTCDriver3.0.0.007.exehttp://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Install the HTC driver and restart your computer
Plug in your phone and run the Ruu.exe file
This will put your phone back to the way it was when you bought it.
Then, take some time and read the threads about rooting and installing twrp before trying again.
Also, try not to post questions in the Dev section.
z28james said:
The sticky at the top of the forum has the links:
http://forum.xda-developers.com/showthread.php?t=1671237
You can flash an RUU while in bootloader mode.
Your problem is that you didn't unlock the bootloader and you are running a third party recovery. The security "features" of the bootloader being locked and you being S-ON prevent the phone from booting.
Click to expand...
Click to collapse
Yea realized what i did after i did it.. I have a Thnderbolt on verizon and also had to s-off. I figured out where to get a ruu i think for the moment so ty lets hope lol
mod should probably move this one to q&a.
Sent from my One X using xda app-developers app
im following this http://forum.xda-developers.com/show...709296&page=38
and so i did this and it worked ok i think on the first try.... like a idiot i attempted to flash a recovry wit s-on and the bootloader lockd so i got stuck in a bootloader loop and then was able to ruu back to 1.85 on att.. now i do excatly the instructions and when i get to
adb shell ls -l /data/local.prop
i get "no such file or directory"
and i have changed dates up the wazoo forwards backwards back to the current, reset the phone by factory wipe and reset via bootloader.. im stuck
also if it matters i get no such file or dir on
adb shell rm /data/data/com.redbend.vdmc/lib/libvd
and link failed file exists on
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
Mortland said:
im following this http://forum.xda-developers.com/show...709296&page=38
and so i did this and it worked ok i think on the first try.... like a idiot i attempted to flash a recovry wit s-on and the bootloader lockd so i got stuck in a bootloader loop and then was able to ruu back to 1.85 on att.. now i do excatly the instructions and when i get to
adb shell ls -l /data/local.prop
i get "no such file or directory"
and i have changed dates up the wazoo forwards backwards back to the current, reset the phone by factory wipe and reset via bootloader.. im stuck
also if it matters i get no such file or dir on
adb shell rm /data/data/com.redbend.vdmc/lib/libvd
and link failed file exists on
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
Click to expand...
Click to collapse
First, you double posted in the Dev section,, if you browse this forum you'll quickly realize that there a no other questions in here..... As such your thread is going to be moved, and you'll probably be flamed more than I'm flaming you now.
Second, if your bootloader was locked how did you try to flash TWRP, If you're still locked are you tampered? Just flash a stock RUU. If 1.85 doesn't work flash a newer one, and then pray to god someone roots it.
Third, with the S-OFF ,, well I would like to know what this has to do with anything as this hasn't been achieved yet. You obviously did a ton of reading before you embarked on your noob flashing.
If you're locked and not tampered (which I doubt) just take your phone back to the store and give them some BS like your battery is bad and have them swap you phone out (if you're ATT).
EDIT: I re-read this. Ignore everything I said with the exception of you posting in the wrong forums. I see you don't even have a One X .... dude ... quit posting here and make a new thread
HydroSkillet said:
EDIT: I re-read this. Ignore everything I said with the exception of you posting in the wrong forums. I see you don't even have a One X .... dude ... quit posting here and make a new thread
Click to expand...
Click to collapse
He said he's trying to root/mod his friends One X (while he himself has a Thunderbolt). But yeah, its confusing.
---------- Post added at 09:27 AM ---------- Previous post was at 09:23 AM ----------
Mortland said:
installed Rom toolbox
Click to expand...
Click to collapse
AFAIK, there is no ROM Toolbox that works for this device. That was probably your biggest mistake. Don't install/flash/mod things willy-nilly before doing the proper research. Every Android device is rooted, S-Off etc. a bit (or very) differently. Lots has changed on HTC phones since the Thunderbolt. Just because something worked for that phone, does not mean it will on the One X.
Back off, and do the proper research before doing anything else. Stick to this subforum (AT&T One X) and don't go Googling around on random sites. Everything you need is here, and safe. At least you have bootloader, so you can probably recover. Mess with it more, without knowing what you are doing, and you may well hard brick it.
You can start your research by reading the sticky at the top of this forum that says not to post questions in Development.
---------- Post added at 09:33 AM ---------- Previous post was at 09:27 AM ----------
Mortland said:
im following this http://forum.xda-developers.com/show...709296&page=38
Click to expand...
Click to collapse
Link is broken, can't tell what you are trying to do.
Your best bet is to flash a stock RUU, I'd start with the 1.85 one. RUUs can be found here: http://forum.xda-developers.com/showthread.php?t=1671237
Make sure your bootloader screen says LOCKED or RELOCKED. If it somehow got UNLOCKED in your tinkerings, you will need to get RELOCKED (RUU will not run with bootloader unlocked). But that is likely not the case.
http://www.youtube.com/watch?v=zNswkPGYtLc
note: updated 2/20 @ 9:20 EST, better ICS compatibility.
Welcome to Facepalm S-Off for the HTC One S (S4 only).
Credits and terms:
Exploit by beaups. Full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
HTC One S superCID: http://forum.xda-developers.com/showthread.php?t=1671643
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
Special note for One S users - flashing the OTA firmware (which you are initiating, but not actually doing here) likes to BRICK superCID phones for some reason. Follow these instructions EXACTLY. After the error 92 in step 5, whatever you do, do NOT run the fastboot flash command again. Make sure you procede on to step 6.
Let's get started:
1.) Download patcher and unzip it in your working directory:
soffbin3.zip http://d-h.st/WrZ Mirror http://goo.im/devs/dsb9938/soff/soffbin3.zip
2.) Download zip that matches your model id and move it in your working directory (do not unzip it!):
OneS PJ4010000-OneS.zip http://d-h.st/sE6 Mirror http://goo.im/devs/dsb9938/soff/PJ4010000-OneS.zip
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip <appropriate zip filename from above>
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
YES
I love you man!
Goodbye bootloader restrictions, hello OTA's! <3
Edit: I made a Tutorial Video! If there's anything wrong that you guys want me to remove or anything, let me know. Once again, good work!
Worked. <33333 oodles of love!
Very simple....thank you guys so much!!!!!!!!
Wow....thank you guys
Sent from my HTC One S using Tapatalk 2
oh yea! thanks a million
Odp: [S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
w00t. Sensation work!
Its possible to edit Scid to any "official" and relock BL after s-off?
Problem resolved
i dont even have this phone and im happy for u guys!! s-off!!! good **it!!!!:good::victory::highfive:
I read earlier on http://chat.andirc.net:8080/?channels=facepalm that higher hboots were having issues. What hboot are you on?
Qs5 said:
I read earlier on http://chat.andirc.net:8080/?channels=facepalm that higher hboots were having issues. What hboot are you on?
Click to expand...
Click to collapse
1.14, so I guess that would do it. I'll downgrade and try again, thanks.
I just don't understand why I'm not getting the vital CID error anymore. I still have SuperCID...
Jewcifer said:
1.14, so I guess that would do it. I'll downgrade and try again, thanks.
I just don't understand why I'm not getting the vital CID error anymore. I still have SuperCID...
Click to expand...
Click to collapse
Hmm he did it. Weird. http://forum.xda-developers.com/showpost.php?p=38176024&postcount=776
Qs5 said:
Hmm he did it. Weird. http://forum.xda-developers.com/showpost.php?p=38176024&postcount=776
Click to expand...
Click to collapse
His HBOOT is actually higher than mine. Odd.
Jewcifer said:
His HBOOT is actually higher than mine. Odd.
Click to expand...
Click to collapse
You could always try redownloading the PJ4010000-OneS.zip, might be a bad download?
Qs5 said:
You could always try redownloading the PJ4010000-OneS.zip, might be a bad download?
Click to expand...
Click to collapse
Come to think of it, when I was downloading the soffbin3 package the download was behaving oddly and kept stalling. Could have been server problems? I'll try redownloading that.
Guy S3 device work or not? Please report.:victory:
Jewcifer said:
Come to think of it, when I was downloading the soffbin3 package the download was behaving oddly and kept stalling. Could have been server problems? I'll try redownloading that.
Click to expand...
Click to collapse
If all else fails try a new cable and or usb port. That seemed to help other people back in the day xD
http://forum.xda-developers.com/showpost.php?p=30845333&postcount=38
Beaups just advised me that some custom roms could have issues, failing S-Off which I had as well. He said better re-clock bootloader, revert to stock rom, unlock bootloader, root, super CID, then s-off
teerapong.g said:
Guy S3 device work or not? Please report.:victory:
Click to expand...
Click to collapse
Definitely do NOT attempt this on an S3 yet. I don't want to speak on behalf of the creators, but seeing as there's a difference between the S4 and the XL, there's got to be a difference between the S4 and the S3.
uvt_novice said:
Beaups just advised me that some custom roms could have issues, failing S-Off which I had as well. He said better re-clock bootloader, revert to stock rom, unlock bootloader, root, super CID, then s-off
Click to expand...
Click to collapse
This was my original plan, actually x) I'm on a CM10.1 base. I'm thinking it should work fine with a sense-based ROM though, I'll try that first.
Amazing job guys.
Confirmed S-OFF on HTC One S (S4) T-Mobile US HBOOT 1.14.0004.
Man...S-OFF....and 2.1.0 Viper??? It's like I'm holding a brick of gold in my hand, lol.
Sent from my One S using xda app-developers app
Hello,
This might be a repetitive question but I couldn't find an exact answer.
Through the research I've done, so far I know that I should S-off my device first and then update my RUU to get android 4.3 on my device.
I am S-on and on hboot 1.11. Using clean rom right now. I'm a noob in this and have no idea abt details.
I bricked my phone once and don't want to do it again.
So, For S-off should I follow facepalm method and then should I update my RUU?? The cingular one??
Also, if anyone has a video on s-off it would be great. I can follow it easily.
Thanks. Any help will be appreciated.
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
timmaaa said:
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
saagar_mistry said:
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
Click to expand...
Click to collapse
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
For superCID, first go into bootloader and run.
fastboot oem readcid.
Tell us what it says.
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
saagar_mistry said:
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
Click to expand...
Click to collapse
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
saagar_mistry said:
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
Click to expand...
Click to collapse
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
exad said:
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
Click to expand...
Click to collapse
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
saagar_mistry said:
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
Click to expand...
Click to collapse
S-Off isn't so difficult, but at least you know where to draw a clear line on when to stop messing with the phone, unfortunately a lot of people don't really know when they are in over their heads.
As long as you can read and follow directions you will be ok. I suggest reading material on what you are doing to your phone, and if what you're doing is beneficial for it. If you read and don't understand then wait until you do so you don't brick your phone.
Sent from my HTC One X using xda app-developers app
hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita
I found another users guide to get back to mostly stock with the faut hboot and stock recovery. However. That leaves the phone rooted. Will I be able to turn in a rooted phone to use the Verizon Edge up service where I turn my phone in for a new one? If not, is tbere a way to unroot the One. I've heard S-ON is impossible, but what about rooting.
tdnookhd said:
I found another users guide to get back to mostly stock with the faut hboot and stock recovery. However. That leaves the phone rooted. Will I be able to turn in a rooted phone to use the Verizon Edge up service where I turn my phone in for a new one? If not, is tbere a way to unroot the One. I've heard S-ON is impossible, but what about rooting.
Click to expand...
Click to collapse
I know Sprint and US Cellular don't really care. I doubt Verizon cares about a rooted phone.
But if you really need to return to stock, try something like this:
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
nabbed said:
I know Sprint and US Cellular don't really care. I doubt Verizon cares about a rooted phone.
But if you really need to return to stock, try something like this:
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
Click to expand...
Click to collapse
I know that the trade in stipulates "in perfect working condition". And I know that Verizon gets pissy if you root their phones and then send it in for repairs, so I was just checking. The method linked above is the one I was talking about to get back to "stock-ish'. I just ran that, I forgot that RUU mode deletes everything. Should have moved my TiBu backups to my laptop first. Oh well.
tdnookhd said:
I know that the trade in stipulates "in perfect working condition". And I know that Verizon gets pissy if you root their phones and then send it in for repairs, so I was just checking. The method linked above is the one I was talking about to get back to "stock-ish'. I just ran that, I forgot that RUU mode deletes everything. Should have moved my TiBu backups to my laptop first. Oh well.
Click to expand...
Click to collapse
I think you lose warranty when you root, so that's why they get pissy about repairing a rooted device. However, when a device is in perfect working condition for the purpose of return/upgrade, I don't think it matters. But that's like my opinion, man. I just recently switched to Verizon.
nabbed said:
I think you lose warranty when you root, so that's why they get pissy about repairing a rooted device. However, when a device is in perfect working condition for the purpose of return/upgrade, I don't think it matters. But that's like my opinion, man. I just recently switched to Verizon.
Click to expand...
Click to collapse
I agree. I'm just trying to have as little hassle as possible. I've done what I can at this point. So we'll see. Worst case is I claim I lost it and pay the $100 insurance claim.
tdnookhd said:
I found another users guide to get back to mostly stock with the faut hboot and stock recovery. However. That leaves the phone rooted. Will I be able to turn in a rooted phone to use the Verizon Edge up service where I turn my phone in for a new one? If not, is tbere a way to unroot the One. I've heard S-ON is impossible, but what about rooting.
Click to expand...
Click to collapse
My M7 was s-off, unlocked when I traded it in for the M8. All I did was put a stock looking rom on it and turned it in. They didn't boot into the bootloader or anything like that. They just made sure it was in good working order.
You just need to do the full unroot from within the app (I forget which root app it uses) after doing the "ruu". Then I wouldn't worry about returning it.
P.S. I put ruu in parentheses not ad a slight to the dev but simply to differentiate it from a true ruu.
cntryby429 said:
You just need to do the full unroot from within the app (I forget which root app it uses) after doing the "ruu". Then I wouldn't worry about returning it.
P.S. I put ruu in parentheses not ad a slight to the dev but simply to differentiate it from a true ruu.
Click to expand...
Click to collapse
After updating with the OTA firmware from Verizon, I am no longer rooted, and have Faux hboot to show locked/S-On. I'm solid. Thanks for taking to the time to respond!
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
alibhatti said:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Maybe @dottat can help...
Hi Guys and thanks for helping me and a very thanks to Member @dottat Who saved my M8 and bought it back to life after few hours or hard work. I was almost lost hope after I tried everything I knew. I done something stupid with my M8 and it got stuck on boot loader and was not able to do anything. So @dottat Not just fix everything for me but also update to 4.4.3 with s-off wooohooo. He is a genius so anyone who is having some big problems you can connect @dottat he is really friendly and helpful
Where are some pictures as proof