At this point it seems that once flashing this you may not be able to revert to a lower firmware without unlocking your BL! This build also may not receive OTAs. So in summary flashing this may cripple your ability to OTA!
URGENT!! Flashing any SBF 1.8.3, 1.5.7, or 1.2.6 using RSD after updating via this method results in permabrick!
http://forum.xda-developers.com/showthread.php?t=1160408
DO THIS AT YOUR OWN RISK!!!! (worked for me and a couple other guys)
No need for this thread anymore Samcripp has put together way better instructions and is receiving way more traffic please use his thread
http://forum.xda-developers.com/show....php?t=1159950
1. Flash 1.8.3 SBF
2. Download file rename update.zip
3. Place file in root of your EXTERNAL SDCARD
4. Reboot into stock recovery and apply update.zip
File is here...
This has been decided to be causing to much damage so the file has been removed. Thread can remain open for support though.
jruweaver said:
DO THIS AT YOUR OWN RISK!!!!(worked for me and a couple other guys)
1. Flash 1.8.3 SBF
2. Download file rename update.zip
3. Place file in root of your EXTERNAL SDCARD
4. Reboot into stock recovery and apply update.zip
File is here...
LINK REMOVED UPON REQUEST
Click to expand...
Click to collapse
Thank you? Im kinda confused why you would want to this, dont we want a unlocked bootloader, not locked?
primeboss said:
Thank you? Im kinda confused why you would want to this, dont we want a unlocked bootloader, not locked?
Click to expand...
Click to collapse
There are still some people out there that have not unlocked their bootloaders, this is for those people.
You linked to "Blur_Version.4.1.83.MB860.ATT.en.US.zip". This is 1.83... not gingerbread.
If it is GB, why the file name is 4.1.8.3?
Sent from my MB860 using XDA App
primeboss said:
Thank you? Im kinda confused why you would want to this, dont we want a unlocked bootloader, not locked?
Click to expand...
Click to collapse
Lol! The thread title means "Gingerbread, for AT&T Atrix phones with locked bootloader" and not "Gingerbread with locked bootloader for AT&T Atrix phones"
polaris441 said:
If it is GB, why the file name is 4.1.8.3?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
When pulled from the motor servers that is the name it downloaded under I assure you its GB.
polaris441 said:
If it is GB, why the file name is 4.1.8.3?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Don't go by the name, it is indeed GB!
Anyone flash that file yet?
Sent from my MB860 using XDA App
Link restored.
jruweaver said:
Link removed due to possible NDA violations. I used this method here to acquire it.
http://forum.xda-developers.com/showthread.php?t=1159320
PM me if you want it
Click to expand...
Click to collapse
How stable is it? What works and what doesn't? Does it have the new Blur? Does the blur work?
Otherwise, thanks for the find. If it's stable - I will try it.
jruweaver said:
Link removed due to possible NDA violations. I used this method here to acquire it.
http://forum.xda-developers.com/showthread.php?t=1159320
PM me if you want it
Click to expand...
Click to collapse
Your link is quoted in the second post! =P LOL
You failed....
Well its GB alright. 2.3.4! Awesome man, thanks!
henrys01 said:
Well its GB alright. 2.3.4! Awesome man, thanks!
Click to expand...
Click to collapse
Did you install it, and do you have a lock bootloader?
Installed. The bootloader is still locked.
Whats the build info on this?
henrys01 said:
Installed. The bootloader is still locked.
Click to expand...
Click to collapse
no root is required is that correct?
Build 4.5.91
Hmmm so is this the official leaked AT&T GB update?
GB 2.3.4 looks amazing .My fingerprint scanner is not working.Not sure if its because of the update because it was not very responsive since the last couple of days. Gtalk is working with FFC !!
Related
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440.
But there's a way to root your 2.2.1 anyways. Follow this guide:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
SuperOneClick works great if you still want root.
KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
Just unlock your bootloader.
I have tried the super one click no luck
Other than unlocking, which is the preferred and safest way to do it. You could just follow the guide that was linked here. I did it for my friend just last week because he was afraid of the official way to root for some reason. It worked perfectly.
Yeah I did it the rageagainstthecage way.
Sent from my Nexus One using XDA App
nope but i read about 2.4 just google for:
google-ice-cream-android-2-4
cant post links
My sig says it all...
KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Odd, are you sure you have the latest Super One Click? It worked fine for me 2.2.1 N1 on T-Mobile.
KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Works fine for me. Did you get stuck at the looping problem after following the steps in the OP?
The way around that, as many of us have discovered, is to turn the phone off then run SuperOneClick and select 'root'. Turn the phone back on once 'waiting for device..' is shown in the program and then just leave it until it finishes.
Ensure USB debugging is enabled before you get started and that your PC has the required drivers installed. (Check Device Manager).
To be fair the Original Post needs updating as the instructions aren't very good without the above being mentioned.
DirkGently1 said:
SuperOneClick works great if you still want root.
Click to expand...
Click to collapse
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
Using exploit to root allows you to get rooted device without unlocking the bootloader. However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).
frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
This does not unlock the boot loader....... and, yes you can flash roms once rooted.
Good luck on that warrenty buisness.
LFact said:
However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).
Click to expand...
Click to collapse
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?
frandavid100 said:
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?
Click to expand...
Click to collapse
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer
rcknr said:
Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440
Click to expand...
Click to collapse
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App
hircus said:
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer
Click to expand...
Click to collapse
His question isn't about relocking the bootloader. But as long as you reflash the stock ROM and recovery, then I don't think there would be a way to tell without further examination. Regardless, HTC isn't too strict with the warranty claims, as many members on this forum have claimed warranty and sent back rooted phones to HTC. You should be fine.
andynx1 said:
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
that's 3 weeks. "coming weeks" being a PR equivalent of more than a month, we should be waiting for gb another 2 weeks at least...
It's only 5% of GB, but you can have the keyboard from it. A definite improvement and works perfectly on my N1 with 2.2.1 (no root needed):
http://www.appbrain.com/app/keyboard-from-android-2-3/com.moo.android.inputmethod.latin.free
ruu 5.07.651.1 already release?
Honeywell said:
ruu 5.07.651.1 already release?
Click to expand...
Click to collapse
No. It hasn't been released. However, the OTA has been pushed, and is available here for manual application if you are a stock, unrooted user, running the stock recovery.
If you're rooted, there are a few stock rooted versions of the 5.07 update in the Development forum.
Yep, they already have an Odex and DeOdexed version under Evo 4G development..
ahh ok but there is a zip file like RUU can use a SD Card? like PC36IMG to software my fone like a brandnew one?
Honeywell said:
ahh ok but there is a zip file like RUU can use a SD Card? like PC36IMG to software my fone like a brandnew one?
Click to expand...
Click to collapse
Like I said before, no, not yet.
Captain_Throwback said:
Like I said before, no, not yet.
Click to expand...
Click to collapse
how about yet??
my father accidentally updated his rooted/unlocked bootlaoder with HTC DEV
and i got the boot loader re-locked, but i need to take it in for warranty service.
i need HELP!!! thank yoU!!!
mike4slund said:
how about yet??
my father accidentally updated his rooted/unlocked bootlaoder with HTC DEV
and i got the boot loader re-locked, but i need to take it in for warranty service.
i need HELP!!! thank yoU!!!
Click to expand...
Click to collapse
Nope, this RUU never surfaced. You can still downgrade the misc partition to normalize the watermark, as detailed in my 2.18 HBOOT instructions.
You'll just have to HTCDev unlock again first.
I know this is a really old thread, but I'm having related problems. My usb port isn't working and I need the newest 5.07 update in a PC36IMG.zip form. Is there any way you can post one? It would be a great help.
Sleepycloud said:
I know this is a really old thread, but I'm having related problems. My usb port isn't working and I need the newest 5.07 update in a PC36IMG.zip form. Is there any way you can post one? It would be a great help.
Click to expand...
Click to collapse
Nothing has changed. This RUU doesn't exist.
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
HBogard said:
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
Click to expand...
Click to collapse
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
aviwdoowks said:
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
Click to expand...
Click to collapse
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
HBogard said:
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
Click to expand...
Click to collapse
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
HBogard said:
.....
Click to expand...
Click to collapse
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
aviwdoowks said:
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
Click to expand...
Click to collapse
It wasn't your fault for trying to help, so it's ok. I'm glad a solution existed.
I'm more than willing to answer the questions, but I am a layman here so please explain some things for me: What do you mean by SW? I just installed the update by going into about phone -> system update on Wifi. The carriers here don't even support 3G, much less 4G (So now you know why Wifi was important for me).
The phone came unlocked day one when I bought it from a friend's friend. I don't know if he did it that way or if it comes unlocked because it is the developer edition.
I installed CW Recovery using Fastboot. I installed the incorrect superuser file using Motofail which wrote the superuser file but failed at all other steps. I was then unable to either access or remove this superuser apk file.
Since I am back on 4.0.4. now, what's the easy way to get root access and superuser permissions that you mention? I wish other XT902 owners would post here too, generating interest would really help in getting development support for this phone.
HBogard said:
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
Click to expand...
Click to collapse
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
HBogard said:
It.
Click to expand...
Click to collapse
Once you root on 404 you can grab your update.zip & copy it to your sd . Any rooting exploit would evolve from that Or the newest xml ver of the 404 you just flashed from rsd. You may be able to request it from your carrier.
---------- Post added at 01:21 PM ---------- Previous post was at 12:40 PM ----------
You can paste the mods from my vzw restore (no vzw software will be used) into the 404 xml & obtain root from a preinstalled cwmr! Then maintain root with voodoo for your ota.
I will help you just read the op. Link is in my signature.
HBogard said:
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
Click to expand...
Click to collapse
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
http://www.aosp.us/wp-content/files/Root.zip <- This one.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
aviwdoowks said:
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
Click to expand...
Click to collapse
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
HBogard said:
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
Click to expand...
Click to collapse
I'm an idiot and forgot the link...
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my Nexus 7 using Tapatalk 4
HBogard said:
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
Click to expand...
Click to collapse
Can you upload the xml only ~ 1kb
UPDATED:
Please jump to the following thread for information on root/lollipop:
http://forum.xda-developers.com/shield-tablet/help/qa-root-shield-tablet-2-0-lollipop-t2945163
garyd9 said:
There's some misinformation going around concerning lollipop (android 5.0), root, and the SHIELD tablet. I'm posting this (redundant) information to (hopefully) clear things up and prevent someone from causing themselves a headache after the tablet updates...
nvidia has stuck very close to AOSP in their tablet firmware updates, so it's a reasonable assumption (at this point) that the new firmware will also be very close to AOSP.
If that comes to be, then "rooting" the tablet will be more difficult than in previous firmware updates. Most of the gory details can be found in this G+ article by @Chainfire : https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
(BTW, as always, a huge thanks to Chainfire for his efforts. If you haven't already, paying for the upgrade to "SuperSU Pro" is well worth the price if for no other reason than to encourage Chainfire to continue work on that project.)
If you don't understand the details of that post from chainfire, I'll try to summarize it: Even if you manage to get a copy of the "su" binary on your system partition (which is essentially the goal of all the older root exploits), it won't matter much in Android 5.0. In Android 5.0, we'll ALSO need a part of the kernel image changed (the ramdisk) so that a part of "superSU" can run at a more permissive context.
Updating the kernel ramdisk shouldn't be too difficult (if its compressed with the kernel in a normal way) once we have the image to play with. As well, in order to put the newly modified kernel image in place, a person would have to unlock their bootloader (which can void your warranty.)
Actually, it's possible (once the image is released by nvidia) that @Chainfire will stick the image on his server in one of his very easy to use "CF-Auto-Root" bundles. (Hopefully, all the @ references I've made will get him to look at this thread and confirm what I've said. The honest truth is that I'm NOT familiar with SELinux, so I'd have to do a bit of experimenting to get this working.)
Take care
Gary
Click to expand...
Click to collapse
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Keithn said:
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Click to expand...
Click to collapse
That Google plus post I linked to describes the needed change.
Sent from my SHIELD Tablet using Tapatalk
Okay, thanks. I guess I didn't catch that.
Sent from my One M8
Root successful!
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
SuperPichu said:
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
Click to expand...
Click to collapse
With a modified recovery or stock ?
matyas69 said:
With a modified recovery or stock ?
Click to expand...
Click to collapse
CWM. The instructions are up in the lollipop update thread
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
Is this root sticking?
whoamanwtf said:
Is this root sticking?
Click to expand...
Click to collapse
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
I'll wait root without custom recovery
SuperPichu said:
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
Click to expand...
Click to collapse
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
whoamanwtf said:
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
Click to expand...
Click to collapse
Testing right now. How should I test these? i.e. What do you use them for?
SuperPichu said:
Testing right now. How should I test these? i.e. What do you use them for?
Click to expand...
Click to collapse
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
whoamanwtf said:
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
Click to expand...
Click to collapse
No problem.
Results
Folder Mount - Made a link from internal to external and the link seemed to be working correctly (files put in one showed up in the other)
Titanium - Backed-up, uninstalled, and restored Netflix successfully with no errors
Here's a link to the root instructions. http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Please post any questions there.
Works for both locked and unlocked bootloaders now.
SuperPichu said:
Here's a link to the root instructions. http://forum.xda-developers.com/showpost.php?p=56854633&postcount=77
Works for both locked and unlocked bootloaders now.
Click to expand...
Click to collapse
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Keithn said:
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Click to expand...
Click to collapse
I was starting to wonder how I was the only person (or at least the first) to have that idea.
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
onduck said:
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
Click to expand...
Click to collapse
No if you unlock your bootloader you can follow my unlocked instruuctions.
onduck said:
Is it too late to follow the instructions to unlock my bootloader at this point?
Click to expand...
Click to collapse
no. Not too late.
Sent from my HTC One_M8
Hope this helps out. This was after I unlocked bootloader and re-setup my phone (so there are some apps installed). Total unpacked size is 3.26GB, zip is 1.52GB.
Folder - https://drive.google.com/folderview?id=0B5fMrmukgO0NeG12S1U1TlJNX1U&usp=sharing
Full Pull Zip - https://drive.google.com/file/d/0B5fMrmukgO0NOE0zRGZBenNVSDQ/view?usp=sharing
Sorry for the seemingly noob question, but I've unlocked, rooted, installed ROMs, and modded system directories for many years but am unfamiliar with system pulls. What is the purpose of this and how can it be used on the new T-Mobile V10? Thanks.
Sent from my Nexus 6 using Tapatalk
branedamig said:
Sorry for the seemingly noob question, but I've unlocked, rooted, installed ROMs, and modded system directories for many years but am unfamiliar with system pulls. What is the purpose of this and how can it be used on the new T-Mobile V10? Thanks.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It can't. It's just a dump of the system partition. Usually benefits people with other devices looking for something off this device. Maybe an updated app or lib.
As soon as @TheJesus and I can get online at the same time we might be able to come up with something...
You guys are quick. Just got mine on JoD, but don't want to do too much until we have a way to return to 100% stock.
Very cool!
Sent from my LG-H901 using Tapatalk
KAsp3rd said:
As soon as @TheJesus and I can get online at the same time we might be able to come up with something...
Click to expand...
Click to collapse
If there is anything you guys need from me, LMK.
mikeyinid said:
If there is anything you guys need from me, LMK.
Click to expand...
Click to collapse
what is the sku # for this device?
Rydah805 said:
what is the sku # for this device?
Click to expand...
Click to collapse
Sku #?
rydah805 said:
what is the sku # for this device?
Click to expand...
Click to collapse
sku #: 610214643872
TheJesus said:
sku #: 610214643872
Click to expand...
Click to collapse
I looked and couldn't find it lol. Where did you get it for future reference?
mikeyinid said:
I looked and couldn't find it lol. Where did you get it for future reference?
Click to expand...
Click to collapse
On the box, lol
Sent from my LG-H901 using Tapatalk
TheJesus said:
On the box, lol
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Bahaha, that was the first place I looked
If someone could modify this to be able to prompt me for an unlock code when I enter a different SIM card, I would be very, very happy. Apparently T-Mobile does something to stop the prompt from coming up, and I want to be able to unlock it almost immediately. I'm on my way to get the phone now, but I don't want to come home with a useless paperweight.
Apparently a similar stock ROM was created for the LG G4 as it had the same problem. I would love to see a ROM for this once TWRP is publicly released for the V10!
TheJesus said:
On the box, lol
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
mikeyinid said:
Bahaha, that was the first place I looked
Click to expand...
Click to collapse
lol thanks guys
ubergeek77 said:
If someone could modify this to be able to prompt me for an unlock code when I enter a different SIM card, I would be very, very happy. Apparently T-Mobile does something to stop the prompt from coming up, and I want to be able to unlock it almost immediately. I'm on my way to get the phone now, but I don't want to come home with a useless paperweight.
Apparently a similar stock ROM was created for the LG G4 as it had the same problem. I would love to see a ROM for this once TWRP is publicly released for the V10!
Click to expand...
Click to collapse
i thought you had to wait at least 15 days since you been using the device to qualify for sim unlocking your phone. tmobile told me that on the phone before.
TheJesus said:
Hope this helps out. This was after I unlocked bootloader and re-setup my phone (so there are some apps installed). Total unpacked size is 3.26GB, zip is 1.52GB.
Folder - https://drive.google.com/folderview?id=0B5fMrmukgO0NeG12S1U1TlJNX1U&usp=sharing
Full Pull Zip - https://drive.google.com/file/d/0B5fMrmukgO0NOE0zRGZBenNVSDQ/view?usp=sharing
Click to expand...
Click to collapse
How do you do a system.img pull if you dont mind me asking through adb?
TheJesus said:
Hope this helps out. This was after I unlocked bootloader and re-setup my phone (so there are some apps installed). Total unpacked size is 3.26GB, zip is 1.52GB.
Folder - https://drive.google.com/folderview?id=0B5fMrmukgO0NeG12S1U1TlJNX1U&usp=sharing
Full Pull Zip - https://drive.google.com/file/d/0B5fMrmukgO0NOE0zRGZBenNVSDQ/view?usp=sharing
Click to expand...
Click to collapse
I have 1 question, is it possible to make a custom rom with the full .zip you uploaded?