Hi Guys, i found a thread about swapping the external SD to be internal SD here
Credits to
Souffre
chongns
I have mod the script to suit our device.
1. Enable developer mode in about phone
2. Enable android debugging mode
3. Change USB mode to MTP
4. Flash zip from recovery
Note:
Script is not tested throughly, flash at your own risk
remember to copy your sdcard0 content to sdcard1
if you disable and enable android debugging mode, it will revert back to default, you have to reboot the phone with debugging mode on.
if you change to Mass Storage mode, it will revert back to default, you have to change to MTP mode and reboot.
/emmc and /sdcard folder are not swapped.
{
"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:
Weird, at first it worked for me and then after restore it doesn't work. Maybe here is something to figure out what the issue might be
This feature was available in stock Atrix 2 if I could remember correctly.
It was available up to before the 4.2 JB. I will mess around with the code to make it work correctly. I don't need it but it comes handy for some
Removed the download link for now. Until figure out
Others interest it in finding a way to make it work for our devices feel free to look into the link at op.
TecknoFreak said:
Removed the download link for now. Until figure out
Others interest it in finding a way to make it work for our devices feel free to look into the link at op.
Click to expand...
Click to collapse
Anymore work being done with this? I'd love to use this as being a former A2 user so I'm use to this set up.
It can be done yes but the code is not recommended as this moment due incompatible with kitkat code. It can easily damage your sim or even yoir phone.
Related
Hey guys,
Big thanks to @autoprime for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.
If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.
If System Update is constantly bugging you to update, follow the directions below:
1) Enable USB Debugging
-Go to About phone and tap on Build number 10 times to enable Dev Options
-Enter Developer Options and enable USB Debugging
2) Download and Install the Debloater tool (this happens on your computer)
-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe
-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg
3) Connect your phone via USB. Make sure to install any drivers needed
4) Watch for pop up requesting ADB Access on your phone
5) Launch the Debloater tool
6) Select OK on the popup
{
"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"
}
7) Click the top left button
8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top
Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
I just ran this and it doesn't show LGDMSClient.apk.....weird
So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"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"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk
So I bricked my CM android one 2nd gen and it's not booting up, I can only see boot page like forever.
How did I come to this?
I cleared the cache in recovery then it somehow corrupted the /cache folder.
What I forgot to do is I did not enable OEM unlocking in settings so I cannot flash anything in flashboot and adb.
I'm stuck because my phone is
1. Not rooted
2. Bootloader locked
3. No custom recovery
4. Stock Android
What I plan to do now is to use the QPST or miFlash, I have already installed the necessary drivers and I can see my phone detected in download mode (using COM port)
My problem is I don't know where to look for the files needed. Or I'm not sure if these are the correct files I need because I just got the screenshot from other qualcom based phones. But I want to try it.
{
"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"
}
Kindly help me please where can I get these files?
prog_emmc_firehose_8974.mbn
settings.xml
MPRG8974.mbn
8974_msimage.mdn
rawprogram0_64G.xml
patch0.xml
Thanks in advance
Or you are free to suggest other methods if you have
Try this bro
They have all the xml files you needed as well as the right rom for those tools. You can also download the tool their using flash its easier and better. Let me know if you succeed.
http://forum.turkdevs.com/konu-6-0-1-stock-qfil-dual-general-mobile-android-one-4g-mmb29k.html?pid=95110
Incase you dont have an account lemme give you the gdrive link for the rom with the xml files.
https://drive.google.com/file/d/0B065LdNGqJLGM1BoZWNxbTFBSDA/view
Password: forum.turkdevs.com
Goodluck kabayan! :good:
I'll try this method but it says
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
:'(
Hi everyone,
few days ago i decided to flash custom ROM instead of my stock 4.1.1 android to my Smasung Galaxy S3 LTE. Everything seems to be fine but when i wanted to make backup through CWM it did it but to the last cwm folder in storage/emulated and then i couldn't make recovery from it. The path of my actual place where is the data is storage/emulated/0. I don't know why the old files are saved in storage/emulated, i can't see them in my windows. Only root browser can show them. Can i delete them? Or can i just change my new storage/emulated/0 path to the old one and use my old apps with new ROM? This is very annyoing problem cus i've got ~16 gb Samsung, and windows shows that there is only 11 gb available and a lot of this space is coverd by files i can't even see. How can i fix it?
{
"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"
}
if something's wrong with my post just say i will try to fix this
thanks for help,
Smasiu
check if you have important files there, i get this when use dual boot or change different kernel or cwm - better use twrp hehe
open folder /data/media/0 and replace
first copy all form /sdcard (phone memory) to computer -not sdcard1
mozesz napisac po PL
My Redmi 9T phone after installing the Pixel 12 operating system (PixelExtended-4.9-chime-12.1-20220930-0442-OFFICIAL), connecting the phone to the computer, the display name is M2010J19SG. But when entering recovery mode (OrangeFox R11.1_4), the phone name and folder are empty. Any way to fix this problem? Please help me, I am using Google translate, because my english is very bad. Thanks very much
When the phone is in normal mode (system)
{
"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"
}
When the phone is in recovery mode
adb pull /tmp/recovery.log
Switch local drivers
hakudayo said:
Switch local drivers
Click to expand...
Click to collapse
Without drivers we wouldn't see device in explorer This is usage problem of OrangeFox, either MTP disabled in GUI or not well implemented by maintainer. that's why I am asking for recovery.log to see what's going on.
aIecxs said:
Without drivers we wouldn't see device in explorer This is usage problem of OrangeFox, either MTP disabled in GUI or not well implemented by maintainer. that's why I am asking for recovery.log to see what's goin
Click to expand...
Click to collapse
aIecxs said:
Without drivers we wouldn't see device in explorer This is usage problem of OrangeFox, either MTP disabled in GUI or not well implemented by maintainer. that's why I am asking for recovery.log to see what's going on.
Click to expand...
Click to collapse
I know whata going on fahg
Switching drivers from google to android or vice versa can solve the problem
hakudayo said:
I know whats going on fag
Click to expand...
Click to collapse