if you had your phone s offed by sonic's java card,a result of the diag file "s58 data clean" is a change of your MID(Model ID) to a superMID of sorts: PN073****
this has an advantage of allowing htcdev unlock without changing cid,but with s off, the bootloader can easily be unlocked without htcdev,so that is not of much importance.
since we dont know for sure if any future activities(turning s on,accepting OTAs,etc) will be affected by a non stock MID,it may be worthwhile to return the MID to stock PN0731000 "just in case"
this thread is for the folks who wish to revert to stock MID. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)restore your verizon MID
warning: *do not try and type the command. please copy and paste it
enter the following:
adb shell
su (if needed to get a #)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
exit (<- only if needed to get back to your normal > prompt)
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0731000 for modelid
fastboot reboot
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links if you have a java card s offed phone:
remove your tampered banner
unlock/lock without htcdev
mine
@scotty1223 you are the Man!
Thank you SO much for these things!
Honestly makes the phone seriously, THAT much better!!
I finally feel safe with Stock MID/CID :good:
andybones said:
I finally feel safe with Stock MID/CID :good:
Click to expand...
Click to collapse
i agree completely. now i can look forward to dumpng one X partitions and looking for all the flags again,since tegra 3 layout is different,lol.
i want to revert my own funky MID on it and lock/unlock etc
Don't you have to be in su ( # ) prompt , i didn't see that in the instructions prior to inputting the command but i did see it in the copy/pasted results?
carm01 said:
Don't you have to be in su ( # ) prompt , i didn't see that in the instructions prior to inputting the command but i did see it in the copy/pasted results?
Click to expand...
Click to collapse
The very first command... adb shell
Sent from my HTC One using Tapatalk
edit: to elaborate a little,the adb shell command will sometimes get you the # prompt. sometimes it will give you a shell with no root access,or a $
if adb shell gets you a $,then you will need to enter su to get the #,and have your phone awake and watching for a pop up to grant permissions. ill add that to the OP to clarify a bit
Yea, I was hoping you would post it in the op as you know some newbies might not catch that or know that if they are not paying attention and get all excited ...lol
Sent from my HTC6500LVW using xda app-developers app
Just got back Scotty, great work again as I see! Thanks for all the time put in for us!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Related
Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?
NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Just remember to keep s-off while running the ruu
So I am completely out of ideas. I hope someone else’s input can solve whatever is going on here.
I am trying to gain permanent root, meaning getting s-off and unlocking the bootloader. I have a HTC One M7 from Verizon, so already have an uphill battle. I had a previous rooted phone, but the sound card died and I had to exchange and get a replacement. Hence, I am not rooted anymore.
Here are my current phone spec’s:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) meid: XXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4247mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now I have tried pretty much every which way I have found to try and gain S-off without using HTCDev. The most promising method it seems from other’s posts on the subject has been the weaksauce and firewater method. However, when I try this method, I get nowhere. I gain temp root with weaksauce no problem. It automatically re-temp-roots after a system reboot, that part works great. It’s the firewater aspect which is the issue.
Since I haven’t taken the most recent update to Sense 6.0 my thought was firewater would still work on my device. Is this wrong?
If it isn’t, then after issuing these commands in my command prompt (with a completely fresh version of ADB/Fastboot and HTC Drivers without HTC Sync):
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
I get this as the response:
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\Program Files (x86)\Minimal ADB and Fastboot>
This occurs every time, and the only thing which differs is my phone will either reboot itself after it stops running firewater, or will hang and need to be manually rebooted.
On other people’s posts with issues gaining S-off with this method they usually are about opening numerous bottles and such, and having to run firewater a number of times before getting the exploit to work. At this point I have probably run the firewater scenario about 50 times. I am at my wits end.
I HATE blinkfeed, even seeing anything about it pisses me off…this is reason #1 why I want to root, to get rid of it, but also I am very particular about how efficient my phone runs, because some days I need it to be fully functional for more than 16 hours, and at stock that’s a pipe dream.
So ideas anyone???
Please……
Do a factory reset on your phone. Have no lockscreens or other security options set.
Make sure you have it connected to WiFi.
Make sure you have got Developer Options set and USB debugging set.
Send Weaksauce to yourself thru GMail.
Open the Weaksauce attachment in GMail and install Weaksauce.
Install SuperSU
Reboot and make sure you're still rooted.
Connect to Windows computer.
Make sure you say "Yes" to connection prompt on your phone.
Now run Firewater and see if it goes all the way.
Boo Tried that....
michaelbsheldon said:
Do a factory reset on your phone. Have no lockscreens or other security options set.
Make sure you have it connected to WiFi.
Make sure you have got Developer Options set and USB debugging set.
Send Weaksauce to yourself thru GMail.
Open the Weaksauce attachment in GMail and install Weaksauce.
Install SuperSU
Reboot and make sure you're still rooted.
Connect to Windows computer.
Make sure you say "Yes" to connection prompt on your phone.
Now run Firewater and see if it goes all the way.
Click to expand...
Click to collapse
Thanks for the quick reply however...
Do a factory reset on your phone. Have no lockscreens or other security options set. - Have done this, multiple times, I can't remember how many at this point :crying:
Make sure you have it connected to WiFi. - Have tried 3 different settings, wifi only, phone network only (4G), and both activated (which is what my default is) which is WiFi when I am at home, which all my attempts have been. :crying:
Make sure you have got Developer Options set and USB debugging set. - Yup and Yup
Send Weaksauce to yourself thru GMail. - Yep, did this a few days ago as it was suggested in another post I found as possible solutions to problems getting Firewater to work
Open the Weaksauce attachment in GMail and install Weaksauce. - Did this as part of the above step
Reboot and make sure you're still rooted. - When I reboot I've been using command prompt: adb reboot, should I be rebooting manually?
Connect to Windows computer. - since I have been using the prompt to issue the reboot, I have already been connected to my Windows 7 computer via the original HTC usb, no hubs, and have tried all 3 USB ports on my computer....
Make sure you say "Yes" to connection prompt on your phone. - Ok this is interesting, because I have never seen a connection prompt on my phone asking me to say yes to anything...what would I be looking for in terms of permissions? Since I have been trying to gain S-off after every factory reset I have basically put all developer options I can, and temp root/SuperSU commands to automatically run without prompt, could this be why?
Now run Firewater and see if it goes all the way. - one thing I haven't been able to find anywhere is exactly the verbiage as to what will show up when firewater is working. If my understanding is correct it can go through any number of 'bottles' but then typically will display some kind of confirmation in command prompt, is this correct or have I been looking for something which wouldn't happen anyway?
I hope I'm not coming across as unappreciative, because I AM, SO VERY MUCH!!!!!
I didn't include all the steps I have already taken in the original post because I was trying to not confuse what my actual issue was. It's a trick I find works when you want to get the right people's attention as I posted, and read posts on XDA. By keeping new question/troubleshooting threads explanatory of the issue yet concise and elaborate as needed in replies. So thank you so very much for the reply, but unfortunately for me, as you can see, I've pretty much tried all you suggested.
I will try right now to do the reboot without my phone connected to my computer to see if that changes anything. Pending that....?
If your running kitkat then I think it's not possible. I've been trolling the web for weeks for a new exploit, but I think they patched all the exiting ones, firewater,weaksauce,rumrunner. They also have htcdev unlock restricted. If you figure that it out please share!!!
hey
Make sure you say "Yes" to connection prompt on your phone. - Ok this is interesting, because I have never seen a connection prompt on my phone asking me to say yes to anything...what would I be looking for in terms of permissions? Since I have been trying to gain S-off after every factory reset I have basically put all developer options I can, and temp root/SuperSU commands to automatically run without prompt, could this be why?
Try another install of your ADB tools, like one from developer.android.com/sdk to obtain newest. My virgin stock M7's give this prompt after typing 'adb devices'. Since it sounds like you're doing it all by the book, SDK tools is the only likely variable.
Now run Firewater and see if it goes all the way. - one thing I haven't been able to find anywhere is exactly the verbiage as to what will show up when firewater is working. If my understanding is correct it can go through any number of 'bottles' but then typically will display some kind of confirmation in command prompt, is this correct or have I been looking for something which wouldn't happen anyway?
It will tell you that your device is now S-0ff and indicate a donation site if you're pleased with the results.
OP, do you have Android version 4.4.2?
Hi All,
I've been a member here for a long time, but now with a new account.
I have a real problem, and I do not know what to do.
Firstly, I am pretty computer literate, but I am lost with phone technology a little. I have a bit of experience flashing ROMS, but I really do not know where to begin.
I bought a HTC ONE M8 for my daughter from eBay (I know... ) and today it seems to have tried an update. This has resulted in bricking my phone. The M8 was (I thought) new, but whatever has happened has screwed things up.
Can someone help me recover from this update failure? I can provide all information from the BOOT screens for you, but as yet, I don't even know what to supply.
Thanks chaps - I know this is the only place that will be able to help as you are all expert.
Simon
Edit: I have installed Android Studio as I have read that this is what I need initially.
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Ratzz2 said:
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Click to expand...
Click to collapse
M8_UL is not a Chinese HTC. I guess your problem is root or previously a rooted device and that is the reason the update failed.
To get to know better about your device, post here fastboot getvar all result minus serial & imei no.
Then we'll see what you need to do ... either roll-back or moving forward with a new Marshmallow stock ROM
Hi, thanks for replying.
I see, I didn't know that M8_UL is not a Chinese HTC - shows how much I know about this kind of stuff!
I will look up how to post the fastboot getvar all information, but if I don't get back to this first, I am assuming (from what I have already read) that I can do this via a CMD window? I am not 100% what I need to download to access my HTC, but will look into it now.
Many thanks again - you have given me a glimmer of hope!
Assuming you have a Windows PC ...
What you need is fastboot/adb, install this : http://forum.xda-developers.com/showthread.php?t=2588979
-when install the adb installer, select Y for system-wide and N for drivers
-you can open Command Prompt from any where that you like when it is system-wide.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Open a command prompt then type fastboot getvar all
copy the output but delete serial & imei no.
Here we go ...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.102s
First - you need this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Since the bootloader is LOCKED, what you can do :
1. Download the RUU zip here : https://www.androidfilehost.com/?fid=24369303960687057
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Then follow these :
Rename the RUU zip to RUU.zip (make sure you don't hide the windows extension so you won't make mistake and rename it to RUU.zip.zip)
put your device on bootloader/fastboot mode (as you get the getvar) and connect to PC
Open a command prompt from RUU folder then run below commands:
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Once complete - fastboot reboot
It should boot, then you run setup .. done.
(Only thing is you will lose all data in internal storage as RUU will give you out of the box state - at least better than a non-working phone)
NOTE : other methods to install RUU zip - http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
Thank-you my friend, am downloading now.
Not worried about the data loss - I'd pretty much written the phone off anyway, so loss of data is a very small price to pay.
Will update you once all done.
If possible use PC with USB2.0
I'm on mobile for 6 hours.
If the above fails, I'll give you another method later.
I don't see a reason it would fail.
Thank you buddy - you are indeed, a GOD! :good::good::good::good::good::good:
It has re-booted and is just updating the apps. I will make sure I turn off the 'auto update' option so this won't happen again.
Just out of interest, if I wanted ever to upgrade the OS are there any good resources I could read?
I really appreciate your time in this - I know it's not easy to see a bit of a newbie type "Bricked" in the title!
Thanks again...
Simon
Great :good:
If you don't plan to root the device, there is no need to turn off auto update. It will success for future update when there is one.
Don't think there will be another OS update for M8, this Marshmallow is the last major OS update. If there is any further update, it will be some patches/small update.
Thanks again, you have been a massive help ...
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
PavM3 said:
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
Click to expand...
Click to collapse
You probably failed to perform one of these steps:
ckpv5 said:
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Open a command prompt from RUU folder then run below commands:
Click to expand...
Click to collapse
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Yes, I had I downloaded the files from the links provided and opened that command prompt from within RUU (holding down shift button and right clicking to get 'open command window here'. I have never done this sort of thing before so pardon my lack of knowledge on the basics....I am just determined to have my HTC m8 working again since there is no care centre in Kenya, where I come from. Thanks for the prompt response - wish I noticed it earlier.
redpoint73 said:
You probably failed to perform one of these steps:
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
Click to expand...
Click to collapse
PavM3 said:
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Click to expand...
Click to collapse
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Yes. The RUU folder contains the file htc_fastboot.exe as well as RUU.zip (which was renamed to this from the initial long name it had when I downloaded). I had already tried copying both RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder and have just retried and I get the error message 'preprocess_file: Cannot read header len bytes. Also I had tried and just retried copying the RUU folder (as opposed to the two separately)in the Minimal ADB and Fastboot folder and now it says 'Fastload is not recognized as an internal or external command, operable program or batch file.'
redpoint73 said:
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Click to expand...
Click to collapse
Can you do a screen capture of the RUU folder contents?
And also of the CMD window, when you try the command to flash the RUU zip (from RUU folder - let's concentrate there).
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
PandaDNB said:
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
Click to expand...
Click to collapse
If the RUU matches your phone's CID, yes.
Well i can currently see on the phone screen CID-11111111 and the 1.6 gig file(which is the RUU ?) is still downloading.
When i ran the fastboot 1.3.1 i got the same output as the OP.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.
Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.
Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.
Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?
Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?
downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip here : http://androidruu.com/?developer=M8
Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!
Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.
Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU
ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.
I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help
Pardon
Now that saw the second message. I will perform this procedure now
Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again
ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.
I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?
In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM