Hi there,
I need some help here. My wife's Sprint Nexus S is acting up - keep popping messages such as "Unfortunately XXX has stopped." So I decided to do a hard reset. I followed the instructions but weirdly the phone did not do it. It acted like doing the hard resetting but then rebooted with nothing changed. I tried both the software way - Settings, factory reset, and the hardware way - Vol up button + Power, then recovery, then Vol up + Power again at the Android with exclamation image, chose "Wipe all data and factory reset." However, the phone boots with nothing changed.
Can anyone help me with this? What else can I try?
Thanks much in advance.
<DELETED>
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
kwudude said:
Have you tried installing a custom recovery and doing a hard reset through that route yet? E.G. ClockworkMod or TWRP
Click to expand...
Click to collapse
Thanks. I will give it a try. Can you point me to some instructions / files for downloading, etc.?
Cpu.gastronomy said:
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
Click to expand...
Click to collapse
This one is actually the Sprint stock rom untouched. So... no Rom Manager on it. Thanks anyway. I guess a custom recovery is the only way to go now...
<DELETED>
I wouldn't install a custom recovery, and ultimately technically void your warranty, for the sole purpose of resetting it though...
Just use a one click root tool, it flashes superuser, cmw, but keeps the rest of the (stock) rom you're on!
---===:::Greetzz, jojoost:::===---
Sent from my iPad using Tapatalk HD
Thanks to you all for all the good suggestions. I have tried several things but did not succeed.
1. Flashed a clockworkmod recovery. That was successful. So I went ahead to use its factory reset function. The process completed without error but once rebooted, the phone remains the same as before.
2. Connected the phone to a PC, turned on USB storage, copied a ROM image zip file to a folder. Then tried to install it through Recovery. But the file I copied was nowhere to be found.
3. Put then phone into the bootloader mode, connected to PC, use fastboot to flash boot, system, recovery, userdata, radio image files. All went through with any issue. Rebooted, phone is the same.
In short, whatever I do, the phone remains the same. No changes can be made.
I also tried the one-click tool but could not proceed ahead. It required USB debugging turned on. I turned it on, the check mark was there, but it was really NOT turned on because on the PC, the message is that it is not on. On the phone, if I switch to a different application, or simply go back one step, and then go to developer option, the checkmark was not turned on.
It feels like the internal memory/storage becomes read-only. No changes can be made. I am not sure if the hardware is bad, or some permission issue.
Any ideas that I should try next?
From what I read and understand, I think I had a bad nand problem. Guess time to let the phone go RIP.
Related
After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help
up.......
You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again
the factory reset didn't work !
still stuck on Google logo
any advice?
farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Try doing a hard reset.
GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States
just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).
GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?
Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"
Try to reset with Odin.
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
jeremyb234 said:
Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
Click to expand...
Click to collapse
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
TechMinerUK said:
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
Click to expand...
Click to collapse
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
jeremyb234 said:
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
Click to expand...
Click to collapse
Depends, if it's a custom recovery it could wipe everything
TechMinerUK said:
Depends, if it's a custom recovery it could wipe everything
Click to expand...
Click to collapse
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
jeremyb234 said:
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
Click to expand...
Click to collapse
Unfortunatley because it's not a common brand of tablet not many developers are working on creating ROMs for it
Kit Kat 4.4.2
Would provide add'l info but can't even boot it up right now.........
Long and short....... phone was not rooted or modified on any way (for once). Only issue I noticed before it died was that the display would "freak out" with some colored lines once in a while....only for a few seconds. Last night, when I went to go into an email app....... everything crashed. All apps put up not responding messages, the UI crashed and the phone shut off before I had a chance to shut down correctly.
Now all I get is the red Motorola logo. I can get to the diagnostic menu (vol down, power, then vol up when the logo disappears). Recovery results in the dead android icon. All other options EXCEPT AP Fastboot Flash result in going back to the red Motorola logo. The phone is recognized in device manager when I plug into laptop, and the phone says connected to USB, and "device is locked". It does not show up as a drive, however (I did not have USB debug set to on if that's the reason).
I'd obviously like to save the phone, but more important are the pictures, which like an idiot I didn't back up. So, what I've tried:
1. Downloaded Moto drivers and made sure phone shows up as Mot Single ADB Interface (Fastboot Vanquish S driver)
2. Downloaded RSD Lite 6.1.6 and installed. Seems to recognize phone, as it lists USB port. Phone info, however, all says N/A
3. Downloaded KitKat stock ROM, which included the XML file, the recovery image and one or two more images. forgive me, but i left the file at work so i can't be specific.
4. When trying to flash that file with RSD, I get a "getvar" error and the flash fails.
Any ideas? Please keep it as simple as possible...... I'm no pro at this. I'll get the exact ROM filename tomorrow, since that might be the issue................
Question...... my pics are obviously on the internal storage, not the external SD card (dumb again)....... is there a chance that this process will not delete those files? I think the internal is considered SD0 on this phone (and maybe on all android platforms), and I read that the internal SD might not be overwritten.
UPDATE: I just read a post that said to delete all the lines with "getvar" from the XML file. I will try that, but in the meantime, if I'm doing anything completely idiotic, I'd like to know.
SECOND UPDATE: Found another site to download the ROM from.......... this time is gets by the "getvar" but fails at the first "flash" command....... see attachment
Thanks
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
re:XT926 (mostly) dead
RikRong said:
Were you on the .15 update? It looks you're getting that fail because you're trying to downgrade to .10. .15 is linked in the general section.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I'm not sure if I was on .15.............. but the file i was trying to flash is 10.1.........so i'll try to find the file you suggest. thanks.
The "dead android" logo is normal, you have to press a combination of keys to "unlock" recovery:
When you see it, hold both volume keys, then quickly press power button, and you should have options.
From stock recovery you can try either clearing cache, or clearing cache and data (if you dont mind losing your files) to try and see if it comes back.
Seen a similar issue (stuck on boot logo) on a xt925 and a moto G before, and simply clearing cache solved it.
Hope you can recover your beloved device, and make sure to report your results here
EDIT: So, I reread your post and seems like you cant go into recovery anymore, so reflashing seems to be the best option. Usually seeing the red logo is a good sign. Dunno about the specifics on flashing a xt926, but yeah, you have to edit the xml file.
Re: almost dead
Thanks........yes i think the recovery option is shot. And for the life of me I can't find version .15 as suggested in another post above. I just searched the general forum for over an hour and only see .10
UPDATE: Damn.......... that sequence worked. saw the dead android and hit your key combo. now have options to:
reboot system
apply update from SD
apply update from ADB
wipe data/factory reset
wipe cache partition
remember, i'd really like to save my media. any idea what the best selection would be?
UPDATE 2
Tried "Wipe Cache Partition". Seemed to complete the function (android icon came alive with electric).........but did not help phone to reboot
thanks so much, even if it doesn't save my data. Progress at least.
Phone was working ok yesterday all day, then I has to take a flight to another city and timezone. When I arrived everything still was ok for about 1 hour, then I wanted to login in the hotel wifi and it wasnt showing the networks. Tried turning on mobile data ando it wasnt turning on either. Rebooted the phone, didn't work. Then I tried to go to the settings and I got an error message "Settings isnt working" and shuts the window. Another message that suddenly appears is HTC Mobile data Lite isnt working.
Tried with info settings > settings > clear data and cache. Didnt work.
Rebooted by holding power and volumen buttons, didnt work.
Went to boot options it says is locked and that ”File" wasnt found.
They boot to recovery gets stuck on the red warning with a triangle image.
Lastly the phone got stuck on reboots, after I do they security pattern it shows they splash screens and logos, reboots and asks for the pattern again.
Never flashed or did something with system files or kernels on this phone.
Wanted to try factroy reset but when I was able to go to the home screen and connect the phone to a Mac using the app AndroidFile Manager..? It said 8gb available to select, which seemed wrong as my phone was almost 60gb full, so wasnt sure it was going to be a good backup.
Any help on what can I do to backup ando solve the issue?
Thanks!
Clear system cache if that's an option.
Factory reset.
If that doesn't get it it will need a reflash. The flight may have caused a Single Event Upset, which is more likely to happen at high altitudes.
The hotel wifi is also suspect, root kit.
Lastly it could be a mobo failure or other hardware issues.
Is possible to clear cache if I can't access home screen? Any chance of backup before factores reset?
I don't think was wifi, didnt have a chance to connect to it or something
I think your stock rom has encrypted your phone's memory . If you want to S-OFF you can try a TWRP recovery otherwise you can install a RUU rom at home. All your data will be destroyed.
Figured out how to wipe partition cache...didn't help. Still stuck on boot loops.
All your data will be destroyed.
Click to expand...
Click to collapse
So there is no method to pull my data out of the device before trying to flash something into it?
Try starting it in safe mode. May take a few tries.
If you get it into safe mode, grab the data.
That's probably your last hope.
This is one big reason I always use a phone that supports an SD card. I use the SD card as the data drive; all critical data goes here. I then redundantly and regularly backup the SD card.
The data drive provides a buffer if the OS crashes/burns and most times is unaffected.
Everything I need to do a full reload/restore is on my data drive. It's time staggered backed up on multiple flashsticks and hdds.
I've lost whole databases before; lessons from the U of hard knocks tend to stick... and suck.
blackhawk said:
Try starting it in safe mode. May take a few tries.
If you get it into safe mode, grab the data.
That's probably your last hope.
This is one big reason I always use a phone that supports an SD card. I use the SD card as the data drive; all critical data goes here. I then redundantly and regularly backup the SD card.
The data drive provides a buffer if the OS crashes/burns and most times is unaffected.
Everything I need to do a full reload/restore is on my data drive. It's time staggered backed up on multiple flashsticks and hdds.
I've lost whole databases before; lessons from the U of hard knocks tend to stick... and suck.
Click to expand...
Click to collapse
Already tried safe mode before your reply. Didn't work either.
Oh well, gonna go for the factory reset then.
Thanks for your help.
xmago said:
Already tried safe mode before your reply. Didn't work either.
Oh well, gonna go for the factory reset then.
Thanks for your help.
Click to expand...
Click to collapse
Try a few more times... play with it.
Been trying, keeps rebooting after entering the security pattern.
I can go to emergency call, it shows com.android.phone is not working but if I click wait after a while it shows the phone UI, I can take screenshots and move the volume bars... one time I don't know how or why, I left the phone while I read something else, on the pattern screen and I had the "Do you want to transfer files" message ... so this gives me hope that I will be able to either go to the system 1 time, or that the ADB is detected so I can pull data.
Tried fastboot boot twrp.img from power shell, but got the warning device won't boot. I guess because I didn't unlocked it and wipe the data first.
Found stock ROM that matches my CID/MID/Carrier, etc. Can I use this to flash something into my phone and fix the booting problem without wiping data?
xmago said:
Found stock ROM that matches my CID/MID/Carrier, etc. Can I use this to flash something into my phone and fix the booting problem without wiping data?
Click to expand...
Click to collapse
The problem is likely in the user data partition itself. Start flipping firmware around all bets are off. Be a lot safer if you could get it into safe mode to retrieve the data.
blackhawk said:
The problem is likely in the user data partition itself. Start flipping firmware around all bets are off. Be a lot safer if you could get it into safe mode to retrieve the data.
Click to expand...
Click to collapse
Gonna keep trying to enter system then, maybe I get lucky.
The zip I downloaded had other zips inside and I can't open or extract them, windows says they are not valid. So I downloaded a different ROM from a different site, and had the same issue. Is this normal? Don't want to be flashing corrupt zip files obviously
xmago said:
Gonna keep trying to enter system then, maybe I get lucky.
The zip I downloaded had other zips inside and I can't open or extract them, windows says they are not valid. So I downloaded a different ROM from a different site, and had the same issue. Is this normal? Don't want to be flashing corrupt zip files obviously
Click to expand...
Click to collapse
The only boot loop I had where I needed data eventually booted into safe mode by itself after a couple tries at normal booting, convenient.
The next time it happened, a few days latter I was ready, lesson learned, always backup data.
As for the files, you're in deeper then I ever had to go. A factory reset be easier and safer if the rom isn't the source of corruption. You got yourself between a rock and a hard place. Personally I would have written the data off by now and factory reset. Of course that's because almost all the data was backed up.
Use the exact same rom.
Someone here can spot what's wrong though with your methods... have patience.
Seems I'm screwd. Did a factory reset, now I'm stuck on the Internet configuration screen after selecting language. Networks don't appear and I got the same "HTC Mobile Data Lite" error screen saying isn't working.
The top bar has a lock and only NFC is turned on. Can't pass that screen.
xmago said:
Seems I'm screwd. Did a factory reset, now I'm stuck on the Internet configuration screen after selecting language. Networks don't appear and I got the same "HTC Mobile Data Lite" error screen saying isn't working.
The top bar has a lock and only NFC is turned on. Can't pass that screen.
Click to expand...
Click to collapse
Try pulling the sim card.
blackhawk said:
Try pulling the sim card.
Click to expand...
Click to collapse
Didn't have one, then I inserted it again, no change. This was the original problem when I got in to the hotel, couldn't turn on wifi or mobile data.
Not sure what else to try. Wanted to try with a custom ROM or something, but can't unlock bootloader, because I can't get the identifier token since I can't get to the debug settings to turn on OEM unlock.
Fastboot oem unlock command is giving me an error.
The status of my software (on the bootloader) says modified, not sure if is it because I tried to boot a twrp.img (but afaik I understood should have been wiped after a reboot)
Extracted the zips with the RUU tool and got some img files, maybe I should try to flash some of those files.
Before you try anything else get the right procedure from an expert here. Otherwise you may trash the one or two shots you might have have.
I'm not that expert but there are members here that are. Sorry to see you having so much trouble...
I had the same problem,
This is processor fault .
the solution that i found to solve this problem is turn off the phone and heat the back cover under the camera using heatgun or hairdyer for about 30sec, don't make it too hot, then power up the phone and long press hardly the back cover under camera using your tumbs while HTC logo comes up. This makes my phone succesed booting up and the signal show up again. Once the phone turn up, just backup everything.
If the signal not showing up and wifi not working , you can use bluetooth tethering or using "gnirehtet" for reverse usb tethtring from computer.
*important : when the phone turn on, go to setting to delete the lock pattern/pin to make your phone not locked.