Hello there!
I have an HTC One Mini 2 that I've managed to put in a boot loop by messing around with the build.prop file. I'd put CyanogenMod 12 on it, that part went fine and it worked for a few days, but then I tried to fix a dual mic issue (that had prompted me to flash CM12 in the first place, in an attempt to fix it - it didn't) by adding an attribute that was supposed to disable it (the dual mic; according to some pointers I'd read on various forums). The app I got to edit build.prop, however, (total commander couldn't save despite being granted root privileges, for some reason) apparently messed with the permissions for that file, and now it won't boot. In anything. If I try to boot it normally (just power button), nothing happens, if I try to boot into recovery I get the HTC logo screen for a couple of seconds, then it dies again, neither adb nor fastboot lists it in devices, and windows doesn't see it either.
I even tried getting it to flash a stock rom (from what I've read, it was supposed to do that by itself, from the sd card, as long as the file name was good), and it wouldn't do that either (although that might be a file name that doesn't match the cid, not sure - I didn't have the presence of mind to write this stuff down, and now I can't get to it).
Any ideas what I could do short of retiring it as an expensive paperweight?
Thanks!
black_mojave said:
Hello there!
I have an HTC One Mini 2 that I've managed to put in a boot loop by messing around with the build.prop file. I'd put CyanogenMod 12 on it, ...... if I try to boot into recovery I get the HTC logo screen for a couple of seconds, then it dies again, neither adb nor fastboot lists it in devices, and windows doesn't see it either.
I even tried getting it to flash a stock rom (from what I've read, it was supposed to do that by itself, from the sd card, as long as the file name was good), and it wouldn't do that either (although that might be a file name that doesn't match the cid, not sure - I didn't have the presence of mind to write this stuff down, and now I can't get to it).
Any ideas what I could do short of retiring it as an expensive paperweight?
Thanks!
Click to expand...
Click to collapse
can you access hboot? if so try reflash twrp. then go from there.
Related
Back when 2.2 first rolled out OTA I've had issues with my phone, it's been dead
It's not rooted or unlocked, was waiting for 2.2 to do all that
when the OTA came up, I had the phone install it
never booted up fully, would stick at the flashing Nexus logo till it locked up completely
now it can't get past the static Nexus logo at all
when attached to my PC it will not show up in ADB devices
I can get into recovery and the bootloader and it can access files on the SD card
what can I do to get something loaded on it so I can root it and move on with a custom ROM?
At one point I did have a file that loaded called PASSIMG that reset the phone to original shipping, but for the life of my I can't find it again, if I can get a hold of that file be it 2.1 or 2.2 based I can do what I need, or are there any other options?
http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Extract the .zip from it, rename to passimg.zip, put it on the root of your SD card, boot into HBOOT and you should be back in business, it will OTA itself up to 2.2.2 in no time.
Read my signature, find there "Unroot/restore" guide.
Something's not right, I have the file in the SD card, boots into HBOOT
Reads the SD card,this step is fairly fast, then does nothing else
This has me intrigued now.
Tried two different files, it is extracted and named PASSIMG.zip
Not sure what else to do
Double check the file isn't named passimg.zip.zip common thing.
Or if you can't be arsed fiddling, unlock bootloader, extract the system.img and boot.img files from the passimg, and use fastboot to flash them.
Ps. You have tried to wipe it since it broke, right?
You don't need to extract anything. Just try to actually read the guide carefully and execute step-by-step, before posting additional questions.
Thanks Jack_R1 finally got it sorta working, it flashed the file over fine but is now stuck on the static Nexus logo for close to 20 minutes and seems to be doing nothing, gonna try again with an older ROM instead of FRG33, which one did it ship with originally?
Stuck on static Nexus logo - might be a faulty SD card, for example.
FRG33 should definitely work, the older that worked would be FRF91, but you won't be able to flash it using PASSIMG once you have flashed the FRG33 - it won't allow to downgrade.
If you can get to recovery (power off, press and hold trackball, power on) - perform a factory reset, remove the SD card, and try to boot again. If it doesn't work - you might consider making things easier on yourself and using fastboot oem unlock.
Jack_R1 said:
Stuck on static Nexus logo - might be a faulty SD card, for example.
FRG33 should definitely work, the older that worked would be FRF91, but you won't be able to flash it using PASSIMG once you have flashed the FRG33 - it won't allow to downgrade.
If you can get to recovery (power off, press and hold trackball, power on) - perform a factory reset, remove the SD card, and try to boot again. If it doesn't work - you might consider making things easier on yourself and using fastboot oem unlock.
Click to expand...
Click to collapse
Not the SD card, works fine on my other phone
Can't unlock, phone not showing when doing a ADB Devices
Thinking it might be bad memory on the phone
To use adb, you have to be able to boot the phone to some level, and you may not be getting there...
Boot into bootloader, switch to the fastboot screen, then try fastboot devices.
You need fastboot to oem unlock, anyway, not adb (if you're planning on taking that route).
Sent from my Nexus One using XDA App
You use fastboot to unlock, not ADB
Yep, got it going now, not sure why I assumed that if it wasn't coming up under ADB, that fastboot would not work.
grats!
It 's alive! :d
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
picante544 said:
Symptoms:
Phone boots to the 3 Android boot screen with Fastboot bootloader. It will not load regularly.
I cannot make a menu choice until I push the trackball. This is not how the menu screen worked before.
I was doing a hard reset because the digitizer was acting up. I have not used this phone much until recently. I purchased it on ebay last year (for the accessories) but have only used it the last three weeks.
Hard resets were becoming less effective resetting the digitizer, which would act up more quickly with each reset.
I may have changed the default bootloader. I was using "clear storage" under hboot, but the phone now starts in fastboot. I have now pushed all number of combinations of menu options.
The phone has never been rooted (as far as I know.)
I cannot mount the phone to the computer via usb. "USB device not recognized...." but "fastboot" does become "fastboot usb" The command adb.exe devices lists no devices.
I have installed sdk but no usb drivers were installed in any of the packages.
So my question is: what do I need to do to have the phone start normally?
Bonus question: I was going to replace the digitizer, but is the digitizer a problem or a symptom of a bigger problem (and thus a waste of time replacing)?
Great welcome to the forum video. My apologies if this question has been asked a dozen times before, but I didn't find an answer. And of course,
"Thanks."
Click to expand...
Click to collapse
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
sphinxcs898 said:
Well, now, thats quite a predicament The N1 digitizer has always been quirky and I've encountered many an occasion where I had to turn off the screen and turn it back on to continue typing.
I have a few questions on this :
a) Are you sure your phone wasnt rooted and a custom ROM wasn't flashed on?
b) Are you able to access recovery from the bootloader screen?
Since you are able to access fastboot, you can:
1) unlock your bootloader
2) Flash su (gain root if you dont have it)
3) Place a custom ROM (CM7 preferably) onto your SD card and flash it.
Hopefully, this should get your phone back on track.
Click to expand...
Click to collapse
picante544 said:
A--I am not sure that the phone wasn't rooted, I bought it on ebay, but I own another N1 that I've used and the OS and functionality seemed identical. I believe that the seller said it was not rooted. I'm not sure how to root a phone, but perhaps I did something after getting into the menu.
B-- I am able to access recovery, I think. When I press the recovery option I get a vibration, the four colored star, a blank screen for a few seconds and finally a robot and a warning symbol. I'm not able to do any further.
1--I'll have to read up on unlocking the bootloader--I'm not sure, but don't believe I can unlock it at this point. I do have the option for either fastboot or hboot, but choosing either one and restarting leads to the same result.
2--I don't believe I can flash SU, again I'll need to read up on the procedure, but...
3--Windows responds when attach the phone via usb, but says it recognize the the device. I cannot access the SD card from explorer. I thought that maybe I need additional drivers, but don't find any that may be of use. Because Windows can't read the SD card, I don't think I can flash with a custom ROM.
However, there may be procedures I'm not aware of.
Thanks.
Click to expand...
Click to collapse
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
http://theunlockr.com/2012/10/16/how-to-root-the-htc-nexus-one/
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Resolved--hardware problem--trackball
Coincidentally, another user had a very similar experience with his N1 at the same time. He determined it was his trackball. I tore my phone apart, disconnected the trackball and the phone now works again.
Thanks again to those two people who responded.
sphinxcs898 said:
You don't need to have your phone connected to the USB of your computer to transfer data. Remove your SD card, place it in an SD Card adapter/reader and connect it to your laptop/PC. Copy your su.zip and custom rom zip file and place it in there.
Now, use standard instructions to do root your phone:
a) Download the latest Clockwork Mod recovery to your PC
b) Now boot your phone in HBOOT mode ( the only option possible )
c) Since fast boot is working, unlock your bootloader using the instructions given in the link above
d) After this, reboot into HBOOT again, and this time, flash on the recovery.
e) Now reboot into recovery, and first flash su.zip ( to gain root access )
f) once that is done, flash your ROM. (wipe everything except SD card)
Hopefully, this should get the good ole N1 back.
Click to expand...
Click to collapse
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.
Ok so long story short: I installed Cyanogenmod onto my HTC One using their installer, used it for a month or so and decided to flash it back to stock, but not before flashing a Google Play Edition rom (Android Revolution's). The rom got me stuck in a bootloop which i've read should be pretty easy to get out of, however my computer won't recognize my phone. I've also done something while trying to clear caches and what not that says the phone isn't rooted. I've tried to re-root it but since i can't drop the file into my sd file (can't see my phone on my computer) i can't do that either. Whenever i do try to reboot out of bootloader i get stuck at the HTC loading screen. I can get the red FASTBOOT USB and my comp dings when i plug in, but i can't see my phone. I've tried re-downloading drivers. Device manager sees my phone, but i can't access my sd card. I also can't get abd push to work either.
I'm pretty damn new to all this...probably started playing around prematurely. I've read quite a few tutorials so i'm not completely dense as to how all this works, but pretty close to it. If i could just get my computer to see my device, get the root and a new rom file on my sd, i'm pretty sure i could figure the rest out. Also, my apologies if this has been answered before; I did some digging an didn't see anything that helped my issue. Any help would be appreciated.
Also...i should probably mention that i was playing around with the format /system etc commands in CMW recovery...and it's likely i may have rebooted at some point afterwards....so i'm pretty sure that is what is causing the HTC screen issue, but I still feel my main issue here is the inability to get any zip files or anything for that matter onto my sd.
Once again...any help here would be greatly appreciated. Thanks
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Red_81 said:
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Click to expand...
Click to collapse
Ill try flashing the stock one, see if it works, thank you