Database Develop

Help Flash From Fastboot after Wiping all

SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.

pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
I have had the issue of ADB unable to find devices. Don't know if this will help you, but has worked for me. Make sure phone if powered off. Hold the volume down button and press and hold the power button in order to boot into bootloader. Then plug your phone into the computer. You should see the screen change to Fastboot USB. From my experience, that is where you need to be.
YMMV. Good luck.

pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
If you want to sideload you'll need TWRP recovery. Here's a guide. http://forum.xda-developers.com/showthread.php?t=2318497 I myself had trouble finding my device, but than I uninstalled all the HTC drivers I had and installed the "universal naked driver" from here http://forum.xda-developers.com/showthread.php?t=2263822

I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....

Sirricharic said:
I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....
Click to expand...
Click to collapse
If you dont have a custom recovery make sure you flash one thru bootloader, fastboot. Regardless of you Hboot or bootlaoder number, you can get it unlock at the htcdev.com website. then you have to flash TWRP recovery. After doing then go to recovery....Don't do anything yet, make sure that you computer recognizes your phone. THATS the mistake I made. Open device manager and look for android USB devices if its not there then you need to install the adb drivers. If its there then on TWRP recovery look for adb side... I think its under advance .... then open the command to tour adb folder and type "adb version" you need at least 1.0.21 or higher. then type adb sideload name of rom.zip

[Q] Only boots to bootloader or recovery, no fastboot

Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.

xpurtwitness said:
Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.
Click to expand...
Click to collapse
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.

alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?

Artemicion said:
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?
Click to expand...
Click to collapse
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.

alray said:
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.
Click to expand...
Click to collapse
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thanks

Artemicion said:
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
Click to expand...
Click to collapse
yes, via fastboot :laugh:
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thank
Click to expand...
Click to collapse
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)

alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Wow, ok, I think that sounds like far too much effort to just update my phone. Guess I'll use the ubuntu fastboot trick once, then just hope I never need to flash anything from fastboot again on this phone. Why is it always such an effort with these damn things? Thanks for the help, won't have a chance to try this for a couple of days but doubtless I'll be back with some other failed horror scenario then.

alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
Yeah, that's pretty much the extent of what I knew, but I really appreciate your response. I did manage to get my old Win7 laptop running and with some effort got all the drivers working. I used htc1guru reset, but sadly I did lose the entire contents of my SD, despite its message that nothing would be touched. :-/ Luckily, most photos were auto-backed up by G+ and it's just a few settings and such that I can't get back or figure out. Least of my concerns after having a functional phone!

alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...

Artemicion said:
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...
Click to expand...
Click to collapse
the answer is always the same, in the same folder you have adb in.
so in ubuntu it should be androidsdk/platform-tools/

[Q] Bricked. Boot Loop. No Data in SD Card.

Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!

Gunny007 said:
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Click to expand...
Click to collapse
instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse

clsA said:
instructions
Click to expand...
Click to collapse
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.

Gunny007 said:
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Click to expand...
Click to collapse
your just flashing a rom ...nothing to do with getting updates

clsA said:
your just flashing a rom ...nothing to do with getting updates
Click to expand...
Click to collapse
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!

Gunny007 said:
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Click to expand...
Click to collapse
Good to here

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks

anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this

Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.

As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho

Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.

anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again

No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,

anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

[Q] I've bricked my M7

Hi,
I had Android revolution installed on my M7. I've started to play with TWRP recovery and I've bricked my phone. It's now turning on straight to TWRP recovery, even if i will choose to boot system. Can you help me fix it?
CID: ORANG001

karoltom said:
Hi,
I had Android revolution installed on my M7. I've started to play with TWRP recovery and I've bricked my phone. It's now turning on straight to TWRP recovery, even if i will choose to boot system. Can you help me fix it?
CID: ORANG001
Click to expand...
Click to collapse
What have you done exactly from TWRP? Wiped /system? Tried to flash a rom? Formatted /data?
download a rom and push it to you internal storage and then flash it using the "install" function in twrp recovery. You won't be able to flash lollipop rom on this phone because the firmware installed is to old.

i don't know how to do this. i can't find software for ORANG001. maybe i can install some custom ROM?
If the phone will be working fine i know how to do s-off, change cid and flash it with stock rom.
Is there any other way to gain s-off except rumrunner?

karoltom said:
i don't know how to do this. i can't find software for ORANG001. maybe i can install some custom ROM?
If the phone will be working fine i know how to do s-off, change cid and flash it with stock rom.
Is there any other way to gain s-off except rumrunner?
Click to expand...
Click to collapse
Your on hboot 1.57. There is only one way to s-off 1.57 and thats Sunshine app. Which cost £25. But before you can s-off you need a functional rom on the device.
You can use this http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_84.0.zip
Download the rom and put it in your fastboot folder and rename it something simple like rom.zip.
If you have twrp 2.8.5.x you should be able to enable MTP in recovery then just copy the rom strait to you internal storage from you pc and install it.
Older versions of twrp don't support MTP in which case you will need to adb push the rom to your device. Instructions below
With the rom.zip in your fastboot folder. Open a adb/fastboot command window. Boot the device to recovery and connect usb. Check adb is working by typing
Code:
adb devices
if you get the expected out put push the rom with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete. When it's done install the rom with TWRP.
Sent from my SM-T230 using Tapatalk

thank you for your help. I've managed to copy rom file using 'push' option Hopefully it will be working fine now