Database Users

dell streak boots into stock recovery image after successful recover image flash

Ok, so I recently bought a used dell streak off of a friend, and although I like it, I don't like dell's ROM, so my main goal here is to install a custom rom.(Specifically, streakdroid 2.0.0). I was able to root my phone, however I am having issues flashing the recovery image,to get to installing the custom rom. I have tried using rom manager to install clockwork, and when I do it says it installs fine, but when I tell it to reboot into clockwork, the phone just boots up normally into android.When I boot using power + vol up + vol down, it just boots into the stock recovery image. I have also tried using fastboot to flash the recovery image using the clockwork recovery image for the dell streak. The command line says the flash was completed, yet again when I boot into the recovery image it is still the dell streak stock recovery image. I also renamed the file: system/ect/install-recovery.sh to system/ect/install-recovery.sh.bak , following another post's advice, still no luck. I have spent several hours looking on forums on how to fix it, and can't find anyone with this problem on the dell streak. I have also tried to find a way to install a custom ROM without using a recovery image, but haven't been able to do that either. Any help at all would be greatly, greatly appreciated, even a possible tip to point me in the right direction.
For some more info about my phone, I do believe that it might be a corporate edition, I don't know if that would effect anything or not, the other details are as follows:
Model Number : Dell Streak
Android version: 2.2.2
Baseband version: GAUSB1A135100-US
Kernel version: 2.6.32.9-perf
OEM Version: GAUSB1A135100
Build number : 15609

Custom Recovery – Prevent Overwriting on Dell Streak

I already tried the advice given on that link. I can't even get into the custom recovery image even one time.

Also I meant to post this under the Q & A forum, if it's possible for someone to move this post, I'd appreciate it.

damoshemeister said:
I already tried the advice given on that link. I can't even get into the custom recovery image even one time.
Click to expand...
Click to collapse
Rename install-recovery.sh before you install the custom recovery. If the phone boots even once the recovery is over written with the stock recovery if you don't.
Also - there are a bunch of posts that state that ROM Manger does not work on the Streak.

I have also tried using adb to flash the recovery image after renaming the file and immediately booting into the recovery image after installing. Still same issue. Also without even renaming that file, I believe I am still supposed to be able to access the custom recovery image one time.

You do have to enter the stock recovery to get into ClockworkMod or StreakMod. It's what you do after you get into stock recovery that takes you into CM or SM.
Rather than tell you how to do it, I will tell you to READ those guides posted above for the answer. If you don't want to do that, then you should stop messing with something you don't understand before you brick your new toy! The Streak doesn't root, recover, or update ROMs like other Android devices.

Ok, while I did have legitimate issues with rom manager it turns out I had a misunderstanding of how to install streamod,as you pointed out. Please forgive me, I was pouring over a ton of information in a very short amount of time, including being completely new to android, how to install apks from a pc, jailbreaking, using adb fastboot to flash images, all for the first time. I didn't realize you had to update from within the stock recovery image to install streakmod. I appreciate your help allot. I was able to successfully install streakdroid like I wanted, wouldn't have been able to do it without your help. Thanks again.

Glad to see you got it up and going. I can understand your frustration. The first time I played with my Streak I bricked it and took it to someone to fix and he didn't know much more than I did about it.
When I got it back unfixed, I spent several days reading and now consider myself fairly proficient in the art of flashing, although I haven't made any steps into cooking up my own ROMS or all the other technical stuff that goes with what these unselfish guys go through for us.
Have fun!!

damoshemeister said:
Ok, while I did have legitimate issues with rom manager it turns out I had a misunderstanding of how to install streamod,as you pointed out. Please forgive me, I was pouring over a ton of information in a very short amount of time, including being completely new to android, how to install apks from a pc, jailbreaking, using adb fastboot to flash images, all for the first time. I didn't realize you had to update from within the stock recovery image to install streakmod. I appreciate your help allot. I was able to successfully install streakdroid like I wanted, wouldn't have been able to do it without your help. Thanks again.
Click to expand...
Click to collapse
Sorry to have been so tough on you. That's the only way to get people to UNDERSTAND what they are doing to their devices. Now that you found it on your own, you will remember it. You also stumbled onto some other info that may not pertain to your situation now, but you will remember seeing it in the future when you need it!
Here is another concise guide that is excellent and a short read:
http://forum.pocketables.net/showthread.php?t=8715
Good Luck!
kraz

Yea, I definitely understand where you guys are coming from. I do like to try to figure stuff out on my own, and did spend some considerable time reading before I posted on this forum. You guys gave the exact help I was looking for, just a nudge in the right direction. Knowledgeable people can save newbs like me hours in frustration.What threw me off was partially bad luck, but definitely due to incomplete understanding as well. It was the combination of rom manager not working , and me not properly understanding how to install streakmod that led to me thinking it had something to do with the bootloader blocking the recovery image from being flashed. I thought I was gonna end up having to flash the bootloader but definitely didn't want to do this as that would have been very vulnerable to bricking. I read the basics on the different images, and what they did before I tried anything. I did end up at one point with my streak not being able to boot, or update from an update.pkg but since I knew I didn't touch the bootloader, I knew I should be able to get it up and running again. THanks for the link, I will definitely read it.

did u try
flash the clockworkmod or the other recovery image. when the flash was done, it will boot the dell streak, meanwhile, press vol up and down, boot into the recovery mood again, I mean NEVER let the streak boot into the rom afte u flash the image.
Sent from my Dell Streak using XDA App

marvin02 said:
Rename install-recovery.sh before you install the custom recovery. If the phone boots even once the recovery is over written with the stock recovery if you don't.
Also - there are a bunch of posts that state that ROM Manger does not work on the Streak.
Click to expand...
Click to collapse
what do i rename " install-recovery.sh " to?
thanks

I renamed mine to "install-recovery.sh.bak", but I have seen "do-not-install-recovery.sh". In other words, you can rename it to whatever you want.

Strephon Alkhalikoi said:
I renamed mine to "install-recovery.sh.bak", but I have seen "do-not-install-recovery.sh". In other words, you can rename it to whatever you want.
Click to expand...
Click to collapse
every time i try to rename it i get a failed message. any other suggestions? thanks for the help in advanced

You have to mount the internal SD as R/W, it's in R/O it sounds like

trucutu62 said:
every time i try to rename it i get a failed message. any other suggestions? thanks for the help in advanced
Click to expand...
Click to collapse
As noted by the post just prior to this one, the system partition is read-only. You need to change it temporarily to read-write using a file manager that can do the job. I used Super Manager, but there are plenty of root file manager apps on the Market that can do the job.

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

[Q] After 4 1/2 yrs on XDA I am finally stuck! Bricked No download mode, No OS.

Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.

Have you tried to reflash bootloader? If not, do that and reflash cloudy right away

wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?

jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?

euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.

Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?

euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.

My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.

euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...

You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.

Deleted

ZTE Axon 7 USA Bootloader/TWRP/Update Help

So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!

Look in the section rooms, recoveries,etc... look for one the says roms update stock DrakenFX

Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.

Nik2424 said:
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Click to expand...
Click to collapse
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?

ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.

tabletalker7 said:
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
Click to expand...
Click to collapse
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?

ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
If you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.

rczrider said:
if you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
Click to expand...
Click to collapse
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)

ctran1996 said:
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
Click to expand...
Click to collapse
http://www.mediafire.com/file/1jw9b24glt5fd7t/recovery.img put this on your SD card
Boot to TWRP
Push Install (top left)
Push Install Image (bottom right)
find the recovery.img and push it - TWRP will install it for you.
Then reboot into recovery.
You will now be in stock recovery and can use it to install update from SD card and install the B20 firmware from ZTE
BE WARNED - THIS WILL FACTORY RESET YOUR PHONE WHEN YOU ARE DONE!!!!!

DrakenFX said:
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
Click to expand...
Click to collapse
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.

rczrider said:
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
Click to expand...
Click to collapse
That is my problem entirely! I AM tech savvy as I have worked as a Microsoft/VMware Systems engineer for over 20 years and when I try to make heads or tails of doing some of the things necessary to flash a ROM, or root, or unlock the bootloader.... after my eyes glaze over I just stick with Nova Prime and hope the original manufacturers get everything worked out. What's really needed is a well written manual detailing step-by-step basics on what all these various things do as well as how to do them. Then more specific guides on a per phone basis. I know, it's asking too much! LOL :silly:

ctran1996 said:
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Click to expand...
Click to collapse
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.

Thank you this is exactly what I was looking for. However, when I tried this the other day, it reset my phone as planned, but TWRP and bootloader were still on there. Any way of getting them off?
swehes said:
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Click to expand...
Click to collapse

LG V20 H910 Root attempt fail, any plan of recourse?

Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.

First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic

MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?

Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again

MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.

reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.

MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.

Slightly better picture without anything cut off.

reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)

MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol

reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing