Related
I will be editing this post, and organizing everything, so stay put.
EDIT: I am no longer using my Fusion 2 as my primary phone, but I will still be able to update this thread. If you need any help, just post here, or shoot me a PM.
Links and Guides
Root your Fusion 2
Installing CWM 6
How to install CM7.2
Q&A
Q1.How do I root my phone?
A1.There are several ways to root your phone.
Shagerty's Guide
RoboticBuddy's Guide
Q2.How do I install a Custom Recovery?
A2. User Oct3178 has discovered that the Y201 CWM works with our U8665. Check out his post here, and follow "Installing CWM Recovery":
User Shagerty has made a step-by-step guide for installing CWM.
Oct3178's Post
Shagerty's guide
Q3. Are there any ROMs for my phone?
A3. The post in A2 gives you that answer. You can use Huawei Y200 ROMs for the U8665.
RFE has also dumped a pre-rooted stock ROM.
NEW:Shagerty has developed CM7.2 for this device. Please refer to the links above the Q&A.
Oct3178's Post
RFE's Post
Thanks to RFE, who made rooting the Fusion 2 possible!
RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE
RFE said:
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE
Click to expand...
Click to collapse
If you could, please PM me the Rom, so I can add it to the OP.
Thank you,
-RoboticBuddy
Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.
statussticks said:
Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.
Click to expand...
Click to collapse
I do believe that RFE is working on a custom ROM that removes all the CrapWare that was pre-installed on the phone. Hopefully after that, he will be able to start to build CM for it.
If I could, I would attempt to start building CM for the Fusion 2, but I do not know how to setup a build environment.
Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?
Thanks
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys
still bricked
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!
BOOOYA, well done! Rooted WiFi homephone.. thank you!
Lmao, so rad
statussticks said:
Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?
Click to expand...
Click to collapse
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
ericrazy2000 said:
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys
Click to expand...
Click to collapse
sinco54 said:
BOOOYA, well done! Rooted WiFi homephone.. thank you!
Click to expand...
Click to collapse
gigilie said:
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!
Click to expand...
Click to collapse
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:
RoboticBuddy said:
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:
Click to expand...
Click to collapse
I hope so, i bought this phone at frys for 59.99 on a crazy 1 day sale for no good reason. lol... Its actually a pretty little impressive piece for the price and a custom bare bones aosp/aokp/cm would be the meow meow!!! cool little phone for sure!!
I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..
statussticks said:
I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..
Click to expand...
Click to collapse
A working twrp would be straight drug deala pimp style.. I'm gonna reach out to a couple of devs that may be willing to help out but I don't know, I may have to get him loaded and bribe him with cheap hookers. Also, if you go for it and your phone explodes into puppies then is be willing to help on a 2 device for development.. ill run by frys and see if they are on sale or if I can weasel the sales guy into hookin a sale price up today after I close the store.. stand by sweetie pie.
Sent from my HTC One XL using xda premium
Got Root/Trying to build CWM
sinco54 said:
Lmao, so rad
Click to expand...
Click to collapse
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)
Shagerty said:
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)
Click to expand...
Click to collapse
I'm trying /a friend of mine/ is to get a twrp to function..
Also, these phones were on sale at Fry's again but were 79.99.. I picked 1 more up solely for development.
Sent from my One X using xda premium
Thank you! Rooted my phone without any problems following your instructions!
Probably it is a wrong place to ask such questions, but could you point me to any information how to unlock network on this phone (currently it is locked for AT&T, and can be used with their SIM cards only)?
Thank you!
I'm still looking for that info too...
Sent from my HTC One XL using xda premium
Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup and Root Uninstaller to remove AT&T apps.
Aknodx said:
Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup to remove AT&T apps.
Click to expand...
Click to collapse
Where did you buy the unlocking code?
Dual Booting Project
Android OS - Ubuntu Phone OS
As the title says, I think we can make posible dual booting Android and Ubuntu.
1st post Experimental Methods, Useful Infromation and Help Needed
2nd post News
3rd post How to install Ubuntu Phone OS
Experimental Methods
1-. This method was originally posted by beidl
The method that beidl suggested us is to make this steps:
"Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff"
"Flash CM back to the device"
"Copy specific files back to /system"
"By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up."
NOTE: Nobody try it, be the first!
*Using these methods you could brick your GNex, the poster of each method and me aren't responsible of any damage on your GNex!*
Useful Information
Here is partition table:
ytwytw said:
[...]
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
[...]
Click to expand...
Click to collapse
&
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
Info about GRUB on ARM v7
Help Needed
I think we can modify partition table making more partitions and modifiying Ubuntu Phone OS kernel to boot in asigned partitions but I need help:
How much partition we have to add? (System, data..)
I think we have to edit bootloader + kernel, How to do it?
It will be posible?
I don't know a lot about partition tables and editing bootloader & kernel but, I think I will be able to help.
PD: If moderator or developers in this section think that it will be better to post this thread in general or in development, don't worry moving it.
News
News
22/02/2013:Thanks to beidl, I think we have the posibility to boot CM 10.1 and Ubuntu Phone OS. Take a look at the 10th post:
beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
23/02/2013: I'm working on a modified version, now fisrtly I will delet all videos & images that came as a sample. EDIT: I have edited it, to download it, go to the 3rd post!
Files & How to install Ubuntu Phone OS
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them in CWM or TWRP (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.
Don't you need like a bootloader to dual-boot?
jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Read the op again. *i think we need to edit the bootloader.
Sent from my Galaxy Nexus using Tapatalk 2
jimmyco2008 said:
Don't you need like a bootloader to dual-boot?
Click to expand...
Click to collapse
Yes, I need help to edit GNexs' bootloader to be able to boot both OS
Regards,
Urko
Enviado desde mi Galaxy Nexus usando Tapatalk 2
It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.
beidl said:
It's a very bad idea to screw around with the bootloader and partition table.
kexec would be the way to go, but it requires kernel patches for both the Android ROM and the Ubuntu ROM.
Also, since Ubuntu Touch is just chrooted inside CM, I guess it would be possible to make some CM specific tricks,
like creating a file on the filesystem, check for it on bootup, if it exists, boot into the chrooted Ubuntu environment.
I still have to take a look at the source though, basically finding out at which stage the ways of Android and Ubuntu seperate.
Click to expand...
Click to collapse
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!
Not a dev, but thought I'd try and give some helpful advise. I have an HP TouchPad that dual boots webOS and Android. Maybe looking at how that works will help you. Just a thought.
urko95 said:
Do you think we will be able to run Ubuntu and CM? My idea was to modify partition table to add more partition and then, if you wanna run Android OS, flash its kernel to boot it in Android OS or flash Ubuntu Phone OS kernel (edited to boot specific partions) to boot Ubuntu Phone OS. Do you really think that it's a bad idea? I think it is the best option (and it's the only I know). Could you give me more details of that "Specific tricks" to do with CM?
BTW, I NEED MORE HELP!
Click to expand...
Click to collapse
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
beidl said:
There is a script + binary in the Ubuntu package which basically set up the the Ubuntu environment inside of a working Android installation.
The Ubuntu folder structure can be found in /data/ubuntu/.
Booting up is just like on every Android ROM, except the mentioned script gets started and the Ubuntu environment is getting started up.
The first proof of concept would be:
Backup every Ubuntu Touch specific file that got installed to /system to the PC, like the chroot scripts and other stuff
Flash CM back to the device
Copy specific files back to /system
By flashing either the boot.img of CM or Ubuntu Touch the desired system should boot up.
Click to expand...
Click to collapse
I will give it a try later!
Thanks for your help!
couldn't modifying the bootloader be considered distributing a derivative work under the dmca?
In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.
anarkia1976 said:
In my opinion to have a dual booting you will need:
- A ramdisk that will prepare the partitions according to the choice of which OS
- A kernel that supports two versions of OS
- Two separate SD with the respective folders drivers etc. ... (This Is not possible on GNEX)
For the rest I do not know ubuntu for phone, it would take some expert.
Click to expand...
Click to collapse
Anarkia, What do you think about beidl's method?
NOTE: Thread organized and updated
A edited phablet file, I have deleted all sample photos, videos and messages. To download it, go to the 3rd post!
Excuse me,
can i flash these flies with CWM recovery?
urko95 said:
How to install Ubuntu Phone OS
NOTE: This files doesn't include the option to make a dual boot yet
-I'm not responable of any damage could have your GNex after flashing Ubuntu Phone OS this way-
Steps:
Download files quantal-preinstalled-armel+maguro.zip (4,6 MB) and quantal-preinstalled-phablet-armhf.zip (481 MB), and copy them to your GNex.
NOTE: You can use a modified file without all sample photos, videos and messages modified by me. Donwload it here: edited-quantal-preinstalled-phablet-armhf-v1.zip
Make a Nandroid Backup (to be able to restore Android later)
Make a Factory Reset
Flash them (1-.quantal-preinstalled-armel+maguro.zip and 2-.quantal-preinstalled-phablet-armhf.zip)
Reboot (In a few seconds Ubuntu will boot up)
If you want to restore Android, make a backup of Ubuntu first if you want to install Ubuntu again
*This guide was originally posted by eng.stk*
NOTE: Second file (quantal-preinstalled-phablet-armhf.zip) will take few minutes to flash so don't panic and relax until it's flashed but, if you use the file that it has been modified by me, it will be faster. This method doesn't wipe your internal storage (/sdcard)
This way you could have both system only restoring backups of both OS. It's a good to have both system while dual boot it's being developed.
Click to expand...
Click to collapse
LucaZPF said:
Excuse me,
can i flash these flies with CWM recovery?
Click to expand...
Click to collapse
Yes, you can, with TWRP or CWM, you choose.
Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
/system/bin/modelid_cfg.sh
/system/bin/ubuntuappmanager
/system/bin/ubuntu_chroot
/system/bin/uchroot
/system/usr/idc/autopilot-finger.idc
/system/quantal-ubuntu_stamp
Click to expand...
Click to collapse
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...
beidl said:
Reporting semi-success
So i diffed the system directories of CM 10.1 and Ubuntu Touch and found the new files.
I pushed those files to my working CM 10.1 installation on the GNex.
Since I did not wipe my GNex when I went back from Ubuntu Touch to CM 10.1, the folder structure
of Ubuntu stayed at /data/ubuntu/.
Then, I rebooted into the bootloader and flashed the boot.img of Ubuntu Touch to the GNex.
After rebooting, the device was stuck at the Google boot logo but the kernel did actually boot, so I was able to adb shell into the device.
dmesg returned:
Code:
<6>[ 15.739807] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4783, /home/ubuntu/jenkins/workspace/phablet-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c]
That means Canonical still uses the kernel from before a week, this kernel doesn't play nicely with the new proprietary GPU driver.
I'll try pushing the old GPU blobs now...
Click to expand...
Click to collapse
Waiting to your results, great job beidl!
Sv: [DEV] Dual Booting Project [Android - Ubuntu Phone OS] (HELP NEEDED)
First zip to flash is linked wrong it links to the IMG
Ubuntu phone os is nice but laggy buggy power eating just tried it. Maybe we should focus on it running good before dual boot
Did anyone try using it ? Gsm and all that did not work on my gnex. Did you guys have luck?
Sent from my Galaxy Nexus using xda premium
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
GiZiM said:
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
Click to expand...
Click to collapse
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button (shouldn't be more than a couple of minutes). On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Thank you! I will look into this but I would love to fix the cause.
I'm sure this is the issue because I cannot get the phone back into a working state until after doing a full factory wipe.
What would be causing 4.3 roms to corrupt my /userdata? Whatever it is it is happening after the first reboot after I get into the rom.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Thanks this is very helpful, I will work on this tonight after work and see what I can come up with.
Right now it is showing as CLEAN but i'm running 4.2.2. Is there anything special to go from 4.2.2 to 4.3?
desktopfusion said:
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Click to expand...
Click to collapse
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
I'm going to give it a go tonight when I get home.
1. So pretty much backup everything, do a complete factory wipe of all data.
2. I'll do a adb push of the .zip for the rom and everything.
3. Flash rom and any other packages needed
4. Run that command see if it comes back clean
5. Reboot go into the rom
6. Reboot, if i get stuck at the Google screen run that script if it's not clean just keep running it?
desktopfusion said:
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
Click to expand...
Click to collapse
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
GiZiM said:
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
Click to expand...
Click to collapse
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Lifesaving string of code.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Holy mother of god.
This was a lifesaving string of code. I was convinced that I was going to have to buy a brand new phone. Kudos to you DesktopFusion. Thanks a lot!
Explanation as to why a corrupt userdata partition causes this issue
So, in case anybody was wondering, I would like to explain how I see the issue at hand (corrupt userdata partition).
Upon first boot, the ROM is getting set up and doesn't have any orders to check /userdata because well, there is none on the device. So why waste precious time being redundant (smart coders, right?). So the userdata partition is not checked.
However, now that the second boot is being performed, there is, by default in the system's repertoir, data put in by the user, so the bootloader is told to check the partition containing user data. Since the partition is corrupt, and the free space is technically "modified", it errors up and gets stuck.
I could be wrong, I'm not a developer of any sorts. Just a dude giving my point of view.
I got this trouble too last night. I'm flashing elia's 4.3 custom rom with under 5 gb free space. Got it boot twice,then got stuck at google's logo after trying flashing slim bean gapps. Flashing whole 4.3 stock firmware finally solve this. Maybe there is correlation between upgrading from 4.2.2 without upgrading the bootloader with this problem.
Sent from my Galaxy Nexus using Tapatalk 4
It ended up running for 6hrs and never finished, I did do the -n and it said it was CLEAN but still could not boot into the 4.3 ROM.
So ran it any way for 6hrs and no change as of right now I am unable to boot into ANY 4.3 ROM.
If eMMC was screwed up why can 4.2.2 roms work fine but not 4.3 roms? what's the difference?
desktopfusion said:
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Click to expand...
Click to collapse
BUMP still no 4.3 love
GiZiM said:
BUMP still no 4.3 love
Click to expand...
Click to collapse
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
desktopfusion said:
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
Click to expand...
Click to collapse
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
GiZiM said:
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
Click to expand...
Click to collapse
Rats. Falling short of ideas.
I might have missed your answer on whether you've tried flashing a stock Nexus image through fastboot, though.
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.http://forum.xda-developers.com/images/smilies/highfive.gif
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
7175 nailed it. I tried flashing all sorts of different ROMs/gapps/Super SU combinations and tried different wipes/formats to no avail. I wish I would have found the instructions to "fastboot cleanse" the phone 4 or 5 hours ago. I have been reading through forums for several hours today and every suggested fix failed. 7175's fix was spot on for me. My phone was locking up at the Google screen with the lock every time I rebooted after installing a 4.3 ROM.
:highfive:
7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
Thanks for this...
First thought it was an issue with SlimRom, tried different kernels, problem wouldn't go away, then realised it was happening with every rom I flashed...
There is a modem for the optimus G here:
http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
but it is from firmware 10b. You may want to try if it works better than your firmware. In this case, it is better if you make a backup of your current modem firmware, so you can go back to your version. Here I will write instructions to backup your modem, so you can restore it if you need.
Probably some of you know this already and feel like these are old news, but maybe we can build a modem firmware library.
You need root and a way to make an adb connection to your phone. If you cannot use adb, you can always use a terminal emulator on your phone, but this makes it a bit harder to type the commands. Also, this is for people who understand what they are doing. If after reading the tutorial you don't understand what the commands do, please don't try it. Or at least don't make me responsible if your phone bricks. Here we go.
NON NEEDED STEPS: This steps are here to show why this works.
1-Connect to your phone by adb.
2- On the terminal type :
Code:
mount
You'll see the following (amongst other things):
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:radio_efs_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
This means that the partition containing the firmware is /dev/block/platform/msm_sdcc.1/by-name/modem and it is mounted at /firmware.
NEEDED STEPS
1- Connect by adb
2- On the terminal type
Code:
su
Check if confirmation is needed on the phone screen. If needed, accept.
3-
On the terminal type:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
4-You will receive the following after some seconds:
Code:
131072+0 records in
131072+0 records out
67108864 bytes transferred in 29.959 secs (2240023 bytes/sec)
5-Type
Code:
exit
exit
adb pull /sdcard/modem.img
6-Now you have your backup.
HOW TO PACK THIS BACKUP FOR FLASH:
1-Download the file: cwm-lgog_e975-europe-10b_modem.zip from http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
2-Open the zip file and replace the existing modem.img with your file
3-Rename the file to something meaningful, like cwm-lgog_e975-europe-10f_modem.zip
After these steps, you should be able to flash any modem, knowing that you can go back to your old version.
You can upload the packed files here, so we can have a library. I will upload the modem from european 10f version here. I tested it and it works correctly, but I won't take any responsibility for what you do with this file.
Good luck.
All this info is obtained from examining the houstonn LGOG modem flasher from team codefire, so all thanks go to them. Thanks.
Very nice tutorial man. It will help newbies like me to back up and restore our modem.img, especially those who have F180* phones that wants or being converted to E975. Nice job. :good:
Nice,i'll add this to the Freaking Annoying Questions.
Sent from Asylum via LG E975/smart phones,dumb people.
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
You should be able to backup your e977 modem following this tutorial.
renatonolo said:
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
sonty said:
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
Click to expand...
Click to collapse
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
I can, however, tell you how to backup it:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
Can I ask why you need that?
dapaua said:
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
Can I ask why you need that?
Click to expand...
Click to collapse
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
dapaua said:
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
Click to expand...
Click to collapse
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
jumper8 said:
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
Click to expand...
Click to collapse
Thanks.
You are totally right, this partition is not a filesystem. And it is mostly empty, it's all zeros except for some bytes. Most of it are text strings, but there are some small binary parts.
I think the 0x8800 - 0x8824 part is the original firmware version.
I wouldn't touch that partition, seems too dangerous .
dapaua said:
I wouldn't touch that partition, seems too dangerous .
Click to expand...
Click to collapse
freegee touches it. I see it made a backup and the difference is that it changed some bytes to 0 (offsets 0x40-0x52), then wrote ANDROID-BOOT at offset 0x4000. the rest is the same. it seems there's nothing like a crc so basically I could write whatever I want in that version field. the bad part is that as an user you'll never know what modem version you have since its version is not stored on the modem partition. I wonder who came up with this system and what was he thinking.
thanks for the clarification. offtopic over .
sonty said:
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Click to expand...
Click to collapse
Some time ago I had the same issue. I solved it by modifying binary data on the misc partition. I was done this only on CM10.1 (F180K). I don’t know if it will work on other custom rom especially stock one.
Today I’ve done this one more time for preparation the following procedure. Maybe some one will use it on the future.
STEPS:
0. Backup the misc partition with your recovery. I was used CWM Advance Edition PhilZ Touch 5:
Backup and Restore-> Custom Backup and Restore->Custom Backup Job->Backup misc (*)
I’m not sure if all CWMs version support misc partition backup. TWRP not support it right now.
1. Dump the misc partition to /sdcard.
Code:
adb wait-for-device
adb root
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc_orig.img"
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 6.539 secs (2565715 bytes/sec)
2. Pull the image to your PC
Code:
adb pull /sdcard/misc_orig.img misc_orig.img
3. Edit downloaded image file by your favorite hex editor (e.g. Notepad++ with Hex-Editor plugin)
Find both baseband name strings (mine were on offset 0x8800 and 0x9000) and change them (CM10.1 use the last one to set gsm.version.baseband in file /system/bin/fetch-swv).
REMEMBER:
- Do not use regular text editor (like Notepad or vi) – they can add some extra characters to the file.
- If possible try to modify only bytes responsible for original baseband name. If the new name is shorter, simply put spaces char (0x20) to clear unwanted chars. If you need to put the longer name, be careful. I don’t know the max size for this string. There are dozens of zeros behind the baseband name on my image file. So, for testing I added extra 20 Bytes text. The new baseband name was shown without problem.
4. Push the modified image file to your phone
Code:
adb push misc_orig.img /sdcard/misc_mod.img
Check if size of the original and modified files are equal.
5. Write the modified image to the misc partition
Code:
adb shell "dd if=/sdcard/misc_mod.img of=/dev/block/platform/msm_sdcc.1/by-name/misc "
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.183 secs (4010809 bytes/sec)
6. Reboot your phone
DONE.
Hi all,
I just create a .zip to backup your modem / baseband / radio with your recovery (CWM / TWRP...)
ok as a newbie i cant figure out how to back up modem using adb... but after reading stuff what i did :
downloaded "Android Terminal Emulator" from playstore
open emulator in phone wrote as u mentioned :
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
after some seconds this came out :
131072+0 records in
131072+0 records out
67108864 bytes transferred in 15.229 secs
then :
exit
exit
after that i checked sdcard but there was no img file...
then i open file manager from the phone and there it was my precious :laugh:
size = 64mb... is it normal?
anyway .. made a new folder "modem" copied the img file into modem folder (using file manger) again connected the phone to pc copied the modem folder on my desktop...
hope it will help new guys here like me :good:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
pedro5148 said:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
akahroba said:
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
Click to expand...
Click to collapse
I already did that, did not work out ...
any more solution?
pedro5148 said:
I already did that, did not work out ...
any more solution?
Click to expand...
Click to collapse
Get back to JB and wait for your midel update
Back to JB I recovered the IMEI, but I have no carrier signal.
So do the root with towelroot, unlock custom recovery with FreeGee, do I back up EFS, and when I restart the machine it loses the IMEI.
So I install the modem and E97710b.kdz for E97710b model recover EFS and nothing happens, still no sign of the operator ...
---------- Post added at 02:22 PM ---------- Previous post was at 02:22 PM ----------
akahroba said:
Get back to JB and wait for your midel update
Click to expand...
Click to collapse
even going back to JB, I continued without the modem
Hi there.
I'm experiencing something really weird... I just can't install any recovery and I've tried them all... TWRP, CWM and PhilZ Touch... everytime I reboot on recovery I just can't gett off of it.
The only way is Odin flash a prerooted firmware
So I just can't test any firmware flashable through recovery
Any clues how to solve this?
Although I am a noob when it comes to android, I never had any trouble flashing several roms on my previous ZTE and my current S III mini...
This T210 I just got, brand new, simply doesn't seem to like recovery software.
Thank you in advance
PS. Forgive my english, not my mother language
I don't know if this is helpful or not, but ROM Manager "asked" me to email this data:
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Jul 8 10:19:24 2014
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v6.0.4.9
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
recovery filesystem table
=========================
0 /system ext4 /dev/block/platform/sdhci-pxav3.2/by-name/SYSTEM 0
1 /efs ext4 /dev/block/platform/sdhci-pxav3.2/by-name/EFS 0
2 /cache ext4 /dev/block/platform/sdhci-pxav3.2/by-name/CACHE 0
3 /data ext4 /dev/block/platform/sdhci-pxav3.2/by-name/USER 0
4 /NVM ext4 /dev/block/platform/sdhci-pxav3.2/by-name/NVM 0
5 /boot emmc /dev/block/platform/sdhci-pxav3.2/by-name/KERNEL 0
6 /recovery emmc /dev/block/platform/sdhci-pxav3.2/by-name/RECOVERY 0
7 /modem emmc /dev/block/platform/sdhci-pxav3.2/by-name/MODEM 0
8 /storage/sdcard1 auto /devices/platform/sdhci-pxav3.0/mmc_host/mmc1 0
9 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 1
I:200 0 Volumes listed.
I:Processing arguments.
I:Cannot load volume /misc.
I:Cannot load volume /misc.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.cm.device=lt02wifi
ro.cm.display.version=11-20140611-UNOFFICIAL-lt02wifi
ro.cm.version=11-20140611-UNOFFICIAL-lt02wifi
ro.adb.qemud=1
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.serialno=4100a9999414a000
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=mrvl
ro.build.id=KTU84M
ro.build.date=Wed Jun 11 12:00:47 EDT 2014
ro.build.date.utc=0
ro.build.host=dave-VirtualBox
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=dave
ro.build.display.id=cm_lt02wifi-userdebug 4.4.3 KTU84M 1b8011aa0e test-keys
ro.build.product=lt02wifi
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.3
ro.build.version.codename=REL
ro.build.version.incremental=1b8011aa0e
ro.build.description=cm_lt02wifi-userdebug 4.4.3 KTU84M 1b8011aa0e test-keys
ro.build.fingerprint=Samsung/cm_lt02wifi/lt02wifi:4.4.3/KTU84M/1b8011aa0e:userdebug/test-keys
ro.build.characteristics=default
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=cm_lt02wifi
ro.product.board=PXA988
ro.product.brand=Samsung
ro.product.model=SM-T210
ro.product.device=lt02wifi
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=samsung
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=pxa988
ro.revision=7
ro.serialno=4100a9999414a000
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20140611-UNOFFICIAL-lt02wifi
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.sys.dun.override=0
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.sys.recovery_update=false
service.adb.root=1
keyguard.no_require_sim=true
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Cannot load volume /misc.
I:Can't partition non mmcblk device: /devices/platform/sdhci-pxav3.0/mmc_host/mmc1
I:using /data/media for /sdcard.
okay
okay so,
odin your prerooted again [i know, it sucks]
then try a
dd write of your custom reco instead of odin
m
was there anything else you did that you forgot to mention?
moonbutt74 said:
okay so,
odin your prerooted again [i know, it sucks]
then try a
dd write of your custom reco instead of odin
m
was there anything else you did that you forgot to mention?
Click to expand...
Click to collapse
I am sorry... what do you mean by "dd write"?
I guess that's all, I don't remember anything where i could screw up.
At this moment I am simply afraid to go into recovery again lol
ROM Manager tells me I have CMW and TWRP installed... well... after I Flashed a complete prerooted firmware (1,13GB) I thought those installations would have gone away.
I could swear that if I enter recovery at this point I would have the basic android recovery.
Is it possible that somehow, there's something confusing ROM Manager?
Or is there something left from custom recoveries somewhere?
ah
RockasKane said:
I am sorry... what do you mean by "dd write"?
I guess that's all, I don't remember anything where i could screw up.
At this moment I am simply afraid to go into recovery again lol
ROM Manager tells me I have CMW and TWRP installed... well... after I Flashed a complete prerooted firmware (1,13GB) I thought those installations would have gone away.
I could swear that if I enter recovery at this point I would have the basic android recovery.
Is it possible that somehow, there's something confusing ROM Manager?
Or is there something left from custom recoveries somewhere?
Click to expand...
Click to collapse
yep it's probably rom manager, look through forum for the odin image and go that way instead.
m
moonbutt74 said:
yep it's probably rom manager, look through forum for the odin image and go that way instead.
m
Click to expand...
Click to collapse
Yes... all the recoveries I installed were through Odin... all with the same result.
It is really strange, never happened before and I do flash firmwares since android 2.1
First time on a tablet, though.
I used all the versions available here: http://forum.xda-developers.com/showthread.php?t=2755532
For my model, ofc... T210 (WIFI only)
ahh hmmm
RockasKane said:
Yes... all the recoveries I installed were through Odin... all with the same result.
It is really strange, never happened before and I do flash firmwares since android 2.1
First time on a tablet, though.
I used all the versions available here: http://forum.xda-developers.com/showthread.php?t=2755532
For my model, ofc... T210 (WIFI only)
Click to expand...
Click to collapse
okay let go of philz snazzy recovery for now try this firzt
current cwm odin tar.md5
http://www.androidfilehost.com/?fid=23501681358545643
moonbutt74 said:
okay let go of philz snazzy recovery for now try this firzt
current cwm odin tar.md5
http://www.androidfilehost.com/?fid=23501681358545643
Click to expand...
Click to collapse
ok... tonight I'll take the risk again... but for the record I already tried that one too.
And even restoring backups or installing new roms from recovery... still looped.
okay
RockasKane said:
ok... tonight I'll take the risk again... but for the record I already tried that one too.
And even restoring backups or installing new roms from recovery... still looped.
Click to expand...
Click to collapse
i understand your frustration.
i would then suggest running your tab stock/rooted with stock recovery until, hear me out,
until you have done a mad amount of reading and learning for the following reason;
you are like looking at doing some HEAVY terminal work to diagnose/identify the full problem
and then MORE terminal work to fix it.
you will need to know for this problem how to use the dd command with respect to directly writing boot/kernel/recovery
images to appropriate mmcblk.
you will need to know what an mmcblk is and what mmcblk corresponds to recovery and boot.
you will need to learn how to disassemble debug and reconstruct boot/kernel/recovery images
you will need to learn to navigate your file system and mount,umount,remount,cd,cp,chmod,chown etc.
or if you reflash normal stock you can take it back to store and get a replacement.
m
moonbutt74 said:
i understand your frustration.
i would then suggest running your tab stock/rooted with stock recovery until, hear me out,
until you have done a mad amount of reading and learning for the following reason;
you are like looking at doing some HEAVY terminal work to diagnose/identify the full problem
and then MORE terminal work to fix it.
you will need to know for this problem how to use the dd command with respect to directly writing boot/kernel/recovery
images to appropriate mmcblk.
you will need to know what an mmcblk is and what mmcblk corresponds to recovery and boot.
you will need to learn how to disassemble debug and reconstruct boot/kernel/recovery images
you will need to learn to navigate your file system and mount,umount,remount,cd,cp,chmod,chown etc.
or if you reflash normal stock you can take it back to store and get a replacement.
m
Click to expand...
Click to collapse
In that case It's better if I wait for my vacations
I guess in the mean time I'll buy me a new and faster tablet... and this will serve the purpose of learning
moonbutt74 said:
i understand your frustration.
i would then suggest running your tab stock/rooted with stock recovery until, hear me out,
until you have done a mad amount of reading and learning for the following reason;
you are like looking at doing some HEAVY terminal work to diagnose/identify the full problem
and then MORE terminal work to fix it.
you will need to know for this problem how to use the dd command with respect to directly writing boot/kernel/recovery
images to appropriate mmcblk.
you will need to know what an mmcblk is and what mmcblk corresponds to recovery and boot.
you will need to learn how to disassemble debug and reconstruct boot/kernel/recovery images
you will need to learn to navigate your file system and mount,umount,remount,cd,cp,chmod,chown etc.
or if you reflash normal stock you can take it back to store and get a replacement.
m
Click to expand...
Click to collapse
Thank you so much for your patience and time :highfive:
Why do you try The The Rommanager?
1. Before you Start to flash a recovery and root your device, you must read and read and not try The first post.
So your are now that The Rommanager are not work in our device.
Every time you can read here post were some one try to root by Chinise app and other, after this they have Boot loops and Brick there device.
bierma32 said:
Why do you try The The Rommanager?
1. Before you Start to flash a recovery and root your device, you must read and read and not try The first post.
So your are now that The Rommanager are not work in our device.
Every time you can read here post were some one try to root by Chinise app and other, after this they have Boot loops and Brick there device.
Click to expand...
Click to collapse
If you read my posts with attention, you'll see I've used odin.
I just used rom manager to check out what was going on.
As I also said, I am a nob when it comes to android but not regarding firmwares... as you can see on my profile, I've been around for some years and not even 40 posts... I kinda read alot and speak few times [emoji4]
I am quite sure I've done everything as I usually do, but this time something has gone wrong... it happens [emoji4]
It is strange and not usuall. When I'm on vacations I'll spend sometime working this thing out... maybe by then kit kat is stable for this device [emoji3]
Edit: typos
Ok... I have a new info.
I used odin to flash prerooted firmware but it looks like recovery "damages" my data partition.
So.. the only way to go around this is to use the option "nand erase all" and install prerooted... then it won't boot even if it plays the booting sound.
So... I have to install through odin TWRP and then fix the data partition... and the only way to do so is to change file system to ext3 and then back to ext4.
At this point I am able to install a rom through TWRP and I can even install kernel and theme but only if i batch the zips...
All boots fine but, if for some reason I enter recovery again... all gets screwed up and i must repeat all steps
Is this helpfull to find a fix for this?
@Tomsgt, @gr8nole, @ketut.kumajaya, anyone?
FYI and future reference... looks like that if I just turn off the phone and enter recovery using the home+vol up+power it works fine.
It's a relieve to me but on the other hand makes me really curious... why?
huh
RockasKane said:
FYI and future reference... looks like that if I just turn off the phone and enter recovery using the home+vol up+power it works fine.
It's a relieve to me but on the other hand makes me really curious... why?
Click to expand...
Click to collapse
the only thing i can think of is to now update/install latest supersu from chainfire [2.00] i believe.
i have had goofy root fails where i couldn't manage reboot into recovery and su update/reinstall
fixed it, but honestly jf your good for now then don't wake the dragon.
m
moonbutt74 said:
the only thing i can think of is to now update/install latest supersu from chainfire [2.00] i believe.
i have had goofy root fails where i couldn't manage reboot into recovery and su update/reinstall
fixed it, but honestly jf your good for now then don't wake the dragon.
m
Click to expand...
Click to collapse
No I won't
I'll leave it as it is until I'm on vacations with the free time to just risk some changes again
Ok, try following:
First, flash the Stock firmware again, and root the device. Then install "Flashify (for root users)". (download it on the google play store)
Download the latest PhilZ kernel.
Now open the downloaded zip and unpack the zip. You need the file "recovery.img"
Now open the app flashify and hit "Recovery image" and choose the file.
Then flash the file.
Then reboot and try it.
Hope I can help you.
RockasKane said:
Ok... I have a new info.
I used odin to flash prerooted firmware but it looks like recovery "damages" my data partition.
So.. the only way to go around this is to use the option "nand erase all" and install prerooted... then it won't boot even if it plays the booting sound.
So... I have to install through odin TWRP and then fix the data partition... and the only way to do so is to change file system to ext3 and then back to ext4.
At this point I am able to install a rom through TWRP and I can even install kernel and theme but only if i batch the zips...
All boots fine but, if for some reason I enter recovery again... all gets screwed up and i must repeat all steps
Is this helpfull to find a fix for this?
@Tomsgt, @gr8nole, @ketut.kumajaya, anyone?
Click to expand...
Click to collapse
How did you change the file system to ext3 and to ext4 ?
Not sure if it would be relevant or not (not had this tab that long and i'll be reading up a lot ) but would or could there be differences in partition info between GSM and WI-FI ROM's? I myself would double check just in case.
Also with ROM Managers and Odin, do they use the same flashing program on the Tablet/Handsets? I only ask as coming from htc there are two variations of what seems the same program to flash a ROM/Recovery etc depending on how the image/zip/etc are presented through Software update (OTA) or .zip or through PC update dictates which is used to install.
This is why I've steered clear of ROM Managers for the most part, either doesn't 100% suit me or I've had bad ROM flashes so I've stuck with going through Recovery or PC updates.
Sent from my SM-T210