Hi, I've updated officially to 5.0.2 but now I am selling the phone.
1) Rooted
2) Bootloader Off
3) Flashed GAPPS
After I did a factory reset, the phone isn't working 100%, I am missing the navigation key, lots of forced closed etc.
I tried to flash a ruu.zip via bootfast but have error.
Can I use a TWRP backup to restore? http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I don't want to mess it up.
story said:
Hi, I've updated officially to 5.0.2 but now I am selling the phone.
1) Rooted
2) Bootloader Off
3) Flashed GAPPS
After I did a factory reset, the phone isn't working 100%, I am missing the navigation key, lots of forced closed etc.
I tried to flash a ruu.zip via bootfast but have error.
Can I use a TWRP backup to restore? http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I don't want to mess it up.
Click to expand...
Click to collapse
To flash the RUU, your boot loader needs to LOCKED or RELOCKED. Open fastboot and type "fastboot oem lock" and then try flashing the RUU using bootloader.
Hi,
How can I find Stick RUU for m8sw?
I flashed TWRP, SuperSu, and xposed for lollipop. after that my phone worked just fine for almost a day. but it is stocked in boot logo. I cant fond anything on the web.
Related
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
kpitao said:
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
Click to expand...
Click to collapse
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
kpitao said:
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
Click to expand...
Click to collapse
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
andybones said:
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
Click to expand...
Click to collapse
the first couples times I did, I choose the firmware "m8vzw_AllInOne_Firmware" and " 4.17.605.9 Modified Firmware ".... both did not work in my case but then I did again with full wipe firmware "4.17.605.9 Full Firmware" and did work.... I didn't have nothing on my phone anyway so, the full firmware which wiped worked..
Thanks
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
MrTooPhone said:
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
Click to expand...
Click to collapse
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
sieze.s said:
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
Click to expand...
Click to collapse
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Did the same thing
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
I did the same thing could someone help me? I updated to 6.0 a couple days ago (I just got the phone) and decided to unlock the bootloader. Everything worked fine. I have minimal ADB and fastboot set up and all the drivers are set up properly too.
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
dcalf94 said:
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
Click to expand...
Click to collapse
You should not have installed supersu. Not sure why that option exists.
MrTooPhone said:
You should not have installed supersu. Not sure why that option exists.
Click to expand...
Click to collapse
What can I do to fix it?
dcalf94 said:
What can I do to fix it?
Click to expand...
Click to collapse
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
MrTooPhone said:
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
Click to expand...
Click to collapse
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
dcalf94 said:
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
Click to expand...
Click to collapse
If you are going to reflash, why not 6.0 firmware?
Is flashing my only option since I have no back-up?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
Did you look at http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 or http://firmware.center/firmware/Motorola/Moto G (3rd gen-2015)/Stock/
dcalf94 said:
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
Click to expand...
Click to collapse
You also may want to look at http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964
MrTooPhone said:
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Click to expand...
Click to collapse
Yes you can.
Edit - My phone was also stuck at this screen only - "Warning Bootloader unlocked"
I also soft bricked my phone 3-4 days ago but got it back.
Follow below steps and you are good to go -
1. Download and install Motorola Moto Drivers
2. download stock firmware from http://forum.xda-developers.com/2015...mages-t3169639 for your Moto G3 model (in my case it was XT1550)
3. download TWRP from http://forum.xda-developers.com/devd...1051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]
4. download SuperSU from http://forum.xda-developers.com/show...25&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]
Now as you have all required things to get your phone back, now follow below steps -
Now flash stock ROM, Instruction here -> http://forum.xda-developers.com/2015...ctory-t3187750
Now flash TWRP - fastboot flash recovery your_recovery_name_here.img
now start your phone (takes 15 minutes around)
now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]
Starting up phone now takes 25-30 minutes approx.
Rooted
[Don't brick and blame me , do it at your own risk ]
The point where things went wrong was that last screen where TWRP asks you if you want to root the phone - NEVER let it do that, ever, even after you properly root it the right way (which is manually flashing that specific version of SuperSU or a later version).
I've had instances where on a random reboot into TWRP - on a properly rooted Moto G3 - where that question screen comes up. It should not come up when the phone is actually rooted but I've seen it once or twice. Again, the point is: NEVER EVER let TWRP do it's own internal rooting process because that's what breaks things on the Moto G3.
- flash stock firmware complete
- go back and flash TWRP
- use TWRP to manually flash the SuperSU version (at least 2.62 beta which is what the Moto G3 running Marshmallow requires)
- make sure after that flash of SuperSU you do NOT use the TWRP option to root the device when you close out TWRP, ever
- flash a replacement logo so you don't see the bootloader is locked splash screen
That's about it.
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
guest_2011 said:
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
Click to expand...
Click to collapse
It is basically a factory reset. Not sure you need adb at this point.
MrTooPhone said:
It is basically a factory reset. Not sure you need adb at this point.
Click to expand...
Click to collapse
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
guest_2011 said:
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
Click to expand...
Click to collapse
same problem with me. almost an hour and the same page "BL Unlocked". how long did it take for your phone to spring back to life?
Hi all, I had one e8 with 4.4kitkat and the OS was for middle east, so I didn't receive any updates for andorid 5 or 6.
I decided to force flash the device and turns out I broke the device.
I tried to flash this image
0PAJIMG_M8_ACE_UL_L50_SENSE60_EMEA_MR_HTC_Europe_2.34.401.5_Radio_1.23.30336021.10G_30.69.336021.00_F_release_431395_signed.zip
using method such as fastboot flash zip file.zip in bootloaderRUU
or rename it to 0PAJIMG and put it in sdcard and boot the phone in bootloader
I tried to flash this image with TWRP also no success (signature verification fail)
so any comments? Suggestions?
The device is
MEC_UL_EMEA PVT SHIP S-ON
HBOO-3.19.0.000
OS-2.3.401.5
and I just want to make it work and have a stock rom on it, doesn't matter which OS version
How You brick your phone?
You wrote that You had 4.4 and You tried install 5.0 with RUU ZIP but You can't (error signature).
What next? You came out from RUU mode?
How's looking your screen when you try ON your phone?
first I wiped out data & system, then I tried to flash Android 6, I even found a version and flash but the wifi & cell was not working, then I tried couple of time flashin & wiping data using stock rom & twrp, now the screen just shows boot loader when ever I turn on the device with vol down + power. if I power up device normally it just show white screen with htc one logo
If U want unbrick your phone and back to 4.4:
You must again unlock yourbootloader by the fastboot USB.
Flash again TWRP by the fastboot USB
Flash backup 4.4 by TWRP for example.
If You want flash 5.0 RUU try make it by the phone:
Change name of RUU to OPAJIMG.ZIP and put it to SDCARD. Reboot phone in recovery mode. That's all.
Cripex said:
If U want unbrick your phone and back to 4.4:
You must again unlock yourbootloader by the fastboot USB.
Flash again TWRP by the fastboot USB
Flash backup 4.4 by TWRP for example.
If You want flash 5.0 RUU try make it by the phone:
Change name of RUU to OPAJIMG.ZIP and put it to SDCARD. Reboot phone in recovery mode. That's all.
Click to expand...
Click to collapse
Since I am s-on I can not get back to 4.4
I tried to flash "OPAJIMG.ZIP and put it to SDCARD" but then I receive fail message of
Device halted due to Large Image update fail!
Press <POWER> to reboot.
I also tried to flash same image using fastboot in fastbootRUU environment, but it was not successful, I get signature error
OK. So You had 6.0 but GSM was not working. Im sorry for mistake :/
I was thinking that you never flash correctly 6.0.
You have here backup TWRP for 6.0.1 - EUROPE SINGLE SIM VERSION.
I have this 7z on my device. It's working fine.
https://drive.google.com/file/d/0BzveTesxQ2iYNGVSUjMtRUVxdUk/view?usp=drivesdk
Just restore it by TWRP.
You know how?
Cripex said:
OK. So You had 6.0 but GSM was not working. Im sorry for mistake :/
I was thinking that you never flash correctly 6.0.
You have here backup TWRP for 6.0.1 - EUROPE SINGLE SIM VERSION.
I have this 7z on my device. It's working fine.
https://drive.google.com/file/d/0BzveTesxQ2iYNGVSUjMtRUVxdUk/view?usp=drivesdk
Just restore it by TWRP.
You know how?
Click to expand...
Click to collapse
Tnx, I will try it
I assume I should extract the file and then
adb push [Content of the extracted file] under root of internal storage device under TWRP folder? and then try to restore?
Cripex said:
OK. So You had 6.0 but GSM was not working. Im sorry for mistake :/
I was thinking that you never flash correctly 6.0.
You have here backup TWRP for 6.0.1 - EUROPE SINGLE SIM VERSION.
I have this 7z on my device. It's working fine.
https://drive.google.com/file/d/0BzveTesxQ2iYNGVSUjMtRUVxdUk/view?usp=drivesdk
Just restore it by TWRP.
You know how?
Click to expand...
Click to collapse
thanks, this backup saved my device, now it is live with androd 6
Gratz
Wysłane z mojego HTC One_E8 przy użyciu Tapatalka
For next generation.
This is only one way from few.
You must place unzipping backup on your INTERNAL or SDCARD to
TWRP > BACKUPS > NUMBER OF DEVICE > (unzipping backup here)
You get number of device by adb.
Plug device and write
Code:
adb devices
Example:
Hey guys, I just happened to flash my firmware (htc one e8) with an updated version (1.22.651.1 to 3.10.651.6). I was initially on 4.4.2 and installed a 6.0 stock rom later on. I flashed my firmware on the 6.0 rom. My phone now doesn't boot past htc one powered by android screen and doesnt go of, plus I don't seem to enter bootloader or fastboot or anything at all. Please I need some help. Thanks in advance guys.
Use Custom rom,,in this case.
I'm running the stock at&t ROM with Android 6. I've successfully unlocked the Bootloader, and have taken S Off (paid SunShine!)
When I boot into Recovery Mode I cannot install from SD without getting a Signature Error. When I attempt to flash TWRP via ADB/Fastboot the bootloader will freeze at prompting the Recovery Mode (only way to overcome is to reflash stock rom).
Any ideas? Was hoping to install LineageOS as I read at&t won't be issuing an OTA for HTC as they've discontinued offering the brand.
Set download mode. Then flash twrp with fastboot command. Fastboot flash recovery twrp.img Should workout just fine.
Nope. Read initial post. After flashing handset hangs when Recovery Mode is selected
StarSage said:
Nope. Read initial post. After flashing handset hangs when Recovery Mode is selected
Click to expand...
Click to collapse
Perhaps its the version of TWRP you are trying to install? Maybe you might have to try an older version since your on 6.0....?
Also, I have the same AT&T device (unlocked bootloader, but S-ON) and am curious about installing custom bootloader/ROM on this device.
Let us know if/when your able to solve it!
So, I downloaded the Windroid Toolkit at https://forum.xda-developers.com/showthread.php?t=2499926 but now I can't get passed the HTC boot screen. I installed Lineage OS, did Wipe Dalvik Cache, then installed Gapps. But no desktop after install. HELP!
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.
This problem has been solved?
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.
hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery