Related
ive looked everywhere and just cannot find anything, my one is from Cinncinati Bell, i was gonna put it back to stock, i did do a nandroid but something went wrong and the MD5`s dont match so thats gone, i cannot for the life of me find the stock rom for my phone at all anywhere
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0
(bootloader) version-baseband: 4A.14.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.422.16
(bootloader) version-misc: PVT SHIP S-O
(bootloader) serialno: HT35JW908396
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
If anyone can point me in the right direction id be very thankful, ive used the search function but find nothing
Thanks
Dan
angry english said:
ive looked everywhere and just cannot find anything, my one is from Cinncinati Bell, i was gonna put it back to stock, i did do a nandroid but something went wrong and the MD5`s dont match so thats gone, i cannot for the life of me find the stock rom for my phone at all anywhere
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0
(bootloader) version-baseband: 4A.14.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.422.16
(bootloader) version-misc: PVT SHIP S-O
(bootloader) serialno: HT35JW908396
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
If anyone can point me in the right direction id be very thankful, ive used the search function but find nothing
Thanks
Dan
Click to expand...
Click to collapse
1. gain s-off
2. Now get superCID
3. now use x.xx.401.x RUU
4. now get CID HTC__001
5. You are ready to get OTA(carrier free)
DONT FORGET TO HIT THANKS IF I HELPED YOU
prunzzz said:
1. gain s-off
2. Now get superCID
3. now use x.xx.401.x RUU
4. now get CID HTC__001
5. You are ready to get OTA(carrier free)
DONT FORGET TO HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
ok bit of a noob lol, so i got S-off, now to get superCID is the one with all the ones? after ive done that i can then use say the developer edition RUU, then i have to change my CID again to the HTC_001 and then i will receive updates
just want to make sure before i do something completly wrong, i understand noobs are frustrating but we all need to learn somewhere lol
oh and i have a USA Cincinnati bell phone, i dont live in the UK, so does that mean i use a different cid?
angry english said:
ok bit of a noob lol, so i got S-off, now to get superCID is the one with all the ones? after ive done that i can then use say the developer edition RUU, then i have to change my CID again to the HTC_001 and then i will receive updates
just want to make sure before i do something completly wrong, i understand noobs are frustrating but we all need to learn somewhere lol
oh and i have a USA Cincinnati bell phone, i dont live in the UK, so does that mean i use a different cid?
Click to expand...
Click to collapse
Hey, thats all right man!!
Nothing frustating
Afterall everyone is a noob at the beginning!!
OK
I gave you the procedure for going to european stock, because currntly european models are getting OTA.
Any ways if you dont want to hurry,(for OTA) which is a good thing(even i am waiting patiently for OTA)
Then do this,
Get superCID(11111111) its the same for all!!
Now run DEV Edition RUU(your regional stock. I mean the one you had initially)
Now when RUU is successfull, get your original CID(it would be something like BM__US1 i guess)
Now you are completely stock
Ask for help without hesitation if you need any!!
Best luck
prunzzz said:
Hey, thats all right man!!
Nothing frustating
Afterall everyone is a noob at the beginning!!
OK
I gave you the procedure for going to european stock, because currntly european models are getting OTA.
Any ways if you dont want to hurry,(for OTA) which is a good thing(even i am waiting patiently for OTA)
Then do this,
Get superCID(11111111) its the same for all!!
Now run DEV Edition RUU(your regional stock. I mean the one you had initially)
Now when RUU is successfull, get your original CID(it would be something like BM__US1 i guess)
Now you are completely stock
Ask for help without hesitation if you need any!!
Best luck
Click to expand...
Click to collapse
thanks for your reply bud, ok ive got the dev edition ruu loaded on but when i try install an update its says something about my device being modified, i presume i have to change my mid? as right now its PN0713000 and i suppose i need it to use PN0712000, also can i just keep the supercid on there?
angry english said:
thanks for your reply bud, ok ive got the dev edition ruu loaded on but when i try install an update its says something about my device being modified, i presume i have to change my mid? as right now its PN0713000 and i suppose i need it to use PN0712000, also can i just keep the supercid on there?
Click to expand...
Click to collapse
Ya
"the device has modified system" = MID mismatch
You need to get that MID which the RUU is meant for
Got it??
prunzzz said:
Ya
"the device has modified system" = MID mismatch
You need to get that MID which the RUU is meant for
Got it??
Click to expand...
Click to collapse
ok thanks, ive found the thread on how to change mid, for some reason when i open command prompt on the platform tools folder and type adb reboot bootloader is says device error:device not found
any ideas? again i really appreciate your help, its hard to find people with patience lol
angry english said:
ok thanks, ive found the thread on how to change mid, for some reason when i open command prompt on the platform tools folder and type adb reboot bootloader is says device error:device not found
any ideas? again i really appreciate your help, its hard to find people with patience lol
Click to expand...
Click to collapse
What is the output of
"adb devices" ??
prunzzz said:
What is the output of
"adb devices" ??
Click to expand...
Click to collapse
i got it going, ruu installing now, will let you know thanks
prunzzz said:
What is the output of
"adb devices" ??
Click to expand...
Click to collapse
well didnt work, when i do adb devices it says list of devices but nothing comes up
sorry i didnt have usb debugging enabled.... i could slap myself.... and yeah i face palmed myself lol
angry english said:
well didnt work, when i do adb devices it says list of devices but nothing comes up
sorry i didnt have usb debugging enabled.... i could slap myself.... and yeah i face palmed myself lol
Click to expand...
Click to collapse
It happens!! LOL
Now everything is ok right?
prunzzz said:
It happens!! LOL
Now everything is ok right?
Click to expand...
Click to collapse
well, it finds the device in adb, when i boot to hboot it shows my PN as it should the new one, and my cid is 1111111 but it still dont want to update, but ive had enough for one night, im off to bed and will try again tomorrow, again thanks for all your help, you have been a star
RUU CB
Hi, i tried to flash a rom TMob 2.31 and now my HTC One S y stock in the white screen do you get the RUU from Cinncinati Bell???, i wan put it back to stock, i did not a nandroid and now i'am in a big trouble If anyone can help me please let me know, ive used the search function but find nothing.
VLE PVT SHIP S-ON RL
Hboot 2.15.000
Radio 1.11.50.05.28
Thanks you
allesp
Hello,
I hope anyone can help me. I' sitting here for many many hours and try to get my phone work.
First of all I flashed the "Firmware 5.11.401.10 | No Red Text" which causes bricked phones for some, so as me.
I send the phone to a repair center ( not HTC ) for a jtag repair, and got I back yesterday.
Firmware was repaired, but:
IMEI now: 12345678xxxxx0 ( was 12345678xxxxx6.)
product: m7_wlv ( was m7_ul )
serialno: total different
MID PN0731000 ( was PN071000 )
CID still super-CID.
Cyangenmod is installed after the repair.
Unlocked as before.
S-Off was lost.
here is my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.00
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: 123456....0
(bootloader) meid: 99000428016233
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
make a long story short:
after hours I got TWRP working, flashing often, got status OK, but doesn't work. Now TWRP 2.6.3.4 is working.
Tried to flash ARHD, starts and reboot....
Tried to flash ARHD TWRP-Backup, starts and reboot....
Tried to flash other nandroid backups starts and reboot....
and tried a lot of other things... nothing worked
only the cyangenmod starts and works
S-Off doesnt work ( rumrunners, firewater, renove )
I am at the end of my knowledge..
Has somebody any ideas ?
I think there was a great mistake at the jtag-repair.
I think due to the changes of Model-ID, Serialno, wrong IMEI now I have this trouble and will have problems in the future too.
Can you give me some advice ?
Many thanks in advance.
Andreas
PS: sorry for my poor english, but I think you understand what I want to say.
Andy_Guinness said:
Hello,
I hope anyone can help me. I' sitting here for many many hours and try to get my phone work.
First of all I flashed the "Firmware 5.11.401.10 | No Red Text" which causes bricked phones for some, so as me.
I send the phone to a repair center ( not HTC ) for a jtag repair, and got I back yesterday.
Firmware was repaired, but:
IMEI now: 12345678xxxxx0 ( was 12345678xxxxx6.)
product: m7_wlv ( was m7_ul )
serialno: total different
MID PN0731000 ( was PN071000 )
CID still super-CID.
Cyangenmod is installed after the repair.
Unlocked as before.
S-Off was lost.
here is my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.00
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: 123456....0
(bootloader) meid: 99000428016233
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
make a long story short:
after hours I got TWRP working, flashing often, got status OK, but doesn't work. Now TWRP 2.6.3.4 is working.
Tried to flash ARHD, starts and reboot....
Tried to flash ARHD TWRP-Backup, starts and reboot....
Tried to flash other nandroid backups starts and reboot....
and tried a lot of other things... nothing worked
only the cyangenmod starts and works
S-Off doesnt work ( rumrunners, firewater, renove )
I am at the end of my knowledge..
Has somebody any ideas ?
I think there was a great mistake at the jtag-repair.
I think due to the changes of Model-ID, Serialno, wrong IMEI now I have this trouble and will have problems in the future too.
Can you give me some advice ?
Many thanks in advance.
Andreas
PS: sorry for my poor english, but I think you understand what I want to say.
Click to expand...
Click to collapse
Sounds like you got a new motherboard
M7_UL to M7_WLV? - isn't that a Verizon one and CDMA instead of GSM?
IMO, the model ID is causing your issues.
Thanks a lot for your answers.
SaHiLzZ said:
Sounds like you got a new motherboard
Click to expand...
Click to collapse
that could not be, that would be the cheapest motherboard I ever bought.
The charge of the repair was 25 euro.
davebugyi said:
M7_UL to M7_WLV? - isn't that a Verizon one and CDMA instead of GSM?
IMO, the model ID is causing your issues.
Click to expand...
Click to collapse
Yes, its Verizon, I assume this causes the problems. I think this will cause problems in the future also, if i decide to go back to stock.
Has anybody additional advices ?
--edit--
the last hours I tested other rom than ARHD, Insert Coin and other...
All stuck at boot. I erased the caches everytime.
nothing is working.
--- end of edit -
Andy_Guinness said:
Yes, its Verizon, I assume this causes the problems. I think this will cause problems in the future also, if i decide to go back to stock.
Has anybody additional advices ?
--edit--
the last hours I tested other rom than ARHD, Insert Coin and other...
All stuck at boot. I erased the caches everytime.
nothing is working.
--- end of edit -
Click to expand...
Click to collapse
They should have left S-OFF!! You need to get S-Off, otherwise you won't be able to change MID, and fix any other problems.
you have hboot 1.54 so rumrunner and/or firewater should work, but radio is consistent with firmware 5.11.401.10 (hboot 1.57) so it's hard to tell which firmware you actually have.
you said cyangenmod works, so try getting S-Off using that and try both rumrunner and firewater
nkk71 said:
They should have left S-OFF!! You need to get S-Off, otherwise you won't be able to change MID, and fix any other problems.
you have hboot 1.54 so rumrunner and/or firewater should work, but radio is consistent with firmware 5.11.401.10 (hboot 1.57) so it's hard to tell which firmware you actually have.
you said cyangenmod works, so try getting S-Off using that and try both rumrunner and firewater
Click to expand...
Click to collapse
Hello nkk71,
thanks a lot for your answer.
you are right, I've to get S-Off to fix the problems. But to get S-Off that's the main problem.
Yesterday afternoon and evening I tried again to get S-Off in many ways ( rumrunners, firewater, renove, moonshine.. ). mostly the result is: unknown error or wrong ROM.
firewater doesn't work also. It starts with permissions problem, so I set the permissions manually to solve the permission issues. At last firewater said: error, run firewater as root. I search the firewater thread, but don't find a solution at the firewater thread. so I've to post this question at the firewater thread.
All Roms, TWRP-Backups ( own and others ) aren't starting, after 10-15 sec. -> reboot.
All other trials with OTA und RUU failed too.
Meanwhile I got an answer from the repair service: ( my comments in blue color ):
>>first of all the last number of the IMEI is not set manually, but generated from the IMEI itself and programmed via JTAG without surgery itself!
>>This is a checksum which results from the IMEI, and even changes to 0! There you have no control over JTAG or otherwise.
I know this. The IMEI-checksum is wrong, was 6, now is 0. so his checksum algorithm works wrong. I additionally verified this with IMEI-Check-"programs"
>>The hanging ROMS should not be the problem, therefore simply flash the Boot.img manually.
I don't know how often I flashed the boot.img manually during the last 2 days
>>the product name is not changed via JTAG, it is taken over by JTAG automatically. When the product name should be changed manually the box shows a message that it is the wrong name, and then the circuit board can not be programmed. Thus, it is checked whether it is the right hardware.
The hardware is M7_UL 801n, why should JTAG switch it to M7_wlv ( verizon ) ?
>>And the serial number is in JTAG guaranteed not changed, there isnt any possibility to do at all, unless the data is automatically written from JTAG automatically.
I have now another serial number
Please look for the ROM again with Boot.img.
Perhaps there are any other ideas ?
Thanks a lot in advance.
Today I take a break and will repair my car, but I will look into the forum every hour.
Andreas
Andy_Guinness said:
Please look for the ROM again with Boot.img.
Click to expand...
Click to collapse
You need to push back to the repair guys to fix their mess
SaHiLzZ said:
You need to push back to the repair guys to fix their mess
Click to expand...
Click to collapse
Hello SaHiLzZ,
thanks a lot.
You're right, I think too, there is no other way as to send back to the repair guys.
But I wonder about if they can manage to restore the firmware.
Wrong IMEI-checksum, changed serial-no, wrong MID, wrong product name, version-main: 1.00.000.00, wrong ROM ( CM instead HTC )....
More error are not possible.
Can anybody recommend a reliable Jtag-service here in germany ?
the germany repair center of HTC ( Arvato ) seems to be very expensive.
SaHiLzZ said:
You need to push back to the repair guys to fix their mess
Click to expand...
Click to collapse
definitely
now, I know where the error is:
he posted the jtag log of my HTC One M7_UL PN0710000 at his website.
JTAG Log:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC OneM7 (PN0713000) V1.0.5149.50216]
Andy_Guinness said:
definitely
now, I know where the error is:
he posted the jtag log of my HTC One M7_UL PN0710000 at his website.
JTAG Log:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC OneM7 (PN0713000) V1.0.5149.50216]
Click to expand...
Click to collapse
Not sure what log you are referring to, but PN0713000 (t-mo usa) would have been better than PN0731000.... sounds like a sloppy "repair" to me
nkk71 said:
Not sure what log you are referring to,
Click to expand...
Click to collapse
He posted the results of his repairs at his website, and so he did with the Riff Box Jtag status, copied out of the programm jtag manager.
So I have now a documention of the wrong flashing.:good:
Andy_Guinness said:
He posted the results of his repairs at his website, and so he did with the Riff Box Jtag status, copied out of the programm jtag manager.
So I have now a documention of the wrong flashing.:good:
Click to expand...
Click to collapse
but you posted a log for a different MID than you're getvar is showing
PN0713000
vs
PN0731000
13 vs 31
Anyway, good luck!
nkk71 said:
but you posted a log for a different MID than you're getvar is showing
PN0713000
vs
PN0731000
13 vs 31
Anyway, good luck!
Click to expand...
Click to collapse
you are right, the MID in getvar is really PN0731000. No typing error, just copy and paste of getvar.
so, let's wait until tomorrow.
In JTAG the operator has to manually select the device. That's bull crap they are feeding you. Someone at the shop screwed up badly. They need to use the right file, and tell them to keep it Soff.
Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................
(bootloader) imei: ................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!
I think S-off is danger may u brick ur phone, it's better to leave it
ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...................
(bootloader) imei: ....................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!
The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.
Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!
here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.
I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.
Hello,
I have a Htc one (M7) that is stuck in a bootloop. I first tried to find the solution in privious threads, but i could'nt find the right rom.
Thanks for your help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3**********
(bootloader) imei: 354*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.211s
- - - - - - - -
tampered
relocked
security warning
------
Please let me know if you need any further information.
And thanks a lot for your great work.
Any ideas mates ?
I tried to find a ruu.exe but i couldn't find it.
Anyone?
thank you
Unlock your bootloader... Maybe gonna fix it
Wysłane z mojego One przy użyciu Tapatalka
123-Quest said:
Hello,
I have a Htc one (M7) that is stuck in a bootloop. I first tried to find the solution in privious threads, but i could'nt find the right rom.
Thanks for your help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3**********
(bootloader) imei: 354*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.211s
- - - - - - - -
tampered
relocked
security warning
------
Please let me know if you need any further information.
And thanks a lot for your great work.
Click to expand...
Click to collapse
If you have relocked the bootloader with a custom rom, custom recovery or custom kernel installed on your phone, it will bootloop. If this is what you did, yes unlocking the bootloader will probably fix your problem.
Stachura5 said:
Unlock your bootloader... Maybe gonna fix it
Wysłane z mojego One przy użyciu Tapatalka
Click to expand...
Click to collapse
Thank you and Dziękuję Stachura5.
Thank you alray.
I managed to unlock the bootloader.
Now I have no boot loop but I only get the white logo screen.
the good news is; i can now access the recovery menu.
To me, it seems as if there is no os at all. For this reason the first thing that came to my mind, is to search for the right rom.
again, thanks.
I
123-Quest said:
Thank you and Dziękuję Stachura5.
Thank you alray.
I managed to unlock the bootloader.
Now I have no boot loop but I only get the white logo screen.
the good news is; i can now access the recovery menu.
To me, it seems as if there is no os at all. For this reason the first thing that came to my mind, is to search for the right rom.
again, thanks.
I
Click to expand...
Click to collapse
Good to hear that it helped. I had the same problem with my One after relocking the bootloader, so I had to unlock it again [emoji4]
Stachura5 said:
Good to hear that it helped. I had the same problem with my One after relocking the bootloader, so I had to unlock it again [emoji4]
Click to expand...
Click to collapse
Yes it helped, no boot loop , and i can access recovery menu. / the full half of the glas. , now I think I should find the right custom rom; right?
123-Quest said:
Yes it helped, no boot loop , and i can access recovery menu. / the full half of the glas. , now I think I should find the right custom rom; right?
Click to expand...
Click to collapse
Yes, now you need a ROM. Find one that suits your liking & try to put it (somehow) on the phone [emoji4]
Stachura5 said:
Yes, now you need a ROM. Find one that suits your liking & try to put it (somehow) on the phone [emoji4]
Click to expand...
Click to collapse
Anything suits me, as long as it´s working. : )
I tried 3 different run.exe roms, but i get an error notification.
should the ruu zip match my modelid and cid=
modelid: PN0710000
cidnum: 11111111
I have almost no experience in this kind of things, so maybe someone here could kindly suggest a specific rom.
thanks
I have a question please:
I am trying to flash the sense 7 rom using TWRP, do you think it suits my device?
thank you
123-Quest said:
I have a question please:
I am trying to flash the sense 7 rom using TWRP, do you think it suits my device?
thank you
Click to expand...
Click to collapse
Why shouldn't it? It's made for HTC devices [emoji4]
123-Quest said:
Anything suits me, as long as it´s working. : )
I tried 3 different run.exe roms, but i get an error notification.
should the ruu zip match my modelid and cid=
modelid: PN0710000
cidnum: 11111111
I have almost no experience in this kind of things, so maybe someone here could kindly suggest a specific rom.
thanks
Click to expand...
Click to collapse
What rom are your trying to flash, and how are you sending it to your phone?
---------- Post added at 12:22 PM ---------- Previous post was at 12:11 PM ----------
123-Quest said:
I have a question please:
I am trying to flash the sense 7 rom using TWRP, do you think it suits my device?
thank you
Click to expand...
Click to collapse
Sense 7 should work. Are you transferring the zip file from your computer to your phone internal memory or you are ADB pushing?
zainkool said:
What rom are your trying to flash, and how are you sending it to your phone?
---------- Post added at 12:22 PM ---------- Previous post was at 12:11 PM ----------
Sense 7 should work. Are you transferring the zip file from your computer to your phone internal memory or you are ADB pushing?
Click to expand...
Click to collapse
I tried to flash sense 7 from recovery/ side load, everything worked well, but then the touchscreen was too unresponsive. I am trying again now.
let's hope.
thank you
123-Quest said:
I tried to flash sense 7 from recovery/ side load, everything worked well, but then the touchscreen was too unresponsive. I am trying again now.
let's hope.
thank you
Click to expand...
Click to collapse
What do you mean by "touchscreen was too unresponsive"? Was it complitely unresponsive? You couldn't do anything with your phone?
donkeykong1 said:
What do you mean by "touchscreen was too unresponsive"? Was it complitely unresponsive? You couldn't do anything with your phone?
Click to expand...
Click to collapse
I mean I couldn't go to the next step using touchscreen, it must be some kind of bug. I am stuck again.
123-Quest said:
I mean I couldn't go to the next step using touchscreen, it must be some kind of bug. I am stuck again.
Click to expand...
Click to collapse
Not a bug. You have a very old h-boot. You will need to upgrade your phone in order to get newer touch drivers so your touchscreen can work
donkeykong1 said:
Not a bug. You have a very old h-boot. You will need to upgrade your phone in order to get newer touch drivers so your touchscreen can work
Click to expand...
Click to collapse
can you please give me a link, i don't even know what to look for.
123-Quest said:
can you please give me a link, i don't even know what to look for.
Click to expand...
Click to collapse
I need to get a hold of my laptop. If you can wait an hour or two till I get home, I will gladly help you
donkeykong1 said:
I need to get a hold of my laptop. If you can wait an hour or two till I get home, I will gladly help you
Click to expand...
Click to collapse
i am lucky to be here. thank you for your help.
I need to get up very early, so maybe i'll check your post tomorrow.
I learnt a lot of new things dealing with this issue/ again i really appreciate this wonderful atmosphere here.