Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
You try flashing back to the original ROM before the patch?
fr4nk1yn said:
You try flashing back to the original ROM before the patch?
Click to expand...
Click to collapse
No, I was already running Newt's NOS ROM and I just flashed the patch/update zip for GSM. I didn't do anything else.
rossvtaylor said:
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
Click to expand...
Click to collapse
Ok, what you're probably going to want to try to do is get rid of CWM Recovery - it has proven short sighted in comparison to TWRP. Do the following;
1. Flash TWRP for the DNA (via GooManager or grab the flashable zip and flash via fastboot)
2. Wipe EVERYTHING - Davik, Cache, Data, System.
3. TWRP Main > Advanced > Sideload
4. Use the 'sideload' command via ADB to flash whichever ROM that you'd like to be running.
5. Reboot System (If it tells you no OS installed, click install from the main and install sideload.zip, normally sideloading the ROM will install aswell, but not always.)
With this method, you start with fresh radios, fresh kernels and a fresh storage.
Hopefully this helps get you back where you'd like to be. I had to do this when I switched from NEWT's NOS 4.3 GPE back to NEWT's NOS MY S5 ROM.
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
rossvtaylor said:
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
Click to expand...
Click to collapse
Glad to hear it! I've been in the modding game since the G1 was released. I know a bit or two about tons of phones. HTC & RUU. Samsung and ODIN. LG and BLEH (don't ever by an LG device). Glad that it worked out for you man, keep on keeping on.
Related
Hi everyone,
First time poster but have been reading and browsing for a couple month now and have been able to find fixes for all the issues on my own. I have however had this one issue from the beginning and have not found any fixes or even the issue being mentioned (been using TnTLite the entire time, going up the versions from early 3's to now 4.4).
When my Gtab goes to sleep or even sits idle for a while my WiFi just stops working. The connection is still there and Gtab thinks it's connected but I can't access the net until I turn Wifi off and on and then it works until I let it sit or the screen shuts off. This is annoying at the least and I would love to fix it, even if I have to go to a different ROM (but I do like TnTLite above others).
Does anyone find version 4.4 more laggy than 4.2.5? Gtab is just not as responsive and I seem to have a Flash issue where net videos crash after working for 1-15min.
Also I have CWM 0.8 and when I try to flash with a MicroSD I keep going back into CWM. I changed SDCARD to SDCARD2 in the common file but still my card is not being read. Basically if I want to install the stock ROM and nothing else I can't cause it only boots into CWM and not the SD card. I do have the card formated in FAT32 at 2048. Am I missing something, do I need to uninstall CMW first somehow?
If you re-read the first post in the TnT Lite 4.4 thread, you'll see that you can toggle the CWM back to stock recovery with some built in commands.
Yeah, I saw that as one of the options but I want to be able to patch via the micro SD card and CWM seems to be interfering with that. I mean if I revert to stock with CWM I will still have CWM installed. I want the true original state but more than that I want the MicroSD card recovery to work.
Switching to stock recovery removes CWM and will allow you to use the MicroSD to install. All you have to do is put a file named "command" in the recovery folder on your MicroSD card with the following contents:
--update_package=SDCARD2:/update.zip
When you reboot into recovery it will find that command and execute the update.zip on your MicroSD card.
Thank you!
It was my suspicion that CWM is interfering but I also had recovered from the SD card a couple times even with CWM installed, at least I think so, but it is good to know. I'm also still having issues with net video crashing now and again. The screen goes white and I have to reboot. Started when I installed 4.4 and now that I reverted back to 4.2.5 it is much better but still I had it happen just now and it never did before 4.4. The upgrade to 4.4 also slowed the tablet down which did improve as I went back to 4.2.5.
Try going into CWM and wipe dalvik cache and also do fix permissions, usually cures most of those problems after going from one version to another.
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Vigilantys said:
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Click to expand...
Click to collapse
Here is a post that explains it
http://forum.xda-developers.com/showpost.php?p=3844295&postcount=5
I have a problem. After finally talkling myself into rooting my phone I was able to pull it off sucessfully, almost. See I havent had service on my phone for 3 months. In that time I have enjoyed using it for wifi, e-mail etc. The phone always kept saying not provisioned a bunch of times but always kept functioning.
I installed cyanogen 7.0.3 (Ithink) last night and after it booted up I said "great I didnt break it" but right in the beginng when I tried to sign into my gmail (at the time already logged into my dads wifi) It wouldnt recognize that I am signed into a wifi. it just kept asking about a data plan. I dont get it.
1 year old Aria
Try going to Settings > Wireless & network settings > Mobile networks, and unchecking "Data enabled".
That was one of the first things I check. I got no idea why it won’t let me jump on internet or market even though I will see on my phone that I am connected to a strong wifi source. Then I'll use rom manager to restore back to 2.1 and my wifi will suddenly work again. It’s driving me nuts because I am having fun with cyanogen mod but the I’ll revert back to 2.1 because I have no internet
Try bypassing ROM Manager. In general there are all sorts of issues that can occur if you use ROM Manager to get to Clockworkmod on S-ON devices like the Aria. I'm not saying this is the actual cause of your problem, but it's one thing you can try.
Shut the phone off completely then do volume down + power button to get into Clockworkmod and try installing CM7 again.
Also, make sure you are doing a full wipe when you upgrade to CM7.0.3. You can't retain any settings from previous versions.
1) Boot into Clockworkmod
2) Wipe data/factory reset
3) Wipe cache partition
4) Advanced > Wipe dalvik cache
5) Partitions menu > format system
6) Install Cyanogenmod zip from sdcard
7) Install Google Apps zip from sdcard
8) Reboot
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
BeanTown_HTC said:
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
Click to expand...
Click to collapse
Yes you will still be rooted. Clockworkmod will still be installed on your phone (which is what you use to install ROMs), and the ROMs that are available on this site (including CM7.0.3) are already pre-rooted. You shouldn't ever have to use Unrevoked again.
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
Click to expand...
Click to collapse
That just means you don't have an ext partition on the SD card. It's normal.
If you partition your SD card and dedicate a portion of it to an ext partition, you can use it for additional app installation space. The Aria's internal memory is somewhat limited so this can be helpful if you like to use a lot of different apps. You don't have to partition the SD card before installing the ROM, although doing it before installing a clean ROM might save you some trouble of having to back up anything from the SD card.
You don't HAVE to partition the card if you don't want to. It's only if you want some extra app space or not.
Great it worked. My WIFI agnolidges me. That was wierd.
Thanks alot for the help.
So I've got a wifi-only Samsung Galaxy Tab 10.1" and I have gone through the rooting guide. The guide includes ClockworkMod (CWM) v4.0.0.4, which for the most part, works just fine. I'm able to flash custom ROMs, make backups, and restore backups.
I'm having a problem mounting USB storage from CWM however. I go to the "Mounts and Storage Menu" and then select "mount USB storage." When I do this, I get a message saying:
E:Unable to open ums lunfile (No such file or directory)
Any ideas what this means, and how to fix it? Is anyone else able to mount USB storage from their CWM recovery image?
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Appreciate the insight -- I hope someone else can expand. To expound on that though, how do you transfer a ROM to the SDcard if you wipe /data and don't already have a ROM available on the SDcard?
I'm worried that I'll accidentally wipe data & cache, but will forget to double-check that I have a ROM on the SDcard partition.
Not to worry, wipe data/factory reset in CWM does nothing to the sd card partition everything will still be there including the ROM file you transferred over.
However factory reset from stock recovery DOES wipe sd card data. So back up your stuff if you do this.
Oh and always make a backup in CWM so you have something to flash in case things get crazy
I'm just trying to plan for a worst case scenario -- let's say all the storage volumes are completely wiped, and all you can do is boot into CWM. On my T-Mobile G2 (Desire Z / Vision), you can mount USB storage, copy over a ROM, and install it.
Looking for some sort of equivalent ability on the Galaxy Tab.
Hmm, let me boot into CWM and see if the computer still can read the tabs storage if I plug it in from there...
Also there is always an ODIN flash.
Nope no dice, i suppose if you were in that scenario ODIN would be your option. I'm not sure if there is an ODIN flashable of stock 3.1, I know there is a .zip i always keep it for emergencies.
Sorry I miss read, there is no ODIN flash.
Would the worst scenario is when you don't even have CWM on the tab?
ODIN flash would probably be your last resort. I am wondering if anyone has run into the worst scenario and got the tab back to the factory stock ROM.
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
task650 said:
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
Click to expand...
Click to collapse
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
FillTheVoid said:
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
Click to expand...
Click to collapse
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Or you could do:
Boot cwm, then
adb shell
mount /data
mkdir /data/media
adb push stock.zip /data/media/
and flash with cwm
Voila !!!
thank you!
you just saved my tablet! thank you.
i managed to brick my tablet (or so i thought) by an interesting combination of things.
first, i installed Alegro graphing calculator. then, i encrypted my tablet. then, i tried to backup my apps, using titanium backup, and whenever it got to alegro, it crashed superuser, market, myapps, googleapps, calendar, acore...a ton of stuff. so i told titanium to ignore it and backup everyything else, and then i went to the market to try to uninstall. no dice..it force closed everything again. so i went to the settings and tried to factory reset. i went through the steps three times, and nothing happened...the tablet rebooted and was the same as i left it.
so as a last resort i went into clockwork and wiped data and cache. tried to boot, and it was stuck on the Samsung Galaxy Tab 10.1 screen.
rebooted..same...waiting hours...same.
i could still boot to odin and recovery, but i didn't have a zip on my tablet, so i couldn't flash anything. i never thought of using adb to push the zip! but this worked perfectly! (after installing the drivers again on my computer).
thank you thank you thank you!
ansonantonym said:
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Click to expand...
Click to collapse
Hey 2 questions about the restock ROM:
1) Can it be flashed over In Paris V5?
2) Can it be flashed with CWM?
Update: answered this myself: Yes it can be flashed over in Paris, and no, it has to be flashed with Odin.
I still have a question though: This is not CWM, but is it the stock recovery or do I need to flash that too? Sending the tab in for service (newton's rings)....
This is what I was looking for. I have a slow internet connection, and Clockwork was still working, but nothing else was. Flashed Task's ROM v8... it's looking good so far... You rock, dude.
This worked for me this afternoon! Was stuck in a constant reboot after thinking that the samsung update would be a good thing. Gave thanks!!! Ordered the 30 pin adapter and now dont even need it. Will come in handy though I am sure.
FillTheVoid said:
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Click to expand...
Click to collapse
This maybe complete rubbish, but I can report a similar issue with the Galaxy S2.
When I install a new ROM, I usually do this:
1/ factory reset
2/ wipe cache
3/ wipe dalvik
4/ Mount ALL the folders, then format each one
When I do this and try to mount USB storage, it says the same error message.
If you then fire up ODIN and push another kernel to the phone, everything works fine. I know its something I am doing wrong, but no idea what!
For you, the solution is to use odin to push another kernel across.
Phil
This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.
I really need help. Major problem.
My storage is not working at all (external-SD card one). I'll try to give all the info about the problem and how it appeared:
My One X+ was on CM 10.1.3 with BLADE kernel 3.1.10 #201305062233 (I didn't use the included kernel in the ROM.zip, used an older version instead). Yesterday I tried to update to CM 10.2 Nightly (I think it was 20131105) but through the CM Updater. It downloaded the ROM and I updated it without flashing the boot.img previously and the phone rebooted and got stuck at bootscreen but, ok, than I tried to flash the kernel through the One X+ Toolkit and it failed. From this point, I may have made some stupid things but here's what I did:
I forgot to clean cache and dalvik cache and since I couldn't flash new kernel I decided to go back to the previous ROM 10.1.3 and after I did it (without wiping data) it rebooted and acted weirdly so I went back to recovery and cleaned cache, dalvik and did a SD card format(!) Reason I did it was cause it didn't recognize anything on SD card when connected to PC via USB, but DID recognize everything in CWM recovery under the Flash new zip - menu. After that, I got lost. One more thing I also forgot - Google apps. I did not flash the zip and now it was deleted from SD along with ROM.zip and other stuff. I thought of bringing it back to SD, but... all I'm getting is this( image one) its emty and when I open properties it shows this (image two). When I try to copy anything on it it doesn't allow me. In phone's file manager I can access internal memory (system, sys, acct, data, rfs, root...) but inside storage-folder is only folder-emulated. No sdcard0, sdcard, legacy and that kind of stuff and if I try to crate them they disappear after reboot. Long story-short, now I can't do ANYTHING! Cant copy stuff to SD, can't flash kernels and ROMs, can't install RUU (i tried that one too-no results, and yes, I did re lock the bootloader), cant't swap recovery, can't use my phone for anything except for calling, texting and searching in the browser (but cant download anything). Another bummer is that I can't access Gapps.
So, to sum up: no way of using SD with phone or PC. I hope there is a way for using my storage again but I can't think of any.
PLEASE help if anyone knows the answer. I'll appreciate it. Thanks in advance. Any other info, just ask.
hey man i know this is a very old post but i have the exact same problem, did you find solution to this problem ?