Related
Starting from a new stock Desire HD, I have attempted gaining root access using Visionary (r14). Temproot worked, but permroot apparently failed. My device rebooted, but didn't come back up - I get the phone-with-red-triangle screen.
If I pull the battery and then boot into the bootloader, using the Image CRC menu option I can see that my system partition has been modified (but all other partitions are unchanged):
<redacted>
Do I have any options available to me now, or am I screwed?
My phone is a stock Desire HD A9191 (stock HBOOT S-ON, stock recovery, stock radio S-ON):
Code:
Branded (Vodafone Australia)
<redacted>
Is there magic process that can be done to re-flash the faulty system partition?
Any help would be hugely appreciated. Sorry to make this my first post to the forums, but I'm well and truely stuck... hopefully not permanently, but I have that sinking feeling
What happens when on the red triangle screen, you HOLD the volume up, and then press power button? I think this will take you to stock recovery. Reboot if you have the option, or Wipe data & factory reset.
Sent from my Desire HD using XDA App
Thanks UpInTheAir.
At the red-triangle screen I press vol-up and power, and it displays the Android system recovery screen. It shows the options:
1 Reboot system now
2 Apply sdcard:update.zip
3 Wipe data/factory reset
4 Wipe cache partition
I've tried (3) and (4) and then rebooted, but it does not help - the phone continues to boot into the red-triangle screen.
It looks to me like the system partition was incorrectly modified / corrupted by visionary, and somehow flashing it back to a known-good condition seems like the only way forward...
Is it possible to use option (2) to flash a new rom if I package it up and put it on the SD card somehow? My phone is branded vodafone-australia, and they have not published any RUU update files yet. I gather that using a WWE rom update from HTC will not be possible?
Try DL think stock 1.32 RUU
Rename to PD98IMG.zip (not .zip.zip, do not extract)
Put PD98IMG.zip onto sdcard
HOLD volume down, and power on -> this will boot into Bootloader
Start update and follow the prompts
I hope this helps, but as always, please don't hold me responsible if anything goes pear-shaped.
Thanks again. Downloading now, and will update this post when I've tried it out. Cheers.
You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)
a33a said:
You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)
Click to expand...
Click to collapse
Won't the Gold Card be useless if the system partition is already corrupted?
This was to be done before using visionary?
Thanks a33a.
My phone doesn't boot (I can only get to the bootloader menu, or the red-triangle screen). I tried talking to it with ADB, but it says "device offline".
The instructions for making a gold-card appear to require you using adb to talk to the phone to get it to tell you some long id number... I don't think it's possible for me to do this.
Is there a work around or some other way?
Did the PD98IMG.zip work?
Did u update the HTC drivers for the usb before. The adb needs the latest drivers for Windows to communicate.
If u can't create a goldcard than u should try and borrow 1 from a friend that already rooted his dhd. It might work that way. If not than u have to bring it to HTC and have it reflash.
When you tried ADB;
1. Make sure your phone is in FASTBOOT USB (HOLD volume down + power on -> Bootloader)
2. Connect to PC
3. CMD (Command Prompt) cd\............android\android-sdk-windows\tools\ (or whewrever the adb.exe & fastboot.exe is)
4. Type fastboot devices
5. You should get pyour device serial number HT............
But as I said, if the partition is screwed up, it is pointless with the goldcard?........
Edit: Memory coming back......You only need the Gold Card if you flash a stock ROM and require OTA updates? Without this you can't get the updates. So not having it shouldn't stop the flash?
Unfortunately the PD98IMG.zip did not work.
As suspected, the bootloader found it, loaded it, checked it, then displayed:
Code:
CID incorrect!
Update Fail!
Press <POWER> to reboot.
I haven't tried creating the gold card yet. I'm not holding out much hope, because with the device not booting into the OS, I don't think you can get adb to connect.
When the phone was working, I was able to use ADB to install apps and run commands from the shell, so I'm pretty sure the USB drivers are OK (I've installed the latest HTC Sync, which included the usb drivers and adb.exe).
I don't know anyone with another Desire HD, let alone anyone who has created a gold card... maybe someone on here with one can zip up the files and send them to me?
Did you try through fastboot? Sorry I don't have one as wasn't carrier branded. I never had intention to keep the stock, so never bothered. I will keep an eye open for ideas though.
I suppose you would get the same if you rename it to update.zip & try flash through the recovery / update. My guess is yes, but doesn't hurt to try?
Sent from my Desire HD using XDA App
I'm just trying the fastboot method now (downloading and installing the SDK as I type).
I'll let you know how it goes.
Thanks for sticking around to help out.
If no good, look on the bright side. There will be no evidence on your phone about the attempted root, still s-on etc. With the system partition corrupt, you could send it back and claim ignorance, not sure what happened. I would think you would have a very goof chance of repair (htc flash) or replacement.
Well hope you have some luck first though.
Edit: meant s-on
Sent from my Desire HD using XDA App
Yeah, I was considering that -- all partitions except system are unmodified and stock, and both S-flags are S-ON. Using the bootloader to wipe cache and data, should erase any evidence that I was attempting to root the phone.
Fingers crossed they will replace / repair under warranty -- if it comes to that!
Okay, as per the earlier post, I've put the phone into FASTBOOT USB mode, and used the Android SDK fastboot.exe program, which gave me back a 12 digit number beginning with "HTxxxxxxxxxx".
However, the linked gold-card creation guide says to run "adb shell cat /sys/... " which does not work -- adb returns "error: device not found". Presumably this is because you can't talk to the phone when it's in the bootloader.
What should I do with the "HTxxxxxxxxxx" value? The goldcard guide doesn't mention it as far as I can tell...
That's your device serial number, meaning you can ay least talk with it via fastboot. Try substituting 'fastboot' instead of 'adb'. Your connected in Fastboot, ADB command is when your phone is powered up and connected in charge only, usb debugging enabled.
Sent from my Desire HD using XDA App
Okay, I've tried a couple more things:
Renaming PD98IMG.zip to update.zip and selecting "Apply sdcard:update.zip" from the recovery menu. This failed, displaying "E:Can't open /cache/recovery/command ---- invalid operation ----"
Then I tried issuing ADB commands using fastboot.exe, but fastboot doesn't support the shell parameter, so "fastboot shell cat /sys/...." doesn't work.
It does look like fastboot can be used to flash various parts of the device though... I wonder if this is worth looking into a bit more?
ie: fastboot's usage output says:
Code:
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
I tried "fastboot update update.zip" giving it the renamed PD98IMG.zip file, but it complained of:
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '....garbage characters...'
Does anyone know how and what to feed to fastboot to get to force-flash the system partition?
UPDATE: yeah I thought this might have been too easy... This link suggests that you can't flash a production device with fastboot unless you already have ENG S-OFF (which I don't).
http://wiki.cyanogenmod.com/index.php?title=Fastboot
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery
haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found
haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)
mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either
haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,
Hey!
So here's the deal:
I'm running LiquidSmooth ROM (KK Version) and I was trying to update the ROM to the newest Lollipop version, but it kept failing. No big deal, i nandroid backed up, and then did a total wipe and tried again. Failed.
Okay, maybe my TWRP recovery was out of date, i tried updating it using the official TWRP app...
then everything went wrong. The install failed and now whenever i ask my phone to go into recovery mode, it sends me into HBoot. I've been trying for 3 days to figure this out, and i cant, so any help would be greatly appreciated.
Im not incredibly well versed at this stuff, so it might have to be a dummy's guide.
in the meantime, here are the details...
When i try to flash ANY custom recovery using ROM Installer app, here is what the error message says:
"COMMAND:
flash image recovery /storage/emulated/legacy/romtoolbox/recoveries/openrecovery-twrp-2.7.1.0-m8.img"
"OUTPUT:
/dev/block/mmcblk0p34: write error: No space left on device
3+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs"
And when i try to reboot into RECOVERY (and it sends me into BOOTLOADER instead), here is the information it gives me:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO - 1.14.21331931.LA02_2G
OpenDSP - v32.2.2-00542-m8974.0213
OS -
eMMC-boot 2048MB
JUNE 16 2014 18:47:55
FASTBOOT USB
thank you so much in advance. i have NO idea what happened... i know the fact that i have S-On might have something to do with it, but i dont have access to a PC, only MACs and i can't use the Sunshine app because i'm already running a custom rom. What can i do?
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Magnum_Enforcer said:
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
Click to expand...
Click to collapse
I'll try to flash it from bootloader! Could you tell me how to place the recovery img file into my adb folder? Thank you!!!
nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
jball said:
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
Click to expand...
Click to collapse
What is DD method? Thank you so much for your help
karmendc said:
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
Click to expand...
Click to collapse
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
karmendc said:
What is DD method? Thank you so much for your help
Click to expand...
Click to collapse
dd is a method using a terminal emulator on your device.
The screenshot is from the twrp website and the "dd" method is described as a working method if in fact you can boot to the OS (SuperSU is needed)
jball said:
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
Click to expand...
Click to collapse
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
jball said:
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
Click to expand...
Click to collapse
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for the more detailed information.
Small keyboards blow for sure.
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
gazzacbr said:
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
Click to expand...
Click to collapse
Thank you for the second opinion kind sir.
http://www.youtube.com/watch?v=JUCM_tJaNHU
Here is a short video on how to input the "fastboot flash recovery recovery.img " command once you have drivers correctly installed and the img file in the proper location .
Now this video is from a tablet to my HTC one m8 and not from a
PC/Desktop as it's over obvious.
Just like all other videos I don't show how to "easily" set up the drivers for fastboot (oh that's cause you don't need drivers to adb or fastboot from a tablet to a phone).
nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Okay so i finally tried flashing it using Terminal/FASTBOOT... I downloaded the latest TWRP recovery for GSM, placed it in my adb/fastboot folder...and typed in the command and it came up with an error. Here are the screenshots. Help? Im at my wits end.... thank you in advance!
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
karmendc said:
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
Click to expand...
Click to collapse
1) you're on hboot 3.18 so that would indicate you firmware (the OS- line or version-main from a fastboot getvar all) is still 2.xx.xxx.x version, so yes, you're going to have signal and wifi problems, as mentioned in the various ROM threads you need matching firmware to the ROM you're running.
2) this could also be the reason it's not entering the recovery, you could try an older version of TWRP, and make sure MD5 checks out on your download, a corrupt download could also be the reason
3) the "fastboot erase cache" doesnt affect your internal storage or anything, it just wipes the cache which will get rebuilt as needed
4) missing/not mounted internal storage, is a common issue on Android 5.x (not only HTC, many devices), download a terminal emulator to your phone (or alternatively open an abd shell), and do the following commands:
Code:
su
restorecon -FR /data/media/0
Below is the official RUU. This zip can be flashed via fastboot/RUU mode or via SD card. It is NOT rooted. This will be especially useful for users who want to relock/s-on in order to sell or return their phone. Once you have your bootloader locked and tamper flag cleared you can turn s on. Then you can flash this RUU to remove any/all traces of root. This ruu WILL wipe internal storage or data. This RUU is NOT ROOTED! This also can be beneficial for going back to stock to take an OTA.
Remember - You cannot downgrade firmware unless s-off!!!
Option 1
Copy 0PJAIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
Boot to download mode
-or. -
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
HTC_fastboot flash zip 0PJAIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 10 minute plus first boot!
Downloads (Do NOT mirror these elsewhere)
RUU.zip
- https://www.androidfilehost.com/?fid=24052804347760882
RUU mode TWRP 2.8.6.4
- https://www.androidfilehost.com/?fid=96042739161893114
Fastboot/adb zip that works for this phone
- https://www.androidfilehost.com/?fid=95916177934554784
Here's a firmware.zip for us too...
https://www.androidfilehost.com/?fid=24052804347760858
RETURN to locked/S-on
Assuming you still have TWRP flashed to your device boot it to TWRP and connect to your PC. Open a cmd prompt from your ADB/fastboot path. Cut, copy, and paste the long command.
Adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot-bootloader
verify bootloader is now "locked"
Flash RUU. As long as phone boots and shows no signs of tampering you set s back to on by booting phone to download mode and issuing the following fastboot command from your PC.
fastboot oem writesecureflag 3
fastboot reboot-bootloader
verify s-on/locked.
Thanks for sharing @dottat! Will hopefully be needing this soon to take the next OTA.
If we use this ruu back to stock to receive the hopefully coming soon Ota... One question? Will we need to send our phones out to you again to get unlocked bootloader and root and s off? Or is there a process for us who have twrp s off unlocked bootloader and root currently to receive the Ota and then get back to flashing our hearts out again?
magesticschu said:
If we use this ruu back to stock to receive the hopefully coming soon Ota... One question? Will we need to send our phones out to you again to get unlocked bootloader and root and s off? Or is there a process for us who have twrp s off unlocked bootloader and root currently to receive the Ota and then get back to flashing our hearts out again?
Click to expand...
Click to collapse
You can flash this all you want. Won't affect s status or bootlaoder status unless you run the commands yourself to revert.
Sent from my HTC6535LVW using Tapatalk
magesticschu said:
If we use this ruu back to stock to receive the hopefully coming soon Ota... One question? Will we need to send our phones out to you again to get unlocked bootloader and root and s off? Or is there a process for us who have twrp s off unlocked bootloader and root currently to receive the Ota and then get back to flashing our hearts out again?
Click to expand...
Click to collapse
As for OTA. Usually an OTA won't set your phone back to S-ON (not sure if one ever has TBH), but there is always a possibility, so hopefully someone like Doug with a Java Card can be the brave soul to try it and find out for the rest of us.
Or depending on how the OTA is put together we can pull the firmware.zip - then you simple flash the firmware.zip in fastboot, then wait for a DEV to put out a stock ROM (or the ROM of your choice) based off the new OTA and you are now up-to-date.
lock unlock
" RETURN to locked/S-on
Assuming you still have TWRP flashed to your device boot it to TWRP and connect to your PC. Open a cmd prompt from your ADB/fastboot path. Cut, copy, and paste the long command.
Adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot-bootloader
verify bootloader is now 'locked' "
Thank you for these gems! WooHoo RUU!
Is there a command to unlock bootloader similar to the above 'lock' command?
michaelbsheldon said:
" RETURN to locked/S-on
Assuming you still have TWRP flashed to your device boot it to TWRP and connect to your PC. Open a cmd prompt from your ADB/fastboot path. Cut, copy, and paste the long command.
Adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot-bootloader
verify bootloader is now 'locked' "
Thank you for these gems! WooHoo RUU!
Is there a command to unlock bootloader similar to the above 'lock' command?
Click to expand...
Click to collapse
Yes but give me a real world reason why you would need it
Sent from my HTC6535LVW using Tapatalk
michaelbsheldon said:
" RETURN to locked/S-on
Assuming you still have TWRP flashed to your device boot it to TWRP and connect to your PC. Open a cmd prompt from your ADB/fastboot path. Cut, copy, and paste the long command.
Adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
adb reboot-bootloader
verify bootloader is now 'locked' "
Thank you for these gems! WooHoo RUU!
Is there a command to unlock bootloader similar to the above 'lock' command?
Click to expand...
Click to collapse
Google is your friend man..
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
thanks,hope you next OTA zip.
Would it be possible to root the ruu to achieve root for non s-off users? I remember seeing rooted ruus for the m8. I'm just curious if it's a future possibility for us who can't ship there phone out.
squito said:
Would it be possible to root the ruu to achieve root for non s-off users? I remember seeing rooted ruus for the m8. I'm just curious if it's a future possibility for us who can't ship there phone out.
Click to expand...
Click to collapse
You would not be able to flash a rooted RUU if you are S-On, because that RUU would not be signed.
The rooted ones for the M8 could only be flashed if you were already S-off.
Ahh okay. thanks for the answer. I wasn't sure what was possible.
what is 2.6.605.10, where can i got this ota ?
xchang168 said:
what is 2.6.605.10, where can i got this ota ?
Click to expand...
Click to collapse
That is the 5.1 base. The OTA isn't available yet. You will need to flash a ROM and firmware in order to get it.
Look at @ΠΣΘ or @andybones threads for both the firmware and ROMs that you need.
dottat said:
Below is the official RUU. This zip can be flashed via fastboot/RUU mode or via SD card. It is NOT rooted. ... This RUU is NOT ROOTED!
Click to expand...
Click to collapse
So keep a copy of SuperSu handy so it can be flashed too ?
dottat said:
Here's a firmware.zip for us too...
Click to expand...
Click to collapse
dottat said:
Actually the ruu will download it firmware and all to the stock shipped os/firmware. Then you can update the firmware using this zip again. Then boot to recovery and try to flash rom again.
Click to expand...
Click to collapse
Just to make sure I'm doing this right, I flash the RUU and I will have the old, but matching firmware ? Then flash the 2.6.605.10 firmware from Neo's thread like I did earlier ? After that, I can try Viper ROM again or Neo's modified stock ROM ?
Sorry for all of the questions
hallstevenson said:
So keep a copy of SuperSu handy so it can be flashed too ?
Just to make sure I'm doing this right, I flash the RUU and I will have the old, but matching firmware ? Then flash the 2.6.605.10 firmware from Neo's thread like I did earlier ? After that, I can try Viper ROM again or Neo's modified stock ROM ?
Sorry for all of the questions
Click to expand...
Click to collapse
Yes yes and yes.
Sent from my HTC6535LVW using Tapatalk
Little donation for this great man Confirmation number: 1MX30407S6169811K He surely deserves it and more for all his help and for always providing us with an ruu, we are lucky to have him cause HTC and Verizon won't give it up! Lol. I hope others who can afford it can buy him a few rounds!
im getting this
c:\adb>fastboot flash zip 0PJAIMG.zip
load_file: could not allocate -1890934261 bytes
error: cannot load '0PJAIMG.zip'
i am on 5.1 firmware. md5 checks out. wondering what to try next? restarted fastboot, replaced ruu zip, still same error.
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.