Related
Any idea? I have to QTEK 8500. One upgraded nicely to 6.1 - the other gives me Error 270 after 5% flashing.
How can I bypass this?
The wiki seems not to exist at least at the moment (timeouts on requests), so I am lost here to know what to do.
Please advice
270 during flashing
First of all - as in instructions to flashing - make sure the phone is unlocked, both aplication and the other unlock.
If it still happens then I had the same thing. I used the clean "boring" ROM. After I changed the bootloader to a newer version, I was ok. So first flash the bootloader - it must be given on the same page as the rom file, and keep your fingers crossed - 'couse if it doesn't work you are in for a problem with a brick.
It should actually take a few seconds only.
After that, flash the new rom, should be ok.
No bootloader update - where is it?
The rom is from the article at http://forum.xda-developers.com/showthread.php?t=374397
(6.1 standard).
So, tell me - Where can I Find the instructions on how to update the boot loader?
Thona said:
the other gives me Error 270 after 5% flashing.
Click to expand...
Click to collapse
is it "corrupted image" error? if yes - READ THE ****ING MANUAL carefully and make sure you have done all the steps in it
Hi,
I had the same problem as you....
My phone was correctly unlocked, but it won't pass the 5% after a first try when i went to 97% (communication error). I was stuck on the nice Erofish sun starting pictures.
I tries many times to flash with the 6.1 standard, but it won't go through the 5% limit (the phone turns off at 5% but it was fully loaded). So I downloaded all the wm6 roms available in this great forum, try to flash them but it was not working (still stick at 5%).
So I doanload a 5.0 rom (Expansys forum : http://www.expansys-usa.com/ft.aspx?k=73618) and was able to flash my phone....
Then after I tried again to reflash with the Erofich rom, and was able to do it. So now, I can use my phone again with the great rom.
Regards,
F.
is it "corrupted image" error? if yes - READ THE ****ING MANUAL carefully and make sure you have done all the steps in it
Click to expand...
Click to collapse
I did - I can redo them, but this is the second phone I try to flash What step do you think I am missing? And it IS the corrupted image error. Is the application unlock wrong?
fdecourt said:
Hi,
I had the same problem as you....
My phone was correctly unlocked, but it won't pass the 5% after a first try when i went to 97% (communication error). I was stuck on the nice Erofish sun starting pictures.
I tries many times to flash with the 6.1 standard, but it won't go through the 5% limit (the phone turns off at 5% but it was fully loaded). So I downloaded all the wm6 roms available in this great forum, try to flash them but it was not working (still stick at 5%).
So I doanload a 5.0 rom (Expansys forum : http://www.expansys-usa.com/ft.aspx?k=73618) and was able to flash my phone....
Then after I tried again to reflash with the Erofich rom, and was able to do it. So now, I can use my phone again with the great rom.
Regards,
F.
Click to expand...
Click to collapse
Thanx! it worked!!!!
Thona said:
What step do you think I am missing?
Click to expand...
Click to collapse
Soft SPL aka SSPL aka USPL
Häh? Sorry, but where is that in the original documentation? I must totally miss it. I follow the instructions in the post verbatim.
It's included in the directions. Problem is, your phone is probably Application Locked. Try running the Application Unlock, then run the SSPL.lnk. When you run SSPL, it should put the phone into a virtual "bootloader" screen. This is where the RUU will run the upgrade process. This should get you taken care of. If not, let me know, we'll see what we can get going for you.
Hello
I have the same problem but when I flash with this original rom after 5% telephon turns off and it shows error 294 invalid vender ID
Anyone helps
Somehow i made hard reset and it works now
EDIT: Man I'm stupid!!!!
I forgot to Relock my bootloader before running RUU. Got it figured out now. I'll just leave this here in case anyone is as stupid as me, they'll be able to self-diagnose!
And for those that don't care to search, the command is
Code:
fastboot oem lock
Thank's for looking!
ORIGINAL POST:
Hello all. I noticed a couple days ago that my beautiful new evoLTE had quite a few really bright, irregular pixels. I tried to ignore it, because I've done so much over the last two weeks making it my own, that I really didn't want to take it back for a replacement. You can only really see them on light colored, or white backgrounds with the screen at an angle.
Try as I might, I just can't stop focusing on them. So I decided I would take it back. I purchased it through Best Buy, and I also got their Black Tie service, and being that it is a hardware not software problem, I didn't think it would matter, but I decided to unroot and relock the bootloader just in case anyway.
I had flashed viperROM, so when I went to Software Information to find out which RUU to download, I couldn't find the information I needed. I opted for 1.13.651.1. RUU was unable to verify the ROM image and failed, so I tried 1.12.651.2 instead. No luck. I thought maybe a factory restore first would solve the problem, so I booted into TWRP and did just that. After it finished, I rebooted, but it just hung up on the viperROM boot screen. Waited for 15mins, just in case it needed that much time, but it never did anything but flash red....
So I rebooted into recovery and restored the first nand I made of the stock rom right after rooted and flashing TWRP, before I first flashed viperROM.
Rebooted no problem. SuperUser was back, obviously, so I removed it again, rebooted, and tried to RUU 1.13.651.1. again. This time I could actually check the Software Information screen to verify the version.
The process got a little further this time, actually rebooted my phone and sent the rom to it, but it fails every time it tires to verify the signature. I get an ERROR [155].
This is what the ReadMe says about it:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
So I tried to download RUU again. The MD5 checked out on the original, so I didn't think it would help, but I tried it anyway. The new file's MD5 checked out as well, but it still failed at the exact same part.
Does anyone have any ideas what I might be doing wrong? I have checked that drivers are loading in Device Manager when the phone reboots into bootloader. And I think I have the right drivers, they are the same ones I installed to run the one click root bat. I'm completely stumped. I'm about to try and reroot and unlock the bootloader again at it is, then try to run RUU again to see if that fixes it, but after that, I'm completely out of ideas. Anyone have any suggestions for me??
I was trying to update TWRP today and something has gone wrong. When I flash a ROM (any rom) it reboots about 3 times on its own before I get to the ring screen, then when I proceed to setup and I get this error
"System is not responding"
it gives you a option to wait or proceed, when I hit proceed it just keeps rebooting. I have a nand of the ROM that was on there, and it does the same thing as described above, it will go into TWRP so it's not bricked.
Any thoughts??
musicman625 said:
I was trying to update TWRP today and something has gone wrong. When I flash a ROM (any rom) it reboots about 3 times on its own before I get to the ring screen, then when I proceed to setup and I get this error
"System is not responding"
it gives you a option to wait or proceed, when I hit proceed it just keeps rebooting. I have a nand of the ROM that was on there, and it does the same thing as described above, it will go into TWRP so it's not bricked.
Any thoughts??
Click to expand...
Click to collapse
Something didn't load correctly or became corrupted.
Unless you have an intricate knowledge of Android and are able to analyze the logcat, which would show what is causing the looping, I would recommend reverting back to a stock ROM and starting again with the process to load a custom ROM. At least, that is the advice I would follow!
Unfortunately, with the HTC unlock process, the steps have to be followed in a very specific order or pieces of a ROM could be missing/loaded incorrectly.
Hope that helps!
joeykrim said:
Something didn't load correctly or became corrupted.
Unless you have an intricate knowledge of Android and are able to analyze the logcat, which would show what is causing the looping, I would recommend reverting back to a stock ROM and starting again with the process to load a custom ROM. At least, that is the advice I would follow!
Unfortunately, with the HTC unlock process, the steps have to be followed in a very specific order or pieces of a ROM could be missing/loaded incorrectly.
Hope that helps!
Click to expand...
Click to collapse
What rom were you tryin to flash? S-on or off?
Sent from the depths of hell
About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3
Hi guys I really need help at this point,
I have an AT&T HTC One M8 originally I was on Skydragon rom rooted till I found out MM was finally available. I then relocked my phone and flashed original firmware to get back to origianal. I tried The OTA at that time but no luck. So I downloaded the MM ruu file from HTC.com and still no luck. I tried like 5 times and it would get stuck step 2 of 2 sending rom to phone... After a few times and calling htc still no luck. The rep said it would be ok to just disconnect and everything was fine I guess. Today I came across a thread here on xda in which a member mentioned flashing the MM firmware first then try the ruu again. The firmware updated but the ruu is still not working. Still stuck on step 2 of 2 sending rom to phone for almost 3 hours now... The biggest problem now is unlike the last times when I tried disconnecting this time my phone would not start. it just gets stuck on white HTC logo screen and that's it... so frustrating... so now I am without phone - please help!
it allowed me to try to run the ruu again but still stuck at the same spot and still wont startup.
someone anyone please help!
side not everyone mentioned memory possibly being the issue - well I checked and I have 21 gb of internal memory:crying: available so...
last thing: I also tried flashing back to stock ruu and now it wont let me after flashing the firmware so i have no idea what to do now.
My responses below in red font:
rsuarez74 said:
I then relocked my phone and flashed original firmware to get back to origianal. What exactly did you flash (file name, I assume an RUU?)?
I tried The OTA at that time but no luck. What does that mean "no luck"? Any error messages, how far did it get, what were the specific results?
So I downloaded the MM ruu file from HTC.com and still no luck.
I tried like 5 times and it would get stuck step 2 of 2 sending rom to phone... Today I came across a thread here on xda in which a member mentioned flashing the MM firmware first then try the ruu again. The firmware updated but the ruu is still not working. Still stuck on step 2 of 2 sending rom to phone for almost 3 hours now... There is a connectivity issue, probably due to PC configuration. Win7 and USB2.0 have the best compatibility. If Win10, you can try to run the RUU in Win7 compatibility mode, and see if that helps. Try another USB port, try another cable. You may have to resort to another PC, if you have access to one.
side not everyone mentioned memory possibly being the issue - well I checked and I have 21 gb of internal memory:crying: available so... The free storage issue (need 14 GB free, maybe more) only applies to the OTA, from what I've seen. It doesn't apply to the RUU.
last thing: I also tried flashing back to stock ruu and now it wont let me after flashing the firmware so i have no idea what to do now. "Stock firmware" meaning what (exact filename)? I assume you mean Lollipop (LP) RUU as "stock" means different things to different folks - so you need to be specific. Once you've flashed the MM firmware, you can't run the LP RUU, unless you find and flash the LP firmware first. The firmware needs to match the RUU, in other words (thanks to some new requirement HTC added with the MM RUU). But seeing as the goal it to RUU to MM, I'd not mess with going backwards at this point, and focus on getting the MM RUU to work.
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
1. RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2
2. got to "2/2 sending rom image to android phone" (black htc logo screen) hung for like 3 hours.
3. I am using windows 7 with usb 2.0 and all proper drivers installed
4. I tried installing the mm firmware before installing th mm ruu but still no luck - same results
rsuarez74 said:
1. RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2
2. got to "2/2 sending rom image to android phone" (black htc logo screen) hung for like 3 hours.
3. I am using windows 7 with usb 2.0 and all proper drivers installed
4. I tried installing the mm firmware before installing th mm ruu but still no luck - same results
Click to expand...
Click to collapse
You really need to stop posting "no luck" without giving any details. I advised you on that earlier, and I don't like repeating myself. What does that mean "no luck"? Please give as much detail as possible. You didn't specify whether the firmware actually installed or not. How far did the firmware install get? What was the output on the screen? Any error messages? Did you flash the firmware twice (which is usually required)?
Its clear you have some general connectivity issue. Until you solve it, you can run RUUs forever, and they will still fail.
Did you try a different cable (as I previously advised)? Is the phone in fastboot mode when you try to RUU? Any response to command: fastboot devices
redpoint73 said:
You really need to stop posting "no luck" without giving any details. I advised you on that earlier, and I don't like repeating myself. What does that mean "no luck"? Please give as much detail as possible. You didn't specify whether the firmware actually installed or not. How far did the firmware install get? What was the output on the screen? Any error messages? Did you flash the firmware twice (which is usually required)?
Its clear you have some general connectivity issue. Until you solve it, you can run RUUs forever, and they will still fail.
Did you try a different cable (as I previously advised)? Is the phone in fastboot mode when you try to RUU? Any response to command: fastboot devices
Click to expand...
Click to collapse
ok I apologize. The mm firmware did install correctly as far as I can tell. Then tied the mm ruu again but still hung at step 2/2 sending rom image. Only difference hat time s when I tried to disconnect I was stuck on white htc screen. I also tried new cable. and yes I did mostly everything in fastbot mode. fastboot seems to be working ok.
Could you boot a TWRP recovery img from fastboot and then use it to restore a NANDroid backup? This assumes you're still having problems.