Database Users

[Q] Boot Problems with rooted P6810

Anyone having problems booting a P6810?
I got my (HK wifi version) a couple of days ago and it gets stuck on the "Samsung" logo on boot up... I have had to do a factory reset 4 times already to get it to boot...
I've rooted it (as per the forum instructions) and have installed a number of apps & am currently trying to work out what the problem is...
The possible causes that I can think of are:
1) A rooting problem? I updated the su binary. And I can't see a similar problem in the forums, so I don't think that this is it
2) The app "Quick Boot" - I used this on my old Tab 7 without problems, but maybe 7.7 doesn't like it?
3) Titanium back-up - I installed a number of apps I used with my old Tab 7 ('app only', without data). I thought this might be the problem, but I had the same boot issues when I tried not using titanium backup.
4) Using a micro sd card that I used with Tab 7 as is (i.e. no formatting)
5) The app ' start-up manager' - although the boot problem exists whether it's there or not
I realize that #3 & #4 might be classic noob errors...
This morning I've flashed the stock firmware using ODIN, re-rooted and installed my apps from market (not titanium backup). I'll give an update later on today / tomorrow to see if that did the trick.
But I'd be grateful if anyone who has had similar issues could let me know how they've solved them, or what they think the problem could be.
Thanks

If it were mine -
I would return it to stock condition, not root it, not install applications.
Use it absolutely stock for a week and see if the boot problem shows up. Send it back for exchange if it looks like a hardware problem.
After I knew the hardware was good, I would install known good applications from market. Again, verify no boot problems.
After that, I would know that the boot problem is due to something risky I installed. I would leave Quick Boot to last, since it was not written for the 7.7 and is most suspect.

Good advice, In addition I can confirm I had no problem with the simple original root from the root guide thread.
However, the partitions on P6810 look like this:
Number Start (sector) End (sector) Size Code Name
1 8192 49151 20.0 MiB 0700 EFS
2 49152 51711 1.2 MiB 0700 SBL1
3 53248 55807 1.2 MiB 0700 SBL2
4 57344 73727 8.0 MiB 0700 PARAM
5 73728 90111 8.0 MiB 0700 KERNEL
6 90112 106495 8.0 MiB 0700 RECOVERY
7 106496 516095 200.0 MiB 0700 CACHE
8 516096 2220031 832.0 MiB 0700 FACTORYFS
9 2220032 29835263 13.2 GiB 0700 DATAFS
10 29835264 30752767 448.0 MiB 0700 HIDDEN
11 30752768 30769151 8.0 MiB 0700 FOTA
Which from other posts I understand to be different from many other tabs including any 3G tabs as they have an extra partition (after 7 for the p6800 I think).
So any tool/utility that has a fixed operation on particular partition numbers from
another tab has a very high chance of failure.
Check how the above compares with your old 7 before using anything with boot in its name.
Edit: also, titanium hung when doing a restore of a system app for me, and the app could not be restored using it. I have
not tried to restore any apps on this device with it subsequently because of this.

Many thanks @davp / @rmm200
Not sure what I did the first time round, but after the clean install, I've been OK. No booting problems.
Thanks for taking the time to reply. I think the partition issue might have been a problem as I was coming from a 3G Tab.
Cheers

[SOLVED] [Q] [HELP] Messed up u8800 partitions

I messed up u8800 internal partitions. Tried to restore the official b526, b518, b137 with no luck. I think I need to repartition the whole internal memory (emmc) and put the right images to those partitions. The problem is I don’t know how and I don’t have the images. FYI, I have access to the pink screen.
Please help me...
Thank in advance!
__________________________________________
UPDATE WITH SOLUTION:
Disclaimer:
If you follow these procedures, you do so at your own risk. A typo in the needed commands may render your phone useless.
Requirements:
u8800 with accessible pink screen
linux box
Download HUAWEI_U8800_FullFlash.rar and extract it
Steps:
Pull out the battery and sdcard from your phone.
Connect your phone using USB cable to your computer while pressing the vol up and vol down to get to the Pink Screen.
Unmount any newly mounted disks/partitions of your phone.
Do in Terminal
Code:
sudo dd if=/path/to/HUAWEI_U8800_FullFlash.bin of=/dev/device_name
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.
Code:
Example (my case):
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
Wait for it... It took me 1,5 hours!
Code:
Output (my case):
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
7733248+0 records in
7733248+0 records out
3959422976 bytes (4.0 GB) copied, 5402.43 s, 733 kB/s
[email protected] ~ $
After the "long" process completed, disconnect your phone from your computer.
Reboot your phone and enjoy official 2.2 on your phone.
Thanks to Blefish, bonowax for his tutorial, and medusa!
Hope it can help others.

What did you do exactly? Maybe we can revert the process and fix it without wiping the device.

Blefish said:
What did you do exactly? Maybe we can revert the process and fix it without wiping the device.
Click to expand...
Click to collapse
I changed the system, data, and internal_sdcard with Minitool Partition Wizard to make the system partition 512mb just like my gnex.
Do you think the method mentioned in the thread [TUT] Full U8800 backup with Linux howto can solve this? Do you have a “clean” u8800.img? I can restore my IMEI with 5irom toolbox.
Edit:
Blefish said:
Yes, this backup has full Android dump, with modem partitions (IMEI and such), also the bootloader and splash screen images.
As long as you have pink screen access, you can restore the backup and your phone will be just like it used to be before.
Click to expand...
Click to collapse

buzzcomp said:
I changed the system, data, and internal_sdcard with Minitool Partition Wizard to make the system partition 512mb just like my gnex.
Click to expand...
Click to collapse
And now Android does not boot?
buzzcomp said:
Do you think the method mentioned in the thread [TUT] Full U8800 backup with Linux howto can solve this? Do you have a “clean” u8800.img?
Click to expand...
Click to collapse
Yes, the method described there would work. The problem is, I don't have my device to do it and upload it. I will do it with a proper tutorial when I get my device back, but for now you should prepare a Linux environment (Ubuntu for ex.), either install it or do a live CD/USB stick. We can recreate the last 3 partitions, I have the default sizes with block numbers for start/end. I will post the full tutorial tomorrow, I have to recheck the commands.

Blefish said:
And now Android does not boot?
Click to expand...
Click to collapse
Yes, it doesn't boot. No huawei logo whatsoever, only like the attached image.
Blefish said:
Yes, the method described there would work. The problem is, I don't have my device to do it and upload it. I will do it with a proper tutorial when I get my device back, but for now you should prepare a Linux environment (Ubuntu for ex.), either install it or do a live CD/USB stick. We can recreate the last 3 partitions, I have the default sizes with block numbers for start/end. I will post the full tutorial tomorrow, I have to recheck the commands.
Click to expand...
Click to collapse
I have live Linux Mint.

buzzcomp said:
Yes, it doesn't boot. No huawei logo whatsoever, only like the attached image.
I have live Linux Mint.
Click to expand...
Click to collapse
I believe the full wipe is the only thing to do in this case as it doesn't seem to even find mmcblk0p5. I believe this did not work?
With device connected to pc, check which /dev/sdX it is in dmesg and do in Terminal "fdisk -p /dev/sdX" with X replaced with the correct character. Copy the output here.

Blefish said:
I believe the full wipe is the only thing to do in this case as it doesn't seem to even find mmcblk0p5.
Click to expand...
Click to collapse
I believe so...
Blefish said:
I believe this did not work?
Click to expand...
Click to collapse
Already tried that and yes, it didn't work.
Blefish said:
With device connected to pc, check which /dev/sdX it is in dmesg and do in Terminal "fdisk -p /dev/sdX" with X replaced with the correct character. Copy the output here.
Click to expand...
Click to collapse
Working on it ... Done.
[email protected] ~ $ sudo fdisk /dev/sdc
Command (m for help): p
Disk /dev/sdc: 3959 MB, 3959422976 bytes
255 heads, 63 sectors/track, 481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x60c808d5
Device Boot Start End Blocks Id System
/dev/sdc1 1 31 245760 b W95 FAT32
Partition 1 does not end on cylinder boundary.
/dev/sdc2 * 31 31 500 4d QNX4.x
Partition 2 does not end on cylinder boundary.
/dev/sdc3 31 32 3000 46 Unknown
Partition 3 does not end on cylinder boundary.
/dev/sdc4 32 480 3606339+ f W95 Ext'd (LBA)
/dev/sdc5 33 35 12288 59 Unknown
/dev/sdc6 41 58 133120 4c Unknown
/dev/sdc7 66 66 500 5a Unknown
/dev/sdc8 74 74 3072 58 Unknown
/dev/sdc9 82 83 7000 50 OnTrack DM
/dev/sdc10 90 91 3072 4a Unknown
/dev/sdc11 98 99 3072 4b Unknown
/dev/sdc12 100 127 224878+ 83 Linux
/dev/sdc13 128 204 618471 83 Linux
/dev/sdc14 205 480 2216938+ b W95 FAT32

Solved it!
Solution in the OP.

Nice. What about the IMEI/Wi-Fi mac address? Did you have to restore it or is it the same?

Blefish said:
Nice. What about the IMEI/Wi-Fi mac address? Did you have to restore it or is it the same?
Click to expand...
Click to collapse
Yes, I have to restore my own IMEI.

sorry, i've the pink screen but there isn't anything appearing in ubuntu, nothing to unmount, i don't if i can explane myself. (see atachment)

Uglamugla said:
sorry, i've the pink screen but there isn't anything appearing in ubuntu, nothing to unmount, i don't if i can explane myself. (see atachment)
Click to expand...
Click to collapse
I’m not an expert of Linux, however check if your phone’s disk/partitions are detected by your Linux machine. Maybe they’re not auto-mounted in Ubuntu.
In my case using Linux Mint, some of my phone’s disk/partitions were auto-mounted when connected, so it had to be unmounted just to be safe.
Open GParted. If you see like the attached image then you’re good to go. You can proceed to the next steps.
Good luck.

My Phone was bricked cause the Data Partition was totally messed Up.
Now its working again!!!
Thanks buzzcomp for your awesome guide!!! :laugh:

mitsosc said:
My Phone was bricked cause the Data Partition was totally messed Up.
No its working again!!!
Thanks buzzcomp for your awesome guide!!! :laugh:
Click to expand...
Click to collapse
You're welcome

For u8800PRO
Dows anyone have, or make a full phone backup for the u8800PRO?
I had one, that I made the first day I bought the phone,
but my HDD failed and now that I need it I don' t have it
PS: I have a backup from my IMEI so restoring that will not be a problem....
And here is the how to, if anyone willing to help...

buzzcomp said:
You're welcome
Click to expand...
Click to collapse
Hmm...Sorry I'm totally a newbie to Linux~
I've downloaded the FullFlash, so how to locate the file?
Hope you can solve my question :good:

3.Unmount any newly mounted disks/partitions of your phone.
how do i do it?

No Pink
I was wondering if Ubuntu could solve my issue if I have no Piink screen. My phone will not turn on ever since i tried to do the update. It said that the updated failed so i turned the phone off and then nothing. No matter what I do it (pull battery 3 button restart or 2 button restart plugged in to pc or not) all I get is a small vibration no screens no nothing just a buzz. Do you think this will work for me? If not could you direct me to the proper technique? I have been searching and searching with no luck. Thanks in advance for any help.

What? So do I need Linux system to restore full flash?
Edit. Now sudo command is working but [email protected] isn't. How to enable that in windows? Guide isn't very good at all, very difficult to understand.
Edit 2: Step 4 is weird. Do I need to write both of those commands to cmd or just the first one?

MerkTheMedia said:
I was wondering if Ubuntu could solve my issue if I have no Piink screen. My phone will not turn on ever since i tried to do the update. It said that the updated failed so i turned the phone off and then nothing. No matter what I do it (pull battery 3 button restart or 2 button restart plugged in to pc or not) all I get is a small vibration no screens no nothing just a buzz. Do you think this will work for me? If not could you direct me to the proper technique? I have been searching and searching with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
So Lets See Here..... your phone is Not Recognized in Pink Screen or You Cant get in Pink Screen.????
---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------
Raineruf said:
What? So do I need Linux system to restore full flash?
Edit. Now sudo command is working but [email protected] isn't. How to enable that in windows? Guide isn't very good at all, very difficult to understand.
Edit 2: Step 4 is weird. Do I need to write both of those commands to cmd or just the first one?
Click to expand...
Click to collapse
i think its only one Command, any One Whichever Works..

Problem with persistent wallpaper

Two days ago i tried the next lancher 3d.. when I installed it, it was also installed its wallpaper.
Today i flash a new rom, the rasbeanjelly.. with twrp recovery: wipe cache, wipe dalvik cache, factory reset, format system, format data and format internal storage! So start the rom, config google account.. when i went to the desktop i was amazed The wallpaper of next lancher 3d is still here!
So i reflash the rom, again all wipe and format.. try with cmw recovery.. flash the aokp.. Flash factory image of android 4.2.2 by google.. but the wallpaper is still here. I can change the wallpaper but this is too weird ..
What could it be?
I read this thread..
In particular :
What are the partitions on a the N4?
A Nexus 4 has the following partitions: http://forum.xda-developers.com/showthread.php?t=2010338
modem -> /dev/block/mmcblk0p1
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p4
tz -> /dev/block/mmcblk0p5
boot -> /dev/block/mmcblk0p6
recovery -> /dev/block/mmcblk0p7
m9kefs1 -> /dev/block/mmcblk0p8
m9kefs2 -> /dev/block/mmcblk0p9
m9kefs3 -> /dev/block/mmcblk0p10
rpm -> /dev/block/mmcblk0p11
aboot -> /dev/block/mmcblk0p12
sbl2b -> /dev/block/mmcblk0p13
sbl3b -> /dev/block/mmcblk0p14
abootb -> /dev/block/mmcblk0p15
rpmb -> /dev/block/mmcblk0p16
tzb -> /dev/block/mmcblk0p17
metadata -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p21
cache -> /dev/block/mmcblk0p22
userdata -> /dev/block/mmcblk0p23
DDR -> /dev/block/mmcblk0p24
grow -> /dev/block/mmcblk0p25
Should i format one of these partitions? I don't know.. help me

disable google backup(after going through the sign in), it restores your wallpaper.

simms22 said:
disable google backup(after going through the sign in), it restores your wallpaper.
Click to expand...
Click to collapse
It was so simple? thank you very much

Aetos7 said:
It was so simple? thank you very much
Click to expand...
Click to collapse
out of curiousity, why does it matter so much since you can just change it?

simms22 said:
out of curiousity, why does it matter so much since you can just change it?
Click to expand...
Click to collapse
because both yesterday and today I had a little 'problems with the phone .. in practice after an hour of use when I try to bring up the menu notifications, this does not happen .. so I tried to touch and I noticed that the area where the status bar is not detected by the touch, as if she were dead .. i reboot and everything is back to normal .. then after an hour the problem appears again.
I changed the kernel, I thought it was that, but no! Now I hope that with the factory image of Android 4.2.2 everything is solved ..
Then, seeing that there was this wallpaper sticking up out of nowhere I got worried thinking that the nexus had broken!

Aetos7 said:
because both yesterday and today I had a little 'problems with the phone .. in practice after an hour of use when I try to bring up the menu notifications, this does not happen .. so I tried to touch and I noticed that the area where the status bar is not detected by the touch, as if she were dead .. i reboot and everything is back to normal .. then after an hour the problem appears again.
I changed the kernel, I thought it was that, but no! Now I hope that with the factory image of Android 4.2.2 everything is solved ..
Then, seeing that there was this wallpaper sticking up out of nowhere I got worried thinking that the nexus had broken!
Click to expand...
Click to collapse
does the dead spot come back even if there arent any apps installed?

simms22 said:
does the dead spot come back even if there arent any apps installed?
Click to expand...
Click to collapse
I do not know yet, I'm testing right now!

Aetos7 said:
I do not know yet, I'm testing right now!
Click to expand...
Click to collapse
i have a feeling that its an app thats causing trouble for you. im also on rasbean(with trinity kernel), and have never had that issue.

simms22 said:
i have a feeling that its an app thats causing trouble for you. im also on rasbean(with trinity kernel), and have never had that issue.
Click to expand...
Click to collapse
I have the same feeling.. because I also tried the slimrom and liquidsmooth and some kernel and the problem still there .. I just find this application makes me this joke

Aetos7 said:
I have the same feeling.. because I also tried the slimrom and liquidsmooth and some kernel and the problem still there .. I just find this application makes me this joke
Click to expand...
Click to collapse
bad joke!
theres a bad joke here at my work too(furniture store). someone is also playing a practical joke on the store, its the 5th time they placed an iphone ad into craigslist advertizing 10 brand new iphones in a box for $425 each, with our phone number. im going to shoot the phone. ive complained to craigslist, and they remove the ad. but the person keeps adding a new one. craigslist refuses to ban the poster or flag out phone number

simms22 said:
bad joke!
theres a bad joke here at my work too(furniture store). someone is also playing a practical joke on the store, its the 5th time they placed an iphone ad into craigslist advertizing 10 brand new iphones in a box for $425 each, with our phone number. im going to shoot the phone. ive complained to craigslist, and they remove the ad. but the person keeps adding a new one. craigslist refuses to ban the poster or flag out phone number
Click to expand...
Click to collapse
Bad Joke!
I think that the app cause the problem is light flow with reduce wake actived!
EDIT; the problem is still here..

[Q] dd command is only writing 64k bits to partition

I have a sprint phone that can only get into bulk mode. I followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142 and everything works fine except for the dd command. When I write to a partition (well at least aboot and recovery since those are the only 2 I've tried) and then cmp the image to the partition I just wrote to only the first 64k bits match out of the 1MB partition. I've tried ubuntu fatdog and gparted and all have the same problem. What's weirder is that before I borked my phone I used the Zv8_aboot.img that is around and when I just try to rewrite that image it is still only the first 64k bits that match so it's like I'm not writing to the write part of the partition because the img and the partition should match.
I didn't make a backup of the aboot partition before doing all of this so if anyone else has a sprint phone with a ZV8_aboot.img in the aboot partition, and has access to bulk mode can you use dd to make an image of the partition so that I can try to at least get my aboot back? After that I'll try this: http://forum.xda-developers.com/showthread.php?t=2708466&page=2 to get into fastboot.
Also, for anyone else that has no download mode and no recovery you can get into bulk mode by going into factory reset mode. I can't remember the exact button presses for that but after you are in and you hit power 3 times your phone shouldn't reset (you might have to have a custom recovery installed for that to be the case though) but it will end up going into bulk mode; it did for me anyway.

sorry for responding to my own thread, the edit of the 1st post just wasn't saving
Alternatively does anyone know an alternative to DD?
Update:
Tried on different computer, tried with my tongue sticking out at a 33 degree angle, tried with ddrescue, always the same thing..... fts

Update
I finally looked at the entire hex file for aboot and I found that it seems to write everything fine except for the bits between 65537 and 122880, 64k-120k or sectors 129 to 240 given 512bit sector sizes. This seems really odd. I think my only hope would be getting a good aboot from someone's sprint and writing only to the other sectors and not 129 to 240. Even then I might have to figure out if 129 through 240 aren't changed or are somehow purposefully scrambled when written to through hardware.... this is so lame.
So if you have a sprint phone with a zv7 or zv8 aboot and can get into bulk mode I'd very much like a copy of your aboot.img when you do a raw copy of it using dd.

going to reply to myself cause
I need to help someone in the development forum, so I need 6 more posts to post there

more self posting
self posting is natural there's no need to be ashamed

man this is annoying why 10 posts
If anyone can help me to create a loop back device that maps to the sectors in question, I'd appreciate the help.

ya, i setup a loop back device
losetup -o 65536 --sizelimit 57344 /dev/loop3 /dev/sdi5

Omg it has worked so far!!!!
setting up a loopback device over the sectors that weren't writing correctly has so far worked for aroot... I think I want to do the same for the recovery and see my phone actually boot first though

Works but.....
This is going to take forever, I guess I better figure out how to right scripts since I'm manaully putting in 4 commands to go 64k at a time out of 16MB.... fml

SOLVED
I did it my way..... oh franky

ArchROM -- any interest?

Hi all,
I had an idea last night; our Android phones are computers, right? And recently someone found a way to run Android apps on Linux.
Many developers here are familiar with Arch Linux; many are also familiar with its minimalist approach. There is a way to install Arch Linux ARM for rooted phones to be used inside Android, but what if we made it better -- what if we made an Android ROM based off Arch that you built from scratch? Consider the possibilities: If you don't care to use your phone (maybe it's outdated) as a regular phone, make it into a computer. Hook it up to a monitor (Chromecast, anyone?) and perform normal computing operations. Although the Moto G lacks RAM, running it with just a WM and making swapspace would do wonders; a Moto X would be even more perfect. Why not re-purpose your old phones into new computers?
I have been using Arch as my primary OS (only one installed on this computer) for 5 or 6 months now, and while I'm no expert I think that getting this to work wouldn't be terribly difficult. My thought on how this project would proceed:
1) Install a basic system (or boot some sort of install img) from fastboot
2) Repartition the internal SD card, do away with Android (maybe add dual-boot support eventually?)
3) Install Arch normally
4) Work on a package for a DE that supports touch screen
5) Create an easy package to allow for installation of Play store and running apps
The beauty of this would be similar to Arch: flexibility, choice and the option to run a minimalist version of Android, stripping away excess features so that users can have what THEY need.
I'm going to try to turn the ISO into an IMG and see if fastboot will let me boot it. I'll report back; if anyone can help out, let me know -- can't do it all by myself! I'd love any recommendations you guys have, or if it won't work just let me know right off the bat lol. Thanks!
EDIT: Tried making an img but don't think fastboot can boot such large images... maybe a custom recovery that can boot images? Basically I'm just trying to figure out how to unmount the partitions and modify them. Obviously if you can't it will be a bit harder because we'll have to build an Arch system that fits into the Android partitions. But a single root partition would probably be most convenient for these purposes.

Repartitioning the internal storage is extremely risky and you could hard-brick your phone
Good luck anyway, you might wanna look into Ubuntu Touch

DustArma said:
Repartitioning the internal storage is extremely risky and you could hard-brick your phone
Good luck anyway, you might wanna look into Ubuntu Touch
Click to expand...
Click to collapse
So I've read... and yes yes, there's Ubuntu Touch, but Arch deserves a mobile port too!

Sounds good... Can I help you with this project?
P.S. I'm not a developer
Sent from my XT1033 using XDA Free mobile app

K3VYNC said:
Sounds good... Can I help you with this project?
P.S. I'm not a developer
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Certainly!
From elinux.org: Fastboot is the name of a tool used to manipulate the flash partitions of the Android developer phone. It can also boot the phone using a kernel image or root filesystem image which reside on the host machine rather than in the phone flash. Think fastboot is what we need. @DustArma mentioned that it's risky to change partitions, but can that hurt fastboot? Can you make a backup of the partitions with fastboot?

This is extremely risky and I don't really think you should attempt it unless you've got more than 3 devices just waiting to get bricked before you may achieve something. I'm not trying to disrespect at all, but a project like this takes a lot of skill and more than just basic knowledge on how to build. Of course, I'm not exactly trying to stop anyone from doing this, but it is extremely risky for your device.

What you are suggesting is very, very difficult to achieve and as it's been said, it requieres a deep knowledge and expertise just to give it a shot... and if I had to bet I'd say it would fail even in the most expert hands. Respectfully said... it sounds like you are considering it out of the lack of experience and skill. Talk to kernel and rom devs, falcon has tricky hardware.
Just my opinion, for sure you are free to do whatever you want with your device.

Oh wow, really? I thought that fastboot was like BIOS, so messing with internal storage would be nothing. Who would you recommend I talk to @fermasia?
Sent from my Moto G using XDA Free mobile app

Jhdoubleoseven said:
Oh wow, really? I thought that fastboot was like BIOS, so messing with internal storage would be nothing. Who would you recommend I talk to @fermasia?
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
YoshiShaPow has done great with his kernel and you read his opinion... But you can browse around the forum. [emoji106]

So what makes Android phones unique compared to computers... Like I can remove my hard drive and my computer can still function, assuming I can boot from a USB drive or CD
Sent from my Moto G using XDA Free mobile app

first of all, wrong section as nothing is uploaded yet and you are just in discussion phase.
second you might get lucky with multiom support. should be less risky. but i don't know how pure arch will run considering so much closed source binary blobs for arm system.
should be a fun project. you should not get discouraged by what others say and you can always get your mobile repaired.

Well...haters gonna hate. No offense. But I think your idea is great!
I think here's what our first thing should be:
1. Since archlinux has a different partition table, we need to study and analyze both android(specifically moto g's) and Arch Linux partition table.
2. A new(or a modified) partition table will have to made, which has the following:
a)keeps fastboot partition untouched(so that we are "brick-free")
b)matches the partition sizes of Arch Linux keeping in mind the internal storage limitation. (Theoretically, bootable USB should be a safer and an easier option).
3. This partition can then be flashed using fastboot (same as gpt.bin file in firmware packages. GPT-General Partition Table).
This completes the first important step. Next step will be the kernel that supports our phones hardware.
PS: I am not a developer. I possess basic knowledge of linux. One can expect nice ideas from me. I'll help in whatever way I can.
Sent from my Moto G using Tapatalk

Please leave the development section for actual development
Thread moved

So I was looking at this:
https://wiki.ubuntu.com/Touch/ContainerArchitecture
And it tells us all about how Ubuntu Touch does it -- think ArchROM needs to be engineered in much the same way, possibly using Ubuntu Touch as a base then slowly removing it and replacing it with Arch -- as they did to Android. Not pure but it works.
Code:
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162815 512K 0700 hob
20 162816 162831 8192 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229119 10.0M 0700 boot
32 229120 249599 10.0M 0700 recovery
33 249600 1605631 662M 0700 cache
34 1605632 3604479 976M 0700 system
35 3604480 3620863 8192K 0700 kpan
36 3620864 30711551 12.9G 0700 userdata
There is what I found for the partitions. Obviously, as mentioned in the Ubuntu Touch article, it would be MUCH easier to let Android initialize the hw then boot up the Arch rfs

Look at this.
https://plus.google.com/101741693669616771532/posts/WZtnchkubYf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}