[Q] Wondering if i can do this - Motorola Droid RAZR

I have a Verizon droid RAZR that the screen has cracked in many places. I have bought a new phone and have no plans for ever using this as a phone. What I would like to do is install a ROM over the stock one, not dual boot both. I was also wanting to get rid of all of the phone stuff, no Verizon apps, no SMS, and no phone logs. I would use this like a tablet and would love to save as much space as possible. I don't need the moto docks (I don't have one). Basicly strip this thing down to just bare necessities. Is it even possible to do this? If so is there a ROM that gets great battery life? Thanks for reading my question.
Nomad7801

You can flash ROM on your stock slot and then delete the useless apks.
Try any AOSP ROM. It should work fine.
Tapatalk with RAZR HD

I have downloaded tonyt's aokp rom. I have extracted the rom to its own folder and have looked at the apps in the app folder. System>app. I am not sure which of these I can get rid of. I would like to get ride of anything that is VZW or phone related just keeping maybe the contacts. I dont know what apps should be gotten rid of with out breaking the rom. Sorry I'm a noob. All I have done was flash a few roms, never tried to remove apks before. Do I need a cellphone broadcast for location services like maps and for the in browser location? I have safestrap installed. It will not let me flash a rom over stock rom. I am trying to find a way to get cwm or twrp installed instead.

ok bricked my phone. Device would restart and get the red moto logo, then nothing, blank black screen. rebooted the phone and could not get to safestrap. Used Matt's utility to install jb and reroot phone.
The procedure that I used to install the rom on my stock image is as follows:
1. copied rom zip to micro sd card
2. booted to safestrap
3. wiped cache, delvic, and system
4. installed rom zip through safestrap
5. no errors got success
6. reboot got nothing

I think anything could still happen even if SafeStrap didnt indicate any error after installation, that's why backup is important, also this ;
ChungHung.Chen said:
Notice 2 - MAKE SURE you see "Update partition detail...." in SafeStrap log console before you press "Reboot System" or you will not get boot!
Click to expand...
Click to collapse
Just sharing what I heard
Cheers

nomad7801 said:
ok bricked my phone. Device would restart and get the red moto logo, then nothing, blank black screen. rebooted the phone and could not get to safestrap. Used Matt's utility to install jb and reroot phone.
The procedure that I used to install the rom on my stock image is as follows:
1. copied rom zip to micro sd card
2. booted to safestrap
3. wiped cache, delvic, and system
4. installed rom zip through safestrap
5. no errors got success
6. reboot got nothing
Click to expand...
Click to collapse
You will need to do a complete wipe when flashing a new ROM, including /data.
Use latest SS. And make sure the ROM is compatible with the latest SS.

neo.ank said:
You will need to do a complete wipe when flashing a new ROM, including /data.
Use latest SS. And make sure the ROM is compatible with the latest SS.
Click to expand...
Click to collapse
How do I format the internal storage? I have about 3 roms I have running and I have games and apps that I have uninstalled that left behind folders in root folders and some apps that did not get uninstalled also left behind some data. I tried doing a factory reset and also tried using safestrap to wipe internal but it fails. I made a folder in my system folder and put 2 pics in it then factory reset, wiped system data, and checked every box in the advance wipe options and that folder (along with the others) are still there.

nomad7801 said:
How do I format the internal storage? I have about 3 roms I have running and I have games and apps that I have uninstalled that left behind folders in root folders and some apps that did not get uninstalled also left behind some data. I tried doing a factory reset and also tried using safestrap to wipe internal but it fails. I made a folder in my system folder and put 2 pics in it then factory reset, wiped system data, and checked every box in the advance wipe options and that folder (along with the others) are still there.
Click to expand...
Click to collapse
Every slot has its own /data partition.
After you activate a slot, wipe /data along with system and cache.
That is called full wipe. It will remove all your apps,files and user settings will be deleted.
Then flash your desired ROM.

Related

[Q] Ghost of ROMs past haunts my Vibrant

I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone

System and user apps accidentally frozen

READ AT THE END OF THIS POST FOR THE SOLUTION
I accidentally used Titanium Backup's widget to frost all system and user apps, leaving mi phone in a infinite boot animation loop. I dont have aNandroid Backup and I would really love to solve this issue without flashing.
I found at Titanium Backup's troubleshooting webpage that I could use this command with adb to solve my issue:
Code:
Type the following command (replace with /dbdata/system/packages.xml if you have a Samsung phone):
busybox sed -n 's/<package name="\([^"]\+\)".*enabled="false".*/\1/p' /data/system/packages.xml | while read PKG; do pm enable "$PKG"; done
but it just says: No such file or directory (yes, I changed /data to /dbdata as stated in the webpage)
Any idea on how to solve this issue?
Thank you!
**EDIT:
This is the way I managed to get my phone working again without having to flash or wipe:
1. Boot in recovery mode and used adb pull command to extract "packages.xml" and "packages-more-backup.xml" from /data/system/
2. Open both files with Wordpad and replaced all protection="2" or "3" lines to protection="1".
3. Also, and very important, replaced all enabled="false" lines to enabled="true"
4. Boot in recovery again and used adb to delete old "packages.xml" and "packages-more-backup.xml" files and push the new ones.
5. Reboot and Voila!
6. Boot once again in recovery mode and fix permissions to avoid any problem.
Hope that this could be usefull to someone else having this horrible problem.
Thank you all!
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
nitox.n2o said:
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
Click to expand...
Click to collapse
I tried with /data too but same result.
shadow65781 said:
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I know I could do that but I would really like to restore my system as it was
Help please
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Simba501 said:
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
Click to expand...
Click to collapse
Pretty sure that's not gonna work because the frozen apps settings are at packages.xml file, but I can't access it I don't know why
jhermit said:
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Click to expand...
Click to collapse
I tried doing that right now but it didn't worked
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
shokuchi said:
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
Click to expand...
Click to collapse
Wrong forum dude
Sent from my Zanpakuto using Getsuga Tensho!
<deleted>
ZIP for unfreezing apps
For those, who accidentally frozen important system app: here quick solution without factory reset, reflashing and ADB
It automatically edits files as described in first post.
You should have unlocked bootloader. If no, ZIP useless because unlocking wipes all data.
Download both ZIP's and just flash them via custom recovery (TWRP / CWM)
If first throws error try second and vice versa. 2nd with mark "New" contains newer updater-binary that must be compatible with recent TWRP.
Then all apps will be unfrozen, so phone will boot.
Fix compatible with all Android versions.
Note: also you can somehow (ADB or filemanager in TWRP) delete file /data/system/0/package-restrictions.xml
More correct to edit that file which ZIP actually do, but deleting not harmful too.
tags: unfroze apps, auto-unfroze, defrost apps, unfreeze apps, 5596
Bonoboo said:
For those, who accidentally frozen system app there is quicker solution without factory reset and ADB.
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen.
Compatible with all Android versions.
Click to expand...
Click to collapse
THANKS MAN!! i just signed up to say thanks! you just saved my life :highfive:
Bonoboo said:
For those, who accidentally frozen system app here quicker solution without factory reset and ADB
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen, so phone will boot.
Compatible with all Android versions.
tags: unfroze apps, auto-unfroze
Click to expand...
Click to collapse
Thanks very much for the zip. It worked great
Same Problem
Does anyone have an updated version of that zip? I also froze an app linked to the device and it won't boot, even after factory resetting it. Tried running the zip on my t-mobile GS4 (probably newer than that zip) from the SD card in recovery mode, however it didn't unfreeze it.
Any help greatly appreciated!
pianoplayer55 said:
Does anyone have an updated version of that zip?
I also froze an app linked to the device and it won't boot, even after factory resetting it.
Click to expand...
Click to collapse
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Bonoboo said:
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Click to expand...
Click to collapse
Yup, unfortunately I did select wipe data on the recovery screen. I am also stuck in an infinite boot up loop and cannot access the phone to install any apps. How can I use a custom recovery to run the zip file if i cannot access the phone? Instructions much appreciated. Thanks again.
pianoplayer55 said:
How can I use a custom recovery to run the zip file if i cannot access the phone?
Click to expand...
Click to collapse
ZIP – it's not app.
Again, you need to install custom recovery.
Here link to TWRP and how install it via Odin on PC.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Bonoboo said:
ZIP – it's not app.
Again, you need to install custom recovery.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Click to expand...
Click to collapse
Downloaded TWRP with Odin and ran custom recovery without a change after the zip (this must have been a deeper-rooted problem in the OS itself), however in the meantime I formatted the system partition, removing the operating system. Installed Kies and ran the update. It reinstalled the OS and I'm good now. Most stuff was backed up anyways. Thanks guys for your time :good::good:
Which apk is the culprit?
Man, I wish I'd found this thread before restoring my phones internal ROM. Had it rooted and set up in every way I like except removing bloatware.
Using TB, I froze a system apk that shut down my System UI and sent the phone bootlooping. What I'm trying to determine is WHICH apk(s) I froze that caused this. I thought I had researched each one that didn't seem obvious, but I musta missed one or one of the 'obvious' ones wasn't so obvious.

[Q] Can't load ROM's with fakeCID ulock?

Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.

Question about how to total whipe

After coming from stock I rooted and installed imperium, in it's aroma installer I choose to have nexus 5 walpapers, then after I reflashed stock rom via odin and rooted, then reflashed a custom rom in the path emulated/0/0/imperiun there are about 15nexus 5 walls, if I delete them after a restart they reappear, if I delete hem through my laptop after a reboot they are still there. I always do a ful whipe when installing a new rom, eaven when I update, but they are still there. Is there a way to get rig of them, or to format the emulated folder when I install a new rom?
dark'em said:
After coming from stock I rooted and installed imperium, in it's aroma installer I choose to have nexus 5 walpapers, then after I reflashed stock rom via odin and rooted, then reflashed a custom rom in the path emulated/0/0/imperiun there are about 15nexus 5 walls, if I delete them after a restart they reappear, if I delete hem through my laptop after a reboot they are still there. I always do a ful whipe when installing a new rom, eaven when I update, but they are still there. Is there a way to get rig of them, or to format the emulated folder when I install a new rom?
Click to expand...
Click to collapse
Yes there is a way to totally format your whole phone (even the system folder). MegaWipe can do that: http://forum.xda-developers.com/showthread.php?t=1832326
Note: MegaWipe will delete your ROM from your phone as well, so you will need to download a ROM and place it in your external sd and after flashing MegaWipe, flash the ROM without rebooting the phone. Because there will be no system to load if you install no ROM.
This is one way to do that. I think there are other ways to do this also.
Thank you.
vinte007 said:
Yes there is a way to totally format your whole phone (even the system folder). MegaWipe can do that: http://forum.xda-developers.com/showthread.php?t=1832326
Note: MegaWipe will delete your ROM from your phone as well, so you will need to download a ROM and place it in your external sd and after flashing MegaWipe, flash the ROM without rebooting the phone. Because there will be no system to load if you install no ROM.
This is one way to do that. I think there are other ways to do this also.
Thank you.
Click to expand...
Click to collapse
Thank you! This is very helpful

2 questions regarding a new Cyanogen Mod installation with Safestrap

How do I make my stock partition smaller, or remove it completely to give to my Cyanogen Mod slot?
What values would I edit in the build.prop file for a Razr Maxx with Verizon?
Thanks a lot!
TheAndroid1 said:
How do I make my stock partition smaller, or remove it completely to give to my Cyanogen Mod slot?
What values would I edit in the build.prop file for a Razr Maxx with Verizon?
Thanks a lot!
Click to expand...
Click to collapse
1. You can just wipe stock slot and install CM on it. You have to do it fresh and not restore a backup from another slot.
2. Why do you need to edit your build.prop?
Draxin said:
1. You can just wipe stock slot and install CM on it. You have to do it fresh and not restore a backup from another slot.
2. Why do you need to edit your build.prop?
Click to expand...
Click to collapse
1. Is there another way to take space from the default slot and give it to the CM slot without having to reset it?
2. Because I need to download some carrier-specific/manufacturer apps that have all of my contacts.
TheAndroid1 said:
1. Is there another way to take space from the default slot and give it to the CM slot without having to reset it?
2. Because I need to download some carrier-specific/manufacturer apps that have all of my contacts.
Click to expand...
Click to collapse
1. No, stock slot, is stock slot... all of that is predetermined space of the partition... If you have titanium backup Pro and a custom launcher... all you will really lose is time. Make sure you are saving to ext. sd just to be safe, backup your user apps, backup again for modified data, and you are fine. For the custom launcher, save your setup. After you flash over, restore. Depending on what/how much you have it could take a couple hours... some games that require extra data, you will still have to download it but, your progress should still be there. Double check if it is a game, as some of them only save via a cloud.
2. I may be ignorant to your particular situation/apps, but, if your previous device was a an android device, and you saved your contacts to your google I.D. they should be waiting for you, when you reactivate from the wipe/flash. When I got my first droid years ago, I was coming from a crappy flip phone from att, they were able to flash my conacts from the att sim over to my new droid. All my contacts are now saved via google.. so it doesn't matter what phone I boot up.. my contacts are waiting for me.
If I helped you, hit the thanks!
Draxin said:
1. No, stock slot, is stock slot... all of that is predetermined space of the partition... If you have titanium backup Pro and a custom launcher... all you will really lose is time. Make sure you are saving to ext. sd just to be safe, backup your user apps, backup again for modified data, and you are fine. For the custom launcher, save your setup. After you flash over, restore. Depending on what/how much you have it could take a couple hours... some games that require extra data, you will still have to download it but, your progress should still be there. Double check if it is a game, as some of them only save via a cloud.
2. I may be ignorant to your particular situation/apps, but, if your previous device was a an android device, and you saved your contacts to your google I.D. they should be waiting for you, when you reactivate from the wipe/flash. When I got my first droid years ago, I was coming from a crappy flip phone from att, they were able to flash my conacts from the att sim over to my new droid. All my contacts are now saved via google.. so it doesn't matter what phone I boot up.. my contacts are waiting for me.
If I helped you, hit the thanks!
Click to expand...
Click to collapse
Ok, I know what I'll be doing this weekend. Thanks!
EDIT:
Will everything will work out if I install CM on the stock, and then delete ROM-Slot1?
TheAndroid1 said:
Ok, I know what I'll be doing this weekend. Thanks!
EDIT:
Will everything will work out if I install CM on the stock, and then delete ROM-Slot1?
Click to expand...
Click to collapse
Keep slot 1 and it's backup til you have the stock slot the way you want it. That way, if you forgot something, you still have what you need til you figure out what you missed and it isn't gone for good.
When you do your wipes DO NOT TOUCH internal storage and micro SDcard... that is all your personal data.. there is where your backups are... you wipe them your screwed.. pictures.. music, all of it is gone, and no one can help you!
Draxin said:
Keep slot 1 and it's backup til you have the stock slot the way you want it. That way, if you forgot something, you still have what you need til you figure out what you missed and it isn't gone for good.
When you do your wipes DO NOT TOUCH internal storage and micro SDcard... that is all your personal data.. there is where your backups are... you wipe them your screwed.. pictures.. music, all of it is gone, and no one can help you!
Click to expand...
Click to collapse
I've done what you've said, booted on to the stock ROM, and it's been on the CM boot screen for an hour, I still have the CM installed on stock ROM 1, what would've caused this problem?
TheAndroid1 said:
I've done what you've said, booted on to the stock ROM, and it's been on the CM boot screen for an hour, I still have the CM installed on stock ROM 1, what would've caused this problem?
Click to expand...
Click to collapse
Lol.. now you know why you wanted to keep slot 1. Either the stock ROM didn't get fully wiped, the CM11 didn't install properly, or it was a bad download.
So. Just a recap, you are using safestrap 3.65 or higher. When you did your wipe, did you just factory reset, or did you go into advanced wipe and wiped Dalvik cache, android secure, data, cache, and system? The CM thread recommends advanced wipe, and doing it three times!
Draxin said:
Lol.. now you know why you wanted to keep slot 1. Either the stock ROM didn't get fully wiped, the CM11 didn't install properly, or it was a bad download.
So. Just a recap, you are using safestrap 3.65 or higher. When you did your wipe, did you just factory reset, or did you go into advanced wipe and wiped Dalvik cache, android secure, data, cache, and system? The CM thread recommends advanced wipe, and doing it three times!
Click to expand...
Click to collapse
OK, I am gonna just start from the absolute beginning again:
I am flashing the Razr back to factory default with RSD Lite... Complete
Booting into the stock Android installation... Complete
Rooting device with RazrBlade... Complete
Installing Safestrap V3.65... Complete
Rebooting into Safestrap recovery... Complete
Wiping ROM Slot 1 3 times, wiping the same as 2 steps below... Complete
ADB Push CM onto /sdcard/
Install and configure CM on ROM Slot 1 as a fallback...Complete
Advanced wipe Stock slot 3 times, wiping the Dalvik cache, Android secure, data, cache, and system, this is where I messed up... Complete
Install and configure CM on Stock slot...Complete
Delete ROM Slot 1... I'll delete it once I have the Stock ROM fully finished.
It works, thanks for dealing with my stupidity
TheAndroid1 said:
OK, I am gonna just start from the absolute beginning again:
I am flashing the Razr back to factory default with RSD Lite... Complete
Booting into the stock Android installation... Complete
Rooting device with RazrBlade... Complete
Installing Safestrap V3.65... Complete
Rebooting into Safestrap recovery... Complete
Wiping ROM Slot 1 3 times, wiping the same as 2 steps below... Complete
ADB Push CM onto /sdcard/
Install and configure CM on ROM Slot 1 as a fallback...Complete
Advanced wipe Stock slot 3 times, wiping the Dalvik cache, Android secure, data, cache, and system, this is where I messed up... Complete
Install and configure CM on Stock slot...Complete
Delete ROM Slot 1... I'll delete it once I have the Stock ROM fully finished.
It works, thanks for dealing with my stupidity
Click to expand...
Click to collapse
Not stupidity. Ignorance (for lack of a better word... look up the true meaning if you are taking offense.)
And just so you know, you probably went through a few extra more steps than you needed too. Stock wasn't damaged, just needed to be thoroughly wiped then reinstalled. Also if you had a backup of Slot one, after you did the firmware reflash with RSD then root and recovery, you could have just restored your slot 1 backup.. same thing, less time. Just a couple of tips.
It is certainly good that you aren't afraid to just reflash a fresh firmware though, that can solve a lot more problems than you think. Hone your searching skills, and you are golden

Categories

Resources