Related
THIS BUILD IS OUTDATED, CHECK:
http://forum.xda-developers.com/showthread.php?t=1177721
I'd like to "present" my recompilation of XDAndroid FRX06 to work with Neopeek's CWM 1.8
No credit for me, but for all XDAndroid devs and Neopeek &co for this.
It doesn't have any other modifications apart from making it available to install from CWM, so everything that applies to FRX06 is useful here. You're the one to decide if you prefer looped or partitioned installs.
Don't try this if you don't know what you're doing. It's only tested by me, so what I'm looking for are TESTERS. PLEASE READ EVERYTHING CAREFULLY BEFORE DOING ANYTHING.
Normally it would be easy to return to previous state by repartitioning/formatting SD, but who knows. I take no responsability for any damage to your device.
The instructions for installing CWM are in Neopeek's forum. Only points:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
2.- Startup.txt, ts-calibration, kernel and modules must be in the same dir as haret.exe, in this case inside "npkboot" dir.
3.-To move in the CWM menu with our Blackys:
Peteflyman said:
I just toggle between "Reboot system now", push "Vol Up" to get directly to "Power off", and then toggle "Vol Down" to get back to "Reboot system now". I just do that a couple of times then "Back menu button enabled" usually shows up. That's it. Hope it works for you guys as well!
Click to expand...
Click to collapse
After the "back menu button enabled" you can use power off button to confirm menu selection. Just select "install zip from sdcard", "choose zip from sdcard" and choose my zip (ofc, don't uncompress it).
4.- You don't need to install Gapps, they're included in the build.
5.- After installed, "reboot system now" and start haret again. Let it work for a while without touching anything until you see PIN or unlock screen to begin using Android.
6.- I'd recommend rebooting a second time before starting to configure everything...
It should work in any device where CWM and XDAndroid work, but the configurations I attach here are for TOUCH HD (Blackstone). If you want to try with other devices, be careful to use the appropiate config files (they shouldn't be difficult to find in your device's forum).
I'm using 1337 kernel & modules from Glemsom's autobuild and it works perfectly with my device, feel free to use the one that suits you better.
Download link:
http://www.megaupload.com/?d=SUBUG5I8
If you have any problem, I'll try to help, but for CWM problems please ask in their forum as you'll find better assistance.
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
if you want to install any other build,or reinstall frx06,go to recovery,choose mounts and storage,then format data,format cache,format system (don't format sdcard for obvious reasons) and then mount data,cache,system,go back and install zip from sd card,choose your zip.
also if you find a build without gapps,go to cyanogenmod.com and grab it there,you should pich gapps for cyanogenmod 6 because that's the froyo build....MDPI or HDPI doesn't matter in our case
many problems are result of gapps missing (some builds come without them,this one doesn't) such as call rejecting or showing black screen instead of lockscreen when you wake the device,so be sure to install them
arrrghhh said:
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
Click to expand...
Click to collapse
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Eodun said:
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Click to expand...
Click to collapse
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
farukb said:
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
Click to expand...
Click to collapse
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Eodun said:
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Click to expand...
Click to collapse
you can at least start with
/system
/app (add or remove apps)
/fonts (obvious)
/framework (the "look" of the build is defined here,so if you want your froyo to look like ginger,take some of the ginger files and swap with those in this one)
/media (it'll tell you what to do by itself)
other folders are build regarded and some playing and asking pros is advised here
any screenshots ?
Simon_WM said:
any screenshots ?
Click to expand...
Click to collapse
It's a vanilla Froyo, identical to FRX06, so I didn't think they were needed. Just look at any basic original Froyo install.
Eodun said:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
Click to expand...
Click to collapse
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
every card is "original" just the manufacturer is different....eg trandescent cards dont work,what's your card?
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Eodun said:
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Click to expand...
Click to collapse
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
arrrghhh said:
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
Click to expand...
Click to collapse
Well, I can't tell because I'm in android now and can't extract it XD Never had the curiosity to check.
Let me see... Yeah, it has a "2" inside sort of a "C", so it must be a C2 8Gb SanDisk MicroSDHC lol
Working on FRX07 update.zip to test if it works with CWM
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
ypsmav said:
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
Click to expand...
Click to collapse
helicopter88 is already working on that
ypsmav said:
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
Click to expand...
Click to collapse
I don't think so. But if you backup everything with titanium backup and then restore apps, appdata and system settings (only those that appear in green) you'll have everything as before.
Eodun said:
Working on FRX07 update.zip to test if it works with CWM
Click to expand...
Click to collapse
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
arrrghhh said:
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
Click to expand...
Click to collapse
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
ypsmav said:
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
Click to expand...
Click to collapse
@arrrghhh: Yeah, I know the update is available, but ypsmav noticed the problem: I need the new rootfs for CWM, and I'm not able to adapt it. As I said, work is being done for that.
Thanks for your replies
Ps It will be a big problem if latest kernel doesn't boot. I haven't been able to boot with it. Edit: But still have to check if it boots with a clean data.
hi,
i have just tried to install LeeDroid 3.0.8.2 and am panicked that i've bricked my phone.
I partitioned the sdcard using Rom Manager - also downloaded and flashed the rom via rom manager.
It seemed to do its thing fine and the leedroid screen loaded up, but now it just keeps looping back on itself showing me that its installing making this funny beeping sound and then goes back to the leedroid screen for maybe 15 seconds and repeats.
Anyone know ever have this experience? can any one help?
thanks
Please make a search...
The best way to avoid bootloop is first to partition the SDcard with Gparted...
Then you need to check a few things (your hboot version among others)
good reading !!!
If it's looping at that point it is almost certainly a problem with the SD-card ext3 partition. Rom Manager is not terribly reliable with making that.
The Gparted suggestion is by far the best solution (assuming you have a PC with a card reader, rather than trying to do it with card mounted in phone)
If you *do* have a reader then try LiveCD with gparted, burn to CD and boot from that.
Make your first partition FAT32, and your ext3 partition at the end of the card. (1GB recommended). Make sure both partition are marked as "primary".
Sorry for jumping in here, but I also need help with this rom (sorry uber noob and all). Figured since the thread was so fresh may as well ask here.
Basically trying to install leedroid v3.0.8.2 (data ++) for my original htc desire.
Cant download from either of the links, they both lead to url 404s.
And i also tried downloading from both rom manager and also the minisite, these downloaded but seem to be corrupt. I cant open the zip file and trying to flash it returns a cant flash (bad) message.
Anybody know where i can get a working zip of this version?
cathalfm said:
Sorry for jumping in here, but I also need help with this rom (sorry uber noob and all). Figured since the thread was so fresh may as well ask here.
Basically trying to install leedroid v3.0.8.2 (data ++) for my original htc desire.
Cant download from either of the links, they both lead to url 404s.
And i also tried downloading from both rom manager and also the minisite, these downloaded but seem to be corrupt. I cant open the zip file and trying to flash it returns a cant flash (bad) message.
Anybody know where i can get a working zip of this version?
Click to expand...
Click to collapse
Have you tried here and choose the ROM you want from the white scrolling list? The 3.0.8.3 data version downloads for me.
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
lovingboth said:
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
Click to expand...
Click to collapse
Repartition your sd-card by using the partitioning guide in my sig.
onknope what
abaaaabbbb63 said:
Repartition your sd-card by using the partitioning guide in my sig.
Click to expand...
Click to collapse
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
lovingboth said:
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
Click to expand...
Click to collapse
Theres no need for a swap partition. If you are using PA it will just act as a waste of space, since the rom doesnt utilize it in any way.
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
chromium96 said:
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
Click to expand...
Click to collapse
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
lovingboth said:
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
Click to expand...
Click to collapse
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
chromium96 said:
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
Click to expand...
Click to collapse
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
lovingboth said:
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
Click to expand...
Click to collapse
Go to system/app. Are the google apps installed? What permissions do they have?
abaaaabbbb63 said:
Go to system/app. Are the google apps installed? What permissions do they have?
Click to expand...
Click to collapse
Ah, no they're not.
About sixty are, owned by root, with rw (owner) and r (group and global) permissions.
I am being tempted to bite the bullet, install the ADK on something and try the adb method.
What about /sd-ext/gapps/system/app. Anything there?
chromium96 said:
What about /sd-ext/gapps/system/app. Anything there?
Click to expand...
Click to collapse
Yep, they are there, with what I presume are the right permissions: as above, owned by root, rw-r-r.
Doing some more nosing around, and looking at the alternative installation instructions on woh-roms.weebly.com/gapps.html
$ adb shell ls /sd-ext/gapps/system
app etc framework lib usr
Click to expand...
Click to collapse
Yes, doing
ls /sd-ext/gapps/system
produces that.
# enable extgapps (quotes needed)
$ adb shell "echo x > /sd-ext/gapps/.extgapps"
# gapps dir should look like this (if .extgapps doesnt exist the init script wont run)
$ adb shell ls -a /sd-ext/gapps/
.extgapps system
Click to expand...
Click to collapse
Yes, doing
ls -a /sd-ext/gapps/
produces that.
.extgapps is a zero byte file, rather than one byte containing 'x' as there, but the root explorer instructions would produce a zero byte file, so presumably a) there's no touch command and b) it's the presence of the file that's important, not what it contains.
BUT...
... if I do
logcat -C
(after doing logcat -c, going oops, rebooting, and getting it right )
then the lines that are supposed to be there aren't.
I'll get the email working, email the output to myself and stick it in a pastebin or similar.
pastebin.com/Qtrps3A8 has the whole thing.
At the start, various links are possibly not set up:
I/run-parts( 75): ln: /system/etc/permissions/com.google.android.maps.xml: Out of memory
I/extgapps( 155): Created /system/etc/permissions/com.google.android.maps.xml
Click to expand...
Click to collapse
is just one example, then later
D/AlarmScheduler( 1300): No events found starting within 1 week.
I/Goo Parser( 839): GAPPS: No file, skipping item 0
I/Goo Parser( 839): GAPPS URL: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130702-signed.zip
I/AlarmReceiver( 839): gooVer: 3601
Click to expand...
Click to collapse
.. so what file is it looking for, and is this down to trying to do things with the card before it is ready?
What has changed:
The search 'app' has gone from the list - I can see from the logs that it is supposed to be replaced, but here it's just missing.
The browser is now very like Chrome... and I don't remember that being the case.
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?
xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!
dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!
dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.