Related
Hi, I'm having some trouble with my phone. I had bamf 1.7 stripped installed and tried to change my kernal to the battery saver one. it didn't like something about this and my wifi and data stopped working. the wifi screen just said error. I could still get phone calls though.
So I figured I'd try to fix this by wiping it all clean and installing perfect storm 1.5. Well I factory reset, wiped and cleared and all that and loaded the rom. I pulled the battery on reboot and when it started up I am stuck on the activation part of the phone set up. The cell signal is X'ed out and I seem to have no service and it just says "Activating...". Please any help is appreciated.
You're using the MR2 radio with Perfect Storm 1.5, right?
hksg said:
You're using the MR2 radio with Perfect Storm 1.5, right?
Click to expand...
Click to collapse
ah shoot, I thought it came with the rom. I have it on my sd card but it's not named correctly. How can I rename it? The sdcard doesn't go into disk drive mode.
Viper Daimao said:
ah shoot, I thought it came with the rom. I have it on my sd card but it's not named correctly. How can I rename it? The sdcard doesn't go into disk drive mode.
Click to expand...
Click to collapse
You have two options.
1) If you have computer access and ADB, turn the phone off, load up the command prompt, and type "adb reboot recovery" (can someone verify that command? I think its the right one). Once you're in recovery, select mounts & storage > mount USB device (the very last option in the mounts & storage menu). That will mount your SD card and you can change the file name from there.
2) Hold the Volume down and Power buttons down until your phone turns on. This will bring you to bootloader, from which you can boot into recovery mode and follow the above steps, minus the ADB part. Holding Volume up and Power might boot you into recovery directly, but I've never done that and I'm not really sure if it will.
If neither of those work for you, stop back by and we'll take it to the next level! Hope this helps bro
Viper Daimao said:
ah shoot, I thought it came with the rom. I have it on my sd card but it's not named correctly. How can I rename it? The sdcard doesn't go into disk drive mode.
Click to expand...
Click to collapse
Did you try going through Internet Pass Through? Enable Internet Pass, wait like 10 seconds, and then try going into disk mode. Or, you can connect your phone and push the file using ADB commands. Or, if you can access the Android market via wifi, just download a file manager, and then go to your SD card directory, fine the file, and rename. Just remember that it is PG05IMG.zip, and it has to be on the root. Then you can just reboot to bootloader and flash the radio. Good luck.
I POSTED EARLIER BUT IT NEVER SHOWED UP SO IM REPOSTING. sry for caps.
rooted my nook color and everything was fine. then i tried to root my nook tablet. searched all over the net for comprehensive instructions to do so and i found this
The first thing you need to do is extract the contents of file #1 and write the extracted img file to a Micro SD. If you are using Microsoft Windows then click the file named Win32DiskImager.exe, select the NT16or8gbV47SDimagefile.img, select your drive letter for your SD card.
If you are using Linux, then open up the terminal and CD into the directory where NT16or8gbV47SDimagefile.img is located. Once in the correct directory issue this command to write the .img to the Micro SD:
sudo dd if=NT16or8gbV47SDimagefile.img of=/dev/sdX
You must replace the X in sdX with the appropriate letter for your SD slot. There are many ways to get the correct letter but I use the program Gparted.
Ok, so now you have an SD card that will root your Nook Tablet. Let's boot into Recovey. Turn off your Nook if it is on, and connect the USB wire to your computer. Your Nook will now turn on and enter into ClockwordMod Recovery. Using the Volume Keys to move up and down and the N key to select, click on Install zip from SD. You will now see a zip file called Root_8gb-or-16gb-NTV4_7.zip. Highlight that file and press the N.
If all goes well, the operation will complete. You are now rooted. Press the Power button to go back to main Recovery menus and select Reboot and press the N key. Your Nook will appear normal. It is not. Press the N key and you will see a new option for Home screen. Clicking the new Home icon will take you to an Android looking desktop. Yay! We are not done yet.
Now, install ES File Explorer from the Play Store. Open the app and browse your Micro SD card. Look for a folder called Apps. In this folder you will see a file named Nook Recovery Flasher.apk. Click this file to install it. Once installed, click on Flash CWM Recovery. Now you do not need the SD card you made earlier to boot into Recovery. It is now part of the system.
Remove the SD card and connect it your computer and format it so that it is empty.
Copy the files #2, #3, and #4 that you downloaded from above to the SD card and insert it back into the Nook Tablet.
Remember how to boot your Nook into Recovery mode? Do it.
Select Install zip from SD again and install ONLY CWM_v6.2.7_emmc.zip. This will upgrade your recovery. Without upgrading, you will not be able to flash CyanogenMod. Once the operation is complete, use the power button go back to reboot the Nook. Boot it to Recovery one more time.
Now you can select the latest CyanogenMod file you downloaded to install it. After that, select the latest Gapps you downloaded. Reboot the Nook and you are good to go!!!
. i folowed all the instructions to the dot. but when i got the this step, "Remember how to boot your Nook into Recovery mode? Do it." and i did it. but when i rebooted it immediately tried to boot into recovery but got stuck on the cardboard box screen and it flickered none stop and would not proceed to recovery (CWM) menu. I tried everything i could think of and i found that if i reformatted my sd card with the CWM sd root img and put sd card into NT and boot up it successfully brings up CWM. from this i tried both normal cache wipe and advanced menu cache wipe and also tried wipe to factory settings and wipe battery stats, rebooted and it still gets stuck on the flickering cardboard box screen..........anyone have any ideas? i cant seem to boot it up at all past this screen. maybe i shud format system through sd-card cwm? but then i would have no OS, so how would i proceed with this. is it totally broke or wut? god i hope not:crying::crying::crying::crying::crying::crying:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
wut ive got so far
digixmax said:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
Click to expand...
Click to collapse
well i think wut u gave me is exactly wut i need. followed the custom rom tutorial and it worked fine to the point to where i first get to cyanoboot menu where i would have proceded to install cm10 and gapps. but i accidentally put the wrong cwm on the sd card and it said bad boot. (note it also said it disabled charging) so i go the right cwm boot img for it. but the fact that it disabled my charger i cannot get back into the cyanboot menu. anyone kno how i can reactivate charging? if not then im completely screwed because once it dies i wont be able to charge it again and it will be flippin useless. even worse than before.........sigh fml someone shoot me in the dome
The "charging disabled" message on the Cyanoboot screen does not mean what you think it means (i.e., charging is turned off on for good until you somehow turn it on again). If you're stuck on that boot screen, just hold down power button for 20-30 sec to turn it off and start over with the SD card with the right CWM.
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
YAY!
Temetka said:
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
Click to expand...
Click to collapse
YAY! i figured out how to get past the bad boot part. just be sure to be vigilant and press "n" asap when the screen boots up in cyanoboot......and i mean like THE second it pops up. that solved all my problems.......
but i dont understand the piece of advice part with the 5 point/ 10 point touch installer deal. ill do alil research on it to see wut it is and wut i got to do. if you care to send a link explaining it that would be super flippin awesome. and btw thx sooooooooooooooooo much. this forum has been the most helpful place. quick responses and accurate information. everyone i talk to rocks. i appreciate it so much. :victory:
The 5point and 10point touch is just that.
So you know how your screen responds to your touch input? And let's say you use to fingers to zoom in on a picture. That would be an example of 2 touch. Expand from there for more finger interaction.
Here's an XDA thread on the topic:
http://forum.xda-developers.com/showthread.php?t=769932
and nice Wikipedia article on how multi-touch works:
http://en.wikipedia.org/wiki/Multi-touch
Glad you are up and running.
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
MrsPurchase15 said:
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
aicjofs said:
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
Click to expand...
Click to collapse
It doesn't have a name :/ It has a model number (SNB02-NV7A), an edition number (SNB02-NV7A-US-SW), android version (4.4.2), a kernel version (3.1.10) and then a build and hard ware number.
I appreciate the advice though. Thank you!
MrsPurchase15 said:
I appreciate the advice though. Thank you!
Click to expand...
Click to collapse
SNB02-NV7A is the model number for the NABI2S. It's likely the Nabi2S TWRP will work for the tablet. To use it though you will likely have to unlock the bootloader and that will erase all your personal data on the tablet. It's the safer method since you will have a backup of your tablet, but will require you to get your hands dirty.
You can read through this http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 and see if it's something you want to try.
Using the above linked thread as the basic outline, in general you would:
-Setup adb/fastboot and the windows driver.
-Unlock the bootloader(wiping all personal data on tablet)
-"fastboot boot" NOT "fastboot flash" the Nabi2S TWRP recovery to the tablet RAM.
- backup the recovery, boot, system, and addon(preload) partitions. Then you can always recovery the tablet if something goes wrong, and help others that need to recover their tablet.
-Download SuperSU and flash from TWRP to obtain root.
I can help with more detailed instructions but if it's something that seems uncomfortable to try then I don't want to type it all out. Again a kingo root or other root method will likely give you root, I personally like having a clean backup before beginning and there is none in existence yet.
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
MrsPurchase15 said:
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
Click to expand...
Click to collapse
Again the Nabi general information thread is going to be the biggest help in understanding what needs to be done. That information is here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 The procedure below isn't as long as it looks I tried to add some troubleshooting stuff along the way.
Best to have a mircoSD card for this well at least 4GB. Start with the microSD in your computer if possible.
1) First you will need to grab all the files you need:
-Drivers: Refer to drivers section #4 in the General Info Thread. Your choice if you want to try PDAnet, NabiLab, or Universal Naked Drivers. The NabiLab drivers are self installing and work pretty good in a lot of situations but not always. Download which ever one you choose to your computer. I'm going to talk about Nabilab and Universal as first resorts, we will revisit PNAnet if you are having driver issues.
-ADB and Fastboot tools. Here it's best to refer to section #6 in the General Thread. Specifically:
Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
-TWRP for the NABI2S. Get that file here: TWRP for Nabi2S
After this step you should have downloaded 3 files and the ADB/fastboot files you should have installed. That leaves the remaining 2 files. One should be NABI2S_TWRP271.img, copy that file to the folder where you installed ADB/fastboot(remember you can find that folder by selecting Minimal ADb and Fastboot from your start menu and typing "explorer ." as explained above.) The remaining file is the which ever driver package you picked. If it's universal naked extract the zip file to a place you know. If it's Nabilab drivers go ahead and install them. PDAnet we will try later if these 2 don't work.
2) Boot the Nabi to fastboot with the USB cable plugged in to your computer. Also open device manager on your computer so you can see when the interface comes up. I don't have a Nabi2S so this may be not exactly right. Start with the tablet off. Press and hold the power button AND the vol up buttons at the same time. At some point you should boot up and have a small text menu in the top corner of the screen.(If that doesn't work try power and vol down buttons). One of the menu items will be fastboot protocol. You will want to highlight that text using the volume keys, and then select it using the volume keys.(again I an not sure which is which. Vol - might change which is highlighted, and vol + will select that line, or vice versa, remember which does does what as you will need it later on). Keep trying combinations or timings if it's not working. When it's right your computer will acknowledge a new device plugged in and the device manager screen should show a fastboot or unknown interface.
3) Getting the drivers working. If you chose the Nabilab drivers they should automatically install, and in device manager you should see and item called Android device, and when expanding that entry some bootloader or fastboot interface(When you see this you should be done with this step). The tablet will also switch the text on the screen to say something like "continue", "bootlader", blah, blah. If you went with universal naked drivers this is where you would locate the unknown or fastboot device with the yellow exclamation mark and manually install the driver by pointing them to the folder you extracted(There could be driver signing issues depending on which version of windows you are using. You will have to google "disable windows driver signature enforcement", but basically you will reboot the computer disabling driver signature enforcement. Hopefully if you picked the Nabilab drivers and they work on your computer this step will be pretty painless and not as long as it looks.
4) Unlocking the bootloader. If you have the command window open now great, if not from your start menu select "Minimal ADB and Fastboot" this should open a command prompt. REMEMBER this step will erase all you data on the tablet, game saves, pictures, etc.
Get ready to acknowledge some text on the tablet itself as you have to be pretty quick using the volume keys to highlight and select(Same function as what you noted in step 2). At the command prompt type:
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
On the tablet some text will pop up asking yes or no do you really want to unlock the bootloader? The selection is made with the volume keys. You should see some confirmation of erasing tablet and completed.
If this step isn't working when you type the command i.e. "waiting for device" the drivers probably still aren't installed correctly. If something failed in this step you may be forced to reboot the tablet and get back in fastboot mode(step2)
5) Install TWRP. With tablet in fastboot mode. Type at the command prompt:
Code:
fastboot boot NABI2S_TWRP271.img
or
Code:
fastboot -i 0x0489 boot NABI2S_TWRP271.img
If you are getting file not found errors the NABI2S TWRP file isn't in the folder. If all goes right the tablet will boot to TWRP. This is where we may have problems as I'm not sure if the NABI2S TWRP can boot the Star Wars Nabi. If it's not booting then we are pretty much done at this point...
6) Getting SuperSU(root). If the tablet booted TWRP. Download this UPDATE-SuperSU-v2.46.zip. Copy that file to your microSD you have inserted in the computer. When that is done safely eject the card from the computer and put it in the tablet.
7) In TWRP select the "mount" tab and check MicroSD(external storage) and the check box should become checked.
8) Make a backup. Select the "backup" tab in TWRP. You will have the options to backup "recovery" "boot" "system" and "preload(or addon)" select all 4 of those. Then select the backup location as MicroSD(external storage). Swipe to backup.
9) Only if step 8 worked install root. Select the TWRP "install" tab. Back out to the highest level, and find external_storage. The UPDATE SUperSU zip should be there. Select it and swipe to install.
10) Only if the step 8 and 9 worked go to the "reboot" tab and reboot. If they didn't work. Press and hold the power key until the tablet shuts off, and we can troubleshoot. If you rebooted the tablet will take a long time to boot initially since you wiped the tablet and it will have to rebuild data. You can then reset up the tablet.
11) Get superSU from Play Store and verify root.
12) If all this work your backup will likely be a benefit to future users so sharing it might be something to consider.
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
MrsPurchase15 said:
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
Click to expand...
Click to collapse
Are you using an app to do this(like link2sd)? Or just hoping root alone would allow you to do this?
I was hoping the root would allow me but I take it that's wrong, lol.
MrsPurchase15 said:
I was hoping the root would allow me but I take it that's wrong, lol.
Click to expand...
Click to collapse
Haha. Understood. You do need root to do it, but root is needed for the apps that can make it possible. My kids never had the problem when they had their old Nabi2's so I'm not as much help on the "how to" portion but I understand how the apps work. Read through this thread to gain some understanding of what it takes now that you have root. http://forum.xda-developers.com/showthread.php?t=2086338
There is another way also where you stop using internal storage altogether and use an external by editing the ramdisk but it has some limitations as well.
This was awesome i have the same star wars edition and everything works well i even made a backup which i can post and i used the 3.0.1.3 kernel backup to restore the tablet and it still worked
I ran into a few issues when rooting my J5 for the first time, but I found a working solution and wanted to share it. I'm not sure if this is the right place - feel free to move the thread or repost as you wish. I just find it important to post because I didn't find a solution anywhere else, and I want others to know how I worked it out anyway, so I just registered real quick to post this here. There's so many things that took me ages to figure out. At some point my screen went yellow when booting, other times my devices wasn't recognized, it was such a mess. But eventually I fixed it. I hope this works out for folks as well.
For sake of complete...ness, let's start at the very beginning.
Prepare:
Don't forget to make a back up of your files first, both on SD and Phone!
1. Download the latest Samsung Android USB Driver for Windows on your Computer
1a. I also downloaded these drivers I think
2. In your phone check Settings -> About Device -> Software Info -> tap a few times on Build Number to activate developer mode
3. Now go to Settings ->Developer Options ->enable OEM unlock and USB Debugging
4. Download these on your computer:
Odin
this .tar file (This one is for SM-J500FN ONLY)
SuperSU
OPTIONAL: Adaptable Storage Enabler PATCH (everything saying optional belongs to this)
5. Connect your phone via USB in Windows and move SuperSU zip into your phones folder OPTIONAL: Also move the storage patch zip to your phone
6. Power off your phone and boot to download mode (Hold VOLUME DOWN/HOME/POWER at once)
7. Press VOLUME UP
8. Go into the Odin folder and right click Odin3.exe -> start as Administrator
9. If your phone is connected properly, it should say "Added!" (if it doesn't, try reconnecting or download drivers properly again)
10. Click on the Options tab in Odin and uncheck Auto Reboot
11. Click on AP and open the .tar file you downloaded
12. Press start and wait until the message PASS! appears (if it doesn't you may have missed a step or something isn't right yet)
13. Shut down the phone when it's finished (if stuck remove the battery)
14. Hold VOLUME UP/HOME/POWER - teamwin should start
15. Swipe to allow modifications -> Install -> locate the SuperSU zip and select it -> (OPTIONAL: Add another ZIP -> locate and select the patch ->) swipe to confirm flash
16. -> Reboot system
DONE!
OPTIONAL ADOPTABLE STORAGE:
17. In your phone go to Settings -> Storage -> SD-Card -> use as internal memory (This requires formatting the SD)
BOOM, DONE!
TIP: Never, NEVER, turn the OEM-unlock option off (and developer mode for that matter), if it goes off like due to low battery it will be soft bricked and you will have to wipe all your files, it sucks, trust me.
____________________________
Sources/Threads that really helped me put this together:
https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3338869
https://forum.xda-developers.com/galaxy-j5/themes/galaxy-j5-adaptable-storage-6-0-1-t3470020
https://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521
https://www.youtube.com/watch?v=m51lZldj0UQ (praise you for the working .tar file)
I had the same problem with rooting J5 2015. It works now, thanks for great instructions!!!
Jan
When I try to reboot twrp...my screen tears up and turns green and glitches out. Normal booting works tho...
I've tried this on two J5s now. First one worked brilliantly. Second one: adaptable storage isn't available.
Both phones are the same model with the same software version. Only difference I can think of is that the one that worked had been factory reset before and the other one has been used for a while.
Any ideas? Anything I can check to work out what's going wrong? I'll see if there's anything useful in the threads quoted in the OP.
Managed to get it to work eventually. Not exactly sure what resolved it. Here's what I did for info:
formatted the SD card as portable storage
shutdown and boot into recovery
re-install patch
click reboot
option still not available
format SD card again
shutdown and boot into recovery
re-install patch
this time don't click the reboot option on screen, navigate back to main menu and click reboot (doubt this made any difference)
option still not available in storage menu, wait
after 30 seconds, a notification appears with option to format the SD card and now offers option to format as internal storage
Question
For this method, is it necessary to unlock bootloader? If so, which are the steps that you considered to unlock bootloader?
Sorry - Forget my question... I realised that with the "OEM-unlock option" you are already unlocking the bootloader
thank you very much!! it's working fine for me.
Thanks for your real effort. I successfully rooted my phone samsung j5. And successfully removed system app.
Thanks for this !
Hello. First of all, really thank you for your guide, it worked easily and smooth even for a person who doesn't know anything about this kind of things.
Still seems I have some issues, hope someone can help me, maybe it will help some inexperienced user like me, since I searched on the internet but I didn't find useful information about that.
Here's what happened: after I followed the guide's instruction I was able to format my sd card as internal memory. Don't know why but my phone still sees sd separate from real internal memory of my phone but not anymore as an sd, while I was expecting the phone to see it as a whole bigger memory (i.e. with my 16 gb sd and 8 gb phone I thought I had 24 gb as a whole where i could install everything).
Because of that, when I install new apps they go in the internal 8 gb memory and when it's full I still have same memory issues I had before.
I tried to get around the problem using Link2SD but still some app can't be moved, and anyway that is not actually a solution of the problem.
Another issue was that, when I connect my phone to computer, it reads only the real phone internal memory (I think, at least that's the space I see available) and not the space on the sd, so I can't put files like music or stuff on my phone from my computer. Same thing with phone camera, which I used to save my photos directly to the sd, but now I'm bound to save my photos in the internal memory and not directly to the space in the sd, as my camera doesn't see any sd. I can't even move them after I took them.
I think I can get around this problem too partitioning my sd, which is probably a good idea anyways (I have to figure out if I can partition the sd without formatting or losing data though. I'm thinking I'll backup my phone on my computer via smart switch, then wipe everything, format and partition my sd and recover my backup into the phone), but still I would be able to access the internal mounted partition only to move my apps after having them installed in the phone memory and for nothing else.
So I don't get it right (clearly), did something went wrong in enabling sd as internal memory?
I hope I have made myself understandable even if I don't really know what I'm talking about.
Thanks again to LordSamsung and to everyone who will try to help.
Will this work with j500g?
its woek < thank you bro
Hi LordSamsung,
The phone is stuck at Samsung logo and when i enter recovery it has a lot of unable to mount /cache (Invalid argument). Is there a way to perform this flash on a phone that doesn't have OEM unlock and USB Debugging enabled?
I've tried your method but i'm unable to flash the NAND this is some of the log.
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
Thanks in advance and sorry if its a stupid question
want to flash but stay quiet on aboot.mbn
LordSamsung said:
I ran into a few issues when rooting my J5 for the first time, but I found a working solution and wanted to share it. I'm not sure if this is the right place - feel free to move the thread or repost as you wish. I just find it important to post because I didn't find a solution anywhere else, and I want others to know how I worked it out anyway, so I just registered real quick to post this here. There's so many things that took me ages to figure out. At some point my screen went yellow when booting, other times my devices wasn't recognized, it was such a mess. But eventually I fixed it. I hope this works out for folks as well.
For sake of complete...ness, let's start at the very beginning.
Prepare:
Don't forget to make a back up of your files first, both on SD and Phone!
1. Download the latest Samsung Android USB Driver for Windows on your Computer
1a. I also downloaded these drivers I think
2. In your phone check Settings -> About Device -> Software Info -> tap a few times on Build Number to activate developer mode
3. Now go to Settings ->Developer Options ->enable OEM unlock and USB Debugging
4. Download these on your computer:
Odin
this .tar file (This one is for SM-J500FN ONLY)
SuperSU
OPTIONAL: Adaptable Storage Enabler PATCH (everything saying optional belongs to this)
5. Connect your phone via USB in Windows and move SuperSU zip into your phones folder OPTIONAL: Also move the storage patch zip to your phone
6. Power off your phone and boot to download mode (Hold VOLUME DOWN/HOME/POWER at once)
7. Press VOLUME UP
8. Go into the Odin folder and right click Odin3.exe -> start as Administrator
9. If your phone is connected properly, it should say "Added!" (if it doesn't, try reconnecting or download drivers properly again)
10. Click on the Options tab in Odin and uncheck Auto Reboot
11. Click on AP and open the .tar file you downloaded
12. Press start and wait until the message PASS! appears (if it doesn't you may have missed a step or something isn't right yet)
13. Shut down the phone when it's finished (if stuck remove the battery)
14. Hold VOLUME UP/HOME/POWER - teamwin should start
15. Swipe to allow modifications -> Install -> locate the SuperSU zip and select it -> (OPTIONAL: Add another ZIP -> locate and select the patch ->) swipe to confirm flash
16. -> Reboot system
DONE!
OPTIONAL ADOPTABLE STORAGE:
17. In your phone go to Settings -> Storage -> SD-Card -> use as internal memory (This requires formatting the SD)
BOOM, DONE!
TIP: Never, NEVER, turn the OEM-unlock option off (and developer mode for that matter), if it goes off like due to low battery it will be soft bricked and you will have to wipe all your files, it sucks, trust me.
____________________________
Sources/Threads that really helped me put this together:
https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3338869
https://forum.xda-developers.com/galaxy-j5/themes/galaxy-j5-adaptable-storage-6-0-1-t3470020
https://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521
https://www.youtube.com/watch?v=m51lZldj0UQ (praise you for the working .tar file)
Click to expand...
Click to collapse
want to flash but stay quiet on aboot.mbn
Does this works with SM-J500M? I ran into the same issue of internal memory storage but i don't want to have trouble connecting the cellphone to my pc and the SD can't be recognized like the other user that can't put music or photos in the SD bcs now it's internal. Can someone confirm this?
LordSamsung said:
OPTIONAL: Adaptable Storage Enabler PATCH (everything saying optional belongs to this)
Click to expand...
Click to collapse
Tenshiros said:
Does this works with SM-J500M? I ran into the same issue of internal memory storage but i don't want to have trouble connecting the cellphone to my pc and the SD can't be recognized like the other user that can't put music or photos in the SD bcs now it's internal. Can someone confirm this?
Click to expand...
Click to collapse
Yes internal storage patch does work
palmbeach05 said:
Yes internal storage patch does work
Click to expand...
Click to collapse
Understood, but i can only use this if i install a custom rom and root the phone?
Tenshiros said:
Understood, but i can only use this if i install a custom rom and root the phone?
Click to expand...
Click to collapse
Yes b/c this feature is built into the roms
same here
Instead of the .tor file you suggested I used TWRP and it worked just fine. Thank you very much for the directions!
This guide was created for people who are not as familiar with the world of Switch exploits.
NOTE: This is not the official ROM thread! DO NOT ask questions about using, troubleshooting, etc. the ROM here. I will not be able to help you and it splits discussion. Please ask questions, tips, etc, in the official thread! This post is purely to guide users in setting up their PC and such for installing this on their Switch.
DISCLAIMER: Everything is done at your own risk. Use common sense.
What you will need:
An RCM exploitable Switch console. Check here to see if your device is exploitable. If you have a newer device an exploit may be possible on older firmwares, but if you haven't already set it up you probably updated to a too new version already. Read more here. (for non-RCM exploitable devices)
A jig or other method of triggering RCM. Here's a few methods. Premade jigs can be found online.
A computer. (Assuming a Windows PC for the purposes of this guide)
A good USB-C cable that can connect to your PC and Switch.
A high quality, high speed microSD card of at least 16GB.
A way to read microSD cards on your PC.
Required downloads:
The ROM, find it in the Downloads section of the first post. Select the SD Card size that matches yours. Read through the post as well for latest information.
If desired (but not required), the shield-ifier.zip and/or the Reboot2Payload zipfile also in the ROM downloads section. Shieldifier should allow you to download games meant for the NVIDIA Shield. Reboot2Payload means you'll reboot to Android when you hit "reboot" within Android (or Hekate if you choose reboot to bootloader). Without it you'll reboot to the default OS.
GApps, AKA Google Apps. This will install the Play Store and other Google services. Not required but 95% of people will want this. Select ARM64, 8.1, and then any on the right (Nano is recommended). Hover your mouse over each option for descriptions. If you're not sure just choose Nano.
TegraRcmGUI. This program will push the exploit to your Switch. Grab the latest .msi installer and install it.
balenaEtcher. This program will write the ROM to your SD card.
Hekate. This is the "bootloader" if you will. Once you get to RCM with your jig (or whatever method) this is the payload we'll be sending over. The ROM developer recommends using version 5.0 exactly, and I'll recommend that. Version 5.2+ however does include support for partitioning your SD card so you can use one SD card for Horizon (Switch's default OS) and Android, though I have not been able to figure it out.
I recommend putting the ROM, GApps, shieldifier, Reboot2Payload, and Hekate files all in one folder so your Downloads folder doesn't get cluttered.
Steps:
Insert your SD card into your PC. Backup anything you need to because all data on the card will be wiped.
Open balenaEtcher. Select the "android-XXgb.img.gz" file you downloaded. In the middle make ABSOLUTELY sure the device selected is the SD card you want to use. You don't want to accidentally destroy some other drive you have attached. Click "flash". This can take a while (30mins-hours depending on SD card speed and size!), especially on larger cards. The progress bar will jump around, and get stuck at like 99%. Don't worry, that's fine.
Once it's complete you can close balenaEtcher. You should be able to see two new drives in Windows explorer. One will give an error if clicked (Don't click format when Windows asks!) and another is a 2gb partition Windows can read. If these don't appear then reinsert your SD card into your PC. Mine mounted the unreadable partition as D:\ and the readable one as S:\. EDIT:Redoing this months later it only shows the one drive for me.
Place the GApps .zip (and shieldifier/Reboot2Payload .zip) file(s) in the root of the 2gb partition. Don't unzip them.
Eject the SD Card from your PC and place it in your Switch.
Use your preferred method of booting into RCM. I posted a link with many methods in the "What you need" list up top. You'll know you're in RCM when the Switch screen stays black and doesn't boot as normal when you hold Power+Vol Up.
Launch TegraRcmGUI. Go to the settings tab and select "Install driver". Go back to the payload tab and select the Hekate .bin file as your payload. Connect your Switch. It should say "RCM OK" in TegraRcmGUI. Now select "Inject Payload". Once you see the GUI on your Switch then you can disconnect it.
Tap "More Configs" and then hold down Vol Up and tap "Switchroot Android". Continue holding Vol Up until you get to the TWRP menu.
Tap "Keep Read Only" on the first screen.
Tap "Mount" and check "System" and "Vendor". Then tap the home button at the bottom. (If they don't appear, move your finger up and down in the middle and it should refresh, try that every time it looks like things are missing in TWRP.)
Tap "Install", then "Select Storage", then "Micro SD card" and "OK". Tap the GApps zip, uncheck "Reboot after installation is complete" and slide the slider to the right. Optionally do the same for shieldifier and Reboot2Payload (press back after GAPPS flash to go back). Once finished with all zips wipe the Dalvik cache (it will prompt you). NOTE: If you want GAPPS you MUST install GAPPS before you first boot up Android, so if you accidentally booted into Android, reflash your SD card and restart the guide (you may be able to wipe data and caches through TWRP to fix it, I haven't tested).
Select "Do not install" if it asks to install the TWRP app. Reboot the device (you may have to hold the power button), enter RCM again, and re-inject hekate from your PC. Boot Android again but this time don't hold any buttons. Your screen may be black for a minute, don't panic. First boot takes a while.
Your device should boot into android. Congratulations. Update the NVIDIA Shield app through the Play Store if you installed it. For setting up anything else, or for questions you may have, use the official thread.
NOTE: This is not the official ROM thread! DO NOT ask questions about using, troubleshooting, etc. the ROM here. I will not be able to help you and it splits discussion. Please ask questions, tips, etc, in the official thread! This post is purely to guide users in setting up their PC and such for installing this on their Switch.
You are missing the step where you mount the SD card first before installing GApps. GApps install will fail if you do not mount the SD in TWRP first.
weirdingway said:
You are missing the step where you mount the SD card first before installing GApps. GApps install will fail if you do not mount the SD in TWRP first.
Click to expand...
Click to collapse
Tap "Install", then "Select Storage" (If the dialog box is blank just slide your finger up and down to scroll and it should refresh), then "Micro SD card".
Click to expand...
Click to collapse
That seems to do it for me.
gorei23 said:
That seems to do it for me.
Click to expand...
Click to collapse
That works for me AFTER I mount the SD card "System" in TWRP
EDIT: You even said it yourself but missed adding it to your guide. Just trying to help
https://forum.xda-developers.com/ni...ageos-15-1-t3951389/post79971072#post79971072
Paper clip
I need a step by step. Cause that parts so confusing...
weirdingway said:
That works for me AFTER I mount the SD card "System" in TWRP
EDIT: You even said it yourself but missed adding it to your guide. Just trying to help
https://forum.xda-developers.com/ni...ageos-15-1-t3951389/post79971072#post79971072
Click to expand...
Click to collapse
Ohhhhh you mean mount the /System partition? I think we had a miscommunication. The "sdcard" is automatically mounted, as shown in the YouTube video I hastily made...
I believe the part about mounting the /System partition is only needed sometimes, depending on what you told TWRP to do with the /System partition on first boot. Got ya.
sSHARPZz said:
I need a step by step. Cause that parts so confusing...
Click to expand...
Click to collapse
Not much to it. Short pin 9 & 10 and hold down power and vol up. If you can't manage it look into buying a premade jig that does it easily and reliably.
So one side of the paper clip directly on pin 9,10 and the other near a conductive metal? Also there are several options on amazon. (Quickest shopping method) any chance you can point me to the correct one?
sSHARPZz said:
So one side of the paper clip directly on pin 9,10 and the other near a conductive metal? Also there are several options on amazon. (Quickest shopping method) any chance you can point me to the correct one?
Click to expand...
Click to collapse
Just shorting 9&10 should do it. They're just plastic with a tiny piece of metal inside. Just find one with good reviews.
What's the best way to boot into recovery, this is my first time trying to do anything in relation to modding my switch, any help will be highly appreciated!
everything is working but my joycons wont connect any ideas?
One thing that isn't on here that was required for me was to wipe the dalvic and the cache right after flashing GAPPS. It wouldn't boot aftr that, might be a good addition to your guide. Thanks for the guide though, it was absolutely amazing and got be Android!
Does it cleans the data on switch or just clear the sd card?
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Does this process make any changes to the Switch? Normally I use SX OS and would rather not mess with it just to try Android.
Will the switch boot android automatically, or do you need to inject hekate from a PC or phone every time you want to boot it?
bottmint said:
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Click to expand...
Click to collapse
Yea get an RCM jig from Ebay. Well worth it with no hassle.
Sent from my SM-G955U using Tapatalk
Clip
bottmint said:
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Click to expand...
Click to collapse
We asked, he answered. What’s it to you?
Atmosphere and Android
This is awesome news, by chance I had just ordered a hackable Switch today.
Might be a silly question, but I was planning to follow the NH Server instructions to install the Atmosphere CFW
I have ordered a 512GB Micro SD Card for homebrew stuff
The instructions here (Thanks, very clear) suggest that an entirely new / dedicated SD card will be needed for Android.
Anyone planning / see a way to partition and have Atmosphere apps AND Android off of 1 SD card?
Thanks
After injecting payload, screen stays black. Anybody having this issue?
See screenshot showing payload was successfully injected.