Now up and running for our 3D's.
HBoot 1.5 users, flash via FlashImage GUI.
So far, so good!
http://www.clockworkmod.com/rommanager
i dont understand what to do with it?? img?? i thought to flash a recovery u put it on the root of sdcard and fastboot finds it and u update.. i have hboot 140 rooted.. so how do i go about flashing this new touchscreen cwm recvovery?? yes im a noob.. and yes i tryed to find out but cant find any thing?? i just thought i needed a PG86IMG.ZIP just like when u flashed the new twrp 2.0?
evod3 said:
i dont understand what to do with it?? img?? i thought to flash a recovery u put it on the root of sdcard and fastboot finds it and u update.. i have hboot 140 rooted.. so how do i go about flashing this new touchscreen cwm recvovery?? yes im a noob.. and yes i tryed to find out but cant find any thing?? i just thought i needed a PG86IMG.ZIP just like when u flashed the new twrp 2.0?
Click to expand...
Click to collapse
flash it via flash image GUI or via fastboot using PC
evod3 said:
i dont understand what to do with it?? img?? i thought to flash a recovery u put it on the root of sdcard and fastboot finds it and u update.. i have hboot 140 rooted.. so how do i go about flashing this new touchscreen cwm recvovery?? yes im a noob.. and yes i tryed to find out but cant find any thing?? i just thought i needed a PG86IMG.ZIP just like when u flashed the new twrp 2.0?
Click to expand...
Click to collapse
If you're HBoot 1.4, you don't necessarily need to do the workaround that 1.5'ers use, but the same method works.
1) Install FlashImage GUI (either buy from market or find the apk file on XDA)
2) Select option to flash recovery image.
3) Locate recovery image of choice. You do NOT need to rename anything.
4) Flash recovery image.
5) Reboot to recovery to confirm image flashed correctly.
Those 5 steps should get you a new recovery. Let me know if you encounter any issues. This new CWM Touch Recovery seems to be working fine so far, I've tested a majority of the functions so far and have had no issues yet.
Is this better than Twrp 2.0 just need someones opinion on it. Are there any other features which makes it must have?
Sent in 3D
Boss2212 said:
Is this better than Twrp 2.0 just need someones opinion on it. Are there any other features which makes it must have?
Sent in 3D
Click to expand...
Click to collapse
I was unable to mount USB storage so i switched back to twrp 2.0
Sounds good, but I think ill wait a month before using to make sure no one finds any serious problems with it
Also, there should be an easy PG86IMG.ZIP made for this, thats how I have ALWAYS done all firmware and recovery flashes and never had a problem. It was the right way before all this flash image stuff.
mnomaanw said:
I was unable to mount USB storage so i switched back to twrp 2.0
Click to expand...
Click to collapse
One option I hadn't tried this morning, and can also confirm this.
Gives an error "E: unable to open ums lunfile (no such file or directory)"
Does it work any better than twrp 2.0?
Would backups from the previous non touch version still function ?
Sent from my CM9 HP Touchpad
DarkManX4lf said:
Does it work any better than twrp 2.0?
Click to expand...
Click to collapse
Haven't experienced any bad flashes on a few test runs yet, but as mentioned earlier in this thread, USB storage mount doesn't work, so any files you need to push you'll need to go through the ADB route until a revised version of this recovery image is created.
Link to the ADB method; scroll to post #9:
http://rootzwiki.com/topic/12348-slow-transfer-usb-mounting-unable-to-open-ums-lunfile/
Charging in recovery is fuctional?
nikosblade said:
Charging in recovery is fuctional?
Click to expand...
Click to collapse
Nope, doesn't appear to be.
You can update this straight from the rom manager application
---------- Post added at 08:46 PM ---------- Previous post was at 08:20 PM ----------
gav-collins1983 said:
You can update this straight from the rom manager application
Click to expand...
Click to collapse
Sorry,my bad,I tried and it just flashes 5.0.2.0, I was able to flash via flash image GUI, without needing to wipe caches, of course, lol, seems pretty cool, ain't tested for bugs as yet, just wanted to correct my error here
cool beans!!! it worked!! ill have to try this out for a while see how it works.. that was the first time i ever used flash gui cause i ahve hboot 1.40 never needed to.. i always thought it would be a pain to use but it was mad easy to use.. good stuff!!!!!!! thanks!!!!!!!!!!!
---------- Post added at 10:05 PM ---------- Previous post was at 09:49 PM ----------
the only thing i dont like is there was no download bar?? so i dint kno when it was going to finish..
evod3 said:
cool beans!!! it worked!! ill have to try this out for a while see how it works.. that was the first time i ever used flash gui cause i ahve hboot 1.40 never needed to.. i always thought it would be a pain to use but it was mad easy to use.. good stuff!!!!!!! thanks!!!!!!!!!!!
---------- Post added at 10:05 PM ---------- Previous post was at 09:49 PM ----------
the only thing i dont like is there was no download bar?? so i dint kno when it was going to finish..
Click to expand...
Click to collapse
Good stuff, man. It's a very handy app, especially for those of us stuck w/ HBOOT 1.5. Great for toggling between kernels and quickly set up new ROMS.
Yes, no more finger Olympics..
Sent from my PG86100 using XDA App
Guys, just to reiterate....
1) Mount USB storage does not work
2) Charging via recovery does not work
If you want to flash a ROM directly through the recovery, you need to rename the ROM zip to "update.zip" w/o the quotes. PITA, but that's the workaround if you do not wish to go through ADB mounting.
i actully went back to twrp 2.0 cause my phone shut off by it self after i flashed cwm touch recovery.. my phone never does that.. so i went back to twrp just to be safe..plus there was kno download bar.???
I rolled back to older version 4 of cwm not a fan of twrp 2.0 tho. Nice features but has some annoying issues lol twrp 2.0
Related
Hi I am almost sure i bricked my phone, i can't make it pass the boot screen on any rom i try to put on the recovery. Yes, recovery is working, what i did to make it this state surprises me, I was trying to put Miuiu on my phone, i followed the instructions and downloaded the app called "Flash Image Gui" and well i did, the problem was that after i did, it asked me to install another app and that started giving me errors, i could not make calls just receive, and whenever someone texted me it would tell me than "The customer you are trying to text is temporarily out of service" ...after that i tryed changing to another rom and when i did it kept doing the same errors, not even data worked. well to get to the point i wanted to install miuiu and i did try. i openeed the app flash image gui and tryed to install the rom...after that it told me to boot, and thats the last thing i did before my endless boot screens for all 4 roms i have tried..i dont know what to do anymore. :/
if anybody could help me, i have been trying all day to make it at least show me the homescreen. but nothing passes the bootscreen. it just freezes there..
edit
i was also trying a RUU.exe stock...but i cant go to homescreen for it to be able to detect my phone :/
If you can still get into recovery, it can't be all bad! Have you tried flashing the super wipe script before flashing a ROM
Sent from my HTC EVO 3D X515a using xda premium
magicalan said:
Hi I am almost sure i bricked my phone, i can't make it pass the boot screen on any rom i try to put on the recovery. Yes, recovery is working, what i did to make it this state surprises me, I was trying to put Miuiu on my phone, i followed the instructions and downloaded the app called "Flash Image Gui" and well i did, the problem was that after i did, it asked me to install another app and that started giving me errors, i could not make calls just receive, and whenever someone texted me it would tell me than "The customer you are trying to text is temporarily out of service" ...after that i tryed changing to another rom and when i did it kept doing the same errors, not even data worked. well to get to the point i wanted to install miuiu and i did try. i openeed the app flash image gui and tryed to install the rom...after that it told me to boot, and thats the last thing i did before my endless boot screens for all 4 roms i have tried..i dont know what to do anymore. :/
if anybody could help me, i have been trying all day to make it at least show me the homescreen. but nothing passes the bootscreen. it just freezes there..
edit
i was also trying a RUU.exe stock...but i cant go to homescreen for it to be able to detect my phone :/
Click to expand...
Click to collapse
Your not bricked lol Does your recovery still work? I don't use flash gui...
You might need to flash another recovery to your phone...
What were you using?
As long as you didn't mess around with radios or prl's you should be safe...
Snag another recovery flash it fastboot flash it and find another rom take a copy of the boot.img from it place it in your platform tools folder where adb is is...
Now wipe everything in recovery other then SD card and then
adb reboot bootloader
fastboot flash boot boot.img
then go into recovery and flash the rom you wanted....
markdexter said:
If you can still get into recovery, it can't be all bad! Have you tried flashing the super wipe script before flashing a ROM
Sent from my HTC EVO 3D X515a using xda premium
Click to expand...
Click to collapse
yes i have tried a super wipe script i do feel relief that you tell me that haha
reaper24 said:
Your not bricked lol Does your recovery still work? I don't use flash gui...
You might need to flash another recovery to your phone...
What were you using?
As long as you didn't mess around with radios or prl's you should be safe...
Snag another recovery flash it fastboot flash it and find another rom take a copy of the boot.img from it place it in your platform tools folder where adb is is...
Now wipe everything in recovery other then SD card and then
adb reboot bootloader
fastboot flash boot boot.img
then go into recovery and flash the rom you wanted....
Click to expand...
Click to collapse
i will never use that flash gui lol am traumatized. haha and yes my recovery works..its ahmm Revolutionary CWM v 4.0.1.4...i was downloading a RUU to rename it too PG86IMG and apparently that should fix the problem? :S if you think it wont please tell me were to get another recovery or what exacly do you mean ,because i have wiped ALOT everytimeee and i have also used a script
magicalan said:
yes i have tried a super wipe script i do feel relief that you tell me that haha
i will never use that flash gui lol am traumatized. haha and yes my recovery works..its ahmm Revolutionary CWM v 4.0.1.4...i was downloading a RUU to rename it too PG86IMG and apparently that should fix the problem? :S if you think it wont please tell me were to get another recovery or what exacly do you mean ,because i have wiped ALOT everytimeee and i have also used a script
Click to expand...
Click to collapse
Just snag a 3.0 based rom you could try eternity 3.0 R80 while it's up
Put it on your SD card copy the boot.img to your platform tools folder and wipe everything in your recovery other then your SD card
Then fastboot flash the boot.img and go into recovery and flash rom....
fastboot flash boot boot.img
I think something is dicked with the boot.img you are using which is why your phone is acting crazy lool
Ya man the boot.img thing when you went to flash with flash gui app something got dicked up and messed up the boot.img from the rom you were using ....
So that is why your calls and **** were messin up
---------- Post added at 09:43 PM ---------- Previous post was at 09:33 PM ----------
In other words your boot.img got screwed up so that is what's causing your issue...
reaper24 said:
Just snag a 3.0 based rom you could try eternity 3.0 R80 while it's up
Put it on your SD card copy the boot.img to your platform tools folder and wipe everything in your recovery other then your SD card
Then fastboot flash the boot.img and go into recovery and flash rom....
fastboot flash boot boot.img
I think something is dicked with the boot.img you are using which is why your phone is acting crazy lool
Ya man the boot.img thing when you went to flash with flash gui app something got dicked up and messed up the boot.img from the rom you were using ....
So that is why your calls and **** were messin up
Click to expand...
Click to collapse
i have used different roms and wiped everytime, so i just put the boot.img (extracted from the rom) then push it thru cmd ? what exactly do i tell it, to push it, my folder is in C:\AndroidSDK\tools\boot.img like this?
magicalan said:
i have used different roms and wiped everytime, so i just put the boot.img (extracted from the rom) then push it thru cmd ? what exactly do i tell it, to push it, my folder is in C:\AndroidSDK\tools\boot.img like this?
Click to expand...
Click to collapse
If your on windows 7 you can just hold shift down right click on the folder adb is in and say open cmd prompt here ..... makes things easy
Where is ADB installed under? Mine is in the platform tools folder.
You open the rom on your computer take a copy of the boot.img
Place it in the folder where adb is... Hook your phone up with the usb cord to computer
Place the rom on you SD card
Then go into recovery and wipe everything like normal
type adb reboot bootloader
then when it says fastboot when your in Hboot type : fastboot flash boot boot.img
Once it's done go into your recovery and flash the rom..
magicalan said:
i have used different roms and wiped everytime, so i just put the boot.img (extracted from the rom) then push it thru cmd ? what exactly do i tell it, to push it, my folder is in C:\AndroidSDK\tools\boot.img like this?
Click to expand...
Click to collapse
try fastboot (see attached)
Plug phone into computer with usb boot into the bootloader and select fastboot
it should show fastboot USB
Unip the attachment into a folder then move the boot.img from the rom you are using into that folder
open the start here.bat
type fastboot flash boot boot.img
let it work and then your phone should boot
just do that when you wanna flash a new rom.
shalkith said:
try fastboot (see attached)
Plug phone into computer with usb boot into the bootloader and select fastboot
it should show fastboot USB
Unip the attachment into a folder then move the boot.img from the rom you are using into that folder
open the start here.bat
type fastboot flash boot boot.img
let it work and then your phone should boot
just do that when you wanna flash a new rom.
Click to expand...
Click to collapse
He already has ADB on his computer and knows what he is doing lol. Don't wana **** him up further lol..
thanks guys am going to try the boot.img then flashing the rom. hopefully it BOOTS! thats all i want. lol i dont care the rom right now haha
magicalan said:
thanks guys am going to try the boot.img then flashing the rom. hopefully it BOOTS! thats all i want. lol i dont care the rom right now haha
Click to expand...
Click to collapse
Ya I was just going off a rom I know is stable lol. Miui is alright not something I want lol
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
reaper24 said:
Ya I was just going off a rom I know is stable lol. Miui is alright not something I want lol
Click to expand...
Click to collapse
First boot may take ali while lol...
Shouldn't take forever tho....
reaper24 said:
Ya I was just going off a rom I know is stable lol. Miui is alright not something I want lol
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
First boot may take ali while lol...
Shouldn't take forever tho....
Click to expand...
Click to collapse
flashing as we speak... hopefully that boots :/ i have tried all the popular roms man, thast why i dont think its the rom at all.. :/
magicalan said:
flashing as we speak... hopefully that boots :/ i have tried all the popular roms man, thast why i dont think its the rom at all.. :/
Click to expand...
Click to collapse
It was the boot img lol... When you used that app.
reaper24 said:
It was the boot img lol... When you used that app.
Click to expand...
Click to collapse
omg i fu^^ng love you yes the homo way. thanks alot man lol
WORKED!!
magicalan said:
omg i fu^^ng love you yes the homo way. thanks alot man lol
WORKED!!
Click to expand...
Click to collapse
Yay
Sent from my Evo3D
magicalan said:
omg i fu^^ng love you yes the homo way. thanks alot man lol
WORKED!!
Click to expand...
Click to collapse
Lmao anytime man....
Hello. Right now, I am in the process of installing a custom ROM on an HTC Evo 4G LTE. I unlocked the boot loader, put TWRP on it, copied Paranoid Android on it with Gapps, and installed the zip. The phone is still in s-on mode and is stuck at the Paranoid Android screen. I have no idea what to do. I have to get it fixed ASAP. Please, help.
well for whatever reason paranoid android is not loading .. so ..go back into twrp a press reboot>system.. and you phone should reboot back into your previous rom...or you can press restore and choose the rom listed there.. and follow prompts from there.... that will get you back to square one.. you can figure out why the new rom wont load from there... make sense?... hopefully you DID make a backup of your old rom!!!
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
oh ya to get back into twrp .. hold down the power button and the vol down button at the same time .. that will take you to the boot loader screen .. scroll down with vol. button and choose "recovery" .. that will get you back into twrp.. easy cheesy
jceccoli said:
Hello. Right now, I am in the process of installing a custom ROM on an HTC Evo 4G LTE. I unlocked the boot loader, put TWRP on it, copied Paranoid Android on it with Gapps, and installed the zip. The phone is still in s-on mode and is stuck at the Paranoid Android screen. I have no idea what to do. I have to get it fixed ASAP. Please, help.
Click to expand...
Click to collapse
Sounds like you didn't fast boot the kernel
heliguide62 said:
well for whatever reason paranoid android is not loading .. so ..go back into twrp a press reboot>system.. and you phone should reboot back into your previous rom...or you can press restore and choose the rom listed there.. and follow prompts from there.... that will get you back to square one.. you can figure out why the new rom wont load from there... make sense?... hopefully you DID make a backup of your old rom!!!
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
oh ya to get back into twrp .. hold down the power button and the vol down button at the same time .. that will take you to the boot loader screen .. scroll down with vol. button and choose "recovery" .. that will get you back into twrp.. easy cheesy
Click to expand...
Click to collapse
Well, I never made a backup of the original stock ROM. I tried everything I could, but then realized I was in S-On mode, and HBOOT is 1.19. Therefore, I think there is no way around it. I just did "locked" the boot loader and ran the RUU. That has gotten it back to stock. Worst part is, I convinced my friend to do this because I had rooted my One S, now, he's never going to want to root again. He didn't back anything up to his computer, just his SD card, which was wiped. Damn. Thanks for the reply.
no prob .. well the the upside is .. you were able to get it back .. and you didn't brick the thing
Like om4 said, all you needed to do was flash the boot image. That is one of the known limitations with your hboot version.
http://forum.xda-developers.com/showthread.php?p=31102864
Sent from my EVO LTE
With s-on you may flash any Rom with a custom recovery. Just not (kernel,bootimg,radio) so what you can do is
HTC dev unlock,root stock rom
download flash image gui.apk
download the Rom and gapps
Open flash image gui
Flash the paranoid rom from FIGUI
Reboot into recovery and flash again
Now you should have a working boot image and rom.
Sent from my EVO using xda premium
Similar issues
Hey all, noob here.
This is as similar to the issue I am having now as I can find. So here's what up as far as brass tacks.
HTC EVO 4G LTE "Jewel"
TWRP loaded and functional
Rooted, (tampered) had SuperUser
Nothing in the internal SD card (explain momentarily)
No OS. Yeah, no.
S-ON due to 3.17.
Lost my Nandroid
Don't know much else cause if I take it out of recovery I have to suffer through a bootloop, but I will get more info once I get an idea of whats happening.
Down and Dirty:
So I have rooted several devices, My old Evo 4G's, a couple SIII and S4's and I thought I could do this in one morning. So I got it rooted, using WinDroids help, but skipped S-Off as 3.17 was too new for the software in the toolkit. Did some reading, read multiple times that S-ON was cool to just a ROM which is what I wanted, So I DL'd the ROM, loaded to internal memory, loaded up TWRP from recovery, ran it.
Failed.That's ok, I have the nandroid, I suffered a boot loop until I learned how to escape, Recovered, and I tried again with a fresh DL. Same. So I nandroided and was looking everything over. Then I butter fingered everything. I factory reset the phone, dumping my nandroid and my OS out the window. No I have a phone with no OS and my only access to it is through USB mount in TWRP. How can I either
A) get it back to stock ROM or
B) install the AOSP ROM I was going for. Any more information required I will be more than obliged to give.
I appreciate everything I get I promise!
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
slowfncar said:
With s-on you may flash any Rom with a custom recovery. Just not (kernel,bootimg,radio) so what you can do is
HTC dev unlock,root stock rom
download flash image gui.apk
download the Rom and gapps
Open flash image gui
Flash the paranoid rom from FIGUI
Reboot into recovery and flash again
Now you should have a working boot image and rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is what I think happened to me, by the way. How would I do a ROM without a Kernel? Just yank the kernel folder out? I doubt it. I used to know but I'll be honest, I have only dabbled recently, it's been a while since I kept up with the science precisely.
(No asking poster, Asking in general)
Read this and also this.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Read my Hboot guide in my sig, and also check out the guide on how to fix your phone after a system wipe. I think you'll find what you're looking for.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
JukeRedlin said:
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
Click to expand...
Click to collapse
You got it:good:
Anything else, just ask.
JukeRedlin said:
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
Click to expand...
Click to collapse
Up and Running on Mean Bean, should be able to get anywhere I need from here. Thanks Fin, and all who helped before~
Not a problem.
Sent from my HTC EVO 4G LTE
This is a working build of CWM recovery.
Thank you to those you have confirmed everything working.
credit goes to utkanos he made this.
if you decide to continue building from this, no need to ask, just give utkanos credit
device tree if you want to continue to work from this:
https://github.com/utkanos/android_device_htc_fireball
download link
http://dl.dropbox.com/u/26383143/HTC Incredible 4G/fireball4.img
Has anyone tried this?
droid10 said:
Has anyone tried this?
Click to expand...
Click to collapse
I can try it when I get home (in about an hour and a half)
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
Flashed, works great.
To access the SD card to flash things, rather than choosing "Choose zip from sdcard" you need to choose "choose zip from external sdcard".
This works just like the regular CWM recovery on the Inc2 (For those that had it) no touch screen aspects of this at all.
For reference (and those lazy)
Boot to the bootloader (when phone is off, hold down power button and Volume Down button till you see the bootloader
OR type this in terminal while phone is on and plugged in (with adb and fastboot)
Code:
adb reboot bootloader
once in bootloader, and makesure fireball4.img is in the same folder you are working in
Code:
fastboot flash recovery fireball4.img
Code:
fastboot reboot
- Or choose "reboot" in the bootloader.
And now you have the recovery. To access it (while phone is fully booted):
Code:
adb reboot recovery
It works perfectly. Thanks
this works perfectly. i tried twrp but its not for me im used to ext4 but ive also used cwm in the past with my og inc.thanks for this
---------- Post added at 02:17 PM ---------- Previous post was at 02:06 PM ----------
I'm looking in the download section of Rom manager and I gotta ask is this from the dinc 2
Linch89 said:
this works perfectly. i tried twrp but its not for me im used to ext4 but ive also used cwm in the past with my og inc.thanks for this
---------- Post added at 02:17 PM ---------- Previous post was at 02:06 PM ----------
I'm looking in the download section of Rom manager and I gotta ask is this from the dinc 2
Click to expand...
Click to collapse
im confused by your question?
a recovery is unique to a phone
u can go ahead and try to run an inc2 recovery on your phone and see what happens, but i don't suggest it lol.
i also didn't build this, I asked utkanos and he did it.
I haven't tried/put in any effort to build a recovery.
I'd like to get the soft keys working on this.
andybones said:
im confused by your question?
a recovery is unique to a phone
u can go ahead and try to run an inc2 recovery on your phone and see what happens, but i don't suggest it lol.
i also didn't build this, I asked utkanos and he did it.
I haven't tried/put in any effort to build a recovery.
I'd like to get the soft keys working on this.
Click to expand...
Click to collapse
I'm guessing he means he was using a CWM recovery on his OG Dinc. I also used the CWM recovery on my OG Dinc and was very happy with it on that phone. CWM did all I needed and worked very well with the pro version of ROM Manger to do scheduled Nandroid backups. Based on that experience, I'm leaning towards using CWM, too. (FWIW, I'm also using a CWM build on my Kindle Fire, too)
This is why I asked if he built it from the dinc2 just curious
Linch89 said:
This is why I asked if he built it from the dinc2 just curious
Click to expand...
Click to collapse
sorry I'm still confused
andybones said:
sorry I'm still confused
Click to expand...
Click to collapse
Who's on first?
Jafmf95 said:
Who's on first?
Click to expand...
Click to collapse
Yes
junkmail9 said:
Yes
Click to expand...
Click to collapse
Bacon
Lemon meringue pie.
andybones said:
sorry I'm still confused
Click to expand...
Click to collapse
If you look at his screenshot, you'll notice that ROM Manager thinks his phone is the Inc2. That's why he's asking.
mdmower said:
If you look at his screenshot, you'll notice that ROM Manager thinks his phone is the Inc2. That's why he's asking.
Click to expand...
Click to collapse
Great catch. I missed that entirely. That could create a bit of a problem if he tries to install a ROM. Sounds like a question for Koush.
I checked the download section of Rom manager for ****s and gigs and that's what I found. Secretly, I was hoping that cm would magically be in there
I don't use ROM manager... I manage my own ROMs
andybones said:
I don't use ROM manager... I manage my own ROMs
Click to expand...
Click to collapse
Sure. I never installed any ROMs from it, either, but the automated nandroid back up feature is nice.
Sent from my Fireball using Xparent Blue Tapatalk 2
have you got the device tree that was used to build this?
Lloir said:
have you got the device tree that was used to build this?
Click to expand...
Click to collapse
here is the device tree
https://github.com/utkanos/android_device_htc_fireball
Hello all,
New to the HTC One and hit the wrong damn box going to quickly and deleted the OS. Device shows "unlocked, tampered". In TWRP I can transfer a rom with my Mac using ADB side load. But when trying to install the rom.zip it fails automatically. Android Revolution is the rom I'm trying to install. Is there a way to just install stock ATT 4.4.2 and start fresh? Edit: Just tried flashing a rom from external sd with no luck either.
Anybody?
Can get to bootloader mode?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
godofwar762 said:
Can get to bootloader mode?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I can get to boot loader. The phone is recognized through ADB and through fast boot. Just have no clue how to get an OS back on the phone, just got the phone and hadn't done a backup since there wasn't anything on it yet. (stupid me)...Can I use the stock backup from this thread?
http://forum.xda-developers.com/showthread.php?t=2701376
Anybody got any ideas to nudge me in the right direction would be very much appreciated!
http://forum.xda-developers.com/showthread.php?t=2721435 I would try this and when u flash the zip in the RUU just get into recovery and wipe big 3 and flash a sense Rom.
---------- Post added at 04:03 AM ---------- Previous post was at 03:59 AM ----------
Be sure get s-off too
Sent from my HTC One_M8 using XDA Premium 4 mobile app
godofwar762 said:
http://forum.xda-developers.com/showthread.php?t=2721435 I would try this and when u flash the zip in the RUU just get into recovery and wipe big 3 and flash a sense Rom.
---------- Post added at 04:03 AM ---------- Previous post was at 03:59 AM ----------
Be sure get s-off too
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've been reading about the RUU mode but how exactly do I go about it? I downloaded a stock backup from Mr. Hofs post based off my CCID, I'm just not sure how to get my phone back up and running:/ Just want to get it back to stock and I'll leave it alone.
Currently there isn't a RUU for stock sense just stock android for the GPE edition . Only way to get a stock Rom is to flash a recovery back up after u do the steps in that Thread .
Sent from my HTC One_M8 using XDA Premium 4 mobile app
godofwar762 said:
Currently there isn't a RUU for stock sense just stock android for the GPE edition . Only way to get a stock Rom is to flash a recovery back up after u do the steps in that Thread .
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What about just flashing a custom rom then?
Try to just mount in TWRP (not sideload) and adb push the custom ROM of your choice to the phone storage.
Not sure if this will put you in any better position. But its worth a try.
redpoint73 said:
Try to just mount in TWRP (not sideload) and adb push the custom ROM of your choice to the phone storage.
Not sure if this will put you in any better position. But its worth a try.
Click to expand...
Click to collapse
I will try and just push the rom over but what do you mean by "just mount inTWRP?".
maclem8223 said:
I will try and just push the rom over but what do you mean by "just mount inTWRP?".
Click to expand...
Click to collapse
The is an actual "Mount" button on the TWRP homescreen. But it should already be setup by default (you can check in the "Mount" options) to mount the phone's data partition when you boot into TWRP and have USB connected.
After you've pushed the ROM to the phone's memory, install from TWRP the "usual" way. I think I've seen there this method has worked for people when ADB sideload did not (on my old EVITA). So hopefully this will work for you.
I did the same thing. I downloaded the custom ROM to internal memory .. popped into TWRP .. .. .. formatted all memory (INCLUDING Internal) .. then had 3.23454542234 seconds of wondering where my ROM was. LOL
All I did was copy the ROM to a MicroSD card (from a different PC with Micro to SD adaptor) .. installed the MicroSD card into the phone .. then flashed from the MicroSD card .. no worries. Easy Pasy!
EDIT: I see you tried. I also loaded Android Revolution .. I think you might want to try downloading the ROM again? I can confirm that I used that exact ROM and did the same thing of deleting the OS.
wattsja said:
I did the same thing. I downloaded the custom ROM to internal memory .. popped into TWRP .. .. .. formatted all memory (INCLUDING Internal) .. then had 3.23454542234 seconds of wondering where my ROM was. LOL
All I did was copy the ROM to a MicroSD card (from a different PC with Micro to SD adaptor) .. installed the MicroSD card into the phone .. then flashed from the MicroSD card .. no worries. Easy Pasy!
EDIT: I see you tried. I also loaded Android Revolution .. I think you might want to try downloading the ROM again? I can confirm that I used that exact ROM and did the same thing of deleting the OS.
Click to expand...
Click to collapse
Thank you, that's what I'm working on now but the MD5's checked out.
redpoint73 said:
The is an actual "Mount" button on the TWRP homescreen. But it should already be setup by default (you can check in the "Mount" options) to mount the phone's data partition when you boot into TWRP and have USB connected.
After you've pushed the ROM to the phone's memory, install from TWRP the "usual" way. I think I've seen there this method has worked for people when ADB sideload did not (on my old EVITA). So hopefully this will work for you.
Click to expand...
Click to collapse
Not sure if the push is working.... ./adb push rom.zip /sdcard/data/media
I hit enter and the terminal just sits there so I'm not sure if I'm doing it correctly.
Put rom on external sd and install unless TWRP dont see external yet. ALways did this on my last few phones.
maclem8223 said:
Not sure if the push is working.... ./adb push rom.zip /sdcard/data/media
I hit enter and the terminal just sits there so I'm not sure if I'm doing it correctly.
Click to expand...
Click to collapse
A lot of ROMs are almost 2 GB (depending on which ROM, of course). So it takes some time to transfer over.
If there is no error message right away, it might be a good sign its being moved over.
---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------
JayRolla said:
Put rom on external sd and install unless TWRP dont see external yet. ALways did this on my last few phones.
Click to expand...
Click to collapse
He already tried this, and response #13 above suggested the same thing.
redpoint73 said:
A lot of ROMs are almost 2 GB (depending on which ROM, of course). So it takes some time to transfer over.
If there is no error message right away, it might be a good sign its being moved over.
---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------
He already tried this, and response #13 above suggested the same thing.
Click to expand...
Click to collapse
It was a sideload issue the whole time. Pushed Android_Revolution and it installed. Now it's rebooting I hope, been on the HTC One screen for awhile?EDIT: All set folks, thank you so much for the help! No OS is still showing in boot loader though.
maclem8223 said:
It was a sideload issue the whole time. Pushed Android_Revolution and it installed. Now it's rebooting I hope, been on the HTC One screen for awhile?
Click to expand...
Click to collapse
First boot after a flash takes a while. Maybe a few minutes (didn't keep track). Wait 5 or 10 minutes before you panic.
---------- Post added at 02:59 PM ---------- Previous post was at 02:27 PM ----------
maclem8223 said:
EDIT: All set folks, thank you so much for the help! No OS is still showing in boot loader though.
Click to expand...
Click to collapse
Please click the "Thanks" button for any posts you found helpful.
I don't show any OS number in bootloader either, and I am also on Android Revolution. Don't know if it was the same when I was on GoldenEye.
redpoint73 said:
First boot after a flash takes a while. Maybe a few minutes (didn't keep track). Wait 5 or 10 minutes before you panic.
---------- Post added at 02:59 PM ---------- Previous post was at 02:27 PM ----------
Please click the "Thanks" button for any posts you found helpful.
I don't show any OS number in bootloader either, and I am also on Android Revolution. Don't know if it was the same when I was on GoldenEye.
Click to expand...
Click to collapse
Made a nandroid backup so now I'm happy. Thanks again!
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
kvip60 said:
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
Click to expand...
Click to collapse
What's the easiest way to install this?
I didn't install it I just used" fastboot boot image-name"
kvip60 said:
I didn't install it I just used" fastboot boot image-name"
Click to expand...
Click to collapse
Ok Thanks. I am in and generating a backup. The touch screen was working for me mostly. It won't let me select Micro SDCard to save my backup.
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
kvip60 said:
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
Click to expand...
Click to collapse
What I did to navigate was I had to push the power button then it would bring the screen up where you can swipe the bottom to unlock the screen and use touchscreen. Navigating the storage was odd because it shows it is stuck on Internal storage, but If i click on SDCard, it will take me to that directory. I hope there is a nice update to this is the near future, so we don't have to access it through "adb reboot recovery"
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
kvip60 said:
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
Click to expand...
Click to collapse
Oh man you were so right. I had it flashed and it caused me all kinds of problems, like booting the screen upside down etc. I was finally able to find the recovery.img in another thread and get back the stock recovery. I think I will also wait until there is a more stable TWRP version.
I always use boot to test and I always backup my recovery before flashing because I had that happen to me before
Any idea on when a decent working custom recovery will be available?
blahforme said:
Any idea on when a decent working custom recovery will be available?
Click to expand...
Click to collapse
Probably when someone will have the will & time to work on it.
Maybe you'd like to take on this topic?
Lol. I hear you. I have very little understanding of Linux I have tried to make one but there aren't enough information about compiling device /vendor tree for a new device to go on
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
lssong99 said:
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
Click to expand...
Click to collapse
Thanks for this. Posting the Mega so people don't have to make an Asus account to grab it.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
The 20170218 recovery works perfectly with my phone (6/64gb, 820). The first one posted in the OP worked, but was a bit glitchy. The updated one has working SD reading and touchscreen works without having to lock it first.
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
blahforme said:
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
Click to expand...
Click to collapse
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
I am using 821 my screen is flipped and no touch even after locking it
Huffy1 said:
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
Click to expand...
Click to collapse
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
blahforme said:
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
Click to expand...
Click to collapse
How did you install Magisk having stock recovery? Using the in-app installation?
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
It seems @EypCnn is the developer of this TWRP builds...
sebastiandg7 said:
How did you install Magisk having stock recovery? Using the in-app installation?
Click to expand...
Click to collapse
I flashed Magisk v11.1 with TWRP, then installed Magisk Manager from the Google Play Store, after I rebooted my device. I did that by booting in to TWRP with fastboot to flash the .zip file. I did not flash TWRP to install Magisk.