Related
Samsung Galaxy Tab 10.1 is rooted.
Instructions
1. Download the tool from below attachments:
2. Commands to type:
adb push Rooting-Samsung-Galaxy-Tab-10.1.zip /sdcard/Rooting-Samsung-Galaxy-Tab-10.1.zip
adb reboot recovery
3. Enjoy Samsung Galaxy Tab 10.1 as rooted
Complete Tutorial at http://www.techofweb.com/technology/rooting-galaxy-tablet-10-1.html
Credits
I am posting this thread here as initially I posted it in wrong Thread in Samsung Salaxy Tab Android Development Forum sorry for that
10.1 or 10.1v?
Is this a guide to root the 10.1 or he 10.1v?
I hope iets for 10.1v.
Rodus said:
Is this a guide to root the 10.1 or he 10.1v?
I hope iets for 10.1v.
Click to expand...
Click to collapse
i have the same question
10.1 the 10.1v currently can't boot into recovery.
Sent from my GT-P7100 using XDA Premium App
Already covered here
johnblade said:
i have the same question
Click to expand...
Click to collapse
its for 10.1
I fallowed the instruction and got root, however I could not get titanium backup to work. It just says no root and busy box, help please
Thanks so much! This worked great on the Google i/O version.
Question. I'm on a Mac... any way to make this thing so when I plug it into the Mac that it pops up as a USB drive? My Inspire 4G does it, but this one doesn't, so I can't for the life of me figure out how to transfer files to it without using a windows machine.
Also, is it really incapable of charging off the USB port? It'll only charge if I plug it into the wall socket. Weird.
So I just got my gtab and wanted to know is there a file named "sdcard" already on the system? Or will it make one when you push it,,,otherwise how does it know where to go when you push it to the sdcard?
techofweb said:
Samsung Galaxy Tab 10.1 is rooted.
Instructions
1. Download the tool from below attachments:
2. Commands to type:
adb push Rooting-Samsung-Galaxy-Tab-10.1.zip /sdcard/Rooting-Samsung-Galaxy-Tab-10.1.zip
adb reboot recovery
3. Enjoy Samsung Galaxy Tab 10.1 as rooted
Complete Tutorial at http://www.techofweb.com/technology/rooting-galaxy-tablet-10-1.html
Credits
I am posting this thread here as initially I posted it in wrong Thread in Samsung Salaxy Tab Android Development Forum sorry for that
Click to expand...
Click to collapse
camblue said:
So I just got my gtab and wanted to know is there a file named "sdcard" already on the system? Or will it make one when you push it,,,otherwise how does it know where to go when you push it to the sdcard?
Click to expand...
Click to collapse
sdcard is already "pre-installed" (if you will) on the system. The 32gb hdd space is essentially our SDcard on the 10.1 Tab. So yes. There is already a /sdcard/ file on your system.
Used the techniques and files here to get my tab rooted - everything works well. Now we just need to get more devs to do some roms on the vanilla version...Really looking forward to how HC 3.1 will run on the I/O versions...
my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance
wrxphantom said:
my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance
Click to expand...
Click to collapse
I'm guessing that the same root method for the I/O tab (running 3.0) will not work on the release tab (running 3.1).
wrxphantom said:
my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance
Click to expand...
Click to collapse
See this thread: http://forum.xda-developers.com/showthread.php?p=14551458
If someone could tell you how to post a system dump, would you be willing to do it? I don't know how, but I'd be glad to help you figure it out or to try to recruit someone who knows how to do it.
EDIT: here is a general idea of how it is done for another device.
http://android.modaco.com/content/a...-dump-system-and-boot-from-a-standard-device/
BTW, it sounds like the best time to do this dump is before making any changes to the device.
someone can correct me if I'm wrong but I don't think you can make a system dump without having root access
some observations.
no fastboot, recovery wont mount data (so sdcard is not avail.).
working on dumping.
pershoot said:
some observations.
no fastboot, recovery wont mount data (so sdcard is not avail.).
working on dumping.
Click to expand...
Click to collapse
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.
pershoot said:
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.
Click to expand...
Click to collapse
great to know you're working on it. keep it up!
pershoot said:
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.
Click to expand...
Click to collapse
tried flashing through odin. wouldn't take (all was healthy and passed though prior to flash).
investigating why it didnt flash.
they really locked this thing down didn't they!
We're kind of split between two threads, so I'm arbitrarily choosing this one.
Pershoot: Let's get this thing cracked. Can you grab an "adb shell mount" output for me? I'm curious as to how that compares to the I/O model. If there's a partitioning difference, that's going to be another hurdle.
NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G
It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.
I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.
so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
WOW, just WOW, awesome work rbox!
I was definitely not expecting this.
rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)
..
JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm
Rbox do you know if the bootloader can boot from usb?
Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Truly amazing. Can't wait for full fledged android on this.
Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.
jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.
rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Hi, I unlocked the bootloader and it was successfully. Thank you rbox
barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.
Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.
nice, thanks rbox, you rock.
The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?
Fullmetal99012 said:
The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?
Click to expand...
Click to collapse
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...
Txjacob said:
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...
Click to expand...
Click to collapse
I used SUInstaller from the same guys who do sunshine. worked fine for me.
How did you get TWRP installed? I can't seem to get it to work.
As for installing the current build, not really sure I want to do that, since I don't have a backup phone to use right now.
I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html
Txjacob said:
I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html
Click to expand...
Click to collapse
That's where I looked too. did you do the fastboot install? I'm trying the app from the store, but it doesn't list the device.
also, interesting. the SUInstaller worked on mine, but it is hit and miss. not sure how to root it otherwise.
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
glad to hear!
ill have to do the fastboot TWRP when I get home.
not sure what is needed for the One Remix to get CM12 support. HTC has the kernel source for the M7 and M8 online(and even the one Max), but not the remix.
It doesn't seem like a whole lot should be done. The hardware ought to be very similar to the HTC One Mini 2, just has to be adjusted for CDMA rather then GSM.
I tried to flash the current CM 12 build, but TWRP complains about the code-names not matching, and the update script failed. I then had to restore from a backup to get it to boot up to the original firmware.
csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.
u-ra said:
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.
Click to expand...
Click to collapse
what is needed to work on a build? I would be interested, but not sure If i need kernel source or device specific drivers. neither of which HTC dev supplies for the One Remix.
It doesn't appear to be much. I've been digging through the CM Porting Guide, and specs on the phones and they appear pretty similar. They both have the same SoC (Qualcomm Snapdragon 400) and GPU (Adreno 305), but the Remix has 1.5GB RAM instead of 1GB. Haven't had a chance to compare the partition schemes, but Verizon might have made them different... Some things need to be changed in the source of the Mini 2 to make it compatible, but the Kernel should be fine.
What about the Radios? does the difference in Radio CDMA vs GSM change anything major. I'll take a look at the porting guide and see if I can get something booted.
https://github.com/kfechter/android_device_htc_memwl
I forked the memul build of CM and renamed it. any help in grabbing stuff from the Remix would be great (kernels, drivers, recovery images)
One more update.
I've asked HTC for kernel source for the one remix. hopefully HTCDev actually comes through and provides it. hopefully also for Lollipop.
I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.
Txjacob said:
I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.
Click to expand...
Click to collapse
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?
Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks
Fullmetal99012 said:
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?
Click to expand...
Click to collapse
Yes, in TWRP you can make a backup of your current partitions (It just dumps the current partition to IMG files), then if you have a problem you can just restore back from those files.
neuclear said:
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks
Click to expand...
Click to collapse
First, download the TWRP build from the TWRP website, the one in this forum is for the Mini 2 and won't work with the Remix. Then boot your phone into fastboot mode and run "fastboot flash recovery twrp.img" on your computer. Then reboot, and after when you select recovery from the bootloader it should open TWRP.
When I boot into fastboot usb, i enter the command to flash recovery and it says error cannot load twrp.img BUT when i type the same command but add USB after fastboot it loads the commands list. Still cant get it to load. The file name in the Android-adb file is twrp.img as well. Ive done everything correct as far as I know. Any input would be appreciated. thanks.
---------- Post added at 08:06 AM ---------- Previous post was at 07:55 AM ----------
I figured it out.
Went into file Android-adb and did shift right click open command window here. typed the command and it worked on the first try. now its time to develop a rom and make this phone worth something!
For RUUs, stock recoveries, stock Nandroids (in case you need to return to stock, unrooted), TWRP links, and other important tools, please check this thread by Rydah805. It has the stuff you want.
Note: S-Off link at the bottom of the OP. You'll need the HTCDev unlock method completed first and you'll need root access to make it work. So once you're done with this little guide (or the noob friendly one in the HTC One international forums here), you can hop right on over to Sunshine (linked at the bottom) to get that done if you don't mind the $25 fee.
I can confirm this works on the following:
Android 5.0.2
HTC Sense Version 7.0
Software Number 1.32.531.25 (tested and working with software update 1.32.531.33)
Kernel Version [email protected] #1 SMP PREEMPT
Baseband version 01.01_U11440251_64.04.50312G_2_F
Build Number 1.32.531.25 CL505029 release-keys
As usual, you do this at your own risk. It's not my fault if you mess things up (although I sympathize completely if you do). I cannot confirm this works on any other version than this one, although I've seen this work on the AT&T, Verizon, Sprint, and International variants. Feel free to link there or just copy paste the whole damn thing and post it over in those forums to make it easier for those folks. I really, honestly don't mind.
It took me a while so I figured i'd make a thread on it to make it easier for our fellow T-Mobile M9 peoples. This is essentially a link dump so you can get to the places you need to go faster. Before continuing, please read this advice from Rydah805 because it's invaluable. Thankfully, we won't be using the 2.8.5.0 version of TWRP in this quick tutorial but the important part of the message is that you should make a nandroid of the unmodified stock ROM BEFORE rooting. Otherwise you will have many problems down the line. If you have thanks to give, give them to the posters of all these various threads. I did nothing special, just went through the steps to see how it worked.
Please note, if you're using Mac or Linux, I don't use those things and couldn't try/test/use the root method on those platforms. I assume Linux works pretty much the same way as Windows (you'll have to get ADB/Fastboot a different way of course).
Let's get started
Pre-requisites:
1. You'll need SuperSU by Chainfire. You can download it here. Put this on your device where you can find it later. I've seen people say it needs to be on an external SD card, but I've seen it work from both internal and external.
2. You'll need a modified version of 2.8.6.0 of TWRP. You can download that here. The link is at the bottom of the post where it says "Beta version with system backup fixed...". That's the one you want.
3. You will need ADB and Fastboot. I recommend Minimal ADB and Fastboot. You can find that here. Install it like any other Windows application AND MAKE SURE TO LET IT CREATE A DESKTOP ICON. This will make finding it later much easier. Linux users will need to find a different way to get ADB/Fastboot. Probably just downloading the SDK...although if you're running Linux you know all this already so let's just move on.
4. You'll need the HTC One drivers. I did this by installing HTC Sync Manager and it worked fine for me. You can download the HTC Sync Manager here.
Okay now for the actual root method.
1. First you'll need to unlock the bootloader using HTDdev.com. Follow this tutorial to do that.
2. Once your bootloader is unlocked. You'll want to flash the TWRP recovery to your HTC One M9. Rename the TWRP file you downloaded in the pre-requisits it to "recovery" (no quotes, and the .img shouldn't be visible) and place it in the Minimal ADB and Fastboot folder on your COMPUTER. For windows, this is usually under your C drive > Program Files (x86) > Minimal ADB and Fastboot.
3. On your One M9, turn it off. Press the volume down key and power simultaneously and you'll get a black screen. Using the volume keys to scroll, go to Download Mode and click the power button to confirm.
4. On your computer, open Minimal ADB and Fastboot using the icon I told you make earlier (you listened, right? ). If you renamed the TWRP image you downloaded earlier to "recovery" and put it in the proper folder as I stated earlier, then all you need to do is type the following:
Code:
fastboot flash recovery recovery.img
5. At this point the recovery should flash successfully. HOWEVER, in my experience, you may get some silly errors (unknown error, Fastboot crashed, too many links, etc). If this is the case, don't panic. Turn the device off, re-enter download mode again, close the command window and re-open Minimal ADB and Fastboot and try again. All I did to get it to work was try a couple of times over again. Sometimes it goes, sometimes it doesn't. Silly Windows being silly I presume.
6. Okay, you should now have recovery. Enter recovery by pressing and holding volume up and volume down while pressing power to enter bootloader mode. Scroll using the volume keys to "Recovery" and hit the power button. You should now be in a weird looking TWRP. This is normal.
7. CREATE A FREAKING NANDROID BACKUP RIGHT NOW. According to some recognized members of the community, HTC updates only work on an unmodified system. If you ever want to receive official updates from HTC, you HAVE to create a NANDROID RIGHT NOW. Do it. I'll wait.
8. Did you create a Nandroid yet? No? You naught boy/girl, go do that now please.
9. But no really, create a Nandroid please.
10. Once your Nandroid is complete and you have an unmodified, unrooted system backed up, we can actually root the damn thing. You should have SuperSU on your device (as per the pre-requisites). If not, go download that using the link I provided above and put it on your device. Anywhere should be fine.
11. Okay now here's the tricky part. TWRP boots into recovery as Read Only but ONLY on unmodified systems. The reason for this is because HTC updates can't install if the recovery is read/write enabled. Since you're not yet rooted, your TWRP is booting up to Read Only. That means even if you flash SuperSU right now, it won't actually do anything because TWRP can't write to /system (yes, it will say it flashed successfully, it's a liar liar pants on fire).
12. To overcome this, you'll need to follow the instructions in this post.
13. Once you have manually mounted the system partition using the post I linked above (did you thank him? I think you should've thanked him), you may now flash SuperSU.zip as you normally would.
14. Reboot, and you should now be rooted. Don't forget to install BusyBox (search "busybox" in the Google Play Store, download the one developed by Stephen (Stericson). Once installed, open it, give it Superuser permission, then just hit install). Once busybox is installed, you will have the full root experience and can use apps like Titanium Backup.
And that should do it folks. Again, don't thank me, all I did was gather links and put the steps in order. The other people deserve your praise.
Now as for updating, I don't know how it will work yet, but this is how I believe it'll work in theory.
If you have a system update:
1. Create a titanium backup of all of your apps (trust me).
2. Reboot to recovery, restore your unrooted, unmodified Nandroid that I told you literally 5 times to make.
3. Reboot, then check for updates. Install the system update.
4. Re-root your device using the steps above (by then I'm sure there will be a more stable TWRP, make sure you always have the most updated one!)
5. Restore your apps via Titanium Backup.
Again, that's how I believe it should work in theory but I won't know for sure until I receive a system update.
IF YOU HAVE PROBLEMS, please contact the smarter people in the threads I linked who are actively working on helping people with issues. I suppose you can post them here, but as you can see by my post count, I rarely pay much attention
Enjoy!
*Edit*
Bonus points: Our device is compatible with the S-Off method brought by Sunshine. It's a $25 purchase but it does work (tested) and I've seen people report that it works on the .33 update as well. Click here to check out Sunshine.
great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?
Rydah805 said:
great write up. mind making a stock backup with the beta 2.8.6.0 twrp and posting it?
Click to expand...
Click to collapse
I could, definitely. Maybe create a clean one (without my stuff logged in) and upload here...what would I have to include so people could actually use it? I've never tried restoring a borrowed Nandroid backup before lol.
All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
Boot.emmc.win
Boot.emmc.win.md5
Recovery.log
System.ext4.win000.win
System.ext4.win000.win.md5
System.ext4.win001.win
System.ext4.win001.win.md5
System.ext4.win002.win
System.ext4.win002.win.md5
System.info
Click to expand...
Click to collapse
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)
Rydah805 said:
All you need to post is system and boot. You don't need to wipe your info, all of that is stored on the data partition, which we don't necessarily need. So just backup using the beta TWRP 2.8.6.0 you mentioned and zip and upload the following files:
The ".md5" files are only created if you have the generate md5 option on in TWRP. If this option isn't enabled, they aren't necessary.
I hope you haven't used TWRP 2.8.5.0 on your M9 at all. Have you?
Edit:
I'm assuming you have root already and what we need is an untouched system partition. If you haven't touched the system partition then we are good, but if not, don't bother making a backup. The easiest way to check if your system partition is still good to use for OTA's, boot into TWRP and go to the mount options and if "System" is an option, it's no good and a stock backup from that particular device is useless, but if the "System" option isn't there, please make the backup and share it. Lol
Sent From My HTC One (M9)
Click to expand...
Click to collapse
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.
DunningKrugerEffect said:
I followed my exact instructions before I posted them I got my device last night and did all of this today (in fact, I wrote it as I completed each step). I have an untouched /system in my nandroid and my TWRP was only 2.8.6.0. Curiously enough, my Nandroid has a system.emmc.win and boot.emmc.win...will that be a problem? I flashed the 2.8.6.0 modified one that allows for backups beforehand but I don't have ext4 I guess.
Click to expand...
Click to collapse
Must be my setup. Yours should be perfect. Looking forward to downloading a copy. ? thanks in advance.
Sent From My HTC One (M9)
Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.
Prasad said:
Could someone please upload the stock recovery for this phone? I need it because I'm interested in flashing TWRP and rooting the phone but I need the stock recovery in case an OTA update hits.
Click to expand...
Click to collapse
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)
Rydah805 said:
When an OTA arrives, download it and it'll contain the stock recovery. By then, I'll post it...
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks! I tried to flash TWRP and got this:
$ fastboot flash recovery twrp-2.8.6.0-hima.img
sending 'recovery' (35928 KB)... OKAY
writing 'recovery'... FAILED (remote: cannot flash this partition in s-on state)
Click to expand...
Click to collapse
EDIT: Never mind.. Got it to work!
[Q] Any benefit to unlock bootloader only?
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?
Gravityrat said:
So I have rooted many of my phones and just received my M9 last night. Not really interested in rooting it just yet. Although I was curious if there is any benefit to only unlocking the bootloader. or just wait for when I root it?
Click to expand...
Click to collapse
Unlocking the bootloader gives you access to installing custom ROMs, kernels and rooting the phone. You only really need to unlock it if and when you're doing any of these.
Figured as much. I wanna run it stock for a bit to see how it runs. I will admit, I am impressed with the battery life so far. I made it 12 hours at work with 17% left when I got home.
Worked for me. Thanks
Am I missing something? While in recovery, after I've already made a backup(It's uploading) I go to advance>terminal and I type in
Code:
mount -t ext4 /dev/block/bootdevice/by-name/system /system
it returns
Code:
mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Device or resource busy
Edit: Apparently it still worked.
Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive
xxquicksh0txx said:
Here is a TWRP backup of my phone right after I unlocked it, so it should be completely stock. I didn't remove any of the files, so the data files are in there as well. (Again, right after I wiped from unlocking)
Just drag the folder into your twrp backup folder and you should be good to go.
Goolge Drive
Click to expand...
Click to collapse
mind if i link that in my thread?
Rydah805 said:
mind if i link that in my thread?
Click to expand...
Click to collapse
That's what it's there for
:good:
does anybody know if this works on mac?
child0fdecadance said:
does anybody know if this works on mac?
Click to expand...
Click to collapse
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.
Prasad said:
I unlocked, flashed TWRP, backed up and rooted the M9 on a Mac.
Click to expand...
Click to collapse
sweet! did you have to change any of the procedure or did you do it step by step?