Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
What probably went wrong is that you installed a 32B Radio (the ion's) on a 32A device.
Now if you can't get into fastboot, hboot or recovery then there isn't anything you can do, unfortunately
Try to get the device replaced if it's still under warranty.
pelaon said:
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
Click to expand...
Click to collapse
I'm pretty sure your phone is finished but you didn't happen to mention what you were doing in the first place? Were you just updating your ROM or flashing a new Radio?
Hum, i fear it has become a very expensive white brick indeed.
I confirm it was a 32A...and i tryed to flash an ion rom wich is 32B.. gasp !
My bad... sould have waited to have my head clear before doing this :/
i'll try to see if i can get the unit replaced/fixed by official means..but idoubt it
Anyone interrested by replacement parts ?
Oh, and what is the radio bootloader mode for (action+power => blue led)...?
Several qustions as i am deseperately trying to revive my Magic:
- Is there anyway to make the phone pick up a special boot on the sdcard Without accessing recovery/fastboot ? If so what file do i need on the sdcard (sappimg ?)
- What is the radio bootloader mode for ???
Try to connect your phone to your computer using USB. Start it in different ways, and see if fastboot or adb finds your phone. As you said you can start it in radio bootloader, try boot in that too, to see if fastboot or adb finds your phone.
If it does, post your radio and hboot, maybe I can help.
Did try all possible boot method, but the phone never registers on the usb with fastboot or adb. It just keeps showing me the operator splashpage.
The last thing i installed on the phone was the "signed-google-ion-ota-14721" (now i see this was for 32B...didn't pay attention enough that day). This overrode the radio with another one included in the zip.
The installation went quite smoothly but when the phone rebooted, it froze on that logo screen...
well i'm here in the same situation...
there must be something to do...
cmon where is the nerd within you, solve this and get a ****load of respect from me
Related
Hey everyone,
i was trying to root my HTC Magic, following this guide:
http://android-dls.com/wiki/index.php?title=Magic_Rooting
i installed RAv1.2.0 : Modded ION recovery! (the H version)
used fastboot
fastboot boot recovery-new.img
then i told it to update from the update.zip that i put on the microSD card.
it said it finished loading the firmware, i did a reset, and now the phone wont load
its just stuck in the "HTC Magic" message that it does when loading, and dosnt get out of it.
I tried doing a battery pull, dosnt solve it.
i can still get into fastboot mode.
Can anyone tell me what i did wrong and how to recover my phone?
thanks.
BTW, my phone is rev 32A
OK, i fixed my issue,
connected my microSD to another phone, put the version
[Updated 7/22] [ROM] RAv1.1.0 (HTC branded Magics)
Can anyone tell me whats the most recommended version?
maybe something with multitouch?
I liked the original one as well
but i needed root to install the hebrew fonts
I don't know what had happened to my magic, but when i try to turn on it, it will not boot properly and stay at the HTC logo startup....
I know I able to factory reset the MAGIC, but that it will be very painful to me as those data will be wiped off...
Can any expert give me help? Is there anyway to solve this problem without losing all my data inside the magic??
are you on a custom ROM?
I am sure everyone will need a lot more info to help you.
so here is a basic list
1. Type (32A/32B)
2. Current ROM
3. Did you flash anything before it became that way? (SPL/RADIO/ROM/Theme)
connect your phone via usb (no need to mount) start the adb app with cmd and type 'adb logcat' you can see whats going on see if your getting errors
i flashed a rom and it took about 8 min to get to the home screen
I have a sapphire (32B)
With a Rav 1.???g recovery.
I tried updating my SPL but my phone didn't reboot after flashing now I get nothing. Did I brick my phone?
technubi : i think you did. But i could be wrong (i hope i am)
My friend asked me to try recovering his T-mobile DE Hero, it was bricked while my friend was trying to root it
I tried to flash official rom, but RUU gets error 170...
This what appears on screen when device is on:
error 170... thats the usb connection error right?
this could be because the drivers are not installed properly.
read this thread, then try again
http://forum.xda-developers.com/showthread.php?t=647353
Although error 170 is indeed USB error, (with windows 7 normally) the nasty looking Icon at the bottom of the screen does not look good, never seen that before
Let us know how you get on please
I had the same error with mine.
I ended up in installing a custom ROM, since NOTHING would work. No drivers no nothing. It just refused to read the phone.
I installed VillainROM 12, it has OS 2.1 so it's working perfectly
I had the same problem, but I was trying to flash my German G2 using an HTC Official RUU. I've been able to flash the recovery rom using fastboot and then boot it, but that's where my progress has ended. I'm about to flash VillainROM12.0.0-Full and see what happens. I'll let you know.
EDIT: VillainROM12 installed via AmonRa Recovery menu, but rebooting takes me right back to the RUU screen with an Xed-out EPROM
Nothing helped
I tried everything You said, but device is showing same screen, I also tried using SD card method but when I turn Hero on (while holding Vol-) same screen appears
Does anyone have any other idea what to do?
Its looking like a problem with a radio (drivers etc). Try to update it through recovery if u can enter there.
You can see in my first post the only screen where I can enter...
Well.. This icon with a "chip" probably say a SPL or Radio of phone is just f***ed up.. :/ You can enter to fastboot so drivers of graphics and other modules are in good condition..
wheeeler i think u should find a .zip with a official SPL and radio and update it through recovery like u did it with Villain ROM
I got some idea but I think u tried it before.
iwanrakic U can connect to phone via SDK?
Try this command. It should update it.
C:\sdk\tools>fastboot flash radio radio.img
Of course u need image of official radio.
What driver does Windows report installed when you plug it into your PC in that mode?
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)
I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"
Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?
test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?
Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.
Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse
Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium
Hey guys.
I have a bricked HTC HD2 here. I installed Android 2.2 on it, and it ran fine for a long time. But a few days ago, it got stuck in a bootloop. It gets stuck on the Android logo and doesn't get past that point at all.
What I've tried (in chronological order):
1. AD Hardreset from aMAGLDR: erased all data, but didn't fix the problem. Kept going in bootloop.
2. AD Recovery: Failed. Doesn't get past the "GO GO GO!!"
3. Repair aMAGLDR using HD2 NAND toolkit: tried repairing (150MB partition size) and installing Clockwork Mod (150MB). Same exact results when trying to get into AD recover. Only diffrence is that I now don't have a ROM on my NAND anymore.
4. Install a diffrent rom: Tried a few of them, but they all keep getting stuck on their bootlogo (HTC, Android, ...).
5. Restore STOCK ROM WM6.5: I'd love to, but I can't get into the three-colors-bootscreen. It goes straight to aMAGLDR, even when I boot holding the right buttons (volume down + power [both short click and long hold]). I had set up the ROM files correctly on the SD card.
6. Install the STOCK ROM using the HD2 NAND TOOL: after going to USB Flash mode and installing the default microsoft drivers (it didn't want to accept the Google Android drivers or HTC drivers I downloaded earlier), the flash utility keeps getting stuck on ERROR 264: CONNECTION. The only thing I can do in the HD2 NAND UTILITY is repair aMAGLDR. Other options result in the same error. Task29 can't find the phone either.
Bottom line, I cannot (ABSOLUTELY not) get into the tri color boot screen. It sends me straight to magldr. Also, my volume buttons are working just fine.
I really don't know what to do anymore. I hope someone can help me, any help would be greatly appreciated
Did you try this?
Download an original win 6.5 ROM for your HTC device from HTC webside.
- Take "RUU_signed.nbh" from an original ROM and copy it to your SD card.
- Rename to "leoimg.nbh"
- Reset your device while pressing the volume down button
powerofthink said:
Did you try this?
Download an original win 6.5 ROM for your HTC device from HTC webside.
- Take "RUU_signed.nbh" from an original ROM and copy it to your SD card.
- Rename to "leoimg.nbh"
- Reset your device while pressing the volume down button
Click to expand...
Click to collapse
Did you even read the OP's post, clearly I think not. The OP says several times that they can not get the device to the multicolor WINCE bootloader.Without being ably to boot into the bootloader they can notflash via SD card.
At the OP you can stop trying to flash via USB flasher in MAGLDR, it is only for flashing Android RIMs, WP7 ROMs, and Custom Android recoveries. If you are positive your volume down button works then you probably have some bad NAND blocks, but that is just a guess, with out access to the bootloader you are pretty much only left with flashing Android or WP7 via USB flasher in MAGLDR.
That's problematic... The HD2 NAND utility can't flash any ROMs, since the utility can't find the device (error 264).
I've tried 8 diffrent ROMS (from http://android.hd2roms.com/) by putting them on the SD card and use the "AD SD boot" function, but none of them can get past their bootlogo... All ROMs keep hanging on HTC / Android logos. Some of them used to work in the past, I recall...
Here, try these fixes and read the WHOLE POST :
http://forum.xda-developers.com/showpost.php?p=21725062&postcount=7
Thanks for the link. Unfortunately, none of the solutions worked. The battery pins were indeed bent, but after putting them back in place, the problem persisted.
I left my phone powered down all night and tried booting it in bootloader this morning. It didn't work. So that rules out solution 3 awell.
I've even put it in the freezer for half an hour (solution 5), but nothing changed.. Browsed through the last thread aswell, but there was no stuff I haven't tried yet. I can't even start tetris, since it keeps hanging on a blank screen aswell
The guy in solution #4 was facing the same issue (I think).
Especially the second part of the solution, where he talks to the OP. Read it carefully, and check out the post and thread he referred to.
Holy freakin..
After reading various threads through links in the one you suggested, I stumpled upon something called American Android. I was able to install it through the USB Flasher. Guess what, it booted PERFECTLY!!
My phone works again, thank you VERY much!!
Lorre851 said:
Holy freakin..
After reading various threads through links in the one you suggested, I stumpled upon something called American Android. I was able to install it through the USB Flasher. Guess what, it booted PERFECTLY!!
My phone works again, thank you VERY much!!
Click to expand...
Click to collapse
horayyy for the HD2 & for the guys that gave the solutions!
need information in case of not getting into the bootloader
how can I use the american android + USB flasher method to work for my hd2 if
I am not able to boot it,
can't soft/hard reset it,
can't get into the bootloader (using volume down + end key pressed).
I used android installed on SD card.
It is totally unresponsive for now. volumn keys worked perfectly when it is was working lastly !
Please tell what can bo done to it to get it working or where does the problem lies.
check your battery pins and also battery if it is charged.
and,
Download an original win 6.5 ROM for your HTC device from HTC webside.
- Take "RUU_signed.nbh" from an original ROM and copy it to your SD card(formatted FAT32.)
- Rename to "leoimg.nbh"
- Reset your device while pressing the volume or without press
Click to expand...
Click to collapse
and then you can try an android rom again..
Another solution?
I had the exact same problem. And I am under the impression that there is no solution for every case. But for me it worked to press the volume down button very softly. I tended to push the button as hard as I could, however when I only pressed the volume down button slightly it went straight to the triboot color.
Hopefully this works for some of you.
Can someone help?
Hi,I want to refresh post, becouse i have exact same problem - can't get to serial bootloader, and in MAGLDR i can use only the USB FLASHER option. If someone could tell me how to flash any new rom only through FLASHER ? Last thing i can say: my problem started from installing this app from google Play play.google.com/store/apps/details?id=eu.chainfire.livelogcat.lite (sry for that, but I can't post URL yet) it might messed up my kernel and i have no idea what to do.