First problem is that there are are about 10 different names for the phone I'm using. Blade V20 Smart, Blade V20, ZTE 2050, and the list goes on. My actual phone says it is the ZTE 2050. But I cannot find any help for rooting and installing custom recovery online when I enter that. So, I started trying the methods I found under the other names. Finally I have been able to achieve root. Problem is, I still cannot install recovery. I have tried using different tools that claim to port custom recovery using my stock recovery, I have downloaded and installed twrp recovery from various other labels of the same phone, I have used SPFT and fastboot, and the list goes on of other things I have tried as well. Can anyone help figure out what is going on? The only way I can boot into recovery is through Magisk. If I try to use the normal method of volume down and power, it simply boots to a black screen that with the orange unlocked bootloader warning. To achieve root I had to downgrade from Android 10, back down to Android 9. When I open Magisk, it says there is no ramdisk but has SAR from Samsung. But as I watch the patching script, it says it is patching ramdisk. Adding to my confusion is when the phone was on Android 10, it said I had ramdisk, but no SAR. Also, even though I have root, when I open my file manager and try to get into the root files, it tells me that they don't exist. It's been several years since I've played with stuff and I am completely lost. Can anyone help point me in the right direction or tell me what I might possibly be doing wrong? Thanks in advance.
Related
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
Im just recently bought this device from a friend so i could ditch my broken Galaxy S2. I just need a good looking phone that does the job without lag and is unrestricted in terms of access which means, i want to be able to install custom roms. Oh and screen size is also important to me.
I however am NOT new to the android modding community and ive created a couple of things myself, but for every new phone im forced to relearn almost everything. Aaand boy did this phone land me in a very awkward situation that 6 hours of pure googling, experimenting with different firmwares etc, couldn't fix.
I learned the hard way that i have a JDI display and that its less common than the other one. I followed some simple guide where i was on 4.4.2 already and basically rooted it with ioroot. Now the only method ive found so far to install a recovery on a stock 4.4.2 lg g2 (d802) 32gb edition is by using a certain application called autorec.
I did try it. It seemed to work. No error. However, to my suprise i found out i had a screen that was completely covered in white/green/blue lines. By how the procedure was supposed to go, the app was supposed to boot me to twrp recovery after the install. And im guessing it did because i could feel the vibrations of the different buttons as i tapped the screen on different places. But i couldnt see what i was doing.
I researched into it and found out about the whole jdi thing. Found a Europe Open D80230b.kdz firmware and flashed it but just blindly booting the phone into download mode tho it was still covered in lines and couldnt see a thing. Once it was done, the phone booted and the LG logo was visible and the lines started to decay and slowly dissapeared. after about an hour, they were totally gone.
Now to the main issue im having and the question i have for you if can help me.
How do i go about installing a recovery that works (that i can actually see) so that i may access the menu in order to install this ldi kernel zip? Ive tried installing a recovery with the one click root + recovery script by somboons.
It gets stuck on this part "author : blog.lvu.kr
SPECIAL COMMAND : ENTER,LEAVE
#"
I basically CANT install a recovery on 5.0.2 with the one click script because it gets stuck. Cant root it either with SRKTools. I CANT install recovery on 4.4.2 with Autorec because my phone gets covered in white lines and i cant see what im doing. I tried installing a certain jellybean firmware to go from there. Using the open europe d802 jellybean firmware wasnt possible because the flash tool kept giving me disconnection errors. So i tried installing a open polish d802 firmware. got white lines so that is a no go too. One thing that i suprisingly can do. I can root it using the LG one click root method 1.3. The 1.2 script cmd version doesnt work. It gets stuck on the special command # part, however the graphical interface version roots without any problems.
ive found the recovery im gonna use which is supposedly nicer to jdi screen that, according to the creator, is supposed to generate less heat on the jdi screen. however i dont know how im supposed to install it. For now im gonna use the 5.0.2 open europe d80230b firmware til i find a solution. All im trying to accomplish here is to successfully install CloudyG2 3.3. And open the doors for a potential cm13 install.
Finally reached recovery by using this app.
https://play.google.com/store/apps/details?id=wli.areclp802
Read description on whats required if you intend to try it yourself. It requires root and some SuperSU option unchecked. Worked perfectly on my LG G2(D802) with JDI display that ran 5.0.2 lollipop stock firmware 30d. It will flash recovery successfully but then i had to manually press the button inside the app for it to boot me to the recovery. its the newest twrp 3.0 recovery. Now im happily running CloudyG2 3.3
This question thread can be closed now!
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
bump:fingers-crossed:
megamind994 said:
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
Click to expand...
Click to collapse
did u ever get it figured out? i am in the same boat grr
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
megamind994 said:
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
Click to expand...
Click to collapse
thanks
Yeah. Sorry for the late reply given you guys found the fix by now, but yes, generally with the sort of severe mishaps from editing or accidental deletion of certain system files or directories, sometimes a dirty flash or even a totally clean flash after performing data ave system partition wipes, will just not fix or restore the device.
You would then need to do a complete stock image reflash either using LGUP or the official LG software recovery tool. If you know what you're doing, you could skip over reflashing stock in its entirety, if say you know the problem has only to do with a particular protected partition like modem, EFS, etc. But generally good practice to just recover all the stock partitions, refresh the device software to factory conditions, reflash your bootloader and recovery images, root STOCK or install custom ROM, so on and so forth.
If you're a frequently curious tinkerer, making backups will be crucial to your sanity.
Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.
Can someone please help me? I don't know what more to do. Please.
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.
I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.
Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!
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