Hey guys, if you've read around this forum, you must be familiar with the infamous bricked eMMC problems. This, sadly, is a hardware issue, and once it's bricked, you have no choice but to get the eMMC replaced by a professional. Following the popular saying, "Prevention is Better Than Cure", here are a few tips to prevent the eMMC chips from burning
=> Do not download multiple apps at once from the market. Even two simultaneous apps can screw your phone up.
=> Never Use the "UPDATE ALL" feature from the market. Update each app separately.
=> When you flash a new ROM, restore your apps using titanium backup before adding a Google Account. This will prevent the market from restoring all your apps at once.
=> NEVER EVER PULL THE BATTERY This is very important. Pulling your battery out is the most prominent cause of eMMC bricks. Use alternatives like -
=> Use ADB Commands to reboot into recovery
=> Press the Volume up, Volume Down and Power buttons together to reeboot the phone. In a bootloop, take off the battery cover (without pulling the battery) and press the buttons. The phone will turn off for 2-3 seconds before it turns back on. That's your window. Pull the battery in this time.
=> If you absolutely have to pull the battery, re-insert it at least 30 seconds later.
ADB Commands
ADB Commands
You'll obviously need ADB on your PC, so download and extract the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on your PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where you put adb and issue the command
Code:
[B][COLOR="Blue"]adb devices [/B][/COLOR] [COLOR="YellowGreen"] ---- what is the result?[/COLOR]
If your device appears to be recognised that's good, so next try
Code:
[COLOR="Blue"][B]adb reboot recovery[/B][/COLOR]
[B][COLOR="YellowGreen"]OR[/COLOR] [/B]
[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
I just purchased a new desire s. Is there still a chance that i will get a faulty eMMc chip?
yes, sadly there is.
Run this command in the terminal app or ADB
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Post the result. If it's M4G2DE, your with us, faulty eMMC
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
djsubtronic said:
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
Click to expand...
Click to collapse
good argument...will keep that in mind.
ben_pyett said:
ADB Commands
You'll obviously need ADB on your PC, so download and extract the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on your PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where you put adb and issue the command
Code:
[B][COLOR="Blue"]adb devices [/B][/COLOR] [COLOR="YellowGreen"] ---- what is the result?[/COLOR]
If your device appears to be recognised that's good, so next try
Code:
[COLOR="Blue"][B]adb reboot recovery[/B][/COLOR]
[B][COLOR="YellowGreen"]OR[/COLOR] [/B]
[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
Click to expand...
Click to collapse
can you provide me an instruction on what to type in cmd for me to go to the directory where my ADB is.. for example in local disk D and inside a folder named ADB.. what should i type in cmd? before typing adb devices?
yerfdes said:
can you provide me an instruction on what to type in cmd for me to go to the directory where my ADB is.. for example in local disk D and inside a folder named ADB.. what should i type in cmd? before typing adb devices?
Click to expand...
Click to collapse
You need to "cd" to the directory where your Android SDK is installed, so eg if it is installed at D:\android-sdk then:
Code:
D:\
cd "\android-sdk\"
And then
Code:
cd "platform-tools"
good advice on titanium backup, just after activating my google account on my DS it download all my installed apps. then my phone hangs.
djsubtronic said:
You need to "cd" to the directory where your Android SDK is installed, so eg if it is installed at D:\android-sdk then:
Code:
D:\
cd "\android-sdk\"
And then
Code:
cd "platform-tools"
Click to expand...
Click to collapse
whoa!! im a total noob here.. should i install first android sdk and can you explain to me what is platform tools??
djsubtronic said:
Nice guide. However, where is it confirmed that only M4G2DE chips are faulty? And if they are, surely not all of them have the fault. Didn't someone report the failure with the other chip too? I have the M4 chip, I've updated many apps at a time, pulled battery numerous times (inserted immediately as well), but never had any issues. I guess it could be safe to say there is no way to actually know for sure which chip is faulty and that everyone should follow this guide regardless.
Click to expand...
Click to collapse
Sadly, in my other thread (in which i collected info), only M4G2DE chips came faulty. I never even saw another chip, maybe that's the only one. I've pulled many times battery too, (but NEVER quick-reinserted) and on the first day of XTC Clip S-off, my phone turned off after i tried downloading 2 apps at once. I had nothing, just S-off, i battery pull made the phone work.
shrome99 said:
yes, sadly there is.
Run this command in the terminal app or ADB
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Post the result. If it's M4G2DE, your with us, faulty eMMC
Click to expand...
Click to collapse
**** Got M4G2DE so this means that i can't pull the battery? right?
yerfdes said:
whoa!! im a total noob here.. should i install first android sdk and can you explain to me what is platform tools??
Click to expand...
Click to collapse
Yes you need to install the Android SDK which includes ADB. You only need to install the basic package and nothing else. Platform-tools is a folder created within the SDK folder where the executables for tools such as ADB are located.
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
shrome99 said:
Sadly, in my other thread (in which i collected info), only M4G2DE chips came faulty. I never even saw another chip, maybe that's the only one. I've pulled many times battery too, (but NEVER quick-reinserted) and on the first day of XTC Clip S-off, my phone turned off after i tried downloading 2 apps at once. I had nothing, just S-off, i battery pull made the phone work.
Click to expand...
Click to collapse
I just pulled and reinserted my battery today again. Probably done it a 100 times now. No issue.
jullejul said:
**** Got M4G2DE so this means that i can't pull the battery? right?
Click to expand...
Click to collapse
As I posted earlier, follow this guide whichever chip you have, just to be safe. As there is no real conclusive evidence as to which models/chips have the fault.
I will check later to see what chip I have cos I have pulled out the battery several times ..in fact it seems to be my saving grace whenever my phone hangs orthe volume down + power button doesn't work
Sent from my HTC Desire S using XDA App
Guys, ALL m4g2de chips are not faulty. Only a few unluck ones are. Sadly, there's no way of finding out if yours is faulty or not. Just follow the guide to be safe
shrome99 said:
Guys, ALL m4g2de chips are not faulty. Only a few unluck ones are. Sadly, there's no way of finding out if yours is faulty or not. Just follow the guide to be safe
Click to expand...
Click to collapse
Okay thanks
Sent from my HTC Desire S using XDA Premium App
lynxnoon said:
I will check later to see what chip I have cos I have pulled out the battery several times ..in fact it seems to be my saving grace whenever my phone hangs orthe volume down + power button doesn't work
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
It does work. You need to hold all three buttons down together. Hold down the volume buttons first then finally press and hold down the power button.
I have a about 3 months desire s, and using command
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
It tells me SEM04G....
Omg. You're probably on a perfect eMMC chip. Have you ever pulled battery?
will read this for sure. thx for the guide mate
Related
Decided to update the instructions for this fix.
Thx to sruon for the fix
Original instructions pulled from IEFtm's post @ Modaco
These fixes require the Android SDK and very basic ADB knowledge. You can copy and paste for most.
Make sure in device manager the driver for fastboot is installed (Win 7 downloads them automatically)
For USB fix
Download the flash_image & mtd-eng.img attached, unzip them and put them on the SD card before starting
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands
fastboot oem enableqxdm 0
fastboot reboot
That should fix your SD card not being detected.
USB Fix * Root REQUIRED *
Update - Some have reported that updating the radio fixes this, so if this guide doesn't work, try that
Run from a terminal emulator in Android since ADB won't work if the USB port is not working
Terminal emulator & ADB commands
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd-eng.img > /data/mtd-eng.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd-eng.img
reboot
And that should fix the USB issue
factory reset?
That was the first thing I tried
Can you pull the battery and try a different sd card? Maybe reformatting (full) the card may help. You could always restore using the base sprint rom and try rooting again
This is probably the same thing known as "USB Bricks" for HTC Desires... It has been untested on EVO 4G but here is a topic that explains it for HTC Desire.
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
It should be the same mechanics so... I have good hope for you.
did you try pulling the battery and trying the same process? I dont think you bricked it, seems like something else is going on. Did you remove the SD card while it was running?
Btw to reenable SD Card and ****s go into fastboot and type
fastboot oem enableqxdm 0
fastboot reboot
You tried hard resetting already?
Turn the power off.
If your HTC EVO 4G is frozen, pull the battery out and reinsert it
Hold the Volume Down button
Press and release the Power button
You are now presented with a menu that allows for Fastbook, Recovery, Clear Storage, and Simlock
Select Clear Storage by pressing the Volume Down button
Press and release the Power button
Now simply confirm your decision: Volume Up for YES and Volume Down for NO
If you selected YES, all data including third-party applications will be deleted from the HTC EVO 4G. Once the wipe is complete, the phone will reboot to its factory fresh state.
sruon said:
Btw to reenable SD Card and ****s go into fastboot and type
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
This did let Android recognize the SD card, so thanks
sruon said:
This is probably the same thing known as "USB Bricks" for HTC Desires... It has been untested on EVO 4G but here is a topic that explains it for HTC Desire.
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
It should be the same mechanics so... I have good hope for you.
Click to expand...
Click to collapse
Hopefully this fixes the USB issue, so I'll report back shortly
West650 said:
You tried hard resetting already?
Click to expand...
Click to collapse
Wiping/Hard reset didn't fix it
If it works... make sure this get stickied and ****s
I'll think I'll wait on rooting my Evo when I get it. I don't want to get into any problems haha.
sruon said:
If it works... make sure this get stickied and ****s
Click to expand...
Click to collapse
Actually it did fix it, I have the SD card & USB function back, so I'll update the first post with the instructions
So thanks a lot for that sruon, I owe you one now
No problem!
Ok updated the original post with the instructions cause I know I'm not going to be the only one with this problem
Thanks for this mate. Worked like a charm... even with your files, I didn't need to muck around with the generator or a hex editor. I will tell you this tho, I dont ever wanna do that again. 10 minutes to type 5 command lines in a shell on an Evo sucks hard.
Calkulin said:
Ok updated the original post with the instructions cause I know I'm not going to be the only one with this problem
Click to expand...
Click to collapse
calkulin good to see you messin around already, you dont waste any time! any idea what caused this issue for you or how to avoid/prevent it?
joeykrim said:
calkulin good to see you messin around already, you dont waste any time! any idea what caused this issue for you or how to avoid/prevent it?
Click to expand...
Click to collapse
+1, i used many of his winmo roms. cant wait to see what he does with android
Darth Pooh said:
Thanks for this mate. Worked like a charm... even with your files, I didn't need to muck around with the generator or a hex editor. I will tell you this tho, I dont ever wanna do that again. 10 minutes to type 5 command lines in a shell on an Evo sucks hard.
Click to expand...
Click to collapse
Glad I could help but be sure to thank sruon as he is the one that posted the link
joeykrim said:
calkulin good to see you messin around already, you dont waste any time! any idea what caused this issue for you or how to avoid/prevent it?
Click to expand...
Click to collapse
I don't know what exactly caused it, I don't remember exactly what I did right before the restore failed but I know I was working on de-odexing the system and since 5pm was coming around, I decide to restore and it failed. So I really don't know if it was the failing of the restore or something else(had flashed the Froyo ROM about a hour before too).
dav1boy said:
+1, i used many of his winmo roms. cant wait to see what he does with android
Click to expand...
Click to collapse
I'm already working on something don't worry But I need to finish my v1.6 ROM for the Moment first
sorry calkulin, me and you go way back, i can't wait for you to start building roms for this bad boy. unfortunately the same thing happened to me, i think my friend broke it when i asked him to pull my sd card out, anyways after i took it out it never read another sd card again. i had to get my evo exchanged yesterday, so the 1st day i didn't even get to play with it.
Nice to see you p-slim, buy yeah I can see how someone can damage the SD card slot, it definitely is a pain to remove and insert a card, especially if you have short finger nails. But don't worry, mine only lasted 3 hours before I "thought" I had killed it, so your not alone
Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.
Sticky Worthy?
How To Guides in Video Form:
How To One Click Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
How To Manually Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
One Click DebugFS method: http://www.youtube.com/watch?v=EpuiKIl7lpI&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Video Root Guide: http://youtu.be/cuiJYKV2GGU
^^This is just a Visual aid for the method provided by Invisiblek outlined here http://forum.xda-developers.com/showthread.php?t=1756885
How to Update Your Baseband/Modem to latest OTA : http://www.youtube.com/watch?v=K2dQ2kv9kYs&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Nandroid backup in Cwm Recovery: https://www.youtube.com/watch?v=4zWSK7cO3xg&feature=youtube_gdata_player
How To Unbrick, Unroot, Factory Restore Galaxy S III http://youtu.be/p0T4FO_NZ8Y
How To Easily Backup Apps and Data to Flashable.zip http://youtu.be/OPPoKlu_4qw
How To Install CM9 or CM10: http://youtu.be/f68NgGgrwAQ
How To Back up and Restore IMEI: http://www.youtube.com/watch?v=dl6Ms3oVEDo&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Use Your SGS3 as a Netflix Remote: http://www.youtube.com/watch?v=JICq0P1Ywg4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Rom Reviews and Install Guides:
JellyWiz Touchwiz Jelly Bean 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=twDBZg4wkBk&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Liquid v2 RC3 Rom Review and Install http://www.youtube.com/watch?v=ieuy5Bx76-Q&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
AOKP 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=kjULad8XS-4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
MIUI v4.1 Jelly Bean Review and Install for Unlocked Bootloaderhttp://www.youtube.com/watch?v=azkToBXLjig&list=UU1J4DKcJXENzC-FkyMU6dow&index=2&feature=plcp
Cyanogen Mod 10 Jelly Bean for Unlocked Bootloader http://www.youtube.com/watch?v=7nW0SRKxUQk&list=UU1J4DKcJXENzC-FkyMU6dow&index=14&feature=plcp
Clean Rom Full Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=0PtIKXddfNI&list=UU1J4DKcJXENzC-FkyMU6dow&index=7&feature=plcp
Bean's Custom Stock Rom Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=napoMpZKCDA&list=UU1J4DKcJXENzC-FkyMU6dow&index=13&feature=plcp
First ROM Stock Stripped by Invisiblek: for Locked Bootloader https://www.youtube.com/watch?v=9Oek_24wEXI&feature=youtube_gdata_player
Cyanogen Mod 10 Rom Review: for Locked Bootloader http://youtu.be/2efLx_iTBDk
AOKP Android Open Kang Project Milestone 6 Review and Install for Locked Bootloader http://youtu.be/ATiFaCssKHs
Synergy Rom (Battery life and Stability) Review and Install for Locked Bootloader http://youtu.be/bj7w2nu_sKk
fix your link. you forgot the opening [ preceding the closing youtube tag.
Could you please do a back-to-stock video as well?
Thanks for doing this. First Samsung phone so it's quite new to me. Appreciate the video, it'll definitely help
Sent from my PC36100 using Tapatalk 2
Always wish these were made for each phone, the devs put so much work into making roms and root methods, but usually skimp on the instructions for those of us who aren't as experienced. Thanks for this
I will try to update this thread with any other videos I make, or I might make a separate thread. Glad its helped though.
Sent from my Galaxy Nexus using xda app-developers app
Thanks for the video. I'll be going through this as quickly as I can get home from work tomorrow!!
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
minmongoblin said:
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
Click to expand...
Click to collapse
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Lemonhead8890 said:
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Click to expand...
Click to collapse
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
trginter said:
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
Click to expand...
Click to collapse
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
NightxFall said:
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
Click to expand...
Click to collapse
That would be my guess. Put it in USB Debug mode, and plug the phone in, I think it auto-installs the ADB drivers.
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
trginter said:
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
Click to expand...
Click to collapse
What is the exact output when you type adb devices?
Good to know root is avail
Will try this tomorrow after work
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
For those having problems with this, look up "how to add a path to the windows command line“. You should not have to CD to a directory to make a command work .
Sent from my SCH-I535
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
I believe this will help a lot of you. Thanks goes to Adrynalyne....
http://forum.xda-developers.com/showthread.php?t=879701
Lemonhead8890 said:
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
Click to expand...
Click to collapse
It sounds like you're not moving to the right directory. Check to see where your adb file is, on the new SDK it's in platform-tools but if you downloaded ADB from a long time ago, it's in another folder (I think tools, but it's been a while).
What I would do is navigate to your adb file from "my computer". At the top, under address, it will show you the path you need to type. For instance, for me, I open my computer, C: drive, Android folder, then platform-tools. So my path would be:
Code:
cd C:\Android\platform-tools
Everyone's path is different depending on where you put your files.
Hi everyone.
I don't know why i have this "module". Only install the other one and nothing more.
I try to delete it then restart phone but it doesn't go away.
Not a problem, just aesthetic
That's weird....
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
Code:
adb wait-for-device shell magisk --remove-modules
and that should remove all your modules including that unknown weird one.
Also, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
Spoiler: Magisk root folder
root: /data/adb
These are just a couple of ideas...hope it helps...
Thx for your help !
The adb command works.
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
I also have the same problem.... ".core" and i cannot delete it...its like a bug or something like that?
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
is this the official version downloaded from an official source? check the magisk forum
febo17 said:
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
Click to expand...
Click to collapse
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
simplepinoi177 said:
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
Click to expand...
Click to collapse
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
What version of Magisk are you using, and where did you download it from?