Hi I know this phone is still new.
Can anyone please tell me if there's any Custom recovery for this phone?
I hope Cyanogenmod will be available for this device soon
Because of the locked bootloader and all the "security things" bb put in the device it will take some time to get a custom recovery if it is possible someday.
Related
Hello. I have an AT&T LG G2 D800 and my phone is currently not rooted. I was running stock D8001o I believe and i was rooted with Custom Recovery. I decided I know longer wanted Root permisons and that i would just flash back with lg flash tool and in doing so i downloaded and flashed the files(LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot) and the (LGD800_20130904_LGFLASHv160.dll) and it went through the process that it need to do. after about 7-10 min it completed and passed. "Now my phone will BOOT UP says I have NO DATA connection and then it just powers its self off and does a repeat of the BOOT UP" boot up bootloop. anyone know what is wrong or how to fix. im stumped and dont know what i did wrong. big thanks to any and all suggestions. one last thing. i was able to go into my about phone to look at some of the info of the phone and its saying their is no IEMI number.
chaz411 said:
Hello. I have an AT&T LG G2 D800 and my phone is currently not rooted. I was running stock D8001o I believe and i was rooted with Custom Recovery. I decided I know longer wanted Root permisons and that i would just flash back with lg flash tool and in doing so i downloaded and flashed the files(LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot) and the (LGD800_20130904_LGFLASHv160.dll) and it went through the process that it need to do. after about 7-10 min it completed and passed. "Now my phone will BOOT UP says I have NO DATA connection and then it just powers its self off and does a repeat of the BOOT UP" boot up bootloop. anyone know what is wrong or how to fix. im stumped and dont know what i did wrong. big thanks to any and all suggestions. one last thing. i was able to go into my about phone to look at some of the info of the phone and its saying their is no IEMI number.
Click to expand...
Click to collapse
so NO one has and useful information or would be kinda enough to help me out. please and will buy the person a beer to helps with the method to solving this issue.
Hello everyone! I'm brand new to the forums so if I am breaking any rule or regulation, just give me a heads up. So, some basic information about my predicament.
- own a Samsung Galaxy Note 3 from Verizon.
- I use t-mobile network. Works great with no problems.
- phone was successfully rooted via towel root.
I was looking to get cynagenmod on the phone so I started looking up guides and such. Only thing I wasn't aware of was that carrier branded versions can't have their recovery flashed. That said, I used flashify and the clockwork apk. The app did its job, killed the stock recovery, but couldn't load the new one. Now the phone says error, no recovery when trying to access it during boot.
It should be said that the phone still boots and works normally but I really want to get the recovery working so I can at least try again the right way to get cynagenmod working.
My question is, is it possible to get my hands on the stock recovery for my phone and just flash it back to how it was? Basically, how do I fix this problem I put myself in. Of course, I didn't make backups. During the whole process, I figured "if I follow this tutorial word for word, why bother with backups?" look how wrong I was
Any help would be sincerely appreciated. I'm posting this from my replacement phone, not my note 3.
Hi all,
I'm new to rooting and modifying my Verizon S5 - so I don't have the most technical knowledge of Android nor do I have a deep understanding of related jargon yet. Recently I was able to root my phone using jrkruse's method (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). I then wanted to flash a new ROM - Resurrection Remix MM in particular. Through some research this seemed the best to my needs.
I understood that to do so I needed to first unlock my bootlader. So to do so I followed GeTex's post at http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909. I followed Method 1. All was well until the step of installiong Bootloader_Unlock_Safestrap.apk to my phone. After doing that and installing safestrap again like the guide said, I went to reboot my phone into recovery mode, however, initially there was only a black screen. Then, a message told me that Safestrap was disabled and gave me the options of recovery or allowing to continue. Here is a photograph of the screen (found online, not my own imagehttp://img.wonderhowto.com/img/99/57/63530107864095/0/install-custom-recovery-new-rom-your-bootloader-locked-samsung-galaxy-s4.w1456.jpg) Tapping "recovery" brought me to Safestrap and tapping "continue" made the screen black again - no Samsung or Verizon load screen followed.
Thinking that maybe this was normal, and that I had to flash one of the safestrap bootloader unlocks, I flashed SafeStrap_PD1_Bootloader_Unlock_AIO.zip as the phone was in safestrap. After that, any way of starting up my phone showed me a small message in red at the top of my screen saying my kernel was bad or broken (sorry I don't know the message verbatim - I should, but it was a while ago and I was in a hurry to have a functioning phone ASAP for work and was immediately concerned with unbricking my phone rather) a warning sign (big triangle with a !) telling me to use VZW software repair.
If anyone can pick out specifically where I went wrong, that would be great. However, as I'm a noob and there's a lot of room for error, that may be easier said than done.
It would also be helpful if someone could tell me (or link me guides) how to set up Resurrection Remix (or any other great ROM you would recommend) on an S5 G-9000V.
Also, any general advice for a noobie looking to optimize his Android would be greatly appreciated.
Thanks! Love this community for how quickly and how well they help out people with troubles like this
Bumping this, looking for help.
Would love some tips, even if they're simple general direction on how to set up this rom.
Thanks all!
jd13 said:
Bumping this, looking for help.
Would love some tips, even if they're simple general direction on how to set up this rom.
Thanks all!
Click to expand...
Click to collapse
After you have unlocked your bootloader, you should just flash the new recovery (I use TWRP) using Odin software. Once TWRP recovery is installed, boot to TWRP recovery and flash RR RoM. Just follow the RR RoM thread and choose Verizon variance.
I don't use safestrap anymore once I were able to unlock my bootloader. Just make sure that your bootloader IS IN FACT UNLOCK, before you can flasH TWRP.
johnnybg00d said:
After you have unlocked your bootloader, you should just flash the new recovery (I use TWRP) using Odin software. Once TWRP recovery is installed, boot to TWRP recovery and flash RR RoM. Just follow the RR RoM thread and choose Verizon variance.
I don't use safestrap anymore once I were able to unlock my bootloader. Just make sure that your bootloader IS IN FACT UNLOCK, before you can flasH TWRP.
Click to expand...
Click to collapse
Thanks a lot for your help, but I just did some more research and found out that my eMMC was in fact Toshiba, while I had originally thought it was Samsung. Oh well! Guess I'll stick to TW based ROMs on my firmware. I was thinking of going with MOAR Lollipop.
Hello can any one help. How can I purchase a z1compact from eBay with a unlockable boot loader. What am I looking for? eg. an international version, or one from a specific region. I have one already but the bootloader unlock allowed =no. It is rooted and I have twrp recovery but I want to upgrade or flash a android 7.0 custom rom .Any solutions for that. I don't want to end up with two phones with seem problem.
senortech said:
Hello can any one help. How can I purchase a z1compact from eBay with a unlockable boot loader. What am I looking for? eg. an international version, or one from a specific region. I have one already but the bootloader unlock allowed =no. It is rooted and I have twrp recovery but I want to upgrade or flash a android 7.0 custom rom .Any solutions for that. I don't want to end up with two phones with seem problem.
Click to expand...
Click to collapse
I can't answer your question directly. It's more an alternative solution which I think should work (at least you can try...).
If you've got a working TWRP you should be fine. Installing AICP/lineage/whatever shouldn't be a problem then, even with a locked BL.
Just boot to TWRP, wipe /data, /system and caches and install the firmware you'd like to have.
Only downside: If something breaks and you can't even enter TWRP you have to use the sony repair/flashtool and reinstall stock. Then repeat the rooting + TWRP installing stuff...
Make sure you've installed a recent (and working) TWRP version as for installing ROM's starting from oreo you need at least TWRP 3.2.x if I remember correctly.
BTW: Why do you want to install 7.0 / nougat? It's outdated and not updated anymore. I'd suggest using android 9
AICP 14
LineageOS 16
or android 8
LineageOS 15.1
or even android 5
LineageOS 12.1
These builds are updated at least monthly. And the first three of them also provide OTA update support which makes things very comfortable.
Thanks so much for your reply. Although I'll say it left me surprised. After researching the last couple of days ,even here on this site I was lead to believe that an unlocked bootloader was absolutely essential to flash a custom rom not based on stock firmware much less upgrade to a later version of android. However I am more than willing to take your word for it seeing that you are one of the modders for the Rom I would like to try "LoS 15 Oreo". I fully understand that the risk is totally mine. A further question, I currently run andriod 5.1.1 with dual custom recovery twrp and cwm, how do I update my current twrp version 2 . Something to the latest recommended. Do I flash the new zip with my current twrp recovery ?
senortech said:
Thanks so much for your reply. Although I'll say it left me surprised. After researching the last couple of days ,even here on this site I was lead to believe that an unlocked bootloader was absolutely essential to flash a custom rom not based on stock firmware much less upgrade to a later version of android. However I am more than willing to take your word for it seeing that you are one of the modders for the Rom I would like to try "LoS 15 Oreo". I fully understand that the risk is totally mine. A further question, I currently run andriod 5.1.1 with dual custom recovery twrp and cwm, how do I update my current twrp version 2 . Something to the latest recommended. Do I flash the new zip with my current twrp recovery ?
Click to expand...
Click to collapse
Well, at first I have to apologize for the "optimistic" answer. There's one "small" detail I forgot about. It's the boot.img signature which may cause problems. However I don't know if Sony was enforcing the verified boot / signature checking even with android L. This would mean the bootloader checks, if the boot.img was signed with Sony keys - if not: it'll enter a bootloop (or doesn't turn on at all). Unlocking the bootloader then allows you to also boot unsigned images.
But I didn't tried booting custom images with locked BL on my own
So I guess it's a try and error thing here... Most likely you'll end up unsuccessfully
However you can still give it a try. Can you post the output of
Code:
cat /proc/partitions
when you're in recovery? (TWRP has an inbuilt terminal, or you can use adb shell).
At first you need an independent recovery - which means it can boot up without needing the stock boot.img. That's your current configuration: original sony kernel boots up and you decide which ramdisk it should load by pressing vol+/-.
That's why it's actually no real recovery. If something in boot.img breaks you won't be able to reach recovery anymore.
So I think of following steps now:
Make sure you've installed the latest sony firmware
install the bootloader patch from @munjeni (he also states you need a unlockes BL, so it's not really promising Maybe he can jump in and give further clarification here?)
install TWRP (e.g. this) with dd like this (change your inputfile accordingly):
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
if you strike it lucky you'll be able to boot into the new real recovery with: poweroff device; hold VOL down and power until vibration; release power but keep holding VOL down until TWRP screen comes up (needs ~10 seconds or so)
To be honest: I lost my confidence a bit. Maybe buying a device with unlockable BL is the way to go. I suppose the devices sold with contracts by big carriers like Vodafone or Telekom (however they are called in your country) DON'T have unlockable BL's. So devices without a simlock may have a good chance to be unlockable. However - that's just a guess.
Well doing some research found an interesting Movistar forum stuff : if you unlock your phone ( free to use whatever SIM you want ) then its possible to change "bootloader allowed : no to yes" . At least thats what the spanish thread says ( https://comunidad.movistar.es/t5/So...not-allowed/m-p/2404928/highlight/true#M26138 )
1- After make your phone SIMfree it says to do a factory reset and check if allowed : yes
2- Also says that you need to send phone to sony tech fisic store
3- Or using Sony pc companion
I am not sure why it says that need to deliver the phone to sony store since online bootloader is kids game, but thats what the thread says
Finally, if you want to buy a new one, all unlocked phones ( no carrier ) will let you unlock bootloader ...... 99% sure :fingers-crossed:
ps : my english is horrible, I hope you understand it
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