Develop Bugs

I give in

I have searched the internet high and low - found many threads in many forums about the O2 XDA IIs being stuck on boot screen and wont hard reset and NO, I mean NOT a single solution posted anywhere despite the numbers of people with exactly the same problem as me.
It will enter boot loader mode and will flash with WM5 or 6 but neither have working camera or sound.
I have flashed it with Ship versions of O2 and even T-Mobile roms but both freeze at the boot screen and wont do anything else, pressing the usual buttons to get it to hard reset don't work.
So unless anyone can help me either restore the factory rom and solve the frozen boot screen or fix the sound / camera I am going to smash it to little pieces and throw it in the bin.

arcnet said:
So unless anyone can help me either restore the factory rom and solve the frozen boot screen or fix the sound / camera I am going to smash it to little pieces and throw it in the bin.
Click to expand...
Click to collapse
Don't do that, tell me the cost and post it to me. I can use the spare parts.
Seriously, what have you tried so far? (I missed the earlier posts).
Are you getting stuck at the four colour boot screen, or at the WM splash screen?

Thanks for the reply Jdc - lol - for a second I thought you were serious about the parts.
I have tried sooo much with this thing I cant remember what I haven't tried now. But to recap when I first got the Xda IIs it was locked to O2 and stuck on the boot screen with the O2 logo and the red writing in bottom left corner showing rom version. Nothing seems to shift from this state, no reset hard or soft makes any difference - take out the battery and when put back in and powered up sticks at the boot screen.
However - I can get it into bootloader mode and merrily flash WM5 or 6 which appear to work perfectly but there is no sound whatsoever and the camera says it fails to initialize the hardware please reset.
I then reflashed it with an O2 stock Ship rom - presumably WM2003 and it is exactly as it was at the start - stuck on the boot screen showing the O2 logo and rom versions.
I even tried a T-Mobile ship rom of the same version and it stuck on the T mobile boot screen.
Arrrgh!!!! I am at my wits end with it - maybe it is faulty somehow and this is not a software fault - I wish there was some diagnostic I could run on it and find out.
I currently have WM6.11 running well but as I said with no sound or camera.
Hope you can suggest something I may have overlooked or done wrong - I am new to this and it is very possible I have missed something.

arcnet said:
Thanks for the reply Jdc - lol - for a second I thought you were serious about the parts.
Click to expand...
Click to collapse
Well, I am, kind of. I have an XDA IIs as well that needs some replacement parts, so if you are going to smash the thing, I'll pay the post to send it my way.
Anyway...
arcnet said:
I have tried sooo much with this thing I cant remember what I haven't tried now. But to recap when I first got the Xda IIs it was locked to O2 and stuck on the boot screen with the O2 logo and the red writing in bottom left corner showing rom version. Nothing seems to shift from this state, no reset hard or soft makes any difference - take out the battery and when put back in and powered up sticks at the boot screen.
Click to expand...
Click to collapse
Hrm...
When it is stuck the boot screen, what does the R, G and D lines show? I'm wondering if the radio ROM might be buggered up. However, you do say that it's working... mostly...
arcnet said:
However - I can get it into bootloader mode and merrily flash WM5 or 6 which appear to work perfectly but there is no sound whatsoever and the camera says it fails to initialize the hardware please reset.
Click to expand...
Click to collapse
No sound... As in playing a sound file with WMP doesn't even produce anything?
Can you use it as a phone normally?
Have you opened it up to see if the camera and speaker(s) are loose?
One other thing to try, if you don't mind doing another hard reset:
1. Download mtty v1.42
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete) kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001 (If you only see COM 1 and COM 2, try unplugging the USB and replugging it)
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

The wierdest thing happened.
Have to say that none of the suggestions or ideas (though welcome) helped. I reflashed the WM6.1 after flashing latest radio rom. Still no sound and camera.
Last night I had kept the battery out for a few hours and then on replacing it had to do reset - hey presto after all this time the sound worked and so does the camera.???? I have absolutely no idea what I did to fix it - almost as if it needed resetting a few times - cant think what else I have done.
Anyway I am happy bunny now - it all seems to be working perfectly.

Excellent! Glad that it's working for you now, hopefully it stays working as well.
If it doesn't, don't bin it, PM me and we can talk.

Lol - sorry Jdc but i wont be parting with it now - it all works perfectly even the phone is superb now which just goes to show that even when it looks like a hardware fault it is often software - a typical PC in other words.
Cheers

arcnet said:
Lol - sorry Jdc but i wont be parting with it now
Click to expand...
Click to collapse
Well bugger. No worries, glad it's working for you.
arcnet said:
it all works perfectly even the phone is superb now which just goes to show that even when it looks like a hardware fault it is often software - a typical PC in other words.
Cheers
Click to expand...
Click to collapse
Well, a typical windows machine. My UNIX and Mac's rarely go and burble to themselves like my windows machines do at times.

Desire Z won't boot, power-cycles, HBOOT/FastBoot doesn't seem to work

Alright, so I'm not the greatest with phone tech, however normal computer tech is my thing so I can sorta get the idea of all this. But anyway...
So for ages I've had apps waiting to install updates, but I never get round to doing it. Today, at work, I was bored & decided to go through & install them. It was all going well, until my phone completely crashed whilst browsing Facebook in Opera. Updates were downloading/installing at this time, though as I say, they were all app updates, there were no OS updates or anything. So, I did what I'd normally do if it crashed or anything, I pulled out the battery & tried to turn it back on. Ever since, I now get to the "HTC Quietly Brilliant" screen, after which the phone cuts off, goes black, resets, & the cycle continuously continues until I remove the battery.
I am able to load it up into HBOOT (I think it's called, by holding down Vol Down + Power), with the following info at the top:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011, 23:36:27
Click to expand...
Click to collapse
With the following options:
Fastboot
Recovery
Factory Reset
Simlock
Image CRC
Click to expand...
Click to collapse
If I click on fastboot, it doesn't seem to work, as whilst it flashes through very quickly it says that it checks the SD & then can't find the images or something:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
Click to expand...
Click to collapse
That's as best as I can tell, as it flashes through very quickly & is hard to catch what it says. Anyway, after that, it just returns to the original menu.
If I click onto Recovery, the phone instantly resets, goes to a white HTC screen, & then to a black screen with the phone & a red exclamation mark within a red triangle. I then press Up + Power & get the following text on my screen:
Android system recovery <3e>
Use volume key to highlight;
click power key to select.
Reboot system now
Apply update from sdcard
Wipre data/factory reset
Wipre cache partition
--------------
(a while down the screen)
E: Can't open /cache/recovery/command
Click to expand...
Click to collapse
If I restart the phone then, it just goes back to how it was. I would apply an update, but I don't know what update to apply or where to get them. And I've not tried to wipe anything as, well, I'll get onto that.
Now I've looked around various threads, & was only able to find one that was close enough to my exact problem & I saw that he was able to get his phone working, with your help, so I'm hoping you could help me too.
Now, the phone has never been rooted, or had any mods or anything of that kind installed. And, to be honest, I'd rather keep it that way.
I did have some backup apps installed on the phone (which, I think backed up to my SD Card), however I've never done a complete backup of the phone onto my computer. Therefore, I'd rather not have to factory reset my phone. Or atleast, I will, if there's a possible way of backing everything up first? Though, I'd much rather root the phone & keep everything, than keep it never-rooted & have to factory reset it; if that is an option?
I'm really at a loss as to what to do, & would hugely appreciate any & all help you can give me. As I say, this isn't my strongest area, but I can kinda work my way around it. I do have a Blackberry 9800 to use as a spare, however, I'm not sure which is worse: a broken HTC or that.
Oh, some other information that might be useful:
-The phone is British, bought from Phones4U (I think) early last summer & is on the Orange/T-Mobile network, with an Orange sim card.
-I saw on that other thread about using RUU, which I nearly went to go do, until I realised it wiped everything off the phone, so I stopped myself there.
-I can never remember which version of Android means what, but I'm pretty sure we've not had any major updates since I got the phone. There may have an update, but don't think I've had any of the major ones. I'd guess it was Android v. 2.2-ish? or 2.3ish?
That's all I can think of, though am happy to answer any questions you need to ask. Again, I'd be hugely greatful for your help. And sorry for the huge essay, however I wanted to try to give as much detail as possible, so you clearly knew the situation as best as I can describe. Thank you.
Edit: Could this work at all for me?

Unfortunately, as the phone is S-ON, you're really stuck with what you can do to the phone.
The symptoms you describe are fairly consistent with a fried emmc, in which case the phone is screwed and there is nothing you can do about it (except warranty return/sell for parts)
The only thing which might work would be an RUU, hoping it isn't a case of a fried emmc.
-Nipqer

Nipqer said:
Unfortunately, as the phone is S-ON, you're really stuck with what you can do to the phone.
The symptoms you describe are fairly consistent with a fried emmc, in which case the phone is screwed and there is nothing you can do about it (except warranty return/sell for parts)
The only thing which might work would be an RUU, hoping it isn't a case of a fried emmc.
-Nipqer
Click to expand...
Click to collapse
What does "S-ON" mean? Never heard of that before.
I'm assuming a "emmc" is some chip inside of the phone? What causes that to fry? Is there really nothing that can be done?
Any idea how long the warranty is for these phones? I really don't remember. I'd assume a year, but I dunno, may be longer? I do have insurance, I believe, on the phone but (as with the last time I had to claim, about 2 years ago) I don't want to get lumbered with a ****ty replacement & getting told the Desire Z range had been discontinued. I want my flip-out QWERTY full-size (well, not Blackberry-sized) keyboard, damnit!

Your only options @ this point is to attempt an ruu (rom utility update) you can go to the htc site for the latest. The s-on is security on (this you posted with your hboot info) or if you are lucky a simple factory reset will do. You won't be able to root your phone without a bootable os, so this is out of the question
Sent from my HTC Vision using xda premium

S-ON means the security flag is set to on, it means the emmc (embedded multimedia card/chip I think) has write protection on certain partitons (/system for example) and performs signature checks on everything that tries to get flashed, making sure its legit htc roms/updates.
There seem to have been a batch of dodgy emmc chips manufactured at some point, and they have a high chance of breaking, so that nothing can be written to it. No way to predict if/when it will break, but you can see (if you have a booting rom/recovery and shell access) whether your chip is more prone to breaking or not.
Standard manufacturers warranty should be about a year, though you can see if local consumer rights gaurantees extends that any? otherwise hope for the best with insurance.
-Nipqer

Alright so there's a bit of an update, albeit not positive. My phone now just sticks on the initial white screen with "htc" on it. Not even "quietly brilliant" appears. Doesn't reset anymore, just stays on until I remove the battery. Can still get to the HBOOT screen though.
Thanks for all the responses/help guys, I knew this would be the place to come to, as you've helped me alot in the past when I had my XDA Serra (HTC Touch Pro). I guess now there's not a lot really I can do? One person suggested trying the RUU, I guess I could try that? Failing that I'll have to contact HTC/phone carrier to see what they have to say about the matter. Is it certain then that there's nothing else that could potentially be done?

[Q] HOX all stock, not booting

Hello,
I know booting issues are possible when opening the bootloader and messing with kernels and rom flashing but that's not my case and I couldn't find a post that helped me so I hope someone can help me out on this.
I am a member of the HTC User Trial program and I'm currently testing the 3.09.401.100 Jelly Bean ROM, all stock, not rooted, never opened the bootloader or flashed any firmware besides official HTC RUU when OTA came out late (UK device, always last to get official OTA )
Last night I left my phone on before I went to sleep and it had low battery. This morning I tried to turn it on and it didn't work so I thought that the battery went out. Naturally, I plugged my phone to the charger and the red led didn't light red to indicate charging for a 30sec-1minute period, than it flashed red a few times and afterwards it lighted up red as if the phone was charging. I've left the phone turned off to charge for about 3.5 hours (even after the led turned green, just to get it really fully charged).
Now, when I try to turn the phone on, it get's stuck in the "HTC ONE" bootscreen with the beats audio logo at the bottom.
Long press on the power button reboots the phone but the issue repeats and the phone does not boot past the boot screen with the logo.
Couldn't attach my HBOOT photo so here's a link: https://www.dropbox.com/s/oxk8yz19ew0gi6s/hboot.jpg

Same
I'm having the same problem with an unlocked bootloader

sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean

Bram89 said:
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Click to expand...
Click to collapse
Contacted HTC with this issue and they are not familiar with it as well. They have asked me to send a bugreport using ADB and told me that a factory reset may be required.
I will update if anything new pops up.

What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)

Vcek said:
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Click to expand...
Click to collapse
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.

IdanK said:
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
Click to expand...
Click to collapse
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?

Vcek said:
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Click to expand...
Click to collapse
I got the update directly from HTC as I'm a member on the User Trial program, no flashing what so ever, just plain OTA download & install.
I was chosen to participate in the User Trial program because I'm also a member on HTC Elevate and they asked users to join the program for testing One X software update.

[Q] What should I do in case of semi-brick?

I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.

After re rooting it it seemed to calm down and the frequency of restarting was down significantly.

Now after a week, it is starting to restart again. Should I of flashed the kernel? I see that throw around a lot here in these forums but I don't know if it pertains to my situation. Anything help would be appreciated.

TheZander said:
I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
Click to expand...
Click to collapse
delete

matt95 said:
delete
Click to expand...
Click to collapse
delete what? am I posting wrong? is there some kind of forum rule or format for asking questions or something?

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link