we dont have a section for the vk815 yet so im posting here.
i just rooted my g pad with a 1-click root fro the g3 section
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i followed this guide by avicohh . be sure to give him a thanks for his work
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
if anyone would like to compile TWRP for the X8.3 we would be very appreciative and i now i would be willing to donate some beer money.
i am not a dev and do not pretend to know anything bout building roms an such but am willing to be a tester
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume UP and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
player911 said:
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume Down and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
Click to expand...
Click to collapse
glad you got root. have you tried installing twrp from the vk810.?
in the TWRP thread under android development i ask if anyone was willing to compile TRWP for us and a guy i said he would take a look at it.
Nah. Just rooted. Honestly since Lollipop and ART, Xposed has kinda lost its luster. I actually like the stock LG experience.
I successfully rooted this am using the OneClick Root 1.3 method described here:
http://www.smartphoneclinics.com/easy-way-to-root-verizon-lg-g-pad-x-8-3-vk815-one-click/
It took about 5 minutes, and all that I had to do was choose PTP mode. After rooting I installed Busybox, and all is good!
Now, If I could just do the same with my VZW G4...
Requested a forum for VK815.
I'm looking hard at the VK815 since my Nexus 7 2013 died. I requested a forum for the device at http://forum.xda-developers.com/showpost.php?p=61761668&postcount=18535
Thanks for the work you folks have done already.
Give the request a bump. I referred to this thread.
Split screen
player911 said:
Nah. Just rooted. Honestly since Lollipop and ART, Xposed has kinda lost its luster. I actually like the stock LG experience.
Click to expand...
Click to collapse
My reason to root would be for increasing the number of applications Will work with the split screen mod. Anyone give this a try on this tablet?
mhonard said:
My reason to root would be for increasing the number of applications Will work with the split screen mod. Anyone give this a try on this tablet?
Click to expand...
Click to collapse
yes the split screen mod work. that was the first thing i did after rooting. not sure what mod you are looking at. all i did was edit build.prop
Where did you find this mod?
player911 said:
Where did you find this mod?
Click to expand...
Click to collapse
I didn't find the mod anywhere. I just looked though the build. Prop till I found the line bout split window or something and changed it to true. I don't have my tab on hand but will look and let you know the exact line
player911 said:
Where did you find this mod?
Click to expand...
Click to collapse
About 3/4 way down the build.prop you will find a line that says, persist.slitwindow.support_all_false. Change false to true and you will have all your apps in splitwindow
I rooted my X8.3 using this. Thanks!
Sent from my VK815 using XDA Free mobile app
neckbonest said:
glad you got root. have you tried installing twrp from the vk810.?
in the TWRP thread under android development i ask if anyone was willing to compile TRWP for us and a guy i said he would take a look at it.
Click to expand...
Click to collapse
Anyone know if/when we will see TWRP for vk815?
winpooh said:
Anyone know if/when we will see TWRP for vk815?
Click to expand...
Click to collapse
Maybe never hard to say. It has a locked bootloader and may not get much love from the devs
neckbonest said:
Maybe never hard to say. It has a locked bootloader and may not get much love from the devs
Click to expand...
Click to collapse
All of the LGs have a locked bootloader. Never stopped them in the past. Should be as easy as the 7" models.
player911 said:
Credit goes to Unjustified Dev for the LG Root Method used here:
UPDATE:
This is the method I used.
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I used these Drivers:
http://sourceforge.net/projects/avicohh/files/Android/LG_VZW_United_WHQL_v2.20.0.exe/download
Follow the guide all the way through ADB pushing the files to the device in step 5. Easy part.
Step 6 has you rebooted into Download mode:
With Tablet OFF, hold Volume Down and plug in PC connection
Once in download mode, UNPLUG the cable (it says not to but its ok) and replug it back in. This will bling on your PC and will start the driver install process. It will take a minute or 2 before the "unknown devices" start to pop up and start installing the drivers.
You should see a LG device under Device Manager > Ports. Mine was COM5. It varies. Now we are ready to continue. Run the "ports.bat" from a CMD prompt. You want to use the "NETDIAG1" port. Mine was COM5. Don't use the modem COM.
use the "Send_Command.exe \\COM5" to get shell access into your tablet. You should see a "#".
I like to type in "ls /data/local/tmp" to verify the files were pushed over properly in the first few steps using ADB.
AND FOR SOME REASON, this doesn't always work on the first try. I have better luck manually typing out the script string.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see a bunch of "inflating...." lines. If it gets stuck or just returns a blank "#" just keep retrying. It seems to work after it is sitting for a few minutes. Eventually you will see the script take off and you are done.
Just hold the power button down and reboot.
Click to expand...
Click to collapse
Thanks for these instructions! I got root successfully on my Verizon LG G Pad x8.3. Only things that tripped me up were getting the download mode - which is holding volume up on this device, and also rebooting at the end. I had a brief panic when I ran the scripts successfully, but couldn't reboot after it was done. I still had adb connection, so I tried typing "LEAVE" in the Send_Command prompt and that rebooted the device. Thank God!
neckbonest said:
About 3/4 way down the build.prop you will find a line that says, persist.slitwindow.support_all_false. Change false to true and you will have all your apps in splitwindow
Click to expand...
Click to collapse
did not work me, says it cant save
---------- Post added at 03:29 AM ---------- Previous post was at 02:45 AM ----------
did you already have root because i cannot save the build.prop
screenfreak said:
did not work me, says it cant save
---------- Post added at 03:29 AM ---------- Previous post was at 02:45 AM ----------
did you already have root because i cannot save the build.prop
Click to expand...
Click to collapse
You would have to already have root in order to save an edited build prop, and have root r/w enabled in the root browser you're using.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
bost005 said:
Thanks for these instructions! I got root successfully on my Verizon LG G Pad x8.3. Only things that tripped me up were getting the download mode - which is holding volume up on this device, and also rebooting at the end. I had a brief panic when I ran the scripts successfully, but couldn't reboot after it was done. I still had adb connection, so I tried typing "LEAVE" in the Send_Command prompt and that rebooted the device. Thank God!
Click to expand...
Click to collapse
I made an edit for Volume Up. It typically is up but I swore I had to actually use volume down. Glad it helped. I like to make detailed walkthroughs so I can not only help others but come back to when I need to later.
Once the script was done, I just waited a few minutes to settle and do a hard shut down. I do that on my G2 and G4.
Related
Hi all! This is a tool I made that will bypass your need to downgrade from 2.11.605.9 or .19 to get S-OFF. It uses the fre3vo exploit by TeamWin/Agrabren and the Revolutionary tool. I take no credit for this method.
Thank Agrabren here.
Thank the revolutionary team at Revolutionary.io
*I am NOT responsible for any bricked devices*
*Rooting voids your warranty! If you do not know that by now, you probably need to research more before you root*
This means that you will not have to deal with large files, and you will not lose any data.
Happy rooting!
*If you have any PG05IMG.zip files on your sdcard, remove them first!*
-----------------------------------------------------------------------------
File: Goo-inside.me Downloads - Downloading DowngradeBypass.zip
MD5 is on download page.
Mirror: http://dl.dropbox.com/u/61129367/DowngradeBypass.zip
MD5: BCD3A6982E819400E87CED8CFA6D3FB7
-----------------------------------------------------------------------------
All you do is download this, unzip it (very important!), and run the RUN-ME.bat. Just make sure to read and follow all directions in the program carefully.
Please copy and paste the beta code for Revolutionary when that step comes along (I tell you how in the tool), because if it gets put in wrong you will need to manually start Revolutionary from the support_files folder.
========= FULL TEXT TUTORIAL! =========
1. Download the file. Check the MD5sum of it. (If you do not know how, download this, open it, paste in the MD5sum that is above, click browse and select the zip file. If it is green, continue. If it is red, redownload the file and start over.)
2. Uninstall Droid Explorer if you have it. If you have any PG05IMG.zip files on your sdcard, remove them. Plug in your phone, set it to charge only (Through the notification menu on your phone), Go to Settings > Applications > Development and make sure to select "Stay Awake" and "USB Debugging" and hit OK on the popup if there is one. Keep the screen on during the process.
3. Right click on the .zip file, and then click extract.
This window will pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure "Show extracted files when complete" is checked, and hit extract.
4. Now a folder will pop up. In that folder, double click RUN-ME.bat.
5. A window will pop up. It should say something like "*Daemon not running. starting it now* *Daemon started successfully*"
If it says something like "*Failed to start daemon* adb server didn't ACK", you need to uninstall HTC Sync or other syncing software (EasyTether, PDAnet, etc.) then restart the tool.
5. You will now be at a menu. If this is your first time rooting, you probably do not have the fastboot drivers installed, so enter N and press enter. (If you do have them installed, enter Y and skip to step 8.)
6. Wait for the driver window to close. It will take awhile. (The big window, not the small one)
7. Click back on the tool window and press enter.
8. It should now find your device. If not, try rebooting your phone and computer and retrying.
9. Then it should say:
-Getting root with fre3vo, thanks TeamWin!
-This will take a minute.
There will be some static-y lines going across your phone's screen. This is normal.
10. After a few minutes, it should finish and say:
-Success!
-Restarting adb...
*daemon not running. starting it now*
*daemon started successfully*
-Putting superuser files on your sdcard...
[some random numbers here]
-Starting Revolutionary and the Website....
And then the window will close.
If not, and it says root unsecessful, then try pulling your phone battery and running again.
11. 11. At this point, a textbox pops up. Once you close it there will be another one. Keep the first one open until you get your beta key (After step 13).
12. The website revolutionary.io and one or two other black boxes will also pop up. If only the website pops up, and no revolutionary window, open the support_files folder and double click revolutionary.exe. If there are two revolutionary windows, you can close one.
13.On the revolutionary website, please scroll down to Download for Windows. Click that button, then cancel the download. Enter your phone's information in the prompts that pop up. The info you need is in the text boxes.
14. Click "Generate Key".
15. Once you do that, copy your beta key from the website, then paste it into the Revolutionary window. To paste it, right click the title bar of the Revolutionary window then click edit then click paste.
16. Press enter on the Revolutionary window.
17.It should say something like:
Code:
Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (Once moar...)
SUCCESS - Life gave us lemons, we didn't make lemonade!
Do you want to download (Internet connection required) and flash ClockworkMod Reocvery? [Y/n]
18. Press Y and press enter.
19. Now it should say:
Code:
Downloading recovery for your phone (mecha)... Done.
Flashing recovery over fastboot...SUCCESS!
Then the window will close.
20. Now, using volume buttons to navigate and power to select, select bootloader.
21. Wait a few seconds, and then select recovery.
22. Your phone will now go to CWM recovery and automatically flash superuser.
23. Reboot your phone and you're rooted.
24. Enjoy!
I think its awesome that someone did this but this method seems way more complicated than doing it the other way. Maybe its just because you spelled out every step though hehe.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
I think its awesome that someone did this but this method seems way more complicated than doing it the other way. Maybe its just because you spelled out every step though hehe.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yeah that's why ;P
These are pretty much the only instructions needed
All you do is download this, unzip it (very important!), and run the RUN-ME.bat. Just make sure to read and follow all directions in the program carefully.
Please copy and paste the beta code for Revolutionary when that step comes along (I tell you how in the tool), because if it gets put in wrong you will need to manually start Revolutionary from the support_files folder.
Click to expand...
Click to collapse
It's not really hard at all, I just wanted to give people something to go by
Yea I figured that. It makes the actual task of rooting seem a lot longer when you put it all to words like you did.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
Yea I figured that. It makes the actual task of rooting seem a lot longer when you put it all to words like you did.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
my original posts in other forums didn't have it, but I got a lot of questions so i decided to add it
I have two replacement Thunderbolts arriving today, and I plan to give this tool a whirl. I'll report back when I'm finished.
I was thinking of writing a tool like this, but I'm *so* glad I don't have to now!
I'm the type of coder who will spend hours trying to automate a process that would take only a few minutes if done manually
This def works.
Sent from my ADR6400L using XDA
Maybe someone here can help me out in this thread? It's about the Unroot tool... http://forum.xda-developers.com/showthread.php?t=1639830&page=2
Is it doing that when you do adb devices?
Sent from my ADR6400L using Tapatalk
disconnecktie said:
Is it doing that when you do adb devices?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I figured out the problem. Thanks though. I'll be rooting my new 'bolt as soon as the one I'm sending back is unrooted so there may be more questions headed your way. Thanks in advance.
Does it work for software version #2.11.605.9?
---------- Post added at 06:24 PM ---------- Previous post was at 05:53 PM ----------
This worked, thanks very much!!!!
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
dblkspecial said:
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Nevermind. I figured it out. All I did was take the stock rom from the unroot tool flashed via bootloader then ran the downgrade bypass tool n am now rooted again
Sent from my HTC Mecha using XDA
dblkspecial said:
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
It worked for me
Sent from my ADR6400L using Tapatalk 2
Double tested yesterday, this does work with 2.11.605.19
Sent from my ADR6400L using Tapatalk 2
worked perfectly, had to unroot cause i thought i was gonna send it in for warranty exchange, but i ended up fixing the issue in nonrooted state, now i used this to go back to root on .19 and flawless. thanks a bunch for ur work!
HTCDEV
If I have my phone unlocked using the HTCdev method do I have yo relock?
zbergmark said:
If I have my phone unlocked using the HTCdev method do I have yo relock?
Click to expand...
Click to collapse
yes you should
I had broken the screen on the Nexus 4 and after a daylong nightmare of pursuading LG and Google that my phone should be repaired in my native USA rather than Australia (the phone I got from Google had a model number for the international market rather than the US market), they finally let me send it in to a US facility to get it repaired. I now received the phone back with the screen repaired (took exactly 14 days and $140).
But when I start the phone it goes into a strange debug screen. After pressing the power button for a some time I get to another, more standard looking screen. But the buttons on the bottom are completely missing (no home, return, or widgets buttons). From there I can only access the settings widget in the top right corner of the screen. When I go into settings I get the following info:
Model Number: Full Jellybean on Mako
Android version: 4.2
Build number:
full_mako-userdebug 4.2 LGEP19
eng.seungju24.choi.20121114.105751 test-keys
Also lots of debug apps seem to be installed, although I have not managed to get to the main screen to actually execute anything.
It seems that LG has replaced the standard OS with another (maybe debug or testing) build that does not work properly on the final consumer
product.
Does anyone have any suggestions? I am concerned that if I try to deal with LG I will be without a phone for another 2 weeks, and based on the
experiences so far I am not convinced that I will not have any further problems.
Thanks!
RWTX
I would suggest you download the factory android 4.2.1 image and flash that. That way you'll have your android os setup like brand new.
1. The firmware(s) can be found on this page :http://forum.xda-developers.com/showthread.php?t=1745781
2. Instructions on how to flash stuff to and on your phone can be found anywhere, but I prefer to use this for it's simplicity and step by step instructions: http://forum.xda-developers.com/showthread.php?t=1766475
On the screenshot posted by the OP, you can also see the option to flash stock. It's pretty easy to do if you follow the instructions. Also make sure you follow the driver installation procedure in the program.
No! Please upload that firmware to the web!
Post some pictures of it. We're all curious to see what it is. This is a Dev forum anyway
Sent from my Nexus 4 using xda app-developers app
Welcome to the forum. Thread moved. Please make sure you post all questions here in Q&A in future.
Thanks
AvRS
Thanks. Can I find instructions somewhere of how to do the firmware upload?
Sent from my Nexus 10 using xda app-developers app
Here some pictures.
First view
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then moves to
Phone info screen
Sent from my Nexus 4 using xda app-developers app
upload that baseband!! :laugh: :good:
This's gonna be good ...subbed
Sent from my Nexus 4 using xda premium
daddioj said:
upload that baseband!! :laugh: :good:
Click to expand...
Click to collapse
I am totally new this. What does basedband mean?
How do I do that upload?
RWTX said:
I am totally new this. What does basedband mean?
How do I do that upload?
Click to expand...
Click to collapse
I don't know either, maybe PM one of the Devs here. If its something of value i would assume they should be glad to help.
Sent from my Nexus 4 using xda premium
Holy wow... That's the ICS boot animation! We've got something good going oh here
Subbed
Sent from my Paranoid Nexus 4 using Tapatalk²
RWTX said:
I had broken the screen on the Nexus 4 and after a daylong nightmare of pursuading LG and Google that my phone should be repaired in my native USA rather than Australia (the phone I got from Google had a model number for the international market rather than the US market), they finally let me send it in to a US facility to get it repaired. I now received the phone back with the screen repaired (took exactly 14 days and $140).
But when I start the phone it goes into a strange debug screen. After pressing the power button for a some time I get to another, more standard looking screen. But the buttons on the bottom are completely missing (no home, return, or widgets buttons). From there I can only access the settings widget in the top right corner of the screen. When I go into settings I get the following info:
Model Number: Full Jellybean on Mako
Android version: 4.2
Build number:
full_mako-userdebug 4.2 LGEP19
eng.seungju24.choi.20121114.105751 test-keys
Also lots of debug apps seem to be installed, although I have not managed to get to the main screen to actually execute anything.
It seems that LG has replaced the standard OS with another (maybe debug or testing) build that does not work properly on the final consumer
product.
Does anyone have any suggestions? I am concerned that if I try to deal with LG I will be without a phone for another 2 weeks, and based on the
experiences so far I am not convinced that I will not have any further problems.
Thanks!
RWTX
Click to expand...
Click to collapse
Dude upload this to the web before you flash back to factory. This is gold to the devs...
Edit: Lol I see u all already told him this as I read the rest of the thread. U are right kcls this is the ICS boot animation.
Using Tapatalk 2
Plz upload this we would all love to see what this is
Sent from my Nexus 4 using xda app-developers app
Someone please tell him how to do it?
I fail to see how this is "gold"? Yes it is the ICS boot animation, and possibly a different baseband, but what exactly would this achieve? We already have the easiest phone to bootloader unlock and root, what good does this do? I can see if maybe this was an HTC phone that was S-Off with an ENG hboot it would be valuable for S-Off.. but it's not..
It's a debug rom, it may contain useful debug tools from LG that arnt available in release roms.
That and some of us just like collecting "official" roms, please upload if you can OP
Worse come to worse, I'm sure there is a developer here that would pay shipping both ways, of you could hold out a week
I am curious if the phone is " Rooted" ( of course it is if it's a developer ROM) bit I would like to know what the boot loader lists.
Sent from my Nexus 4 using Tapatalk 2
Bump
Sent from my Nexus 4 using xda app-developers app
RWTX said:
I am totally new this. What does basedband mean?
How do I do that upload?
Click to expand...
Click to collapse
Someone get this man the tools to get the images of this off his phone ASAP!!
Do you have windows or OSX?
---------- Post added at 08:08 PM ---------- Previous post was at 07:56 PM ----------
Not sure if anyone knows if there's a new version of ADBRecovery or if this would still work for him. Download the Android SDK (http://developer.android.com/sdk/index.html and USB Drivers if you're in windows), then do this:
Make a nandroid backup:
1. download ADB Recovery -> ADBrecovery v6-1.zip
2. copy the content of the ZIP to your SDCARD (there should be a "recovery" folder and an "update.zip" file, you need to copy both to the root of your SDCARD)
3. download the Android SDK -> Android SDK | Android Developers
4. extract the Android SDK to a folder of your choice
5. on your phone go to "Settings -> Applications -> Development" and select "USB debugging"
6. turn off your phone and start it by holding the camera and power button (a /!\ sign should appear - if it doesn't you're doing it wrong or you have the newest bootloader and should power up the phone using the "X" key on your physical keyboard together with the power button)
7. after you get the /!\ sign press the volume up and camera button
8. from the menu select "apply update.zip" (you can move around using the d-pad and confirm your selection with the d-pad)
9. after the update.zip loads you should be at a similar screen with a bit of extra info on it
10. connect your phone to your PC using the USB cable
11. open the console on your computer (Start -> Run -> cmd)
12. navigate to where you extracted your Android SDK and then navigate to the "tools" directory inside the Android SDK dir
13. write the following commands
Code:
adb shell
nandroid-mobile.sh --backup
It should then ask you for a name for your backup. You can leave it blank or write something of your choice
14. after the backup is done, you can "exit" the adb shell and restart your phone
NOTE: If you need to restore your nandroid backup, just replace the "backup" from step 13 with "restore" and select the name of your backup.
Click to expand...
Click to collapse
Getting the baseband/radio:
Just a quick guide for those who want to extract/pull radio img file from their Nexus Phone.
So, basically, here is what you need to do.
1, conncet via adb
2, Type "su" without the "", just SU, 2 letters.
3, Allow superuser with it.
4, Type "dd if=/dev/mtd/mtd5 of=/sdcard/radio.img" without the "", just those letters in the "..."
5, It should take a few second to copy the file to your sdcard and it will mention that it is successful.
6, When it mention succesfully copied, go to your sdcard with USB MOUNT to your computer.
7, You will find a file name "radio.img"
Click to expand...
Click to collapse
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
FIRST OF ALL THANKS AND CREDITS GOES TO THE FOLLOWING XDA MEMBERS
@fnoji111 for working on the ENG HBOOT in the Droid DNA forum
@Argumentation for creating the flashable zip that I used for this tuttorial
@daddioj for doing the leap of faith and used the ENG HBOOT on his device which lead me to writing this tutorial
NOTE: I created this tutorial because HTC One has different variants. After reading mike1986. article on HTC One variants I realized why I can't install OTA updates with my model ID (MID). Now since we have S-OFF I wanted to get updates from the UK. But since I have a different MID to the UK version, I can't install OTA updates. And this is the only solution I found to work at this time. So I hope it will help people who wants to change their MID
VIDEO LINK AT THE BOTTOM OF THIS POST
REQUIREMENTS:
1: S-OFF
2: KNOWLEDGE OF ADB COMMANDS
3: PATIENCE
PLEASE MAKE SURE YOU PAY ATTENTION TO EVERY STEP ON THIS TUTORIAL
***** I WILL NOT BE HELD RESPONSIBLE IF YOU BRICK YOUR PHONE*****
STEP 1:
Make sure you don't have HTC Sync Manager installed, if you do uninstall it!! Also make sure you have HTC drivers installed!
Step 2:
Go here http://forum.xda-developers.com/showpost.php?p=38180376&postcount=6 and download the Argumentation's zip file
Step 3:
After downloading the PL83IMG.zip you will need to edit the android-info-txt inside. Please see sample picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4:
Now you have to place the zip file in C:\Android SDK\sdk\platform-tools folder. I know some people don't have the same directory as I have so this is just an example. Just make sure you place in the platform-tools folder.
Step 5:
Now connect your HTC One (MAKE SURE YOUR DEVICE HAS PLENTY OF CHARGE) to your PC and start a command prompt in the "platform-tools" folder. The quickest way to do this is (see picture below):
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually
You will not lose S-OFF and still have unlocked bootloader. I suggest that backup all important stuff before doing this I hope it helps.
If the mods feels that this doesn't belong here, please feel free to remove it. Thanks.
Here's a short video that shows how I changed my MID (model ID) on my HTC One
Just a side note: better to edit all kind of text with notepad++.
1) It formats text better (not just one single line)
2) It keeps Unix coding if needed
EDIT 05.12.2013 by the request of user @alray
THIS METHOD WILL NOT WORK USING WINDOWS 8.1
After flashing ENG hboot, Windows 8.1 won't detect the device and fastboot won't work, so you can't change MID and execute the RUU. (win 8.1 drivers issue).
I'll give this a go shortly
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
tyler1234567 said:
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
shadowboy23 said:
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Click to expand...
Click to collapse
Oh ok I got ya. Didn't see that before.
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
If it doesn't belong here then the mods can delete that is fine by me.
EDIT:
Just sent a message to one mod so he can delete this thread if it doesn't belong here.
thank you very much it worked like a charm just changed a tmous mid so far so good waiting to install ota
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
False. How is this not developement. And if this isn't developement then neither is the cid thread, or all the stock rom threads.
shadowboy23 said:
If it doesn't belong here then the mods can delete that is fine by me.
Click to expand...
Click to collapse
No harm, just easier to follow one thread since I am interested in this.
I converted my ATT One to the Dev Edition (hoping that nothing ATT is on m phone now except service), easy since both have the same MID but will be doing this for the PN0710000 soon.
Thank you for the tutorial. :good:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
CheesyNutz said:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
Click to expand...
Click to collapse
Which one? Do you mean the "android-info-txt"? If that's what you meant then you have to put in your current model ID, CID and ROM version..If it's the same as mine then you just copy what is written in the first picture. Just remember that Argumentation's zip file is intended for Droi DNA but all you have to edit id the "android-info-txt" and you don't have to touch the HBOOT.nb0.
A video lesson would be perfect
Tried to do something, but adb is not for me, I guess...
It would be perfect to change from carrier to free uk version..
darenas said:
A video lesson would be perfect
Click to expand...
Click to collapse
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
shadowboy23 said:
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
Click to expand...
Click to collapse
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
Click to expand...
Click to collapse
I see already.
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly..
Click to expand...
Click to collapse
Well my phone has S-OFF and have a unlocked bootloader. S-OFF is a MUST! You will see in the video very clearly what I type in adb/fastboot so I'm pretty sure people can work it out.
Video link is up! It is at the bottom of the OP. I hope it helps people.
Done with OTA :thumbup:
Sent from my HTC One using Tapatalk 2
What's the likelihood of anything happening with the ZTE Maven 3? I understand it's pretty new but I literally can't even find any discussion on it.
I just picked the Maven 3 up today myself and I must admit I'm pleasantly surprised... It performs great considering it was only $30 brand new, and I love the fit & finish of it... Now just gotta try to be patient and hope for Lineage/ResRemix,TWRP,Root,Magisk,etc.... =)
It's apparently going to be $8 shipped from best buy on black friday. I think a lot of people will pick one up even if it were to be just an emergency phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any news?
tge101 said:
What's the likelihood of anything happening with the ZTE Maven 3? I understand it's pretty new but I literally can't even find any discussion on it.
Click to expand...
Click to collapse
Have you found anyone thats rooted it?
Logos Ascetic said:
Have you found anyone thats rooted it?
Click to expand...
Click to collapse
No, I haven't found anything about it still. Hoping for at least roof, LOS would be a nice surprise.
I've found that QDLoader is activated in EDL mode (adb reboot edl; you will know you are in when the screen is off and nothing is happening) but I'm not sure how that's useful for us. fastboot and adb do not work in this mode. Volume down + Power button = FTM (field test mode) but I'm not sure what to do in that mode - you can use adb commands but you can't do anything special like mount system as r/w - no fastboot in this mode either. I also tried the ZTE Axon 7 tuliptool but that didn't detect anything (worth a try I guess). iRoot, srsroot, kingroot (pc & apk) don't root it in the FTM mode or regular OS. I've tried adb reboot disemmcwc thing to disable write protection but that didn't seem to do anything different. adb reboot bootloader only brings you to the regular OS. There is also a recovery, but that really only allows you to wipe data/cache and view logs, etc. (volume up + power).
There is an OEM Unlock option in the developer settings, but I still haven't found a way to get to use fastboot. Looking in the system, there are some debug scripts in the /system/bin folder, as well as busybox (toolbox & toybox included) which is interesting. The device is on 7.1.1 & security update "July 1, 2017" (any later exploits?). In "About", there is also a section called "Additional system updates" which seems to allow installing update packages from root directory on storage card?
I'm stuck there, as I'm not super knowledgeable in the art of rooting. Hopefully someone can figure this out!
Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it. I just want to use it as a music player with Google music. The main things I want to do are get rid of the preinstalled "locked" apps and unlock it to get rid of the activation nags. How did you get the developer options? When I tap on the Android build, I get this big N. For just over $20, I got a music player with 32 gigs for music. Not bad. I would love to get Aptx HD if we are able to get LineageOS or root it and install the codec but it's not a really big deal since I have it on my main phone. I just want to use this at work plugged in.
Tim Elliott said:
Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it. I just want to use it as a music player with Google music. The main things I want to do are get rid of the preinstalled "locked" apps and unlock it to get rid of the activation nags. How did you get the developer options? When I tap on the Android build, I get this big N. For just over $20, I got a music player with 32 gigs for music. Not bad. I would love to get Aptx HD if we are able to get LineageOS or root it and install the codec but it's not a really big deal since I have it on my main phone. I just want to use this at work plugged in.
Click to expand...
Click to collapse
Tap the build number 7 times. It worked for me.
Maven query
First, am I permitted to ask a technical question about this model here? I couldn't find a thread for any sort of Q&A, and starting my own would likely take a week to get a response. If not, kindly point me in the right direction please?
Note: My question is about how to retrieve the encryption key as I adopted my SD card to internal, and now it won't read it suddenly. I believe a file named (expand%s.key) is what contained the key, and I'm not sure how it was deleted. This happened after using Zarchiver and compressing about 700 images into a .zip with ultra compression, 256-bit encryption with password. After it finished the phone rebooted and didn't read the SD card upon boot.
I'm working on a terminal-only approach to rooting using the linux shell. I've got 4 books on linux checked out from the library including a command reference that's about 800 pages thick. If there's a way to root using the command line, I'll find it. Success could take a week or two depending on how many hours a day I put into this. It's also possible that there simply isn't a way to root from the command line only. Wouldn't it be nice though?
Maven root
denny777 said:
I'm working on a terminal-only approach to rooting using the linux shell. I've got 4 books on linux checked out from the library including a command reference that's about 800 pages thick. If there's a way to root using the command line, I'll find it. Success could take a week or two depending on how many hours a day I put into this. It's also possible that there simply isn't a way to root from the command line only. Wouldn't it be nice though?
Click to expand...
Click to collapse
It'd be nice if there were ANY way to root the Maven 2 or 3, I've tried pretty much every well know apk , without PC, & no root. Almost got it 1 time & started to try to remove some crapware & bam reboot.
I'm confused on the custom recovery / root thing. Seems like a chicken / egg ? Need root to install recovery but the root methods on Youtube all seem to start with them all having a recovery installed. You need to get a job but you have no experience, but you need experience to get a job...
Tim Elliott said:
Thanks for the information, Nick. I'm sure a lot of people got these for 8 bucks like I did just to play around with. I have no intention of putting a sim in it.
Click to expand...
Click to collapse
If you want to have some basic data, the Freedompop LTE SIM shows up as an ATT SIM in this device, so it works, even w/o unlocking. can get up to 400 MB of data free per month, along w/free VoIP minutes. While that data isn't going to get you streaming, it's more than enough for some IoT stuff.
Heres a little video i made of the Maven 3 running antutu benchmark.
ZTE Maven 3 ( SIM Mobile Network) Not Working
I am trying to use a ZTE Maven 3 from AT&T(US) in Africa (gift from a friend), but the mobile network (SIM card) is not active after inserting SIM. I've tried to search available mobile networks but I get the error message "error while searching for networks" after it tries searching for about 10 seconds.
My first thought was that the phone is locked to the AT&T network, but it did not prompt for an unlock code. I have had to reset the phone several times just to ensure that it gets to read the network. NB. (I have the network unlock code and have tried using it on the phone through alternate means to no avail) Is there anything I'm missing? I'll be glad to get your ideas. Thanks.
I am working on one also, looks like it might be a while, device is pretty locked up. Spent most the day today with my kali box trying to find any weakness. so far all I have found is that can be hacked with reverse_tcp in metasploit, not much else yet. Played with some Dirty CoW but didnt get to far with that, phone just hard reboots when the scripts are executed. If anyone else working on this wants to collaborate send me a pm.
I dont log on often but I get the notifications when I get a pm in my email
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
000Nick said:
I've found that QDLoader is activated in EDL mode (adb reboot edl; you will know you are in when the screen is off and nothing is happening) but I'm not sure how that's useful for us. fastboot and adb do not work in this mode. Volume down + Power button = FTM (field test mode) but I'm not sure what to do in that mode - you can use adb commands but you can't do anything special like mount system as r/w - no fastboot in this mode either. I also tried the ZTE Axon 7 tuliptool but that didn't detect anything (worth a try I guess). iRoot, srsroot, kingroot (pc & apk) don't root it in the FTM mode or regular OS. I've tried adb reboot disemmcwc thing to disable write protection but that didn't seem to do anything different. adb reboot bootloader only brings you to the regular OS. There is also a recovery, but that really only allows you to wipe data/cache and view logs, etc. (volume up + power).
There is an OEM Unlock option in the developer settings, but I still haven't found a way to get to use fastboot. Looking in the system, there are some debug scripts in the /system/bin folder, as well as busybox (toolbox & toybox included) which is interesting. The device is on 7.1.1 & security update "July 1, 2017" (any later exploits?). In "About", there is also a section called "Additional system updates" which seems to allow installing update packages from root directory on storage card?
I'm stuck there, as I'm not super knowledgeable in the art of rooting. Hopefully someone can figure this out!
Click to expand...
Click to collapse
ZTE phone bootloaders are very secure, unless its part of the ZTE Open project, best we can hope for is a root solution, anything else is a pipe dream or is far far away.
Also not to crush your hopes, a majority of phones now show that OEM Unlock button even though there is not much you can do. Busybox is just toolbox. However that said, If you like I can get you a list of all busybox commands on the phone.
GidgetTheGnome said:
I am working on one also, looks like it might be a while, device is pretty locked up. Spent most the day today with my kali box trying to find any weakness. so far all I have found is that can be hacked with reverse_tcp in metasploit, not much else yet. Played with some Dirty CoW but didnt get to far with that, phone just hard reboots when the scripts are executed. If anyone else working on this wants to collaborate send me a pm.
I dont log on often but I get the notifications when I get a pm in my email
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
ZTE phone bootloaders are very secure, unless its part of the ZTE Open project, best we can hope for is a root solution, anything else is a pipe dream or is far far away.
Also not to crush your hopes, a majority of phones now show that OEM Unlock button even though there is not much you can do. Busybox is just toolbox. However that said, If you like I can get you a list of all busybox commands on the phone.
Click to expand...
Click to collapse
I was also able to gain reverse_tcp meterpeter shell and attempted Dirty CoW with no results (not even a reboot ). Im no expert on Android but perhaps someone could use DRAMMER to bit flip the selinux policy to permissive and or gain temporal root?
FreakofN said:
It'd be nice if there were ANY way to root the Maven 2 or 3, I've tried pretty much every well know apk , without PC, & no root. Almost got it 1 time & started to try to remove some crapware & bam reboot.
I'm confused on the custom recovery / root thing. Seems like a chicken / egg ? Need root to install recovery but the root methods on Youtube all seem to start with them all having a recovery installed. You need to get a job but you have no experience, but you need experience to get a job...
Click to expand...
Click to collapse
LOL. Sorry FreakofN, not laughing at you but if your laughing I'm with ya. I too am playing with a Z835 maven 3 and though my knowledge isn't as advanced to rooting I am learning a thing or two here and there by reading, what I'm finding to be limited, discussion's on the topic related to this particular phone. Now I'm about to boldly reach out to the good people of XDA sporting this particular phone and show my smarts off by asking can someone please tell me where I can find the clipboard on this particular phone. LOL! ?? ROCK N ROLL!
---------- Post added at 09:10 AM ---------- Previous post was at 08:43 AM ----------
Eric1084 said:
It's apparently going to be $8 shipped from best buy on black friday. I think a lot of people will pick one up even if it were to be just an emergency phone.
Click to expand...
Click to collapse
WOW! good deal.
First i want to say Speacial Thanks to @xyz`, @k4y0z, @diplomatic and @ggow who make it possible to get a costum rom on a fire 7(9th gen)!
But i needed informations from more sites to get it work and i want to collect all informations in this Thread to make it easier for noobs like me I hope thats okay, i only collect informations, credits goes to:
@k4y0z and @xyz` for the bootloader hack
@diplomatic for the temp root
@ggow for the lineageos for mustang
So i will show the hole way From Stock FireOs 6.3.1.2 until you boot LineageOs 14.1
In this Guide i will use the Software method to get into bootrom mode. Software method: use mtk-su to do the thing.
Careful: this will break your device… and then you fix it by installing a new OS.
Any OS above 6.3.1.2 needs to use the hardware method!
Here you can find the hardware method: https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
I flash some devices but that was the most difficult. It will help if you have some experience how to flash devices.
NOTICE :
Before you move further, make clear that rooting device -
Your warranty will be void
Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
All your data on device will be lost
Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Make sure you read this guide completely before starting!
This Hardware you need:
Working Amazon Fire 7 2019 9th gen (tested with FireOs 6.3.1.2)
USB cable for Kindle Fire
empty USB drive (min. 2Gb)
computer that can boot from USB drive
Download This Software:
lubuntu-19.10-desktop-amd64.iso # get it here https://lubuntu.net and download the AMD64 version
rufus-3.9.exe # get it here https://rufus.ie
mtk-su_r21.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4971443
amonet-mustang.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4785431&d=1561925516
lineage-14.1-20190827-UNOFFICIAL-mustang.zip # get it here https://androidfilehost.com/?w=files&flid=297948
open_gapps-arm-7.1-mini-20200403.zip # go to https://opengapps.org and choose AMR -> 7.1 -> and a variant of your choice i use mini
Step 1 Prepare Usb Stick
################################
Okay first we make the usb stick ready with Lubuntu.
1.1 Start the rufus-3.9.exe
1.2 choose the Lubuntu image file and push start
1.3 it will ask ISO image mode or DD image mode, choose the DD image mode!
1.4 after that put these files to C:\ :
mtk-su_r21.zip
amonet-mustang.zip
lineage-14.1-20190827-UNOFFICIAL-mustang.zip
open_gapps-arm-7.1-mini-20200403.zip
1.5 Turn off your Computer!
Step 2 Boot Live Linux
################################
2.1 Turn on your Computer and boot from usb and start lubuntu
(2.1.1 If you use wlan connect with it)
2.2 Open a terminal window # (go to "start button" at the left corner choose -> system tools -> QTerminal)
2.3 type "sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot" push enter
2.3.1 it ask you something, say yes
2.4 type "sudo apt-get remove modemmanager" push enter
2.4.1 it ask you something, say yes, if it done close this window
2.5 Click on the "Computer" icon on Desktop
2.6 Search your Windows device and copy the 4 files from step 1.4 to lubuntu home directory (make it easier later)
Step 3 Prepare kindle
################################
3.1 Go to settings and enable developer options (need to push the serialnummber multiple times)
3.2 Go to developer options Enable USB debugging
3.3 Connect kindle to computer
3.3.1 On the kindle,
3.3.2 pull down the menu,
3.3.3 click the USB charging, “tap for other USB options” and select PTP for “transfer photos”
3.3.4 Click Accept to allow permission for your computer.
Step 4 Temporary root (Terminal window1)
################################
4.1 Open the mtk-su_r21.zip
4.2 copy the arm folder to lubuntu home directory
4.3 Open a new terminal window
4.4 type "sudo adb push arm/mtk-su /data/local/tmp” push enter
once successful, run these commands:
4.5 type "adb shell" push enter
4.6 type "cd /data/local/tmp" push enter
4.7 type "./mtk-su" push enter
4.8 type "getenforce" push enter # Just to confirm it says Permissive
4.9 type "echo 0 > /sys/block/mmcblk0boot0/force_ro" push enter
4.10 type "dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8" push enter
Dont close this window!. you will need it in a moment.
Step 5 Bootrom Mode (Terminal window2)
################################
5.1 Open the amonet-mustang.zip
5.2 copy the amonet-mustang folder to lubuntu home directory
5.3 Open a new terminal window
5.4 type "cd amonet-mustang/" push enter
5.5 type "sudo ./bootrom-step.sh" push enter
5.6 Go back to the first Terminal window and type "reboot" push enter
5.7 Go back to the second Terminal, the tablet should restart, and the amonet script will begin to run.
Press Enter to continue, it will start copying things. Should take about 4 minutes.
Once the script finished, the kindle will restart into fastboot mode.
5.8 All you will see if the amazon logo. to verify that the device is in fastboot mode go back to the first Terminal window
and type "sudo fastboot devices" push enter
it will list the device # if it find 1 device you make all right
Step 6 Fastboot & TWRP
################################
6.1 Go back to the second Terminal window
6.2 type "sudo ./fastboot_step.sh"
The tablet will flash some text and do a few things. give it a minute or two.
The tablet will flash and appear to restart, let it do its thing until the screen goes dark.
6.3 Tap the power button twice and TWRP will pop up.
SUCCESS! # TWRP (Team Win Recovery Project) is now installed and can be launched by holding down VOL Down (left most button from pwr) and Power when starting up the device.
(At this point you can try to put the files on a SD Card, but i try it with multiple ones and TWRP dont find one, if you have one that work you can jump to step 8.4)
Edit: or use adblink from here https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Step 7 Set permissions to Copy
################################
7.1 In TWRP on you kindle push wipe -> push Format Data and Swipe to reset
7.2 Now we need to obtain the idVendor of the kindle.
Go to the first Terminal window and type "sudo dmesg" push enter look for idVendor"XXXX", for me, the ID was "18d1".
7.3 Next, you need to give the ”plugdev” group access to the device.
You are going to create a file and then change some permissions then restart the services.
7.4 type "sudo nano /etc/udev/rules.d/51-android.rules" # create the file
7.5 and type the following line: #(Change idVendor to your ID)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
7.6 push ctrl + x , and hit y to save. # push a button and it close but hold the terminal open
7.7 Now assign read permissions on the files, reload udev and reload the adb daemon:
7.7.1 type "sudo chmod a+r /etc/udev/rules.d/51-android.rules" push enter
7.7.2 type "sudo udevadm control --reload-rules" push enter
7.7.3 type "adb kill-server" push enter
7.7.4 type "adb start-server" push enter
(You may have to disconnect and connect again your device to the USB port) # i dont needed it
Step 8 Copy & Install LineageOs
################################
NOW you can copy the files using the adb push command, like we did before.
8.1 type "sudo adb push /lineage-14.1-20190827-UNOFFICIAL-mustang.zip /data/local/tmp/lineage.zip" push enter
8.2 type "sudo adb push /open_gapps-arm-7.1-mini-20200403.zip /data/local/tmp/gapps.zip" push enter
After it finish copying, use TWRP to install the image
8.3 In TWRP push install go to path /data/local/tmp/ # there you find lineage.zip & gapps.zip
8.4 Choose lineage.zip and swipe to install
8.5 After that go back and choose gapps.zip and swipe to install
8.6 if its done you can push "Reboot System"
You are Finaly Done LineageOs 14.1 will booting now! # it will take some time at the first boot
Edit:
Install the "sod-fix-test.zip" by using TWRP you can find it here https://forum.xda-developers.com/showpost.php?p=80621157&postcount=253 @Ziona
(This fix the charge issue)
i find so much usefull things at xda-developers to flashing much devices include this device
So for this device it was really difficult and i was think it will be great thanks when i collect all informations for other(and me for the next time ).
And i think, thats understandable for anyone. I Hope it will help other People too.
Sources:
Unlock & root By xyz` https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Amazing Temp Root By diplomatic https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
LineageOS 14.1 By ggow https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Thanks for the guide, do you know if this also applies to Fire OS 6.3.1.5 ? as I have a fire 7 mustang version
At first start i connet the fire 7 with wifi and it makes a small update to 6.3.1.4 then i make a factory reset with stock recovery and i was back to 6.3.1.2
Try the factory reset if that dont work and you are still on 6.3.1.5, dont try this Guide i only test it with a 6.3.1.2 device!
It's all good, followed your guide and I'm on lineage os now. Thanks again!
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
lucas.lop said:
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
Click to expand...
Click to collapse
Thanks! i edit it! if you find some other things tell me
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Thats a good question
_SWaTcH_ said:
Thanks! i edit it! if you find some other things tell me
Thats a good question
Click to expand...
Click to collapse
I try here with 6.3.1.5 and don't work. I'm with this problem too.
lucas.lop said:
I try here with 6.3.1.5 and don't work. I'm with this problem too.
Click to expand...
Click to collapse
This guide will only work if you are on 6.3.1.2 or below.
MTK-su = Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Is no way out for 6.3.1.5?
lucas.lop said:
Is no way out for 6.3.1.5?
Click to expand...
Click to collapse
Go here for the hardware unlock method-
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Michajin said:
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Click to expand...
Click to collapse
Im sorry that i miss the credit for diplomatic :silly:
I add note that you need to use the hardware method for Os version above 6.3.1.2 and add links to their threads.
Device offline MTP Error
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Yeah it worked perfectly with the hardware hack
Ozed20 said:
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
Click to expand...
Click to collapse
So i think you have install TWRP and you only need to copy the files to your fire 7, Michajin post a other way:
Michajin said:
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Click to expand...
Click to collapse
Worked then broke
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save on memory usage these devices don't seem to come with much to spare. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Additional Info: I had to use the hardware method since reset to factory took me back to 6.3.1.5
DrGuns4Hands said:
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save a memory usage. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Click to expand...
Click to collapse
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Michajin said:
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Click to expand...
Click to collapse
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
DrGuns4Hands said:
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
Click to expand...
Click to collapse
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Michajin said:
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Click to expand...
Click to collapse
Thanks. This is my first time with a custom ROM. I got the tablet just to do chromecast control for my TV in the living room and realized quickly that Fire OS just felt to clunky to keep on the device. Guess I'll be learning how to do update patches since I think that lineage will still be the better solution overall. Any suggestion on where to look to understand how to do the updates? I followed this guide as a step by step assuming it would be the whole kit and kaboodle, so can't really say I understand what pieces I'd need to update or where to look to keep things up to date to the most stable version.