Very big problem from an android noob.. - HTC One Mini 2

Hello guys i'm having a very very big problem with my HTC one mini 2 - i already spent hours at google searching my problem but i can't find a working solution so i decided to register at this forum.
Situation:
Weeks ago i rooted my HTC one mini 2 ( unlocked bootloader + rooting + installing Super SU )
The phone was definitely rooted ( root check positive ) also Super SU worked perfectly - i installed a lot of app's and used my phone normal for two weeks.
After two weeks i forgot to charge my phone over night so it shut down - when i tryed to reebot the device i stuck at
'This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.'
It won't boot - also i'm unable to start the bootloader mode because i can't turn my phone off for a restart.
The only way to turn off my phone is to let it run out of battery.
I also tryed to reboot my phone with adb fastboot but sadly my computer says waiting for device and nothing happens
I'm very desperate.. it's the first time i rooted my device, also my first time posting anything at this forum - so if i forgot to give you something you need i'm sorry
A big thanks in advance
Tata

Tata26 said:
Hello guys i'm having a very very big problem with my HTC one mini 2 - i already spent hours at google searching my problem but i can't find a working solution so i decided to register at this forum.
Situation:
Weeks ago i rooted my HTC one mini 2 ( unlocked bootloader + rooting + installing Super SU )
The phone was definitely rooted ( root check positive ) also Super SU worked perfectly - i installed a lot of app's and used my phone normal for two weeks.
After two weeks i forgot to charge my phone over night so it shut down - when i tryed to reebot the device i stuck at
'This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.'
It won't boot - also i'm unable to start the bootloader mode because i can't turn my phone off for a restart.
The only way to turn off my phone is to let it run out of battery.
I also tryed to reboot my phone with adb fastboot but sadly my computer says waiting for device and nothing happens
I'm very desperate.. it's the first time i rooted my device, also my first time posting anything at this forum - so if i forgot to give you something you need i'm sorry
A big thanks in advance
Tata
Click to expand...
Click to collapse
i think your problem is you keep trying to boot your phone with USB cable pluged in.
also power+ Vol+ should reboot your phone.
unplug USB and try.

Tata26 said:
Hello guys i'm having a very very big problem with my HTC one mini 2 - i already spent hours at google searching my problem but i can't find a working solution so i decided to register at this forum.
Situation:
Weeks ago i rooted my HTC one mini 2 ( unlocked bootloader + rooting + installing Super SU )
The phone was definitely rooted ( root check positive ) also Super SU worked perfectly - i installed a lot of app's and used my phone normal for two weeks.
After two weeks i forgot to charge my phone over night so it shut down - when i tryed to reebot the device i stuck at
'This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.'
It won't boot - also i'm unable to start the bootloader mode because i can't turn my phone off for a restart.
The only way to turn off my phone is to let it run out of battery.
I also tryed to reboot my phone with adb fastboot but sadly my computer says waiting for device and nothing happens
I'm very desperate.. it's the first time i rooted my device, also my first time posting anything at this forum - so if i forgot to give you something you need i'm sorry
A big thanks in advance
Tata
Click to expand...
Click to collapse
Hi,
First charge your device for about 2 hours, then perform the following steps:
- Flash with the boot file attached at the bootom of this link: http://forum.xda-developers.com/showpost.php?p=63859743&postcount=3
- Then try to flash TWRP again
And if I remember correct I was stuck on the white screen as well when I started even without TWRP after wrong boot flash, for me the second flash of TWRP worked, the first time did not work, stuck on the same screen when entering recovery as well...
Good Luck..

Related

[Q] Random reboot into bootloop- cannot access recovery. Please help!

a few days ago my fiance was complaining her basically stock Nexus was rebooting into a bootloop - where it displays the loading X and vibrates and then reboots and repeats every few moments (a few days after her doing the system update)- if I remove the battery for a few minutes then put battery back and reboot it will boot into the OS where it will stay sometimes for a few minutes othertimes an hour or more before going into the bootloop- so I told her I would attempt to flash a new rom. after many hours of messing with the phone and attempting to access the recovery it just will not work- the phone just goes into the bootloop - exactly as mentioned above. I have used fastboot to flash new images (userdata, system, boot, recovery etc) numerous times and it still does the same thing- crashes and reboots into the bootloop from the OS randomly and bootloop when trying to access recovery. I am pretty sure it is a hardware issue (the phone is only 3 months old) but the company i bought the phone from is stating it is a software issue and not covered by tehir warranty.
Problem is I unlocked the bootloader while messing with the rom's yesterday and am now concerned they wont honour the warranty anyway- does anyone have any suggestions as to anything else I can try? As far as I can tell as I cannot access recovery I cannot install any other roms..
Please help- otherwise I will be posting a yourtube video of me destroying a basically brand new nexus one- I really am that frustrated....
a bit more info- it was rooted but still had locked bootloader when this started- rooted using onclickroot or something- which after the update it wasn't rooted anymore- I am wondering if this has caused some low level conflict somehow- I have rooted again using superoneclick - and as stated have unlocked the bootloader.
is there any way to flash a rom using fastboot or adb on this thing- I would hazard surely there is but amongst all the information floating around for this phone I cannot find out how- I am thinking maybe I try and load cyanogen 6 or something if I could work out how to flash a rom using adb (because njo matter how many times I try to flash different recovery images it wont boot into recovery- I can access fastboot etc but as soon as i select recovery I get the bootloop...
and before I get flamed I have spent three days searching and reading and attempting everything short of voodoo witch magic. I thought my X10 was a P.I.A. to root and flash etc but really it was simple compared to the trouble this phone has given me..
I am wondeirng if some of the rom's are incompatible with some hardware- and I don't quite understand the whole radio thing either... can someone explain that?
BTW Im not a total noob- I have been around for a while without an account - then have had this account for a while but mostly just read the forums as I have no real input and knowledge to give...
...help!
Can no one help?
I have managed to get into recovery (by putting the phone in the freezer for ten minutes at a time to reduce the temperature and stabilise it enough to run for 15-20 minutes at a time)...
Have flashed different kernels this way and nothing is stable- it still bootloops because of heat....
I contacted HTC Hong Kong (it was purchased from a Hong Kong company) and they have told me there is a $350 fee to repair it as its a UK phone. Now the phone is exactly 55 days old not three months and I am really really frustrated.
Does anyone know if its worth contacting HTC UK?
I have friends in the UK I can have them send it in and recieve it from repair....
Someone please help- even if its just a comment of "just smash the damn thing..."
Thanks guys sorry about the long self centred posts but I am ready to destroy this phone- it doesnt have a mark on it either- any ideas what its worth for spare parts?

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

HELP MY phone is Bricked SPICE 410

Sad day today....all was well, tried to play around with Swap memory and then the trouble started,
First all the data on my SD card got wiped out !
After that the phone just went dead, no led when connected to charge,screen was dead no light, flicker of any sort, removed battery and tried many times still no luck...
suspected it could be a software problem so connected to to SUT, a phone was detected, tried completing the stock ROM reload, went to certain extent but then resulted in FAIL
Post that now I get a led red light when connected to charger but nothing else. does not go into download mode or battery charging animation.
Tried SUT once again but this time there is no phone detected.....
not sure if it is battery / handset problem....did the core areas in the phone get corrupted while playing with Swap ???
I partitioned using CWM, used Swapper2 app, all went well till I realised that data in SD was wiped clean.
Was on sharp mod...missing the phone badly...any help or guidance will be much appreciated...
Also will visit to service center help now that this phone is completely off SPICE stores ? yes it is still under "Warranty"
had to switch back to blackberry yucksss !!...for sometime I was infact trying to touch the screen
hoping to hear soon from you guys !!!!
First of all very sad to hear, My heartfelt condolences....
At this stage after trying SUT for multiple times, I think a visit to Spice service center is the only solution, please try it and update here
Be ready to part with your phone for a week atleast
BACK in BUSINESS
I got it Back folks.....thanks to SUT & Windows.....was breaking my head on what could be wrong...retraced back all my steps....
checked if the device has been wrongly configured by windows....went to device manager...lo I saw there was "Other Device" with something registered as Qualcomm CDMA. Deleted it...removed the usb and reconnected.....
Windows did a fresh installation of the device...after sometime I could see F drive of the device with image folder and all its contents....
Simply ran SUT once again, even now there was no display, just a gut feel everything will proceed smoothly....and yes SUT detected the device went through the installation. At one step it also asked if it could format F drive....I went ahead pressing OK....SUT finished successfully...after few anxious moments saw the familiar battery charging icon ......My day was made....and after few more anxious moments....I pressed power button to see SHARP Loading....my device is reborn again !
lesson learnt.....Don't play with SWAP mem, let the dev folks figure out and guide us...
If in any trouble keep SUT and preferrably Stock NB0 file handy.
Back in business folks !!
well done bro, was following your situation closely, so glad your phone is back to normal.
Sent from my SH8188U using xda premium
Glad that it works
Great job done
Sent from my Desire HD using xda premium
I will note your experience. Because I am a newbie who tend to do stupid things may be experiencing the same thing. Glad you can solved it and thanks for sharing.
Device still bricked
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
9K OMG without looking at the phone
ya that idiot has fu***-up my phone earlier too. few months back my glass cracked, although the phone kept working fine. he changed the glass and returned the phone 2 months later, with all signs of ra**e been committed on phone. they never knew anything about the phone and were surprised to see such a huge device from spice. so they tried all there *tools* to pry it open before realizing that what damage they have done. my gps stopped working since then, they refused to fix it saying that as the phone has been *opened* (ra**d by them) it is out of warranty, although it was still under warranty.
And now this has happened.
Mod edit : dont use any abusive words its against the forum rules if u do need to use them i have edited ur post OK
forthe said:
Hi, I have the same problem. My device (spice mi-410) suddenly stopped working. screen is blank, without power. It wont start in recovery or download mode. It wont charge. Only red led when connected to charger. That red led comes even when battery is not placed in the device and charger is connected. When i connect it to pc, windows detect it as HUAWEI Mobile Connect - Bus Enumerate Device in USB controllers. F disk is not visible nor can SUT detect it. Guess I am struck. This thing happened without me doing anything. It was working properly till night, just saw the device in the morning in this state. I had flashed official .nb0 few months back and the device was working flawlessly till now. Sending it to repairs to spice service centre is out of question (as it is out of warranty), nor those idiots know anything, they just gave me an estimate of INR 9k for repairs without seeing the device.
Any help appreciated.
Click to expand...
Click to collapse
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
vijayar said:
Hi Pretty similar to the problem I had, try and do the following
Try to use the newer SUT (1.8) version, search in this forum and you will get the link. If you are on it great.
Keep the nb0 file of any original rom - Spice GB on .32 kernel or Sharp GB on .35 kernel
connect the device with battery (hopefully charged well) to your computer, let windows detect it, launch your SUT, if you see a phone connected you are in luck !...just proceed with the next steps of by selecting the nb0 file, and selecting erase all user data.
SUT will prompt that your F disk is gone bad and do you need to reinstall it, select yes and let SUT do its stuff.
This will 100% load the ROM and F disk stuff and device will boot into the ROM once you finish.
In case SUT is not showing A phone is connected, restart your computer, ensure no other application is running, clear all earlier recognized devices in Device Manager and start fresh by connecting the device again.
Click to expand...
Click to collapse
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
haree said:
hi
this is just my exp i had to use the old sutL3 which is the old 1.7.3
to flash the original India update of the 2.3 it did not work on the 1.8
this is based on my experience when i flashed back the orignal to sell the same and get the one V . I could be wrong do correct me if so but i did this just around 2 weeks back:laugh:
Click to expand...
Click to collapse
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
vijayar said:
You could be right, if I recollect I infact flashed directly Sharp Stock ROM when I was facing the same problem. ....
btw how is HTC ONE V....you could have invested in a device with more RAM If I am not wrong this is with 512
Click to expand...
Click to collapse
hi
its ok budget buddy i didnt have much money and only the spice guy was giving me the buy back :laugh:
Phone not detected
I tried all the methods mentioned above on two different PC's. The Problem is that the phone is detected as "USB Input Device". The driver is provided by SUT. When it says device driver installed it shows as "usb input device" and the red notification LED glows. This happens whether or not battery is inserted. I charged the battery externally too.
Any Solutions?

[Q] Sprint HTC One reboot issue

I got a Sprint HTC One last week, rooted it, s-offed it and flashed several ROMs on it.
My problem is that in every ROM I've tested, the phone reboots after a couple of minutes.
Here are the ROMs I've tried so far:
- CLEAN ROM SPR 2.5
- CM-10.1-20130714-NIGHTLY-m7spr
- MIUI_m7wls_signed_07042013
- Slim-m7spr-4.2.2.build.7-OFFICIAL
- Sprint_HTC_One_1.29.651.10_Stock_Deodexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Stock_w_Goodies_One_1.06
- viperROM_One_v1.1.0
I'm using TWRP 2.5, advanced wiping: dalvik, cache, data, system before flashing the ROM.
Does anyone have sugestions?
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
alexyomar said:
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
Click to expand...
Click to collapse
I guess that's a slightly different problem then mine.
My phone is S-OFF already and I've wiped and flashed almost every single ROM out there and the phone reboots (doesn't shutdown) every 2 minutes...
After I read some other similar issues, I'm guessing I'll have to use a RUU tool to fix the problem. The other problem is that I only have Mac and Linux...
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
1alemao said:
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
Click to expand...
Click to collapse
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Aldo101t said:
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Click to expand...
Click to collapse
This!
Sent from my HTCONE using xda app-developers app
I've only used Sprint ROMs but still got those freaking reboots. Only by using RUU (provided by viperboy) I managed to solve the reboot issue.
Now I'm waiting for a software SIM Unlock solution, since I'm in Brazil an cannot unlock it OTA.
I'll post an update here as soon as I have a solution...

Bricked after supersu binary update reboot!!!

Hey guys.
im really in a bind here. as the title says my phone has died a most horrible (semi)death. it refuses to turn on all it does is flash one red and two green leds every time i hold any vol + power button combos. i took the phone to the official repair representative in my country (south africa ) and they wanted to replace the circuit board and strangely the lcd screen. i refused this as the phone was working perfectly fine prior to the reboot ( they seem like sharks to me quoted me R5000 or $350 to "repair"). if anyone can assist me in this matter i would really appreciate it.:crying:
[email protected] said:
Hey guys.
im really in a bind here. as the title says my phone has died a most horrible (semi)death. it refuses to turn on all it does is flash one red and two green leds every time i hold any vol + power button combos. i took the phone to the official repair representative in my country (south africa ) and they wanted to replace the circuit board and strangely the lcd screen. i refused this as the phone was working perfectly fine prior to the reboot ( they seem like sharks to me quoted me R5000 or $350 to "repair"). if anyone can assist me in this matter i would really appreciate it.:crying:
Click to expand...
Click to collapse
I've never heard of this issue before, but generally what you need is access to bootloader. If you don't have that, I doubt that there ever will be a software solution in sight.
Yeah its a strange problem when i connect the phone to my pc it shows up but im struggling to to find the driver it just shows in device manager as an unknown device. Adb fastboot does not pick it up either
yes there's a problem in su binary of version 2.76, all root apps won't work properly
i have formated my phone and rooted it again with older version and blocked auto update in playstore
Thanks for replying guys. How did you format your phone? When i connect the phone to my pc it just shows up as a unknown device that is named in Chinese characters. Cant locate any drivers. No access to any recovery. The phone was working perfectly fine before i got the reboot request.
[email protected] said:
How did you format your phone? .
Click to expand...
Click to collapse
from recovery (TWRP)

Categories

Resources