Related
I sort of started explaining my issue in the Skyraider Vanilla RC2 thread... but I didn't want to take over that thread for my own issues.
This is what happened-
I tried to install this update that was on the thread, I did a nandroid +ext back up before I did so. When I ran the update it said something about sense 3.1 update so I thought something was a bit wierd, when I turned on my phone, all my apps were rapidly force closing in front of the setup window so I rebooted my phone into recovery and did the nandroid restore. I cleared dalik cache as well, just to make sure things restored smoothly. My phone turned on, but was laggy and and the sd card was read only, it didnt show up when I attached it to my computer... I didn't have the original Vanilla RC2 file on my card, since I initially installed with rom manager, but then switched over to the amon ra recovery image so it was not there.
I rebooted into recovery again, and cleared dalik again, and cache, and then cleared the ext part of my sd card because I thought maybe there was an issue there... Now i turned on my phone my launcher is gone, some of the apps that came with vanilla in the first place are gone along with most of my other apps aside from appbrain for some reason. The phone is so laggy it is almost not even usable as a phone... What should I do?
Buy a new sd card? factory reset? I am totally at a loss..
to andrew
this is what I would do... go back into recovery and do all wipes. then format the card to your desired partitions. toggle usb and redrop the rom you want back on there and run zip from sdcard. You will have a bone stock system again and have to load all the things you want on there, but at least you will have a normal running phone again. If you happened to have things you wanted to save from the sdcard then the nandroid backup you had saved , well you should have drug it off the sdcard to your computer first. Then after you have a setup with the same rom running that you had your nandroid originally made from should load fine when you reload the backup.
1 save that nandroid backup to your pc
2 wipe completely and reformat your card
3 load the rom zip on the card and run it
4 load the nandroid backup to your sdcard and run it
or do 1-3 and start from scratch... hope this helps
buzzdroidx said:
this is what I would do... go back into recovery and do all wipes. then format the card to your desired partitions. toggle usb and redrop the rom you want back on there and run zip from sdcard. You will have a bone stock system again and have to load all the things you want on there, but at least you will have a normal running phone again. If you happened to have things you wanted to save from the sdcard then the nandroid backup you had saved , well you should have drug it off the sdcard to your computer first. Then after you have a setup with the same rom running that you had your nandroid originally made from should load fine when you reload the backup.
1 save that nandroid backup to your pc
2 wipe completely and reformat your card
3 load the rom zip on the card and run it
4 load the nandroid backup to your sdcard and run it
or do 1-3 and start from scratch... hope this helps
Click to expand...
Click to collapse
If do have a few backups saved to my computer, (from vanilla 2.5.2) but not the new one. (which is fine)
If I repartition the card, will it go back to being normal again? right now it is read only and will not show up on my computer at all so.. Also when you say wipe, do you mean wipe all data also?
yes wipe all the wipes they recovery you use offers then do a factory wipe THEN go into the format options and reformat your card. It wipes it all but you get a fresh start. then after you drag your rom back onto the sdcard and load it then do your nandroid Its possible your sdcard is hosed but not very likely
buzzdroidx said:
yes wipe all the wipes they recovery you use offers then do a factory wipe THEN go into the format options and reformat your card. It wipes it all but you get a fresh start. then after you drag your rom back onto the sdcard and load it then do your nandroid Its possible your sdcard is hosed but not very likely
Click to expand...
Click to collapse
It's alive!!!! Thank you so much =)
Gotta reload everything but, who cares!
your very welcome
I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason
I am curious what the results will be if I use the factory restore within a custom rom . I'm currently running AOKP M5.1 . I am wondering if there are any unsightly ramifications to booting into TWRP and doing a factory restore and erasing the SD card contents? I would like to do this to free up as much space as possible and remove the left over remnants of over 20 flashes and a plethora of app installs. One question I have is will TWRP wipe its own directories?
Would this be better from a stock perspective? The only time I wiped my SD card I was on stock and I really don't care to experience any directory malfunctions or card mounting issues. Doing this within a custom rom will my device still know its a kindle lol?
Edit: I know that this will not restore to 6.3.1 I'm just looking to run AOKP in a clean fresh environment including the SD card thanks for any input
Reserved
Thepooch said:
I am curious what the results will be if I use the factory restore within a custom rom . I'm currently running AOKP M5.1 . I am wondering if there are any unsightly ramifications to booting into TWRP and doing a factory restore and erasing the SD card contents? I would like to do this to free up as much space as possible and remove the left over remnants of over 20 flashes and a plethora of app installs. One question I have is will TWRP wipe its own directories?
Would this be better from a stock perspective? The only time I wiped my SD card I was on stock and I really don't care to experience any directory malfunctions or card mounting issues. Doing this within a custom rom will my device still know its a kindle lol?
Click to expand...
Click to collapse
You cannot wipe recovery from inside recovery, only the TWRP backups on your sdcard will be lost. The sdcard is on its own partition apart from recovery and system files.
Backups are backed up on my pc also the only time I have used factory restore is when I was going to flash something new. The idea of this seems simple I just don't want it to be problematic since I won't be doing a new flash.
Thepooch said:
I am curious what the results will be if I use the factory restore within a custom rom . I'm currently running AOKP M5.1 . I am wondering if there are any unsightly ramifications to booting into TWRP and doing a factory restore and erasing the SD card contents? I would like to do this to free up as much space as possible and remove the left over remnants of over 20 flashes and a plethora of app installs. One question I have is will TWRP wipe its own directories?
Would this be better from a stock perspective? The only time I wiped my SD card I was on stock and I really don't care to experience any directory malfunctions or card mounting issues. Doing this within a custom rom will my device still know its a kindle lol?
Click to expand...
Click to collapse
Factory data reset from a ROM will wipe the /data partition. It's effectively the same as "Wipe -> Factory Reset" from TWRP.
On the other hand, if you do the equivalent from the stock software, it too will wipe the /data partition, but it will also take the SD Card contents along with it. I learned this the hard way.
kinfauns said:
Factory data reset from a ROM will wipe the /data partition. It's effectively the same as "Wipe -> Factory Reset" from TWRP.
On the other hand, if you do the equivalent from the stock software, it too will wipe the /data partition, but it will also take the SD Card contents along with it. I learned this the hard way.
Click to expand...
Click to collapse
I would like to flush the SD for a clean start music video and apps can all be restored before I stick both feet in I want to make sure that it just gives me the spring cleaning that I'm looking for
Well here's what I decided to do I figured since I had a working rom on I would do it all from the factory restore in the rom. So I clicked factory restore and erase SD card after rebooting it prompted me to set up my Google account. After it restored my account and all my apps downloaded and installed, I moved some files to my SD that I wanted back on and did a backup through twrp. All said and done I was very excited to see that I had 4 gigs of remaining space on my SD card so I managed to clear out 2 gigs of excess clutter from what I have done on my kindle. The only downside I have noticed so far is when hooking my kindle to my computer it shows G: removable disk . ADB drivers are good but its no longer listed as kindle under my computer which isn't the first time I've seen this.The way I figure no big deal adb works and I can access my SD card contents on my computer how its listed is irrelevant.
Drivers driver drivers windows sucks lol at this point they are functioning so I will not be trying to reinstall them. Later I will try another restore and wipe my SD through twrp to see if that changes probably won't make a difference I'm just gonna do it for kicks and giggles
On a device that only has 5 gigs of storage regaining 2 more gigs of play room is substantial. There was more clutter than what I anticipated I was only hoping for a half a gig and I'm certainly thrilled by 2
I have a Galaxy Nexus that won't boot. It goes through a boot loop. I've tried everything to try and get it working. I've wiped data/factory reset, I've formatted system and re-flashed ROMs that were already on my phone, I've tried restoring backups from several nandroid backups. It never gets past the initial Google splash screen with the unlock symbol.
I'm going to send it in for service, but I'm wondering if there's a way to try to access the flash memory to copy all the data to my computer? I've stupidly done tons of regular backups (Titanium, SMS, nandroid) to my flash memory on my phone, but never backed it up to my PC. I can see the directory structure through CWM 5.5.0.2, but I can't mount it as a USB storage device from CWM and I assume I actually have to be booted up to use ADB.
Any suggestions?
big_raji said:
I have a Galaxy Nexus that won't boot. It goes through a boot loop. I've tried everything to try and get it working. I've wiped data/factory reset, I've formatted system and re-flashed ROMs that were already on my phone, I've tried restoring backups from several nandroid backups. It never gets past the initial Google splash screen with the unlock symbol.
I'm going to send it in for service, but I'm wondering if there's a way to try to access the flash memory to copy all the data to my computer? I've stupidly done tons of regular backups (Titanium, SMS, nandroid) to my flash memory on my phone, but never backed it up to my PC. I can see the directory structure through CWM 5.5.0.2, but I can't mount it as a USB storage device from CWM and I assume I actually have to be booted up to use ADB.
Any suggestions?
Click to expand...
Click to collapse
You should be able to do adb with the device in recovery mode. I'd recommend doing something like
Code:
> adb pull /data/media sdcard
This will copy the entire contents of the pretend SDcard on the phone (/data/media) onto a new folder on your computer called "sdcard".
I don't think there's a way to access the internal memory through CWM. For CWM to do that, is that to unmount that partition, and it cannot unmount data (where the sd-cad resides) as android wouldn't run without the /data partition, or so I've heard.
Feel free to correct me if I'm wrong.
Theshawty said:
I don't think there's a way to access the internal memory through CWM. For CWM to do that, is that to unmount that partition, and it cannot unmount data (where the sd-cad resides) as android wouldn't run without the /data partition, or so I've heard.
Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse
Recovery is not Android, it will run fine without the /data partition mounted (though there isn't a whole lot it would be able to do then, since that's where all your flashable goodies would reside). CWM accesses internal storage all day long when you're flashing ROMs and kernels and whatnot.
Thanks! I assumed ADB wouldn't work in recovery because I tried it quickly on a PC that didn't have the drivers installed. I plugged in it on my upstairs PC and I'm doing a very lengthy adb pull as I type this. Thanks!
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
jaredmac11 said:
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
Click to expand...
Click to collapse
You can either download the whole firmware and use Odin to flash or get adb setup and push a rom zip to the internal card using adb.
Sent from my SM-N900V using Tapatalk
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Thank you both. I lost my SD cards and card reader in a move so while that orders, I will attempt to utilize ADB. I'm pretty green but I'm certain there are guides out there..
moonbutt74 said:
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Click to expand...
Click to collapse
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
jaredmac11 said:
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
Click to expand...
Click to collapse
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
moonbutt74 said:
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
Click to expand...
Click to collapse
Well I was able to find a good stock firmware download, flashed that via Odin and I'm back to square 1. I am going to forego the external SD route. Perhaps too technical for me or some other hang up is abound but I am leaving that method alone for now. Thank you for your help : )