Well recently I was trying to root my Mytouch 4g Slide and ACCORDING to this thread:
http://forum.xda-developers.com/showthread.php?t=1801106
All I had to do was flash the custom ROM as it would have the root already in there.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
Click to expand...
Click to collapse
Which I did.
I was using this kids download tools to get the files I wanted. So I extracted the boot.img and used this tutorial to flash it for me.
THAN I ran a back up in clockwork. I haven't put the files on my SD card yet, I was just jumping ahead and was not prepared.
So I tried to go back to my phones regular state, but it is stuck on the "MyTouch 4G" splash pages, doesn't move what so ever.
I than grew worried about the phone, and thought I just bricked it or something. I am still able to get into Clockwork and do stuff in it. I tried to do a restore from my backup, didnt work. Tried wiping everything then do the backup, didnt work.
So I said, well maybe its because its a custom boot.img or something and it doesnt want to work? Luckily I had a old Mytouch 3G laying around so I could put stuff on my SD card.
So I put everything the kid provided from his mediafire folder and placed it into the root of my SD card. Switched over to the 4G and tried to install the packages.
The first was the ROM. At first it didnt work, it gave me an error:
Code:
assert failed: getprop("ro.product.device") == "glacier" || getprop("ro.build.product") == "glacier"
By googling the error, I come to this thread: http://forum.xda-developers.com/showthread.php?t=2250785
And a few posts down, a person writes this:
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Step 4.OK,safe
Click to expand...
Click to collapse
I followed those steps, and it did work. It "Installed" this time.
I followed the rest of the steps until it got to the last package. When installing "grapefruit" my phones display shut off, and then when it went back on, I was back at the beginning of Clockwork. So I went and tried to install it again, and this time it gives me a (Status 0) error, with no other information.
I assumed that it was already installed or something, and it was just saying it is already installed.
I tried to reboot back to normal and I am still stuck where it says "Mytouch 4g"
So now I am on this thread: http://forum.xda-developers.com/showthread.php?t=1844910
And there are the download links, I click on both of them to get this:
{
"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"
}
And now I am here. Cant find the download for this dang it file.
Anything helpful will be greatly appreciated.
Your in the wrong forum man, the slide is called doubleshot
Related
adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"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"
}
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.
Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides
Hello, i have LG G2 with TWRP recovery and im asking how to wipe root directory of phone because i have there files from twrp and superuser and i wanna send my phone to RMA.. Full wipe (/system, /data, /cache, /sdcard) will not wipe /.. Ty for answers
Michalko5896 said:
Hello, i have LG G2 with TWRP recovery and im asking how to wipe root directory of phone because i have there files from twrp and superuser and i wanna send my phone to RMA.. Full wipe (/system, /data, /cache, /sdcard) will not wipe /.. Ty for answers
Click to expand...
Click to collapse
Follow this thread to restore your phone to stock.
http://forum.xda-developers.com/showthread.php?p=45293512
This will wipe everything (including internal SD card) and return your phone to the same state as if you were pulling it out of the box for the first time.
Not exactly... After this method the phone status remains "rooted" when booted in download mode. Couple of users reported this problem...
Edit: here's the fix http://forum.xda-developers.com/showthread.php?p=52991286
jake.the.cake said:
Not exactly... After this method the phone status remains "rooted" when booted in download mode. Couple of users reported this problem...
Edit: here's the fix http://forum.xda-developers.com/showthread.php?p=52991286
Click to expand...
Click to collapse
That tool does not unroot your phone. All it does it trip the root flag so when you boot into download mode it says unrooted. It is meant to be used so that if you take your phone into your carriers store and an associated wants to check if its rooted, it will say its unrooted when the associate puts it in download mode, but it is in fact still rooted. This DOES NOT unroot the phone.
See attached screen shot:
{
"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"
}
Sure. But after you flash kdz file with flashtool the phone isn't rooted anyway, although in DLM it states "rooted"...
As I undrstand it, somehow after you flash kitkat kdz it misses some files and status "rooted" appears in DLM. Explained here: http://forum.xda-developers.com/showthread.php?t=2703501
Tapatalk na LgG2
jake.the.cake said:
Sure. But after you flash kdz file with flashtool the phone isn't rooted anyway, although in DLM it states "rooted"...
As I undrstand it, somehow after you flash kitkat kdz it misses some files and status "rooted" appears in DLM. Explained here: http://forum.xda-developers.com/showthread.php?t=2703501
Tapatalk na LgG2
Click to expand...
Click to collapse
Interesting. I never had that happen when I used it. I'll keep an eye on this thread in case something's happens. Thanks for sharing.
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"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"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
Hello friends, please guide me.
First I tried to install Phronesis rom in my note 3 but failed. Then I tried to install "Norma Rom Note 5 V29" but again it failed just like before.
When I click "install" option in the TWRP recovery main menu it open a new menu where it asks me to select the zip. When I select zip file it asks me to "swipe to install". When I swipe it open a new window where few commands starts appearing on screen and a blue bar starts moving at the bottom of screen. After a few seconds a command appear saying "starting aroma installer". and after this phone restarts and get stuck on note 3 logo.
Please help me in this regard. All the information about my phone is given below.
TWRP recovery version that I have is "twrp-3.0.1-0-hlte".
{
"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"
}
No one?
Some using the search function and you find out that TWRP 3 does not work with Aroma Installers. ^^ Use 2.8.7.0 and you are set.
waqar bukhari said:
No one?
Click to expand...
Click to collapse
You have already been given instructions but are to lazy to read and require spoonfeeding .
emuandco said:
Some using the search function and you find out that TWRP 3 does not work with Aroma Installers. ^^ Use 2.8.7.0 and you are set.
Click to expand...
Click to collapse
JJEgan said:
You have already been given instructions but are to lazy to read and require spoonfeeding .
Click to expand...
Click to collapse
Thanks to you. If I knew that TWRP is causing it then surely I would have searched. By the way I have been trying to use search option but due to not-knowing of what to search this option is not very helpful. That's why I have to create new thread. If I am violating any rules of the forum then I apologize.
I got the solution for this problem before you "SpoonFeeded" me. Instead of being rude you should have mentioned this at the moment when I asked this question for the first time? And I was not given any instructions to do this.
Thanks to you. If I knew that TWRP is causing it then surely I would have searched.
As i said read Questions and Answers its all posted but you refused to read .
2.2 Question:Why is it unable to flash the Rom? After flashing the Rom Zip File from TWRP, the AROMA Installer wan't open and the Phone would just reboot.
I try to flash the Rom but now i stuck on Samsung Boot Animation. Phone don't boot. What to do? Answer:
1. Have you checked the MD5 Checksum? Sometimes a Download is corrupt and a Instalation fails. You find the MD5 Checksum behind the Downladlink.2. Which Recovery you using? Sometimes the Recovery make problems install a Rom with Aroma Installer.
For now TWRP V3.0 makes trouble and don't let you instal the Rom. Try a earlier version or a different Recovery.
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
f19fox said:
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
View attachment 5290275
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
View attachment 5290281View attachment 5290283
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
View attachment 5290293View attachment 5290297
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
Click to expand...
Click to collapse
Flash magisk zip in via recovery
Austinredstoner said:
Flash magisk zip in via recovery
Click to expand...
Click to collapse
Hi. Thank you for your reply and advice. I flashed Magisk using TWRP recovery but it still won't install. Here is the screenshot. I also uninstalled the App and re-downloaded as per these instructions https://bit.ly/32P3Z9z but I still get the same error
Do you or anyone else have any more suggestions please?
Thanks!
@f19fox: Apologies to be hijacking your thread.
Build Number: NMF26X.J510FNXXU2BRJ4
Android Running Version: 7.1.1
I downloaded the IMG file of the BRJ4 raw boot image from firmware.mobi, successfully patched it via the Magisk app, and subsequently flashed the patched boot image via TWRP (selecting the boot partition within TWRP).
However, the Magisk card within the app still displays N/A within the app.