I just bought this phone off Amazon. It is unlocked. I'm running 5.0 stock. I've always carried a Samsung note and I'm fully aware of the rooting and roming etc.. Since this phone was bought out right will the bootloader be unlocked? Also I don't have a pc so I was hoping towelroot. But like I say,I'm new to Sony. Kingroot?? Also is there a way to check if bootloader is unlocked
Sent from my C6802 using XDA Free mobile app
harley1rocker said:
I just bought this phone off Amazon. It is unlocked. I'm running 5.0 stock. I've always carried a Samsung note and I'm fully aware of the rooting and roming etc.. Since this phone was bought out right will the bootloader be unlocked? Also I don't have a pc so I was hoping towelroot. But like I say,I'm new to Sony. Kingroot?? Also is there a way to check if bootloader is unlocked
Sent from my C6802 using XDA Free mobile app
Click to expand...
Click to collapse
If your bootloader is unlocked, it'll behave much like a Nexus. Rooting won't be an issue ever, and all you'll have to do is to boot a kernel with recovery (CWM/TWRP) and flash SuperSU. Done.
It's a lot worse if you have a locked bootloader. You can find out if the bootloader is unlockable by dialing *#*#7378423#*#*, then go to --> "Service Info" --> "Configuration".
Bootloader unlock allowed - Yes << Means that your bootloader is locked, BUT it's unlockable.
Bootloader unlock allowed - No << Means that you can't unlock the bootloader
Bootloader Unlocked - Yes << Means that your bootloader is unlocked (which is unlikely on a new device)
The easiest way to unlock the bootloader is to get the unlock key directly from Sony, which is quick and easy, and then use Flashtool (on your computer) to unlock the bootloader. After that, happy flashing.
Do ask if you have any other questions.
I used the sequence you provided and it does say root status bootloader unlocked. My phone is international version
Happy flashing then.
If you only want an enhanced stock experience, flash any custom kernel built for stock 5.0 via fastboot, this will also give you recovery in which you can flash SuperSU and get root.
Or, if you want to try something different, AOSP-based ROMs like CM12.1 are also available. You need to unpack the kernel (boot.img) from the ROM zip and flash that using fastboot, in order to get the recovery that cones with the ROM. Then boot into that recovery and flash the ROM zip itself and reboot.
You can also install a semi-permanent TWRP recovery (i.e. won't change with your kernel), but I'll stop here and let you do your experiment.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Thing is I'm use to Samsung. They come with a stock recovery. The z don't. I guess. I can't access it. How do I load a kernel without having recovery?
Sent from my C6802 using XDA Free mobile app
harley1rocker said:
Thing is I'm use to Samsung. They come with a stock recovery. The z don't. I guess. I can't access it. How do I load a kernel without having recovery?
Sent from my C6802 using XDA Free mobile app
Click to expand...
Click to collapse
Flash or hotboot a custom kernel that has recovery on it using fastboot or QuickIMG, boot and then press VOL UP when the LED turns on. It doesn't matter what kernel you use. I usually use a KitKat kernel with recovery since it has been laying around on my computer for years
Speak up if you need any technical help.
I've been trying the volume up and power button. No light or nothing. It just boots up. Do I need a pc ?
Sent from my C6802 using XDA Free mobile app
harley1rocker said:
I've been trying the volume up and power button. No light or nothing. It just boots up. Do I need a pc
Sent from my C6802 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, the LED will only light up once you have recovery, and since it doesn't have a recovery by default, it won't light up. You'll also need a computer to flash a custom kernel. Then you'll be able to either install a proper recovery (I recommend NUT's Dual Recovery, which will give you Philz Touch and TWRP), or just flash SuperSU and live with root (but no recovery).
BTW, what Android version are you on?
5.0.2... So once I have a pc hooked to it,there's a tool that'll push a recovery to the phone?
Sent from my C6802 using XDA Free mobile app
harley1rocker said:
5.0.2... So once I have a pc hooked to it,there's a tool that'll push a recovery to the phone?
Sent from my C6802 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, so I guess you haven't gotten the 5.1.1 update quite yet. Once you're on a computer,
1. Install Minimal ADB & Fastboot to install the needed tools
OR you can use QuickIMG, if the command line scares you.
2. Download NUT's Dual Recovery. Be sure to download the right version!
3. Put your device in Fastboot by holding VOL UP when you plug your Ultra to the computer. The LED will be BLUE
4. Flash the kernel and unplug your Ultra from the computer and boot it, and press VOL UP once your phone vibrates/LED light up
5. You're now in recovery, and it's now permanent (until you flash a different kernel), and flash SuperSU.
6. Reboot and you're done.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)
Thread closed
Related
Im a new owner of the Note 2 and a new member to XDA. I have been doing a lot of reading over the last couple days regarding unlocking the bootloader, flashing CWM and rooting my phone. My question is, is there a certain order that this has to be done in. For example, the bootloader then the recovery or does it not matter
Sent from my SCH-I605 using xda app-developers app
kevinbauman said:
Im a new owner of the Note 2 and a new member to XDA. I have been doing a lot of reading over the last couple days regarding unlocking the bootloader, flashing CWM and rooting my phone. My question is, is there a certain order that this has to be done in. For example, the bootloader then the recovery or does it not matter
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Read the unlock post in the dev section....
I have but I will reread it again, just want to make sure I fully understand everything before I start.
Sent from my SCH-I605 using xda app-developers app
Hint: You can't load anything until you unlock the bootloader.
Adams guide in original development http://forum.xda-developers.com/showthread.php?t=2043636
Follow this and you will be unlocked rooted and twrp
Thanx man
Sent from my SCH-I605 using xda app-developers app
kevinbauman said:
My question is, is there a certain order that this has to be done in. For example, the bootloader then the recovery or does it not matter
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
1.Flash revision3 via odin following the guide in its thread. (This will give you root)
2.Follow the bootloader unlock process in adam's guide from its thread (this will unlock your bootloader and unless hes changed it flash twrp a custom rocovery.)
Now you need to reboot into recovery and make a back up. To do this you need to go into recovery (twrp or clockwork mod). You can get to recovery by powering off the phone and holding volume-up+home+power. Now go to backup and back up. If you have an external sd I would recommend selecting the option to backup to it.
After that select a rom you want. If you want stock rooted you dont have to flash anything. Look in your app drawer if you see an app called supersu or super user you're rooted. If you want another rom follow these steps to flash it.
1. Read rom thread for known bugs so you know what youre getting into.
2. Download rom. DO NOT UNZIP.
3. Check md5 sum.
4. Move to external or internal sd where you can find it.
5. Boot into recovery.
6. Select install.
7 navigate to rom file.
8. Swipe to install. If it has aroma follow instructions if not wait for it to do its thing
Sent from my SCH-I605 using xda app-developers app
My bootloader is officially unlocked. To easy, I think it took me less than 5 minutes. Thanx for your help.
Travisdroidx2 said:
Adams guide in original development http://forum.xda-developers.com/showthread.php?t=2043636
Follow this and you will be unlocked rooted and twrp
Click to expand...
Click to collapse
Evankovich406 said:
1.Flash revision3 via odin following the guide in its thread. (This will give you root)
2.Follow the bootloader unlock process in adam's guide from its thread (this will unlock your bootloader and unless hes changed it flash twrp a custom rocovery.)
Now you need to reboot into recovery and make a back up. To do this you need to go into recovery (twrp or clockwork mod). You can get to recovery by powering off the phone and holding volume-up+home+power. Now go to backup and restore back up. If you have an external sd I would recommend selecting the option to backup to it.
After that select a rom you want. If you want stock rooted you dont have to flash anything. Look in your app drawer if you see an app called supersu or super user you're rooted. If you want another rom follow these steps to flash it.
1. Read rom thread for known bugs so you know what youre getting into.
2. Download rom. DO NOT UNZIP.
3. Check md5 sum.
4. Move to external or internal sd where you can find it.
5. Boot into recovery.
6. Select install.
7 navigate to rom file.
8. Swipe to install. If it has aroma follow instructions if not wait for it to do its thing
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Nicely written!
Travisdroidx2 said:
Adams guide in original development http://forum.xda-developers.com/showthread.php?t=2043636
Follow this and you will be unlocked rooted and twrp
Click to expand...
Click to collapse
It seems like CWM is the preferred recovery among most flashers and ROM developers. But I could be mistaken. Somewhere on xda or elsewhere I read a comparison of the 2.
Personal preference I used to use cwm but once I made the switch to twrp I did not look back. However some roms like cm10 say you must use cwm.
I used cwn on my nexus and twrp on my note 2. It seems if its touchwiz they recommend twrp if its aosp sourced they recommened cwm
Sent from my SCH-I605 using xda app-developers app
Sorry if this was addressed elsewhere, but I did try to seek it out first. I am stock rooted (Exynos abuse method) and I have added in the all apps in multiscreen modification. Two questions:
1. From what I can tell, I do not need to flash revision3 first (since I am stock VRALJB rooted), just run the casual exploit and then flash suckitverizon, correct?
2. Does the add apps to multiview mod conflict in any way with unlocking the bootloader or flashing a new ROM?
I think I know the answer to both (yes and no respectively), but I like to measure twice and cut once. Thanks
Im not exactly sure. But in all honesty it would probably just be best to odin flash to stock and start over.
Sent from my SCH-I605 using xda app-developers app
tfly212 said:
Sorry if this was addressed elsewhere, but I did try to seek it out first. I am stock rooted (Exynos abuse method) and I have added in the all apps in multiscreen modification. Two questions:
1. From what I can tell, I do not need to flash revision3 first (since I am stock VRALJB rooted), just run the casual exploit and then flash suckitverizon, correct?
2. Does the add apps to multiview mod conflict in any way with unlocking the bootloader or flashing a new ROM?
I think I know the answer to both (yes and no respectively), but I like to measure twice and cut once. Thanks
Click to expand...
Click to collapse
1. just did everything yesterday. i rooted with the exynos exploit but couldn't get odin to flash suck it verizon, so i rooted with casual, unlocked the bootloader with odin, which also installed twrp. i then hooked it up to my computer, copied clean rom to the sd card, and installed. no need to install revision if you don't want to. go straight to beans/cm10/PA/cleanrom or whatever else you want.
summary - root, unlock bootloader, install whatever rom you want. no need to install roms then overwrite those roms
2. if the rom is TW based, you can make any app multiview. beans and cleanrom come with the modification there already afaik. cm1-/aosp roms don't have it, as it's part of touchwiz
Followed the advice to flash back to bone stock, then unlocked the bootloader and flashed cleanrom. Piece of cake as advertised. Only hiccup was getting Odin to recognize my phone...had to start it a second time, but that was it. Thanks for the help.
hey guys im trying to unlock my bootloader as we speak and i cant get it to work it says my adb server is out of date. killing...
ADB server didn't ACK* failed to start daemon *error: protocol fault (no status) please help this is the first device ive had problems with thank you verizon
Well I may have truly found out how to brick this phone. First what you want to do is unlock the bootloader, then flash a recovery. Next you want to gain SU on the phone and root. If your their and you want to brick your phone you will need to do the following steps.
1. Forget to create a restore
2. Flash the google nexus 4.3 to the phone
3. realize it in a boot loop
4. format data on the phone (yeah that's right...I wiped everything)
5. sit back and admire your work.
Any ideas?
Jtag
jd1639 said:
Jtag
Click to expand...
Click to collapse
what he said
Can you get into recovery?
There is a way to adb a rom file onto the phone using twrp as long as you can get into recovery and the pc recognizes the phone....if no recovery though I don't know.. would have to be able to get into fastboot and flash twrp.
Sent from my HTC One using xda app-developers app
00mred00 said:
Can you get into recovery?
There is a way to adb a rom file onto the phone using twrp as long as you can get into recovery and the pc recognizes the phone....if no recovery though I don't know.. would have to be able to get into fastboot and flash twrp.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
I have tried to side losd a rom but either I'm doing it wrong or it just won't work. I keep getting errors. I can reboot the phone from ADB on the computer but I can't seem to move any information across...Heck I can even lock and unlock the bootloader but not side load.
Did you try this? http://forum.xda-developers.com/showthread.php?p=42426459
Sent from my HTC One using Tapatalk 4
Oh, i feel your pain, Just "soft" bricked my phone. Lucky it has plenty of juice and i was still able to get to booloader. Somewhat of an easy fix. But boy did my heart start pumping.
When you reboot, what does it do? Just sit there on the HTC screen, not light up at all, or something else?
I only ask because I thought I borked mine today going from the OTA, to .12, to S-OFF, the accidentally making it ENG S-OFF, and then the screen not lighting up when I'd try to do anything.
But I was able to get the silver HTC screen to pop up and flash the 4.1.2 RUU to go to WWE 4.2.2.
Sent from my HTC One using Tapatalk 4
Got this phone yesterday. Rooted via the kingo app and disabled/deleted knox. When I reboot phone under where it says mega its an unlocked lock that says custom. And when I press the vol - and home plus power it comes up asking if I want to download a custom rom? Is this normal?
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
yes. That is just download mode for things like odin. Still doesn't get a custom rom to work with our locked bootloader, unfortunately. You could flash stock rom that way if the need came up.
Sent from my SAMSUNG-SGH-I527
Does anyone have a quick write up of how to do this? I have an HTC one and I have been running the Insert Coin roms, but now the new roms require TWRP and I dont want to end up with a bricked phone.
sjorge3442 said:
Does anyone have a quick write up of how to do this? I have an HTC one and I have been running the Insert Coin roms, but now the new roms require TWRP and I dont want to end up with a bricked phone.
Click to expand...
Click to collapse
Easiest way is to install GooManager > Grant SuperUser access > Menu > Install OpenRecovery Script > Confirm > Wait for it to download & finish.
https://play.google.com/store/apps/details?id=com.s0up.goomanager
http://teamw.in/project/twrp2 > It's explained here, along with the other methods. Just click on the Get TWRP for Your Device box at the top right and put in HTC One, then make sure to pick the right one. The recoveries are different between manufacturers and the M7/M8, obviously.
Pretty hard to brick install recovery on these things.
I would suggest just using fastboot, fastest and safest method
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I would suggest just using fastboot, fastest and safest method
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's my preferred way to do it too, but TWRP themselves have the app install as their preferred way on their site.
So does clockwork and 4ext but I prefer fastboot. Choice is for the user I guess
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So does clockwork and 4ext but I prefer fastboot. Choice is for the user I guess
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Indeed. Another reason to suggest the app as it is more friendly to the timid ones.
It really does pay to get familiar with both fastboot commands and adb though, if you plan to mod your phone. At least to make sure that the drivers are loaded in worst case scenarios.
As far as I understand it, CWM or TWRP run in temporary partitions and in the RAM, much like boot tools on a PC such as Pmagic.
I started off with CWM via Odin on the PC and have since managed everything from there. I tried out TWRP by using a flashable zip in CWM, rebooted the usual way via the gui, tried out TWRP, then flashed CWM back and everything is fine.
It seems to me there is no danger and you just flash it the way you would a custom firmware. Plus you can back up and restore your recovery using either CWM or TWRP. In my short experience with it so far, you don't need an app, just flash and be happy. But always remember to have a backup or the original zip in case you wish to go back.
And if somehow you do mess something up (I guess it happens sometimes), make sure you have the right md5 to reflash in Odin. Simple. Just never delete anything you could need again.
Well, I am really considering purchasing a new Sony Xperia Z Ultra and selling off my GPe model of the Z Ultra since it cannot be rooted and who knows when it will be (running lollipop and not able to backup TA at this time). Just wondering if the Xperia model running jellybean or kitkat will be better for rooting purposes? The only reason I need to root it is that I am desperate for a sound/volume mod as I've had to switch back to my old Note 2, calls are so hard with the low volume on the GPe model. Any recommendations between the jellybean or kitkat models or doesn't make much difference? I really love this phone and do not want to give up on it, and rooting seems to be the only answer for a volume mod. Thank you!
Info
musebox said:
Well, I am really considering purchasing a new Sony Xperia Z Ultra and selling off my GPe model of the Z Ultra since it cannot be rooted and who knows when it will be (running lollipop and not able to backup TA at this time). Just wondering if the Xperia model running jellybean or kitkat will be better for rooting purposes? The only reason I need to root it is that I am desperate for a sound/volume mod as I've had to switch back to my old Note 2, calls are so hard with the low volume on the GPe model. Any recommendations between the jellybean or kitkat models or doesn't make much difference? I really love this phone and do not want to give up on it, and rooting seems to be the only answer for a volume mod. Thank you!
Click to expand...
Click to collapse
search Dev section of each phone u want
and check which one has trustful root method or tool
:good:
Thanks, I have been reading up but was getting a little confused with all the bootloader versions being referenced. Or are they firmwares? I'm just used to Samsung devices and trying to learn about Sony. Anyway, looks like a Z Ultra running KitKat will be best for rooting and will also work with scrobbers ROM if I decide going that route too. Right now I just want root.
But now I just read that the Z4 just passed through certification in Japan. Just when I thought there would not be a successor. Maybe I'll wait and see.
Sent from my C6806_GPe using XDA Free mobile app
musebox said:
Thanks, I have been reading up but was getting a little confused with all the bootloader versions being referenced. Or are they firmwares? I'm just used to Samsung devices and trying to learn about Sony. Anyway, looks like a Z Ultra running KitKat will be best for rooting and will also work with scrobbers ROM if I decide going that route too. Right now I just want root.
But now I just read that the Z4 just passed through certification in Japan. Just when I thought there would not be a successor. Maybe I'll wait and see.
Sent from my C6806_GPe using XDA Free mobile app
Click to expand...
Click to collapse
On the GPe, if you aren't concerned with DRM keys, warranty and camera you can just unlock the bootloader and root that way (camera may still work if unlocked on L)
There's a massive tutorial on rooting the xperia z ultra 4.4.4 (kitkat) as for Jelly bean I've owned 3 ultras and after today 4 lmao. Anyways 4.3 (jelly bean) you should be able to run towel root by Geohot.
Just get a Sony Xperia z ultra C6806 or c6833 and root it, unlock the bootloader and you can run a rom port of the GPE
I'm still on kitkat, and plan to stay for another year til M comes out. As for the z4 ultra it's just a rumor they said the same thing when the z2 came out. If it does come out I'm OK with the same screen size I just want more ram, and a faster processor even though my ultra still has no stutters
blueether said:
On the GPe, if you aren't concerned with DRM keys, warranty and camera you can just unlock the bootloader and root that way (camera may still work if unlocked on L)
Click to expand...
Click to collapse
Thanks, when I check my bootloader unlockable status it says unknown instead of either yes or no. Should I just give it a try anyway?
By the way, I'm reading through your guide and unlocking the bootloader via the Sony site and using fastboot should work for me right even if I'm on lollipop? I think I understand the process now and I don't care about the warranty or camera.
Sent from my C6806_GPe using XDA Free mobile app
musebox said:
Thanks, when I check my bootloader unlockable status it says unknown instead of either yes or no. Should I just give it a try anyway?
By the way, I'm reading through your guide and unlocking the bootloader via the Sony site and using fastboot should work for me right even if I'm on lollipop? I think I understand the process now and I don't care about the warranty or camera.
Sent from my C6806_GPe using XDA Free mobile app
Click to expand...
Click to collapse
Yes, unlocking the BL will work just fine on LP. Then just hotboot DooMLoRD's kernel to get recovery, and from there flash the superSU update zip for LP to get root.
Hotbooting a kernel: either use flashtool or "fastboot boot <path_to_doomlords_boot.img>"
It will be interesting to see if the camera focuses if the BL is unlocked from LP
OK, I'm going to give a go. Took me so long to download the flashtool but i think I'm ready to go. Will post results soon, hopefully.
Sent from my C6806_GPe using XDA Free mobile app
Well, I guess I'm out of luck. I got an unlock code from Sony but when I tried to unlock using Flashroot, it said my bootloader cannot be officially unlocked and it quit. Bummer.
But I don't understand. I thought all GPe devices were bootloader unlockable? And why was I able to get an unlock code from Sony?
Sent from my C6806_GPe using XDA Free mobile app
musebox said:
Well, I guess I'm out of luck. I got an unlock code from Sony but when I tried to unlock using Flashroot, it said my bootloader cannot be officially unlocked and it quit. Bummer.
But I don't understand. I thought all GPe devices were bootloader unlockable? And why was I able to get an unlock code from Sony?
Sent from my C6806_GPe using XDA Free mobile app
Click to expand...
Click to collapse
The GPe should be unlockable.
start a command prompt in the adb folder under flashtool and try this:
put phone into fastboot
"fastboot oem unlock 0x<key_from_sony>"
I was finally able to unlock the boot loader using flashtool and then flashed doomlord kernel for GPe but I can't boot into recovery. On the screen the android is on its back with the red triangle and it says no coomand. It keeps looping like this and the doom lord booting image. I've tried reflashing the kernel and same results.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
musebox said:
I was finally able to unlock the boot loader using flashtool and then flashed doomlord kernel for GPe but I can't boot into recovery. On the screen the android is on its back with the red triangle and it says no coomand. It keeps looping like this and the doom lord booting image. I've tried reflashing the kernel and same results.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
The doomlord kernel wont boot LP, to get a bootable phone flash the boot.img from http://forum.xda-developers.com/xpe.../lollipop-5-0-boot-fotakernel-images-t2960269
The system.img from the same thread may be the easist way to gain root. Either use that or HOTBOOT doomlords kernel
Hotbooting doesn't flash the kernel to the device, just boots it for the next boot so you should be able to use recovery
blueether said:
The doomlord kernel wont boot LP, to get a bootable phone flash the boot.img from http://forum.xda-developers.com/xpe.../lollipop-5-0-boot-fotakernel-images-t2960269
The system.img from the same thread may be the easist way to gain root. Either use that or HOTBOOT doomlords kernel
Hotbooting doesn't flash the kernel to the device, just boots it for the next boot so you should be able to use recovery
Click to expand...
Click to collapse
Makes sense now that I think about it. Just frustrated in that I haven't been able to successfully download and install adb all day. My internet must be bogged down because it times out. I was able to install minimal adb but wouldn't recognize my device and then kept getting a server out of date error. So I'm trying to do everything via fashtool. Now I can't seem to download DoomLords lollipop kernals to flash with flashtool. Talk about bad luck overall all day! What's the easiest way to get the boot image in a flash able format? Is adb the only way? Am i missing something? I might have to wait until tomorrow if that's the case.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
musebox said:
Makes sense now that I think about it. Just frustrated in that I haven't been able to successfully download and install adb all day. My internet must be bogged down because it times out. I was able to install minimal adb but wouldn't recognize my device and then kept getting a server out of date error. So I'm trying to do everything via fashtool. Now I can't seem to download DoomLords lollipop kernals to flash with flashtool. Talk about bad luck overall all day! What's the easiest way to get the boot image in a flash able format? Is adb the only way? Am i missing something? I might have to wait until tomorrow if that's the case.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah the easiest way to flash a *.img is with fastboot or flashtool (both ways are using the fastboot command)
blueether said:
Yeah the easiest way to flash a *.img is with fastboot or flashtool (both ways are using the fastboot command)
Click to expand...
Click to collapse
I was afraid of that. I just can't for the life of me get adb going. Its installed but either won't recognize my device or errors out and fails. I don't know what else to do. I should have left well enough alone, so crushed at this point. I'm about to throw in the towel.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Now looks likey battery finally discharged completely on the Z Ultra. How can I charge it back up. Can't get it to boot up.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
musebox said:
Now looks likey battery finally discharged completely on the Z Ultra. How can I charge it back up. Can't get it to boot up.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
It should charge fine on a wall charger
I gave it another go this morning but adb won't recognize my device. I've trued killing it and unplugging the phone and vice versa, uninstalling and reinstalling the drivers for both, but just can't seem to get it to work. All I need to do is flash the 5.0 boot img but can't find a way to do it. Even in flashtool, I get an error that device needs to be on adb/fastboot depending on which way I do it.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
OK, was able to fastboot buy now I'm getting an error regarding the boot image. It fails and says:
writing 'boot'...
FAILED (remote: image is not a boot image)
I've tried downloading the boot.img multiple times but still fails. Maybe I'm downloading wrong? If I click on it, I directs me to a webpage with all the coding, so I've been using 'saving target as' to save it onto my PC. Is there another way?
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
blueether said:
Yeah the easiest way to flash a *.img is with fastboot or flashtool (both ways are using the fastboot command)
Click to expand...
Click to collapse
Can you please explain to me how I should be downloading the boot.img file posted by DoomLord? I'm obviously doing something wrong because I can't apply it fastboot without erroring out. I've also tried searching for the complete ota files so I can pull the stock boot.img file and no luck. I'd anyone has it, could you please post it for me? The boot.img file for stock lollipop 5.0.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app