Convert from "Roth Diagnostics" to Regular Shield(STOCK)? - Shield Q&A

I recently got a Shield for $85 because the ebay seller said it was missing apps.
I've got it rooted with the custom towelroot, but i'd like to use a recovery and restore to normal shield firmware instead of the Diagnostics it's on.
Basicaly, it's The shield, stripped of google services, & OTA update, with "Input Viewer," and "Mfg Test" added.
It's on 4.2.1 Build- rothdiag-userdebug 4.2.1 JOP40D 7947_223.4068 test-keys
Kernel- 3.4.10-g6f428d8 [email protected] #1 Tue Aug 27 16:37:56 PDT 2013
Model number is Roth Diagnostics
It runs everything fine, I just need to put it to stock shield as a normal user would have, since I can't stream from my laptop to it with how it's setup now (It has tegra zone, but won't detect my pc)

I just recently acquired a Shield Portable as well, and of course, now I’m doing the research to get all I can from the device.
When I got mine, I immediately unlocked and rooted it, installed TWRP recovery, flashed the Roth 1.6 updates, and flashed CM12.1 Nightly with Open GApps ARM 5.1 Micro. All went well, and works fine, though I’m still uncertain as to the best recipe to bake my Shield with.
As for your question, how to get back to stock, well, from what I did, it’s actually quite simple.
Take my method with caution!! I’m still new to the Shield, and whenever flashing a device you always run the risk of bricking, so be damn sure you know the do’s and don’ts. Also, this method should completely return you to stock, including removing any custom recovery you installed.
Keep in mind, when I flashed back to stock, my Shields bootloader was unlocked, had a custom recovery, and CM12.1 installed. I’m not quite sure if this makes a difference, I’m just pointing out my configuration at the time.
One last thing, I flashed from a Windows 10 rig, and my instructions will be noob friendly for those that stumble upon this post and need to know what to do from the beginning.
1. Connect your Shield to your PC, and boot your Shield into Fastboot mode by simultaneously pressing the Back + Home + Shield button. Your shield will boot to a black screen displaying menu options such as Continue, Restart Bootloader, Recovery Mode, among some other options.
2. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) Now, make sure your Shield can be seen on your PC.
In Windows, go into Device Manger, and if there’s an exclamation point next to your Nvidia Shield device (it might read Fastboot device or Roth), then you’ll need to fix that problem so Windows installs the proper drivers.
I’m running Windows 10, and the following method worked for me to get the proper driver installed.
Right click Nvidia device in Device Manager then click the following... Update Driver > Browse My Computer for driver software > Let me pick from a list of device drivers on my computer > Android Device > Android Composite ADB Interface > Click Next and that should install the driver.
3. (SKIP IF SHIELD DRIVERS ARE PROPERLY INSTALLED ON PC) If you have the driver properly installed, you can verify Windows sees your shield by running fastboot devices.
To do this, one method is to download Shield Root files courtesy of CriticalComposer from this link https://www.dropbox.com/s/mr8ro1gx2axynwg/Shield Root.zip
Extract the file, go into Shield > Shield Root. The ABD files are located there.
Press the shift key on your PC keyboard as you right click in that folder, then select “Open command window here”. This will open a command prompt pointing to the Shield Root folder.
Now type fastboot devices in the command prompt and press enter. If Windows sees your Nvidia Shield a serial number will appear. If nothing appears, that means you may not have your Nvidia driver properly installed or in Fastboot Mode.
4. Now that your Shield is connected to your PC and can be seen by Windows, you’ll need to download the Stock image from Nvidia.
Here’s the link https://developer.nvidia.com/gameworksdownload
You might have to create an account to download.
I believe NVIDIA SHIELD Portable Recovery OS Image Update 106 is the latest as of this post. Download it and extract it to your PC.
5. (THIS STEP STARTS THE FLASHING PROCESS) Open the extracted folder, and simply double click flash-all.bat. That should start the flashing process, and it will flash everything needed to return to stock. If it doesn’t start the flashing process, re-check to ensure Windows has the proper drivers installed.
6. Once it completes flashing it will display “press any key to exit” in the DOS box, do that, then reboot your Shield.
7. When your Shield reboots, it should display a screen with NVIDIA and its logo, and might take up to 5 minutes to finish booting.
8. Hopefully all goes well, and you should now be back at stock with Lollipop 5.1 and Nvidia update 106.

Same Situation Different Issue??? NoWiFi??
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.

simmpledeals said:
I have the exact same situation as the OP but i cannot get the WiFi to work at all, I tried flashing every recovery ROM from the site from factory image to update 106, still no WiFi,I have also tried rooting and installing CM but the issue is still present. i have found other posts about the same problem but most posts only talk about the K1 tablet, I tried restarting over and over again, i have tried factory reset, I feel like i have tried just about everything, if anyone has better knowledge and cant step me through it that would be much appreciated because i was told the item only had apps missing and i tried to return it but was denied somehow so i'm stuck figuring it out, everything else works on the shield portable perfectly and it looks new, i just feel its only half a shield with no internet.
EDIT:
Also i just used foxfi on my phone and paired them and when i enable "use for internet access" It enables and then automatically disables, So it seems like a software issue, i'm still clueless as what to do, i assume if i could find the system apk for WiFi i could reinstall it but i can't find it.
Click to expand...
Click to collapse
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.

loismustdie555 said:
I've had this issue before back in the days when the Xperia Play was still a thing. The problem (if I remember correctly) was the radio.img needed reflashed.
You'll have to get the latest one and put the device in fastboot mode, and do
fastboot oem unlock
fastboot flash radio radio.img
in the cmd prompt.
Click to expand...
Click to collapse
I know how the process works but I tried so many times and searched all over and I cannot find a radio.img for this device, do you know how or where I can find it, it would be amazing to get this too work at its full capability, cause it pretty much sucks without wifi.

Sorry to ask a dumb question but, why not restore the sock image from Nvidia's site?
It sounds like you all bought failed attempts to use CM.
Sent from my HTC One_M8 using Tapatalk

Related

Officially desperate. Please help. Will pay in form of just about anything.

Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.
first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2
dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.
You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.
Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!
I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus

[Q] Bricked tf300t, replaced motherboard...

So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
n3tm0nk said:
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
Click to expand...
Click to collapse
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
transformer pad tf300t
graphdarnell said:
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
Click to expand...
Click to collapse
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
n3tm0nk said:
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
Click to expand...
Click to collapse
What happens when you follow the directions here by Tobdaryl (reverting back to official 104220 where 4.2 is encrypted)? Short of returning the MB, ain't much you can do hanging on to it, right? I've done this with my tab on official 4.2, and it went back to official 104220 without problems. Must warn you though, it took quite a few minutes and at times, looked as if it's frozen. Just leave it on till it says it's done. Patience counts.

Help! Can't flash stock!

Just bought a used Nvidia Shield (1st gen, not the k1). It was already rooted and I wanted a clean install. Wiped the data with TWRP, downloaded the stock zip from Nvidia and tried to install it in TWRP. No luck, I get "Failed to sysMapFile 'sdcard/longzipname.zip' Error flashing zip..."
So I tried to do it manually with fastboot. Have no problem doing any adb commands, but fastboot does nothing, just always 'waiting on devices'. My device shows up when doing 'adb devices' but not 'fastboot devices'.
Something tells me there could be a driver issue on my computer (Windows 10), but Windows won't let me update the drivers I downloaded from Nvidia, it always automatically installs its defaults.
I'm bootlooped now, but can get into TWRP and the bootloader. Halp!
UPDATE: New problem. Got the driver deal resolved (see below). Got stock reflashed onto the device, booted back and began going through first time set up process. While connecting to my wifi (the first part of the setup process), everything went black. I saw TWRP come on the screen for just a second along with a script of some kind (didn't get a chance to see what it was), and everything went black again. Now my device will not turn at all. Can't boot into bootloader either. Device will charge when plugged in (there's a light). Additionally, the computer does recognize it (APX Device?). I'm still researching at the moment, but any help would be appreciated.
Did you flash newsest firmware? You have the links kn the CM thread
I did download the latest. I do want to reiterate, I'm not trying to flash CM, but stock.
Got the driver thing sorted it seems. When plugged in and in fastboot, I needed to update the fastboot driver in the device manager. flashall.bat didn't seem to want to work, but manually flashing the items seems to doing things. Working on it and hoping!
In case anyone else needs this in the future, I could run adb commands no problem, but couldn't do anything with fastboot. I downloaded the Nvidia drivers from their website, but the Device Manager wouldn't let me update the drivers for my Shield tablet. How I fixed: when in fastboot on the tablet, I pulled up my Device Manager. There was one specifically for fastboot and (surprise) the driver was no good. Updating that one with the ones I downloaded from Nvidia did the trick.
But I now have a new problem. Edited first post.
sounds like you bought a recalled tablet. If the seller did not tell you that then you need to chat with him.
This is what I was worried about. There's a thread in here to determine if your Shield tablet is slated for the kill switch update. It looks like mine was. Then I found the Nvidia recall website and it does appear that a claim has already been submitted on this tablet. So if I understand that process correctly, whenever the claim was done by whatever previous owner, Nvidia activated their kill switch. I think maybe the fact that it was rooted and didn't have the latest update protected it. Until I flashed the latest stock. The moment it connected to my WiFi, boom.
Is there anyway to fix the bootloader (which appears to be corrupted)? I found threads where people were talking about NVflash, but no real specifics.
True, lots of people come in and say they can fix but never do. I think they hope someone else will fix for them.
In reality it is also posted many times that this is not fixable except by nvidia itself.

TWRP Bootloop [SOLVED]

Hi all
I've had my Tf700 for a long time now. I've had it unlocked and rooted and had CROMBi before trying OMNIRom and then finally moved to KatKiss7.1 last year. All was well until today when, having enabled screen rotation, the background went a strange looking pink colour and would flicker back and forth to black. Then the WiFi started to misbehave so I rebooted it. But instead of rebooting, it just went into a bootloop.
I used power + VolumeDown to access the recovery mode and tried to get to TWRP (2.8.7.4) via the RCK option but without any luck. At that stage, all it was doing was resuming the loop. I tried booting into Android but got the same result. I tried for TWRP a few times and it always failed.
My next move was the Wipe Data option. Turned out to be a bad one. I hadn't done anything with the device in so long that I forgot about the "don't use the Wipe Data" instruction and I didn't read up before doing anything else. The device rebooted itself and then appeared to be going into TWRP - I could see the logo coming up - but my hope was short-lived as the device then proceeded to go into a bootloop where it displays the TWRP splash screen, but then reboots.
About the only thing I seem to be able to do is access APX, but I didn't know about APX or NVFlash until today when I started trying to read everything to do with anything that might help.
I run Linux on my PCs and have installed ADB so that I can try to use fastboot or adb. Neither seem to work in that nothing shows up when issuing either "fastboot devices" or "adb devices". But on a more basic level, nothing shows up in lsusb. The mouse is listed, as is my card-reader, but the TF700 isn't. The thing is, I haven't connected the device to a PC in a long time and the last time, it was windows, so I can't say for sure that the PC is definitely seeing it or not.
And so to my questions:
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup?
(I've seen instructions for the TF201, but can't see anything for the TF700)
Any help would be really appreciated.
With thanks,
Scouser27
I don't like the sound of this. This "background went a strange looking pink colour and would flicker back and forth to black" business makes me suspect a hardware failure. Maybe something got fried on the board - don't know.
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
Click to expand...
Click to collapse
Yes, it should, something like this:
Code:
...
Bus 003 Device 009: ID 0bda:57af Realtek Semiconductor Corp.
Bus 003 Device 016: ID 0b05:4d01 ASUSTek Computer, Inc. Transformer Prime TF201 (debug mode)
Windows is not going to help you. If it doesn't connect in Linux it definitely won't in Windows....
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
Click to expand...
Click to collapse
Not unless you get a connection in either fastboot or adb
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup? (I've seen instructions for the TF201, but can't see anything for the TF700)
Click to expand...
Click to collapse
No, nvflash files are device specific
If you cannot get it to boot into fastboot or get an adb connection - however briefly - it is a brick.
Install Hardinfo in Linux - it is very similar to Windows Device Manager - and open the USB page. Then reboot into TWRP. If you are lucky you may get a few seconds before TWRP loops where the PC has an adb connection and sees the tablet. If that works, follow this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Still a tiny chance but better than nothing.
If bootit.ko kicks it into the bootloader and you get fastboot you can reflash the recovery, format data in fastboot and all that good stuff.
But my guess is: No dice
Try it anyway - good practice.
I still have a couple of TF700 lying around, one with a so so screen. If you want it, you can have it for the cost of shipping. You can either swap the screens or m-boards...
PM me if you want to go that route.
Good luck
Update
Thought I'd post something in case it's useful to anyone having similar trouble to what I described. This applies to my instance of TWRP booting in a loop and never exiting until the battery was flat.
Ensure your cable is working correctly.
If it's not, you won't see anything on your pc. (I use linux and nothing was showing up in lsusb or dmesg)
If this is the case, borrow a cable if you can or invest in one. I did - best 5 Euro ever.
Get the bootit.ko file that's mentioned in a few places such as here.
While you're getting that file, read the instructions there a few times and also have a look at the details over at this page (same one @berndblb links above)
Connect your tablet and boot it. As soon as you see the TWRP logo, it's time to try to run commands.
If you use linux, you can issue all commands at once like this:
Code:
sudo adb devices; sudo adb push bootit.ko / ; sudo adb shell insmod bootit.ko
Note the "/" after "push bootit.ko" - that's not a typo. If you leave it out, it won't work.
I don't know if sudo was strictly needed, but I wanted it to work and it didn't cause any trouble.
I haven't used Windows in a long time so I don't remember if you can do the same, but you could put the various adb commands into a batch file and run that. Don't forget to drop the sudo.
If it has worked, the tablet will reboot. You should now be able to get back to the bootloader.
Follow the fastboot erase instructions at this thread.
I found it useful to write the commands as
Code:
fastboot -i 0x0b05 erase boot
The last version of TWRP that I was using was KANG TWRP
I downloaded that, extracted the blob file and flashed it:
Code:
fastboot -i 0x0b05 flash recovery boot.blob
I used that because I wanted to install TimDuru's KatKiss 7, but you could presumably install whatever Recovery you wanted and proceed as normal.
And that's it. I flashed KatKiss7 and SU and all was well again:laugh:
Big thanks go to @berndblb for his help on this - If, like me, you didn't read his posts before, you really need to read them now. And maybe, just maybe, you'll be able to recover.
Thanks to all other contributors whose post's I've linked or whose work contributes to this solution - you've all just saved me having to buy a new tablet. Nice one!:victory:

LG V20 H918 T-Mobile Guide from out-of-the box --> 20H, TWRP, Root

hi,
this is a guide for real helpless people, that got a V20 H918 T-Mobile out of the box and have no idea
what to do, to get TWRP and root. and since on this phone its a REAL hard odyssee if youre not a pro,
and you dont want to spend days and weeks to pick up countless small puzzlepieces to finally get all together up and running, i decided to write this guide. im no pro myself, but with countless hours of reading and try and error, misery, headaches and brainpain, i managed to get this thing running all right with working downloadmode,
newest TWRP-version and 20H oreo 8.0
so far, everything seems working good. ill play around with this version and if i encounter some crap, i will edit this guide later. sadly most "newbie-guides" here, are from pros for advanced users with decent knowledge. so when u start from zero, you dont understand half of what is written. thats why i will keep this guide as simple as possible, with some side explanations. its a lot to read and a lot to do, but this way works!
what we have before starting:
a V20 H918 t-mobile 20H oreo 8.0 with bootloader locked. simply a crippled standard phone.
what we will have after this guide:
a V20 H918 t-mobile 20H oreo 8.0 rooted, with unlocked bootloader, working downloadmode,
and newest TWRP-version.
with twrp u can backup your whole system "as it is", means u fukk up your phone, simply go to twrp-recovery, restore your backup and you have your phone up and running 100% as before all went down the drain. simply and easy. just like a new installation of win10, but in 5 minutes. u can flash custom roms, kernels etc., install all kind of stuff, no need to pay for apps anymore, get rid of obnoxious bloatware, just 100% freedom and the full potential with the V20 (which is the last phone of its kind with exchangable battery, which is why i got myself 3pcs of it )
sidenote: get yourself some extra protection foils so u can change from time to time.
also get yourself 1 or 2 10000mah powerbatterys from aliexpress (perfine) with protective rubbercase, of course, they dont have the printed-on mah, but at least a considerable amount, so that your phone will last at least 3-6 days. my V10 lastet 11 days normal usage with zerolemon powerbattery. unfortunately, these retards refuse to send to europe, and as far as i know, theyre not producing for LG phones anymore, so aliexpress/perfine is whats left.
the rubbercase gives the phone a superior protection, adds a serious amount of weight and will stick in your hand like glue. it is by far less likely to drop out of your hand like these glass-phones for imbeciles. and if it drops, the rubbercase grants excellent protection. my V10 dropped countless times, still working perfect.
but lets get to the guide now.
at first, we will unlock the bootloader. without it, you wont be able to do anything.
unfortunately, LG produces great phones (with great audio!) but terrorizes the users with their strict anti-root attitude. it seems it gets harder everytime to root and unlock the bootloader. i remember back in the days old samsung devices, had been rooted in no time. this one here cost me about 2 weeks.
on this phone, u simply cant hook it up to the pc, and unlock the bootloader with adb. it will be recognized by the pc, but as soon as u enter fastboot, nothing will happen, no command works.
the solution is a FWUL (forget windows use linux) usb-bootstick, with that u boot your
pc into a custom linux (i think) only here u have full access to your phone via fastboot and can unlock the bootloader in no time. it will not work on win10 !
- first, get rufus, a win10 tool, with that u can create boot-usb-sticks.
https://rufus.akeo.ie/
- then get the linux FWUL image (only 15GB version is still up)
https://androidfilehost.com/?w=files&flid=214529
- unzip the linux image to your c drive or your desktop.
- start rufus and select your usb-stick (it should be 30gb+ in size)
be carefull not to chose any other drive or stick (it will get erased completely), better double check.
- select the image you just unziped. (i use 7zip for unzipping)
- leave all other options as they are, press start. when dialog-box pops up, chose DD-mode !
- now waste some time, as it takes a long time to create the bootstick (in my case about 30min)
- when the stick is ready, in my case it couldnt be recognized anymore in win10, its just a raw-drive, that cant be
opened. thats allright. dont worry
- now close down all applications running and insert the created bootstick. (at this time u might consider using a
separate laptop, so you can follow this guide here at pc and use the laptop with linux running, thats what i did)
restart your pc, hit F2 or F8 oder DEL or whatever to enter bios.
select the created stick as bootpriority nr1. so that the system will use this stick as
the first bootmedium to boot from.
- u get to a screen with 9 bootoptions to chose from. chose the first one. it should now boot into linux.
when password request pops up, enter: linux
- u reach the "desktop"
connect your LG V20 H918 20H via usb-c to the pc, which has linux running, make sure that
developer options are unlocked, OEM-unlock and USB-debugging is enabled and u chose picture transfer protocol
(PTP) as transfer-protocol (also in developer options). if PTP doesnt work, try media transfer protocol.
watch your V20, at some point it will ask for confirmation of connection , click OK.
in linux, click on the up-arrow in the most downleft corner and chose "terminal emulator", which is
a pendant to windows shell/command-line.
- here you can execute the adb commands.
first, check if your V20 has been recognized by your pc with linux running.
type: adb devices
it should appear a message like:
* daemon started successfully *
LGH9182bfblablabla device
that means, that your V20 has been recognized correctly. now you can reboot it in fastboot mode.
type: adb reboot bootloader
your V20 screen goes black and seconds after, it restarts in bootloader mode ready for unlocking.
you might get a red warning that your warranty is void if bootloader is unlocked. cool.
type: fastboot oem unlock
wait for response, your bootloader is now unlocked.
u can check by typing: fastboot getvar unlocked
it should say: yes.
the bootloader is now unlocked.
now we will replace the standard recovery with twrp on the phone.
this step will be a little confusing and complicate, just follow the steps, and it will work.
since we cant flash twrp with adb, we have to use the linux bootstick again.
but before, we have to downgrade the 20H version to 10P, bcuz the next stepp will not work with 20H !
so you get the following:
DOWNLOAD H91810P KDZ FILE
https://androidfilehost.com/?w=files&flid=282709
after that, download LGUP (the LG tool for downgrading from 20H to 10P)
and uppercut (dont know what uppercut is for, i just used it instead of running LGUP directly and it worked. its supposed to recognize the phone/driver automatically)
http://downloads.codefi.re/autoprime...sh_Tools/LGUP/
and download the recent LG-usb drivers.
http://tool.cdn.gdms.lge.com/dn/down...=UW00120120425
install LGUP, uppercut and usb-drivers.
connect ur phone to pc in download mode.
turn of phone, press and hold vol.UP button and connect usb cable, small message appears, phone is now in download-mode and waiting.
now run uppercut and hope, that ur phone will be recognized. if not, think about, what kind of restrictions u did to ur system, like OnO-shutup or xpantispy (both great programs to keep win10 from calling home to scum gates) or whatever. in my case, it ONLY worked, after i reset the OnOshutup settings to recommended. so the phone get recognized correctly in LGUP (if not, try laptop or different pc), select upgrade and select the downloaded 10p KDZ file. press start or go, and wait until the procedure is finished.
now your phone is downgraded to 10p.
now we go back to linux, we connect the phone in downloadmode with the pc/laptop where linux is running,
(turn phone off, hold volUP, connect usb-c-cable with linux-pc/laptop, phone will start in download-mode.)
make sure, your laptop/pc has internetaccess.
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode. why? i dont know, thats the way it worked for me.
we dont want twrp onto downloadmode, since twrp is a recovery. so the next step is, to flash the newest twrp version for H918 to recovery. at first, we will gather all neccessary downloads, after that, we will flash them one by one. that way, you dont have to get your micro-sd card out of your phone again and again. we put all together on the card, put the card in your phone and we are almost done. for now, have your micro-sdcard connected
with your pc and download the following:
twrp-3.4.0-1-h918.img
from
https://dl.twrp.me/h918/twrp-3.4.0-1-h918.img.html
and put this .img file on micro-sd card.
then download (and put on sd-card):
MAGISK ZIP DOWNLOAD (for root)
https://github.com/topjohnwu/Magisk/...gisk-v16.0.zip
then download original 20H firmware(and put on sd-card)
H918 20H
https://androidfilehost.com/?fid=11410963190603864639
you remember, we have now twrp on downloadmode
for restoring download-mode, download (keep on desktop or c):
H91820h_00_1115.kdz
https://lg-firmwares.com/downloads-file/17076/H91820h_00_1115
then download the firmware extractor:
https://forum.xda-developers.com/attachment.php?attachmentid=3975633&d=1482337024
ok, lets see what we have now:
we have the phone bootloader unlocked and twrp on downloadmode. we can access twrp when we start the phone in downloadmode (hold volUP, and connect usbcable, phone will start now in twrp.)
we dont want twrp on downloadmode, we want twrp as recovery. and we want to restore the original downloadmode. for that we do the following:
unfortunately, the neccessary file for flashing orignal downloadmode is not online anymore, so we have to extract it from the 20H firmware with the firmware extractor (thanks to logical gamer for his guide)
https://forum.xda-developers.com/v20/how-to/guide-h918-restore-laf-partition-t3804728
Extract WindowsLGFirmwareExtract vx.x.x.x. to your desktop, and open it up (preferably in it's own folder).
u might have to install framework 3.5 for it to run.
Select Open across from KDZ/TOT file, and browse to your KDZ (H91820h_00_1115.kdz)
you download previously and double click.
After it loads the kdz check H91820h00.dz, and click Extract KDZ.
Close and re open the program this time Click open across from DZ File in the folder where you placed WindowsLGFirmwareExtract you should see a file called H91820h00.dz Double click to open it.
Check laf_6.bin then click Extract DZ.
put this laf_6.bin on your micro-sdcard. thats your original downloadmode we will flash now.
ok, now we have our micro-sdcard with twrp, magisk, laf_6.bin and H91820h.zip.
put this mirco-sdcard in your phone. start the phone in downloadmode.
it will start in an older twrp-version. in twrp, go to install and select install img
select the twrp 3.4.0.1. img and on the following screen select "recovery"
swipe
this will flash the 3.4.0.1 version of twrp onto recovery.
then go to reboot into recovery. it will now boot into the newly flashed recovery.
then go to wipe, advanced, and select everything EXCEPT micro-sdcard!
this will totally wipe your phone (except twrp), so u can flash the 20H firmware onto a clean phone.
then, go to install, select H91820h.zip. this will flash your original oreo 8.0 firmware.
after that, go to reboot into recovery.
go to install, select magisk. install.
this will root your phone.
after that, reboot into recovery, go to install, select install img, select the laf_6.bin, and select "download"
now the original downloadmode has been restored.
now you can reboot into system, your phone will start as on day1, with new twrp on recovery and root.
i did a complete backup in twrp, so i can get back to a day0 clean install whenever needed. i will do a second backup with twrp with all the stuff installed and working ok and place this on my sd-card. so when things go bad, i always can go back to this state in no time.
congrats, your done. and me too . gonna get a cold one now.
hope this guide will help someone. in case, just drop a like/thanks/or just a short note.
its a long guide, and im no pro, if i made some mistake pls. tell here and i will correct.
thx to all the pro-guys for helping the helpless.
Hi
Im on v20 H918 firmware 10p with bootloader unlocked.
I tried with dirty cow but not works with lafsploit i have a Problem with rufus for create a bootable Linux.
Pendrive is 32 GB i followed your setting but my PC boot only in windows 7.
I succesfully unlocked a h990ds with dirty santa but for this model is not supported.
Can you help me
hi
i tried with dirtycow also, didnt work.
thats why i eventually came to the method i described.
teling by your short description, your next step would be to create a bootable linux-usb-stick, and to find a pc where it will boot correctly. the stick didnt boot on my main pc ( i dont know why, it just canceled with an error),
thats why i had to use the laptop where it worked.
Thanks for the guide man! Very funny and fun to read. I can't wait to turn mine into a 4-day brick like yours. #lastphonewithbatteryrevolution
Sadly I got the dreaded encrypted error at the end though when booting. Everything else worked fine.
After the encrypted error though I formatted and flashed LineageOS 17.1 and then magisk and still keep getting error 1. Even tried Lineage recovery and still same. I think maybe a problem with Magisk 16 itself.
Anyway it works fine just no root.
Edit: Had to flash Magisk 21 and it worked
Thanks for this tutorial. I was able to get my V20 rooted with minimal trouble. The only major trouble was finding a computer that will fully boot into Linux and the only minor issue was locating the UPPERCUT but I was able to find it. Link below.
It's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
UPPERCUT link: UPPERCUT: Add Any LG Device to LGUP for TOT/KDZ Flashing (G4|G5|G6|V10|V20|MORE???) | XDA Developers Forums (xda-developers.com)
MAGISK link: Releases · topjohnwu/Magisk · GitHub
cool, glad this guide helped at least a little bit. my v20 still works great, no issues so far. as a side phone for unwanted persons, i still use my v10 with powerakku and rubbercase "brickstyle" every time i hold a regular phone from other people, it feels weird since these phones weigh like nothing, and i have to focus not to slip it out of my hand. i love my bricks
and by now, about 4 month later, reading this whole guide, to me its still strange and hard to follow. there is no way to get through this without reading everything possible about it and become familiar with all the technical terms.
I have a h918 with an unlocked bootloader and it's downgraded to 10p. The shell script fails everytime to a hash check. I've run it 4 separate times with the hashes being the same every time. So it looks like the file has been updated but the hash hasn't.
I'm coming late to the game and it seems most of the guides are out of date. I'd appreciate any help I can get.
Update: It works fine. This is by far the easiest guide to follow that I've found. Many thanks! I did have to follow xstahsie's tip.
​xstahsie​It's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
I followed the guide after I rooted and installed Lineage OS 18.1. I had to remove LineageOS because it was bad with response, couldn't see hidden wifi, and just ran hot. So I followed your guide and I am in a logo bootloop and get the reminder to lock the bootloader everytime it starts. Any suggestions for getting past the bootloop?
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
memnon79 said:
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
Click to expand...
Click to collapse
You're stuck with it, it's just the way it will be from now on.
memnon79 said:
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
Click to expand...
Click to collapse
I don't remember seeing that. I probably didn't care if it did show up since it was a new install from scratch anyway.
Does encrypting the phone work after following this guide?
hey there, cant help u with the encryption thing cuz thats far beyond my knowledge. some weeks ago my phone dropped, and a tiny crack on the edge appeared. what i didnt know was that this crack is the beginning of the end of the V20. heres the story short: small crack over time leads to a bigger crack, bigger crack multiplies and u have some more cracks covering the whole screen. also the screen can pop off and hanging loose a little. in my case 4-6 weeks and i have to get out phone 2/3 which i am setting up using this guide now. fortunately i left myself a huge pyle of information on how to do this when starting at 0. over time u forget EVERYTHING u have done, so having these infos is hammering.
lucky me did i save my internal memory of phone 1/3 bcuz 30min later the screen was totally fuqqed up, no access no chance of backupping internal memory.
so heres my recommendation:
DONT drop your phone. even in my case with rubber battery case from aliexpress
(perfine "10000"mah) a 50cm drop cracked the edge of the screen. if that happens, backup your internal memory !!! (just do this on a regular base)
when ur screen gets damaged and u cant enter information or cant see anything anymore on the screen ur internal data is lost. so always have ur internal memory backuped!
and great job LG for producing such a huge pyle of ****. one small drop, screen cracked, bravo, last time i ever bought anything from lg. my V10 dropped like a 1000times, nothing, still up and running. v20, drop, 6weeks later, dead. thanks LG the customers all over the world couldnt wait to use these bull**** crackable glass-screens. great job, -1 customer.
I've tried this on two different computers with two different cables in every USB port on the machines but can't get by the Windows portion. I am using UPPERCUT as the windows box/LGUP reports no device found without it...
Of course UPPERCUT drives windows security mad as it's reported as doing bad things but as I'm using an extra win laptop that will be wiped I disable all of that....
I have three different sourced KDZ files as the one linked wasn't initially reporting any mirrors. Eventually a mirror did pop up for it but by then I had downloaded two others -- all were the same size and one of the three reported from LGUP was bad. Every attempt with the other two failed. Invalid Command response came up a few times... sometimes it just failed at around 80+ percent from the PC side which was 99% on the phone's downloader mode progress bar.
It's very frustrating.... I would like to blame windows but there seem to me plenty here with success... any other ideas?
Also... since it got so far, rebooting at this point just goes to the download mode so I might be hosed... I can force it to the fastboot mode and it is still unlocked so I've been trying to install TWRP onto recovery using the linux/android machine but when I type
fastboot flash recovery twrp.img from the directory where twrp was downloaded I get this:
sending recovery --- okay
writing recovery --- failed remote: unknown command
So... any thoughts?
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
dikkbutt said:
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
Click to expand...
Click to collapse
The phone is recognized by the PC, no problem. I do have to use UPPERCUT to get LGUP to recognize it though. The step I'm stuck at is applying the downgrade. It gets to various percentages of done-ness and fails. It got far enough that now my only options on the phone are Download mode or fastboot mode. Problem is, I can't seem to get anything to push to recovery so I assume that it's still not properly downgraded.
I've tried a few different cables and keep in mind the cable I used in the linux adb bootloader step worked fine. I don't entirely know what difference there is between a charging and data cable but I do know the main differences in the steps are a> Windows and b> size of transfer.
weird. since im no pro myself, my ideas are limited on this one. there might be some kind of loose contact at the charging port,
that when the phone is moved just a little it looses connection for a second and reconnects again, had that in the past, so try not to touch the phone at all. did u use the 10p kdz file mentioned before? did u make sure it has been downloaded correctly?
if an error occured and there are some % missing... its like faulty ram, hard to detect.
assuming, u did or did not downgrade to 10p, did u try to continue with the linux-step? ---->
---------------------------
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode
-----------------------------
maybe uppercut/lgup displayed an error message for no reason, and the downgrade itself went through without a problem in the background.
pcs sometimes do weird things.
if nothing works, try setting up win10 and try on a virgin system. in my case, OnOshutup prevented win10 from recognizing the phone,
or try using a 3rd pc from a friend.
i was able to setup my phone 2/3 using this guide in 30min, no problems at all. (i hope i wrote down, how i solved that simlock issue.....)
no matter what causes the problemin ur case , id be interested to hear what it was.
Thanks! Rooted and Unlocked thanks to this guide!
I tried following other guides using UPPERCUT and it fails to downgrade due to Anti Roll Back. How does this relate to this guide since the last thing I want is for (by design) for it to brick the phone. I have yet to find anything specific saying an unlocked bootloader will bypass the anti rollback check.
Hi As a noob does this keep VoLTE? I have followed this guide and backgrade to 10p was perfect! VoLTE working on a phone that was "new" from china. VoLTE did not work on the 20p rom it had. Also does anyone prefer Phoenix591's h918-20g-prerooted rom to the stock one? I have read a lot but am somewhat confused by varying instruction threads. I want to use this as a daily driver. Thanks

Categories

Resources