Related
When I try to turn my phone on, it will not get passed the ROM loading screen (Energy blue logo). This is because the internal memory is full.
I really need to get into the file system to delete a file (and fix the problem) or copy certain stuff out - it has pictures of my fiance on to say the least, and I really want them.
But, as Windows won't boot I can't do this in the traditional way. Obviously I can still get into bootloader - so is there a way I can access the file system? A bit of software I can run on my laptop that can somehow access the file system through bootloader mode? All I need to do is identify a c.1mb file and delete it...
The background to all this is the phone was displaying messages about 'memory nearly full' - but it had done this before and just stopped, so I left it again. Except, at some point signal reception dropped and stayed at 0. So I rebooted, and got stuck at the loading screen - which is where we've been for the last few days now.
I really hope someone can help. If you can, I'll buy you a few beers.
Thanks,
David
Phone was running WM6.5 with HSPL (3 I'm fairly sure)
How in the hell did you manage to fill your internal memory up, why not just use a SD card for storage?
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
I think I took too many photos! Though I'm not exactly sure tbh... Some bug in the ROM kept changing the save dir from SD card to internal, but I did keep an eye on the space, perhaps just a few too many photos in one night...
Anyway ActiveSync isn't working (for me at least) in bootloader mode - don't I need to have Windows Mobile loaded?
Should activesync work in bootloader mode?
TheATHEiST said:
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
Click to expand...
Click to collapse
doesnt work. you cant access the live file system from anywhere except within running wm.
You can dump off the rom partition into .raw files, but when you rebuilt it (in a ktchen) you would still only end up with the original rom as it was out of the box, no user data.
@OP, you could possibly go into bootloader, confirm 2.08.hspl, flash magldr, and then boot from an sd android, though i suspect you still wouldn't see the winmo files. (I assume there are now android builds that can be booted to and run from sd without the need for haret/winmo? i'm a nand man meself so unsure. )
It's what i'd try if it really was that critical, otherwise I'd weep for a little while, kick myself and write 'backup' post-its all over my office, then hard reset and move on.
Thanks for the advice - I will definitely try your suggestion before 'moving on', losing a whole bunch of contacts will also be a real pain.
Do you know of any threads/links explaining magldr and how it will help?
Is there no other way to access any part of the internal memory and just delete 1 file?
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Thanks
Bear in mind WP7 and winmo are two very different OSes.
WP7 has been out btw.
Once you flash the device, with MAGLDR, android or WP7, the internal storage is wiped so it makes no sense to flash it if you still want what is in it.
davenash said:
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
Click to expand...
Click to collapse
any type of flashing (nandroid, wp7 or wm) will destroy whats on there already, thus defeating the object.
There are more than two options in magldr, one of which is 'boot sd ad' for boot sd card android.
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Click to expand...
Click to collapse
its probably not an issue of the file system type, android (linux) can access fat partitions no problem. Its probably more to do with whether the sd builds can mount the internal rom or not.
Im no linux head at all, still fumbling in the dark though, so i could be wrong.
I find myself being a noob after being a lurker around here for 2 years. This is my first post. I came here to learn and pretty much felt everyone here knew so much more than I did and I really had little to post of value. About a month ago I flashed several of the ROM's and then upgraded the OS on my Windows 6.5 mobile HTC HD2 using the binaries and instructions from the xda Windows forum. Everything went smoothly and it is now running beautifully on Windows 7.5 mobile. Faster than any of my friend’s stock Win 7 phones, I might add. I'm a certified Unix Engineer and pretty much an expert on Linux having written much of the original code for printing when Linus was developing the first version. I now run Linux Mint in an Oracle Virtual box on Windows 7 Ultimate for my SMTP server. I realize this is somewhat of a regression and I apologize for boring you guys with my background but I felt the need to give a bit of personal info before getting into my request for help, so that any adviser would know that I can talk the talk as well as walk the walk. My noob status is because I came here to learn and not post stupid issues and embarrass myself, I constantly see much of that in all the forums. I have searched and read all advice I can find on xda prior to this post and find others who have had the same problem but their resolutions don’t work for me. I am at the point where I had to post. If anyone has any fresh ideas that can help, please speak up. I'm not bricked but I might as well be, I'm stuck on 3.0.1. Here is my problem.
I allowed Acer's OTA 3.2 to update my Icona A500 last Thursday. The table was rooted and I had updated the xpa_supplicant to support ad hoc wifi while on 3.1. I saved that update over to my external SD before accepting the OTA update to Android 3.2 from Acer. I was hoping that Acer had fixed the ad hoc issue but afraid I might have to re-root and reapply the xpa_supplicant after the flash. I stupidly didn't read all the cries for help both on xda and on the Acer sponsored A500 forum prior to taking on the Acer OTA update. Many of the Acer forum post now showing up are from owners who aren't technical, have no idea what rooting is and no idea even that their Android is hosted on Linux but were unhappy with superficial changes the upgrade had done to various parts of the the UI and the effects it was having on some of their apps. My issue was I need ad hoc wifi or my tab is worthless for my business needs if it can tether and travel. Again, I regress and I apologize.
You guys already know the consequences for the OTA 3.2 update from Acer so I won't go into that. I had planned to flash my first ROM this weekend anyway, as I wanted to upgrade to Tabtoony 2.1. But, after realizing that I couldn't root after the OTA 3.2 from Acer, I download the Acer recovery installer and installed thor's CWM recovery v5.0.0.0 rev 1.3.4 and used it to flash the tablet back to Android 3.0.1 via stock 1.141.07_COM_GEN1. 3.0.1 was known to be buggy and won't even keep a wifi connection for longer than 5 minutes so I couldn’t just stay at 3.0.1. So I proceed forward by then following very systematically the directions from drkalo on the xda A500 forum on flashing your first ROM. These are the step that I when through.
1. I download the Tabtoony 2.1 zip via Windows. I ran IZarc test on the zip from Windows to make sure there were no CRC problems in the zip. All files were good and I even unzip it on Windows with no errors or other problems.
2. The tablet was rooted by CWM so I didn’t need to run Gingerbreak or Iconaroot. I connected the tab to Windows via wifi after re-downloading File Manager HD from the market (I like it better than Root Explorer) because it supports network connetion to Window NTFS file system.
3. I copied the upgrade zip using File Manager HD over to my External SD card and to the Internal SD card, still unsure which one it should be on. There are several YouTube video tutorials on Flashing Tabtoony to the A500. In every one, the demonstrator copies the zip to be flashed to the internal SD card but drkalo explicitly says the external SD. I copied it over to both. BTW, my external SDHD is formatted to FAT32 could that be a problem? I know most Linux distributions have built-in support for FAT32 but I realize the core Linux used on the tab is customize and not one of the standard distributions at least as far as I know. So I have no idea what features may or may not have been removed. But the external card was visible and useable in 3.1 after I created a mnt point to it manually.
3. I then booted into recovery mode and CWM came up and I cleared several caches as suggested and I then chose “– choose zip from sdcard”. I immediately got the following of message:
E:Can’t mount /sdcard
I am then returned to the CWM recovery menu
4. I have tried formatting the sdcard from CWM. Although I still don't know which SDcard is being referred to, but I get the following messages:
Formatting /sdcard…
Error mounting /sdcard!
Skipping format….
Done.
Upon rebooting back to 3.0.1 both sdcards still have all their data on them so format truly does fail. So I'm stuck in 3.0.1 and can't get CWM to mount "the" sdcard or format it. So I can’t flash a new customized 3.2. I have gone over drkalo xda post step by step several times to be sure I'm not missing something but the results are always the same. I would be grateful for any advice or new ideas.
Thanks and I apologize for the long post.
Grady
There are already some threads with the very same question and nobody seems to know the answer.
http://forum.xda-developers.com/showthread.php?t=1294654
http://forum.xda-developers.com/showthread.php?t=1276082
http://forum.xda-developers.com/showthread.php?t=1261801
http://forum.xda-developers.com/showthread.php?t=1186535
I personally use the external sd card formatted on an Android phone to place the update.zip. CWM mounts the external card (even though the option is called mount /sdcard/ and you can choose the zip file on it.
Good luck!
Piotr
Just use a usb thumb drive, copy the rom to it, plug into your tab, boot cwm, select the rom and flash. I always use the thumb drive.
Thanks your point is well taken. I used a Windows 7 phone to format the the SD card. I noticed in one of the links that you posted for me a link to a program called SD format. That link provides a format program for Windows and Apple. But, one of things they explain is that a properly formatted SD
has a reserved area for file indexing. I've probed mine and can't find such an area visible or hidden. That may the problem. I don't have a Win machine that uses micro SDs but I'll try formatting it in my friends Android phone and see if that fixes the problem. Thanks for you help. I'll post back to this thread so anyone interested can kow the result if this resolves the problem or not.
Sent from my A500 using xda premiium
Thanks Shaun, I did notice that USB was an option. Actually that's probably the easest way. That never ocurred to me. Fortunatly I have a few thumb drives lying around unused. Bet that will work. I'll try that tonight. I still fell a bit obligated to help solve the SD card problem since it seems to be
so prevelant. I'll let you know how it goes. One question though how do you format your USB? Do you do it on Windows or your adriod device?
Thank for you help and suggetion.
Sent from my A500 using xda premium
I don't know if I have ever formated my thumb drives just the factory format. Did a windows format and it still worked fine for a test and fat 32. Have you tried a different msd card. Good luck, can get stressful.
Well Piotrdev was correct. I reformatted the drive on a friends Android phone and immediatly noticed a difference. While still in the phone it now showed a lost file folder that the Windows phone format did not create. There may hane been other differences, but I didn't take the time to explore further. I immediatly reinserted the card back into the tablet, copied over the Taboony 2.1 zip and rebooted into CWM. Chose the option - install zip from sdcard, it then ask me to choose which file to install. I navigated to the Taboony 2.1 zip, pressed the power button to select it and installation began. Several message flew by indicating installation was proceeding then it said ROM flash completed sucessfully. I did a power off and back on and immediatly saw a new spinning screen that said Taboony. It ran for about 3 minutes then went to an unconfigured login screen. I knew I had made it then.
So the lesson learned is that neither Windows FAT 32 format is acceptable to CWM, nor is CWM's format acceptable because CWM's format fails if the card is not already properly formatted because he can't mount an improperly formatted drive.
Guys thanks for all your help. I had been stuck for 2 days. I learned something and maybe the others who Piotrdev reported posted a similar issues can get theirs resolved too. I'm pretty sure improper drive formatting is the cause of most other posters problems. We need to write an SD format program for Android Tablets. There is nothing in the market that indicares that it formats SDHDs.
I now have a Taboony 2.1 Tablet which has lots of new apps not available in the market. I need to explore a bit more to see what apps were in the flash but the most needed by me is a full featured office suite and ad hoc wifi to my cell phone router. The xda Taboony Team has ported over Asus's Polaris Office and my first look at it indicated that it appearedsc that it fits the bill. Of course I've just voided my warranty, but after Acer's lockdown to preventing rooting, I had pretty much decided to avoid any updates from them in the future anyway As I told my friend whose phone I used to format the card, at the price they are selling for now, it's just a throw away if you brick it and can't recove.
Problem solved!
Peace
Sent from my A500 using xda premium
gradyzero said:
I find myself being a noob after being a lurker around here for 2 years. This is my first post. I came here to learn and pretty much felt everyone here knew so much more than I did and I really had little to post of value. About a month ago I flashed several of the ROM's and then upgraded the OS on my Windows 6.5 mobile HTC HD2 using the binaries and instructions from the xda Windows forum. Everything went smoothly and it is now running beautifully on Windows 7.5 mobile. Faster than any of my friend’s stock Win 7 phones, I might add. I'm a certified Unix Engineer and pretty much an expert on Linux having written much of the original code for printing when Linus was developing the first version. I now run Linux Mint in an Oracle Virtual box on Windows 7 Ultimate for my SMTP server. I realize this is somewhat of a regression and I apologize for boring you guys with my background but I felt the need to give a bit of personal info before getting into my request for help, so that any adviser would know that I can talk the talk as well as walk the walk. My noob status is because I came here to learn and not post stupid issues and embarrass myself, I constantly see much of that in all the forums. I have searched and read all advice I can find on xda prior to this post and find others who have had the same problem but their resolutions don’t work for me. I am at the point where I had to post. If anyone has any fresh ideas that can help, please speak up. I'm not bricked but I might as well be, I'm stuck on 3.0.1. Here is my problem.
I allowed Acer's OTA 3.2 to update my Icona A500 last Thursday. The table was rooted and I had updated the xpa_supplicant to support ad hoc wifi while on 3.1. I saved that update over to my external SD before accepting the OTA update to Android 3.2 from Acer. I was hoping that Acer had fixed the ad hoc issue but afraid I might have to re-root and reapply the xpa_supplicant after the flash. I stupidly didn't read all the cries for help both on xda and on the Acer sponsored A500 forum prior to taking on the Acer OTA update. Many of the Acer forum post now showing up are from owners who aren't technical, have no idea what rooting is and no idea even that their Android is hosted on Linux but were unhappy with superficial changes the upgrade had done to various parts of the the UI and the effects it was having on some of their apps. My issue was I need ad hoc wifi or my tab is worthless for my business needs if it can tether and travel. Again, I regress and I apologize.
You guys already know the consequences for the OTA 3.2 update from Acer so I won't go into that. I had planned to flash my first ROM this weekend anyway, as I wanted to upgrade to Tabtoony 2.1. But, after realizing that I couldn't root after the OTA 3.2 from Acer, I download the Acer recovery installer and installed thor's CWM recovery v5.0.0.0 rev 1.3.4 and used it to flash the tablet back to Android 3.0.1 via stock 1.141.07_COM_GEN1. 3.0.1 was known to be buggy and won't even keep a wifi connection for longer than 5 minutes so I couldn’t just stay at 3.0.1. So I proceed forward by then following very systematically the directions from drkalo on the xda A500 forum on flashing your first ROM. These are the step that I when through.
1. I download the Tabtoony 2.1 zip via Windows. I ran IZarc test on the zip from Windows to make sure there were no CRC problems in the zip. All files were good and I even unzip it on Windows with no errors or other problems.
2. The tablet was rooted by CWM so I didn’t need to run Gingerbreak or Iconaroot. I connected the tab to Windows via wifi after re-downloading File Manager HD from the market (I like it better than Root Explorer) because it supports network connetion to Window NTFS file system.
3. I copied the upgrade zip using File Manager HD over to my External SD card and to the Internal SD card, still unsure which one it should be on. There are several YouTube video tutorials on Flashing Tabtoony to the A500. In every one, the demonstrator copies the zip to be flashed to the internal SD card but drkalo explicitly says the external SD. I copied it over to both. BTW, my external SDHD is formatted to FAT32 could that be a problem? I know most Linux distributions have built-in support for FAT32 but I realize the core Linux used on the tab is customize and not one of the standard distributions at least as far as I know. So I have no idea what features may or may not have been removed. But the external card was visible and useable in 3.1 after I created a mnt point to it manually.
3. I then booted into recovery mode and CWM came up and I cleared several caches as suggested and I then chose “– choose zip from sdcard”. I immediately got the following of message:
E:Can’t mount /sdcard
I am then returned to the CWM recovery menu
4. I have tried formatting the sdcard from CWM. Although I still don't know which SDcard is being referred to, but I get the following messages:
Formatting /sdcard…
Error mounting /sdcard!
Skipping format….
Done.
Upon rebooting back to 3.0.1 both sdcards still have all their data on them so format truly does fail. So I'm stuck in 3.0.1 and can't get CWM to mount "the" sdcard or format it. So I can’t flash a new customized 3.2. I have gone over drkalo xda post step by step several times to be sure I'm not missing something but the results are always the same. I would be grateful for any advice or new ideas.
Thanks and I apologize for the long post.
Grady
Click to expand...
Click to collapse
I have the same problem, my CWM is not mounting my sd card, but it seems to recognize my USB flashdrive as the SD card, im super confused and i havent seen any forms that have talked about it, i never had this problem with my HD2 OR my Samsung Galaxy S
Hi,
I have an Acer Iconia A500, currently running Taboonay (ICS). I bought it in the US, and brought it to the UK with me, so I can't get it back to the place I bought it (unfortunately), or I'd return it... but hoping someone here can help me fix this:
Shortly after I bought it, the tab lost the sd card, and I've only once ever been able to see it again. While flashing Taboonay, the recovery did (once only, not reproducable) recognise the sd card, and show me the contents properly. This is the slim hope I have that it's not a hardware issue...
I have tried with multiple SD cards, formatted with different file-systems, and none of them have mounted at all, or even been recognised by the tab.
I have tried a few (can't remember the names of them now) root-level card-mount applications, and none of them have helped either. They just can't see the card at all.
If anyone has any tips for software solutions that I can try, I'd be very grateful! I would very much like to avoid a re-flash, or anything that will reset my internal storage...
Thanks,
Rich
Phyrefly said:
If anyone has any tips for software solutions that I can try, I'd be very grateful! I would very much like to avoid a re-flash, or anything that will reset my internal storage...
Click to expand...
Click to collapse
Typically EXT SD Card issues usually are software related. With the exception of bad SD Cards.
1. Update your Recovery to the most recent version.
2. Or, try a different recovery like Public Recovery
I will assume you are on an ICS bootloader, and that your recovery is correct for ICS?
If you have the V8 Bootloader installed for example, you can boot the tab to Fastboot mode, Then start Fastboot from the Android SDK on your PC. (place your recovery image in the same folder as fastboot.exe) and type;
Fastboot Flash Recovery nameofyourrecovery.img
Also, the rom you are using may need to be re-installed again (wipes and formats)
But go for option 1 or 2.
One more note. I have heard of people using the Format option in Recovery and have had success when PC formats won't work.
Along with using some specialized PC Format applications.
MD
Moscow Desire said:
Typically EXT SD Card issues usually are software related. With the exception of bad SD Cards.
Click to expand...
Click to collapse
This is good news...
1. Update your Recovery to the most recent version.
2. Or, try a different recovery like Public Recovery
Click to expand...
Click to collapse
1) I have done this many, many times before I initially gave up...
2) This is something new (or at least new-ish, I may have gone through two when I rooted, but that was some time ago)
I will assume you are on an ICS bootloader, and that your recovery is correct for ICS?
Click to expand...
Click to collapse
Don't assume anything! I am not a pro at this, although I am a techy for a living, it's quite possible I have this wrong. How would I tell?
If you have the V8 Bootloader installed for example, you can boot the tab to Fastboot mode, Then start Fastboot from the Android SDK on your PC. (place your recovery image in the same folder as fastboot.exe) and type;
Fastboot Flash Recovery nameofyourrecovery.img
Click to expand...
Click to collapse
Also, the rom you are using may need to be re-installed again (wipes and formats)
Click to expand...
Click to collapse
Really, REALLY don't want to go down this road again... and I have done many times already with no change, so don't hold much hope of that working.
One more note. I have heard of people using the Format option in Recovery and have had success when PC formats won't work.
Along with using some specialized PC Format applications.
MD
Click to expand...
Click to collapse
I was under the impression that Recovery Format formatted the internal memory on the A500 (as the internal memory is called "sd-card"). I would hate to get this wrong!
If you can suggest a PC Format app for me to try I'll give that a go too.
Rich
I have installed Public Recovery, and one change it has made, is that my boot time is significantly reduced...
I haven't had the time to do anything else yet.
Testing with an SD card shows that inserting one while the tablet is running DOES now pick up that a card is there. However, mounting it does nothing at all. Attempting to mount it through apps like DiskMount fails, but doesn't give me a meaningful error (just "Drive could not be mounted")
This seems to be a positive change, as the disk is being seen, if not understood, by Android now. First sign that there is a fix to this!
I googled for apps to format the SD on the PC, but didn't find anything (all the tips I found said to format with right-click, which hasn't worked so far)
Any further advice?
I have changed the recovery (again) to the latest Thor CWM, which claims to be good for ICS.
I am going to flash my bootloader tonight to one that explicitly works with this recovery and my current ICS ROM. I downloaded all the bits I need last night, but didn't have the time to actually flash it after all that.
I figured updating these couldn't hurt, and would ensure that I am on compatible versions.
The only thing left that has been suggested (beyond a total re-install) is formatting the sdcard with something more likely to give me a compatible format. I still lack confidence that the recovery knows the difference between my internal memory (called sdcard) and the actual SD card. For example, when installing a new recovery, selecting "install from zip on SDCard" takes me to the internal memory to select a file... This only leaves me with the option of using a specialist PC app, as was recommended, but still can't find one, so any advice here would be welcomed.
Or of course, any new course of action entirely...
Thanks,
Rich
Phyrefly said:
...
The only thing left that has been suggested (beyond a total re-install) is formatting the sdcard with something more likely to give me a compatible format. I still lack confidence that the recovery knows the difference between my internal memory (called sdcard) and the actual SD card. For example, when installing a new recovery, selecting "install from zip on SDCard" takes me to the internal memory to select a file... This only leaves me with the option of using a specialist PC app, as was recommended, but still can't find one, so any advice here would be welcomed.
Click to expand...
Click to collapse
I've used sdformat (attached) in the past or gparted (linux) will do it too...and yeh you're right to be wary...if the recovery doesnt recognise it then it will use yr internal sd...
not sure if you've got the drivers installed or not and
usb debugging is enabled
I do know that i had this issue with taboonay on HC once, never did get it figured out so just used another rom
the afterOTA tool will tell you if you have the drivers installed,
what rom and b/l you're running, yr uid and sbk and will also flash the bl and recovery for you
dibb_nz said:
I've used sdformat (attached) in the past or gparted (linux) will do it too...and yeh you're right to be wary...if the recovery doesnt recognise it then it will use yr internal sd...
not sure if you've got the drivers installed or not and
usb debugging is enabled
I do know that i had this issue with taboonay on HC once, never did get it figured out so just used another rom
the afterOTA tool will tell you if you have the drivers installed,
what rom and b/l you're running, yr uid and sbk and will also flash the bl and recovery for you
Click to expand...
Click to collapse
Sorry for not replying with results - when trying to use the "idiot-proof" tool, I supplied the world with a bigger idiot.
Somehow I managed to brick - not my tablet, but my laptop. I'm now in mourning... And looking for a new laptop.
And then I will be back to trying to fix the tablet!
(Yes, I'm fairly certain it wasn't the tool that killed my laptop, but it happened while I was using it. Can't even get to BIOS at the moment... think the motherboard fried somehow)
Rich
Phyrefly said:
Sorry for not replying with results - when trying to use the "idiot-proof" tool, I supplied the world with a bigger idiot.
Somehow I managed to brick - not my tablet, but my laptop. I'm now in mourning... And looking for a new laptop.
And then I will be back to trying to fix the tablet!
(Yes, I'm fairly certain it wasn't the tool that killed my laptop, but it happened while I was using it. Can't even get to BIOS at the moment... think the motherboard fried somehow)
Rich
Click to expand...
Click to collapse
Dude, just when you thought things couldn't get worse.
I have an old Gateway laptop with WinXP if you want to come to moscow and get it. (sound doesn't work but comes with USB CLabs Sound, needs new battery). Hate to throw it in the garbage.
MD
Moscow Desire said:
Dude, just when you thought things couldn't get worse.
I have an old Gateway laptop with WinXP if you want to come to moscow and get it. (sound doesn't work but comes with USB CLabs Sound, needs new battery). Hate to throw it in the garbage.
MD
Click to expand...
Click to collapse
As much as I'd love an excuse to go to Moscow - I think it'd be cheaper to buy a new laptop
Phyrefly said:
As much as I'd love an excuse to go to Moscow - I think it'd be cheaper to buy a new laptop
Click to expand...
Click to collapse
Does the laptop come with Girls? Mine does.
Hope you get a good deal over there. Moscow prices are horrible sometimes. And you only get HP, Apple, and Acer. And some local brands.
MD
Hello all,
My friend wants me to put android on the old HD2. I've followed the guides to install via NAND and installed hspl, magldr, and the latest radio for T-Mobile US. I've gotten as far as flashing a Sense Leo ROM and getting to the step where the phone says "Reset now...!" at which point the phone won't reset. So then I try it all over with Task29, then I get stuck at 96% for flashing radios. I've also encountered bootloops with magldr, vibration patterns while booting, and a bunch of other problems. I think the original ROM is gone due to one of the steps wiping it. Can someone please help me either get any android rom to work or revert back to stock? I've been at this for hours and it's really frustrating me. Thanks in advance.
Edit: It just occurred to me that this might have been an unlocked phone from the factory. I've tried downloading an official ROM from T-Mobile but they don't recognize it. It's a T8585.
Edit #2: Just tried flashing Artemis Rom, went to 100% and rebooted but got stuck on HTC screen. Also tried a shipped WWE ROM, but that quit at 9%. Someone please help me...
I've had similar problems with my previous HD2. Hangs and bootloops on flashing ROMS, and an overheating phone. After 2 weeks of spending evenings trying to get things stable, I finally gave up and sold the phone, got a new one, and flashing succeeded on the first try. On first HD2, it was definately a hardware defect. The guy i sold it to couldn't get it to work either. There are so many defective HD2's around...
Whats your Radio version?
Do you use AD Recovery in MAGLDR for flashing the ROMS? Try playing around with different System Partition sizes on MAGLDR repartition. My current HD2 is very picky about this, a 'wrong' system partition size results in various hanging and bootloop problems.
Using HD2 Toolkit, follow the following steps:
1) Task29 (from bootmenu)
2) Install MAGLDR (from bootmenu)
3) MAGLDR repartition (from MAGLDR USB Flasher)
4) MAGLDR AD Recovery -> install ZIP from SD card
5) Reboot, if problems, go to step 3) with a different system partition size
I don't remember which radio version I tried last. I think it may be the latest tmous one, which I don't think is the correct one seeing as this particular HD2 is an 1100. I've been flashing via USB flash because the installation instructions on the ROM threads tell me to. I have to reflash MAGLDR every time a ROM flash fails because it either goes into a bootloop, or it goes to MAGLDR but without any menu. Nevertheless, I will try out your method and report back.
Edit: Can I still use a European radio even if I'm in the US?
wcstick said:
I don't remember which radio version I tried last. I think it may be the latest tmous one, which I don't think is the correct one seeing as this particular HD2 is an 1100. I've been flashing via USB flash because the installation instructions on the ROM threads tell me to. I have to reflash MAGLDR every time a ROM flash fails because it either goes into a bootloop, or it goes to MAGLDR but without any menu. Nevertheless, I will try out your method and report back.
Edit: Can I still use a European radio even if I'm in the US?
Click to expand...
Click to collapse
What I am not seeing here is details which may pinpoint the problem.
You need to pick one rom which works for a fair number of us and detail *exactly* what you are doing.
The radio, once flashed, remains. My signature should point you to a radio known to work in the US.
Beyond that, how are you partitioning you device; what kind of sd card and how is it formatted and setup; how are you flashing the rom; which recovery are you using; are you making any changes to the rom zip file... We could go on but hopefully you understand that, according to Murphy, the 1 piece of information you forget to mention out of the 100+ is the one that would have made one of us go "aha!"
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
Okay. I will start completely over and document my actions. I'm switching to cLK since I seem to get more consistent results.
Device: HTC HD2 T8585 1100
SDcard: SanDisk 32GB MicroSDHC formatted to FAT32
Program: HD2 Toolkit 4.3.1
ROM: http://forum.xda-developers.com/showthread.php?t=2046327
Procedure:
1. Wipe with Task29 loaded from HD2 Toolkit 4.3.1
2. Make cLK Partition of 280 MB and 5 MB cache.
- Final message on phone screen: "fastboot: processing commands"
3. Install cLK Recovery in fastboot option
- Final message on phone screen: "rebooting the device"
4. Device never reboots.
wcstick said:
Okay. I will start completely over and document my actions. I'm switching to cLK since I seem to get more consistent results.
Device: HTC HD2 T8585 1100
SDcard: SanDisk 32GB MicroSDHC formatted to FAT32
Program: HD2 Toolkit 4.3.1
ROM: http://forum.xda-developers.com/showthread.php?t=2046327
Procedure:
1. Wipe with Task29 loaded from HD2 Toolkit 4.3.1
2. Make cLK Partition of 280 MB and 5 MB cache.
- Final message on phone screen: "fastboot: processing commands"
3. Install cLK Recovery in fastboot option
- Final message on phone screen: "rebooting the device"
4. Device never reboots.
Click to expand...
Click to collapse
I will be only a little help with CLK since I don't know it but..
If this is your first Android install perhaps you should try a stable rom, not an alpha one. Anyway, you don't seem to get to the rom install at all.
Is this a US or EU device? The latter has less space..
Are you SURE CLK requires 280 MB? If this us not a typo how much space is given to system and data?
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
It seems to be an EU device since it doesn't have any of the indications that it's the tmous device. But it will be used in the US.
I don't think cLK itself requires 280 MB, I set it to a higher value than what was mentioned in the ROM thread. I'm probably wrong in assuming that, when the thread says "System partition size 275," it means the cLK partition. I apologize for selecting an unstable ROM, I just picked one that I'm vaguely familiar with (i.e. CM). Should I lower the cLK partition?
wcstick said:
It seems to be an EU device since it doesn't have any of the indications that it's the tmous device. But it will be used in the US.
I don't think cLK itself requires 280 MB, I set it to a higher value than what was mentioned in the ROM thread. I'm probably wrong in assuming that, when the thread says "System partition size 275," it means the cLK partition. I apologize for selecting an unstable ROM, I just picked one that I'm vaguely familiar with (i.e. CM). Should I lower the cLK partition?
Click to expand...
Click to collapse
Look at it this way: once you get one rom to boot the rest will be much easier to try.
Okay, let's backup a little and get on common ground. It may not seem so but we're making progress.
Please keep in mind I have never installed cLK so am not sure about it. However, cLK, like Magldr, is a bootloader. As such I suspect it. Does not use a traditional partition.
I am guessing that the 280 is intended for system. The EU Leo has 512 MB if NAND space. The US (tmobile) version has 1 gb. They have, essentially the same RAM.
Your NAND memory needs to be devided into partitions: boot, system, data and, possibly cache and misc. How these are created is likely specific to your bootloader (cLK or Magldr). The file systems often are dictated by those as well - Magldr uses different formatting for the boot partition than cLK.
Anyway, you will need someone cLK knowledgeable to help if you cannot spot the problem. BTW, which version of cLK are you using? I *think* v1.5.x black is one of the preferred versions.
Once you are able to load the bootloader you can start dealing with the rom. If your device is a 512 MB EU model start with a smaller rom or one that offers DataOnEXT installation.
I will check back to see what progress you will make but first a few hours of sleep (it is 3 am here).
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
Thanks for the help. I'll look into it tomorrow as I need to sleep as well. I've been thinking of trying Magdlr again since you're familiar with it. I know how to flash ROMs on Android devices (CWM) so yes, once I get any rom flashed, the rest should be fairly straightforward. It's just not going to that critical step...
I can really recommend you to try flashing the ROM through MAGLDR instead. I have CLK issues myself, repartitioning CLK on my HD2 also leads to hanging phone. Try repartition MAGLDR instead and then flash the ROM by using AD Recovery from MAGLDR menu.
Also, repartitioning with too large system size gives hanging problems on my phone. I think due to bad memory blocks and lack of space for the rest of the programs. Try different partitioning sizes.
Try THIS rom, it is in my opinion the most stable: http://forum.xda-developers.com/showthread.php?t=1434860
Go for DataOnExt. The rom then needs 175MB, so go for 180MB system partition size when repartitioning MAGLDR.
Please create a FAT32 primary partition with 32KB cluster size, then an EXT4 primary partition with default cluster size on your SD card.
The EXT4 should be about 1GB - 2GB.
So:
1) Task29 (from phone bootmenu)
2) Install Magldr (from phone bootmenu)
3) Repartition Magldr 180 MB (from MAGLDR USB Flasher)
4) Format SD card with 2 partitions (MiniTool Partition Wizard Home Edition)
5) Place the ROM ZIP on the FAT32 partition
6) Insert SD card in phone
7) install ZIP from SD card (from MAGLDR AD Recovery)
8) Choose ROM ZIP
9) choose DataOnExt (in Aroma installer)
10) Choose Davik Cache Wipe (in Aroma installer)
11) Reboot when done
12) Have fun with Android
make sure the HD2 is not fake, there was one here before & he showed a photo of it & it really looked like the real thing, also use the HD2 Toolkit to make it easier for you.
& since it's a T-mobile there are certain Radios that can brick that model if it is such (1g version) so better do a little more reading & there are lot of reference here in XDA.
Thanks for the help. I will try it when I get home later and report back.
I think I've bricked the phone...I tried flashing Magdlr again but got only the header when it booted. So I task29'd it again and attempted reflashing. It got stuck at 96% for a super long time so I did a battery pull. Then I tried booting it into recovery and it does nothing but vibrate...recovery, hard reset, nothing works...looks like the end of the road for this phone.
wcstick said:
I think I've bricked the phone...I tried flashing Magdlr again but got only the header when it booted. So I task29'd it again and attempted reflashing. It got stuck at 96% for a super long time so I did a battery pull. Then I tried booting it into recovery and it does nothing but vibrate...recovery, hard reset, nothing works...looks like the end of the road for this phone.
Click to expand...
Click to collapse
If you truly bricked it the phone would not do anything - would not go to 96% or anything.
If Magldr did not finish you certainly would not have a recovery installed yet.
Task29 is over-rated and, in most cases, simply unnecessary. You are wearing out your NAND memory if you keep doing it.
OK, so having said all that.. Did you try a different USB cable, a different USB port, re-installing the Windows side of the software (ActiveSync?)
Look for MSKIP's guide to flashing the HD2 - it should get you past the MAGLDR install.
Er, I meant to say I think I've bricked it after I tried reflashing Magdlr. It does nothing but vibrate when I attempt to turn it on now.
wcstick said:
Er, I meant to say I think I've bricked it after I tried reflashing Magdlr. It does nothing but vibrate when I attempt to turn it on now.
Click to expand...
Click to collapse
You cannot even get to the tri-color bootloader??
You didn't overwrite HSPL somehow, did you?
Before you try anything else make sure your battery has a decent charge (at least 50%).
The last thing you want is to die in the middle of these steps.
If HSPL is (or should be) OK, disconnect the device from any external power source. Remove the battery and place it back after a short while. Remove the HD2's back cover and press (and hold) the volume_down key. Press in the red reset button under the back cover to the bottom left of the SIM (you will need a sharp object for this) and release the soft reset button but continue to hold the volume down key in until you are presented with the tri colour bootloader screen.
If you get to the boot loader, make sure you have HSPL in tact. You can use this mode, with the tri-color screen, to flash Magldr later.
If you made it this far try the following steps.
Make sure you are using the correct radio - this can create serious problems! YOU NEED A RADIO WHICH SUPPORTS 576 RAM (2.08.50 or later should be fine but the Radio NEEDS to be 2.**.50.**). I recommend the 2.15.50.14 radio
The Original MAGLDR thread by Cotulla is here if you need it. MAGLDR doesn't replace OSPL/HSPL. It runs in the chain after. So it's safe to install and remove it Once you are in the tri-color bootloader mode:
Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable. As an alternative method to activesync you can restart your phone in Bootloader Mode, then connect the usb cable and wait until 'usb' appears in the bottom half of your phones screen
Browse to the folder you extracted your Magldr Package files to on your pc, right click on ROMUpdateUtility.exe and select Run as Administrator (Win7 or later)
Tick the box to confirm you are aware of the risks and select 'Next'
Tick the box to confirm you have followed the preperation steps and select 'Next'. The program will check the usb connection.
Select 'Update'
Verify the image you will flash (it should say 2.00.000.0) and Select 'Next'
Read the process list and Select 'Next'
Your phone will enter BootLoader Mode and the progress will (hopefully) goto 100%
Your phone will Reboot. You should now have MGLDR installed.
To Enter MAGLDR Menu Screen after installation, Long Hold the Power Button when resetting the phone and the menu will appear
If you make it this far I suggest you now run DAF.EX to repartition and update your recovery software. We can talk about this step next - let's ee if you can make it this far!
Frustrated with the whole process...What process?
I have spent WAY too many hours this weekend reading through threads here and elsewhere, with the goal of converting my T-Mobile WMo HD2 to Ice Cream Sandwich.
I have seen three for four different message thread that seem to contradict each other on what the process is.
Here is what I have done.
Changed to 2.08.HSPL. It was 2.10.000 .
Flased MAGLDR and it is working.
So I currently have a useless phone, although not bricked.
I had to use an old WinXP Laptop, since my Win8-64 Laptop would not see the phone.
Downloaded a ROM, NexusHD2-ICS-CM9-HWA_v2.9a .
Apparently there should be an Installer or a Daf included, but there is not.
I tried running Daf from the directory on the PC where the MAGLDR installer and other utilities are, like others have. Now I know that that will not work.
The current NAND Toolkit will not work on 32 bit windows. This is according to bzdemes here http://forum.xda-developers.com/showpost.php?p=19931919&postcount=501 . It certainly does not work on my Windows XP, "hd2toolkit.exe is not a valid win32 application" .
If my Windows 8 Laptop would see the phone, then I suppose that I could try it there, but once again, that does not work. I do not have access to any more Windows 7 PCs.
I have since seen messages indicating that I should have done Task29 before flashing MAGLDR. I have seen other messages indicating that it is not necessary. Of course, no usable toolkit, so here we go back into the loop of failure again...
I have wasted an entire weekend on this and have nothing to show for it, other than a non-usable phone.
I know that you guys put a lot of effort into playing with this stuff, but I really hope that someone here can provide a clear concise process for those of us who do not have play time.
FWIW, I am a noob at converting phones to Android, but I am very technical otherwise, with nearly thirty years in IT and Telcom / Data. Clearly this is not rocket science, but for those of us who do not have this specific experience, and generally have all of our time consumed by our non-Android jobs, this is a challenge.
Thanks
Dean
warpedspeed said:
Here is what I have done.
Changed to 2.08.HSPL. It was 2.10.000 .
Flased MAGLDR and it is working.
Click to expand...
Click to collapse
Excellent start! Before long you shall be looking back at this, smiling.
The next question you have to answer is if you wish to install all to NAND or place your apps and data on an SD Card. If you have an EU HD2 the SD card method is strongly recommended. I have the larger (1 GB) US version but prefer to use the SD Card method for a number of reasons (we can cover those another time if you wish).
warpedspeed said:
I had to use an old WinXP Laptop, since my Win8-64 Laptop would not see the phone. Downloaded a ROM, NexusHD2-ICS-CM9-HWA_v2.9a .
The current NAND Toolkit will not work on 32 bit windows. This is according to bzdemes here http://forum.xda-developers.com/showpost.php?p=19931919&postcount=501 . It certainly does not work on my Windows XP, "hd2toolkit.exe is not a valid win32 application" .
Click to expand...
Click to collapse
I have not used the Toolkit myself but one would think it would run OK on XP..
Having said that, try this - should be relatively quick and painless (I hope):
Download dafexe_399.zip - 5.17 MB to your PC and unzip it into an empty folder of your choice.
If you wish to use install option #2 (DataOnExt, placing only your boot, recovery and system partition on the device itself (NAND) use the setup as is. See notes on partitioning your SD Card before attempting to install the ROM! If you wish to install everything to NAND you must modify the file called FLASH.CFG which you shall find in the folder you extracted the zip file to - reduce the size of the system partition (the fourth line in the cfg file) to something like:
Code:
system ya 200M
I suggest setting it to 200M (200 MB) to start but you may have to redo this and make it larger if your device has bad blocks. A large system partition will, in turn, make for a smaller data partition - as a result you may be limited on the number of apps and data you can have on the device. This is why I personally prefer install option 2, placing the data partition on an SD card.
Once ready, boot your device to MAGLDR
Select USB Flasher from the MAGLDR menu (you can replace steps 3 & 4 with entering the tri color boot loader, if you wish)
Connect your device to the PC via USB
Make sure you are in the folder you created in step 1 and run DAF.EXE on your PC. This will partition your device according to the specifications in FLASH.CFG and also install ClockworkMod Recovery v5.x into the recovery partition.
If you decided on install option 2 - DataOnEXT - make sure your SD card is correctly partitioned before going on from here! You must have a FAT32 partition and an EXT4 partition (in that order), both set as PRIMARY. The EXT4 partition should be at least 1 GB, you can make it bigger if you have a larger card. If you need more info on partitioning and setting up the card please read post # 3 in this thread.
Copy the ROM of your choice to the FAT32 partition of your SD card.
Reboot your device while holding the END key to enter the MAGLDR menu.
Select menu option # 8 - AD Recovery. This will load Clockworkmod Recovery you flashed in step 6.
Select install from ZIP menu option and locate the ROM zip file you placed on the SD card earlier.
After the device reboots you should be running the new ROM. Now, you may still experience some problems - such as bootloops or getting stuck at the logo screen if you made the system partition too small for your device or if you have too many bad blocks on your device and you selected install option # 1. In this case you will have to return to step 2 and increase the system partition size and do it all again.
Does any of this help thus far?
Yesterday I had a chance at work to try another Windows XP PC that is pretty much just used for testing. It has a fairly fresh image on it. I had the same Win32 error on it with the NAND toolkit.
I also was able to get my hands on a Win7 32 bit PC, with the same result.
Then I was able to “commandeer” a PC that was going to be re-imaged anyway. I put a Win 7 64 image on it, and sure enough the toolkit worked.
So it appears that the NAND Toolkit works on Win 7 64, and possibly Win 8 64, but support for 32 bit Windows appears is over, unless the program gets fixed.
The problems that I was having with synching the phone on my Win 8 64 PC may have been due to using a USB3 port. Last night I was able to see the phone on that PC with a USB2 port. I should have tried that this last weekend.
So I ended up using the Toolkit yesterday, before I saw your reply. I did look through the partitioning guide that you referenced. I opted not to go with the Data on EXT option. It is a 1Gb T-Mobile HD2, so I am in good shape there. I did not want the operation of the phone to be dependent on a relatively slow SD card. I will just keep optional data there, such as music, pictures, and documents. I will keep anything important, such as programs and notes that I use for reference in the main memory. I do not have all that many extra programs or data.
So I am up with the ICS-CM9-HWA_v2.9a build and it is pretty good. So far I like it. Previously I was doing a dual boot, using Haret and a Gingerbread build, basically as a test, and while I was waiting for some Android apps to mature, that initially were not a good replacement for some specialized WinMo apps that I had. I finally have all of the functionality that I need on the Android platform.
For me, the biggest challenge in this was the variety of documented procedures that are out of synch, and mostly out of date. For instance Mr Skip’s guide is well written, but out of date to the point that it sent me down the wrong road. I am not picking on Mr Skip, in fact his guide was the best written of the bunch, so that is why I mention it.
If I am the last guy on this particular planet to make the switch on an HD2, then it is probably is not worth updating the docs out there. However there might still be a few holdouts in the wings yet.
If I can get my wife to stop using my T-mobile upgrade credits, then maybe I can get a newer hardware platform someday! Although I am very impressed with the longevity and durability of the HD2. That is a rare thing anymore.
Thanks for the help.
Glad you got it to work. I only have a couple of brief comments to add.
warpedspeed said:
I opted not to go with the Data on EXT option. It is a 1Gb T-Mobile HD2, so I am in good shape there. I did not want the operation of the phone to be dependent on a relatively slow SD card.
Click to expand...
Click to collapse
Going with option 1 is fine. You may or may not encounter limitations and you can always change later if need be. However, it should be noted that the HD2 NAND operates at roughly the same speed as a Class 4 card, hence you could not slow it much by using a card.
warpedspeed said:
For me, the biggest challenge in this was the variety of documented procedures that are out of synch, and mostly out of date. For instance Mr Skip’s guide is well written, but out of date to the point that it sent me down the wrong road. I am not picking on Mr Skip, in fact his guide was the best written of the bunch, so that is why I mention it.
Click to expand...
Click to collapse
Mark's guides are indeed excellent and as you noted, somewhat dated since they were written early in the HD2 / Android days. A number of things have changed and I think Mark has moved on to Samsung or Nexus devices since that time. For good or evil his guides survived the test of time.
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
I have quite an old laptop and decided to give Phoenix OS a try, loved it that much that I decided to try and install it as a standalone OS, so I download the 64bit ISO image and used rufus to install it onto a 16gb USB stick, I also got hold of parted magic, so the steps I took was to reboot into parted magic and remove all my partitions, then create a new ext4 partition across the whole drive, which in this case is an SSD 120gb, after parted magic had finished I proceeded to install phoenix OS, booted off the USB stick and selected the option to install to the hard drive, It then proceeds to ask me a few questions, do I want to install grub2 efi, I say yes and point to dev/sda1, and do I want to install boot partition, I say yes to this too, it then installs, but just wont boot, every time I restart it says there is no boot device found, or I just get a flashing cursor at a black screen like its waiting for something, what am I doing wrong ?
I have tried with the file system as FAT32, ntfs, and ext4, and also tried with uefi bios and legacy bios, always the same result.
Any help much appreciated, thanks.
Reply to my own thread, finally figured out how to do it, its pretty much only took me all day, but running as a single OS now with no Windows in sight, on a samsung evo 840 120gb SSD, running like lightning.
Seanie280672 said:
Reply to my own thread, finally figured out how to do it, its pretty much only took me all day, but running as a single OS now with no Windows in sight, on a samsung evo 840 120gb SSD, running like lightning.
Click to expand...
Click to collapse
it would be just too cool if you told us how you did it or what went wrong before you succeeded ?
HausiX10 said:
it would be just too cool if you told us how you did it or what went wrong before you succeeded ?
Click to expand...
Click to collapse
Download the latest Phoenix ISO and create a bootable USB stick with it using rufus, format to FAT32, and partition scheme is MBR for UEFI and legancy bios, tick quick format, tick create a bootable disk using.........and browse to the Phoenix ISO, and tick create extended labels and icon files, my bios is also set to legacy bios, not tried as uefi, may give it a try next weekend if I can be bothered, like I said although my laptop is a 64bit machine, its quite old, so im using the 32bit OS, may try again with the 64bit OS and uefi mode, not that it makes any difference to this OS.
Now get yourself a copy of parted magic and create a bootable USB stick or CD with it, now boot to it, remove all the partitions off your drive, so you now have one complete unpartitioned space, now you need to create 2 partitions, 1 at 350mb (sda1) format to FAT32 then when done, right click it, select manage flags and mark as boot, now format the rest of the drive as EXT4 (sda2).
Now reboot and boot off the other USB stick containing Phoenix, select installation to hard drive, when asked where you want to install it to, select sda2, then you'll be asked if you want to install grub2, say yes, and it will ask you to select a location for it, select sda1, also say yes to installing the bootloader, DO NOT format any of the partitions, let it do its thing, at the end it will ask, start phoenix or reboot, I selected start phoenix, once the screen went black I removed the USB stick and phoenix started up, starts up fine everytime now.
That grub2 was the issue, needs to be on its own partition.
Hi Seanie280672
thanks for the detailed answer. Going to try soon on an old Vostro...
Hans
HausiX10 said:
Hi Seanie280672
thanks for the detailed answer. Going to try soon on an old Vostro...
Hans
Click to expand...
Click to collapse
Ive created a video here: https://youtu.be/c68qgPepjFI
Seanie280672 said:
Now reboot and boot off the other USB stick containing Phoenix, select installation to hard drive, when asked where you want to install it to, select sda2, then you'll be asked if you want to install grub2, say yes, and it will ask you to select a location for it, select sda1, also say yes to installing the bootloader, DO NOT format any of the partitions, let it do its thing, at the end it will ask, start phoenix or reboot, I selected start phoenix, once the screen went black I removed the USB stick and phoenix started up, starts up fine everytime now.
That grub2 was the issue, needs to be on its own partition.
Click to expand...
Click to collapse
ok so mine when i boot off the bootable usb stick of phoenix os to install the standalone os that i had created using rufus 2.17 it comes to the GNU Grub version 2.02~Beta2 command any ideas on what im doing wrong?
Quittakingmyname said:
ok so mine when i boot off the bootable usb stick of phoenix os to install the standalone os that i had created using rufus 2.17 it comes to the GNU Grub version 2.02~Beta2 command any ideas on what im doing wrong?
Click to expand...
Click to collapse
Make sure you used the correct settings in Rufus to create the bootable stick
Seanie280672 said:
Make sure you used the correct settings in Rufus to create the bootable stick
Click to expand...
Click to collapse
yes the setting are correct ive used it to do the remix os the same way but phoenix os will not boot up it just goes to the GNU Grub menu
And I also used gparted to do my partitions the way I needed to as well and it will not go past the GNU Grub menu
Try 32bit
My os is 64, but phoenixOS auto-downloader said I needed the 32 bit. Try that.
Does this work with hp notebooks?
Seanie280672 said:
Download the latest Phoenix ISO and create a bootable USB stick with it using rufus, format to FAT32, and partition scheme is MBR for UEFI and legancy bios, tick quick format, tick create a bootable disk using.........and browse to the Phoenix ISO, and tick create extended labels and icon files, my bios is also set to legacy bios, not tried as uefi, may give it a try next weekend if I can be bothered, like I said although my laptop is a 64bit machine, its quite old, so im using the 32bit OS, may try again with the 64bit OS and uefi mode, not that it makes any difference to this OS.
Now get yourself a copy of parted magic and create a bootable USB stick or CD with it, now boot to it, remove all the partitions off your drive, so you now have one complete unpartitioned space, now you need to create 2 partitions, 1 at 350mb (sda1) format to FAT32 then when done, right click it, select manage flags and mark as boot, now format the rest of the drive as EXT4 (sda2).
Now reboot and boot off the other USB stick containing Phoenix, select installation to hard drive, when asked where you want to install it to, select sda2, then you'll be asked if you want to install grub2, say yes, and it will ask you to select a location for it, select sda1, also say yes to installing the bootloader, DO NOT format any of the partitions, let it do its thing, at the end it will ask, start phoenix or reboot, I selected start phoenix, once the screen went black I removed the USB stick and phoenix started up, starts up fine everytime now.
That grub2 was the issue, needs to be on its own partition.
Click to expand...
Click to collapse
Thank you for the guide, would it still work if sda1 was ntfs? I can't get gparted or parted magic to work so I must create partitions from within the OS installer itself...
addminusevei said:
Does this work with hp notebooks?
Click to expand...
Click to collapse
Yes it works great for dual boot on hp
Phoenix stuck at initial boot
I installed on hard-disk partition with 75gb space
Followed the exact procedure from the official Phoenix OS website
But when I restart the laptop
The Boot gets stuck at "System Initialising, please wait...."
Can anyone pls help me?
Hello, i burned the iso exactly like your post, but when i boot my ASUS T100TAF with the USB it goes to the grub> prompt
what Am i doing wrong?
need help about phoenix
Seanie280672 said:
I have quite an old laptop and decided to give Phoenix OS a try, loved it that much that I decided to try and install it as a standalone OS, so I download the 64bit ISO image and used rufus to install it onto a 16gb USB stick, I also got hold of parted magic, so the steps I took was to reboot into parted magic and remove all my partitions, then create a new ext4 partition across the whole drive, which in this case is an SSD 120gb, after parted magic had finished I proceeded to install phoenix OS, booted off the USB stick and selected the option to install to the hard drive, It then proceeds to ask me a few questions, do I want to install grub2 efi, I say yes and point to dev/sda1, and do I want to install boot partition, I say yes to this too, it then installs, but just wont boot, every time I restart it says there is no boot device found, or I just get a flashing cursor at a black screen like its waiting for something, what am I doing wrong ?
I have tried with the file system as FAT32, ntfs, and ext4, and also tried with uefi bios and legacy bios, always the same result.
Any help much appreciated, thanks.
Click to expand...
Click to collapse
i have just installed phonenix i mean i tried flashing a bootable cd to a sda4 partition on my arch linux system . later i found it hard to edit the exsisting grub so i have followed the mounting the iso and creating a folder on the /mnt dir and adding the path to the /etc/grub.d/40_custom , and it worked .. phoenix works well but everytime i shutdown my pc and boot up agian , the phoenix os asks for username and wifi . the storage too seems small regaurding i have installed on a 80 gigs arch linux system still the phoenix uses only 8gigs .can you help me with this?
I suppose, POS can install only to an UEFI laptop the standard way. I installed Phoenix OS 3.0.2... the old way, https://forum.xda-developers.com/ph...tall-phoenix-os-3-0-2-ext4-partition-t3821121 in an old laptop. I don't use Android for day to day work, just to experiment. I didn't open it for sometime, and when I did today (few mins ago.) it got updated to 3.0.3.64. POS notified there is a new version, I agreed, so it downloaded it and installed it.
BTW, Phoenix boots through Ubuntu's grub.
EDIT: I read the whole thread just now. You've succeeded, that's good.
Hi. I also have problem with installation. I want to build a small android video game console. I use mini itx asus mainboard AT5IONT-I with 2core intel atom, nvidia ion gpu and kingston ssd. Installation goes like on Seanie280672 video, but after clicking " run phoenix os" my computer restarts, boots from ssd and I it shows black screen with _
What is the problem and is there any way to fix it?
CPU stopped N no Base cpu clock
Why, when i installing Phoenix Os. And i oppened a CPU Z. My Cpu core 0 and 1 has stopped n cpu clock n/a. And in launcher and cursors so laggy. Can you gime me the solution. Thanks