Database Develop

[Q] PLEASE HELP flash TrickDroid - FROZEN - REBOOT = BRICKED

in short:
i used the ALL IN ONE TOOLS to unlock boot loader from HTC DEV as instrcutions.
then took a few times to install CWM, CWM TOUCH, TWRP finally end up with CWM TOUCH
then i flashed TRICKDROID successfully
Thing went bad when TRICKDROID installation completed and asked to reboot, i didn't do that but continue flash the theme zip as i used to do it with gapps. During the AROMA INSTALL its frozen at 40% for 30 mins. I try to reboot and my PHONE STUCK at the boot screen. At fist i couldn't access to RECOVERY but after a few try to Re-lock and reset Iam able to get into CWM to re-flash TRICKDROID, it kept stuck when i select options randomly for a few times until i end up with error mounting sdcard the error is similar no mater what recovery i use.
Now my phone is almost useless, the only thing i can do to get CWM to see couldn't mount SdCard error. I read and many solutions to re-flash to stock but always came up with signature checking failed ... i follow [HOW-TO] Fix soft brick & error mounting sdcard from HTC ONE S without successful. NAROID BACKUP ZIP AND RUU re-flash also failed so far. i used my back up and TELSTRA backup from HTC M7 RUU Collection, the trouble now is I have no ways to access to SD CARD.
Please help, it took me almost 12 hours continuously already,
my phone details is
based Band 4A.14.3250.13
hboot 1.44.0000
main 1.29.841.2
model id PN0714000
cid TELSTRA001

hdt_anh said:
in short:
i used the ALL IN ONE TOOLS to unlock boot loader from HTC DEV as instrcutions.
then took a few times to install CWM, CWM TOUCH, TWRP finally end up with CWM TOUCH
then i flashed TRICKDROID successfully
Thing went bad when TRICKDROID installation completed and asked to reboot, i didn't do that but continue flash the theme zip as i used to do it with gapps. During the AROMA INSTALL its frozen at 40% for 30 mins. I try to reboot and my PHONE STUCK at the boot screen. At fist i couldn't access to RECOVERY but after a few try to Re-lock and reset Iam able to get into CWM to re-flash TRICKDROID, it kept stuck when i select options randomly for a few times until i end up with error mounting sdcard the error is similar no mater what recovery i use.
Now my phone is almost useless, the only thing i can do to get CWM to see couldn't mount SdCard error. I read and many solutions to re-flash to stock but always came up with signature checking failed ... i follow [HOW-TO] Fix soft brick & error mounting sdcard from HTC ONE S without successful. NAROID BACKUP ZIP AND RUU re-flash also failed so far. i used my back up and TELSTRA backup from HTC M7 RUU Collection, the trouble now is I have no ways to access to SD CARD.
Please help, it took me almost 12 hours continuously already,
my phone details is
based Band 4A.14.3250.13
hboot 1.44.0000
main 1.29.841.2
model id PN0714000
cid TELSTRA001
Click to expand...
Click to collapse
Choose install zip from sideload in recovery
Put your ROM.zip in your adb folder on your computer and open a terminal from the folder
Command
adb sideload name_of_your_rom.zip
Or try using the toolkit to sideload but I'm unfamiliar with the toolkit method as I use a Mac
Sent from my HTC One using xda premium

I enabled ADB side from TWRP then your command, it said * can not read 'sideload' *
Using ALL IN ONE TOOLS the CMD windows is all black for about 5 minite, device not found, from bottloader it's clearly seen FASTBOOT USB before enter RECOVERY. I can hear the sound from my LAPTOP whenever turn on/off ADB Sideload, so my LAP should see my phone
i am pretty sure that the ZIP is okie and flash-able before.
i found one thing my HTC ONE is the TELSTRA BRAND in AUSTRALIA with the base mainbase 1.29.841.2 while the Trickdroid is from 401 brand 1.29.401.16 R (WWE). according to my understand my HTC able to use m7_UL ROMS which should be fine, iwonder i might the reason cause my phone bricked like that?
i tried ti find the stock base RUU for my TELSTRA TELST001 but no luck so far. NO ONE have seen that RUU before.
If that's is the case what should i do next? thanks in advance

My HTC One is screwed?

Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.

Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.

MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this

MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry

[Q] HTC One semi bricked!! i think help

Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!

The cid on the phone and the ruu has to be the same.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Try -off

andyp1 said:
Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
Click to expand...
Click to collapse
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Also, to run the RUU your bootloader must be locked/relocked since you are S-ON.

majmoz said:
Based on your CID you got the incorrect RUU. You should have gotten this one: RUU_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Click to expand...
Click to collapse
that wont work as he is s-on, his HBOOT is 1.54 and that RUU has HBOOT 1.56, too many steps up, it will fail with image error.
you need to use this: http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
or this one is probably better for you which is probably the same version you had on the phone to start with: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
push it to your internal storage and flash like a custom rom, select wipe data, install stock recovery and install stock radio when prompted, you should get OTAs after that.

[Q] Problems with OTA Upgrade

I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.

Check PM

sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...

[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.

Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.

Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?

sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off

bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.

sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom

Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??

After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!

Yes you need to unlock your bootloader again to be able to flash twrp

I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!

You can get SuperSU or Superuser from the playstore or install a custom rom.

A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.

A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?

Soft Bricked m7 on hboot 1.44. How to completely wipe + flash recovery + flash rom?

Hello everyone,
I recently ran into a bit of problem with my HTC One m7 (early model). Back when I first got it I performed an HTC Dev bootloader unlock and ever since I've been flashing different roms through TWRP. The other day I tried downgrading from Android 5 to 4.2 and something went wrong. The Aroma installer for AndroidRevolutionHD hung at 10% for about an hour, and I decided to restart. Upon restart, TWRP greeted me with messages such as
"E:/ cannot mount system" or "E:/ cannot mount cache".
After changing through various TWRP revisions (2.6.1 seemed to remove the system error), I still have not been able to install any ROMS successfuly. I tried different versions of ARHD and ViperROM but they all seem unable to install to some part of the filesystem, and the phone never boots.
Is there a way to gain S-OFF while in this dummy state?
Is there a way to flash over everything and get a clean recovery and rom working (through fastboot/terminal)?
All help is appreciated. Thanks a lot.

Rarestg said:
Hello everyone,
I recently ran into a bit of problem with my HTC One m7 (early model). Back when I first got it I performed an HTC Dev bootloader unlock and ever since I've been flashing different roms through TWRP. The other day I tried downgrading from Android 5 to 4.2 and something went wrong. The Aroma installer for AndroidRevolutionHD hung at 10% for about an hour, and I decided to restart. Upon restart, TWRP greeted me with messages such as
"E:/ cannot mount system" or "E:/ cannot mount cache".
After changing through various TWRP revisions (2.6.1 seemed to remove the system error), I still have not been able to install any ROMS successfuly. I tried different versions of ARHD and ViperROM but they all seem unable to install to some part of the filesystem, and the phone never boots.
Is there a way to gain S-OFF while in this dummy state?
Is there a way to flash over everything and get a clean recovery and rom working (through fastboot/terminal)?
All help is appreciated. Thanks a lot.
Click to expand...
Click to collapse
1- recovery is too old, you need at least 2.6.3.3 or higher, you could check 2.8.6.4 universal build
2- FAQ Sticky in particular page 3
3- as for S-OFF, if you are truly on such old firmware, then
---> hboot 1.44 dated pre June 2013, you can use this with revone
---> or rumrunner

nkk71 said:
1- recovery is too old, you need at least 2.6.3.3 or higher, you could check 2.8.6.4 universal build
2- FAQ Sticky in particular page 3
3- as for S-OFF, if you are truly on such old firmware, then
---> hboot 1.44 dated pre June 2013, you can use this with revone
---> or rumrunner
Click to expand...
Click to collapse
Thanks for the advice, but after updating to TWRP 2.8.6.4 it still displays " E: unable to mount '/system' ". Tried flashing the stock rom that you linked in that thread but its installer hangs again while "formatting partitions".
If I try to flash a stock recovery, how do I avoid updating hboot? Also is it possible to use revone or rumrunner without access to the Android system? Both guides seem to depend upon Android working on said system.

Rarestg said:
Thanks for the advice, but after updating to TWRP 2.8.6.4 it still displays " E: unable to mount '/system' ". Tried flashing the stock rom that you linked in that thread but its installer hangs again while "formatting partitions".
If I try to flash a stock recovery, how do I avoid updating hboot? Also is it possible to use revone or rumrunner without access to the Android system? Both guides seem to depend upon Android working on said system.
Click to expand...
Click to collapse
1- revert back to twrp 2.6.3.3 as mentioned in the faq
2- do the [real] formats in twrp 2633
3- then flash rom (take your pick, adb push, sideload or otg)
4- get s-off (provided the per-requisites are met)