Database Info

[UPDATE: 2011.11.16] [RECOVERY] [ROOT] G2x Gingerbread 2.3.3 Stock using Linux

Follow the chronological order of the listed items...
1. Several things to KNOW and DO BEFORE starting:
- this is for Linux (that is your computer OS is Linux based) users ONLY!
- Mac (though UNIX based) and Windows users GO somewhere else!
- this REPLACES your stock recovery w/ clockwork recovery; this is NOT the same as installing rom manager from the market, which won't work on your "unrooted" phone anyway, go ahead try it
- this does NOT root your phone by itself, you need to follow all the directions
- be sure your battery is FULLY CHARGED, even though you'll be removing it for part of the directions
- COPY a rom of your choice to your external sd (ONLY if using ctso's procedure or using the updated clockwork recovery zip file labeled "external," otherwise copy the rom to the internal sd); I recommend CyanogenMod 7.1.0.1 Stable
- follow the procedure listed in #2
2. Procedure for replacing your stock recovery w/ clockwork recovery:
- SEE UPDATE BELOW as this flashes clockwork recovery v3.0.2.4
***********************************************************************************************************************************
The following procedure was provided by xda member ctso...many thanks to him!
***********************************************************************************************************************************
http://forum.xda-developers.com/showthread.php?t=1044326&highlight=recovery
***********************************************************************************************************************************
Again, thanks to ctso for the UNIX terminal bash script! Be sure to THANK him yourself!
***********************************************************************************************************************************
UPDATE:
- download one of the attached clockwork recovery zip files (they include nvflash) below INSTEAD of ctso's "nvflash-recovery.tgz" to have the newer clockwork v4.0.1.5
- use the "external" file to have clockwork read files from your external sd card
- OR use the "internal" file to have clockwork read files from your internal sd card
- THANKS to krylon360 for the updated clockwork
3. Several things to DO AFTER your DONE with the procedure by ctso above:
- reboot device into clockwork recovery by holding the POWER button and VOL DOWN button, let go when you see the word "ANDROID" in the mid-left, upper portion of the screen (occurs after the LG logo appears)
****I can't stress the next 4 items in bold red enough BEFORE proceeding to load your new rom****
***If you don't do this, you're a fool***
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card in #1
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
- your done; you now have "rooted" and "rom'ed" your device!
_____________________________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Do as I say, not as I do
- If I'm coming across as an asshole, it's because I probably am; I'll try to be nicer next time
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
_____________________________________________________________________________________________
- LG P999, Rooted, CyanogenMod v7.1.0.1 Stable
- HP dv7t w/ Debian Linux

interesting
but usability does it actually bring to the phone

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
Endless ....

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
If you have to ask, then you probably shouldn't be "rooting" your mobile.

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
You obviously have never checked the G2x Development Forum... lol

I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?

leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.

Listen to me very carefully...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
************************************************************************************************************
************************************************************************************************************
thank you, for a detailed question. i appreciate that. i am glad you understand the basic concept of replacing the stock recovery, this helps immensely.
************************************************************************************************************
read carefully and thoroughly!
************************************************************************************************************
************************************************************************************************************
First, some questions and a bit of information...
1. did you install ubuntu linux as a virtual machine (guest) (i.e. using vm ware or virtual box) while using another os as a host (main) os?
2. ...or did you erase your previous os and replace it with ubuntu linux?
3. ...or are you dual booting ubuntu linux w/ windows or some other os (i only ask this to AVOID confusion in any further communicae)?
4. for the rest of this discussion we will assume you are EITHER dual booting w/ a linux os OR you erased your previous os and replaced it w/ some flavor of linux; if we HAD assumed that you were "virtualizing" a linux guest os inside of a host system like windows, then the unix bash script that ctso wrote MAY NOT work b/c virtual systems (regardless if vm ware or oracle's vrtual box) sometimes fowl up, for lack of better explanation at this point, and may not be able to identify usb connected devices properly
Second, some information...
1. a linux os (i.e. linux mint, ubuntu, debian, cent os, fedora, arch, open suse, slackware etc., etc.) does NOT need drivers to communicate to your linux kernel mobile as windows does. the linux os communicates, so to speak, to the linux that is running in your mobile handset
2. windows needs apx drivers to translate, if you will, windows/dos speak into linux/unix speak; again, the apx drivers mean NOTHING to linux b/c it does NOT need them and further more CAN NOT use them as they are for windows based computers only
3. windows' super oneclick/nv flash will NOT work w/ ANY g2x that has stock gb on it, even though it did work w/ a g2x that has stock froyo; this may change in the future (if this has changed tell me; though the info is personally useless to me b/c i have ran linux since 1999)
Third, more information...
1. the unix command 'lspci', literally means "list all pci devices" in unix speak, which, to reinforce again, is NOT understood by windows (for the most part; though dos was formulated off the unix structure)
2. the 'lspci' command is used just so you can verify that your g2x is connected to your linux computer, nothing more; and it is NOT necessary for any of ctso's procedure, he's just being complete
3. if you typed 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), you would NOT see 'g2x' or anything of that nature listed; you would see a listing such as '00:05.0 PCI bridge: blah blah' (just an example!) that would indicate your mobile device is connected
4. so, do NOT worry about 'lspci'
Fourth and finally, more information and hopefully, a solution...
1. now, let's move on to more lessons in linux
2. let's pretend you downloaded ctso's script "flash-recovery.sh," how do you use it?
3. remove your mobile's battery
4. hold down VOL UP + VOL DOWN
5. simutaneously, connect your g2x to your computer (remember it better be running linux for this to work!)
6. release VOL UP + VOL DOWN
7. nothing will happen on your mobile (no "updating" or anything) and nothing will happen on your computer running linux (no windows popping up, no devices found, nothing!)
8. at this point, you could type 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), but you won't b/c you don't know what you're looking at anyway
9. now, open the linux/unix terminal (what windows users like to call a command prompt)
10. navigate, yes, navigate through the folders using the terminal to where you downloaded ctso's script "flash-recovery.sh"
11. let's pretend you have the script and the ACCOMPANYING FILES that you got from ctso in a folder named 'linux' on your desktop
12. when you opened the terminal, you saw something that looked like this...
"[email protected] ~ $" w/o the quotes
13. navigate to the desktop by typing...cd Desktop
[email protected] ~ $ "cd Desktop" w/o the quotes, the "D" in desktop is capitalized and no spaces after the $
14. navigate to the folder named 'linux' that has all the goodies, not just the bash script, that ctso gave us (you are NOT going to directly use these other files, but the bash script DEPENDS on them!)
[email protected] ~/Desktop $ "cd linux" w/o the quotes
15. now, your in the folder named 'linux'
[email protected] ~/Desktop/linux $
16. now what? you will type the following...sudo bash flash-recovery.sh
[email protected] ~/Desktop/linux $"sudo bash flash-recovery.sh" w/o the quotes
17. you will be prompted for your user password, type it and press enter!
18. your mobile's screen will magically light up and say, "updating" or "SW" or whatever
19. when the terminal says the recovery image was transferred successfully, disconnect the mobile from the computer's usb, regardless of the mobile still displaying "SW"/"updating"!
20. you're done
21. i'm exhausted
_____________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
__________________________________________________ __________________________
- LG P999, Rooted, Gb 2.3.3 Tweaked v1.2.2 by Xboarder
- HP dv7t w/ Debian Linux

If windows didn't exist, it would be a better world...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer said:
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer, I appreciate you trying to help leonblade45 , but...
****************************************************************************************************************
You are confusing the issue.
- apx drivers are NOT needed in a linux based os (i.e. ubuntu linux) and WILL NOT work in linux
- leonblade is trying to use linux, but is getting confused w/ windows knowledge he may have regarding drivers and why they are needed for windows
- windows' oneclick (as far as i know; if i'm wrong, correct me) is NOT currently able to flash the recovery onto any g2x running STOCK GB
- PLEASE SEE MY POST BELOW leonblade's QUESTION
- thank you

linux_user9 said:
If you have to ask, then you probably shouldn't be "rooting" your mobile.
Click to expand...
Click to collapse
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?

Oh well...
blestsol said:
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?
Click to expand...
Click to collapse
****************************************************************************************************************
Mr. bletsol:
- remember "rooting" or granting super user access to the linux kernel is NOT BENIGN
- Aesthetics of the mobile is NOT a good enough reason to "root", functionality/usability is understandable
- I'll say it until I'm blue in the face (which seems to be, what it takes when trying to educate windows and mac users): If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel

I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.

Glad to hear it!
leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
I'm glad to hear that the instructions were of use, please forgive me if I came across stern or condescending. I am also glad to hear you are exploring the world of linux and that you're one-step closer to completely replacing windows!
linux_user9

leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
Yeah, I did that dual-booting a year ago as well. And then, after 2-3 weeks, I switched. I've been Windoze-free for a year now.
(lol... sounds like out of rehab)

G2X Root with linux
WINNING!!!
Ubuntu lucid. Worked perfectly.

softbrick
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.

Soft-Brick
cyberlync said:
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.
Click to expand...
Click to collapse
2011.12.05
cyberlync:
I am sorry to hear that you're having issues with the procedure. Let me first say that I didn't receive your message until yesterday, as I choose to receive only weekly updates via email on posts that I create.
If your issue is resolved, let me know. What you're describing in your post is what is called a "boot loop," if I'm understanding you correctly.
PLEASE READ ALL OF THE INSTRUCTIONS (I know that I can be long-winded)
First, several questions for you:
1. What Linux distro are you using (i.e. Debian, Linux Mint, LMDE, Ubuntu, CentOS, etc.)? Also, what version of Linux distro are you using (i.e. Debian 6.0, Linux Mint 11, etc.) Hopefully, you're not running Linux as a VM in a Mac or Windows host.
2. What Android distro or "rom" did you decide to use (i.e. CyanogenMod, Bionix, EDT, WeaponG2x, Tsugi, etc.)? You may need to download a "fresh" copy of the "rom" in case it is damaged, corrupt or incomplete. Again, I highly recommend Cyanogenmod 7.1.0.1 Stable (Don't forget to install "gapps" if you want Google Apps in CM7)
3. With your mobile off, are you able to boot into Clockwork Recovery by HOLDING DOWN THE VOL DOWN KEY and the POWER BUTTON simutaneously, THEN RELEASING them after the initial splash screen has displayed (the splash screen image will depend on which Android distro you're using; i.e. the LG logo.)?
4. Which Clockwork Recovery are you using, that is, what is the version number (if you don't know, tell me the color that the text is appearing; i.e. orange, red, blue, etc.)? Did you use ctso's recovery flash image or one of the updated attached one's that I provided, courtesy of krylon?
Second, there's GOOD NEWS if you can boot into Clockwork Recovery, the "fix" will be much quicker. Boot into Clockwork Recovery, then do the following:
1. Check to ensure that you have a copy of the "rom," that you downloaded onto your computer, on your mobile by going to (the power button is the enter key, vol keys allow scrolling up/down) --> install zip from sdcard > choose zip from sdcard; if you do NOT have this on the sdcard, all is NOT lost in the short-term provided you used the EXTERNAL recovery flash image from krylon that I provided or the ONLY recovery flash image from ctso. If you have used the INTERNAL recovery flash image (and depending on which "rom" you have chosen, as some have re-ordered the P999's mount points), make your life easier and REPEAT THE INSTRUCTIONS IN THE OP USING THE EXTERNAL IMAGE, otherwise you may need to download the Android Debugging Bridge (ADB) from the Google developer's website and I'll have to administer some Linux/UNIX command-line instructions. IF THIS IS THE CASE, I DON'T MIND HELPING YOU, BUT IT MAY BE EASIER TO CHAT IN ICQ OR ANOTHER ONLINE MESSAGING SERVICE.
2. PROCEED TO THE FOLLOWING IF YOU USED AN EXTERNAL RECOVERY IMAGE AND HAVE A "ROM" ON YOUR MOBILE'S SDCARD:
a) If you do NOT have a "rom" on your EXTERNAL SDCARD, connect your mobile via USB to your computer, boot into Clockwork Recovery, then go to: mounts and storage > mount USB storage, press enter (power button). Then copy the "rom" to your device's EXTERNAL sdcard (NOT THE 5.8GB SDCARD [IF APPEARING; IT MAY NOT DEPENDING ON WHICH "ROM" YOU'VE CHOSEN AS SOME RE-ORDER THE P999'S MOUNT POINTS], THAT IS YOUR INTERNAL SD); next > unmount USB storage. Safely Remove drive (right-click) via the Linux file manager.
b) NOW DO THE FOLLOWING FROM MY OP:
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
3. This should've fixed it.
More questions/problems? We'll work through it.
linux_user9

[HELP!] Velocity Cruz T301 Full Brick Recovery

Hi XDA,
so basically i bought a Velocity Cruz T301 recently and followed the known procedures for rooting, flashing ClockworkMod Recovery and custom rom (SJHill Rom v0.3).
before the full brick my device was at ClockworkMod 5 and rooted with SJHill Rom v0.3.
i installed CWM by flashing the zip in stock recovery, then succesfully rooted the device, finally wiped and flashed my custom rom
after major dissapointment in this tablets performance i decided i wanted to get rid of it.
So i downloaded the stock rom, wipe and flashed it onto the tablet...
the tablet turned off when it was finished (i think it was attempting to reboot) and never turned back on again...EVER! :good:
i cant even get to recovery
i tried flashing with adb and fastboot but the device is never even presents itselft to the computer.
i found out that you can boot the device into USB boot mode where you hold the "VOL -" (Volume Down) button and press the reset button and while connected to the computer (windows only) a "JZ4760 USB Boot Device" appears.
i did some googling and also found out that the T301 is based on similar tech to a bunch of tablets and they can all be modified by some software released by Ingenic called USBBootTool.exe
the tool is written in chinese and i cant decypher it all, though i found out how to use it based on its usage for other Ingenic based tablets
1.) you will need to disable driver signature verification (press F8 on boot of windows and toggle the setting, i hate rebooting too but it has to be done)
2.) boot your tablet into USB Boot Mode (hold down Vol - and press Reset button)
3.) install the driver for your device (included in the files below)
4.) with the tablet disconnected you would open the USBBootTool.exe
5.) select your tablet in the options and fill each box with the files needed to flash (files included below)
6.) reconnect the tablet while still in USB Boot Mode and the software will flash your device on detection
everything goes fine for me except when i get to the flashing part in the end.
when USBBootTool detects my tablet, it attempts to flash and gives me a stream of errors and never flashes my device.
i dont know what to do at this point. i have provided direct links to all the software im using and also links to where i got them.
any help would be appreciated, thank you to the XDA community in advance
>------------------- DOWNLOADS ------------------------<
USBBootTool.exe / Tablet Drivers (4725 / 4725B / 4740 / 4750 / 4755 / 4760 / 4770)
http://dl.dropbox.com/u/79196608/burn_tools_3.0.16.rar
obtained from - http://forum.xda-developers.com/showthread.php?t=1720621
Velocity Cruz T301 Update.zip (contains the system.img / data.img / mbr-xboot.bin files)
http://www.cruztablet.com/T301update.zip
obtained from - http://www.cruztablet.com/Article_861.php
SJHill Rom v0.3
http://www.androidfilehost.com/?fid=9390362690511176486
obtained from - http://www.slatedroid.com/topic/27583-rom-t301-sjhill-rom-17-feb-2012-download-link-updated/
ClockworkMod 5
http://files.androtab.info/ingenic/cwm/20120514/T301-recovery-signed.zip
obtained from - http://androtab.info/mips/ingenic/clockworkmod/

I have the same situation. I have gone through every menu in the USB Boot tool and to no avail am I able to recover my T100.

gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.

feyerbrand said:
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
Click to expand...
Click to collapse
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one

JustSayTech said:
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
Click to expand...
Click to collapse
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.

wow, i learned alot from that post, seems like writing a usbboottool-like application that can send the commands but also log and possibly bypass security checks etc but that def would take sometime. thank you for your insight, seems youve come the closest to cracking the case, actually you found the fault, hopefully your methods can eventually bring about a fix

JZ 4770
gmick said:
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
Click to expand...
Click to collapse
for my JZ4770 Earlier USB tool was flashing .img without any problem but for now it is saying "load cfg failed". "API downlaod failed' like dialogues and doesnt flash anything. Any idea? Thanks in advance!!

First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball

Yes, I did
JustSayTech said:
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Click to expand...
Click to collapse
Yes, I tried with this suggestion. Rather I reinstalled xp and the tried again. But the dialogues are same. The history is like this. Was having ICS on JZ 4770. Formatted with usb tool and put JB updates. It was not sensing touch so reflashed another JB updates. Now the tab boots, it reaches to boot logo for around 12 seconds and restarts in stock recovery. While it is in booting stage it get detected by windows and adb also. In stock recovery mode it get detected by windows and in turn by adb also. If I tried to install updates through SD card it shows it had installed and reboots after completion. But again the same way it goes to boot logo and then back to stock JB recovery. It also boots in ingenic boot device mode and gets detected by USB burn tools. But when try to flash any of the ROM it gives the same dialogues "check cfg failed" "api download failed" "boot. fw failed" and cant flash anything.
Is there any tool which can be flashed or a script which can be used from SD card for completely formatting flash memory so that USB burn tool can flash required ROM?

can you flash the stock rom in recovery?

Managed using USB BOOT TOOL for ingenic JZ 4770 board in English
JustSayTech said:
can you flash the stock rom in recovery?
Click to expand...
Click to collapse
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html

Got USBBootTool.exe kind of working.
1. Download the following file from Ingenic.
ftp * ingenic * cn/3sw/01linux/tmp/jz4770-20110610.rar
2. Download Applocale from Microsoft.
www * microsoft * com/en-us/download/details.aspx?id=13209
3. Extract the jz4770-20110610.rar and find the folder. (Using 7zip should keep the UTF encoding in Chinese)
20110610\04burn\20110524_4770_Programmer
4. Copy the folder 20110524_4770_Programmer to location you want to use it in.
5. Install Microsoft Applocale (Just in case, I don't think it is required)
Now Start Applocale and create a shortcut to USBbootTool.exe inside 20110524_4770_Programmer
中文(简体) is simplified Chinese option and should let you view the GUI correctly.
6. Now with the Applocale Shortcut created for USBbootTool.exe you can start the application with correct fonts.
Now this is where is breaks down.
TABLET-8 NAND FINAL BSP(S3 TEST) will allow you to read from it and write to it, but the CFG is off.
\tool_cfg\tablet-8-nand-final.ini is the configuration for it.
DO NOT CONNECT THE DEVICE WITH ANY OPTIONS CHECKED OR LOAD ANY FILES.
See Attached Images.
Next to the Read button is some Boot Option menu. I am not fulling aware of what this does.
What I need is a someone to help me fix/correct the ini/cfg files in
\20110524_4770_Programmer\tool_cfg\.ini
\20110524_4770_Programmer\4760\
to correctly match the files of the NAND.
Also if anyone has a copy (dd to img) or (cat to img) of the block devices.
That would help a ton.
# cat /proc/partitions
# cat /proc/mtd
I would also love another T10x Tablet for cheap.
I want to start building things like new bootloader, kernel, system image,
performance libraries to take full use of the Ingenic JZ4760 (www * ingenic * cn/product.aspx?CID=11)
I also bring Christmas gifts
2 APKS. You can place them in /system/app or /data/app.
Google Play will crash now and again, but it will load and work. (Vending.apk)
Secondly I bring the gift of performance increase, just by a slight bit.
edit the line of the heapsize in /system/build.prop dalvik.vm.heapsize=96m
Remember to make sure the permissions are set back to 666 or 644.
Original Vending.Apk before updates came from here: (Incase you are paranoid)
code * google * com/p/ics-nexus-s-4g/source/browse/trunk/system/app/Vending.apk?spec=svn20&r=18
ics-nexus-s-4g * googlecode * com/svn-history/r18/trunk/system/app/Vending.apk
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for
Click to expand...
Click to collapse
Stupid. how do you expect real people to help post Tech Docs? That is bad Moderating and Administrating.
Make sure to replace the Asterisk's with spaces to normal dots.

Requesting Block Images.
Does anyone have a copy of it they can send me for a T10x?

block images......
IceGryphon said:
Does anyone have a copy of it they can send me for a T10x?
Click to expand...
Click to collapse
Which block images do you want?
...also is there a way to rip the stock images off the jz4760 in the t301.
Such as:
Can i usethe ingenic uboot tool?
Anybody find the jtag pins?
Is the 4 pin conn next 2 the batt for serial?
.......i guess ill try to take a look this weekend
Ics would be really nice, but probably slower than stock..... especially with the limited ram
I unpacked the stock rom. I also unpacked an ics rom for a jz4770, and repo sync'd the aosp and mips 3.0.8 android kernel.
I'm still trying to figure out specs for the processor though. I know that its mips32 - el- fp- r1, but i cannot figur out the dsp version ... if it has one?

Error in erasing nand
nanachitang420 said:
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Click to expand...
Click to collapse
I used english ingenic tool to erase bad blocks but m nt able erase bad blocks live suit is giving eror id=0x4848

[Q] Trying to root SM-G920F using Linux

Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!

torbengb said:
Hi! I'm exasperated so I turn to the experts: you! I hope this is right (or should I have continued this megathread?)
TLDR: Want to root international S6 running branded 5.1.1; but using Linux and having trouble getting things to work. Have tried lots already; details below.
1. bootloader status = I think it's unlocked but not sure how to determine this.
2. Rom name with complete baseband/date/version = "Austrian 3/Hutchinson" branded, PDA Version G920FXXU3COI9, CSC Version G920FDRE3COJ1, PHONE Version G920FXXU3QOJ1.
3. Kernel name = uh, stock Samsung 5.1.1?
4. Mods = none
5. Custom Rom = none
6. Guides =
7. Root status = unrooted.
8. Your exact problem = Want to root, having trouble doing so.
9. Any method you tried that failed = see details below.
10.Any other detail you think would be necessary = my phone's ODIN screen lists this information:
PRODUCT NAME: SM-G920F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I've tried rooting my S6 using Linux, using a virtual WInXP hosted on Linux, and using an old real WinXP computer. None of the methods worked, but let me describe what I've tried on each -- I'd be happy if I can get either one of the methods across the finish line!
1) Virtual WinXP computer on Linux host
created a brand-new virtual WinXP installation to make sure nothing would interfere.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
In the settings for the virtual machine, set up rules to ensure all Samsung USB devices (USB vendor ID 04e8, any product ID) would be routed directly to the virtual machine.
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Neither Windows nor Odin sees the phone - neither in its normal operating mode nor in its "Odin" download mode.
Give up.
2) Physical Ubuntu computer, using JOdin
Installed Heimdall (latest version = 1.4.0-0).
Downloaded JOdin (latest version = v1035).
Installed Oracle Java 8 (8u67).
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
JOdin says: "We could not obtain the pit file. We tried, but it didn't work." It seems that this is not really JOdin's fault but rather Heimdall (which JOdin relies on) because running just Heimdall from the CLI gives the same problem, as seen from this log (verbose version).
I dare not download a "random" PIT file from the Internet; this would satisfy JOdin but the risk of choosing the wrong one is too high. Other sites also mention ways to use the adb shell but ironically these require root - so I can't use them.
3) Physical WinXP computer
I did all of the above Linux trickery because I don't own a computer with Windows. By sheer chance, a friend came by with an old WinXP machine that I could commandeer for this purpose.
Installed Samsung drivers.
Installed Odin 3.06 - this is the newest version I could find that didn't show the error "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll."
Rebooted for good measure.
Connected phone in rear USB port, directly on motherboard (no hubs).
Odin sees my phone in download mode (first success!) and I can do the steps to start the root.
Odin works it way through the file and goes to "NAND write start" and then "Complete(Write) operation failed". I've tried this using the CF-Auto-Root and also separately using the unibase kernel for 5.1.1, with identical results.
I feel that I'm so close and yet success is not yet in reach. What more can I do? Thank you for your help and kind assistance!
Click to expand...
Click to collapse
I think may need to find a way to run the newest odin thats the only thing i can see thats rong in your attempts idk im not a big linux guy. U might need to get ahold of a win8 pc

WinXP SP2 = solved!
I solved the problem on Windows and finally got that big friendly PASS! :laugh:
As it turns out, there were two things blocking my success:
Odin version not compatible
Windows XP needed Service Pack 2
Initially I tried using the newest version of Odin, of course. But version 3.10.7 does not work, says "is not a valid Win32 application" so I went back to earlier versions until I found one that could run. The second-newest Odin version 3.10.6 does not work, says "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.dll." Finally, version 3.06 could run, but as I now know, that version is so old that it does not support the Samsung S6! Of course it doesn't say so, and that's why I was stumbling in the dark for a good while.
So I need a newer version, but what can I do to make the newest one work? I finally discover that v3.10.7 (despite being only a minor release) has this in its unofficial release notes: "Removed support for Windows XP or earlier"! Okay that was hard to find!
So I need the previous version, v3.10.6. However, that one complains about kernel32.dll. Where can I find a newer version of that DLL? It dawns on me that my brand-new WinXP installation doesn't have any of the service packs yet, so I install WinXP SP2 and, lo and behold, version 3.10.6 can finally run!
But all of this was on my virtual machine, and it still couldn't detect when I plugged in the phone on the host computer. So I took a look at the WinXP machine that luckily was passing through my home just now. It's in German, and only runs WinXP SP1. I managed to find and install SP2 in German, and finally I had Odin v3.10.6 running on that machine - and it actually detected my phone!!
From here on, it was trivial to complete the rooting process. Once the software gets to run as intended, it's a beautifully simple thing. My phone is now rooted, and I can finally have Llama put it into airplane mode when I go to sleep. SUCCESS!
(But I still don't know why it doesn't work on Linux.)

[Root] H901 - For Newbies!

None of the methods in this thread are my own work. I struggled with getting my phone rooted for a long time and spend 10s of hours on the process. I had never rooted before and was therefore unfamiliar with all the terms, unfamiliar with how to complete all the recommended checks to ensure one had the right model, etc. There were several helpful threads but most approach the subject with the assumption that one knows something about the process. In this post I lay out what worked for me in a step-by-step way and what you have to do to achieve my results.
#1 Ensure you have a H-901 motherboard and not the Korean F600 motherboard by checking the sticker, and checking “About Phone” -> “Hardware Info” -> “Model number” in settings. These must both be LG-H901…from what I can tell the community has only developed technique for the H-901 variant.
#2 Get a micro SD card and load it with Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 , and if you have Marshmallow or Lollipop and want Nougat (much better experience IMHO), load the files in this thread: https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203 And maybe this thread as well (read both and then decide): https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
#3 Ensure you have unlocked your bootloader. (apparently only for T-mobile LG v10s since other carriers lock the bootloader) The FWUL virtual machine root method will not work if you have not done so. This is an entire process in itself. The following 2 videos which show how to root android 6.0 or earlier (process will not work with Nougat, 7.0, since some fastboot commands are missing). https://youtu.be/OtXlokk6JkQ , https://youtu.be/PPLwFGxLQA4
Also, this thread may be helpful. https://forum.xda-developers.com/tm...t-mobile-bootloader-factory-unlocked-t3236224 , download the nexus root toolkit here for easy ADB command entry http://www.wugfresh.com/nrt/ —we will only use the “Advanced Utilities” -> ”Manual Input” -> ”Launch CMD Prompt”. When it prompts you to select a phone, select the first option and then for android version select Android *** Any. Don’t use any of the other commands because they are not configured for your device.
If you get a “waiting for device” error while attempting the fastboot oem unlock command in the above thread, see: https://forum.xda-developers.com/tmobile-g4/help/fastboot-waiting-device-t3489789 Great video which shows how to change drivers. You will need to do this, I found a number of drivers that were already on my PC from google and Samsung worked although I didn’t have the specific one mentioned in the above thread. Don’t be afraid to experiment… you can always try another driver. And don’t require it to be hardware compatible. Ignore the warning message: https://youtu.be/nQjg6ePnGAc
---------------------------------------------
NOW that you have your bootloader unlocked you can proceed to actually flash the TWRP image as per this thread: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Notes before beginning:
-To enter download mode to begin: Plug a USB cable into your phone with your phone powered off, hold down on the Vol Up button and plug the USB cord into your computer. It should immediately boot into download mode. Exiting Download mode after flash: pull battery…no damage will be done.
-To enter recovery after flashing TWRP: power off the phone then hold both the down volume and power at the same time. When you see the black LG screen briefly release the power button and then press it again while not letting the volume down up. You will see a screen asking if you want to delete all user settings. Say YES (via the volume and power keys—no touch input). You will see a screen asking if you want to delete all user data. Say YES (the data is only deleted if TWRP loads successfully) You will briefly see the black LG bootup screen. TWRP or factory recovery will load. Or if you did not unlock your bootloader, it will say recovery is corrupted and cannot be trusted, and then boot normally without changing your settings or deleting files.
-Additional note: as of 7-23-18 some commands had changed:
From V20 forum, Brian (runningnak3d) has moved to gitlab.com. So instead of github.com, we have to use a new git repository that Brian created in gitlab.com.
cd
mv lglaf lglaf_BAK
git clone https://gitlab.com/runningnak3d/lglaf
cd lglaf
git pull
git checkout v10-miscwrte
There are additional comments in the thread. Some timeout errors may be solved by: 1 - Download the VirtualBox extension pack: https://download.virtualbox.org/vir..._VirtualBox_Extension_Pack-5.2.8.vbox-extpack
2 - Go to File / Preferences / Extensions / click the + and browse to where you downloaded it.
3 - Once installed, with the VM off, right click on the VM, and go to settings. Click on USB, and pick USB 3.0. If your machine doesn't have a USB 3 port, pick 2.0.
But frankly, simply up arrow after a timeout error to load the last command on the command line and hit enter again. Simply keep doing this until it works. You know it works because no dialog appears for several minutes before informing one of success.
**Upgrade to Nougat after Flashing TWRP and booting to Recovery steps: (I did a full wipe as suggested by this thread: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 before flashing the v30b upgrade then full Nougat zip, and then flashing Magisk. I flashed the 3 zips sequentially. I was afraid Nougat would not boot successfully because the zip files are less than 2 gb combined but success! You may want to also flash the 30c upgrade before flashing Magisk for a total of 4 zip flashes. I did not try this. However doing all this means no backups are done so if there is a problem you may have to flash a KDZ with the LG UP tool (don’t ask me how).
As a final note, I cannot answer specific questions about the various processes provided or errors you may encounter that I have not listed in this write up since I have not experienced them. A bit of research on your part may be required, but this post should provide you with a huge head start compared to where I started. Good luck!

Methods to get unlimited mobile hotspot, very useful if you're on the $50 MetroPCs (owned by T-mobile) unlimited plan. All you $70 T-mobile plan suckazzz! https://forum.xda-developers.com/tm...ited-tetherting-hotspot-t3825144#post77249285
I would actually recommend using a USB tether client and forgoing root access if tethering is your only objective and you are trying to be efficient with your time. However, with root you can install all these cool apps!: https://www.digitaltrends.com/mobile/best-android-root-apps/
The following caught my eye:
-Rec: screen record
-liveboot: boot animation (does not work with Magisk)
-Servicely: checks to see which apps are using a lot of battery and lets you suppress them
-Adblock Plus
-Titanium backup: very powerful phone backup application & bloatware remover look into for quickly switching over to a different lg v10
-Greenify: put apps into hibernation
-System tuner: get lots of info about you phone but be careful making changes
-ES file explorer: dig into the android system
-Disk digger: recovers deleted files (photos only?)

Help me with my hard-bricked N920P

I guess I finally hard-bricked my N920P trying to install Universal SafetyNet Fix. It was on stock (N920PVPS3DRH1) but I had TWRP and Magisk Canary installed. I was trying to get Zygisk working but couldn't get it properly turn on, even on the stable and canary builds. That's where I had tried to install the SafetyNet fix module. It said it doesn't fully support anything below Android 8.0, but it did finish installing and asked me to reboot. And it never turned back on.
I cannot get into the download mode, recovery or system. Tried all key combos and no life at all. I drained the battery all night long and tried plugging into the PC and now it detects it as an unknown "Exynos7420" device. That was something from the nothing I got before. I tried looking up on how to rebuild the corrupt bootloader but I couldn't wrap my head around on how the process works. There was material on getting a software called "USB_Downloader" and I got all the way to installing the drivers and getting that software recognise the device as a COM port. I did this in a Windows 7 32 bit VM on VirtualBox (VMWare kept crashing my entire USB Host Controller everytime I tried passing the phone's connection to the VM, which was weird).
Now I'm stuck with this software and am unable to understand what I need to do next. There was something about getting the sboot.bin file and creating 4 new files to push through the Exynos COM port to fix the bootloader. There was also something about getting a Hex editor to do this, but I cannot understand what's going on. Could someone please help me get around this?
Thanks in advance!!

Never mind I fixed it. Just posting it here to make sure no one else gets stuck like I did for a long while. So what I had done was I forgot I had a custom ROM installed. It had been based on the N920PVPU3DQC5 firmware. So I downloaded that firmware, extracted the sboot.bin file then went to work with a hex editor (HxD for Windows specifically).
Open sboot.bin in the hex editor and start making new files listed below. The sections are also listed below, you can ensure the size in the bottom of HxD.
Save them as novi1.bin, novi_2.bin, etc...
The offsets I used are:
BL1 or novi1.bin: 0 - 0x1FFF (size 0x2000)
BL2 or EL3 or novi_2.bin: 0x2000 - 0x31FFF (size 0x30000)
EL3 or BL2 or novi_3.bin: 0x32000 - 0x3dfff (size 0xC000)
S-BOOT or novi_4.bin: 0x3E000 - 0x18F100 or end of file (size 0x15110), this will include tzsw.
Next this is the cfg file I used:
Code:
; S Project
; must keep order of binary list
; BL1
DNW_STORE e5250 fwbl1 200 20 novi1.bin
;DNW_WAIT
; BL2
DNW_STORE e5250 el3_mon 2000 20 novi_2.bin
; u-boot
; Wait Re-Enumeration
DNW_WAIT
DNW_STORE e5250 bl2 2000 20 novi_3.bin
;DNW_WAIT
DNW_STORE e5250 bootloader 20000 20 novi4.bin
;DNW_WAIT
;DNW_STORE e5250 tzsw 20000 20 4pt.img
Copy this code and save it as SH-usb-booting.cfg in the same folder as your .bin files. Now you can launch the multidownloader and load the .cfg and select Auto Run. Now press and hold the power button on your phone and connect it to the PC. It should automatically go through the whole flashing process and end up in the download mode screen. You can now flash the firmware from there!
If you have any doubts hit me up!

LOL I'm stuck again. I got into Download mode but my VM was having trouble connecting to the Download mode USB modem and it crashed the USB controller on my PC. I had to reboot the phone and now I'm stuck again in Exynos USB mode. Trying to get back into Download mode using the files I created above but it's not working anymore. I can hear the USB getting disconnected on the host at the AP Re-enumeration step but it isn't disconnecting from the guest VM. I guess I'll have to find a physical PC to try this out on.
EDIT: I had used VirtualBox until this step. After the hanging on Re-enumeration issue, I figured it could be Virtualbox causing the issue so I tried using VMWare, and ta-da, it worked. Read posts below for updates.

So I somehow got myself to get into Download mode consistently. Turned out my VM's USB controller was acting up so I clean installed it and I'm able to send the sboot files and get into Odin mode. But new trouble. Everytime I flash the stock firmware it goes through the process, passes and resets. But it never boots!! Just goes back to the same Exynos mode. I can re-flash the sboot file to get back into Odin mode but I'm stuck like this. I have no idea what to do now...

Progress so far:
I can't remember what custom ROM I had originally. Radeonmaya S8+ N920P ROM was supposed to be based on the DQC5 deodexed stock ROM posted here in the N920P forum.
1. Tried creating new files from DQC5 - SPR sboot.bin: Booted into Download mode, tried flashing the 4 file firmware, no progress, resets back into Exynos mode.
2. Used the DQC5 - SPR sboot.bin to boot into download mode: Tried flashing thr 4 file firmware for the latest firmware that was installed in the phone which was DRH1. No progress, resets back into Exynos mode.
If I'm reading this correctly, the Radeommaya ROM makes changes to boot.img and system partitions. Everything else remains stock, therefore my original bootloader for firmware DRH1 should work. However, I'm not able to get into the system.
I must note that TWRP recovery was installed on the device. The best course of action would be to install the same custom ROM back together with TWRP, but I could not find an Odin flashable tarball for the Radeonmaya ROM. The forum's been dead for a couple of years and the Telegram group is also dead. Looking for ways to make my own tarball using handpicked files maybe.
Currently trying to create new .bin files to boot into Download mode via the Multidownloader from sboot.bin files I salvaged from the XAS (Sprint Unbranded) firmware packages DRH1 and DQE1 (Apparently this firmware has helped someone in the Radeonmaya ROM thread to boot back into the system from a similar hard bricked situation, however I speculate this would not fix my problem because the DQE1 firmware is newer than the DQC1 firmware, which the custom ROM was based upon)
Will post more findings later.
P.S. VMWare could be quite finicky to work with when trying to passthrough the Exynos USB Device to a Windows 7 guest. It caused my AMD Ryzen host to crash its entire USB controller and both my USB mouse and the phone wouldn't connect to the HOST, let alone the guest. It causes a never-ending loop in the code which also stops a proper system restart, hence needing you to force power-cycle the whole computer.
This is because of the unusual nature of the driver being 32-bit only and incompatibility with VMWare. However, it should work when you reinstall VMWare without the Enhanced Keyboard driver, and also reinstalling the Exynos USB driver on the host and the VMWare USB Device (found in the Universal Serial Bus controllers section when you have the USB connection passed through to the VM).