I am having an issue trying to FXZ flash my friends Droid Bionic using RSD Lite. The flashing process keeps stalling at the point where the phone is supposed to reboot into recovery mode and flash the 2 radios. When it reboots I get the screen that show a droid laying on it's back with a red triangle with an exclaimation point in it above the open chest of the droid. After a few minutes the phone resets and then tries to boot normally and gets stuck at the last boot screen that has the transforming red droid logo. The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available. I have tried wiping data and cache before and after attemping to FXZ flash. I am at a loss at this point it seems to me there is something wrong with the stock recovery mode since the droid on his back is showing up instead of the droid standing next to the yellow triangle with the exclaimation point. Any help with this issue would be greatly appreciated.
To clarifiy I am using RSD lite 5.7 and the 6.7.246 FXZ flash file (downloaded copies from multiple sites). I have attempted to flash on 2 different computers that have successfully flashed other motorola model phone in the past using RSD lite. The Bionic has never been rooted and just randomly got stuck in a boot loop the other day.
I had the same problem. I had the update .zip file on my sdcard and I went into recovery mode after one of the failed reboots and took a chance on installing it that way. It worked for me.
examan said:
I am having an issue trying to FXZ flash my friends Droid Bionic using RSD Lite. The flashing process keeps stalling at the point where the phone is supposed to reboot into recovery mode and flash the 2 radios. When it reboots I get the screen that show a droid laying on it's back with a red triangle with an exclaimation point in it above the open chest of the droid. After a few minutes the phone resets and then tries to boot normally and gets stuck at the last boot screen that has the transforming red droid logo. The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available. I have tried wiping data and cache before and after attemping to FXZ flash. I am at a loss at this point it seems to me there is something wrong with the stock recovery mode since the droid on his back is showing up instead of the droid standing next to the yellow triangle with the exclaimation point. Any help with this issue would be greatly appreciated.
To clarifiy I am using RSD lite 5.7 and the 6.7.246 FXZ flash file (downloaded copies from multiple sites). I have attempted to flash on 2 different computers that have successfully flashed other motorola model phone in the past using RSD lite. The Bionic has never been rooted and just randomly got stuck in a boot loop the other day.
Click to expand...
Click to collapse
SamuriHL's House of BIONIC should be able t fix your broken recovery for you.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Just to clarify my post, I used HOB when I had the same issue. If you try it, I would also suggest having the .246 zip file on the sd card and try installing it from recovery if you get stuck again. I'm certainly open to hearing other ideas from any of the experts out there.
But the OP cannot get into recovery.....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
If you use the HoB I recommend trying fast boot mode instead of rsd mode.
Sent from my Xoom using Tapatalk HD
Thanks I'll give those ideas a try and let you know if i have any luck.
Sent from my DROID RAZR using Tapatalk
I keep getting thus logo when it attempts to install the radios.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This happened when i was using rsd before trying to use HoB and HoB yielded the same result. Any more ideas?
Sent from my DROID RAZR using Tapatalk
There's a radio fix in the HoB you may try. Check the utility menu. Once you do that, then try the 246 FXZ again.
I tried the radio fix in the utilities but got the same result, the little dead Droid screen then the phone reboots after about 5 minutes of inactivity.
Sent from my DROID RAZR using Tapatalk
Then I would say you have physical problems with the phone.
That's what I was beginning to think...thanks for the help.
Sent from my DROID RAZR using Tapatalk
johnlgalt said:
But the OP cannot get into recovery.....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Click to expand...
Click to collapse
examan said:
The screen showing the droid laying on its back also shows up when I try to boot into recovery mode manually, I am able to get past this screen by pressing both volume buttons and the recovery mode is then available.
Click to expand...
Click to collapse
I took this to mean he can get into recovery and this was exactly my situation as well. This was the point I got it to install from the sd card. Maybe I just got lucky this time. Hopefully not a sign I'm going to be screwed next attempt.
Samuri, thanks for the tip on using fast boot mode instead, I'm probably going to need that advice.
examan said:
I tried the radio fix in the utilities but got the same result, the little dead Droid screen then the phone reboots after about 5 minutes of inactivity.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Hmmm. I wonder if it tried to flash the radio during the ICS update and got FUBARd in the process? Either that, or the radio hardware is kaput.
I know your friend said it was not rooted but was it already upgraded to ICS? Did he, per chance, try to take the RAZR JB leak?
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
He said it installed the Ota update just fine then a few weeks later it just stopped working. I think it's most likely a hardware issue.
Sent from my DROID RAZR using Tapatalk
sounds like it, if it was already working on ICS before.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
Related
So I did an OTA to ICS, and it was working fine. So I rooted, safestrap'd, and loaded Eclipse 1.3 Hybrid. Was working ok. Messed with the DPI a bit, and got itself stuck in a bootloop.
So I tried a nandroid restore - boot loop.
Tried reloading Eclipse 1.3.2, wiped data et. all - bootloop.
Tried restoring my stock build - bootloop.
Went back to safe mode off - black screen, no boot anim, PC gets motocrap popping up.
Fastbooted back to 217 - black screen, PC gets motocrap popping up.
Suggestions?
Are you still getting the safestrap splash screen?
My advice would be to do a factory reset in stock recovery. If that doesn't fix it, fastboot everything manually. If by chance you did it manually the first time, this time use RSDlite.
It sounds to me like you either missed something the first time (it happens to the best of us), or you got really unlucky and developed a hardware problem randomly. Since it sounds like safestrap was coming up before, I doubt it's hardware.
Sent from my Amazon Kindle Fire using xda app-developers app
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
mxgoldman said:
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
Click to expand...
Click to collapse
How did you get an unlocked bootloader?
Also, what happens when you try to boot into fastboot mode?
Sent from my XT894 running ICS
Internal Engineering sample. It'll go to fastboot mode, but it does give a warning about the bootloader being unlocked. I've done the fastboot with the 217 files, then booted to recovery and wiped data/cache. No luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Sent from my Amazon Kindle Fire using xda app-developers app
you need to flash fastboot files immediately until battery will be discharged. or you have to make motorola factory cable
Yes, the rate of discharge the D4 suffers from when OFF is ridiculous. I once had the phone discharge 40% in 24 hours...with the phone turned OFF
You really should have a factory cable or adapter and you will be able to fix it very quickly with RSD Lite and the full XML.zip of fastboot images.
The factory cable will bypass the battery and charging circuit and power the device directly, allowing you to flash and recover it no matter what state the battery is in.
That's a very unusual device and it would be a shame not to be able to fix it.
There is no reason, with a factory cable, a complete recovery would not be possible if you can get to the boot menu as you have shown in your pic.
podspi said:
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Click to expand...
Click to collapse
Holy snackycakes, that worked! AWESOME.
... I want that bootloader! :good:
Glad to hear you are back in business!
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
SamuriHL's House Of Bionic
READ all the OP until you understand it. Any question you can have is probably addressed in the threads. HOB scripts automate most of the things you can screw up.
Good Luck
What happens when you try to use the stock recovery?
rahm0809 said:
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
Click to expand...
Click to collapse
The FXZ file, for some reason, won't wipe the /data partition. Your best bet is to boot into Stock Recovery, wipe data, power down. Then boot up into flash mode for RSD Lite. Reflash and then everything should be okay.
The device was probably on Gingerbread and the ICS flash caused the OS to freak out when it saw a /data folder full of Gingerbread things without any sort of preparation laid down.
I could have sworn the FXZ always wipes data...Well, the unmodified FXZ. And it erases internal storage, too....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
So I ordered a kindle fire hd 7" Saturday. Got it yesterday and the plan was to root it, flash recovery and install a custom rom to get jelly bean. But I ran into some issues. First was getting adb working, eventually I got it sorted out and started to flash twrp recovery. I used this method after I tried another and it failed. I went to go reboot my kindle and it's now stuck in a persistent boot loop at the kindle fire boot logo.
I have read about using adb to fast boot, reflashing the system and using system recovery utilities. Since I don't know a lot about adb I went for the latter of the choices, something that might could make it easy. But my computer never sees that the device is plugged in and neither doing adb. Even when manually typing the command to fast boot it doesn't work. Just says waiting for device. I check device manager and there is nothing in there related to my kindle.
I have tried searching around for a solution but I cannot find another thread of website telling me what to do if my computer does not see the tablet.
So now I'm stuck. I know my kindle can be fixed if my computer could see it, but it can't and I don't really know what to do now. Any help from you guys is greatly appreciated.
That command only works primarily on a 8.9 inch when its bricked, and secondarily on a kindle that can fully boot up. You need a fastboot cable to fix it. They are fairly cheap. Once you plug one of those in it will go straight into fastboot mode and u can reflash the system image. Unless I misunderstood and you have a blue kindle fire logo, in which case u can just hold down volume down and get into twrp and flash stuff from there.
Sent from my Amazon Kindle Fire HD using xda app-developers app
I do not have the blue logo. I researched a little more and figured I needed that cable. I ordered one from eBay this morning. Will be here by the weekend hopefully. Once I get the cable the restore utility should work correct? If not what steps should I take? Also what did I do wrong? I followed the steps but it was unsuccessful, obviously. If I can get my kindle restored I would still like to try and flash the recovery so I can install another rom. I've never used utilities on the computer for this so I'm sorta a newbie. On other android devices it was always an easy root with an app and recovery was installed at the same time. If you could point me to a good tutorial to install recovery for my kindle on firmware 7.4.6 (pretty sure it was) i would greatly appreciate it.
scaryjam8234 said:
I do not have the blue logo. I researched a little more and figured I needed that cable. I ordered one from eBay this morning. Will be here by the weekend hopefully. Once I get the cable the restore utility should work correct? If not what steps should I take? Also what did I do wrong? I followed the steps but it was unsuccessful, obviously. If I can get my kindle restored I would still like to try and flash the recovery so I can install another rom. I've never used utilities on the computer for this so I'm sorta a newbie. On other android devices it was always an easy root with an app and recovery was installed at the same time. If you could point me to a good tutorial to install recovery for my kindle on firmware 7.4.6 (pretty sure it was) i would greatly appreciate it.
Click to expand...
Click to collapse
I keep hearing of using firstflash apk to do the job, and for restore I hear system restore is best, I would try either one if not try KFFirstAide for the restore and I heard they fixed the root and boot loader install problem. Either one would work and they got friendly and quick help in their own threads.
sent from this thing in my hands on cm10.1
---------- Post added at 12:33 PM ---------- Previous post was at 12:31 PM ----------
stunts513 said:
That command only works primarily on a 8.9 inch when its bricked, and secondarily on a kindle that can fully boot up. You need a fastboot cable to fix it. They are fairly cheap. Once you plug one of those in it will go straight into fastboot mode and u can reflash the system image. Unless I misunderstood and you have a blue kindle fire logo, in which case u can just hold down volume down and get into twrp and flash stuff from there.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
@stunts513 man you must reallly like helping bro, hopefully you get lots of thanks because I see you in every or every other "please help thread", and you always seem to beat me.
sent from this thing in my hands on cm10.1
Ah thanks I just have a lot of free time on my hands and like to fix things, or in this case help other people fix things. xD
I'll try to not hog all the posts though, seems kinda bad if I don't let other people get a word in edgewise.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Alright thanks guys. I'll try your suggestions when my cable arrives and see what I can do. If I have any issue I'll post back here and hopefully you guys can help. But I hope everything goes smoothly from here on out. Thanks again guys I really appreciate it
Installed drivers finally, in process of restoring now.
So I used kfhd system img restore tool. It said it went through the steps successfully but I'm still stuck on a boot loop. Any ideas?
In the mean time I'm going to try KFFirstaide and see what happens with that.
Its probably the boot IMG, try using KFFirstAide to restore kindle to stock 7.2.3 os and everything should be back to normal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=1922304
I process of doing that now. Says downloading 3 imgs. I will post an update after its finished letting you know how it went. *fingers crossed*
OK just so u don't worry the last image takes a while to download and to send to kindle so be patient and wait it out, total time will take around 10-20mins.
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Made you click!
Well it downloaded the 3imgs and and went black for a few minutes. Then said sending boot (8192 KB)...failed (command write failed <no such device or address >
I just tried to erase cache and user data and it said it failed. Kindle is still boot looping. I'm going to try the process again I guess and see what happens.
Seems to be more succesful this time. Before the cmd screen went black then the error came up. Now it said sending boot etc. and was okay now sending system.
Maybe this time will work lol
Well it said everything was successful. Before it would boot up and show kindle fire for about 3 seconds then turn off, show the boot logo and repeat constantly.
Now it shows the kindle fire boot logo but it stays on for roughly 30 seconds, then reboots and repeats the process.
I tried the whole process again and once again everything said okay. I went to wipe userdata and it said it failed (too many links) Kindle is still staying stuck at boot logo.
edit: Thank you guys so much! After like 6 reboots it finally launched to the screen where I can select my language, now I'm going to try to flash a custom rom, twrp etc. again and maybe more successful. Thank you guys again so much!
Your welcome knowing I helped and spread the word about KFFirstAide is thanks enough.
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Made you click!
After update to sense 6.0,
Just a quick overview:
I am rooted stock fw stock kernel and latest twrp recovery,unit rebooted prior to rooting also,however prior to update I was fine.
Handset was originally a Vodafone handset unlocked now on 3uk.
I've also included some screen shots of as version etc...
1. Phone auto reboots every 2 mins continuously (while on battery or on charger).
2. Battery drains in 4 to 5 hrs and phone becomes very hot.
3. SYNC is continuously ON most of the day.
4. Apps*requiring update from play store, keeps getting re-installed several times when the SYNC is ON.
I have performed a full factory reset 3 times,no avail.
If I leave at default*apps, my phone is OK. But once I reinstall all my*apps*from play store and setup (individual app manually, with out restoring from backup) the problems reappear.
Thanks for your time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk
Sounds like a 'stuck' sdcard, you may want to try restore tricks but may not help
Stuck sd card?
Sent from my HTC One using Tapatalk
Unfortunately, I have roughly the same problem. I have a rooted HTC One M7 (International), stock everything, unlocked, TWRP recovery.
After updating to Sense 6, the first time I rebooted my phone, it got stuck in a reboot loop (it did a full boot to Android without a hitch, I could even unlock my phone and access my home screen, but a few seconds later it would reboot). Manually restarting the phone didn't help. I finally managed to solve it by shutting the phone down, and then starting it again (instead of restarting). Today however I had to reboot the phone again, and now it's stuck once again in that reboot loop. Switching off the phone isn't working this time.
Any ideas anyone?
vlix said:
Unfortunately, I have roughly the same problem. I have a rooted HTC One M7 (International), stock everything, unlocked, TWRP recovery.
After updating to Sense 6, the first time I rebooted my phone, it got stuck in a reboot loop (it did a full boot to Android without a hitch, I could even unlock my phone and access my home screen, but a few seconds later it would reboot). Manually restarting the phone didn't help. I finally managed to solve it by shutting the phone down, and then starting it again (instead of restarting). Today however I had to reboot the phone again, and now it's stuck once again in that reboot loop. Switching off the phone isn't working this time.
Any ideas anyone?
Click to expand...
Click to collapse
well i had the same issue.
but after rebooting. the boot loop stopped. now the homescreen is just black. saying unauthorized device. i can still swipe down the notification bar and go to settings. but thats about it. i can for some reason still pick up the phone. but i can't navigate through my home screen because its black like i said above. nor can i go to my applications.:crying:
I at first managed to fix my problem by rolling back to the standard Android 4.4 without Sense 6. My phone worked fine for a few days, but now, after a manual reboot, it has started rebooting again! Exactly the same problem. Whatever is wrong with it, it's also related to a battery drain. The reason I had to reboot was because Google Services was sucking a lot of battery. But I guess it doesn't really have anything to do with the Sense 6 update.
What the hell is going on here....
vlix said:
I at first managed to fix my problem by rolling back to the standard Android 4.4 without Sense 6. My phone worked fine for a few days, but now, after a manual reboot, it has started rebooting again! Exactly the same problem. Whatever is wrong with it, it's also related to a battery drain. The reason I had to reboot was because Google Services was sucking a lot of battery. But I guess it doesn't really have anything to do with the Sense 6 update.
What the hell is going on here....
Click to expand...
Click to collapse
ehh possible to put back a custom recovery (TWRP) and flash a custom rom and then try again?
Davies_90 said:
After update to sense 6.0,
Just a quick overview:
I am rooted stock fw stock kernel and latest twrp recovery,unit rebooted prior to rooting also,however prior to update I was fine.
Handset was originally a Vodafone handset unlocked now on 3uk.
I've also included some screen shots of as version etc...
1. Phone auto reboots every 2 mins continuously (while on battery or on charger).
2. Battery drains in 4 to 5 hrs and phone becomes very hot.
3. SYNC is continuously ON most of the day.
4. Apps*requiring update from play store, keeps getting re-installed several times when the SYNC is ON.
I have performed a full factory reset 3 times,no avail.
If I leave at default*apps, my phone is OK. But once I reinstall all my*apps*from play store and setup (individual app manually, with out restoring from backup) the problems reappear.
Thanks for your time.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Same problem with my bro's HTC One Max but was fixed. I told him to go to recovery(TWRP), go to wipe, click "advanced wipe", check everything except usb-otg. Then click "format data" and type "yes" and install everything again.
Hope this helps
Hi, did you manage to solve that ? I'm having the same problem here and can't use my device
raphael.lira said:
Hi, did you manage to solve that ? I'm having the same problem here and can't use my device
Click to expand...
Click to collapse
did you read the post just above your's ?
did you format data in twrp and type yes and reinstall your Rom ?
Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.
DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?
kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.
DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?