I was deleted my ext2 partition that it was used by app2sd. Now my tab was rebooting after boot animation and it never stop until I move the battery. I still can go to recovery mode, wipe all data and factory reset. But nothing happens, it still boot looping and never get onto system.
For Information :
My device is Chinese made Tablet based on MTK6573 platform with Dual GSM SIM Card and Analogue TV support. I can't found any stock ROM or custom ROM for this model. So please don't suggest me to flash it ROM. I have been try every related thread with MTK6573 but nothing fix.
Every step I've tried :
1. Flashing new ROM with SP Flash Tools. Result : No ROM compatible with this tablet.
2. Flashing with Update.zip ROM from Recovery. Result : Same as above.
3. Flashing with fastboot. Result : HBoot is not supported this tablet.
Please help me to solve this problem. Big thanks for your help!
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
r.darwish said:
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
Click to expand...
Click to collapse
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
nerot said:
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
Click to expand...
Click to collapse
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
r.darwish said:
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
Click to expand...
Click to collapse
Official builds do not contain the recovery.
Sent from my LG-P350 using xda premium
oneovo establish
I used official builds for both 10 and 7.
Hello Guys. First off i must say im very confused! I'm not very tech savy when it comes to rooting phones and such. So please when you reply could you make it as simple as possible. thanks
Okay so my phone is currently on 4.0.3
BASEBAND I9100XXLPS
BUILD NUMBER IML74K.XWLP4
Now i've tried updating to a later version but it doesn't seem to work. I'm not sure what im doing incorrectly. I think its odin that you wait for that Yellow light or something but it never goes yellow?
Anyway could you kindly link me to a stable firmware that i should use.
Could you provide any links for odin ( or any other software needed ) just incase there are updates because i haven't used it for a while.
Rooting
I would assume i would root after once i've updated to the new version.
Could you kindly provide a link that explains it pretty easily for me to root the phone.
My end goal is to put CyanogenMod on the phone.
If i've missed anything out or miss understood something, please feel free to explain.
thank you in advance for the help.
First,forget about doing anything until you get Odin sorted out.
You can root and flash roms without using Odin.......but if something goes wrong(like no bootup c/w cant acess recovery) then you are in big trouble because Odin isnt working.
skip the firmware update and jump right for cyanogenmod.
1. Download any version of CWM from here
2. Get desired rom
3. Place everything in Externel SDcard
4. Boot into stock recovery (Power+Home+Vol up)
5. Use stock recovery to flash CWM
6. Backup Current stock rom
7. Wipe the usual
8. Flash Custom rom (Or just kernel)
9. Reboot
10. ?? Profit ??
Now you got Custom rom or Kernel + Full stock rom backup (can always get stock rom from sammobile if you lose it)
Okay so i update the firmware wooo.
Wouldn't i need to root the phone to install cyanogenmod ?
I have been dual booting stock Android 4.0.4 and CM 9.1 on my S2 for awhile now with minimal issues. However, some small things have stopped working correctly, and since I noticed that both stock Android 4.1.2 and CM 10.1 are now available for the S2, I figured it was about time to switch to those.
I fought with this all last night though but couldn't get it to work. I have been trying the following steps:
Download Android 4.1.2 stock rom from sammobile.com and flash to device using Odin 3.07. Boot up and verify everything is working correctly.
Download Siyah kernel (I'm unfortunately not sure what version as I am at work and it is on my computer at home) and flash to device using Odin 3.07. Boot up and verify everything is working correctly.
Download cm-10.1.3-i777.zip from download.cyanogenmod.org and load image on internal SD card. Boot into CWM recovery. Choose to install 2nd ROM from internal SD card and select that zip file. Verify CWM says installation completes successfully.
Boot both primary and secondary roms and verify they work correctly.
My verifications succeed until step 4, in which both fail. The primary rom (stock Android) gets stuck in an infinite loop loading the AT&T startup image. I just get a blank screen when booting the secondary rom. I've tried these steps a few times with minor variations with the exact same result.
Should I be able to get this to work? If so, what Kernel do I need? My web research seems to be inconsistant as to whether this can work or not. I haven't found anyone that definitively stated they've done this on an S2.
I did find a post for the "Googy" kernel (http://forum.xda-developers.com/showthread.php?t=2270158) that claims this should be possible, but the instructions on how to load it are less that complete. It just says "Flash Googy-Max Kernel", but I'm not sure how to do that. I only know how to flash a kernel using Odin, but Odin needs a .tar.md5 or similar file. The Googy kernel comes in zip format and contains a META-INF directory and boot.img file at its root, and Odin doesn't appear to support that format. Trying to load the zip from CWM after loading the Siyah kernel had ... less than desirable results.
hi,
here's the steps I did :
1) I had on phone last official sony android firmware 4.0.4 version.
2) rooted the phone and unlocked the phone : ok
3) tried to load custom rom ultimate hd but no success, phone was blocked on the initial logo
4) downloaded official sony emma tool in order to load the original firmware:
the only option was android 2.3.6 and I was able to load it and phone worked again;
5) rooted again the phone,
6) now pc companion pops up with message of possible update to 4.0.4; try to do it but
message error got, update is not possible due to modified firmware.
here's my question : how I can got again android 4.x in general starting from android 2.3.6?
Never mind is not the official one, I 'm interested to any rom 4.x (working ok of course, maybe optimax)
that can be downloaded on the phone.
Is it possible to have all the steps in detail? I'm not so familiar with flashtool.
Thanks/andropagp
andropagp said:
hi,
here's the steps I did :
1) I had on phone last official sony android firmware 4.0.4 version.
2) rooted the phone and unlocked the phone : ok
3) tried to load custom rom ultimate hd but no success, phone was blocked on the initial logo
4) downloaded official sony emma tool in order to load the original firmware:
the only option was android 2.3.6 and I was able to load it and phone worked again;
5) rooted again the phone,
6) now pc companion pops up with message of possible update to 4.0.4; try to do it but
message error got, update is not possible due to modified firmware.
here's my question : how I can got again android 4.x in general starting from android 2.3.6?
Never mind is not the official one, I 'm interested to any rom 4.x (working ok of course, maybe optimax)
that can be downloaded on the phone.
Is it possible to have all the steps in detail? I'm not so familiar with flashtool.
Thanks/andropagp
Click to expand...
Click to collapse
- make sure you have installed the android sdk (just press install packages) & install flashtool allways IN main drive (not in subfolder) also install the proper drivers from drivers folder of flashtool install.
how to get to official 4.0.4 ROM using flashtool (only way after bl unlock..) (dl & good explanation there)
http://talk.sonymobile.com/t5/Andro...y-Bean-ICS-Ice-Cream-Sandwich-and/td-p/154389
how to install custom ROM: 1st check if you need a custom kernel --> b)
a) no custom kernel need (& you still have stock kernel FROM SONY ICS UPDATE!)
- install CWM recovery by x-parts tool found in xperia arc apps thread
- place rom & other needed files (maybe gapps) on SD
- boot to CWM. select wipe data/ factory reset.
- install ROM as mentioned on thread.
- boot.
b) if you use a custom kernel CWM is mostly inside. so just press vol down contunesly on boot screen (on very 1st)
- place rom & other needed files (maybe gapps) on SD
- boot to CWM. select wipe data/ factory reset.
- install ROM as mentioned on thread.
- boot
bejunk said:
- make sure you have installed the android sdk (just press install packages) & install flashtool allways IN main drive (not in subfolder) also install the proper drivers from drivers folder of flashtool install.
how to get to official 4.0.4 ROM using flashtool (only way after bl unlock..) (dl & good explanation there)
http://talk.sonymobile.com/t5/Andro...y-Bean-ICS-Ice-Cream-Sandwich-and/td-p/154389
how to install custom ROM: 1st check if you need a custom kernel --> b)
a) no custom kernel need (& you still have stock kernel FROM SONY ICS UPDATE!)
- install CWM recovery by x-parts tool found in xperia arc apps thread
- place rom & other needed files (maybe gapps) on SD
- boot to CWM. select wipe data/ factory reset.
- install ROM as mentioned on thread.
- boot.
b) if you use a custom kernel CWM is mostly inside. so just press vol down contunesly on boot screen (on very 1st)
- place rom & other needed files (maybe gapps) on SD
- boot to CWM. select wipe data/ factory reset.
- install ROM as mentioned on thread.
- boot[/QUOTE
Many thanks, I was able to load the official rom; it was easy.
Just a note : I was not able to download flashttol and rom from link provided for free.
I was anyway lucky, because I already doownloade din the past the rom and
old version of flashtool; i used them and everything was ok.
Next step will be to load a custom a ROM
thanks again/angropagp
Click to expand...
Click to collapse