Related
Helo dear friends.
Well I just wanted to get some Hebrew in my Hero.
I have the Orange hero in Spain. Upgraded to official rom - 2.73.61.5, worked fine.
Now i am trying to downgrade it, so i can root it, so i can add all the fun stuff (including hebrew).
Did the gold card, since i understood that this hero is CID locked. (and maybe i am wrong). Then failed few times with error 140 when tried the 1.76.405.6 and 1.76.405.1 rom downloads. Then tried to downgrade to 2.73.405.5 rom as someone suggested here... and the process started happily, downloaded Splash1 ok, system ok, userdata ok, boot ok, bootloader ok, then GOT STUCK ON "Radio-V2 - updating" (at about 85%.. froze!)
(I attached a picture).
This happened few times, sometimes never even started to download, was just froze at the beginning of the process with: "zip header checking..."
So every-time this happened i had to disconnect it, pull the battery out or something, and try again. (I also found out that for some-reason things moved forward when restarting windows which by the way, works on parallels, mac ...)
Now the hero is stuck on the white error screen i guess, pictures attached.
Mmmm... hope someone can suggest something... straight and to the point, i feel i am going circles will appreciate allot.
Thanks in advance
Cheers!
First off ... KEEP THE PHONE PLUGGED IN! (So the battery doesn't die... If i remember right... fastboot chews through battery)
Next.. how long has it been stuck?
Well, first time for 30 minutes of no movement, then at the rest of the attempts i kept losing my patient each 20-30 minutes... in a process that might take 10?
yeah the battery ran out once..
thanks.
Trying again, now it's stuck on "system - updating". 20 minutes.
Please help.. someone?
Should i try another rom? any suggestion for Orange Spain?
Someone experienced problems via Parallels ?
Parallels as in your trying this from a VM? I would bet thats your problem! While it techincally shouldn't make a difference... I would try with real PC!
yes, virtual machine...
Ok, and that PC, should it have all the drivers for the phone? i mean now that the hero is stuck, would a different computer recognize it?
I should just download the rom to the computer and try to install it?
thanks.
You'll want to install the USB drivers (The HTC Sync download from htc.com likely has these included...)
If the VM still see's it - any PC with the drivers installed correctly will see it.
If you get the the custom recovery image flahed, you'll be able to do everything from your mac after that...
ho really? can you elaborate a bit on that? start with: " custom recovery image flahed"
Thanks.
Details @ http://forum.xda-developers.com/showthread.php?t=561124
Thanks. and this i do after i downgrade successfully the rom (with lets say a proper PC?) ?
Do i need to root after downgrading?
As far as I remember - Yes - you will need to root the phone, then:
adb remount
adb shell rm /system/recovery.img (If this fails with file not found dont worry about it)
I seem to remember needing those when I rooted my hero ...
Thanks kiall, resolved it at the end, without downgrade, no PC, just pushed the Recovery to the formatted sdcard, flashed it and the modaco rom and then radio and hebrew fonts, all is ok now...
Thanks for you time.
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.
Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?
I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.
devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..
Oh my goodness......... It is pantomime season after all
Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.
I have a problem. I have a tendency to destroy phones, which is why the last 2 phones I owned has been HTC M8. They are rugged enough for me not to destroy them.
However, 10 months ago the first one had problems with the battery, so I replaced the phone because it was cheaper than replacing the battery. The second one have worked fine, but lately the USB plug is worn out, so charging is becoming a problem.
This leads me to my problem. I (ofcause) bought a 3d one. This one was hardly used, and was 1 owner phone.
As it turns out, the previous owner had made 1 mistake. He had done the factory reset, but half way through it, it ran out of power. This means that booting it up, causes loads of errors: Gapps errors, Sense Home errors, Hangout errors and finally Google play service errors.
Now, I have worked with computers from 1991-2016 (including IT support for all the major companies) so I do know how to fix something like this - if this was windows . But since this is Android, I am a complete noob . I am just too stubborn to give up on this phone just because it has corrupt software . But this is a LOT more difficult than working with Windows I think Prior to this I have only rooted 1 phone, and that was in 2013 . I have been working on this the last 2 days .
So here is what I have managed to do so far:
I have unlocked bootloader through the HTC website and I can access the recovery program. Through that I have wiped cache, Ramdump, and done something like 15+ factory reset.
Through this I am able to get into the phone - sort of. I get a box asking if I want to send an Error rapport - and when I do that, I can get into the settings on the phone.
Through the settings, I have enabled developers options + enabled Debug, and disabled Fastboot.
I also tried to cleared cache on Gapps, google play services and Hangout - but that didnt help - so I disabled those things.
Now I can sort of use the phone. I cant update it, and it doesnt find the sim card. It does however connect find through wifi.
After all of that, I have been able to connect the phone to the computer though USB. I get both computer and phone to accept the connection (type in the code) and I can transfer files to the phone. It also works in HTC Sync software.
In Bootloader I can also get it to find FASTBOOT USB, so it does find something.
However, next step was that I had to root the phone using ADB and TWRP but I cant seem to get that connection working. Both programs finds no devices. So I am not able to actually root the phone.
I also tried RUU but had the same problem. Cant seem to get that connection working, so I can flash/root the phone.
Because of this, I tried to install upgraded versions of Android using an SD card. I can get the phone to read those zip files, but it always ends up with an: "Footer error" or "Verification failed".
I even tried the official HTC Android Marshmallow that you can download, but that came with the same verification error.
The only version that got close was an older version of the software on it. That one came up and said it was an older one, and aborted the installation because of that.
I have tried:
crDroidAndroid-6.0.1-20160826-m8
crDroidAndroid-7.1.2-20180117-m8-v3.8.5
crDroidAndroid-9.0-20190315-m8-v5.2
himauhl-3.10.84-perf-g09631a4
m8qlul-3.10.49-perf-g6f6e344
OTA507
So what am I asking help with? The simple answer is that I wanna install new android software - similar to reinstalling windows. The old phone had Android 5, and the first one Android 6. If I can upgrade to something newer, that would be a bonus, but I am good with "just" getting the phone to work .
So how do I get the phone to accept that zipfile for the android software? How do I get passed that Footer Error/verification error?
Oh and please explain the steps I need to take, for complete a complete noob . Simple steps will be greatly appreciated
*** Software status: Official***
** UNLOCKED ***
** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT- 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v 51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
I have done some more testing.
aicp_m8_o-13.1-UNOFFICIAL-20181002
cm-12.1-20150509-UNOFFICIAL-ace
crDroidAndroid-6.0.1-20160826-m8
crDroidAndroid-7.1.2-20180117-m8-v3.8.5
crDroidAndroid-8.1-20180809-m8-v4.6
crDroidAndroid-8.1-20181018-m8-v4.7
crDroidAndroid-9.0-20190315-m8-v5.2
himauhl-3.10.84-perf-g09631a4
m8qlul-3.10.49-perf-g6f6e344
OTA507
And finally the one that gave the best result:
OTA_HIMA_UHL_L51_SENSE70_MR_HTC_Europe_2.10.401.1-1.40.401.8_release_444119
This one came up with a Sideload package error - Status 255. From what I can tell by google, that is an error caused by CM or TWRP. Its suppose to be corrected by deleting some files in TWRP but I dont have TWRP.
So how do I solve this new problem?
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!