Hi!
Long story - short:
- I played around with a custom rom, but due to Google Pay issues I went back to stock rom, but forgot to flash the stock bootloader before I locked the bootloader and also didn't activate the developer options to unlock the bootloader again. So now the system does not allow me to boot and I'm stuck.
- Tried LGUP, LG Bridge, LGMobile Support Tool which all work but are not able to repair the locked bootloader problem.
- I don't care for any data on the phone - I just want to get it working again
- No warranty (as anybody can see from the log below) due to having unlocked the bootloader at least once
On every boot it shows: "Your device has failed a routine safety check and will not boot. This may be a temporary problem. If this message occurs repeatedly, visit this link on another device and refer to the Red case: g.co/ABH"
Currently both bootloaders are not bootable (output from fastboot getvar all):
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:1
(bootloader) unlock_count:1
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4358
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xB8C8F4000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x11B800000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) ufs-bootlun:1(a)
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:LMG710EMxxxxxxxx
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
I can see that I am not the only one which fell into this trap but from the existing threads I can't see a clear strategy to solve this. So help would not only serve my cause...
I would guess (wild speculation due to lack of knowledge) there are two options for me:
1) Flash a kdz file with dev options to unlock bootloader pre-set (but I don't have such a thing) to be able to unlock the bootloader
- Is this really possible or do I have an error in my thinking about this? If not, does anyone have such a "recovery" image for LG G7?
2) Force the flash of the stock bootloader (I have a extracted bootloader boot_a_65286.bin from my stock kdz) with Qualcomm tools (QPST, QFil, 9008 mode???), but I don't know how
- Do I understand this correctly that I do have to shorten two pins on the motherboard to get into this programming mode or can I also use this from EDL without opening the phone?
- I guess, independent from the former question, I am in need of "outside" assistance for this solution because of some non-public files needed for this procedure
Are there other ways to fix this? Your help would be greatly appreciated!
Best regards,
Oliver
I must ask you. Why did you lock bootloader?
I personally don't know how to help you if flashing .kdz didn't work.
But i always wonder why people are locking their bootloaders, not being sure if everything is ok, knowing risk that it can brick their phone.
ShadoV90 said:
I must ask you. Why did you lock bootloader?
I personally don't know how to help you if flashing .kdz didn't work.
But i always wonder why people are locking their bootloaders, not being sure if everything is ok, knowing risk that it can brick their phone.
Click to expand...
Click to collapse
It always the same ... I didn't know/think about bricking the phone and wanted to get rid of the message which prompted at each boot. It is that simple. Be asured, it wasn't my intent
I was thinking about the following procedure - maybe someone could tell me if this makes even sense...
1. Build an KDZ image file which has already "Developer Options" enabled and within Developer Options it has "Bootloader unlock" enabled (is this even possible)
- I found some KDZ tools but currently don't know where to start
2. Start phone into fastboot mode (which currently works - but due to missing developer option settings I can't flash the bootloader)
3. Unlock the bootloader again (with unlock.bin)
4. Flash the correct bootloader
5. Flash the wanted stock KDZ
6. Everthing should be fine...
The crucial part is 1) Can anyone tell me if this makes sense and might be possible. If it is the case then this would be an easy and universal way to solve these issues.
Flashing original .kdz should fix that problem, because it should overwrite both boot_a and boot_b, even if you don't have enable oem unlock turned on.
Building any custom KDZ not signed by LG will fail due to... LOCKED Bootloader.
ShadoV90 said:
Flashing original .kdz should fix that problem, because it should overwrite both boot_a and boot_b, even if you don't have enable oem unlock turned on.
Building any custom KDZ not signed by LG will fail due to... LOCKED Bootloader.
Click to expand...
Click to collapse
Thank you for your reply!
I tried again...
First time I was using LGUP V1.14
- first with the original TIM Firmware (G710EM10q_00_0111.kdz) with Refurbish and with Upgrade - all went okay -> same error screen -> won't boot
- second try korean pie version (G710N20f_00_LGU_KR_OP_0308.kdz) with Refurbish and with Upgrade - doesn't work - stops at 75% (92% on the phone) - seems to be a problem with V1.14
What about the other options within LGUP V1.14? Did I use the wrong options?
Second time I used LGUP_Cmd V1.15
- first try korean pie version (G710N20f_00_LGU_KR_OP_0308.kdz) -> shows "AB slot change fail" but carries on and finishes, but -> error screen -> won't boot
- second try with the original TIM Firmware (G710EM10q_00_0111.kdz) - all went okay -> same error screen -> won't boot
What are these "[EXTRA_OPTION(Optional)]" with LGUP_Cmd
Any suggestions?
I tried another stock KDZ and directly entered fastboot. It shows no unbootable slots initially.
But after I try to boot up it tries to boot from slot a 7 times shows the familiar error message and then sets slot a to unbootable ...
This should not have happened. I flashed the correct oreo firmware KDZ (which should also replaced the bootloaders with stock ones), booted into this rom, rebooted into fastload and then locked the bootloader. That is all. How could this even happen?
Okay, now I think it is fully broken...
I can't boot into EDL anymore ... it looks like it would do so for 0,5s then it jumps into fastboot
I guess I am looking for another brand
MagicOJB said:
Okay, now I think it is fully broken...
I can't boot into EDL anymore ... it looks like it would do so for 0,5s then it jumps into fastboot
I guess I am looking for another brand
Click to expand...
Click to collapse
Sorry dor your loss,but it's not about brand.
You should be careful when playing with bootloader stuff.i hard bricked my mate 10 pro for 6 months,and there was litteraly no solution.screen was off completly by just flashing official beta firmware(classic huawei).
So you at least have hope with correct software to solve the issue.
MagicOJB said:
Thank you for your reply!
I tried again...
First time I was using LGUP V1.14
- first with the original TIM Firmware (G710EM10q_00_0111.kdz) with Refurbish and with Upgrade - all went okay -> same error screen -> won't boot
- second try korean pie version (G710N20f_00_LGU_KR_OP_0308.kdz) with Refurbish and with Upgrade - doesn't work - stops at 75% (92% on the phone) - seems to be a problem with V1.14
What about the other options within LGUP V1.14? Did I use the wrong options?
Second time I used LGUP_Cmd V1.15
- first try korean pie version (G710N20f_00_LGU_KR_OP_0308.kdz) -> shows "AB slot change fail" but carries on and finishes, but -> error screen -> won't boot
- second try with the original TIM Firmware (G710EM10q_00_0111.kdz) - all went okay -> same error screen -> won't boot
What are these "[EXTRA_OPTION(Optional)]" with LGUP_Cmd
Any suggestions?
Click to expand...
Click to collapse
I am not sure if this works. I had similar issue with my google pixel. Luckily even if you re lock boot loader, as long as you dont disable oem unlock setting manually in developer option it will be possible to unlock bootloader again. OEM unlock will not reset no matter how many time you flash a rom. Hence try unlocking bootloader.
coolrevi said:
I am not sure if this works. I had similar issue with my google pixel. Luckily even if you re lock boot loader, as long as you dont disable oem unlock setting manually in developer option it will be possible to unlock bootloader again. OEM unlock will not reset no matter how many time you flash a rom. Hence try unlocking bootloader.
Click to expand...
Click to collapse
Thanks for your reply. I flashed a new image booted up, but forgot to set developer settings before locking the bootloader
MagicOJB said:
Thanks for your reply. I flashed a new image booted up, but forgot to set developer settings before locking the bootloader
Click to expand...
Click to collapse
I think, what MagicOJB want to say it's just retry to oem unlock!
Type the command again, maybe the oem in dev setting was not reset, so it will work.
I'm not sure to but when you re-lock the bootloader you're able to unlock it just after.
kadiix said:
I think, what MagicOJB want to say it's just retry to oem unlock!
Type the command again, maybe the oem in dev setting was not reset, so it will work.
I'm not sure to but when you re-lock the bootloader you're able to unlock it just after.
Click to expand...
Click to collapse
Thanks for the reply kadix.
Sadly this doesn't work because the developer options are not set - so (re-) unlocking the bootloader isn't allowed.
But currently the phone is back to the seller. Let's see what they can do...
MagicOJB said:
Thanks for the reply kadix.
Sadly this doesn't work because the developer options are not set - so (re-) unlocking the bootloader isn't allowed.
But currently the phone is back to the seller. Let's see what they can do...
Click to expand...
Click to collapse
OK finger cross.
I hope for you that it will be free
What second non-original bootloader are you talking about? Could you fill me in on that?
jazir said:
What second non-original bootloader are you talking about? Could you fill me in on that?
Click to expand...
Click to collapse
I don't know what you are referring to. By flashing stock firmware you always get an "original" bootloader.
Guys! @Vlaaaad Fixed my LG G7 (LM-G710EM). Recovered my phone from RED CASE in about 1 hour. It does required remote access. PM him for more information.
Erus Tyrannus said:
Guys! @Vlaaaad Fixed my LG G7 (LM-G710EM). Recovered my phone from RED CASE in about 1 hour. It does required remote access. PM him for more information.
Click to expand...
Click to collapse
After recovery bootloader is locked or unlocked?
After trying to re lock the bootloader my phone got bricked. But he fixed it in 40 minutes.
Brick same
Erus Tyrannus said:
After trying to re lock the bootloader my phone got bricked. But he fixed it in 40 minutes.
Click to expand...
Click to collapse
Hola, can you help me ? thanks
my problem is the same that you ^^
Contact @Vlaaaad, he can help you.
Related
Hello everyone. So, I have a problem. I've been running on CM10.2.1 [stable version] , and after install, everything was fine, on the second day, after i had lunch, i saw that there's no connection to my SIM card. To be clear, my SIM card is fine, i checked it. I read like milion threads , done many many custom roms, nothing. All the same, no IMEI, no baseband [see attached photo] , then i got back to stock rom using this met chanhod - http://forum.xda-developers.com/showthread.php?t=1546970 but nothing. I tried running RUU , but it's says bootloader fail, i cannot find higher version of ruu than mine phone's version-main: 3.20.401.1.
Oh, i've donwloaded 'Root explorer' to check if there is EFS folder, unlucky, but no, no folder.
But i know, that my IMEI is there somewhere, because when i typed in cmd: fastboot getvar all , i get this:
D:\Android\OneXRoot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0
(bootloader) version-baseband: 5.1204.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.20.401.1
(bootloader) serialno: HT23WW137751
(bootloader) imei: 3**188*43*80*76 - I changed numbers with * to be not seen fully.
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3789mV
(bootloader) devpower: 47
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.823s
So, long story short, can anyone help me? Thanks.
bl1ndway said:
Hello everyone. So, I have a problem. I've been running on CM10.2.1 [stable version] , and after install, everything was fine, on the second day, after i had lunch, i saw that there's no connection to my SIM card. To be clear, my SIM card is fine, i checked it. I read like milion threads , done many many custom roms, nothing. All the same, no IMEI, no baseband [see attached photo] , then i got back to stock rom using this met chanhod - http://forum.xda-developers.com/showthread.php?t=1546970 but nothing. I tried running RUU , but it's says bootloader fail, i cannot find higher version of ruu than mine phone's version-main: 3.20.401.1.
Oh, i've donwloaded 'Root explorer' to check if there is EFS folder, unlucky, but no, no folder.
But i know, that my IMEI is there somewhere, because when i typed in cmd: fastboot getvar all , i get this:
\
finished. total time: 0.823s
So, long story short, can anyone help me? Thanks.
Click to expand...
Click to collapse
OK try this DOWNLOAD THIS copy the one x odexed.zip to your sd card then go in recovery and flash it flash the boot.img and the last recovery.img then restart the phone and check for update over wi-fi you must have update then update your phone and check if you have IMEI and baseband if you have you can update to latest base or leave on this base and don't forget if you restore your IMEI to make nandroid backup for future problems if you have
Thanks for reply, sadly, it did not worked. :< I did exactly as you said, but nothing. I forgot to mension, that AIRPLANE mode is on TURNING OFF.. like, not fully OFF. Radio is OFF. Any other suggestions?
I think, that the problem is with RADIO OFF? Anyone? Thanks.
bl1ndway said:
I think, that the problem is with RADIO OFF? Anyone? Thanks.
Click to expand...
Click to collapse
are you tryed wit wi-fi to check for OTA and update the phone are you try factory reset
I think I have a solution, listen up:
I read in this thread http://forum.xda-developers.com/showthread.php?t=2370699 that he got it all worked out by flashing a efc.zip file to his phone. Other guys made a Flashable Zip , installed via CWM and it all worked. So, can anyone do that for me? Maybe thats the solution? Or it's not possible?
Guys, I think it's good news for me. Somehow magically I have RADIO ON , I have my IMEI in settings. But still, no service? SIM card is fine. I tried another SIM - same, no service.
But no EFS folder, how come? I have IMEI, baseband, but no EFS folder?! Help!
bl1ndway said:
Guys, I think it's good news for me. Somehow magically I have RADIO ON , I have my IMEI in settings. But still, no service? SIM card is fine. I tried another SIM - same, no service.
But no EFS folder, how come? I have IMEI, baseband, but no EFS folder?! Help!
Click to expand...
Click to collapse
Turn on Mobile data, turn on Wi-Fi and check for OTA. And don't compare Samsung devices with HTC I think we dont have EFS folder Or I can't find it
Thant said:
Turn on Mobile data, turn on Wi-Fi and check for OTA. And don't compare Samsung devices with HTC I think we dont have EFS folder Or I can't find it
Click to expand...
Click to collapse
Have you checked it with Root Explorer for EFS folder?
bl1ndway said:
Have you checked it with Root Explorer for EFS folder?
Click to expand...
Click to collapse
Yes no EFS folder or the roort explorer didn't find it
bl1ndway said:
Guys, I think it's good news for me. Somehow magically I have RADIO ON , I have my IMEI in settings. But still, no service? SIM card is fine. I tried another SIM - same, no service.
But no EFS folder, how come? I have IMEI, baseband, but no EFS folder?! Help!
Click to expand...
Click to collapse
Hi! Last night my phones signals just vanished, I thought it was a network problem but this morning there were still no signals and the same situations as yours, on airplane mode turning off, no imei etc. How can I fix it? Tried reinstalling kernel and tried few roms, nothing works for me. My phone is just like an ipod now, please help me have my imei and sim work again! Please
kassaaam said:
Hi! Last night my phones signals just vanished, I thought it was a network problem but this morning there were still no signals and the same situations as yours, on airplane mode turning off, no imei etc. How can I fix it? Tried reinstalling kernel and tried few roms, nothing works for me. My phone is just like an ipod now, please help me have my imei and sim work again! Please
Click to expand...
Click to collapse
First of all - try with your current ROM to do this!
Finally I managed to get out of Airplane mode 'Turning Off' [later I'll write a normal tutorial] , simply, I was using this ROM http://forum.xda-developers.com/showthread.php?t=1705334
install it, download ES explorer, go to - tools - tap ON on Root explorer, go to system files and create there a folder called - EFS and then wait, like 60 seconds, if nothing happens - reboot phone. And wuala! It worked for me. I hope it will work for you.
NOTE: you need tu have Super Su app and be rooted of course.
I worked for me, but now, when I put my card in the sim tray, still - NO SERVICE - no sim card. So please, if you succeed doing my tutorial, reply to me, is it fully working when you put your SIM card, o it's like mine's NO Service - no sim card.
bl1ndway said:
First of all - try with your current ROM to do this!
Finally I managed to get out of Airplane mode 'Turning Off' [later I'll write a normal tutorial] , simply, I was using this ROM http://forum.xda-developers.com/showthread.php?t=1705334
install it, download ES explorer, go to - tools - tap ON on Root explorer, go to system files and create there a folder called - EFS and then wait, like 60 seconds, if nothing happens - reboot phone. And wuala! It worked for me. I hope it will work for you.
NOTE: you need tu have Super Su app and be rooted of course.
I worked for me, but now, when I put my card in the sim tray, still - NO SERVICE - no sim card. So please, if you succeed doing my tutorial, reply to me, is it fully working when you put your SIM card, o it's like mine's NO Service - no sim card.
Click to expand...
Click to collapse
Man my phone is rooted and have latest SU binary and still no EFS folder
Hi! Thanks for replying, I already have es file explorer and i followed your steps but couldn't understand that where you wanted me to create the efs folder? In the very root of the phone or in the system partition? Anyway i created "efs" folder in both the system partition and in the root of the phone where every other partition like system, data, sys etc are shown. Restarted my phone but still no success. Mobile Signals are still no where but every other thing works fine even wifi, bluetooth etc.
I am trying to find any solution on the internet, I will let you know if anything works for me.
Btw @bl1ndway is your hox s-off or s-on? Mine is S-on thats why i think it will be nearly impossible to recover from this situation.
(At first: I'm a noob when it comes to this and I know this has been a big mistake)(Also, my first language isn't English, so please be nice ) So today, I tried to root my HTC One M9 with this video: (I did EXACTLY those steps one by one)
sakitech - How to Root your HTC One M9 (Full Guide)
(Can't post links yet)
I did get a bootloop (Yay), so I started to get frustrated. After that, I searched for fixes and deleted some things (Which has been the biggest mistake I've ever done in my life). Now I seriously dont know what to do. I can't enter the Recovery mode, I can't do sh*t. Even my computer cannot detect my smartphone anymore..... Whenever I type smth like "adb reboot recovery" it says it FAILED..... If I try to get into Recovery mode, it tells me: "failed to boot to recovery mode".
So one of the only Screens I can get is the Bootloader and download reboot screen. (Not exactly sure if there's more)
"Software status: Modified" " RELOCKED" "S-ON"
-All this Boot-Stuff-
I can't even get to the Homescreen, in fact, I can't install SunShine to get S-OFF. I don't even want it rooted anymore, I just want it to work again
Please, help me somehow ._.
(Sorry for grammar fails)
//Edit: I installed the M9Toolkit by SQUABBI and I discovered, that none of those Commands have any effect on my phone. Doesn't matter what I'm pressing, either it's "No Device Found" or nothing happens.
Which model you've? CID, MID? You need to RUU your device through SD-Card method. Since you're S-On, you can only use signed firmwares.
What do you mean by which model do I have? As I said, I'm a noob if it comes to this (Bought it from amazon, so I dont have any trouble with Verizon and stuff)
CID: HTC__102
MID: 0PJA10000
Loligerloler said:
What do you mean by which model do I have? As I said, I'm a noob if it comes to this (Bought it from amazon, so I dont have any trouble with Verizon and stuff)
CID: HTC__102
MID: 0PJA10000
Click to expand...
Click to collapse
Do you have skype or hangouts? i could help you out over live chat.
Just chiming in with the old "why root it if you have no clue what you're doing".
You need to unlock the oem bootloader lock as you have relocked it so now it wont allow you to do much.. Thats the hard bit. Not sure how you do that as I've never borked it so bad.
Once unlocked, if you can re-unlock it, you can flash twrp 2.9.0.1 and supersu 2.65.
I advise doing any oem ota's prior to rooting and taking a twrp full system backup (4gb). If you include data in the backup you need 12gb free on internal memory.
Sent from my HTC One M9 using Tapatalk
So true ._. Was a huge mistake ...
I didnt really care about rooting it anymore, so I tried EVERYTHING to work again somehow.
Thank god Black_Eyes posted the right thing.
I just pasted the right RUU file on my SD-Card and installed it on the phone. Had to reboot a few times but in the end it worked.
Loligerloler said:
So true ._. Was a huge mistake ...
I didnt really care about rooting it anymore, so I tried EVERYTHING to work again somehow.
Thank god Black_Eyes posted the right thing.
I just pasted the right RUU file on my SD-Card and installed it on the phone. Had to reboot a few times but in the end it worked.
Click to expand...
Click to collapse
I too have the same issue. Sakitech . So what should I do? I've unlocked bootloader and S-ON. What did you do? From where did you download the stock ROM for your device? How did you install it? With TWRP or Download mode or they stock recovery?
anirudh.das13 said:
I too have the same issue. Sakitech . So what should I do? I've unlocked bootloader and S-ON. What did you do? From where did you download the stock ROM for your device? How did you install it? With TWRP or Download mode or they stock recovery?
Click to expand...
Click to collapse
I've relocked the bootloader (which isnt that hard).
Then I searched the internet for the correct RUU(It's a german page, I dont think you would understand anything ).
I copied the RUU onto(?) my SD-Card (You gotta rename it to: "0PJAIMG.zip" without " ), and sticked it into my phone and started the download mode. It asked me if I want to install it and so on. Had to reboot it a couple of times though.
After it installed properly I deleted the file from my SD-Card and I was fine.
Loligerloler said:
I've relocked the bootloader (which isnt that hard).
Then I searched the internet for the correct RUU(It's a german page, I dont think you would understand anything ).
I copied the RUU onto(?) my SD-Card (You gotta rename it to: "0PJAIMG.zip" without " ), and sticked it into my phone and started the download mode. It asked me if I want to install it and so on. Had to reboot it a couple of times though.
After it installed properly I deleted the file from my SD-Card and I was fine.
Click to expand...
Click to collapse
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
anirudh.das13 said:
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
Click to expand...
Click to collapse
Sadly, I'm not the best when it comes to this But make sure you rename the zip file and dont put it in any folder. Just copy it directly on the card. Relocked is important too (I guess). Most of the files I am finding are German ones, so I can't promise if this works all the time.
Maybe install the firmware at first (Works just like the RUU, rename and copy) :
https://www.androidfilehost.com/?fid=24341993505161594
I would stick to this RUU:
https://www.androidfilehost.com/?fid=23991606952595217
i see that your cid is HTC_J15. As far as i know, the RUU must match both your cid and mid (correct me if im wrong). Are you from egypt?
anirudh.das13 said:
I've tried this thousand times. But I get an error after it starts to flash. It says- Error: -2: -14: Failed to flash from downloadzip. What is this? I tried this with both Unlocked and Re-locked bootloader. But same error. Is this due to incompatible RUU? If possible can you search the RUU for my device and post the link here?
Kernel: lk
Product: htc_himauhl
Version: 1.0
Version-main: 1.32.401.17
Boot-mode: download
Version-bootloader: 1.0.0.0000
mid: 0PJA10000
Cid: HTC_J15
Above given are my device's info.
Click to expand...
Click to collapse
What size is the sdcard? For some reason, it has to be 32GB or less and FAT32.
iElvis said:
What size is the sdcard? For some reason, it has to be 32GB or less and FAT32.
Click to expand...
Click to collapse
It is 4GB with Fat 32
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
Roobwz said:
i see that your cid is HTC_J15. As far as i know, the RUU must match both your cid and mid (correct me if im wrong). Are you from egypt?
Click to expand...
Click to collapse
I searched a long and finally found stock ROM in HTC DEV/downloads. My device was manufactured in Saudi Arabia. But in that site it shows that my version(1.32.401.17) matches with WWE S Africa. How's that possible?
Loligerloler said:
Sadly, I'm not the best when it comes to this But make sure you rename the zip file and dont put it in any folder. Just copy it directly on the card. Relocked is important too (I guess). Most of the files I am finding are German ones, so I can't promise if this works all the time.
Maybe install the firmware at first (Works just like the RUU, rename and copy) :
https://www.androidfilehost.com/?fid=24341993505161594
I would stick to this RUU:
https://www.androidfilehost.com/?fid=23991606952595217
Click to expand...
Click to collapse
I downloaded the Firmware. Then booted into RUU reboot(black screen with white HTC logo). Then I flashed the Firmware with fastboot flash zip firmware. zip. After this I get a failed error (14: failed to flash with downloadzip). What is this? The same error comes when I install via download mode by remaining the file to 0PJAIMG.zip. What to do now?
Have you checked the download for matching md5 and filesize? Could be a corrupt file.
Sent from my HTC One M9 using Tapatalk
would you mind helping me too?
Black_Eyes said:
Which model you've? CID, MID? You need to RUU your device through SD-Card method. Since you're S-On, you can only use signed firmwares.
Click to expand...
Click to collapse
I see you know what's going on with the m9. I had a slow WiFi problem, so I messed with things. Tried to clear the system cache and did something to the bootloader, now I'm stuck in airplane mode. Of course I dropped my Sim card in the dark messing with it. My phone company (ntelos) has no idea what I'm talking about and put me in a loaner phone. They have now been bought by sprint and no longer offer the m9. So... I'm trying to fix it and move it to another carrier. Maybe... or just fix it for fun..lol
How would I reset the bootloader to the way it was before I deleted random stuff?
Thanks
I am really new to all this, long ago I rooted my phone (don't know how cause I was really clueless and just watched tutorials), so now I wanted to just update my phone, but they say I have to unroot my phone to have updates on my HTC M8(Gold OPTUS). So I went into recovery mode and accidently wiped the whole data, I cross marked System, data, etc. So now I have no OS, after couple while, I've managed to use my SD card reader and put the SD card onto the computer and download the Viper Rom. Put the SD card back into the device and I installed everything and it went smoothly. When I was testing everything out the WiFi was not working, I tried turning it on, it just wouldn't swipe on or even locate any other WiFi. So I've read online that I need to update my firmware, and in order to update my do that I need to go back to my original version and update the OTA? I'm not sure what they mean about that. The version that came with the phone was v4.4.2 KitKat. Thank you I really appreciate the help!! By the way my phone use to be S-OFF but after all this now it is S-ON
When I try fastboot getar all, this is the info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(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: TELST001
(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: 23c984e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
eatme3 said:
So I've read online that I need to update my firmware, and in order to update my do that I need to go back to my original version and update the OTA?
Click to expand...
Click to collapse
Returning to the original stock (unrooted) ROM and stock recovery (matching your current, outdated KitKat firmware) should trigger OTA (over the air) updates, which will update the OS and firmware. You will probably have several updates, which will eventually bring everything up to the latest Marshmallow version.
See the following instructions and files. I believe you want to restore the stock TWRP backup 1.54.841.8 and corresponding recovery.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can install firmware 6.12.841.4 using Post #5 of that same thread, then restore stock backup 6.12.841.4. (Post #4).
It also appears that in general, you need to slow down, and have a better understanding of the proper methods and processes before rushing headlong into doing something. Wiping things in TWRP is not the proper way to unroot (doesn't unroot anything). And its obvious to you now, wiping things without knowing what the results will be (system) was not a good idea.
Do yourself a favor, and take some time to read up, learn, and gain some real understanding. Do that before diving into any of the methods. If some things seem unclear, come back here and ask. YouTube is not a valid path to real understanding, and guessing how to do things, is a bad idea also.
redpoint73 said:
Returning to the original stock (unrooted) ROM and stock recovery (matching your current, outdated KitKat firmware) should trigger OTA (over the air) updates, which will update the OS and firmware. You will probably have several updates, which will eventually bring everything up to the latest Marshmallow version.
See the following instructions and files. I believe you want to restore the stock TWRP backup 1.54.841.8 and corresponding recovery.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can install firmware 6.12.841.4 using Post #5 of that same thread, then restore stock backup 6.12.841.4. (Post #4).
It also appears that in general, you need to slow down, and have a better understanding of the proper methods and processes before rushing headlong into doing something. Wiping things in TWRP is not the proper way to unroot (doesn't unroot anything). And its obvious to you now, wiping things without knowing what the results will be (system) was not a good idea.
Do yourself a favor, and take some time to read up, learn, and gain some real understanding. Do that before diving into any of the methods. If some things seem unclear, come back here and ask. YouTube is not a valid path to real understanding, and guessing how to do things, is a bad idea also.
Click to expand...
Click to collapse
I have followed the instructions and read through everything, but the problem is that I don't have any backups nor I have created any backup files.
eatme3 said:
I have followed the instructions and read through everything, but the problem is that I don't have any backups nor I have created any backup files.
Click to expand...
Click to collapse
Did you click the link???
redpoint73 said:
Did you click the link???
Click to expand...
Click to collapse
I'm not sure what you mean by that, I clicked the link you directed me to it, found the backup version that was recommended, but in the instructions it says I need to have a folder name backups in the TWRP folder in the internal storage but I do not have one as I haven't created a backup
eatme3 said:
I'm not sure what you mean by that, I clicked the link you directed me to it, found the backup version that was recommended, but in the instructions it says I need to have a folder name backups in the TWRP folder in the internal storage but I do not have one as I haven't created a backup
Click to expand...
Click to collapse
Ok, now I understand the problem. Next time, try to be more specific about what the problem is, what step you are stuck on, etc. Sorry, I misunderstood, and thought you were saying you had no backup to restore (when the link has all the files you need).
The folder structure is created by TWRP when you make a backup. Try going into TWRP, select BACKUP. Then just check the "boot" option. Its not actually important to make a backup of anything; rather to just force TWRP to create the proper folder structure, in which to place the downloaded files. And boot.img is the smallest thing to backup; you won't actually use the backup for anything, think of it as just a "dummy" backup.
After you do that, you should have the folder structure similar to indicated in the guide. Its based on your phone's unique serial number, so its not that easy to make the folder with a file manager, etc. (which is why I'm telling you to do it the way I just indicated).
Simply put, if the problem is that you haven't made a backup . . . then just make a backup!
redpoint73 said:
Ok, now I understand the problem. Next time, try to be more specific about what the problem is, what step you are stuck on, etc. Sorry, I misunderstood, and thought you were saying you had no backup to restore (when the link has all the files you need).
The folder structure is created by TWRP when you make a backup. Try going into TWRP, select BACKUP. Then just check the "boot" option. Its not actually important to make a backup of anything; rather to just force TWRP to create the proper folder structure, in which to place the downloaded files. And boot.img is the smallest thing to backup; you won't actually use the backup for anything, think of it as just a "dummy" backup.
After you do that, you should have the folder structure similar to indicated in the guide. Its based on your phone's unique serial number, so its not that easy to make the folder with a file manager, etc. (which is why I'm telling you to do it the way I just indicated).
Simply put, if the problem is that you haven't made a backup . . . then just make a backup!
Click to expand...
Click to collapse
The first method didn't work, I am trying the second method but it seems when I get to the CMD where i type fastboot flash zip fw_xxxxxx.zip, it just says can't load and now I am stuck on this screen, can't go into recovery or even boot info the OS. Any suggestion?
eatme3 said:
The first method didn't work
Click to expand...
Click to collapse
Please provide more detail as to why it didn't work. Step that failed or you got stuck on, error messages, results, etc. Describe your actions in detail.
If it didn't work, its mostly likely pilot error, which is fixable.
If you didn't get method 1 to work, I don't think method 2 will go much better. You'll still have to restore a stock TWRP backup after you flash the MM firmware. The only difference is that you are restoring a MM backup, instead of a KK one (and saving you from doing multiple OTA updates).
eatme3 said:
I am trying the second method but it seems when I get to the CMD where i type fastboot flash zip fw_xxxxxx.zip, it just says can't load and now I am stuck on this screen, can't go into recovery or even boot info the OS.
Click to expand...
Click to collapse
"Cannot load' always means that you either didn't put the firmware zip in the right place, or renamed it incorrectly (if you renamed it).
Again, I would need you to describe the exact steps you did, in order to figure out what you did wrong (and exact commands used). The file needs to be in the same folder as fastboot.exe, and the file syntax needs to be exact (a single wrong character will cause the command to fail). Did you rename the file? If so, to what?
I assume you locked the bootloader (per the instructions) which by definition renders the phone unable to boot (so this is a normal and expected result based on what you've done). I recommend to keep trying to flash the firmware to flash (figure out what you did wrong). Then you'll need to unlock the bootloader again, install TWRP, and the Marshmallow stock backup.
Sorr
redpoint73 said:
Please provide more detail as to why it didn't work. Step that failed or you got stuck on, error messages, results, etc. Describe your actions in detail.
If it didn't work, its mostly likely pilot error, which is fixable.
If you didn't get method 1 to work, I don't think method 2 will go much better. You'll still have to restore a stock TWRP backup after you flash the MM firmware. The only difference is that you are restoring a MM backup, instead of a KK one (and saving you from doing multiple OTA updates).
"Cannot load' always means that you either didn't put the firmware zip in the right place, or renamed it incorrectly (if you renamed it).
Again, I would need you to describe the exact steps you did, in order to figure out what you did wrong (and exact commands used). The file needs to be in the same folder as fastboot.exe, and the file syntax needs to be exact (a single wrong character will cause the command to fail). Did you rename the file? If so, to what?
I assume you locked the bootloader (per the instructions) which by definition renders the phone unable to boot (so this is a normal and expected result based on what you've done). I recommend to keep trying to flash the firmware to flash (figure out what you did wrong). Then you'll need to unlock the bootloader again, install TWRP, and the Marshmallow stock backup.
Click to expand...
Click to collapse
Sorry the first method I skipped because I thought it wouldn't work without the backup folder, I am doing method 2 and this keeps staying here target
reported max download size of 1830612992 bytes
sending 'zip' (31474 KB)...
And I'm on the gray HTC when I boot into fastboot oem rebootRUU screen
I'm currently doing method one now instead of two, when I created a the backup folder on checking the Boot, I look into the HTC and there is no Backup in the TWRP folder, Ahh sorry it seems that I cannot see it on my computer when I am in recovery mode but when I go to my actual OS I can see it and extract it.
eatme3 said:
Sorry the first method I skipped because I thought it wouldn't work without the backup folder, I am doing method 2 and this keeps staying here target
reported max download size of 1830612992 bytes
sending 'zip' (31474 KB)...
And I'm on the gray HTC when I boot into fastboot oem rebootRUU screen
I'm currently doing method one now instead of two, when I created a the backup folder on checking the Boot, I look into the HTC and there is no Backup in the TWRP folder, Ahh sorry it seems that I cannot see it on my computer when I am in recovery mode but when I go to my actual OS I can see it and extract it.
Click to expand...
Click to collapse
OMG I LOVE YA!!! I LOVE YOU!! After freaking 4 hours of being clueless and stressed out, you sir have changed my life and made me the happiest man on earth! I really appreciate your help a lot! Everything is back to normal after doing method one! Once again thank you so much! Oh by the way, why does it keep updating and not install the update? It just boots my phone into recovery mode TWRP and when I turn my phone back on again, it asks me to install it again if i want, and it's installing the same update and update all over again, v4.4.3, not sure why?
Read the instructions thoroughly.
You need to install stock recovery to do update.
It won't work on TWRP.
ckpv5 said:
Read the instructions thoroughly.
You need to install stock recovery to do update.
It won't work on TWRP.
Click to expand...
Click to collapse
Do I have to download the matching stock recovery that is the same number as the download in post #2
Yes
2.23.841.1 backup + 2.23.841.1 stock recovery
Please edit the post and delete the serial number and imei
ckpv5 said:
Yes
2.23.841.1 backup + 2.23.841.1 stock recovery
Click to expand...
Click to collapse
Do as ckpv5 says. The man is wise.
Looks like I was off by one version (1.x versus 2.x). Since the OS number (main version in getvar) was wiped out (known issue with old version of TWRP which was originally used to root it) I was trying to go by the hboot and radio number. Hard to recall those old hboot and radio numbers from 2 years ago!
redpoint73 said:
Do as ckpv5 says. The man is wise.
Looks like I was off by one version (1.x versus 2.x). Since the OS number (main version in getvar) was wiped out (known issue with old version of TWRP which was originally used to root it) I was trying to go by the hboot and radio number. Hard to recall those old hboot and radio numbers from 2 years ago!
Click to expand...
Click to collapse
I always go for hboot version.
3.16 - 1.xx
3.18 - 2.xx
for 3.19 then we'll see the baseband no.
Ok Guy's
In the last few weeks there are more and more people struggling
with their devices so I decided to make a thread about a POSSIBLE fix.
It seems nobody knows what happens exactly.. but at some point the
download mode is no more accessible and you can only enter booloader mode with the white screen.
And once more this is only a Possible fix....no magical repair for your defective emmc or something like that.
This should only be a little help for some of you guys I´m not responsible for anything.
You do this on your own.
If it works, a hit on the thanks button would be nice, if not sad to say but I think you have to
go to the repair center.
We are starting at the point that you are familiar with fastboot and have a correct setup with drivers etc. on
your PC. (If not... search the forum and read how to set it up)
Files are signed so they should be also flashable with s-on.
Steps:
1. Download the Package for your Android-Version :
Lollipop:
https://www.dropbox.com/s/ts8tur5tkzv1o4l/0PJA_HIMA_L51_service_hosd_collection_900002.zip?dl=0
Marshmallow:
https://www.dropbox.com/s/pgw3hslknajl9kc/0PJA_HIMA_M60_service_hosd_collection_900001.zip?dl=0
Nougat:
https://www.dropbox.com/s/2azzxi9q65iilsj/0PJA_HIMA_N70_service_hosd_collection_9000033.zip?dl=0
2. Unzip it and take the CORRECT hosd.img for your version. (best is... you know wich version you have)
3. Connect M9 in bootlader mode and flash with fastboot:
fastboot flash hosd <filname>.img
4. MAYBE now you can enter download mode again.
5. If you don't know what version you have you can try one file after another..
fastboot outputs only okay when the right hosd.img is flashed.
(try to boot to download after every file)
6. If no one work it's pretty sure that your emmc is broken.
There is nothing more I know or I can do for you
so I can't give more support after this point.
Good Luck
broken link
You can reload the files
finitura said:
broken link
You can reload the files
Click to expand...
Click to collapse
This link will be around for a while... https://drive.google.com/folderview?id=0B4vTiHTBB629bFBtd3FUS01Ia1U
Beamed in by telepathy.
thank you
Thank you for this post which already the last hope for many people but please if you have to the files for Android Nougat please upload it many phone are broken after nougat update
thank you in advance
puede volver a subir el enlace
To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.
Hi guys,
maybe you can help me, otherwise I will open a new thread.
I got a M9 here from a friend that i wanted to fix.
Mode: Modified
S-ON
Bootloader: Locked
It began, that the Phone and SMS/MMS apps on the phone dissapeared until one day it didn't even boot up.
Can't flash anything because i can't access download mode or recovery mode, both say:
"Failed to boot to download/recovery mode" in red warning font...
I downloaded all signed htc one m9 firmwares from:
handy-faq.de/forum/htc-one-m9-firmware-ruus-otas-backups-stock-recoveries-t314182/#comment-2885828 and tried to flash every hosd.img file from the firmwares via fastboot. always got back "OKAY", rebootet but still didn't work...
Also tried to follow this tutorial:
handy-faq.de/forum/geloest-htc-m9-wiederbeleben-t320617/?page=1 and tried to flash the other files as well, but they always say "FAILED, cannot flash this partition in S-ON state" for example for aboot or other .img files...
Could you help me? Also read that some M9 have Storage Failures or problems.
I can't give you info of getvar all command in fastboot, because that doesn't work without download/recovery mode.
Thanks in advance!
Chris
There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs
Hey,
woah that reply came fast, didn't expect that.
Much thanks for the info!
Yeah the app dissapearence and then the complete failure of the phone made me think of that too... but thanks for clarification!
That a subsequent update of the firmware does not make the board functional again makes sense, haha...
I will have a look if I/he can still get a change of the motherboard by warranty, if not i will gonna just put it into the trash bin.
Well, there's no reason not to answer if I'm around and have the time to write a post. (On the other hand it might happen that I don't have enough time for several days.)
It's a bit funny that Handy-FAQ is back online. That guest account that answered in the second thread you linked is mine. I left the site over a year ago and as far as I heard from my former fellow team members the site got shut down some months ago...
Sent from my HTC One M9 using XDA Labs
Can you please re upload the files i wan't to try them out?
joostnl said:
Can you please re upload the files i wan't to try them out?
Click to expand...
Click to collapse
c.f. what I wrote on page 1 of this thread:
Flippy498 said:
To everyone whos's searching for alternative/new download links:
You can find the hosd.img inside of the RUUs that are posted in the ReadMe thread. The decryption tool that is linked in its RUU section will help you to extract the needed file from the encrypted RUUs.
For being on the safe side you should only use files from RUUs that are matching your current firmware version. You can try to use the files from other RUUs with a similar version if there's none available for your current firmware/your SKU, though. However, never flash a CDMA file on a GSM phone or vice versa.
Click to expand...
Click to collapse
Flippy498 said:
There's probably nothing you (personally) can do. That looks like faulty hardware. The main problem of the M9 is the same that every smartphone with the snapdragon 810 is suffering from. Depending on the usage of the phone the soc is roasting the phone's internals. The latest firmware version fixes the overheating but it won't repair damages that got created while the phone was used with one of the older firmware versions.
If the warranty is still valid you can send the phone to HTC for letting them change the motherboard. The data on the phone is lost, though.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hey there,
I will get a broken m9 (already paid for it) for less money which doesn´t start anymore after the update (to nougat?) but had no issues since 2 years like she told me.
I hope it´s only a bootloop, got not more information about that problem (owner has no clue about it).
I may need those files...
I think the newest firmware is installed so if i can´t access the bootloader, could you upload me this file?
I don´t want to restore stock, i want to unlock the bootloader and flash LineageOS and use it as daily driver.
My One M8 is a great phone but a cheap upgrade isn´t bad
D:\HTC M9\L51>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks
Files reuploaded + nougat hosd if somebody need good luck
Good afternoon all,
Hoping someone can help me here.
*Keeps boot-looping
*Some reason i have s-on and it may be the thing preventing me to do anything through bootloader or command prompt
*When i go into recovery mode, it goes back to boot-looping
*When i put firmware onto an SD card and put it into my phone, doesnt register anything is on there or fails to install.
Is there a way to get s-off from bootloader or download mode, even command prompt?
kranksta said:
Good afternoon all,
Hoping someone can help me here.
*Keeps boot-looping
*Some reason i have s-on and it may be the thing preventing me to do anything through bootloader or command prompt
*When i go into recovery mode, it goes back to boot-looping
*When i put firmware onto an SD card and put it into my phone, doesnt register anything is on there or fails to install.
Is there a way to get s-off from bootloader or download mode, even command prompt?
Click to expand...
Click to collapse
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best
Mr Hofs said:
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best
Click to expand...
Click to collapse
hTC download mode
*** UNLOCKED ***
htc_pmeuh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.0.8996.00007_0809
OS-2.42.710.2
Tried flash recovery in CMD and in download mode on SD card, fail due to an error 225
kranksta said:
hTC download mode
*** UNLOCKED ***
htc_pmeuh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.0.8996.00007_0809
OS-2.42.710.2
Tried flash recovery in CMD and in download mode on SD card, fail due to an error 225
Click to expand...
Click to collapse
Did you flash a firmware or a recovery image? I'm confused about your use of terms for stuff you flashed. Got a link on what you flashed?
Try this :
Download this file : https://androidfilehost.com/?fid=817550096634779605
Rename it to : 2PS6IMG.zip (NOT 2PS6IMG.zip.zip !!!)
Copy it to the sdcard and enter download mode and flash the full RUU (follow the instructions)
Mr Hofs said:
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best
Click to expand...
Click to collapse
Mr Hofs said:
Did you flash a firmware or a recovery image? I'm confused about your use of terms for stuff you flashed. Got a link on what you flashed?
Click to expand...
Click to collapse
I just flashed TWRP, then from there I installed supersu. Phone was successfully rooted. Then i lent it to someone for a day and he said "errr i went into some weird twrp program and then it stopped working". I told him specifically to only use it for Facebook, Messages and Calling but nooooo. He must of deleted my firmware, is this possible from TWRP?
kranksta said:
I just flashed TWRP, then from there I installed supersu. Phone was successfully rooted. Then i lent it to someone for a day and he said "errr i went into some weird twrp program and then it stopped working". I told him specifically to only use it for Facebook, Messages and Calling but nooooo. He must of deleted my firmware, is this possible from TWRP?
Click to expand...
Click to collapse
No he can't delete your firmware from within TWRP, only the rom can be deleted. If you do as described above the phone will be flashed to 100% stock but beware, all of the info will be erased from the phone. As it came out of the box the very first time !
I tried and here is a photo of the error
https://www.dropbox.com/s/npi8bgntwud6n8n/IMAG0981.jpg?dl=0
kranksta said:
I tried and here is a photo of the error
https://www.dropbox.com/s/npi8bgntwud6n8n/IMAG0981.jpg?dl=0
Click to expand...
Click to collapse
Strange!
Can you try to reflash TWRP and enter it again. If that works you can flash any custom rom
I tried still a no go. Here is a video.
https://www.dropbox.com/s/ti45qpjq2suw7ow/VIDEO0052.mp4?dl=0
kranksta said:
I tried still a no go. Here is a video.
https://www.dropbox.com/s/ti45qpjq2suw7ow/VIDEO0052.mp4?dl=0
Click to expand...
Click to collapse
There is a thing that might work but to be honest it's a shot in the dark. You could try to flash the TWRP image to the boot partition. When the phone starts it won't try to start the boot.img but the twrp.img
Once you can reach the recovery you must flash a custom rom, that will reflash the boot.img to the boot partition.
Are you sure the 2PS6IMG.zip wasn't a corrupt download?
roirraW "edor" ehT said:
Are you sure the 2PS6IMG.zip wasn't a corrupt download?
Click to expand...
Click to collapse
I got the files from XDA and I'm positive that they wouldn't be/
Mr Hofs said:
There is a thing that might work but to be honest it's a shot in the dark. You could try to flash the TWRP image to the boot partition. When the phone starts it won't try to start the boot.img but the twrp.img
Once you can reach the recovery you must flash a custom rom, that will reflash the boot.img to the boot partition.
Click to expand...
Click to collapse
I gave it a shot and unfortunately that didn't work either. If i can just somehow get to S-OFF state, I will be able to install any rom through the bootloader. Any ways of getting S-OFF on bricked device?
kranksta said:
I got the files from XDA and I'm positive that they wouldn't be/
Click to expand...
Click to collapse
It doesn't matter where you got them from. Downloads can get corrupted coming from anywhere. I'm not saying the files supplied are corrupted, I'm saying it's possible that your download of the file(s) may be corrupted.
If a MD5 or other kind of hash is provided for the download, use a program on the PC or app on the phone to see if the hash if the file you downloaded matches the hash that's provided for the download. If they don't match, then your file is corrupted.
This is a very common thing and should be the first thing you should check, when a hash is provided, if you have problems with flashing anything on the phone.
I don't necessarily check the hash of every single file I download for my phone, but I do of the ones that are the largest and/or most critical. Checking the hash can save a lot of trouble of trying to figure out what's wrong when there's no possibility of getting something working because the download is corrupted.
I check the hash right on the phone because even if you download something on the PC and verify it's correct, when you transfer it to the phone it can be corrupted that way, too. I use @scary alien 's Android File Verifier (AFV) https://forum.xda-developers.com/showthread.php?t=826001. It's also in the Play Store. There are also Android file managers that have built-in hash generating/checking capability.
Ok, here is a link to an image with all the files i have https://www.dropbox.com/s/9zlju4izi19a75a/IMAG0982.jpg?dl=0
Where should i start? I can do .img files and a few others, just not .zip files. I can't do a single thing in bootloader due to S-ON. what should I extract? What file in the extraction should I use and also where should I flash it to?
System?
Data?
Boot?
Recovery?
Cache?
Misc?
Thanks again, as soon as this is fixed, there is a donation coming to XDA Developers as a token of my appreciation.
kranksta said:
Ok, here is a link to an image with all the files i have https://www.dropbox.com/s/9zlju4izi19a75a/IMAG0982.jpg?dl=0
Where should i start? I can do .img files and a few others, just not .zip files. I can't do a single thing in bootloader due to S-ON. what should I extract? What file in the extraction should I use and also where should I flash it to?
System?
Data?
Boot?
Recovery?
Cache?
Misc?
Thanks again, as soon as this is fixed, there is a donation coming to XDA Developers as a token of my appreciation.
Click to expand...
Click to collapse
I'm out of the blue here. If the 710 RUU doesn't work i don't know what would work. Usually the full RUU is the last resort to completely flash the device.
Bummer..... Thanks anyway.
kranksta said:
Bummer..... Thanks anyway.
Click to expand...
Click to collapse
Last thing i can think of is to relock the bootloader and run the full 2.42.710 ruu again. That's all from my end. Sorry......
Mr Hofs said:
Last thing i can think of is to relock the bootloader and run the full 2.42.710 ruu again. That's all from my end. Sorry......
Click to expand...
Click to collapse
I seem to be (what i think) 1 step closer.
https://www.dropbox.com/s/tw4t53ykxmzjh4z/IMAG1003.jpg?dl=0
This was after Trying TWRP again, When i boot the phone normally, i dont get the Developers message under my htc (still doesnt boot though) and I noticed that adb can't find my device which tells me USB degging must have been turned off before he ruined my phone. Any other possible way to enable USB debugging Through CMD/PowerShell?
If this helps even:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: *********784
(bootloader) current-slot:
(bootloader) imei: ************644
(bootloader) version-main: 2.42.710.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: OPTUS001
I'm on twrp, not exact sure how but i'm here! ?