My phone suddenly had a momentary display malfunction (some of the text on the screen just turned into garbled pixels) and then entered into a boot loop. I didn't make any changes or updates to the phone recently. It no longer boots normally - just the Samsung logo and some of the Verizon logo animation, then it reboots and starts again. How do I pull my user data off (photos mainly) before trying a factory reset? The phone is totally stock. I haven't unlocked it, rooted it, or installed any custom recovery/ROM/bootloader/whatever. (I sound like I don't know what I'm talking about because I don't, haha.) The touchscreen is fully functional. I'm sure this has been covered here before, but I haven't found anything that totally explains how to do this in this particular situation, so I'd really appreciate any help anyone can provide.
The only time I can get the phone to show up under adb devices is when I boot it in recovery mode and select "Apply update from ADB". But it says "sideload" next to it in adb devices, and the push, pull, and shell commands return errors. I've read that this is normal. Wiping the cache partition didn't solve the boot loop problem.
If it helps, this is what the top of the recovery screen displays:
Android Recovery
Verizon/heroqltevzw/heroqltevzw
8.0.0/R16NW/G930VVRSBCTC1
user/release-keys
I'm no Android expert, clearly. I've heard it mentioned that I need to install a custom recovery in order for this to be possible. To be clear, I want to make sure I don't erase the user data before I have a chance to pull it off the phone. These are the questions that I still have after reading information elsewhere (some of which I'm just asking out of an abundance of caution):
Is it correct that I need to install a custom recovery before I can pull this data off the phone?
Do I need to have it unlocked/rooted/anything else in order to be able to install a custom recovery? Or is there anything else I should do before installing it?
Which custom recovery should I install?
Do I need a custom ROM, if that's a different thing?
Do I need a custom...bootloader, if that's also a different thing?
Should I use Odin or Samsung Smart Switch to install the custom recovery?
(Extra credit: Does it sound from my description of how the boot loop started that this phone has hardware problems and should be replaced ASAP?)
Thank you so much for any help you can provide! Any extra information beyond my questions will be very much appreciated, too, of course. You guys never cease to impress.
You have a B version bootloader like me, and so far no root/custom recovery has been made for our versions of bootloaders. If I were you, I would check if you had maybe like a previous backup, and if Google made an automatic backup of your apps and photos? If you didn't use a 3rd party backup, and if you don't want to wait, you might lose some files. I also think you might be able to flash a certain part of stock firmware to get your phone to boot again, but I'm not sure
Also, if you don't care about files that can't be get through automatic backups, might as well flash a whole stock firmware, which as far as I know, may be the easiest way to get out of one.
Please correct me if I'm wrong
Also to answer your bullet points:
1. I'm not sure if you need a custom recovery, but from my experience from a Verizon s5, that's probably a yes.
2. Since this is Verizon, you would need to unlock your bootloader in order to install a custom recovery, which in where I posted my first reply, the B version of the bootloader is still locked down without any known way to unlock it. You and me are stuck with this, as I also have the B version.
3. If the heavens line up and you somehow unlock the bootloader, try to flash a recovery Called TWRP under the name "Herolqte" (that's what I think). If that doesn't work, try to find one that works with the phone on XDA. If neither of those show up try to use another custom recovery like CWM.
4. If your trying to recover data on a phone, flashing a custom ROM is probably the last thing you want to do. A custom ROM is a modified version of Android, which may mean you'll have to format your device anyways so this is probably not what you want (even though it would be nice :[ )
5. As in post 2, all you would need to get a custom recovery is to unlock the bootloader. I'm not even sure if you CAN get a custom bootloader, as Odin won't even let me flash a stock bootloader to my phone that is the same exact Version >:[
6. You would need to use Odin if you were trying to flash something to your phone. Smart switch I think WOULD let you back up your device, but you would need to be on the home screen on your phone, which in turn, would probably need you to be out of that bootloop.
7. This is probably a software issue. If you don't care to much about the idea, try flashing some parts of a stock firmware. I was personally in a boot loop 2 days ago, but I flash a stock modem file (I think that was the second file slot from the bottom in Oden) and that got me out, but for some reason wiped my phone clean, and I'm not sure why.
Anyways. Goodluck in recovering your data. Also I'm not sure if a factory reset would even fix a boot loop
yaas
yaas
Related
Just running this by, to see if i have everything correct.
if i have cwm installed, regardless of model,
to install a stock firmware from samsung, thus basicaly resetting my device back to stock,
i can go into cwm and install this,
http://samsung-updates.com/details/12916/Galaxy_Note_8.0_LTE_Canada/SGH-I467M/RWC/I467MVLAMG2.html
since thats my model,
and it will restore the device to factory settings, correct?
will this wipe out cwm or will cwm stay?
also, can i do this from odin?
if so,
as long as one can get there device into download mode, they can restore the device correct?
and if thats the case, what are the ways that one may wipe out that portion of the device?
is that part of the bootloader?
or is it part of the kernal,
sorry for such noob questions...
i am really new to rom flashing, but really want to get good at it.
thanks everyone in advance,
ths forum is amazing, and all you people are amazing.
Samsung devices are pretty easy to restore and hard to brick, as long as you have some firmware you can flash through Odin. Download mode should remain intact even if you mess up the bootloader/system.
I haven't looked at the link you provided, but assuming the downloads there are in Odin format, flashing back to stock should be easy as pie.
If however, you don't have Odin flashable firmware, and you ahve soemthign that needs to be flashed via fastboot/recovery, then I'm hoping your recovery is still intact and you can boot to it via Volume Up + Home + Power. If you can get into it, you should be able to load firmware onto a MicroSD card and flash from there.
GhostCyber said:
Just running this by, to see if i have everything correct.
if i have cwm installed, regardless of model,
to install a stock firmware from samsung, thus basicaly resetting my device back to stock,
i can go into cwm and install this,
http://samsung-updates.com/details/12916/Galaxy_Note_8.0_LTE_Canada/SGH-I467M/RWC/I467MVLAMG2.html
since thats my model,
and it will restore the device to factory settings, correct?
will this wipe out cwm or will cwm stay?
also, can i do this from odin?
if so,
as long as one can get there device into download mode, they can restore the device correct?
and if thats the case, what are the ways that one may wipe out that portion of the device?
is that part of the bootloader?
or is it part of the kernal,
sorry for such noob questions...
i am really new to rom flashing, but really want to get good at it.
thanks everyone in advance,
ths forum is amazing, and all you people are amazing.
Click to expand...
Click to collapse
sorted!
Got it sorted, thanks very much..:good::laugh:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Im having the same issue too
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Try this? http://forum.xda-developers.com/showthread.php?t=2451696
I finally solved the issue, miraculously, nothing was working so I just left the phone to continuing formatting for an hour so, came back, and it seemed to have done it, I installed Custom ROM, and it booted up normally, I'm not sure what triggered the phone to accept the system mount, but I am sure as hell happy it did. I was worried I was going to have a bricked device on my hands.
Hold strong, just allow the phone to continue doing what it needs to do I guess. Leave TWRP in all STOCK settings, I tried to modify multiple settings based on Devs saying to get a faster formatting to enable RM-F but I have no clue why and what didn't work.
Anyhow, problem resolved!
On another note, I would never use the recommended method from Droid_<3er as they would completely brick your phone unless you're specifically in the situation listed in that thread. As you would put your phone into a state where you lose both access to Recovery and ROM access, rendering your phone to a piece of plastic and metal. But it's definitely worth mentioning, I just had to do some research on the method cause I had the same thinking as well.
I can confirm by using normal make_ext4fs while formatting /system is the best way to avoid this. Was afraid of having a 5.2 inch brick, but thankfully, disabling the quick way to format has fixed it and allowed /system to be remounted.
I think (<-- that's the disclaimer) that it's OK to use the fast formatting method for Dalvik Cache and Cache, but not for System.
in my opinion it's best to use rm -rf /system aka delete_recursive("/system"); than formatting
I'm having the same issue, and I'd be willing to try this one. How would I do this?
I have the same issue with CWM and now got over to twrp with the same outcome.
Right here I see solutions that worked so far, but it seems like this was rather accidentially.
I want to try some of these, but in the thread posted above
"Try this? http://forum.xda-developers.com/show....php?t=2451696"
it says "Do it the wrong way and your phone might get nuked"
unfortunately it doesn't say what the commands in there mean...
Can anybody be of assistence which method will properly work without nuking the phone?
I have the MOTO G 2014 (2nd Gen)
It is an updated bootloader
i got the latest twrp
and some titan roms.
only stock rom will work so far,
custom roms will result in a bootloop.
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2471370
The program get's stuck at analyzing device and doesn't flash or download anything. It would be nice if I can perform at least a factory reset in case something wants to blow up in my face. If anyone has some ideas (ridiculous or not), feel free to let me know.
slicknessessity said:
I'll be as descriptive as possible.
I must have did a bad flash with CWM, so I tried to reflash with CWM, TWRP, and even the OEM recovery. When attempting to boot to recovery, the screen goes blank. My pc attempts to connect every drive letter I've got when I plug in the usb. Among which, I can access an image folder on the device. Can't figure out how a bad recovery flash does this, but I can't find a fix for the life of me. Phone works as it should. My problem is anything involving recovery will give me a black screen, so factory wipe will not work.
Any ideas would be well appreciated.
Thanks
Click to expand...
Click to collapse
Hey man you could try just using Flashify to flash a recovery...its a app...then boot to recovery
I tried using that method. It gives me the same thing. Maybe somewhere in the recovery location (or associated locations) seem to may have gotten damaged somehow during the bad flash? Flashing the phone completely I'm sure would do the trick. I came from the droid 4, so sbf/fastboot flash would solve all my problems. Searching around landed me to a kdz, which seemed to be an equivalent, but isn't working or maybe I'm doing something wrong? Any advice on this would be greatly appreciated.
I went and did a full flash using this method: http://forum.xda-developers.com/showthread.php?t=2448960. Since I couldn't find a recovery fix per se, I decided to flash the whole thing and start fresh (oh well).
It downgraded to 11A in the process, so the same can probably be said for 10B for compatible custom builds.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.
Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.
Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.
93-14 hasn't been leaked yet. So you'll be stuck for now.
Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.
Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.
Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.