Develop Bugs

[Q] Problem with adb remount

OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?

wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back

S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z

If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App

steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App

wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.

joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App

wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042

joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.

Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App

My One X Plagued With "Unfortunately The Process com.EVERYTHING Has Stopped" Messages

My One X Plagued With "Unfortunately The Process com.EVERYTHING Has Stopped" Messages
A few weeks ago my One X started giving me stopped process error messages for, well, for everything. Within 5 minutes of booting the phone up, everything would start stopping. gapps, acore, htc.bg launcher, browser, exchange...everything.
This was on my carrier's stock, ICS ROM, but, since then I've tried a custom JellyBean ROM that I found here. The problem is exactly the same, so I guess it's something deeper....
I've tried factory resets, I've tried with and without a google account linked (as I've read that can be a problem sometimes)....I've cleared cache partition and Dalvik cache....what else can I do?
Is there a "nuclear" option, that's even more intensive a wipe than a "factory reset"?
What else can I try?

Try ARHD 7.2 its basically a stock Rom were as jellybean is a ported version with not much working first I would sugguest flashing back to stock choosing the RUU from your country after your completely stock check for updates then go in bootloader and restore device factory settings don't install any apps until your sure the problem has gone if your still getting problems I would return for repair or replacement
Sent from my HTC One X using xda premium

canna666 said:
Try ARHD 7.2 its basically a stock Rom were as jellybean is a ported version with not much working first I would sugguest flashing back to stock choosing the RUU from your country after your completely stock check for updates then go in bootloader and restore device factory settings don't install any apps until your sure the problem has gone if your still getting problems I would return for repair or replacement
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Okey doke, I'll give that a try thanks. I'll be back with some dumb questions soon, probably.
Actually, here's one to start with: What's RUU?

JimBadger said:
Okey doke, I'll give that a try thanks. I'll be back with some dumb questions soon, probably.
Actually, here's one to start with: What's RUU?
Click to expand...
Click to collapse
I would ask guys from link below I've never had to flash all stock radio and firmware before just know the right ruu is important
http://forum.xda-developers.com/showthread.php?p=25018342
Sent from my HTC One X using xda premium

Erk....I'm stuck.
I downloaded a zip full of stock ROMs (One_X_1.26.114.3_odexed.zip), but I don't know what to do to get just the bits I need from it.
Having done "fastboot oem readcid", I know that I need ORANG001 stock ROM, but not sure how to "cook" it. Or even if I need to.
These are the instructions I'm trying to follow, but it's the "extracted and cooked from right RUU" bit that has flummoxed me....I've looked around for the answer, but can't find a thread that doesn't assume a level of pre-knowledge (or intelligence) that I don't have
Install stock rom of your CID
-fastboot oem readcid (to know your CID)
-all roms are based on x.xx.401.xx , so you need to download the right RUU(that matches your CID) and extract rom.zip to cook a stock rom for you
-flash custom stock rom(extracted and cooked from right RUU) on custom recovery
-fastboot flash boot c:\boot.img (flash stock kernel that's inside custom stock rom boot.img file)
RElock the bootloader (you can allways unlock)
-fastboot oem lock
Right RUU file for your CID
-put your phone on fastboot (it will not boot because you have a custom rom on a locked bootloader)
-now you can run the RUU exe file and upgrade your phone
Click to expand...
Click to collapse
Once I've got the stock ROM bit sorted, I think I'll be okay with the rest! (famous last words)

It tells you to download stock Rom matching your cid then extract it on pc (winRAR) you should get 2 folders one is the boot.IMG and the other is the Rom copy the Rom xxxx.zip to your phone and flash in cwm recovery then fastboot boot.IMG. That's it before updating your phone check stock Rom if its fixed your issues just whack arhd or some think stock based there more reliable
Sent from my HTC One X using xda premium

canna666 said:
It tells you to download stock Rom matching your cid then extract it on pc (winRAR) you should get 2 folders one is the boot.IMG and the other is the Rom copy the Rom xxxx.zip to your phone and flash in cwm recovery then fastboot boot.IMG. That's it before updating your phone check stock Rom if its fixed your issues just whack arhd or some think stock based there more reliable
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Okay, thanks, I get that bit now. But I don't know how to tell which ROM matches my CID...
I've googled phrases like "ORANG001 stock RUU" etc, but every thread seems to lead to a different
Is it likely to be this (for ORANG001): RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_...?
The actual flashing, etc, I'm comfortable with...it's just finding the right thing to flash that is doing my head in.

JimBadger said:
Okay, thanks, I get that bit now. But I don't know how to tell which ROM matches my CID...
I've googled phrases like "ORANG001 stock RUU" etc, but every thread seems to lead to a different
Is it likely to be this (for ORANG001): RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_...?
The actual flashing, etc, I'm comfortable with...it's just finding the right thing to flash that is doing my head in.
Click to expand...
Click to collapse
Ok give me a few hours I'll download and have a look I need to reinstall android SDK first that may take some time
Remember hitting the thanks button would show that you appreciate my time
Sent from my HTC One X using xda premium

Cool, I've thanked each of your posts.
I've tried both of these RUU exe's, but both just end with an "Unknown error"...which obviously isn't very helpful.
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed.exe
and
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_release_256475_signed.exe

JimBadger said:
Cool, I've thanked each of your posts.
I've tried both of these RUU exe's, but both just end with an "Unknown error"...which obviously isn't very helpful.
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed.exe
and
RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.28.061.9_Radio_1.1204.103.14_release_256475_signed.exe
Click to expand...
Click to collapse
Have a read thru this thread it may help
http://forum.xda-developers.com/showthread.php?t=1799881&highlight=back+to+stock
I'm still installing android SDK it takes so long :banghead: I'm not sure if I'll get time today if I don't I'll check it tomorrow bit busy tonight :beer::beer::beer::beer:
Sent from my HTC One X using xda premium

canna666 said:
Have a read thru this thread it may help
http://forum.xda-developers.com/showthread.php?t=1799881&highlight=back+to+stock
I'm still installing android SDK it takes so long :banghead: I'm not sure if I'll get time today if I don't I'll check it tomorrow bit busy tonight :beer::beer::beer::beer:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'll have a look, thanks. Enjoy the beers! Have one or two for me.

Omg just got backk its still downloading my firewall was blocking it defo have a look tomorrow
Sent from my HTC One X using xda premium

JimBadger said:
Erk....I'm stuck.
I downloaded a zip full of stock ROMs (One_X_1.26.114.3_odexed.zip), but I don't know what to do to get just the bits I need from it.
Having done "fastboot oem readcid", I know that I need ORANG001 stock ROM, but not sure how to "cook" it. Or even if I need to.
These are the instructions I'm trying to follow, but it's the "extracted and cooked from right RUU" bit that has flummoxed me....I've looked around for the answer, but can't find a thread that doesn't assume a level of pre-knowledge (or intelligence) that I don't have
Once I've got the stock ROM bit sorted, I think I'll be okay with the rest! (famous last words)
Click to expand...
Click to collapse
I'm free now I've just tried to download orange001 but its a filefactory link and I don't have premium account if possible please upload (mediafire.....) Or any were that allows more than 500mb to non premium members and pm the link
Edit: don't need Rom watch video
Sent from my HTC One X using xda premium

Watch this video very quick guide and easy to understand www.YouTube.com/watch?v=SZuAjz4PIjU
And yes for orange001 it is .x61.xx as you mentioned above
Sent from my HTC One X using xda premium

To update your Bootloader Unlocked with One X and Root Do the following:

:fingers-crossed: Hello friends! I had done unlocking the bootloader and then did the Root to install other Roms. The problem is that after that, he could no longer update officially OTA. Saw some friends who are having the same problem I had before officially updating my X. One So here's the solution I used to re-lock the Bootloader and Root withdraws.
* Follow exactly the tutorial that actually will work! In my case everything went right! OK? Good Luck! Big hug!
To return to the HOX Stock Room and be able to upgrade that came out yesterday by OTA, primarily due to rebloquear Boot loader through Fastboot.
For this you will need the following files on the fastboot below to download
Archive for the Stock Room of One X for his method RUU (attention can not be any room has to be the same as your device or as similar as possible and with the Software Number identical to its X One (ex: 1.29.401.11) .
Example of a aquivo RUU: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
Was this RUU I used to restore my ONEX.
When you download one RUU it will be installed on your computer and then opened a wizard to install the Stock Room in its X One, the assistant has instructions of what should be done, only a detail inportante be with the One X mode Fastboot Ruu to use.
Ruu find any files here: RUU or try google.
http://www.filefactory.com/f/7cc7b2fbdd03c031/
try google
To find out which of your Room One X, go to "menu", "settings", "about", "information software, or being in fastboot mode use the command" fastboot getvar version-main "in command prompt fastboot .
Summary:
1 - Lock your Bootloader One X.
command to lock the Bootloader in fasstboot command prompt: fastboot oem lock
note that after boloquear your bootloader it will not be as locked but as relocke, but it is blocked.
2 - Install the file. RUU exe file that you downloaded with the original room and follow the wizard's own RUU (do not forget to use the RUU x One should already be in fastboot mode.)
3 - Install the update OTA that is available
Go to "menu", "on", "software updates" and search for updates.
4 - If you want to unlock the bootloader and do the root again, this follow my tutorial: Unlock Bootloader and Root HTC One X
download:
Fastboot
http://www.4shared.com/zip/KeugC_6C/Fastboot.html?refurl=d1url
RUU
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Manual RUU
http://www.4shared.com/office/Q10uuu-Q/RUU_MANUAL_BrPt.html?refurl=d1url
Make your own risk!
Good Luck!Big hug! :fingers-crossed:

Will try after getting back... Thx
Sent from my HTC One X using xda premium

You don't need to relock bootloader or remove root before doing ota, only flashing the stock recovery and having the stock Rom
Sent from my HTC One X using xda app-developers app

XxVcVxX said:
You don't need to relock bootloader or remove root before doing ota, only flashing the stock recovery and having the stock Rom
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I am trying to find the correct recovery for my cid... Can help?
Sent from my HTC One X using xda premium

A bit confused here, I'm aware stock Rom and recovery are must, but dozens of threads also claim unroot &relocked bootloader are needed. Can you shed some light? You've done ota this way successfully?
Sent from my HTC One X using xda premium

The recovery is same for all cids, search around in dev threads. You don't need unroot and relock, just stock recovery and stock rom with all the bloatware intact. Any changes to the rom will prevent the ota from applying.
Sent from my HTC One X using xda app-developers app

Same as this one:
ICS and RELOCK after upgrading Hboot

Now!
eminemwei said:
A bit confused here, I'm aware stock Rom and recovery are must, but dozens of threads also claim unroot &relocked bootloader are needed. Can you shed some light? You've done ota this way successfully?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Friend! Mine was with custom rom and root! why could not upgrade by OTA Official! So doing various searches on the net about it I found this tutorial. I did and it worked for me! OK? Big hug! :fingers-crossed:

Thank you for your instruction XD:silly:

SM-Cryterions said:
Friend! Mine was with custom rom and root! why could not upgrade by OTA Official! So doing various searches on the net about it I found this tutorial. I did and it worked for me! OK? Big hug! :fingers-crossed:
Click to expand...
Click to collapse
You couldn't update because you didn't have the stock recovery and stock ROM. Locked/unlocked bootloaders and root don't have anything to do with a failed OTA update. You're adding steps you don't need to do.
Hickory, Dickory, Dox...Snowflake approves of my HOX....

Now!
Babydoll25 said:
You couldn't update because you didn't have the stock recovery and stock ROM. Locked/unlocked bootloaders and root don't have anything to do with a failed OTA update. You're adding steps you don't need to do.
Hickory, Dickory, Dox...Snowflake approves of my HOX....
Click to expand...
Click to collapse
Ok! These steps will be swapped for those on official rom custom rom. Understand? I tried in several ways! I removed the root, I lock the bootloader. Still could not get the update by OTA. I could only do it after you have done what it says in this tutorial! As described below Tutorial: Make at your own risk! OK? If I'm wrong, then tell me that I take the tutorial forum! OK? Thank you!

Ia struck at the white screen after updating the RUU...
Sent from my HTC Sensation XE with Beats Audio using xda premium

[REQUEST] Nandroid backup

Hi, can someone upload their nandroid backup files? I don't know how; but, the system on my phone is shown as 0MB. I used 4ext recovery to format all partition and decided to try Slim Bean (coming from Jelly Baby). The phone stuck on the slim bean loading page for about 10 minutes and I decided to take out the battery and restart. That's when the problem started.... I can still boot into 4ext recovery; but, it says the recovery is in safe mode and I need to format the system. When I tried to re format all my partition I got "make_extf4fs failed on dev/block/mmcblk0p25" message.
I have tried to just ignore the message, flash a ROM; but, it won't boot. When I go to "info" on 4ext recovery it says that system, data, and cache size are all --MiB (which I think means that there is no data there).
I have tried to push the system.img from http://forum.xda-developers.com/showthread.php?t=1085624 to the /dev/block based on some google search and it still failed.
I also tried to do an RUU using the T-Mobile Froyo stock rom found in this thread: http://forum.xda-developers.com/showthread.php?t=1178912. When I tried to do update it, it just says it failed in my phone and the only option left is to reboot.
I am able to access the recovery; so, my last option is to try a nandroid backup. I thoughtI got a nandroid backup when I tried to do this whole thing and turned out I don't have one.... So, any help on uploading the file is truly appreciated. This is pretty much the last thing I hope will work....

I doubt a nandroid would do anything, can you post all info from bootloader screen?
Also see here
http://forum.xda-developers.com/showthread.php?p=43195539
You will find links to a bunch of info including toward the bottom of the first post there is a link to important brick info, I suggest reading through this as well
Sent from my Nexus 4 using xda premium

Here are some information about my bootloader recovery, etc
S-off
HBOOT - 0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
4ext recovery touch v1.0.0.5 RC5
Thanks for the link. I read some other similar thread and so far, I think I tried most of them.... For whatever reason even after flashing a fresh rom, pushing system.img that I previously mentioned does not help.
When I check on "info" in 4ext recovery, it shows that system, data, and cache size are all "--MiB"

Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?
Sent from my Nexus 4 using xda premium

demkantor said:
Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It says Vision pvt eng S-off.
I don't remember which method I used to root since it has been more than a year ago. But, I think it was gfree because I remembered reading somewhere that root using visionary has a chance to brick the device...

Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)
Sent from my Nexus 4 using xda premium

demkantor said:
Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I got the same result with your PC10IMG.zip with the other PC10IMG.zip that I've tried.
When I choose to update, it just says -Fail-PU on the first one (which is the bootlader). This is how it looks:
Parsing... [SD ZIP]
[1] BOOTLOADER - Fail-PU
[2] RADIO_V2
[3] RADIO_CUST
[4] RECOVERY
[5] SPLASH1
[6] TP
[7] TP

So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium

demkantor said:
So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hmm, I haven't tried flashing the engineering hboot yet. I will try to flash that through fastboot later today when I got home. Hope this works :good:

demkantor said:
So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
When I tried to flash the hboot, I used command "fastboot flash hboot g2hboot.img"
The result is:
sending 'hboot' (1024 KB)... OKAY
writing 'hboot'... FAILED (remote: image update error)
Any clue on what else I should do that might help this old phone?

Check and see which emmc you have, instructions are in the link I provided earlier
Sent from my Nexus 4 using xda premium

demkantor said:
Check and see which emmc you have, instructions are in the link I provided earlier
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
All I got is
'grep' is not recognized as an internal or external command,
operable program or batch file.
All the other adb command works so far; but, I don't know what happened with this grep is not recognized.... Do I need to update my android sdk? Or is it something else?
Edit:
Nevermind... I just re-tried it by separating the adb shell command following this thread that I found: http://forum.xda-developers.com/showthread.php?t=1854558
I followed both of the commands and for the first one which is:
adb shell
dmesg | grep mmc0
I got good result (as in the internal is not fried, I think); but using the second command (which seems to be the same with your thread), this is what I got:
C:\android-sdk-windows\platform-tools>adb shell
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 6.152069] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
Does that mean I just got a bad luck with that chip and there is no salvation for this phone?

That chip has a very high brick rate, with the issues your having my guess is its fried, sorry
Sent from my Nexus 4 using xda premium

demkantor said:
That chip has a very high brick rate, with the issues your having my guess is its fried, sorry
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well... I guess that's just my luck.... Thanks for the help!
Is there anything else that might worth a shot?

you could try to boot off sd card, There is info on how to in the first link i sent, which may not work if your bootloader partition is whats fried, but worth a shot anyway
best of luck!

[MOD] Hboot 3.16.0.000 without red text on custom kernels.

This mod removes the red text from HBOOT with custom kernels.
It is a simple binary replacement of the text that would normally display with a long string of 0x20 (The character for spaces).
WARNING: THIS IS DANGEROUS, if your phone powers off while you are writing to the hboot, you CAN brick.
S-off, root, and busybox are required
Download:
http://www.cheatersedge.org/android/m8/hboot-no-red-text.img
SHA1: 8619b74b5f22459753498d89de38f47b23518f78
Installation (This can be done in normal boot mode, but booted to TWRP is a MUCH safer bet):
Code:
adb push hboot-no-red-text.img /sdcard/
adb shell
su
dd if=/sdcard/hboot-no-red-text.img of=/dev/block/mmcblk0p11
reboot

will this be persistent between rom flashes? ie. a 1 time thing? I think it should since it is its own partition right?

epsiblivion said:
will this be persistent between rom flashes? ie. a 1 time thing? I think it should since it is its own partition right?
Click to expand...
Click to collapse
Yes, it should be persistent unless for some insane reason you decide to flash a ROM with an HBOOT image built into it.

Fenny said:
Yes, it should be persistent unless for some insane reason you decide to flash a ROM with an HBOOT image built into it.
Click to expand...
Click to collapse
it would take an even more insane dev to make such a zip. I don't think I ever saw one. except maybe one time when one of the phones I was using needed firmware update to be compatible with the new android version, and the new roms included it. though it'd be safer to have it as a separate zip.

For some reason, it's giving me an error
Code:
/sbin/sh: su: not found
while booted into twrp recovery. It has no issue finding it while booted though. Don't want to mess around flashing this hboot without being in recovery. Any ideas?

captainreynolds said:
For some reason, it's giving me an error
Code:
/sbin/sh: su: not found
while booted into twrp recovery. It has no issue finding it while booted though. Don't want to mess around flashing this hboot without being in recovery. Any ideas?
Click to expand...
Click to collapse
OH no need to worry, you are already running as root in the recovery. You can skip the "su" step.

Fenny said:
OH no need to worry, you are already running as root in the recovery. You can skip the "su" step.
Click to expand...
Click to collapse
Yeah, figured it out when I noticed the hash symbol Got it working - thanks for making this!

Hey, if I make a backup of my current hboot using dd, will I be able to restore that backup using dd if I ever need to go back to stock? Thanks!
Also, if any of y'all want the stock t-mobile hboot (3.16.0.0000) let me know, I'll upload it somewhere.

crashfocus said:
Hey, if I make a backup of my current hboot using dd, will I be able to restore that backup using dd if I ever need to go back to stock? Thanks!
Also, if any of y'all want the stock t-mobile hboot (3.16.0.0000) let me know, I'll upload it somewhere.
Click to expand...
Click to collapse
Yes, that works just fine.
Sent from my HTC One_M8 using Tapatalk

It says "no such file or directory" on the first command. Am I doing something wrong?
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 12:27 AM ---------- Previous post was at 12:01 AM ----------
verysick said:
It says "no such file or directory" on the first command. Am I doing something wrong?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I forgot to copy the img to my adb folder [emoji28][emoji191] It worked. Thanks! No more red letters [emoji41]
Sent from my HTC One_M8 using Tapatalk

Thanks for this. Worked perfectly

Thank you very much Fenny for this Eazy Peazy mod!!!!
Makes reboot look soooooooo much better

It doesn't seem to work if you have a custom splash screen installed. Any way around that? Thanks for the mod anyways :highfive:

So the phone have to be on bootloader or recovery?
Sent from my HTC One_M8 using xda premium

So i am assuming that reverting the hboot to have red text, we would just flash our own Hboot dumps?

I'm assuming so.. Either way it can't hurt to put back what was already there to begin with so give it a go
Sent from my HTC One_M8 using xda app-developers app

pp085ster said:
I'm assuming so.. Either way it can't hurt to put back what was already there to begin with so give it a go
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
I just removed the "Tampered" banner (Didn't know i can do that, LOL), so really all that is left if the Red Text. i really don't care if it says locked or unlocked.

Any way to do this in the phone without a computer?
Thanks
Sent from my HTC One_M8 using xda app-developers app

Worked as said. Red warning gone. Thank you!
Phone: T-Mobile HTC M8 rooted-superCID-s-Off
ROM: Latest Cyanogen
Recovery: Lates TWRP

tony_5309 said:
I just removed the "Tampered" banner (Didn't know i can do that, LOL), so really all that is left if the Red Text. i really don't care if it says locked or unlocked.
Click to expand...
Click to collapse
How did you remove the tampered banner?