yashsingh1/xdaforums huggingface dataset:
[HTC Desire 300] ivoa:
Thank you for your answer.

Is there any way to check hardware or parts of hardware of phone with fastboot or some other tool. If it is hardware failure then nothing can be done:( Can I check that somehow?

However, if it is software problem, then I would like very much to go on:)

You have suggested to try to find a working recovery and flash it. I have one working Desire 300 bought at same time in same shop with same mobile provider. Can it be used for necessary files (images) or whole phone ROM - can I take files from that phone?

I can try to flash your recovery image, but as you sad, I successfully flashed SPaWn's recovery. During flashing process on phone screen was visible small vertical green progress bar for loading and then red progress bar for writing and double OK confirmation on prompt window. Is this indication that phone RAM and other hardware is good after all?

I can extract boot.img from the stock odex rom (downloaded from link in my previous post) and flash it to see if regular boot is ok.

If hboot or radio is corrupted, can I use file(s) from working phone to fix? Before that should I try to put it in S-OFF? I saw few pages where this procedure is described. Should working phone also be in S-OFF for getting these file(s)?

What do you suggest to do first?

You sad:

"It might have been a better idea if you had tried getting a replacement instead of unlocking it.

But honestly I can understand the need to try and fix it yourself. In any case if you ask htc nicely,

and explain the situation to them, they might still be willing to help."

Unfortunately, phone is out of warranty and this was not an option since screen is a bit cracked (but it worked for months that way). I repair electronics for years and I am glad that you understand my need to try to fix it myself:)

Than you very much in advance,

Ivo
[HTC Desire 300] 4m8:
I don't know of a way to use fastboot for hw diagnostics, sorry.

I've never seen a progressbar while flashing via fastboot, then again I'm only checking

the output of fastboot. (written x kb in y seconds etc)

But I never had to confirm anything while doing so. Are you sure you did everything correctly?

You mentioned 0P6AIMG.ZIP in your first post. This is not the right way to flash a custom boot or recovery!

You need to use fastboot for this to actually work.

web: grab my recovery and extract it to get recvovery.img

phone: Boot to hboot and select fastboot don't forget to connect USB

pc: in bash or dos prompt > fastboot flash recovery recovery.img

pc: check if everything went ok

phone: select bootloader and then start recovery

fingers: crossed

And yes, your secondary device could be very helpful in order to restore the primary BUT

there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.

Still it's an excellent source to get system data and boot.

I've never tried restoring a cwm backup of one device on another of the same model, but as long as the partitioning

is the same I can think of no reason (except a cwm sanity check) why this shouldn't work.

You could also use dd if cwm fails but let's try the uncomplicated way first :)
[HTC Desire 300] ivoa:
Hello,

I tried with your file, but crossed fingers didn't help...endless loop is here again, first time with entering recovery written.

About confirmation during flashing, I thought on this confirmation (this is taken with your recovery.img file):

C:\HTC\fastboot-win>fastboot flash recovery recovery.img

sending 'recovery' (6484 KB)...

OKAY [ 1.214s] <----this confirmation

writing 'recovery'...

OKAY [ 2.321s] <----this confirmation

finished. total time: 3.537s

Sure I didn't need to click on anything to confirm. Sorry for my unclear explanation at previous post:)

About 0P6AIMG.ZIP in my first post - I saw procedure for upgrading here: forum.gsmhosting.com, guide-how-upgrade-your-htc-android-phone-microsd-card (I am not allowed to put external link yet)

In step 2 there is explanation for renaming upgrade file to model number + inf. I found that when SD card is inserted, during fastboot I see on screen following:

SD Checking...

No gift file...

Loading...[0P6ADIAG.zip]

No image!

Loading...[0P6ADIAG.nbh]

No image or wrong image!

Loading...[0P6AIMG.zip]

Loading...[0P6AIMG.nbh]

No image or wrong image!

So I thought that phone expect any of these files for booting. This is why I renamed original ROM that I found and put it on SD card and try to boot. Then I got 'Lack of heap' error.

One more try that you have suggested is to try extracting the boot.img from the stock odex rom and flash it. (fastboot flash boot boot.img). Is this image from zip file which I found on link from my first post, or should boot.img file be taken from working phone (if yes, how to do that)? Zip file name 'HTC_Desire_300(Zara mini)_stock_odex_1.10.401.4_root_updated_v.1.0.1.zip' indicates root updated and my phone is/was not rooted.

You sad:

"And yes, your secondary device could be very helpful in order to restore the primary BUT

there is no way to switch this phone S-OFF, at least none that I know of, so you won't have the permissions to modify hboot or radio.

Still it's an excellent source to get system data and boot."

Can you please tell me how to get needed files from working phone and which files? I assume that I should use commands in ADB tool?

Thank you for your time that you are spending for my problem:)

Ivo
[HTC Desire 300] 4m8:
For now focus on getting the phone to boot again. So far the recovery partition seems to be broken.

Next try flashing the recovery image on the boot partition (flash boot recovery.img) to check if you can boot from there.

If it works you can continue by replacing it with the boot.img from your other device.

If you can't get recovery to boot from either the boot or recovery partition, you can consider this phone a brick.

At least until S-OFF is available so you can try replacing hboot and radio.

To get the boot image from the the other device you will have to install a recovery.

Afterwards you can just make a backup and you'll find the boot.img in the backup folder

You could also grab any files you want from system or data by renaming *.tar.a to *.tar and extracting it with 7z

Alternativly dd can be used from an android terminal to backup any partition to an img file on the sdcard, (requires superuser)

It is true that the files hboot lists while starting are used to start diagnostics and updates depending on the zip file

but I'm pretty sure it requires the contents to be signed by htc in order to work.
[HTC Desire 300] ivoa:
I tried to flash boot.img extracted from the stock odex rom (fastboot flash boot boot.img), but endless loop is still present. So obviously phone can't continue in any direction after first initialization.

Since currently there is no way for S-OFF, is there anything else to try or we came at stop point:(?
[HTC Desire 300] 4m8:
Technically it's over. But just to be completly sure try to flash the recovery.img as boot.

We can't be certain that your system partition might be corrupted aswell unless we try a 100% working ramdisk.

if recovery can't start from either the boot or recovery partition you'll have to wait for S-OFF or just use the device for spare parts.

If it actually boots you can still use it to restore your device but remember if you restore a backup or flash a new rom you will

permanently loose recovery until you reflash it to boot again, sacrificing your system in the process.

Still, good luck for your final attempt and my condolences if this last resort also ends as a failure.
[HTC Desire 300] ivoa:
I will try that, just tell me can I run 'fastboot flash boot recovery.img' (with your recovery image or SPaWn recovery image) or should I rename recovery.img to boot.img and then run 'fastboot flash boot boot.img'

What I mean does file name during flashing matter or only content of file is important?
[HTC Desire 300] 4m8:
the filename is completely irrelevant. The important part is that it is smaller or equal to the partition size of boot.

Since both boot and recovery are roughly 16MB, everything should be fine. Well in your case probably not...

but you know what I mean. ;)

btw:

After a little pondering my guess would be a broken RAM.

For one it is unlikely that your device managed to kill radio (which wouldn't matter for recovery)

or that hboot got damaged, since it would usually end in it not booting whatsoever.

Furthermore it is highly unlikely that two partitions of your internal emmc broke at the same time.

And since ramdisks (like boot and recovery) get loaded into RAM in order to work. (hence the name)

I'd guess, with a rather high certainty, that somehow your RAM got damaged and now your device is toast.

For your sake, I hope I'm completely wrong. :angel:
[HTC Desire 300] ivoa:
I have tried, but with same results......

I think that we can conclude that I indeed have hardware failure (most probably) with access to RAM.

What else can I say except thank you so much for time spent and for advices that you gave me.

My next step will be to disassemble the phone and see if there are any obvious cracks on printed circuit board, although I think that chances to repair this are close to nothing since this is double or multiple layer board packed with SMD components.......

I will certainly let you know if I make any progress!

Once again, thank you very much for all. If you come to Zagreb, we can always go for a beer:)

Best regards,

Ivo
[HTC Desire 300] ivoa:
EXTRA! EXTRA! Read all about it...!

It works!!!!!!!!!!! Yes, it works again!!!!!!!!!!!!!!!

A friend of mine has friend who works in repair shop and, as she heard sad story about phone, told me to bring it to see if anything could be done. So I left phone at shop and tomorrow she called me and told me that it works! She explained me that her colleagues put new software and after 40 minutes phone was working!!!

So, after all, it was not hardware failure. It could be that part of software which is protected with s-on was corrupted. However, it works again!!!

I just wanted to share news with you:)
[HTC Desire 300] 4m8:
Glad to hear you got it booting again.

enjoy the working wifi on the stock rom. ;)
[HTC Desire 300] jitendra42:
i have same problem plz help me...
[Xperia Z3 Compact General] UserX10:
HI [MENTION=535343]all[/MENTION],

now that we have a FW for the device - is root possible?

All known root methods are not working.

BR

UserX10

Edit:

Solved -> Thanks you DooMLoRD

http://xdaforums.com/z3-compact/orig-development/d58xx-cwm-based-recovery-6-0-4-7-root-t2890231
[Xperia Z3 Compact General] dillalade:
Delete.
[Xperia Z3 Compact General] King p1n:
Jeez.

People haven't even got their hands on the phone yet...

Be patient ;)
[Xperia Z3 Compact General] plisk3n:
Anyone wanna try Framaroot?

http://framaroot.net/index.html
[Xperia Z3 Compact General] raxman68:
framaroot does not work ...
[Xperia Z3 Compact General] plisk3n:
Ok because I saw it posted on this blog and thought it would work. Strange!
[Xperia Z3 Compact General] CollinsJ:
Well, it says "tested on device" and is from 9/4, before the device was even unavailable. I'd be careful that apk isn't something more.
[Xperia Z3 Compact General] Dsteppa:
Yeah that's also the reason why I decided not to download it, I'll just wait till someone @ XDA finds a way to root the device. It's not like we'll die because our device isn't rooted for x weeks/months.
[Xperia Z3 Compact General] Frontier3:
Weeks/months?! I would die! It's been a day and the amount of things I can't do is driving me nuts!
[Xperia Z3 Compact General] tilal6991:
If you have an unlocked boot loader see what I say at http://xdaforums.com/showthread.php?p=55709585. If you don't I think you'll be waiting for a while - someone needs to find an exploit and write the app/code needed to exploit it. This has become increasingly hard as Android has become more secure - before Towelroot AFAIK the Z1/Z2 was not rootable for a long time. You'd probably be waiting a similar length of time for the next big root exploit.
[Xperia Z3 Compact General] mudnightoil:
Would it not be helpful to contact Sony themselves? They're increasingly developer friendly, these days. Maybe they'd be willing to offer pointers to root app developers?
[Xperia Z3 Compact General] tilal6991:
Well I know people at Sony and long story short: if you want root unlock the boot loader. Its as simple as that. You have to understand that while a root exploit looks nice to tinkerers its also a serious security issue which must be fixed - that is why many root solutions also patch the exploit they use after using it.
[Xperia Z3 Compact General] sublimnl:
Does unlocking the bootloader require wiping the phone? I know this is required on the nexus phones. If it requires wipe then its the very first thing I'm doing once I get the phone out of the box.
[Xperia Z3 Compact General] mudnightoil:
I'm aware of this ... but on the one hand being one of the few if only manufacturers to provide official unlocking for the bootloaders (with the obvious intention of spurring development etc), but on the other actively closing non-simple (i.e. ones requiring a dedicated program) root 'exploits' would seem a little at odds. Is it really that black and white? You'd think it might be in their interests to provide an official complex / secure rooting method.
[Xperia Z3 Compact General] tilal6991:
Yes. It will wipe everything AFAIK - double check with the website.

Your statements contradict themselves. Rooting without unlocking the bootloader needs a security flaw. How can any method which leaves a security hole be secure?

Bootloader unlocking gets around this by letting you control the boot partition of the device so you can disable the "security barrier" that android provides. This is a choice you are explicitly making which is why it is the only "secure" way to root.
[Xperia Z3 Compact General] MrOeyta:
Does towelroot work?
[Xperia Z3 Compact General] bmbm:
Unfortunately Towelroot does not work.
[Xperia Z3 Compact General] tacocats:
I've read some people saying that unlocking the bootloader causes you to lose your DRM keys which apparently would affect software/ camera issues?

Can anyone verify this?
[Xperia Z3 Compact General] dillalade:
This is very true. On the z1c I neglected to back up the TA partition. And apparently lost native mirror cast and some camera features when I rolled the device back to stock.

Back up your TA partition before unlocking BL.
[Xperia Z3 Compact General] tacocats:
Any idea how this could be done?
[Xperia Z3 Compact General] dillalade:
http://xdaforums.com/showthread.php?t=2292598

Those that have rushed into unlocking the BL without backing up the TA partition risk voiding warranty in afraid.
[Xperia Z3 Compact General] tacocats:
Thanks for this. But z3/z3compact isn't listed as a compatible device... hopefully someone comes up with a root exploit that doesn't require unlocked bootloader soon :/
[Xperia Z3 Compact General] dillalade:
I didn't say it was listed. Merely pointing you to the how to.

But that will be the procedure.

Await root.

For now embrace stock.

I myself an die hard aosp veteran. For instance when I got the z1c only 4 months ago I rooted and customised it asap and have no time to stock.

Being forced to on this occasion with z3c I just say I'm enjoying the experience. It's one of the cleanest second to sense6. And the battery options baked into xperia stock are fkin fantastic.
[Xperia Z3 Compact General] tacocats:
I actually want to use stock rom but I still require root for superuser
[Xperia Z3 Compact General] dillalade:
(Apologies for grammer mistakes in previous post :sly:

So what type of things are you wanting to do/achieve when rooted on stock... Xposed I assume?
[Xperia Z3 Compact General] tacocats:
Yes that! I'm certainly installing gravitybox once rooted and also titaniumbackup.

I don't like to say this because people on xda frown upon free loaders but I sometimes use it for paid apps like poweramp and lucky patcher :/
[Xperia Z3 Compact General] dillalade:
Cool all I want is:

1. SD write access.

2. Privacy guard (CM)

3. Active Display (omni)

4. Kill with long press back button - Navigation bar tweaks.

5. Swipe status bar brightness control

6. Titanium to rid/uninstall bloatware apps.

Just to name my most wanted
[Xperia Z3 Compact General] tacocats:
Oh and the biggest reason why I'm getting gravitybox is to get the "quick pulldown" that cyanogenmod has. I'm currently running cm on my HTC one and loving it but can't use it for z3c cause I like the multitasking and camera too much to give up.
[Xperia Z3 Compact General] Dreamweaver:
hey early adopters:)

After reading this Thread so far I decided not to buy a Z3C until there is a possibility for rooting that device.

For me personally there is no chance running any smartphone without

- firewall (AFWall+)

- privacy fake & control tool (Xprivacy)
[Xperia Z3 Compact General] tilal6991:
I'm presuming you are unwilling to unlock the boot loader. If so yes its unlikely root will occur soon.
[Xperia Z3 Compact General] clouds5:
I'll wait for a few weeks to see if my device has any issues that would be covered under warranty then I'll go ahead and unlock it. If that's the only way to achieve root access. Android just isn't the same without root :)

-Biggest reason: gesture control, that's how I like to use my devices..

-Nav bar tweaks

-titanium backup

-kernel tweaks

-full system backups

-touch to gamepad

-xposed

-I have to admit it: ads. I'll buy every ad free version of apps but there are still way too many without that option.

I could go on and on :) but the z3c is very usable without root I have to say.
[Xperia Z3 Compact General] marumari:
It's a bit ugly, but I finally got there. Unlocked bootloader, of course:
[Xperia Z3 Compact General] russel5:
Tell us, how
[Xperia Z3 Compact General] TiMiN8R:
Yes please do share how you did it.
[Xperia Z3 Compact General] muken:
Do you know which features will be disabled by the fact that the DRM keys will be wiped during the unlock process?

It seems to be no good official information from Sony on that?

(I don't want to lose any camera features...)

Edit: It would be interesting to see if the X-reality feature will be disabled when unlocking the bootloader.

I tested (on an unlocked z3c) creating 3 screenshots with the different settings, and the effect will be captured on the screenshots so they can be compared on a computer screen.

Check out this post: http://xdaforums.com/showpost.php?p=55694359&postcount=5
[Xperia Z3 Compact General] dew.man:
Anticipation is killing us!?

:confused::eek::D
[Xperia Z3 Compact General] dillalade:
On the z1c we lost some camera functionality and native mirror cast. Also by not backing up TA partition you void your warranty.
[Xperia Z3 Compact General] muken:
I have read reports on that, but couldn't figure out exactly which camera features you lose...
[Xperia Z3 Compact General] dillalade:
Apparently the DRM keys hold some keys related to camera functionality. Without which camera will work but not to the best of ability. Other features as well as camera and mirror cast may be affected to.

Warranty would be a big loss if you come into any warranty applicable RMA.

TA partition backup would be the ideal.
[Xperia Z3 Compact General] marumari:
Warranty is a big loss, but everything else seems to be working. I was able to take pictures with the camera at ISO 12800, which indicates that BIONZ, the special processing, is working. Otherwise, you're limited to ISO 3200. Still, it's up to any of you whether or not you want to take the risk involved in unlocking it.

Here are the steps I followed. Again, it's a bit hackish. Many of you may just want to wait for an official recovery, whenever that happens. Presumably you'll have to redo these steps after software updates.

1) Unlock your bootloader

2) Enable developer options, unknown sources, etc.

3) adb root

4) adb remount

5) Unzip supersu.zip to supersu

6) adb push supersu/ /tmp/supersu/

7) adb shell (make sure you are root here)

8) sh /tmp/supersu/META-INF/com/google/android/update-binary

9) reboot

Hopefully that'll work. No warranty, no guarantee, I may have misremembered, etc. etc.
[Xperia Z3 Compact General] Frontier3:
That achieves an actual root of the phone? Has anyone verified those instructions yet? (i know i know, she just barely posted it)

EDIT* sorry about the incorrect pronoun!
[Xperia Z3 Compact General] marumari:
Well, I can consistently get a root shell and SuperSU intercedes. I've also used TitaniumBackup to restore app+data on my phone without issue. Like I said though, no promises.

Also she, not he. :)
[Xperia Z3 Compact General] TiMiN8R:
DooMLoRD just released an insecure kernel with CWM

http://xdaforums.com/showthread.php?t=2890231
[Xperia Z3 Compact General] marumari:
Even better! :D
[Xperia Z3 Compact General] NRG1975:
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3

CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3 Compact
[Xperia Z3 Compact General] munkustrap:
Am I understanding it correctly: to unlock th BL without compromising DRM/warranty you have to back up TA first; to back up TA with the tool above you have to root the device first; but the only method to root our Z3c is to unlock the BL first.

Kinda endless loop? :confused:
[Xperia Z3 Compact General] Hjbotha:
Correct. Unless someone figures out how to gain root through an exploit, which bypasses the step of unlocking the bootloader.
[Xperia Z3 Compact General] Why So Serious?:
On all previous Xperia phones, this has been the case until a security exploit is found to root phones with locked bootloaders.

It used to be quick, but the Z2 took a couple of months (iirc) as Android has become more secure.

I'll wait for a locked BL root, backup TA's, unlock BL and go from there.
[Xperia Z3 Compact General] dillalade:
Only a matter of time
[Xperia Z3 Compact General] ahong99:
I think so. In weeks ,the issues may be fixed.
[Xperia Z3 Compact General] mickliq:
Has anyone installed Xposed yet? Results? Were you able to change the notification and/or navigation icons?
[Xperia Z3 Compact General] dew.man:
Xposed (dalvik) works great!

HOWEVER, I did a clean flash and rooted with the new CWM recovery prior. Should be same as this approach but you never know...
[Xperia Z3 Compact General] mickliq:
Ooooh so happy. Android L navigation! I'm going to need to swap the status bar icons for AOSP, I see you have GB loaded for that task!
[Xperia Z3 Compact General] marumari:
Yep, no problems with Xposed. I've been using GravityBox, App Settings, and AppOpsXposed without any issue. The only problem I have been having is that GEM Xperia Xposed, despite enabling the option, doesn't seem to replace the default lockscreen with the AOSP lockscreen. Hopefully that will be fixed soon.
[Xperia Z3 Compact General] plisk3n:
Quick question, if I unlock my bootloader does the phone get factory reset? I had customized the phone and don't wanna redo everything.
[Xperia Z3 Compact General] marumari:
Yes, every Android phone does this, for security reasons. Sorry!
[Xperia Z3 Compact General] plisk3n:
Ok thanks for the info! Has anyone whose rooted tried changing the system dpi in the build.prop yet? I find the icons and whatever too giant.
[Xperia Z3 Compact General] marumari:
I think most people just use either Xposed modules or other launchers these days. There are Xposed modules that let you adjust DPI on an app-by-app basis, without messing up other applications.
[Xperia Z3 Compact General] Galactic2:
How did you get Xposed Modules to show up in your Phone settings like that?
[Xperia Z3 Compact General] dew.man:
Xposed module called "Xposed Preference Injector"
[Xperia Z3 Compact General] Failipp:
Since I can't post in the Orginial Dev Thread, is it safe to flash the Kernel on my Z3c running FW 23.0.A.2.98?
[Xperia Z3 Compact General] TiMiN8R:
Probably. Unlikely kernel has changed with minor firmware revision. If not, you can just flash the kernel from the .98 ftf with flashtool.

I might give it a go tonight, am on .98 also.
[Xperia Z3 Compact General] dew.man:
I first flashed the global 93 image, and then the new recovery/kernel. No issues.