Develop Bugs

[Q] help, bricked phone

Hi all, I followed the usb brick fix by the professor but it didnt work. the phone has a black screen with white htc. also i was s-off running cm7 r2. can't get into bootloader.this is my fastboot oem boot
c:\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH09APL12956
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =421
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB992000
(bootloader) 0 androidboot.keycaps=qwerty androidboot.mode=normal android
(bootloader) boot.serialno=SH09APL12956 androidboot.bootloader=6.93.1002
(bootloader) no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:526368 msec
FAILED (status read failed (Too many links))
finished. total time: 13.261s

And why don't you boot into fastboot with back + power button?
And remember one thing: If your phone still reacts, it's not bricked.
TouchPaled from Oxygen with Transparent XDA App

bricked is so over used.... you can access fastboot?? So what have you tried to fix the problem?

It all satrted when i backed up my rom with nandriod and then tried to flash a wifi n kernel, i then got boot loop, i then removed the battery and got to into recovery to flash backup only to realise that i could access my sd card. i then tried to flash back to my stock ruu without changing my hboot partitons (big mistake) thats when i could access any options on my bootloader, all it says is alpharev cm7 r2, radio and kernel, under all that where it should have fastboot recovery so on all it says is ruu. then when i plug usb cable in i get black screen with white htc and triangles in all 4 corners with exclamation marks in them.
i tried this usb brick by the professor guessing thats the problem, i have no idea what the correct terminology for what has happened is so i'm guessing after numerous google searches that its a usb brick. I generated my mtd0.img with the cid generator and move the mtd0.img and flash image to sdcard, but got stuck after that.
I hope this all makes sense to someone and you can help me through this.
Thanks very much guys

Was ROM manager involved in any way?

No rom manager involved.

The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!

Ok.
Well going back to what BigMrB asked, can you boot into fast boot still? (Back + power from off)?
If you can, then check if when you plug in the USB cable, it changes to "Fastboot USB" please

Hey if you had taken backup of your rom then go to recovery by pressing volume down and power button then select recovery there go to back and restore and restore to the backup you had taken. Even i get my device not working while flashing new things there is nothing to worry you can always do the same.
Hope this helps you
Sent from my HTC Desire using XDA Premium App

iain2510 said:
The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!
Click to expand...
Click to collapse
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have

rootSU said:
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have
Click to expand...
Click to collapse
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh

BigMrB said:
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh
Click to expand...
Click to collapse
He doesn't have to, he can flash a stock hboot, then flash recovery and a rom, but Id rather he RUU, which would require the downgrader

I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys

mizdel said:
I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys
Click to expand...
Click to collapse
Either download the adnroid flasher from the desire dev forum here, or follow my fastboot faq in my signature to do it manually. Download the downgrader from alpharev.nl (Redeirects sometimes to revolutionary.io so may have to click the alpharev link once redirected to the revolutionary page) and flash it.
It willput your phone in a state where a RUU will work woth the stock partitions but shouldnt be used as a hboot in iots own right so if you decide not to RUU, you would be better just flashing the stock hboot.

I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one

BigMrB said:
I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one
Click to expand...
Click to collapse
+1, its always good to understand a bit of what you are doing. Some of my other faq's may be helpful too.

i flashed downgrader to my hboot and now it says rebooting and nothing is happening. how long do i wait or do i have to flash stock ruu now?

How did you flash it? It should just say:
writing....
done
If you used fastboot flash hboot blahblahblah.img

i used android flasher and attached downgrader to flasher at hit begin

Well if its still in the same state, there's not a lot you can do but pull power
Sent from my HTC Desire using XDA App

[Q] Stuck in RUU [HELP PLEASE!]

Dear developers,
I got a problem, there were a lot of things I could help my self with but now i'm stuck.
My HTC Desire Z won't boot... I can't flash anything to my phone because the bootloader is locked and I can't find a official RUU that would help me out.
I tried to boot in fastboot and I get the HTC logo with in every corner an exclamation, when I disconnect the phone I get the following screen:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-boot
Apr 11 2011,23:36:27
RUU
- no reboot possible
- screen says RUU (when plugged in, RUU USB)
- can't find device with adb devices
- can find device with fastboot devices
- not possible to make goldcard, because no adb connection
- running new RUU didn't work either (because I can't find a RUU for 2.42.405.5)
I have no solution, can someone please help me?
------- Update
I have a gold card using another phone
If I now just try to flash something on my phone I get a signature error

What happened around the time your phone stopped booting? Did you go to HTC website to get the latest ruu from them? Also boot back to fastboot and try
fastboot check_emmc_mid
Sent from my Nexus 7 using xda premium

On the HTCDev.com I can vind a RUU for software version: 2.42.405.2 but I have 2.42.405.5
Now I tried the command: fastboot oem check_emmc_mid and get the output:
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.010s
I don't understand anything about it, I hope you do
And I tried a the command: fastboot oem boot and than I get the output:
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: SH0BNRT08614
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =496
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.51.26 androidboot.c
(bootloader) id=HTC__E11 androidboot.batt_poweron=die_battery androidboot
(bootloader) .carrier=HTC-Dutch androidboot.mid=PC1011000 androidboot.key
(bootloader) caps=qwerty androidboot.mode=normal androidboot.serialno=SH0
(bootloader) BNRT08614 androidboot.bootloader=0.85.0013 zygote_oneshot=of
(bootloader) f kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:27964 msec
FAILED (status read failed (Too many links))
finished. total time: 7.423s
And mij device gives a normal boot logo (the white one instead of the black one with the "!" in every corner)

Just wanted to se which emmc you had as one is prone to failure, you do have a good one though!
Now its all about finding the right bit to flaash for you which may be a bit hard as unrooted and bootloader locked phones only allow new os versions to be flashed. I won't be near a computer for a while but when I get back ill try to dig up a file for you
Sent from my SGH-T839 using Tapatalk 2

if you would like to do I'd be very grateful!

yeah seems like you have the latest version right now other than the latest g2 ruu but you dont have super cid so you wont be able to flash that either
do you remember what happened when your phone stopped working? may help figure this out.
also just for fun what output do you get when you type this in fastboot
fastboot flash system system.img
dont worry that there is no image, im more concerned if your current bootloader will allow you to do this, i doubt it but why not
also check this
fastboot oem partition_test all

Like evry other flash I try:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
and the output of the partiton test:
(bootloader) [ERR] Command error !!!
I think the phone does not flash because the bootloader is locked? (S-ON)
I do not know how the device can not work anymore, I've bought via ebay ...'m a bit ripped off because it said that the phone worked

yeah a bit ****ty of whomever sold it to you, id try for a refund!
i take it you tried the basic stuff like booting to recovery and doing a factory reset?
this is real annoying too being without knowing the cause and having such limited access its hard to fix this thing, one of those deals where if i had it in front of me i think i could figure it out! but really you are going to need an updated ruu signed by htc to get this thing up and running if all the simple fixes havent worked... i guess you can see if debugging will work in recovery mode? if so then should still be fixable...

I tried a lot, can't boot to recovery because there is no.
it automaticly boots into RUU mode and if i try to boot it in to bootloader, system or recovery it stuck at the HTC logo.
How can I debugg the device? I know how to debug C# applications with Dot Net but a simple android phone is a lot harder
I could send my phone to your house if u think that would help?

Problem solved! partially i used a RUU from asia with a higher Version

dont send me the phone i live far away, send it back to whoever sold it to you and get the refund. hell ill sell you one that does work!
by debugging i meant to see if it were turned on on the phone, this is what allows for adb to work where you do the debugging. adb wont work in bootloader/fastboot mode, only in os and recovery. but again the problem is you can flash a recovery or os being you have a locked/shipped bootloader, the only thing to do at this point is to work with the limited fastboot commands you have or install a PC10IMG.zip, again the problem with this is they have to be signed by htc and be of a new version then your phone thinks you have installed... kinda stuck without some nicer options

Oh, I had forgotten that "adb" for android debugging bridge stands.
I do not have adb access only fastboot access, and a PC10IMG.zip does not work,like you already said it needs to have a htc signature.
Sending my phone to you was a joke.
But it is now almost entirely successful. I have an official RUU software used with a higher number, I had 2.42.405.5 and I have set up a foreign RUU and it worked "HTC Asia WWE 2.42.707.3"
I now have at least access to the HBoot, now I'll have to see how I can get S-OFF. flashing and "get_identifier_token" are still not working

Awesome news! So as of right now you have a stock ROM/Hboot/recovery?
If that is the case go right over to the xda wiki for the vision and root your phone with gfree!
Do it now before anything else brakes! Once you root (only use gfree method laid out in wiki) then everything else will be easy! Let me know how things go or if you need a hand!
*can't believe I glossed over that ruu!
Sent from my Nexus 7 using xda premium

He does not work well, he gets stuck on the normal boot logo.
If I run fastboot reboot bootloader he walks onto the boot screen. Install another RUU does not work, it stuck on "wait for bootloader"
Now the option "Image CRC" is added to the HBOOT menu, and I ran a factory reset that fails, that is what crashed my phone

can you post everything on your new hboot screen here? also everything that image crc says or any other options that may have appeared. also does it let you boot to a recovery?

Code:
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
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
crc output:
7 times vibrate
Code:
calculating... please wait
osbl: 0x7EE4ED8C
amss: 0x0
hboot: 0x887F7ABB
boot: 0x0
recovery: 0x0
system: 0x0
Press power key to go back.
I could get into recovery but after I did the factory reset (what went wrong) I can't. I can only get into the bootloader by "VOL-" and "POWER" but if I from fastboot reboot-bootloader command doing he stack onto the HTC logo.

well according to this you have no system, kernel or recovery installed right now just a locked bootloader with all security flags on.
can you try another ruu, or flash the same one again? also look in here nipqer made these and they may help you out... actually he or ghul would be very helpful on this unless you can wait longer, i have some things im working on right now and i can look this over again tonight when i have some more time.
see if you can find them or another helpful one at FREENODE make a name and join #g2root

Yeah, yesterday I was @ the chat on freenode, they told me to try the asian RUU (a) I'll try the DZ_PC10IMG.zip form your link and if that doesnt work I'll wait for the next option
Thanks a lot!

I can't flash any RUU because after the command "reboot bootloader" he keeps waiting for the bootloader but the device gets stuck on the htc logo and doesn't boot to the bootloader, even if I set it from "VOL UP" + "POWER" to the bootloader the RUU installer status remains: "Waiting for bootloader"
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
And I tried to flash a stock recovery but than I got a Signatue failure.

Try taking the pc10img off SD card or removing SD altogether
Then of will boot into fastboot, the in fastboot mode type
fastboot OEM rebootRUU
Sent from my Nexus 7 using xda premium

[Q] Unrooted HTC Desire Z on boot loop

Hello everyone. First of all, please bear with me for I am absolutely a newbie here and have a very limited knowledge on android(or any other) os. Not much of a tech savvy so please, go easy on me. I just wanna try the possible solutions you guys could give me and help my sis save hundreds of bucks from acquiring new phone or going to pricey repair shops.
The phone's HTC Desire Z A7272 (unrooted)
So here's the problem: When I try to turn on the phone, it's just stuck on the HTC logo(w/o the quietly brilliant tag below it). Prior that, my sister was just using the fb app when it suddenly froze. She waited for a couple of mins for it to respond, but nothing happens so she pulled out the battery. When she turned it on, it's stuck on a boot loop (HTC logo+quietly brilliant). We tried removing the battery for a while to let it cool before placing it back but still, same thing happens. We even tried booting it after draining the battery and having it fully charged, w/ and w/o the SD card and sim, but to no avail. Now, it's still stuck on boot loop: HTC logo(w/o quietly brilliant below) then green arrows icon with gray loading bar.
We're able to access the HBoot and here are the details:
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
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
IMAGE CRC Output:
osbl: 0x7EE4ED8C
amss: 0xB7A63815
hboot: 0x887F7ABB
boot: 0xEE80C905
recovery: 0x34337D88
system: 0xADA36D23
On Fastboot, I tried the Reboot and the other options but it just goes on a boot loop.
When I select Recovery, it boots on logo, then there's green arrows icon with gray loading bar below, and then a red triangle with down arrow inside. I read somewhere that it's the stock recovery and from there I could wipe/clear cache, but then when I tried pressing and holding the Up+Down+Power buttons, it says E: couldn't wipe cache/ mount command/recovery - something like that.
When I select Factory Reset, it just loops on the HTC logo and the green arrows icon.
I tried installing HTC sync and connected the phone via USB, but it can't detect the phone(though the PC can, as mass storage and on HBoot it shows 'HBOOT USB PLUG')
My sis downloaded an RUU from HTCDev and copied it to SD Card. She said she was able to Clear/Wipe Cache Partition and data
via bootloader but when it reboots, it's still on the same state.
After looking on some threads with similar issue, some say the ROM may be corrupted so I downloaded stock recovery, stock ROMs (changed the file name to PC10IMG.zip) and copied it to the SD card hoping that it'd reinstall the ROM but still, no effect.
Probably, the ones I've downloaded aren't compatible to the unit, but I don't know how and where to get the exact official ones for the device.
Others are suggesting that I should flash a ROM, but then it requires to root the phone - I don't wanna risk doing it 'cause I'm afraid I might do more damage.
Is there a way to simply reprogram or reformat it(just like what you do on PCs) with fresh/original stock ROM?
Some say that it could be hardware damage (eMMc/Mobo) - hopefully not >_< , but others tell that since we could access the boot loader it's more likely a software issue.
We also see people mentioning things like Gold card, adb, kernels, etc. but we just get more confused upon reading them(too much tech jargon to take)
Are we doing everything wrong? Please let us know.
Most of the solutions we find online are for rooted phones. Hers isn't and just want her phone to get fixed.
Please help. We're really clueless. Do you think this is a hopeless case?
Sorry for this very long post, but I hope I was able to explain the problem well.
Thanks for taking your time in reading this post. Any help would be greatly appreciated.
- Meg

Sounds to me like its a fried eMMC, in which case there's nothing that can be done.
Seeing as the phone is completely stock, there's not many ways to check if this is the case, but trying to flash a new stock rom won't hurt the phone at all.
Any chance you can run (in fastboot mode) 'fastboot getvar all' and copy those results here?
-Nipqer

Nipqer said:
Sounds to me like its a fried eMMC, in which case there's nothing that can be done.
Seeing as the phone is completely stock, there's not many ways to check if this is the case, but trying to flash a new stock rom won't hurt the phone at all.
Any chance you can run (in fastboot mode) 'fastboot getvar all' and copy those results here?
-Nipqer
Click to expand...
Click to collapse
Hi Nipqer!
I tried going to shipped-roms but the thing is, I actually don't know what particular stock rom to download. Is there like a key or serial number that I should look for that's compatible to my device?
Btw, here are the results for 'fastboot getvar all'
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.707.3
(bootloader) serialno: SH118RT02311
(bootloader) imei: 352212048194208
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3960mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s

Hi, i've had a similar problem and found a suitable ruu rom in 6th attempt
i've tried with 5 random rom's until i've downloaded one with radio version of my Desire Z.
try with official from shipped-roms_dot_com under Vision folder and search your rom with radio version (26.10.04.03) - there are 3 available;
change zip name, save on sd and try :good:
p.s.
maybe your emmc is still ok

merslavics said:
Hi, i've had a similar problem and found a suitable ruu rom in 6th attempt
i've tried with 5 random rom's until i've downloaded one with radio version of my Desire Z.
try with official from shipped-roms_dot_com under Vision folder and search your rom with radio version (26.10.04.03) - there are 3 available;
change zip name, save on sd and try :good:
p.s.
maybe your emmc is still ok
Click to expand...
Click to collapse
Hi merslavics!
Yep, phone's okay now I was able to find the right ruu after reading through the threads here regarding that matter. You're right, we should take note of the CID and radio versions to get the right match. Success after 3 attempts! Cheers!

[Q] Need help with unbrick.

Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
fastboot getvar all
(bootloader) version-bootloader: FLO-04.02
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 16G
(bootloader) serialno: 05848bba
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x000000031b7fbe00
all:
Click to expand...
Click to collapse

Demian87 said:
Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
Click to expand...
Click to collapse
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again

Bobbi lim said:
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again
Click to expand...
Click to collapse
Thank you for a suggestion to search your posts.
I found only the same post in this thread: http://forum.xda-developers.com/showthread.php?t=2624688
and some flash-all decision here: http://forum.xda-developers.com/showthread.php?p=49347871#post49347871
As you can see, I have already tried to flash-all few times and this piece of advice was useless in my case, unfortunatelly.

[Solved] Bootloop issue on Stock phone. Possible to fix without loss of data?

Hi Everyone
Newbie here so please be gentle. I have a HTC One M9 that has gone into a permanent bootloop for no apparent reason. It happened yesterday. Noticed that my phone was a bit sluggish so I decided to restart it but it didnt completely restart and went into the boot loop. The only significant change that I can think of was that I updated HTC Senses via the play store a few days ago and this was the first time I have restarted the phone after that update.
I have not modified the phone in any way and has the stock rom installed. I can access the bootloader and recovery mode. Here is a dump of fastboot getvar all command:
With the phone in Bootloader screen
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
all:
finished. total time: 0.149s
With the phone in download mode:
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.047s
I do not have developer mode or USB debug enabled (wish I had enabled these before this happend!! )
I have tried to install an OTA update via the the 'Apply Update from SD card' method (from recovery mode) and tried to use the OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_487250.zip but I get an error after the 'verifying current system...' message which says:
System partition has unexpected contents E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Considering that I have not modified the phone in anyway, not sure why I am getting this error message as I was hoping that applying the OTA might fix the bootloop issue. If I was able to update using the OTA, would that have solved my issue? Is there any way of overcoming the Status 7 error?
Considering that I dont have developer mode enabled and USB debug enabled, is there any posibility to accessing the system files and flashing the system partition with a stock image without having to wipe personal data or do I have no choice but to do a factory reset, loose all my data and hope for the best? Any advice and step by step guide would be appreciated. Even if I can access my personal data on the internal drive and copy it somewhere else, that would be a result!
Many thanks
Rob

There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks you very much!!!
Phone is alive again thanks to your instructions. I had given up after trying different things. I tried flashing the RUU via fastboot but kept getting an error 9 (something to do with security). Even the factory reset option from the recovery menu wasnt working (it formatted, unpackaged and then rebooted into the boot loop) hence I gave up hope and bought a Nokia 8 as a replacement (Still prefer the M9 but I'll give the Nokia some time). If you had responded towards the begining of the week, you could have saved me £300
Any ideas why the factory reset option did not work considering that I had not modified the phone in any way? (S-ON, bootloader locked, no custom ROMS or recovery mods)
Thanks again for your help. :good:

Unfortunately I don't have time to monitor the forum and answer immediately, even if it saves someone a few quid.
Under the consumer rights act (UK) you can return the phone within the 2 week grace period for a no quibble money back. You don't need a reason. After 2 weeks the device must be faulty.
The factory reset didn't work because android is inherently broken. There is no real valid explanation at this stage but the android developers know about it but do not know how to fix it.
In all circumstances where issues are encountered flashing stock the ruu via zip should be on the cards as it fixes many things on htc phones.

I've got a
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
.... Help ?

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks. Do you know any other way to do that without sd card?