Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"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"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.
Related
Ok guys, first of all I have to say that you cannot access recovery without something like quickboot -or- rom manager so please get your preferred app for this.
I AM NOT LIABLE IF YOU SOMEHOW MANAGE TO **** UP A ONE CLICK APP! Do not ask me for support. Learn something and fix it yourselves.
Next, I will say that AlbertWertz will be making a video, but this is -really- simple.
All you do is click the button corresponding with what you want to flash.
I will work on aesthetics later but for now, it works, checks md5's, and flashes the images.
Problems:
None with my app, however there are sure to be a few bugs on the recovery. Also: this flashes to internal, that's why I included a reset to stock button!
How to fix a borked install: CLICK ME CLICK ME FOR THE FIX!
(Note, you need superuser otherwise not a damn thing will happen!)
Download link:
here
Instructions:
Just click the button that has the recovery you want to flash. It's really simple. Screenshots, credit, and changelog will be posted in the next post.
Wait 10 seconds for the flash to finish then you can reboot if you want.
Please don't mirror
Changelog:
Code:
2.1: Updated with 1.4.3 stock image and the 6.x CWM image.
2.0: Cleaned up the code, added better md5 checking now it won't flash without a good md5.
1.5.5: Fixed md5 hash checking
1.5: Added Reboot Recovery button
1.1: Fixed filename issue for stock recovery
1.0: Initial release.
Credit:
Code:
nemith for the recovery
myself for the image of stock and designing the app
Screenshots:
{
"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"
}
This is my post.
dropbox not working i get error 404 page popup.
Also if we flash the CWM from xboxes thread do we need to uninstall it then flash this one?
Oops! No one could have flashed the stock recovery back because of the simple screwup I did. I didn't have a properly named file. ^_^ Anyway, it was fixed.
promek said:
dropbox not working i get error 404 page popup.
Also if we flash the CWM from xboxes thread do we need to uninstall it then flash this one?
Click to expand...
Click to collapse
It was still uploading. It's done now.
Also no, you shouldn't have to uninstall his CWM. It's the same image, just simply flashes over the old one. It just helps to be able to flash whatever whenever you need it.
dumb question
which one is better to flash, or can you do both
and then switch between on boot
cuz on my xperia x10, i can switch between, both on boot...
Stock recovery is what you need if you plan to use the unroot method, etc. CWM is used for custom software / firmware flashing...No, you can't switch between. You flash CWM if you want to flash zips and if you want to have stock recovery again which doesnt give you a menu, you flash stock.
I'll probably end up packaging my root mods into the flashable zip. I'll see if cfoesh or whatever wants to package up snowball mod.
Indirect said:
Ok guys, first of all I have to say that you cannot access recovery without something like quickboot -or- rom manager so please get your preferred app for this.
Click to expand...
Click to collapse
Hey, wanted to say thanks and wanted to say this: flashed CWM and at first I couldn't access recovey with n+Power, but now I can. Tried shutting down and then n+Power, nothing. Then used ROM Manager's "reboot into recovery" and it booted like normal instead of going to recovery.. then ROM Toolbox and used and "shutdown"... Started back up with n+Power and it worked. Tried again a few times with normal boots and shutdowns, then n+Power and it goes to recovery.. Hoping I remembered exactly what I did but hey, it works like it should on any device now
EDIT-Oh, apparently if I let go of the power button too quick then it doesn't go into recovery... just tried again with quick letoff and booted normal even though I had the 'n' button firmly pressed the whole time.. Gave it a 2 second count next time before letting go and went into recovery
Sent from my BNTV250
Donation sent. Thank you Indirect! I appreciate your efforts.
Update will be pushed out to add a reboot recovery button to the app.
Indirect said:
Update will be pushed out to add a reboot recovery button to the app.
Click to expand...
Click to collapse
What method of recovery did u use internal or sd and also I been seeing all this cool stuff on getting recovery to work but yet can't find the simplest way to root lmafo. Well thank bub and **** haters keep doing u on here and people will soon realize what's the real deal. But thanks again. Just been lurking till its the moment to unwrap that baby and be in love
Sent from my PG86100-EVO3D-using Tapatalk Born Jan 5th 84 and still getting it in eeee
As requested, i have cleaned this thread.
Peace!
Indirect said:
Update will be pushed out to add a reboot recovery button to the app.
Click to expand...
Click to collapse
Thanks again for another great project Indirect, i will wait until the update i trust more in you at the time of releasing such of complex things, though i dont know if its possible yet but have you think about a menu for normal reboot, hot reboot, reboot to recovery and shutdown when you long press power button instead of cancel and shutdown options? that would be an awesome project. Take it as a proposal/request to anyone that can help in make it possible .
Peace!
~ Veronica
Edit: I just realized that all the signature pics went down, weird my twitter logo disappear ... now they are back lmao
Update was just published, same link, just download it.
lavero.burgos said:
Thanks again for another great project Indirect, i will wait until the update i trust more in you at the time of releasing such of complex things, though i dont know if its possible yet but have you think about a menu for normal reboot, hot reboot, reboot to recovery and shutdown when you long press power button instead of cancel and shutdown options? that would be an awesome project. Take it as a proposal/request to anyone that can help in make it possible .
Peace!
~ Veronica
Click to expand...
Click to collapse
Yes I have that on my Asus transformer, like you say it has all the different options in one popup menu. Much more straight forward
Thing is, if it's a sizeable thing to code, is it going to be worthwhile considering cm7/9 is hopefully not far away ?
I know CM9 development seems to have halted (nothing updated on OP in a decent while) but it could still be a lot of work for something that will only be used for a very short period of time.
technically, i should be able to use this to flash back to "complete stock" (including removing cwm)?
It's used to either flash over stock recovery, or over CWM. Depending on which option you choose. It's the same process, just different files. That's it.
Fantastic work. You've made it easy to do and I thank you!
Sent from my ADR6300 using xda premium
Working with a net--restore is working!
Many thanks to bauwks, nemith, goncezilla, and indirect for bringing clockwork mod to the NT. I'm a thorough-going noob and always will be, so I've been waiting for a custom recovery so I could have a nandroid backup to save my hide (and my ui) when I go a-themin'.
For example, I just hacked up my framework-res to try to get rid of some horrible list separators, which of course completely broke the tablet. Power-N, restore from internal sd card, and I'm ready to break things again.
Thanks!
The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Mistake 1: google account has nothing to do with unlocking. If you have fastboot access you're unlocked! so forget mistake 1 and 4
Mistake 2: no comment except that i don't understand what instructions you followed from the net, the cmd part... A backup is performed within CWM ... Nevertheless you're bricked so it isn't very important.
Mistake 3: a big mess in your head. If you just unlocked and flashed cwm it's logical that you are not rooted in your ROM. CWM has nothing to do or care with root !! CWM is totally independant from the ROM, it has by default root power as it runs froms a different partition and deals with /system and /data etc from 'outside'.
You gain root by either flashing a custom ROM (they are all rooted) or flashing the super user itself only (SU.zip).
Mistake 4: don't use cwm on that device.
Mistake 5: you are a monkey typer.... STOP trying every crap you find 'on the net' ! You seem to have quite blurred knowledge of what is an android device, so be extremelly carefull or you'll end with a real hard bricked prime.
Prime is very specific, don't use things that have not been designed specifically for it.
You are in recovery bootloop, see in dev section the unbrick thread (in stickies threads), option 1a.
Don't use cwm.
Use TWRP.
big time noob said:
The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Click to expand...
Click to collapse
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/showthread.php?t=1782413
Download and install http://forum.xda-developers.com/showthread.php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here ....http://forum.xda-developers.com/showthread.php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/showthread.php?t=1774352
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
johanjonker said:
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
Click to expand...
Click to collapse
Your welcome ... I think.... did I get you out of a jam?
I dont troll I try to help people from what i have experienced..... I myself have made some questionable decisions.... just figure since I have learned from them .. no reason to make others suffer through needless anxiety......
big time noob said:
The Good:
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Click to expand...
Click to collapse
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Very valid point Mithrandir007.... just to be cleear when following the nvflash instructions.... follow step by step.... all the way to the end..... from this thread http://androidroot.mobi/t3_nvflash/ dont stop until you see the statement ... coming soon... then you are actually done....
Thanks
Thank you guys for your help, and not being too hard on me...except maybe the first guy.
I will try those things when I get back from work.
Seriously...
Gage_Hero said:
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
Download and install naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here .... this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions...
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
Click to expand...
Click to collapse
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
It comes vaguely in my mind that I read something about cwm not supporting charging but I'm not sure.
If the battery is drained completely it will need several minutes with wall charger to come back to life.
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
big time noob said:
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
Click to expand...
Click to collapse
Some usb connections don't charge... my pc at work is like that.... or they charge so little that it barely makes a difference. Plug it into the wall for at least a hour... preferably longer since you are going to be doing things that may not work out so well if the battery dies in the middle of things.... Also given how frail the charger socket is, unless you have it sitting on a flat surface, I wouldn't attempt doing the work while it is plugged in... Would want you to get the software fixed and you bust up the charging socket or cable...
Prime needs 15 volts to charge, USB only delivers 5, so it's discharging while plugged to an USB most of the time.
Don't know how to fix your CWM problem but I do know the Prime will charge on a USB port if it's turned off. It does take a very long time though.
From the TF201 manual:
{
"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"
}
Might help
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Thanks for the response. On the nvflash page it says NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
Does that mean me? If so, I might be stuck.
I tried installing with the update.zip option, didn't work. I also tried installing by browsing, but weirdly, it does not give me the options of any of the roms I have on the SD card...when the prime was stock, it saw the files on the SD card, but now it just shows me options of several folders that do not actually exist, a couple of subfolders, but no actual files or zip files.
When I boot (holding the power and down volume button) The message basically says, The device is unlocked, Android cardhu-user bootloader. Says something about the version I was running, .28, and that it is looking for an ota update. At the bottom, it says booting recovery kernel image. Then it loads clockworkmod.
I installed the naked drivers, so I can now see the Android ADB interface on my windows device manager. I cannot see the device as one of the drives from windows explorer.
I hope that info helps. What do you think? How screwed am I still?
rr0yy said:
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
Click to expand...
Click to collapse
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
2 things:
1. I cannot see the sd card in the mount/unmount area of CWM. I feel like this is a big part of my problem.
2. The instructions I see for nvflash involve fastboot. I could be wrong, but if I cannot get to the fastboot screen on my prime, how can I run the fastboot command lines? I can only get to the cwm screens.
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
Attached 2.1.2 twrp....give it a go....
Just recently purchased Bungbungame MiSS (Tegra 3, nice screen) etc. Have unlock bootloader, but cannot seem to get root access. su is not in system/bin or system/xbin directories and when I attempt to use su in SSH I get a permission denied. Cannot mount as "read-only file system".
Thanks in advance for any help
DT
I have the MiSS as well, just started trying to look at how to root it. Appreciate any info you find.
BUMP...
Anyone figure out how to root one of these Bungbungame MI100 tablets yet? Just got mine today. Pretty sweet for the price, just need to get ROOT!
bumpbumpbumpbump!!!
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
[/COLOR]Enter Recovery Menu
Hold down power and volume up at the same time, then as soon as the screen flashes on, let go of the power button and you should see something like this in the left top corner OTA....... start pressing the volume down button and volume up simotanously about 4-5 times then it will enter recovery menu. Next i will try to push the crystal root method through recovery in adb push update to see if that roots.
{
"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"
}
ok that didnt go well i ended up getting a android with an exclamation mark
but also wanted to note that im on my windows 7 machine and i already had the manufacture drivers installed working in regular adb mode....and when i was in the cmd and my device was in adb sideload mode it wasnt being recognized, so i looked in my device manager and i had a exclamation by my miss device. The tablet usually works perfectly fine when im booted up and in adb cmd no problems with the drivers at all, im able to log cat and read my device HOWEVER when im in adb and my tablet is in recovery adb sideload all of a sudden the drivers werent acting right and i couldnt communicate with adb cmd and my device.......so what i did was googled apx no driver found because the message coming up when the drivers were trying to be detected was just that "apx no driver found" so i have this link here http://forum.xda-developers.com/showthread.php?t=1998650 and downloaded it and then went to my devices and updated the drivers under the MiSs driver and after installing it made my driver name into google android driver...then i went back to cmd adb and i was able to sideload the update file to my device..... The update zip installation was aborted but at least i know how to sideload in adb now with the correct driver needed. When i rebooted my device into regualr mode and plugged it into my pc my device manager reads miSS still...and when i jump back into sideloading through recovery menu my manager device puts me back under google driver blablablabla so i guess you guys will probably need this driver too if you want to do some work....its made for Universal TEGRA devices.
I also used these commands to sideload and placed the update.zip where i was pointing to the adb.exe heres the link
http://www.droid-life.com/2013/02/12/guide-how-to-use-adb-sideload-to-update-a-nexus-without-root-or-custom-recovery/
dtippey said:
Just recently purchased Bungbungame MiSS (Tegra 3, nice screen) etc. Have unlock bootloader, but cannot seem to get root access. su is not in system/bin or system/xbin directories and when I attempt to use su in SSH I get a permission denied. Cannot mount as "read-only file system".
Thanks in advance for any help
DT
Click to expand...
Click to collapse
how did you unlock the bootloaders? Did you do this manually with Linux or did you use a program?
BungBungame Has a safemode
Im not to sure what i can do in safe mode with this True Android 4.1.1 bungbungame device but i managed to get into safemode heres what i did..
1) download this root method (RootDebugfs) http://forum.xda-developers.com/showthread.php?t=1706588 and select root (your device will reboot, and freeze at bungbungame logo)
2)Hold both volume up and volume down then release volumes and click them simutanasouly now your device is in safe mode.
here is a picture of safe mode..
BungBungame bootloader menu
When i was connected to adb i entered command "adb reboot bootloader" and i got this menu...also instead of power button being the selection button in the menu the select button is volume up and volume down cycles through the selections power button does nothing.
here is a picture of the menu
unlock MiSS bootloader
No4g4Me said:
how did you unlock the bootloaders? Did you do this manually with Linux or did you use a program?
Click to expand...
Click to collapse
think this link worked - just a variation
at addictivetips.com
look for
what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide
DT
dtippey said:
think this link worked - just a variation
at addictivetips.com
look for
what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide
DT
Click to expand...
Click to collapse
yup that worked thanks i did
STEPS TO UNLOCK BOOTLOADER:
1)adb devices (Type this in ADB, device read)
2)adb reboot bootloader (Type this in ADB)
3)fastboot oem unlock (Type this in ADB)
4)select unlock it (bootloader unlocked sucessfully)
5)reboot device (all user data gets wiped)
note**i had to boot into recovery mode after unlocking bootloader and wipe data/cache (because it frozed)
Yea unlocked bootloader thanks again. Have you tried motochopper root method after unlocking bootloader?
im going to try it now, before it wouldn't
ROOTED SUCCESS!!!!
1)Download Motochopper (http://forum.xda-developers.com/showthread.php?p=40747604)
2)Extract Double click RUN.bat
3)Rooted
YESSSSSSSSSSSSSSSSIR
No4g4Me said:
yup that worked thanks i did
STEPS TO UNLOCK BOOTLOADER:
1)adb devices (Type this in ADB, device read)
2)adb reboot bootloader (Type this in ADB)
3)fastboot oem unlock (Type this in ADB)
4)select unlock it (bootloader unlocked sucessfully)
5)reboot device (all user data gets wiped)
note**i had to boot into recovery mode after unlocking bootloader and wipe data/cache (because it frozed)
Yea unlocked bootloader thanks again. Have you tried motochopper root method after unlocking bootloader?
im going to try it now, before it wouldn't
ROOTED SUCCESS!!!!
1)Download Motochopper (http://forum.xda-developers.com/showthread.php?p=40747604)
2)Extract Double click RUN.bat
3)Rooted
YESSSSSSSSSSSSSSSSIR
Click to expand...
Click to collapse
AWESOME!!! That root method worked for me as well. Thanks for the efforts!!! Now, does anyone think there is there a custom recovery that would work with this?
j36047 said:
AWESOME!!! That root method worked for me as well. Thanks for the efforts!!! Now, does anyone think there is there a custom recovery that would work with this?
Click to expand...
Click to collapse
i think the asus tf201 has the same pit tables so i was going to try and use their recovery from rom manager but im afraid of brick cause its the recovery so instead im going to dump this command in
adb shell....
su......
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
The reason why i say it might work is becuase when my evo shift 4g didnt have a custom recovery the forums said just to use the evo 4g from rom manager. So i did and i was able to flash install and back up successfully. So im tempted to just flash the asus tf201 thing is theres no coming back if the device wont boot recovery like the evo shift 4g had a .exe flash program for recovering to stock in emergencies unlike this bungbung
since my mods and tweaks applied I have amazing performance and battery life I've been using it for about 9hrs straight.I'll post a battery log later.didn't have time for this round which is only the first since the first rooted charge, battery calberation, also use deep sleep battery, and greenify
No4g4Me said:
i think the asus tf201 has the same pit tables so i was going to try and use their recovery from rom manager but im afraid of brick cause its the recovery so instead im going to dump this command in
adb shell....
su......
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
The reason why i say it might work is becuase when my evo shift 4g didnt have a custom recovery the forums said just to use the evo 4g from rom manager. So i did and i was able to flash install and back up successfully. So im tempted to just flash the asus tf201 thing is theres no coming back if the device wont boot recovery like the evo shift 4g had a .exe flash program for recovering to stock in emergencies unlike this bungbung
Click to expand...
Click to collapse
Yea, I noticed that Rom Manager seems to think this is a tf201 and I was very tempted to try flashing the recovery for it but seriously don't want to wind up with an expensive brick.
j36047 said:
Yea, I noticed that Rom Manager seems to think this is a tf201 and I was very tempted to try flashing the recovery for it but seriously don't want to wind up with an expensive brick.
Click to expand...
Click to collapse
yea your right brick it will be, its actually a miss evaluation on my part the exact brother for this devices processor is the T30 Tablet
Motochopper works! What apps/ mods do you recommended.
No4g4Me said:
yea your right brick it will be, its actually a miss evaluation on my part the exact brother for this devices processor is the T30 Tablet
Click to expand...
Click to collapse
Motochopper works! What apps/ mods do you recommended. Would really like to extend battery life.
Thanks
dtippey said:
Motochopper works! What apps/ mods do you recommended. Would really like to extend battery life.
Thanks
Click to expand...
Click to collapse
Add busybox latest version.Inside romtoolbox the functions that worked are, boot animation, and font changer works, xposed app and xposed install (change the launcher app to DPI 190, Fullscreen and you get a nice size icon going on + put always potrait mode orientation, ill post a screen for that.) Pimp my Rom app use universial Init.d support to activate that, add block and system tweaks for network, VM Heap size, ect....just dont mess with the kernel or cpu because that will lock up your device then you have to reboot then the setting dont stick and also dont apply any flashable mods or tweaks because you dont have a custom recovery yet. The apps to save battery life are DS Battery Saver and Greenify.I got my device up to 4400 one time. Custom kernel would be cool clock it to 1.6 vroooom
Ok, so anyone else's GPS failing to lock after rooting? It sees plenty of satellites, but the notification icon never blinks as if it's trying to lock and no love actually locking on.
Sent from my MiSS using xda app-developers app
j36047 said:
Ok, so anyone else's GPS failing to lock after rooting? It sees plenty of satellites, but the notification icon never blinks as if it's trying to lock and no love actually locking on.
Sent from my MiSS using xda app-developers app
Click to expand...
Click to collapse
it didn't happen to me but I used pimp my ROM app to lock onto my GPS its a mod with in the app. try it out. I did have a few apps force close on me since I rooted they don't want to launch they just kick me out without any error message. but those apps are like a few games I never play anyway.
Howdy all!
What's this? Read on, dear reader, to discover the magic that is PurpleDrake.
{
"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"
}
What is this?
This is a utility to easily root your LG G3 (specific models only). It's a fairly foolproof script that includes all the dependencies you'll need for getting your phone rooted easily.
This is the LITE version. This means that this version will only ROOT your phone. If you have a T-Mobile G3, we'd suggest you look for the full version in this same forum on XDA, since that will root, install TWRP, and prevent your root checker from showing your phone as rooted!
Click to expand...
Click to collapse
Who made this?
This root is a collaboration between myself (IOMonster), jcase, and autoprime.
Special thanks also to beaups for some initial guidance looking at the vulnerable application.
Click to expand...
Click to collapse
Is my phone compatible?
The new LG G3 models each are slightly different with regards to rooting and unlocking.
The vulnerability we're exploiting for PurpleDrake has actually been present on quite a few LG phones for some time, and as such this script will automatically detect if your phone is capable of rooting with this method.
To see a matrix of which LG G3 phones are compatible with this root, please see this Google Docs spreadsheet that we've compiled.
When you run this program, your phone will reboot and run a test to see if it's compatible. If the application succeeds, it'll let you know that it's able to permaroot you. If not, it'll fail gracefully and reboot you back to normal Android without having changed anything.
Click to expand...
Click to collapse
How do I use this?
WE NOW SUPPORT WINDOWS! YAY ME
To start, for either platform you'll need to scroll down to the download section and get the file.
Ensure that your phone is in ADB mode (PTP Mode for everyone but Verizon. Verizon users need to be in "Internet"/"Ethernet" mode)
Linux Instructions (in a terminal!)
Extract the file you downloaded...
tar xvf ~/Downloads/PurpleDrake-Lite_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-Lite
chmod +x purpledrake_linux.sh
./purpledrake_linux.sh
OSX Instructions (just a bit easier)
Extract the file you downloaded
Double-click on "purpledrake_osx"
Windows Instructions
Extract the file you downloaded
Double-click on "purpledrake_windows"
The application will guide you through all the steps you need.
You will still need to install SuperSU from the market after installing PurpleDrake. This pack does not include one.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254062&postcount=2
Click to expand...
Click to collapse
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
Where do I get this?
WINDOWS/OSX/LINUX VERSION OUT NOW!
- Fixed Windows support
- Fixed OSX ADB issues not detecting phone first try
- Fixed race conditions leading to errors permarooting
- Added 64-bit Linux ADB
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R01.tar.gz[/url]
Please DO NOT mirror or re-upload the PurpleDrake software to your own site, or any other file host.
If you need drivers for Windows (thanks @autoprime for having these handy!):
Verizon Drivers: http://downloads.codefi.re/autoprime/LG/LG_G3/LG VZW_United_WHQL_v2.14.1.exe
Everyone Else: http://downloads.codefi.re/autoprim...leDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
Click to expand...
Click to collapse
Help, it doesn't work!
Post here, let us know what happened and we'll try to help you. DO NOT private message us on XDA or on IRC asking for help. We will not assist privately.
Most questions if not answered here can be answered on #lg-g3 on IRC in Freenode.
Click to expand...
Click to collapse
Thanks so much! How can I show my appreciation?
Since this was a collaboration project, proceeds that are made from this root will be split between amongst us so we can purchase a Sprint test phone to root (as it's currently not rooted).
If you'd like to donate to us, click the "Donate to me" button on the left sidebar under my name, and be sure to enter a comment to let us know that you're donating towards the PurpleDrake project.
Thanks again!
Click to expand...
Click to collapse
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
Look, instead of rushing to take an OTA to get the latest software.. think for a moment.
We do no know if the bootloader will stay "unlockable" in future updates. OTA's can update not only software..
but the boot stack as well.. enabling features to block downgrades.. close exploits.. and all sorts of fun stuff.
so.. instead of taking an OTA.. wait for the files to get posted so we can look at things first.. possibly only updating /system, /boot, /modem (maybe tz/rpm)
without updating the rest of the boot stack. ya... do that. Plan on making a lil thread on this soon to make things easier.
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
img files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
I have made a new thread on EFS backup and restore which can be found [URL="http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329"]HERE[/URL].
[/HIDE]
[B][SIZE="5"]Restoring Stock / Remove root flag:[/SIZE][/B]
[HIDE]
Download the tmo .tot file and use lg flash to restore it to stock. itll format everything on internal sdcard so backup anything u may need off it.
T-Mmobile firmware can be found [URL="http://downloads.codefi.re/wolfgart/LG_G3/D851"]here[/URL]. Thanks to [user=608699]@wolfgart[/user] for the files and [user=1157052]@thecubed[/user] for codefire hosting.
*Step by step picture guide - [url]http://imgur.com/W83hMPE[/url]
install the drivers.
put phone into Download Mode (power off. unplug USB. pull battery. put battery back in. press/hold Volume Up then plug in USB cable.)
In Windows Device Manager set the phones serial COM port to #41. (*see picture guide for help)
Install LG Flash. In "C:\LG\LG Flash" folder delete megalock dll. Replace with .dll below.
new megalock dll - [url]http://bit.ly/1cQADXm[/url] (this site includes a "download manager.. UNCHECK THE BOX before downloading dll file.)
Run LG Flash in the "C:\LG\LG Flash" folder. Select korean factory if asked.
When LG Flash opens you will see a box to select firmware and dll.
Select LG Flash (.dll).
Select (.tot)
Hit OK (*see picture guide for help)
Hit yellow start button. If you get Milkyway error click ok. LG Flash will then run a crc check on the tot file. Takes a bit.
After crc check finishes unplug the phone. plug phone back in. it should now be seen in LG Flash and start flashing.
Phone will reboot when finished. You may end up on a screen with s "2"... let it sit there for a minute or two.
If stuck on "2" try unplugging the usb cable from the phone.. wait 10 seconds.. then plug the usb cable back in. now wait 30 seconds and hopefully it changes to a "3"
Once the phone says "3" you can unplug the USB.. remove the battery and plug back in.. boot back up... you are now 100% stock.
[/HIDE]
Yes ROOTS!!
this will work for sprint?
Sent from my LGLS990 using XDA Free mobile app
---------- Post added at 11:51 AM ---------- Previous post was at 11:47 AM ----------
mrkrabs said:
this will work for sprint?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
ignore that question I just read alil bit
Sent from my LGLS990 using XDA Free mobile app
any possible release dates for F/G FWs?
can someone explain if there are any differences between towelroot, ioroot and purpledrake? the end result is the same, no?
cnn888 said:
can someone explain if there are any differences between towelroot, ioroot and purpledrake? the end result is the same, no?
Click to expand...
Click to collapse
towel root doesn't work for some phone that have taken firmware updates and ioroot doesn't work on D851 and purpledrake does
Thanks for the awesome work, devs!
Has anyone figured out what the hidden menu code is for the vzw vs985, to be able to turn off ota? Plugging in "985" for the model number doesn't work.
Will there be a method to turn off/reset root counter for those of us who used IOroot?
thecubed said:
I won't quote the whole OP
Click to expand...
Click to collapse
I can confirm that it worked on the D855 euro (10A). so you guys can go ahead and remove the question mark if you want. Also if you give me the right commands I can check if the 855 eur bootloader comes unlocked or not(google doesn't know them )
For me relaunching two times worked with d855 european version v10g leaked. But what about TWRP for D855?
lukemo said:
For me relaunching two times worked with d855 european version v10g leaked. But what about TWRP for D855?
Click to expand...
Click to collapse
I just hope that lg doesn't try to fix this exploit
Hidden menu for Verizon?
autoprime said:
ioroot is better
much thanks to iomonster jcase and dees_troy. glad i could play a part in this rad-ness.
I would be careful taking OTA's.. wouldnt want to lose an unlock(too early to say..)
Disable OTA:
Open LG Hidden Menu --> WLAN Test --> OTA Setting --> OFF
(This worked on LG G2.. hopefully work on G3 but won't be confirmed until OTA comes out)
Hidden menu = 3845#* then model then #.. so 3845#*851# --> 3845#*850# --> 3845#*855# etc etc
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
iimg files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
[B]Backup:[/B]
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
[B]Restore:[/B]
adb shell
su
dd if=/sdcard/modemst1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/modemst2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2[/FONT]
Click to expand...
Click to collapse
Is there a different method for the Verizon models? I tried this but could not access the menu.
this root method works on 10G
http://forum.xda-developers.com/lg-...wrp-root-twrp-tmo-lg-g3-t2821005/post54258277
ofcourse using the corresponding file for d855 from THIS thread.
Thanks !!! Good work!!!!
Works with D855 10g on os x
Enviado desde mi LG-D855 mediante Tapatalk
Works on the F400S. Probably the easiest thing I have ever done in my life.
Is there a way to check root on LG G3 though? I don't see the SU app, though I can use Titanium Backup without a problem.
epikvision said:
Works on the F400S. Probably the easiest thing I have ever done in my life.
Is there a way to check root on LG G3 though? I don't see the SU app, though I can use Titanium Backup without a problem.
Click to expand...
Click to collapse
just download the app root checker from the store.
Sent from my LG-D850 using XDA Premium 4 mobile app
Yeah....I learned how to read! Had the waiting for device issue on Ubuntu, figured it out on the other thread.
Guys,
who tried this method with European D855 (3/32) model with E/F/G fw's but also taking a TWRP from the thread with full package?
[ROOT / TWRP][D851 ONLY] Root/TWRP your TMO LG-G3 with PurpleDrake!
some say it's for D851 only, is it true?
Who tried it on D855? Does it work?
MarvinFS said:
Guys,
who tried this method with European D855 (3/32) model with E/F/G fw's but also taking a TWRP from the thread with full package?
[ROOT / TWRP][D851 ONLY] Root/TWRP your TMO LG-G3 with PurpleDrake!
some say it's for D851 only, is it true?
Who tried it on D855? Does it work?
Click to expand...
Click to collapse
The d855 have a locked bootloader, that's why it will not work!! No recovery for us, at the moment!! We have to wait.
Gesendet von meinem LG-D855 mit Tapatalk
john0699 said:
The d855 have a locked bootloader, that's why it will not work!! No recovery for us, at the moment!! We have to wait.
Click to expand...
Click to collapse
I thought recovery goes to recovery partition, and locked bootloader have nothing to do with it, isn't it?
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
UPDATE: [8/2/16] I have recompiled the binary with some fixes beaups made. These fixes should take care of the "samsung device only" error some are getting on 4.4 roms.
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
You must unzip the file first.
Download
Code:
adb push unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n3
chown root.root unlock_n3
./unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Your the best. Trying it right now
Sent from my SM-N900V using Tapatalk
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
ryanbg said:
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
Code:
adb push samsung_unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n3
chown root.root samsung_unlock_n3
./samsung_unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./samsung_unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Click to expand...
Click to collapse
Perfect thanks so much ..this is tremendous [emoji120] [emoji120] donations are required. Donate to whom just breathed life into a great phone..Flashify idea by @alexp1289 was great idea to install recovery..this is f### ING awesome
Sent from my SM-N900V using Tapatalk
Awesome! Trying this now!
Cheers,
B.D.
God you are a life saver, I've been trying to get my uncle hooked up with a phone with a unlocked bootloader for awhile,
now he can use his current phone for it.
Does this work for v4.4.4 and 5.0?
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Do the commands HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
jellyhead said:
Does this work for v4.4.4 and 5.0?
Click to expand...
Click to collapse
Yes.
BackCheck said:
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Click to expand...
Click to collapse
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
Gl17ch said:
Do the command HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
Click to expand...
Click to collapse
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
tomixnscale89 said:
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
Click to expand...
Click to collapse
Do a battery pull and run the second step again. It will say "backing up loaders" when it is actually done.
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
It works, I have TWRP installed. I'll be divvying out donations come payday.
BackCheck said:
It works, I have TWRP installed. I'll be divvying out donations come payday.
Click to expand...
Click to collapse
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
BackCheck said:
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
Click to expand...
Click to collapse
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
Yep just download the app and select the one in the pictures.
Download link for Flashify--
https://play.google.com/store/apps/details?id=com.cgollner.flashify
{
"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"
}
Sent from my SM-N900V using Tapatalk
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
I got sick of using dd to reinstall recoveries on my LG V500. There are one or two other apps I've seen that do this but this one always worked for me.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
https://twrp.me/devices/samsunggalaxynote3qualcomm.html
You still can download it manually. Read the notes and it shows the verizon note 3 supported.
Just confirmed good old "dd" method works fine and recovery boots nicely. Make sure you pick the correct version at the twrp website.
Now on to bigger and better things! Will donate!
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
I'm supposing that if I am running 5.0 the 4.4 TWRP will not work...
Once I get this to work will I be able to downgrade to 4.4/install a custom recovery/etc. ?
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
Sent from my SM-N900V using XDA-Developers mobile app
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
App flashify installs Twrp easy. All there no searching works beatiful
Sent from my SM-N900V using Tapatalk