Nexus 5x Full Restore not working (Nexus Root Toolkit) - Nexus 5X Q&A, Help & Troubleshooting

Hello,
I'm in a bit of a pickle. Bought my sister a brand new Nexus 5x about 3-4 months ago, first thing I did was install Pure Nexus (6.0.1) on it (prerooted) and unlocked bootloader, don't know why I did it but I thought it'd be nice for her to use foreign country appstores/other things. Anyways long story short, I installed Nexus tool root kit (latest version 2.1.9) to return the device to stock and relock the bootloader.
First thing I did was do a full backup (around 600mb, she didn't install much stuff).
Backed up other things - SMS/Phone/Contacts/Media (70mb.. weird), also copied and pasted all media to computer as I didn't trust the small file size here.
Next, I did a flash and unroot with stock firmware, selecting the latest firmware 7.0 (bullhead MTC20k) and this wiped the phone. After that finished, enabled debugging and etc and reconnected. At this point I used the toolkit to relock the device and it was wiped once again. Now, the phone was running the latest firmware and was locked and back to stock.
After rushing through the initial setup, (wifi, account etc.) I got back to home screen, went to developer options to re-enable USB Debugging and got the phone's fingerprint access thing approved. Then I went to open the toolkit to run the restoration. Following prompts and accepting to restore (no password set/required), I saw pretty much all the app names pop up and being restored. However after it completes, the computer's log says check device. Looking at the device I see no apps added or anything. I've run this step a few times but it appears no applications are being restored.
I would greatly appreciate some advice on what to do next, as I'm at a loss here. Thank you!

Hey guys,
Reporting back, I have downgraded the firmware to the latest Marshmellow version 6.0.1 MTC20K, and tried the whole process again. I'm glad to say that the restoration now worked and all the apps can be seen (including the ones requiring root, which now, no longer work).
It appears upgrading to a completely new version prevented the apps from showing.
Anyways, glad the ordeals over, once photos and contacts restored I can present the phone back to my dear sister.
Thanks!

Related

[Q] HTC Thunderbolt 605.10

Hello everyone, first off, I read these two posts in their entirety:
http://forum.xda-developers.com/showthread.php?t=1009969
and
http://forum.xda-developers.com/announcement.php?f=943
I apologize if this might not be the best forum to post in, but as I just signed up I didn't have enough posts to post in the first thread like other people.
So I kinda have a good understanding of what I need to do with my phone, but need someone to recommend the best thing for me to do to change my firmware to 6.05.6 or 6.05.9, so allow me to share my rooting experience:
First off, I am running Windows 7 64-bit and I have never rooted a phone before and my Thunderbolt was my first droid device that I got 5 days ago on April 2nd, but I have plenty experience with flashing firmware for other devices such as routers, DVD drives etc. Initially I was not going to bother rooting my phone because of how complicated it looked, but then I found the one-click method and was becoming increasingly annoyed by not being able to get rid of the bloatware such as the Blockbuster app, Bitbop, Lets Golf 2, Rockband, Peep, and a couple others, so I decided to give the one-click method a shot.
Initially I had an issue with the ADB driver as Windows failed to install it successfully, after many agonizing minutes and a couple forums later, I installed HTC Sync and that fixed the issue, so now my batch file was working thus far. My second problem was the hbooteng.nb0 file. I had extracted the files from the exploits.zip correctly to the platform-tools folder, but my mistake was that instead of using the RUU filed and renaming it for the first flash, I initially flashed it with the one that was already name PG05IMG, so basically I thought I had done it correctly until I ran into the hbooteng.nb0 issue and realized I had flashed with the wrong file, leaving my phone basically unchanged and unrooted, but working perfectly fine.
Sooo I started over, this time knowing for sure I was using the correct files, and the process went pretty smoothly and the oneclick method told me my phone was rooted and to install the SU and ROM Manager so I did. Also did the clockworkmod thing as well.
But here is where my current problem is: My firmware is the 605.10 version and I would like it to either be back at the stock 605.6 or the newer 605.9. My phone works modestly well with the 605.10 so far EXCEPT it isn't correctly detecting my location. I live in Indiana, but the clock keeps setting itself to Rio de Janeiro. Also if I try to use Google Earth and do "find my location" with the GPS enabled, it takes me to Rio de Janeiro!
So here is my question: Which method of getting to the 605.6 or 605.9 firmware is the safest for me to use? And will using the one-click batch file to flash to either of those firmwares be safe since in the beginning it says that method does not work unless it is already at 605.6 or 605.9? Or should I attempt to do the option of factory resetting my phone through the SDcard settings, and what will I lose, and will I be back at 605.6, OR am I somehow supposed to use the ROM Manager app to flash to 605.6 or 605.9?
Many thanks in advance!
Ok so I ended up using ROM Manager and flashed to the 1.12.605.06 and it worked successfully but now my phone is no longer rooted since the ShootMe app doesn't work.

[SOLVED] Completely stock GSM Galaxy Nexus -- 4.0.4 update stuck at Google screen

Update (5/2/2012):
I think I've isolated the issue as a broken recovery image. It appears that some of us received a broken 4.0.2 OTA and are now suffering for it.
This issue can be completely fixed by manually installing the 4.0.4 update. For reasons stated in my post below (message #9 in this thread), I do not think this issue can be fixed with an OTA update, so don't wait for Google to fix this. Fix it yourself or send it back for a refund.
----
Title says it all.
I have a completely stock GSM Nexus running 4.0.2, YAKJU build. Several times, I have received the notification that the 4.0.4 OTA update is available. Each time when I try to take the update, the phone reboots and gets stuck at the "Google" screen indefinitely.
At this point, the only way to shut the phone off is to remove the battery.
Has anyone else had this problem? I can't believe Google is unable to deliver a working update to a stock phone, especially after the months of delay this has been. (My phone is nearly unusable on 4.0.2 due to the keyboard lag, random reboots and other issues.)
I really don't want to mess with the bootloader due to warranty issues.
Same thing is happening here. Completely stock on 4.02, receive notification for 4.04, downloads, reboots to install, doesn't get past "Google". Not sure what's going on there...
Same here, tried twice now. Left it for about an hour and it went through a stage of the back of the phone getting warm (antenna location, I believe... at the top by the camera) then cooled down later. I thought maybe it was downloading the update? Not sure if it normally downloads before or after the reboot.
Additional info:
Mine's wasn't originally yakju, but I flashed to yakju 4.0.1 from yakjuux (or whatever) when I got it months ago, and was able to get the 4.0.2 update OTA just fine.
Mine was yakju out of the box, so I don't think it's a flashing issue.
Yep, mine too. YAKJU out of the box. I haven't done anything to mod this phone.
I'm going to try to manually update it in the next day or two and share results
No factory reset either
Huh. I thought maybe doing a factory reset from the Settings menu would help. In fact, I can't do that either!
After clicking through all of the confirmation dialogs, the phone reboots and.... get stuck at the Google screen. I have to pull the battery out, just as when applying the 4.0.4 update. Luckily the phone will start up again, but the wipe never happened.
It looks like there's a problem with some Galaxy Nexuses being able to go into recovery, perhaps?
Hi All
I got the exact same problem. Out-of-the-box, no mods, no root, 4.0.2. Got the OTA to 4.0.4 the third time this morning. Still can't pass the "Google" screen.
Solved -- sort of.
Hey all,
I spent some time investigating this issue. Here's what I've determined: for those of us affected with this problem, it appears that we somehow received a botched installation of 4.0.2 (the version we're running currently). What's the botch? Our phones don't have a working recovery image.
You can test this by trying to enter recovery. Turn off your phone. Then, simultaneously press and hold volume-UP, volume-DOWN, and POWER until a screen with an Android on his back appears. This is the fastboot screen. From here, you can choose 'Recovery'. If your phone is like mine, any attempt to go to Recovery will just put you in the dreaded Google logo loop.
So, what's the solution? I'm afraid the only way to resolve this yourself is to unlock the bootloader and do a complete install of the 4.0.4 image yourself. One step of that process is to flash an updated recovery image; this will cure the issue. Fortunately, on the Galaxy Nexus, you can easily re-lock the bootloader with a single command. I have done all of this and can confirm that it works.
If you're not comfortable unlocking the bootloader, the only other way to fix this is to send it back to the vendor. I have a strong suspicion that phones affected by this bug are unable to receive any further OTAs at all. This means Google can't fix your phone by pushing out a different OTA.
Final warning: until this is fixed, you can't do a factory reset, either -- that process will fail because it, too, uses the recovery. So don't plan on selling your phone on eBay until you get this fixed.
Your research is much appreciated modenastradale. It seems this is a fairly big **** up on Google's part. But I guess these things happen. I don't have any particular problems with unlocking the bootloader, I just didn't feel like wiping the phone right now and having to reinstall and set everything back up again which is why I've remained stock this whole time.
Unlike previous phones, this one has felt great out of the box, so I've never had the need to root it to get more performance out of it.
I guess this will be the project for the weekend. Yay!
Looks like a good opportunity for me to switch to the US version (takju).. even though it's 99.9% the same right now. Just in case they give us a better radio for the region.
Idea:
What if I flash the recovery only? (like step D.12 here: http://forum.xda-developers.com/showthread.php?t=1626895)
I already have an unlocked bootloader, so it looks like I wouldn't need to wipe the system to unlock it. I guess I would get the 4.0.2 full image and flash that recovery (not the 4.0.4), though I'm not sure it would made a difference anyway.
I might try it out, but still interested in maybe switching to Takju anyway. I thought about anything that I'd lose by wiping, and since almost everything is on google's cloud (gmail, google music, coctacts, pics on google+, etc) it's not a big deal to wipe.
Fixed
The method I suggested in the last post worked!
You need to be able to flash a recovery image though, which I think would mean you need an unlocked bootloader? The benefit of doing this over just flashing the complete 4.0.4 image is that you don't need to wipe the phone (assuming you already were unlocked)
In more detail, here are the steps I took.
- Preparation (I already had this done) - have Samsung drivers installed on your PC, ADB, fastboot, etc. - check other threads for how to, such as: LINK
- Follow this post's how-to for flashing the recovery image - the poster also has the stock 4.0.2 link, which I can't find on google's site anymore: LINK
- The only command I ended up using is
Code:
fastboot-windows.exe flash recovery F:\recovery.img
Where F:\ was the location I extracted the image file to.
- Restart via:
Code:
fastboot reboot
- When it restarted, it gave me the OTA notification and was able to install fine.
I don't know if the OTA notification would automatically show for everyone, if not you can try to check for updates in the settings or try some of the step on the thread: LINK
related issue
I found and issue on code.google.com that seems related to this.
I'm linking them in the hopes of getting some official response about this.
Just search for number 29954 on code.google.com as I'm not allowed to post links here yet.
This worked perfectly for me. Glad to have that done with. Didn't lose any data at all.
I have this issue also. Stock Galaxy Nexus from the Spain, no mods, not unlocked.
Its necesary unlock bootloader to flash a recovery image
I can reboot my Nexus after going through the install of 4.0.4 (my phone don't get stuck at the Google logo), but the version stays at 4.0.2 however.
Do I also have to unlock bootloader and flash 4.0.4 etc. or is there another way to work around the update problem?
Stock and unlocked Galaxy Nexus bought (and in use) in The Netherlands.
Thanks!

HTC One M8 - Soft brick on unrooted phone (apart from OS upgrades)

I've had my M8 since about the end of 2014. Originally on Android 4, have since done OTA upgrades to 5 and 6 as they were flagged as available by my carrier (UK, O2).
I've never managed to get HTC Backup on my PC to recognise the phone, even with the original USB cable, so have never done a proper backup (Yes. I know). Fortunately for me, my Gmail contacts list was almost up to date, and apart from my calendar, that was the most important thing to save, so I've just had to grin and bear it.
Because of the lack of proper backup and therefore the facility to restore from one, I'd never done a factory reset after the various OS upgrades, which I've been told might have avoided my present situation, which is that I can't get any further than a bootloop situation. Other than that, I can get into recovery mode, but no further.
I've tried clearing the cache, I've tried a factory reset. Neither of those have got me anywhere.
I've no great desire (at present) to go fiddling with rooting or anything clever with the phone, I'd just like to get it working again. I've downloaded Android Studio to get the SDK for ADB but don't really know what I'm doing, and if I mess around without expert advice I could end up with a hard brick - which is why I'm here.
Can anyone give me some guidance about what I need to do to get my phone working again?
Thanks in advance...
Hi, I have the same problem, started a few days ago when I was trying to download VLC from the play store, the phone rebooted and said optimizing apps.... It has been in an optimizing apps bootloop since - it gets to the end, then says starting android then freezes and reboots, then starts again... I tried clearing the cache and doing the factory reset as well but nothing helps. We could really use some expert help on this :S
If a stock phone isn't booting, and factory reset doesn't help, the OS is possibly damaged or corrupted in some way; and needs to be restored.
If your version has RUU, you can try to run that.
If no RUU for your version, then probably your only choice is to unlock the bootloader, install custom recovery, so you can restore a stock TWRP backup from the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am in a very similar situation, apparently because of a botched automatic system update, almost same symptoms as airick94. I haven't tried a factory reset yet though, because I want to try to recover what I can from the internal storage first. Can I do that through ADB even if my phone is not recognised as a device by the computer?

Official RUU Restore to Stock FAILS Unbrick Using This Method

There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
upperdecker said:
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
Click to expand...
Click to collapse
Thanks, and MetroPCS. I'm going to try and decipher what you just typed and see if I can restore the handset, because it's stuck atm.
I flashed the exposed framework but my phone wasn't working right so I did twrp restore from a backup that I had previously used however now my phone is STUCK ON THE HTC logo screen.
I downloaded your files, followed your instruction and OMG! Thank You sooooo much I'm back to normal AND WITH SU. Thanks again!!
WARNING careful when messing with exposed framework its works but my phone had issues
Thanks grmiyce
Woooogh! That info was sooo helpful. I was able to restore my phone ( HTC Desire 530 - TMobile ) to normal behaviour after it was stuck at the HTC logo for 2 days. How did it get there?
Well , long story short, I installed TWRP , did not make a Nandroid backup, and installed super su v2.46. Then to help fix the problem I installed super su 2.74 , all from twrp, but that did not help the situation. I wiped all that could be wiped from TWRP but that did not help.
I tried to install my stock ROM but could not find it in a zip format so that was a failure. I was considering a custom ROM (and still am) but to this point I am uncertain as to what ROM I can use with minimal to Zero issues ( i don't wanna brick the phone). I'll gladly accept any suggestions.
Anyways I came across this info and it saved my life...I am so happy.
Also as i am back to square one, I still have to try to network unlock this phone, it is locked with TMobile device Unlock app. I have paid for an unlock service and i was told that it was good to go but i could not get the device unlock app to reach to the 'permanent unlock' screen so i can unlock the phone. And that is why i was trying to root to uninstall the app and reinstall it since it was a system preinstalled app.
Btu anyways , I'll have to figure that out, at least the phone is back up now..
Thanks.
grniyce said:
There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Click to expand...
Click to collapse
it work on htc desire 530 OR not?
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
m3gapxl said:
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
Click to expand...
Click to collapse
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
yurais said:
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
Click to expand...
Click to collapse
Yeah, I've seen that disclaimer multiple times. However, the warranty portion of my post is non-consequential and unrelated to my real question: *has anyone found a way to unroot the phone successfully, yet?* HTC explicitly states on their website that unlocking the boot-loader doesn't void your warranty, in and of itself. Only damage that occurs as a result of said rooting (e.g: hard-bricking your phone by installing the incorrect ROM or over-clocking the CPU).
That being said, (according to articles like these: motherboard.vice.com/en_us/article/jailbreaking-iphone-rooting-android-does-not-void-warranty) they wouldn't be able to deny me service, even if they wanted to. Not that you asked, but my phone has a manufacturer defect (faulty usb port) and is increasingly becoming more unstable; the root had nothing to do with it.
Thanks for the heads up, I'm simply looking for help in the other matter. I'll keep it in mind when contacting them.
HTC Desire 530 (Canada - Freedom Mobile) Bricked(?)
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
chiassoo said:
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
Click to expand...
Click to collapse
Awesome job my man saved me from a brick last night flashed boot system then supersu and all rooted and we'll[emoji41] [emoji12]
Sent from my HTC 2PST2 using XDA-Developers Legacy app
I can confirm that the decryption tool works for update 1.36.1550.5 on the MertoPCS version
http://www.htc.com/us/support/htc-desire-530-metro-pcs/news/
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.5_Radio_01.01_U113251531_68.01.61229G_release_495720_signed_2.exe
*edit* it still get a notification about an update
guess ill just use htc's method
I can not install a rom on my htc desire 530 because the android version I have is 1.01.619.1 and the one on the htc page is 1.01.617.25.
help
RUU from HTC says phone wrong model, TWRP says right model, update fails!
I'm getting an update available notice on my HTC Desire 530 from MetroPCS. It says that "Software update: 1.36.1550.14 (66.88 MB) This update contains critical security updates and system enhancements to improve overall device performance."
I'm currently on 1.36.1550.5 so I tell it to Install now. It downloads, reboots into recovery, which is TWRP 3.0.2, and when I look at the log, it failed.
"This package is for "htc_a16ul" devices; this is a "a16".
M60QCT.02.003.021
E:unknown command [set_err_msg]
This package is for "htc_a16ul" devices; this is a "a16""
When I am in download mode, it says it is htc_a16ul.
So, I tried downloading the update from HTC on my computer. I grabbed this file:
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.14.exe
It fails basically with the same error.
How can I flash the update?
Boot into download mode and then run the .exe update
Worked great. Thanks Bennyoo

[Q] Please help, unrooted HTC One XL lost/"forgot" all SMS (no backup)

Dear all,
I hope you can help me retrieve my lost SMS. Please excuse me if the question has been asked before, but all threads I found were dealing with very different devices and/or devices rooted prior to the event.
Also, I'm an absolute newbie to this matter, up until now my phones have worked just fine the way they were delivered.
I have an unrooted HTC One XL with Android 4.2.2 and HTC Sense 5.0 (~4 years old). Yesterday, my phone went out of power while I was watching a youtube-video. Back home, I started to charge it, and turned it back on after half an hour of charging. Everything seemed perfectly normal, but when I got an SMS and openend it, I realized it was the only SMS left in Messages! So far, I have never done a backup of my SMS (even though some of them are very precious to me - I'm such a naive fool ), because the nice ladies at the O2-shop always helped me transfer them from the old phone to the new one.
Please excuse the wall of text to follow, but I have downloaded a ton of software already to save my data, and I guess you need to know precisely to help me:
First, I turned on flight mode to keep new SMS from writing over fragments of the old SMS which might still be there. Then I've "tried turning it off and on again" , but to no avail. Then I've tried recovery software working without root, Myphoneexplorer and Titanium backup, but of course they only found the one SMS that I hat received after the crash. Then I downloaded Android Data Recovery by Aiseesoft, which unfortunately needs a rooted device, so I set out to root my first phone.
I tried different Apps, towelroot + SuperSU, King Root and Kingo root, which all didn't work. I then tried the "official" way via htcdev.com, but got stuck in the middle (My phone was in fastboot usb attached to my laptop, but the command fastboot oem get_identifier_token was not understood. Imagine my distress, I'm such a newbie that just the sight of a command window gives me sweaty palms.). Maybe something to do with the drivers (the HTC drivers coming with Hasoon2000's Toolkit, which I also tried for the "official HTC route", weren't compatible with my Windows 8 laptop, so I had to download some universal ADB drivers instead).
I've asked my more tech-savvy friends on fb, who mentioned some of the Apps I've tried, but also frightened me with the contribution that if I root my phone now, I'd HAVE to go through a factory reset in the process. So my SMS fragments, if there were any on my phone still, would be erased by the time I could give Android Data Recovery a shot.
So please help me with the following:
- Do you see any way how I can retrieve my lost SMS?
- Is there a way to root without factory reset?
Additional info: I don't mind if my phone gets destroyed in the process of saving my SMS. It's anyhow time for a new one. What I WOULD mind is destroying my laptop, so as a laywoman I would only very reluctantly try stuff like "force-feeding" my laptop new drivers and such. Still, I would be thankful for any kind of ideas, whether I'll be brave enough to try them or not.
Thank you very much in advance,
M&C
Marigold&Catnip;69616753 said:
Dear all,
I hope you can help me retrieve my lost SMS. Please excuse me if the question has been asked before, but all threads I found were dealing with very different devices and/or devices rooted prior to the event.
Also, I'm an absolute newbie to this matter, up until now my phones have worked just fine the way they were delivered.
I have an unrooted HTC One XL with Android 4.2.2 and HTC Sense 5.0 (~4 years old). Yesterday, my phone went out of power while I was watching a youtube-video. Back home, I started to charge it, and turned it back on after half an hour of charging. Everything seemed perfectly normal, but when I got an SMS and openend it, I realized it was the only SMS left in Messages! So far, I have never done a backup of my SMS (even though some of them are very precious to me - I'm such a naive fool ), because the nice ladies at the O2-shop always helped me transfer them from the old phone to the new one.
Please excuse the wall of text to follow, but I have downloaded a ton of software already to save my data, and I guess you need to know precisely to help me:
First, I turned on flight mode to keep new SMS from writing over fragments of the old SMS which might still be there. Then I've "tried turning it off and on again" , but to no avail. Then I've tried recovery software working without root, Myphoneexplorer and Titanium backup, but of course they only found the one SMS that I hat received after the crash. Then I downloaded Android Data Recovery by Aiseesoft, which unfortunately needs a rooted device, so I set out to root my first phone.
I tried different Apps, towelroot + SuperSU, King Root and Kingo root, which all didn't work. I then tried the "official" way via htcdev.com, but got stuck in the middle (My phone was in fastboot usb attached to my laptop, but the command fastboot oem get_identifier_token was not understood. Imagine my distress, I'm such a newbie that just the sight of a command window gives me sweaty palms.). Maybe something to do with the drivers (the HTC drivers coming with Hasoon2000's Toolkit, which I also tried for the "official HTC route", weren't compatible with my Windows 8 laptop, so I had to download some universal ADB drivers instead).
I've asked my more tech-savvy friends on fb, who mentioned some of the Apps I've tried, but also frightened me with the contribution that if I root my phone now, I'd HAVE to go through a factory reset in the process. So my SMS fragments, if there were any on my phone still, would be erased by the time I could give Android Data Recovery a shot.
So please help me with the following:
- Do you see any way how I can retrieve my lost SMS?
- Is there a way to root without factory reset?
Additional info: I don't mind if my phone gets destroyed in the process of saving my SMS. It's anyhow time for a new one. What I WOULD mind is destroying my laptop, so as a laywoman I would only very reluctantly try stuff like "force-feeding" my laptop new drivers and such. Still, I would be thankful for any kind of ideas, whether I'll be brave enough to try them or not.
Thank you very much in advance,
M&C
Click to expand...
Click to collapse
I currently see no means to save your SMS { I am really sorry to say that }
The first step to root is to unlock bootloader, unlocking it sure wipes the data
DevUt said:
I currently see no means to save your SMS { I am really sorry to say that }
The first step to root is to unlock bootloader, unlocking it sure wipes the data
Click to expand...
Click to collapse
Oh, that wasn't what I had hoped to hear. Anyhow, thanks for your contribution.
Will unlocking the bootloader completely erase the data, or will it "only" allow the phone to overwrite the space if new data comes up? If the latter were the case, maybe the Android Data Recovery might have a chance afterwards?
Please excuse my newbie questions, I bet this is common knowledge among all of you.

Categories

Resources