Database Develop

[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

[HELP] [URGENT] Boot loop - None of the solutions are working

Hi,
I have an M7 and after trying every possible solution below:
- Flash continuously and wiping cache/dalvik
- Flash stock ROM from Guru
- wiped system/cache/dalvik as well
Absolutely nothing is working. Device is stuck in boot loop and wouldn't have any of it. I have TWRP 2.6.3.3. installed and I have side loaded stock ROM, ARHD ROM's.
Could someone help? The device had encryption issue whereby I couldn't log on to it. I then sideloaded ROM using ADB and it worked - ONCE. After booting once, it got stuck into boot loop and ever since it is like that.
Does anyone have any ideas?

5fifty5 said:
Hi,
I have an M7 and after trying every possible solution below:
- Flash continuously and wiping cache/dalvik
- Flash stock ROM from Guru
- wiped system/cache/dalvik as well
Absolutely nothing is working. Device is stuck in boot loop and wouldn't have any of it. I have TWRP 2.6.3.3. installed and I have side loaded stock ROM, ARHD ROM's.
Could someone help? The device had encryption issue whereby I couldn't log on to it. I then sideloaded ROM using ADB and it worked - ONCE. After booting once, it got stuck into boot loop and ever since it is like that.
Does anyone have any ideas?
Click to expand...
Click to collapse
in twrp wipe every partition and format data. reboot the recovery and push and flash arhd 84.

Ive tried that too.
On a different note, is there a good software to recover data after all partitions have been wiped?

btw, when I tried that, it said there was No OS installed afterwards

5fifty5 said:
btw, when I tried that, it said there was No OS installed afterwards
Click to expand...
Click to collapse
Sure, choosing Format Data erases the entire phone. All you do next it Push or Sideload a rom back to the phones sdcard storage
adb push rom.zip /sdcard
or with the phone in sideload in TWRP/advanced/sideload
adb sideload rom.zip
Sideload will start the install for you ..adb push you have to install the rom.zip

You need to flash your phone's specific RUU file. I had the same issue, did everything you did, and RUU worked!
Sent from my HTC6500LVW using XDA Free mobile app

cahibo said:
You need to flash your phone's specific RUU file. I had the same issue, did everything you did, and RUU worked!
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
That's what worked in the end - Thanks to @Danny201281

[Q] Phone totally bricked, please help!

I have a Moto G XT1068. I've flashed the latest ROM from the [ROM][5.0.2][titan][XT1068/69]The Titan Prime ROM[MAR 2](Version 1.2.1 RC) thread, then attempted the OTA null-null update, then upon rebooting it got stuck at the loading screen (colorful balls floating around) and whilst stuck it ran out of battery and switched off. Now I am only able to go to bootloader and recover (TWRP 2.8.5.0) (all other options take me to that same loading screen) and everything I try to do in TWRP fails. I cant do anything from adb and fastboot or mfastboot, it all fails. Anything I try to copy from pc to phone internal sd card while in recovery (in bootloader it doesn't see the phone as a storage device) either fails to copy or does and then disappears forn TWRP after reboot. I don't know what else to do, please help, I'm desperate!
Thank you

Few details are missing
1. Which rom where you using before
2. Did you wipe fully (Data, System, Cache, Dalvik (if))
3. Did you do factory reset before switching roms
4. Incase you did all and when you did the Update did it require any wiping and did you do it
5. Did you try flashing another kernel
6. Did you try with another SD Card
Try these it may help i am a very tech savy but these things usually helps

Download the ROM to a PC, transfer it to your EXTERNAL SD, and clean flash with TWRP.

TWRP not working (pretty much everything ends with 'failure')

So I have my Moto X 2014 bootloader unlocked and rooted (Android 6.0)
I wanted to update to LineageOS, and realized everything I try with TWRP Recovery (3.1.2-0) does fail.
I am able to flash another recovery though. i tried downgrading and upgrading TWRP but it didn't help at all.
I also noticed that, while adb is working just fine, my PC can't find my device when in fastboot mode.
So the actions I tried to perform (and failed) with TWRP are: Wiping (davlik, cache, system, data, all together and separately). Trying to copy the log to the SD card also fails.
Mounting (and unmounting) partitions seem to work, at least the checkboxes work and i can see all the contents of my internal sd card.
I'm pretty much out of ideas what to do. Should I try another recovery? Any other ideas?
Thanks in advance!

SteepSheep said:
So I have my Moto X 2014 bootloader unlocked and rooted (Android 6.0)
I wanted to update to LineageOS, and realized everything I try with TWRP Recovery (3.1.2-0) does fail.
I am able to flash another recovery though. i tried downgrading and upgrading TWRP but it didn't help at all.
I also noticed that, while adb is working just fine, my PC can't find my device when in fastboot mode.
So the actions I tried to perform (and failed) with TWRP are: Wiping (davlik, cache, system, data, all together and separately). Trying to copy the log to the SD card also fails.
Mounting (and unmounting) partitions seem to work, at least the checkboxes work and i can see all the contents of my internal sd card.
I'm pretty much out of ideas what to do. Should I try another recovery? Any other ideas?
Thanks in advance!
Click to expand...
Click to collapse
Install Motorola USB driver,
Download last stock rom for your device(not downgrade or you risk an hard brick)
Use zahidim script or mine for install rom
Enable USB debug
Reboot in fastboot
Flash twrp 3.1.1-0

[URGENT] Stuck in Bootloop. Help.!!!

I was on MUI9 Nougat 7.1.2. Unlocked my bootloader properly. Wanted to try out Google Camera. So I searched the forum, found TWRP 3.0.3 Installer. Installed the TWRP successfully. Then I thought of installing the new TWRP, so flashed TWRP 3.2.1 from the previous TWRP. When I booted back to Recovery, saw the Encryption Error. I never set any password. Got tensed. Searched the forums again for solution. Found that I have to format the data. So formatted the data, flashed LazyFlasher. Did not know what else to do, tried booting and got stuck in Bootloop. I only have Internal Storage. And have one OTG Pendrive in case it comes handy. Downloaded Dot OS 7.1.2 and tried to install it from the OTG by booting back to TWRP, failed, it said Corrupt ZIP, but the zip file was ok. So started the process again, rebooted back to TWRP, wiped everything and this time tried to flash an old MIUI9 Recovery ROM through it, it still gave the same error, Corrupt ZIP. So basically what I have left is that I can boot into TWRP and also Fastboot is working well. But dont know how to get past this Bootloop. Someone please help. Really urgent. So tensed. :crying:

do you flash miui rom in twrp or miflash? try to flash the miui rom with miflash and see if ur phone booted up or not.

Deleted

Deleted

Thanks bro. Never mind. Somehow managed to flash DotOS Nougat version through TWRP 3.0.3. Now bro please tell me one thing. I wont stay at DotOS, I dont like it, just flashed it to get through the bootloop. So now I have downloaded MIUI9 8.3.22 Developer Recovery ROM. Still having TWRP 3.0.3, BL Unlocked, ADB working, Fastboot working, USB Debugging everything taken care off. Just tell me steps to flash the Developer ROM now so that I dont go into bootloop again. Please. Thanks in advance.

ummm kinda easy actually, download the miflash software, open it, it should have the select, refresh, and flash menu. click select, and navigate to your rom file (u need to download the fastboot rom version! not the recovery version, should be easy to find in google. the format should be .tgz change it to rar, extract it, it will shows another rar extract it again, it should be folder now) that folder is your rom file. now enter fastboot mode, plug ur phone, and click refresh. it will shows some number and alphabet. if the number and alphabet appears, click flash! and wait! and ur phone will boot itself
sorry for **** english

1. Go to twrp...
2. Wipe (cache, data, dalvik/cache, system)
3. flash miui 9 dev 8.3.22
4. flash lazyflasher...
Reboot..
It will take more then 5 min to start (first boot usually take that much time)
Your phone boot normally....
If you are facing TWRP Recovery Issue then update TWRP
Link :- https://drive.google.com/drive/folders/17YW09XpEHq7xgBAriwA-mgtEG0pckop2?usp=sharing
V3.2.1-5 is latest one...
Hit thanks
From my Redmi 4X using Tapatalk VIP