Hello all, as the title says, I'm new, both to the site and android rooting in general.
I used the latest sunshine to s-off, although now i read that that wasn't necessary. What I'm trying to do is get rid of the bloatware on my phone and gain a little more control over the device itself. It is a verizon phone on the tmobile network and things like verizon vm and the verizon cloud apps and such are really just taking up space.
So the question is, now that I have s-off'd the device, where do I go next? I managed to get TWRP on there, but I just don't know where to go from there. Yes, I searched the site, Yes I searched Google, and yes, I prayed to the Skating Droid of Legend.
Any advice would be great. All of the information i have found on my own is about 2 years old.
If you already S-OFF'd it, and even got twrp going, I recommend the only thing left to do is downloading a ROM from the Android Development section (in ZIP format), saving it to your phone's internal memory or external sd card, then flashing it via twrp. That way you will have a rooted, pre-de-bloated phone. In my case, the ROM I liked best and that worked fine for me was S-ROM-JW-5.2.5 (doanloaded from this thread http://forum.xda-developers.com/ver...ment/romthe-worlds-100-m9-1-32-401-8-t3065304).
I personally selected "Global" during the flashing options, as I do not use Verizon network (I live in Brazil currently). But even so, you can change to/from Global and Verizon (and something else) in the Android settings after you are already set up.
To flash, first place the ZIP file in your phone (do not unzip it). Either internal storage or external sd-card. Then turn the phone off, unplug it (make sure you have plenty of battery like 40% or more just to be safe). Then turn the phone back on booting into twrp (power + down vol, then select Recovery, then Power). Then select "Flash ZIP" and navigate to your ROM ZIP file select it and follow the prompts. Choose "full wipe" when prompted (this will only wipe internal storage system files and apps and such and not your external sd card). After flashing finishes, just let the phone reboot (you can select Reboot while still in the twrp recovery mode).
Do not panic during first boot, it takes several minutes in the HTC logo (like some 5 or 10 minutes) until Android itself shows up and starts building itself into your phone and booting up properly.
Please proceed carefully and just to be safe, before flashing the ROM, make a full BACKUP (theres the Backup utility inside twrp) and save the backup to your external sd card or PC. That way you can recover using that backup if needed (but you should be ok).
gamekill said:
If you already S-OFF'd it, and even got twrp going, I recommend the only thing left to do is downloading a ROM from the Android Development section (in ZIP format), saving it to your phone's internal memory or external sd card, then flashing it via twrp. That way you will have a rooted, pre-de-bloated phone. In my case, the ROM I liked best and that worked fine for me was S-ROM-JW-5.2.5 (doanloaded from this thread http://forum.xda-developers.com/ver...ment/romthe-worlds-100-m9-1-32-401-8-t3065304).
I personally selected "Global" during the flashing options, as I do not use Verizon network (I live in Brazil currently). But even so, you can change to/from Global and Verizon (and something else) in the Android settings after you are already set up.
To flash, first place the ZIP file in your phone (do not unzip it). Either internal storage or external sd-card. Then turn the phone off, unplug it (make sure you have plenty of battery like 40% or more just to be safe). Then turn the phone back on booting into twrp (power + down vol, then select Recovery, then Power). Then select "Flash ZIP" and navigate to your ROM ZIP file select it and follow the prompts. Choose "full wipe" when prompted (this will only wipe internal storage system files and apps and such and not your external sd card). After flashing finishes, just let the phone reboot (you can select Reboot while still in the twrp recovery mode).
Do not panic during first boot, it takes several minutes in the HTC logo (like some 5 or 10 minutes) until Android itself shows up and starts building itself into your phone and booting up properly.
Please proceed carefully and just to be safe, before flashing the ROM, make a full BACKUP (theres the Backup utility inside twrp) and save the backup to your external sd card or PC. That way you can recover using that backup if needed (but you should be ok).
Click to expand...
Click to collapse
That's extremely helpful, thank you very much.
It turns out that Verizon is much better in my area than T-Mobile, so I wont be removing all the stuff I originally wanted to, however anything that gives me more options and power should I choose to wield it, is a welcome addition.
Thanks again.
Related
I put the update and recovery in the internal sd card. I installed tnt and when I rebooted I went into a boot loop.
I then put update.zip and recovery ( changing to sdcard2 in command) and I see the box. It installs then it reboots into a boot loop.
What should I try next?
big tony said:
I put the update and recovery in the internal sd card. I installed tnt and when I rebooted I went into a boot loop.
I then put update.zip and recovery ( changing to sdcard2 in command) and I see the box. It installs then it reboots into a boot loop.
What should I try next?
Click to expand...
Click to collapse
Per this very imformative guide: http://forum.xda-developers.com/showthread.php?t=865245
If your tablet bootloops…
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 4096, and for the second option select 64. Then, redo steps 7-10.
big tony said:
I put the update and recovery in the internal sd card. I installed tnt and when I rebooted I went into a boot loop.
I then put update.zip and recovery ( changing to sdcard2 in command) and I see the box. It installs then it reboots into a boot loop.
What should I try next?
Click to expand...
Click to collapse
Follow same procedure with microsd 2, but this time install Clockwork .8. Same setup with placing Clockwork on the device.
Once installed you can access Clockwork at power-up by pressing power + volume up. Once there, clear the cache and data (two options on main screen and use volume to scroll and home to select). You should boot up now. If not, some of the XDA elders may need to chime in to help.
If still in bootloop, open Clockwork again, but this time go to bottom to activate USB storage. Connect USB and then activate- this should show you the internal space. Place the TnT 2.4 update in the root of it (no recovery directory).
1. Deactivate USB storage
2. Clean cache and data
3. Chose install update.zip
4. Pick the update.zip
Should be out of the loop once complete.
Try a reflash, clear cache, wipe the user data (in that order, try the next if the previous did not work). Worst case scenario is re-partitioning the SD card which seems to work most of the time.
I have mentioned this before, but I really think that our devices are either not imaged properly or our SD partitions become corrupt over time. I would also argue that clockworkmod is really a requirement for anyone using these mods. It's so critical when problems like this occur.
I tried this:
Instructions for those with clockworkmod .08:
- Extract the RAR and place the update.zip file anywhere in /sdcard (do NOT just copy the original RAR, that won't work! You have to open up the RAR and copy the update.zip inside. You don't need the /recovery folder for cwm). I would recommend putting the file on the root of /sdcard, since it will be easier to upgrade that way.
- Reboot into recovery. Do a backup first, as that's always a good idea.
- Then, choose "apply sdcard:update.zip", assuming you added the update.zip to the root of /sdcard, and run it.
- Reboot.
Note: I have heard reports that this might "Status 7" and I have no fix for that, yet. It seems to be intermittent.
-----------------------------------------------------------
Clockworkmod v.08 only update.zip (for technical users only!) :
I installed the sd card update and I still get the same reboot loop. What am I doing wrong?
The flash was probably successful, but a boot loop occurred afterwards. This does happen. Since you have clockworkmod, you have a lot of things you can do, as I mentioned.
I got it running.
I fixed the adoble flash, installed a pdf viewer, and titanium backup.
I cant't see the tabs in titanium backup for some reason.
My screen does not auto rotate even thought its set to auto rotate.
Install Adw.Launcher , if you want it to rotate.
Here is my situation, my phone is HTC myTouch 3g...I wanted to lessen the internal or system's space but can't find the right software to do it in Market so I played with my phone and what I did is restart chosing "Recovery". When I reached prompts and commands area I chose to wipe out battery memory (don't know what was the exact term but something like that)...so now, my battery won't charge plus when I did "Reboot Recovery", the phone won't start as if it wipes out all the system! So now, I'm hanging on for 30 minutes or so but nothing happened when I turned my phone on, it just shows HTC Magic and nothing else. I wonder how to fix this problem. My phone won't even connect to the PC via USB or even if I plug it through AC charger.
OK, so I figured out how to go to the Clock Recovery but still, it won't boot! Help!
Full Wipe
Wipe Cache
go to mounts and storage
format boot
format system
format data
go back to main menu
install .zip from SD Card
flash CM from there and reboot.
Replacing rom in HTC HD2 NAND
hi, new to this rooting stuff. Got android rom loaded on NAND of my htc hd2. This not like this rom so i want to try a new rom. My question is do i have to erase my phone or do anything to it before i flash a new rom. thanks.
Problem Solved but...
Here is what I did to the problem:
1. I downloaded Cyanogen Mod 6 for my HTC Magic to my PC. I also downloaded the Google Tiny Apps. I put both into a newly formatted SD card (must be FAT32).
2. Since I still have the ClockWorkMod I restarted my phone by pressing the home and power button. I pressed install from flash from the options and it gave me options to open and install both of Cyanogen and/or Google Apps, I did Cyanogen update first then Google Tiny Apps. Note that there will be only two options. I forgot to write down the exact path name.The path names were obvious so you'll figure it out when you get there.
3. Just wait until the install is finished, look at the prompt in the screen until it says done.
4. Then reboot it using the options, just press the back button to go back to Clock's home screen.
Then it is done and solved.
BUT!!!!!! My problem now is that the backlight option is missing so my phone has no backlight now.........somebody help with that glitch???
Hey everyone, I recently decided that it IS worth it to root and flash a custom rom onto my 2.3.3 LG G2X but unfortunately I'm having a bit of trouble getting to that point. I just realized that I'm unable to post a link to the guides that I used until I have more posts :c Hopefully that won't be too relevant and if it is it won't be too difficult to find them since they're the only guides pertaining to rooting a 2.3.3 I could find. Anyway, after following those guides to the tee and reaching the final step of installing the zip from the sdcard, to much dismay I realized that the zip refuses to appear on the phone. If my laptop is to be trusted it is definitely on the root of the SD card so I have no idea why this is happening. Any suggestions or responses in general would be greatly appreciated!
I've also considered simply putting the zip on the phone's internal memory, but I'm kind of at a loss for how to get to it while the phone's in this state :/
Edit: I managed to access the internal sd card but unfortunately the zip does not show up there on the phone either
Also, if more information is needed please don't hesitate to ask! I'm new to android modifcations and wasn't really sure what else to put since the phone is pretty much entirely stock save for an lg driver to fix the white noise/clicking problem on calls and the apx drivers required for this process
I'm assuming that you used the NvFlash method so you should have clockworkmod recovery installed correct? If that is the case finding the rom you would like to flash will depend on the version of cwm recovery you used. The easiest thing to do is to place the rom (it's a zip file but do not unzip it) that you downloaded onto your internal sd card and also put a copy of it on your external sd card. Then reboot (or boot) into cwm recovery by holding the volume down button together with the power button until the LG logo changes to a different color and then let go of the buttons. It should take you to cwm recovery and from there use the volume buttons to navigate and the power button to select. Navigate to and then select "install zip from sd card", then "choose zip", and then the rom you placed on the sd card should be somewhere in that list. If it says choose zip from internal and choose zip from external you can pick either one and the rom should be in that list because you copied it to both. Hope that helps
Sent from my Motorola StarTAC
Hello
I got my HTC One S s4 a couple of days ago. It was unlocked. With the guides here I managed to root it and S-off and ass I was feeling confident, I installed Maximus HD 10 rom (I think I had android 4.0.1). I followed the instructions and I even got the error described in there.
My problem starts here:
Code:
Make sure that installation was successful and press enter to reboot device.
Device will boot in system, wait till you can see device on PC and copy ROM on internal SD card once again.
Repeat ROM installation with Aroma installer, do wipe during install.
Congratulations, you have device with fully working Android 4.2.2 and Sense 5.0
The device did boot in system and everything seems to be fine, new android and sense version, ect. I pluged it to PC, copied again the firmware.zip, went to TWRP recovery but the file isn't there. I even placed it inside a folder from root but still the file doesn't apper and that's why I can't continue witht he flashing process even though it seems that there is nothing more to do.
I could leave it like that but what if I want to try another rom some day?
In thephone I see 16 gb of storage, in windows explorer 10 gb more or less. If I mount the folders TWRP lets me, I get a device showing in windows explorer that needs to be formated and it's only 48 mb
What can I do?
thanks a lot!
Hello mate.
I second this.
I am currently having the exact same issue as described here.
I have rooted my phone, superCID, S-OFF, installed MaximusHD, flashed new firmware for MaximusHD and this is where I hit a roadblock.
It began like this:
I went to TWRP, plugged in phone, mounted it (I chose to mount Data in TWRP not SD card, as SD card could not be selected) - system was asking to format the device - I chose no, and moved over the MaximusHD rom (let's call it ROM.zip) using
Code:
adb push ROM.zip /sdcard/ROM.zip
The operation was succesful, TWRP showed the file ROM.zip in /sdcard, however, when I tried flashing it, I couldn't -> the access to SD card was blocked. I followed all the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1630459
After this, I went back to TWRP, mounted SD card (this time it was selectable) and pushed ROM.zip onto /sdcard
The operation was succesful, and yet TWRP did not show the file in /sdcard.
Note: System does not ask to format the device anymore, but it shows only 50mb of storage. TWRP also confirms 50mb (47mb, to be exact)
I repeated the process, same result.
I tried to boot into system using TWRP -> reboot -> system, the phone restarts and hangs on HTC One screen.
To try something else, I went into bootloader and locked it using
Code:
fastboot oem lock
The device restarted into system, once again went into HTC One screen but this time, after a couple of seconds began optimizing apps.
A system launched. Weird, considering firmware update supposedly wiped everything off the phone, not even mentioning all the resets and wipes I did by following the thread I posted earlier. I went through first launch steps and was now in a fully functioning MaximusHD system, the one I installed the first time.
The device connected to PC easily and now it showed full storage size, with all the folders and structures inside.
Inside I found two icons which surprised me. They looked like two 0 bytes empty partitions that could not be double clicked or deleted (upon deletion system throws an error that device might have been disconnected). I tried to move ROM.zip onto there, after it finished, instead of ROM.zip now there were three 0 bytes empty partitions. This is when it struck me - my 2 previous attempts to bring ROM.zip onto /sdcard with adb push are those two partitions that were already there. I unplugged and plugged my device back on, the partitions disappeared and ROM.zip showed up.
I went back into recovery and it still showed 50mb storage size and nothing inside SD card (nothing other than two folders, TWRP and .android_secure).
I rebooted the device into system and it hung up on the HTC One screen. I unlocked my bootloader and locked it again using
Code:
fastboot oem lock
and was able to return to system. Somehow, locking my bootloader lets my device get past the HTC One screen. However, the system started fresh again so I lost all the apps that were meanwhile installed (a file manager) and all settings. I went through the process and was back into working system. This is the moment where I am now, confused as to what to do next.
I went into my file manager which I got from Play Store again, which showed the entire folder structure. When I pressed back to go into the root, I was surprised to see that I actually wasn't in /sdcard.
Right now, the exact same folder structure seems to be located in four places on my phone:
/storage/emulated/legacy
/storage/emulated/0
one of these two were on default in the File Manager,
also found one here:
/storage/sdcard0
and also in:
/sdcard
My theory is that the file system in /sdcard gets wiped every time the phone is restarted and somehow brought back fresh onto /sdcard, but it doesn't make much sense and doesn't explain why TWRP shows completely different paths.
I also flashed TWRP to the newest version, to no result.
I fixed my own issue 5 minutes after posting this response...
I skipped the point where you have to install TWRP that is given in the Install Package in RUU mode. This was the root of all problems.
Reflash your firmware, following the instructions here: http://forum.xda-developers.com/showthread.php?p=45621060 (post 68).
What a way to waste 5 hours just because i thought I don't need TWRP because I already had it installed.
Good luck on your issue.
How I unbricked "Decryption unsuccessful" The password is correct but... (Apps2SD)
Hello, I don't usually post in tech forums, I usually the guy that only reads,
but this is the time when i could not find the straight answer to my problem and had to google the solution out of similar posts, so I decided to glue everything together and write my solution to this particular situation,
so I might save a lot of time to someone who got in exact or similar situation.
Sorry for my crappy English, but here we go.
What this post trying to solve:
You stuck at boot loop: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
and how to make it work Apps2SD with Huawei P9 SD card with enabled password protection.
Basically my Huawei P9 (EVA L-19) with Android 7.0 Nougat got running out of internal space, and i am really a heavy user on apps. Kirin 955 handles just fine as long as it has at least 10Gb of internal free space.
I have SD card 64Gb, but huawei stopped support, native move apps to SD, long time ago. My device is rooted, so I was searching for a solution. There is few apps that can transfer your internal memory apps to SD by using root, but the one that actually worked for me is Apps2SD. The thing is, my SD card is password protected (Huawei native function) I want to keep this function in case of device getting stolen.
Problem is, many third party apps that move your apps to SD, does not know anything about Huaweis SD card password feature. In fact (as far as i tested) only Huawei phone allows you to enter password and show contents of SD card, no PC, or for example Samsung phone will recognize this SD card.
So i was messing with Apps2SD, partitioned my SD card in to 2 primary partitions, 1- exfat, 2- Ext3. It works kinda fine, but after reboot, there is delay, Huawei unlocks SD card after main boot part, and Apps2SD does not understand this and show that it failed to mount second partition.
In this case, Apps2SD starts giving you solutions, one of them is this ADVANCED mounting option. It does not tells u about any dangers, nothing really.
I chose that option to see if it will be able to see second partition contents faster, rebooted - boom bricked.
You see the message: "Decryption unsuccessful" and asks you for decryption password. It might be SD card password, not sure, it does not matter, because you can type ANYTHING and it always say:
"The password that you entered is correct but unfortunately your data is corrupt". And gives you only option: fully data factory reset. Now hold your horses, dont press that. I just knew that this is bull**** and no way
my personal data is corrupted, its just some hadshake issue. (I was right i fully recovered everything up n running)
Assuming you got in this mess, your device must be rooted and you probably have TWRP recovery, cause Apps2SD work only with rooted devices.
To recover from "Decryption unsuccessful" boot message and restore all data and settings:
Got to TWRP recovery by holding power button and volume UP (after phone vibrates, hold both buttons 2sec more and then release power button, and then after 2sec more release volume up, cause if
you do this too fast, u will end up in wifi recovery by Huawei, and it wont work anyway cause your device rooted).
Then go to advanced and file manager, locate sdcard folder (this will be internal memory, not external), you should be able to see all of your personal files! Copy them to flash drive by connecting with OTG.
What we gonna do now is: do a full nandroid backup: TWRP, backup, check: BOOT, SYSTEM, DATA. and do a backup to flash drive connected with OTG or hard drive if it works for u.
After backup is done, go to WIPE, select format data, select DATA partition and see what original file system it uses. Now format in any other system, then reformat again to your original file system.
DATA partition somehow lost its encryption handshake key and this caused the problem, reformatting fixes it.
Now do a full wipe as if you would install new rom, wipe: system, data, storage, cache, dalvic cache.
Restore your previous nandroid backup, reboot to system,now your phone should boot with all the apps and settings just as you left.
You might be missing some pictures and other media in main storage, just connect your P9 with usb cable to pc, and restore previously backed up media from flash drive manually in pc interface (copy paste, replace all),
some small minority files might wont copy, don't worry about it, Im not sure but they are mostly indexing files, all ur media will be back in place.
Now, how to make Apps2SD work with this configuration?
Don't use that advanced method to find SD cards second partition, use any of first 3, the 3rd one worked for me just fine, cause its SU library based one.
Don't move your apps fully to SD, or they will "disappear", move everything except APK, ODEX, DEX (Lib is optional, you usually can move this one just fine). SO basically app core will stay in main storage but cache and app data will be on second SD card. This way, after you reboot your phone, you will have to wait like 3mins and App2SD will link your files to apps itself just fine. It might will show some errors right after reboot, but after Huawei unlocks its card, files will be linked, and apps wont be "gone" cause app core still stays in main storage.
This way i managed to save a lot of space and move most of app storage to SD card, P9 became very responsive, even in 2018 this is a really fast smartphone.
Sorry for a messy post, I'm not a writer, but I hope this helps to someone!
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
So glad this helped someone
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
zgfg said:
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
Click to expand...
Click to collapse
I'm not entirely sure what caused it, but I suspect Apps2SD just like in the original post (I installed/tried to use it shortly before the problem occured).