Hi all,
I have been going on xdadevelopers a lot and have received so much helpful information. Now, I decided to give in my contribution to the forum. This is my first tutorial so there might be some mistakes...please be easy on me.
The reason I write this tutorial is because I have not found a good one yet on the internet. Although this thread "Just rooted my remix mini" provided some information, but I feel like a more detailed tutorial would be appropriate. So here we go!
Success screenshot:
{
"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"
}
Credits: all credits goes to these two links and authors:
http://forum.xda-developers.com/remix/remix-mini/rooted-remix-mini-t3311736
http://23pin.logdown.com/posts/435610-root-remix-mini
Requirements:
- Difficult level: Medium
- Tools:
+ Small screw driver
+ Scissors
+ A USB flash drive.
+ Thin metal wire.
+ Serial Converter (I bought on Amazon.com)
- Software:
+ Appropriate driver for the serial converter. Mine is CP2102 driver. Download here. If your serial converter use PL2303 then download this driver. You can google for your specific driver as well.
+ CoolTerm. Download here
+ SuperSU. Download here
- A lot of patience.
Steps:
1. As you can see, I stripped the wire and cut it in small pieces. As long as it is metal wire, that's okay.
2. Open up the Remix Mini with a screw driver.
2a. Flip it up side down, and rip the rubber ring out. It's okay, it will still adhere to the case afterward. Once you ripped it out, you will see two screws holding the remix mini. Proceed unscrew them and gently take the case apart.
2b. Gently take the case apart:
3. Connecting the serial converter to the board.
3a. Plug the 3 metal wires into RX, TX, and GND cable endings of the serial converter.
3b. Connect the other ends of 3 mental wires into RX, TX, and GND of the board.
3c. Make sure connection as such: RX to TX, TX to RX, and GND to GND. This part took me a lot of patience because the wires kept falling off. So please try to keep them in place.
4. Install appropriate serial converter driver.
5. Plug the serial converter into PC.
6. Extract and open CoolTerm.
6a. Click Options -> Serial Port -> Hit "Re-Scan Serial Ports" so it detects the appropriate port for serial converter. Mine is COM3.
- To find out, go to Device Manager -> Ports
6b. Select the right port. Then change the setting as in the picture:
Baudrate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Click to expand...
Click to collapse
6c. Go to tab Terminal -> Select Line Mode.
6d. Hit OK.
7. Power Remix mini up (make sure this happens or you will get serial 103 or 104 error code)
8. Hit Connect button in CoolTerm.
8a. If you have done everything correctly until here, texts will appear in CoolTerm as your Remix Mini booting up.
8b. The texts will keep flowing up. Wait until you only see CPU readings. Then proceed to next step.
9. Download the UPDATE-SuperSU-v2.46.zip file. (Please double check the zip's file name. In my case, I am using SuperSU version 2.46)
9a. Copy UPDATE-SuperSU-v2.46.zip file onto flash drive.
9b. Extract the downloaded "UPDATE-SuperSU-v2.46.zip", from the extracted, go to META-INF/com/google/android/update-binary, copy "update-binary" file onto flash drive.
9c. Make sure you have 2 files, UPDATE-SuperSU-v2.46.zip AND update-binary, on the flash drive.
9d. Plug the flash drive to Remix Mini.
10. Commands: (copy each line and paste into CoolTerm)
Code:
/dev/tty.usbserial 115200
mount -o rw,remount /
mount -o rw,remount /system
mkdir /tmp
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-v2.46.zip /data/local/tmp [COLOR="Red"]<- Double check zip's file name and try Storage02 if Storage01 does not work because it depends on which usb port you plug the flash drive in. [/COLOR]
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
cd /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip
reboot
11. Success. :victory::good:
11a. Wait for Remix Mini booting up, optimizing app..and DONE! CONGRATS! You have now voided your Remix Mini's warranty and cannot receive OTA system update anymore.
I have not figured out how to update manually but please hit me up if anyone knows how.
11b. Download Root checker to verify.
GOOD LUCK!!!!!! :good:
I'm gonna wait for an easier way..
This has got to be a joke.
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far.
Note: first boot takes longer than factory. Be patient. Jide will know it has been hacked so no support for updates but the opportunity to customize was worth it for me.
robot_head said:
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
I tried everything..even Baidu Root...nothing works...I am happy that I can do so many things with the Remix Mini now...rooting it was a genius decision lol
Major kudos, this is a true root method for all the hardware hackers out there. You've never truly "hacked" until you've tapped into a UART console. Very exciting!
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
bullet25 said:
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
Click to expand...
Click to collapse
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
unloseking2500 said:
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
Click to expand...
Click to collapse
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Sounds like a software issue. Someone else had a recovery partitionfrom Jide search maybe they could upload it.
bullet25 said:
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Click to expand...
Click to collapse
Interesting...yeah, try oncouch1's method..try to recover from a partition..see if it helps?!
oncouch1 said:
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far..
Click to expand...
Click to collapse
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Yoswin said:
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Click to expand...
Click to collapse
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
...
oncouch1 said:
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
Click to expand...
Click to collapse
Thanks for reply. I don't think the method can hard brick my device any way. The box itself can be flashed via a PC program made by CPU manufacturer (Amlogic here) and I have both stock firmware and Remix OS firmware images. So I think it's gonna worth a try. Thanks any way for your comment.
Keep us posted, may need one of those!?
Okay got my remix replaced. New remix updated to latest update then did root. It started boot looping. Had to run these commands in coolterm turing a boot loop.
Code:
mount -o rw,remount /system
dd of=/dev/block/by-name/system if=/data/local/tmp/system_image
Don't know if that was the latest update to cause that or what but its all working now. Also was able to easily install the google play services again and get playstore.
Of course I once again broke the power button because that wire is hanging on by a thread.
Apologies for the noob question but what does a root on the Remix Mini allow someone to do with regards to OS options and what are the other advantages?
vinicioh23 said:
I'm gonna wait for an easier way..
Click to expand...
Click to collapse
Please see this: https://secure.avaaz.org/en/petitio...tters_Users_need_root_access_to_remix_mini_1/
Just wanted to give a thanks it worked perfect for me...Just want to add that if you happen to use a built in serial port on an older pc or laptop don't forget to put a ttl converter on your port, or your console screen will be garbage printing out
Related
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"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"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
{
"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"
}
Introduction:
After months of research and development, both hardware and software... I'm happy to announce UnBrickable Mod is a matter of modifing your phone once, with a single small wire. From that point on, you can click a button to unbrick. This can even be applied to a phone which is already bricked.
This is an example from the Captivate. The procedure is the same on the Vibrant.
Instructions
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device:http://forum.xda-developers.com/showthread.php?t=1273083
2. Run UnBrickable Resurrector: Get it from THIS POST: http://forum.xda-developers.com/showthread.php?p=17135277#post17135277 This will only work on linux currently. Install Linux or dual boot if you have windows.
3. Run Heimdall One-Click http://forum.xda-developers.com/showthread.php?t=1278683
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
conclusion
You've unbricked the unbrickable captivate... This should not have been difficult. If it was, you should learn teh computer better... Really. And with that said, I'm happy to announce that you no longer have to flash with a fear of bricking.
HIBL
The HIBL is the key to resurrecting a S5PC110 based processor. I'm going to let Rebellos explain the inner workings of the Hummingbird Interceptor Bootloader. It's really quite amazing. While my work is more hardware and high level tasks like making things into one-clicks, Rebellos' work involves reverse software engineering, assembly language, and more...
Rebellos said:
Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
Code:
�������������������������������������������������� ����������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.
Click to expand...
Click to collapse
Tools
Windows32 command line app and drivers http://forum.xda-developers.com/attachment.php?attachmentid=709292&d=1315091521 (doesn't work very well... just want you to know this)
Linux one-click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=712232&d=1315349672
Wow. i mark it! thank you for your great work!
I just resurrected a Vibrant today using the method above. This tested great. No problems to note at all.
Here's a picture of my work http://forum.xda-developers.com/showthread.php?p=17896376#post17896376
This is slightly more difficult then a captivate because there is no room to work around the resistors.
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Aneez1990 said:
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Click to expand...
Click to collapse
You're welcome. Glad this helped.
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
younix258 said:
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
I'd like to see Ubuntu. Turn these devices into a lamp server or security/web cam orsomething when were done with them.
I would also like to see work on Ubuntu. is there any work being done for that? I'm still thinking about getting the UB mod sometime soon.
Hey guys Im having a problem with step #2. It says to download Unbrickable Resurector but this post is the HIBL post with no "Unbrickable resurector" download link. Is that just an error or do I just download the file listed on the previous post called "UltimateUnbrickResurector.zip"? Thanks for any clarification...
Also, when I launch the resurector on the previous post I get the following error smdk-usbdl: not found. Do I need to have Heimdall running prior to launching the resurector? Thanks again...
Code:
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Building command list
Building command list
Requesting Permission to access device/tmp/skorpnHeimdallOneClick51336EBC/Script.sh: 3: /tmp/skorpnHeimdallOneClick51336EBC/UnBrickPack/smdk-usbdl: not found
Moved this post to the "Mod" thread.
The Resurrector is not working, either because the mod was done incorrectly, or my Ubuntu machine has been setup wrong. The Resurrector keeps giving me the smdk-usbdl: not found error, but the file exists. My best guess is that the Mod was done incorrectly, either that or my Linux box is being a pain... Also noticed adb not working as well.
EDIT: Im going to go out on a limb and say this error is telling me the "usb device" has not been found, which would mean my mod did not take.
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
dohandrew said:
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
Click to expand...
Click to collapse
If you're asking, you will want to find someone more experienced.
i see where would u suggest going to ? im located in california i dont really know of a place that does welding on phones
Adam will do it for $30 + shipping, PM him.
Atleast thats what hes said (correct me if im wrong)
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
SkOrPn said:
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
Click to expand...
Click to collapse
Yes I do. No it doesn't.
AdamOutler said:
Yes I do. No it doesn't.
Click to expand...
Click to collapse
Excellent Im on 11.10, and thanks for the info...
I was able to remove the resistor and replace it with another resistor from an old samsung phone. I used a circuit writer pen from radio shack, it lays down a conductive polymer, which I used to adhere the new resistor onto the bottom spot on the board. "the resistors are so small I could not imagine being able to do this with a soldering iron. I would have probably shorted something out because the amount of solder that needs to be laid down might not even fit on an ants back (seriously!)"
Another note: when using resurector, my phone only went into download mode if I pressed on "only" the volume down button.-I hope this helps someone out there with a brick like the one I had.
Does that mean after applying this mod the vibrant will never brick at any cause ???
galaxyfitftw said:
Does that mean after applying this mod the vibrant will never brick at any cause ???
Click to expand...
Click to collapse
yes that is the meaning of this mod....is just awesome
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
jadengore said:
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
Click to expand...
Click to collapse
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
1wayjonny said:
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
Click to expand...
Click to collapse
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
agrabren said:
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
Click to expand...
Click to collapse
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
AndrewNeo said:
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
Click to expand...
Click to collapse
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
PR0XIDIAN said:
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
Click to expand...
Click to collapse
The issue with the touchscreen is the driver. While it runs great in Android, it doesn't work in recovery, making a touch-based recovery a nightmare. Believe me, I already tried for a few days. I'm sure with enough time, I could get it working, but I didn't want to invest that much time with all the other things on my plate at the moment. I just don't expect recovery to come out this week with touch.
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Fix Fastboot issues on Windows 8: http://www.youtube.com/watch?v=XSisjVwcPbE
wwjoshdew said:
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
Click to expand...
Click to collapse
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
1wayjonny said:
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
Click to expand...
Click to collapse
haha. She's a trip though. Thanks a lot dude, you don't see to many "screen captures" that show the computer rebooting and everything! lol
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Evo_Shift said:
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Click to expand...
Click to collapse
I had the SAME PROBLEM! I uninstalled the drivers, and chose from the list manually! Eventually you choose have disk and there is a long list of things. Find NVIDIA Fastboot from that list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Evo_Shift said:
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Click to expand...
Click to collapse
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
wwjoshdew said:
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
Click to expand...
Click to collapse
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
I finally got it. I am pretty sure it is because of incorrect adb drivers getting auto installed on me when I plugged in the Shield. I wish you could force Windows not to autoinstall drivers when you plug something in and instead always choose your own location. Once I deleted enough of the incorrect drivers and installed the correct drivers to the SHield again it seems to work.
1wayjonny said:
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
Click to expand...
Click to collapse
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
hmm...
I have only "Nvidia Shield" not Nvida Shield ADB in my devices Manager - adb is enabled
Code:
adb devies
List of devices attached
(none)
wwjoshdew said:
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
Click to expand...
Click to collapse
Had this issues so I installed the "manual" way and still commands wont work in fastboot
Edit: followed the video as opposed to the sceenshots above. Good to go now.
1wayjonny said:
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Click to expand...
Click to collapse
Is APX mode available on NVIDIA Shield? I've used APX mode before on my Notion Ink Adam (Tegra 2), but I have read that the OUYA (Tegra 3) has APX mode encrypted or something so you would have to know the key to use it.
Would be nice to have APX mode on the Shield, but probably not necessary.
~Troop
This is only first part. In this part, I will NOT mention any OSes. I will teach you how to run rEFInd on this device.
In other parts, I will edit rEFInd's config file to make it really "work". BUT, after this tutorial, you may fell happy that dual boot will most likely work on the device you just hod in your hands.
This guide is for me176cx only. Steps for other devices may be similar, only try to do this on other devices if you are sure you know where the differences are and how to change the commands!
So let's begin!
My tablet before doing anything
{
"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"
}
on http://www.rodsbooks.com/refind/getting.html , click on get binary zip file
Extract the downloaded zip
look for the folder "refind" inside the extracted folder
////////////////////////////////////////////////////////////////////////////
Now, we need to move it to Efi System Partition.
Istall busybox. Then, install Android Terminal Emulator.
Using some file browser with root rights, make a folder in the root of your device's memory called "esp"
Then, mount Efi System Partition on it:
Run the Android Terminal Emulator, type su, and confirm the SuperUser dialog.
Then, type: busybox mount /dev/block/mmcblk0p3 /esp
it should have no output.
Then, copy the "refind" folder to file system root.
Then (using terminal emulator) copy the refind folder to the ESP.
Then, make sure it is really there
Then write: busybox umount /esp
///////////////////////////////////////////////////////////////////////
Now, add rEFInd's binary to bootorder and set the bootorder to !!!NOT!!! boot it first, becouse you have to test it first (and you do not want to run and buy the first powered hub to be able to get back in android some complicated way)
Download this file and move it to some location where you will execute it from:
http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
(Thanks to social-design-concepts for compiling this to work on android)
Issue this command (the paste function does not work in terminal emulator so you have to rewrite it by hand)
Then, make sure the path is set well:
Then, set the boot order to boot Android first by ./efibootmgr64 -o 0001,0000
Then, set the next boot (only next boot) to rEFInd
////////////////////////////////////////////////////////////////////
Now, just power off the tablet, (do not restart) and power it on again. You will see rEFInd, but you cannot do much without powered hub.
So if you have one, look around with keyboard. If you do not have one (like me), just power off the tablet by holding the power button, power it on again and wait for the next part of this tutorial
EDIT:
tuxic001 edited rEFInd binary so you can select what to boot.
http://forum.xda-developers.com/showpost.php?p=62463032&postcount=60
\\\_///
P.S If you use nandroid backup to update, you only update kernel and ROM (or recovery, fastboot, esp partition and whatever the other partitions are), depends on what you backup. And I don't think UEFI is stored on EMMC, so if UEFI update (or bootloader, recovery, etc. update) is present, you are totally ignoring it. On the other hand, UEFI update is a risk of not being able to access it..
Is refind working with touch or volume\power keys?
A powered hub is non-optional. OTG power is super finicky on this tablet, especially if you're adding a flash drive on top of mouse and KB
t68kv said:
Is refind working with touch or volume\power keys?
Click to expand...
Click to collapse
Voume keys work, but power key doesn't. But tuxic001 is working on editing the source code so it will. Maybe tomorrow this time it will work
Good And Bad news
Which you want to hear first?
Look fo EDIT in the main post.
I also got my tablet down, it boots only to UEFI as there's no efi bootloader to load anymore.... I'll run and get a powered usb hub to try to use the UEFI, cause the vol keys don't cut it.
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Shump said:
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Click to expand...
Click to collapse
Yeah I have run grub 2, it was nice. I got stuck somewhere in kali linux booting process, and then ubuntu-based dostros said bad kernel magic number blah blah. So I tried abother grub. First I found was nice, but still not working with ubuntu. So I tried to use ununtu's grub. It didn't show up in rEFInd. Now I can't find the good grub again What about your progress? Did you need to use powered OTG cable?
EDIT: found working grub again, kali linux stuck at this error: http://unix.stackexchange.com/quest...o-find-a-medium-containing-a-live-file-system
Any new?? This tutorial works on Lollipop?? If do this tutorial exist any risk for example brick??
Can you do a tutorial and upload to youtube??
or someone explain me the process?
Thanks in advance.:good:
I get invalid argument on the first command lenovo tab s8
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
jet_98 said:
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
Click to expand...
Click to collapse
have you installed busybox? as simple as that.
Yeah!!!!
pcGoose said:
Yeah!!!!
Click to expand...
Click to collapse
How'd you go about it?
Sent from my SM-N920T using Tapatalk
I connected Remix mini to pc with UART cable, and installed update-su.xxx. zip from there.
You GOTTA post some How-To's here!
MANY Remix Mini owners on the planet are trying to accomplish just this!
Great Job, though.
For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.
The gain of root access outshadows the lost warranty of any device imo. We are not even talking about a 700$ device here.
Done a quick search here before work. Correct there are 3v and 5v uart? At what voltage level do we need to be to interface with the mini?
RemixOS_Cameron said:
For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.
Click to expand...
Click to collapse
i was 1 of the original backers of this kickstarter project and was looking forward with excitement to receiving my mini told some of my friends and relatives who were also enthusiastic, so i received my mini played with it and patiently waited for a method to become available to root it people asked me about my mini but in all honesty could not recommend it because of the lack of root access.
i believe most of the people who backed the project are like myself enthusiasts and have at least 1 or more rooted devices have become dismayed by JIDE`S intransigence by refusing to offer any form of root access they are now playing catchup as remix os gets ported to other devices with better specs . i know were ill be looking for my next version of remix os and it sadly wont be with JIDE.
There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Code:
[email protected]:/ # ls
acct
cache
charger
config
d
data
default.prop
dev
etc
file_contexts
fstab.sun50iw1p1
init
init.common.rc
init.environ.rc
init.rc
init.recovery.sun50iw1p1.rc
init.sun50iw1p1.rc
init.sun50iw1p1.usb.rc
init.trace.rc
init.usb.rc
init.zygote32.rc
init.zygote64_32.rc
logger
mnt
nand.ko
proc
property_contexts
root
sbin
sdcard
seapp_contexts
selinux_version
sepolicy
service_contexts
storage
sunxi-ir-rx.ko
sunxi_tr.ko
sys
system
ueventd.rc
ueventd.sun50iw1p1.rc
vendor
verity_key
[email protected]:/ #
johnmurrayvi said:
There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Click to expand...
Click to collapse
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?
It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
White -> TX
Green -> RX
Black -> GND
1. Download UPDATE-SuperSU.zip
2. Unzip the UPDATE-SuperSU.zip
3. Copy superSU and META-INF/com/google/android/update-binary(from #2) onto USB drive
on putty
mount -o rw,remount /
mount -o rw,remount /system
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-xxx.zip /data/local/tmp
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-xxx.zip
reboot
Nidor said:
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?
Click to expand...
Click to collapse
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
pcGoose said:
It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
Click to expand...
Click to collapse
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.
No, we are not connecting vcc。
johnmurrayvi said:
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.
Click to expand...
Click to collapse
pcGoose said:
No, we are not connecting vcc。
Click to expand...
Click to collapse
Just RX, TX, and GND.
Whoops, didn't mean to imply 3.3V was actually related to the Mini's UART.
Thanks for catching that, didn't intend for that ambiguity.
@johnmurrayvi @pcGoose
Thanks for the info. Finally I can get started on actually using my mini.
SuperSU install doesn't work.
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)
Guerol said:
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)
Click to expand...
Click to collapse
https://download.chainfire.eu/696/SuperSU/
I'm about to buy an USBUART PL2302 Cable, hoping it works.
pcGoose said:
https://download.chainfire.eu/696/SuperSU/
Click to expand...
Click to collapse
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?
Guerol said:
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?
Click to expand...
Click to collapse
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.
did you install busybox ?
Nidor said:
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.
Click to expand...
Click to collapse
here is a link to a chinese site the guy said he installed busybox first
h**p://23pin.logdown.com/posts/435610-root-remix-mini