yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Q&A, Help & Troubleshooting] yoda_la:
I have severe problems when reflashing my Galaxy Tab GT-P1000 (via recovery) to CM 10.1 nightly. Before that, I ran 9.1.0-p1 for quite a while.

What I do:

Reboot to recovery (CWM-based Recovery v6.0.1.2)

wipe data/factory reset

wipe cache partition

install zip from sdcard, e.g. cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip

It tells me: "This ROM uses an incompatible partition layout. Your /data will be wiped upon installation. Run this update.zip again to confirm install" and "assert failed: run_program("/tmp/updater.sh") == 0".

I re-run the zip as told.

It reboots to a seemingly updated CWM-based Recovery v6.0.3.2

And now, all kinds of errors occur. First time I tried, flashing seemingly went through (despite showing some ot the CWM error messages mentioned below). After rebooting, I ended up with a weird looking CM10 bootup animation (didn't fit to screen) animating forever with no further (visible) progress. I waited for more than 10 minutes and tried re-booting several times, but it hung there forever. I couldn't connect via adb.

After some tries, the error has changed. Now it won't come to starting CM10 at all, but CWM ends up in a loop saying "Root access is missing. Root device?". If I choose "Yes", it reboots to end up in the same question over and over again.

I tried a lot of nightlies, all showing a varying selection of the errors described above and none leading to a somehow booting CM10.1. I tried some of the official nightlies from get.cm (e.g. cm-10.1-20130515-NIGHTLY-p1.zip), cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip from goo.im/devs/cdesai/cm as well as the OpenPDroid taste announced by alroger (cm-10.1-20130514-UNOFFICIAL-p1.zip).

They all seem to use the same new CWM, which gives me collection of error messages, all seemingly connected to partitioning:

Usually, I see a varying number of erros in /cache/recovery, e.g. that it can't mount and/or open /cache/recovery/command, as well as .../log, .../last_log and .../last_install and that it can't open the same files.

Sometimes, I see "E:unknown volume for path []. E: Can't mount"

Sometimes, when trying to wipe, I get informed that make_extf4fs failed on mmcblk0p3

Normally, I'd say that I'm either making a fundamental error in the process or my hardware is somehow badly broken. BUT what puzzles me is that I can go back to CM 9.1 at any time and flash it as often as I want - it always works and CM9 is starting up correctly.

So, I more suspect that my partitioning is somehow setup in a way that CWM v6.0.3.2 or the setup scripts from update.zip can't handle cleanly.

Any suggestions / ideas? Please let me know if there are any logs which could help in narrowing things down! I should be able to operate a Linux shell, so don't hesitate to suggest things I could try manually. (I can certainly access "adb shell" in the recovery - but please note that I didn't manage to connect with adb during the CM10 boot hang, so I can't provide logcat from that state, sorry...)
[Galaxy Tab Q&A, Help & Troubleshooting] mike_disturbed:
[youtube]JmvCpR45LKA[/youtube]

:thumbup::thumbup:

And restock..

I recommend overcome method..

Search for it..or wait for priyana come here and post "click at my signature" :p

Then press the thanks button..

When you on stock..

Install the overcome kernal..

Flash cm10..3x

First..to get cwm..

Second..to change partition layout..

Third..to install cm10..

Then flash the gapss..

Reboot..

-----------------------------------

(҂`☐´)︻╦̵̵̿╤── .:System:.

-----------------------------------
[Galaxy Tab Q&A, Help & Troubleshooting] yoda_la:
No interest in solving the problem in CM10?

Wow, first of all thx for the rapid answer! And thank you for the hint, I can certainly try that.

However, my initial intention was not only to have the problem solved for my tablet but I tried hard to do a qualified bugreport so that the situation can be correctly handled in the cm10.1 nightlies. I at least assume that an update from a clean CM 9.1 to CM10.1 should be a supported update path, no? As said, I returned to a clean CM 9.1 several times and re-tried the update from there.

So I assumed that the CM10 developers would be interested in my feedback and analyzing the error. Unfortunately, however, I'm not allowed to post that to the right thread yet, so I chose the Q&A channel.

If you don't think the developers are interested in the bug report, just let me know and I'll happily try your suggestion. Otherwise, I'd refrain from it now to not disturb the test case yet...
[Galaxy Tab Q&A, Help & Troubleshooting] mike_disturbed:
I'm not really sure about this..but cm9, cm9.1 and cm10 , cm10.1..

They have different partition layout..and the rom zip..can change partition layout from gb to cm layout..something about mtd layout or something..lol:D

I'm not quite sure myself since i still using gb base rom..:p

Just help in general and q&a..then you can post at dev section..that's the rule..and it apply to everyone..even the dev..

Yeah the dev would definitely interested with that..but..i think that cm10 is been here long enough..and someone would likely brings that up already..but if you still think that it worth a shot..try pm'ing the dev..may take a while for the reply..but I'm sure the dev would love to get some helping hand..or just complete the 10 post..you have done 2 post here already..8 more to go..

-----------------------------------

(҂`☐´)︻╦̵̵̿╤── .:System:.

-----------------------------------
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Only cm Rom from last year April onwards use new partition scheme.

If yours was old one, better restock.

Like mike said, check my signature.
[Galaxy Tab Q&A, Help & Troubleshooting] mtbsoft.:
What can I say... that is totally f****** but damn it... it flamin' well works! I can't even guess how you came up with that sequence but THANK YOU! This has been driving me nuts.
[Galaxy Tab Q&A, Help & Troubleshooting] yoda_la:
Stil no luck...

Ok, tried all that several times, but it still doesn't work. "Restocking" is great as it brought back my /efs partition which has somehow been damaged during my first update tries, so thank you again!

However, my tab still won't boot with CM10, even after "restocking" successfully two times and trying different CM10 nightlies (the current cm-10.1-20130604-NIGHTLY-p1.zip as well as cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip as I found specific success reports for that one on the forum). I also tried flashing CM10 3 times in a row as you told.

I always end up with a boot hang and the weird distorted boot animation shown forever. In recovery, I still see errors when accessing the

/cache partition. I've no idea whether this is the root cause of my boot hangs or if this is expected behaviour in CM10 nightlies, but when I try to wipe cache, I get:

E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3

I also checked with "adb shell" in /proc/partitions and found that there's simply no mmcblk0p3 found by the kernel:

-> reboot to recovery
$ adb shell
~ # cat /proc/partitions
major minor #blocks name

31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 443904 mtdblock2
31 3 22528 mtdblock3
31 4 12800 mtdblock4
31 5 11264 mtdblock5
179 0 15552512 mmcblk0
179 1 13586400 mmcblk0p1
179 2 1966080 mmcblk0p2
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15339520 mmcblk1
179 25 15335424 mmcblk1p1

dmesg show no suspicious entries during mmc detection, it looks like mmcblk0 simply only has two partitions. So can someone tell whether I should have a mmcblk0p3 partition or if my fstab is somehow broken? Any idea how to narrow this down further?
[Galaxy Tab Q&A, Help & Troubleshooting] mtbsoft.:
How are you restocking? I used the Overcome method and files, going back to GB Stock Safe V5. Then I put the Overcome kernel 4.0.0 on, finally doing the CM10.1 x 3 and GApps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Schwooby:
I'm using ktoonsez AOKP rom currently, but I'd like to try Cyan.

I'm also getting an error when mounting my internal sdcard. It reads: E: cannot mount /sdcard

I guess I'll have to go home and flash a stock rom and start over. Ideas/comments?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Yeah, it's about as stable as an aosp Rom can get. Last I checked they had just released RC2 for the d2att and other variants.

A word of caution. If you want to flash the rc, you will need to be on the jelly bean bootloader and LK3 modem. If your not, you will probably get some kind of error when trying to flash and it won't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The LPT:
I believe the issue started happening after the release of RC2. Since I am running RC2 with UMLJ1 modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
It's not an issue because it was purposely added. CyanogenMod wants your device to have the latest bootloader in the most recent stock update to your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Schwooby:
Well hell. Idk what tondo. My phone becomes unresponsive during calls and I have to restart it to terminate the call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I just know what CyanogenMod put on G+ :
[One (M7) Android Development] Phil3759:
Main thread + features + install instructions + dev support

http://xdaforums.com/showthread.php?t=2201860

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

To take a screen shot, just slide left

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

XDA:DevDB Information

[m7][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the HTC One

Contributors

Phil3759

Version Information

Status: Stable

Created 2014-06-02

Last Updated 2014-06-02
[One (M7) Android Development] Blindie:
its looks like that the recovery have the wrong resolution
[One (M7) Android Development] dirtbikerr450:
Thanks
[One (M7) Android Development] Phil3759:
description, pic?
[One (M7) Android Development] migascalp:
Big problems with AROMA and HTC One :(

thank you for porting your recovery :)
[One (M7) Android Development] Phil3759:
This can be sorted out in a second time, using a stock kernel/ramdisk fixed this issue for all phones affected till now

However, I need to have first a few feedback about how it is now and if there are issues

After that, we sort out bugs
[One (M7) Android Development] Blindie:
sorry, cant make pics.

The background ist green and pink and the layout ist double(i see the options on the left änd right side), sorry, cant discribe better, my english is bad :(
[One (M7) Android Development] migascalp:
double vertical display

adb don't work. Wrong driver?
[One (M7) Android Development] Phil3759:
I used last CM source

They are modifying it every few mn. I will do a sync an release a new version

If it fails, I will repack around stock ramdisk

Thank you for the report
[One (M7) Android Development] Nekromantik:
will this feature ability to mount /data/media as a USB disk drive?
[One (M7) Android Development] Phil3759:
that you cannot
[One (M7) Android Development] Flyhalf205:
Hey. Check out my git for the m7 and the correct configs there. Use the twrp kernel in the thread linked to my goo. Its zarboz kernel. Better for aroma. Hope this helps.

Edit: someone took out the recovery config out of the m7. I got to see if I can get it back in. I'll be updating the official recovery with zarboz kernel soon.
[One (M7) Android Development] Phil3759:
Thanks

I will wait for you to update your device repo to release next update

The display issue is strange as I compiled using stock cm-10.1 tree
[One (M7) Android Development] Flyhalf205:
Just updated my device tree with his kernel.

The discolor might be because you need to add TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888" and maybe RECOVERY_GRAPHICS_USE_LINELENGTH := true but hopefully you don't. Had the exact same problem with TWRP.
[One (M7) Android Development] Phil3759:
Thanks for the support (keep in mind I do not own the device or any HTC phone)

Except the device tree with precompiled kernel, do I need some ramdisk post compile ramdisk changes for your kernel?
[One (M7) Android Development] Flyhalf205:
Not to my knowledge you shouldn't need any. Just make sure you compile...

BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31

BOARD_KERNEL_BASE := 0x80600000

BOARD_KERNEL_PAGESIZE := 2048

BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x01400000​

Which you already have that since previous post shows a photo of your recovery :)
[One (M7) Android Development] Phil3759:
Yes, those are already defined in BoardConfigCommon.mk

Thank you for the support (out of the daily limit for :good:)

Will try to compile it tomorrow

Just one question: stock CWM has also broken graphics for your phone? Still wondering why my compiled one went broken if stock cwm is ok for your device
[One (M7) Android Development] Flyhalf205:
No. Never has broken graphics. Only TWRP has and has been fixed with those two lines. Not sure why yours is.
[One (M7) Android Development] Phil3759:
I will sync the repo, who knows

It could be the png is too big as a background, but strange anyway
[One (M7) Android Development] Phil3759:
New update, using Flyhalf205 device tree

http://d-h.st/users/philz_touch/?fld_id=16699#files

Let me know if graphics are fixed and about eventual other bugs
[Networking] rp56:
I have been told the I-wireless uses sprint and T-Mobile towers for there wireless service I'm not completely sure that this is correct.I live in western part of u.s.a. and I have alot of saved up airtime minutes,texts,etc for I-wireless and I'm just trying to figure out if I can use my I-wireless service on my T-Mobile Gs4.If anyone knows if this is possible please let me know.any information would be greatly appreciated. :cool:
[Networking] MrObvious:
It depends. Here in Kansas it's Sprint. In Iowa it's T-Mobile. You'd have to look at the phones they sell in your area to get an idea.
[Networking] electro`:
i-wireless is a Kroger Sprint company.

iWireless/i wireless is a T-Mobile affiliated company.

i-wireless uses CDMA technology.

iWireless uses GSM technology.

If you want to use iWireless in the western part of the US, you would be roaming on T-Mobile with no charge because you're outside of the iWireless main service area which is all of Iowa and parts of nearby states.

You could not use your T-Mobile Galaxy S4 on i-wireless, but you could on iWireless.
[Networking] rp56:
See I have a cheap I-wireless phone that cdma and I dont use the phone but I get free time so I have 1500 minutes plus $300.00 cash credit on it I was just trying to think of a way to use up all that money in time.
[Networking] MrObvious:
Trade your T-Mobile SGS4 for a Sprint one?
[Networking] Greg1964:
Sprint sucks...

Sent from my SGH-M919
[Sprint Samsung Galaxy S III] Lobster$:
When I am on the Network Mode LTE/CDMA/EVDO

AND

on 4g, my data works as intended, download and upload works. However, if I am still on LTE and only have 3g service...I get ZERO upload data. This is why MMS doesn't send and other things (Instagram, Snapchat).

To get these things to send, I got to set my Network Mode to just CDMA/EVDO Auto. The downside to this is that 4g will never get picked up when available.

If anybody knows how to fix this so that my data uploads when I'm 3g but on the LTE/CDMA/Evdo network mode that would be great!!!!

I am running the Carbon 5/10 nightly but I believe this is a common AOSP issue.

Thanks!!!
[Sprint Samsung Galaxy S III] nicksmizzle:
shut up:D:cowboy::angel::o:rolleyes::cool::eek::cowboy::D:crying::p:cyclops::good::highfive::fingers-crossed:
[Sprint Samsung Galaxy S III] Lobster$:
Bump lawl.
[Sprint Samsung Galaxy S III] Lobster$:
Nobody? :(
[Sprint Samsung Galaxy S III] LuigiBull23:
Which modem are you on?

Once you can identify the baseband version try different modems besides your current one and see if it makes any difference for you. I'm sorry it took so long for anyone to respond to this..
[Sprint Samsung Galaxy S III] Lobster$:
No worries....

And I'm on MD4, but I have also tried MC3, MB1, and LJ7, no luck.
[Sprint Samsung Galaxy S III] CNexus:
Try forcing hands free activation (while connected to wifi)

##72786#
[Sprint Samsung Galaxy S III] Lobster$:
Even though TW data works fine and I only having issues on AOSP?

Should I nand aosp, restore tw and force activation, and restore my aosp?
[Sprint Samsung Galaxy S III] CNexus:
Yes, try that

But first, are you sure it's not just issues with your AOSP rom?
[Sprint Samsung Galaxy S III] Lobster$:
Nope not just the rom, it happens on carbon/deviant/liquid and even rootbox AOKP.
[Sprint Samsung Galaxy S III] Lobster$:
Tried this hands free method. Will post results when I have 3g at work tomorrow!
[Sprint Samsung Galaxy S III] CNexus:
Cool, let us know how it works out
[Sprint Samsung Galaxy S III] Lobster$:
Unfortunately, this did not work. I'm wondering if this is an APN issue, although I don't really know what I'm talking about.

As you can see from the screenies...3g upload speed is non-existant when on the LTE network mode.

Edit: 1st screenie is on LTE. The 2nd is on CDMA/Evdo Auto.
[Sprint Samsung Galaxy S III] Ragnar:
What are you talking about 3g on lte network mode. 3g is 3g. LTE is 4g two completely different things. If you have LTE in your area your device would connect and say 4g. If not it will connect to only 3g. If you are on a stock rom you might only be connected to 1x speed but your phone will display 3g. Only custom roms will break it down to actually show if you are on 1x connection.

If you are on a custom rom then that may be your problem if you do have lte in your area, even more so if you are on aosp type rom. They have issues handling the exchange between 4g and 3g. I pretty much bet that's what it is an rom issue handling the exchange.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Lobster$:
Under settings - mobile networks - network modes. The LTE mode is selected. In areas where 4g is not available and only 3g is...upload data does not work. However, if just the CDMA/EVDO auto is selected under mobile networks (LTE NOT SELECTED) data upload works fine.
[Sprint Samsung Galaxy S III] Ragnar:
What Rom are you on? Never mind, just read your on Carbon. This is a common issue with aosp roms. You should leave it always in cdma/lte/evdo never change from there. Set it to that and reboot. Use the toggle for 4g to turn 4g on or off.

But beltway to assure yourself that it is a rom issue is create a nandroid, then flash a TW rom and test the handling between 3g and 4g, and your data.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Lobster$:
I am on LiquidSmooth v2.4 official. However this happens on the past few AOSP roms i have tried.

Back to what you said, maybe the handoff from 4g to 3g is just not working with data upload properly.
[Sprint Samsung Galaxy S III] Lobster$:
Wow I must say thanks for the toggle idea. Beats the heck out of going into mobile settings and switching modes every time I want to send an MMS.
[Sprint Samsung Galaxy S III] Ragnar:
Correct, just do yourself a favor in order to eliminate a hardware issue. Make the nandroid of your current set up. Clean flash a TW rom anyone and check the handoffs if it works property it's a rom issue if you still have problems it could be the device itself. It takes less than 5 minutes to test you don't have to set everything up just flash log in with Google account and check.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Lobster$:
Yep, testing TW was one of the first things I did when discovering this issue.

, I'm assuming there is no fix for these handoff data issues?
[Sprint Samsung Galaxy S III] Ragnar:
Not really, the aosp roms for this device are all built on leaks or source from a different device. That is, not built from source for the Sprint GS3. Some Roms work really good others don't, but nothing beats the TW handling of it on our device. On the other hand I also have a Gnex which is pure aosp and it works awesome but there is true source for that device.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Lobster$:
Thanks for the help!
[HTC Amaze 4G] Kalout:
My Amaze was/is running fine on Gingerbread, rooted Bulletproof v2. Now I'm trying multiple ROMs, mostly Cyanogen Mod 10.1, and they all have the same problem. After installing via 4EXT RC9 (I'm S-On) the device boots into the Rom, lasts 5-30 seconds (can't get past lock screen and/or setup screen), freezes, then restarts. How can I fix this?

*Nevermind* ICS RUU. Got it. Thank you.
[Xperia Arc Q&A, Help & Troubleshooting] chabol:
Hi guys,

I've read a lot of threads in the forum and I didn't found any where my problem was solved so I go.

My Arc s is bricked and I'm trying to unbrick it, but flashtools gives it:

16/029/2013 21:29:03 - INFO - Device connected in flash mode

16/029/2013 21:29:43 - INFO - Device disconnected

16/030/2013 21:30:11 - INFO - Device connected in flash mode

16/030/2013 21:30:31 - INFO - Please connect your device into flashmode.

16/030/2013 21:30:34 - INFO - Opening device for R/W

16/030/2013 21:30:34 - INFO - Reading device information

16/030/2013 21:30:51 - INFO - Unable to read from phone after having opened it.

16/030/2013 21:30:51 - INFO - trying to continue anyway

16/030/2013 21:30:51 - INFO - Start Flashing

16/030/2013 21:30:51 - INFO - Processing loader

16/030/2013 21:30:51 - INFO - Checking header

16/030/2013 21:30:51 - INFO - Ending flash session

16/030/2013 21:30:51 - ERROR - Error in processHeader : 2 : El sistema no puede encontrar el archivo especificado.

16/030/2013 21:30:51 - ERROR - Error flashing. Aborted

Could someone tell me why my phone can be read please?

Thx:crying:
[Xperia Arc Q&A, Help & Troubleshooting] TheHaso:
uhh, translate the error mesaage to english please. Im on my phone atm
[Xperia Arc Q&A, Help & Troubleshooting] TraxXrAt:
Connect your phone in fastboot mode. Push the Menu button and connecte the usb cable maintaining the menu button. And the led should turn blue. And here you go, fastboot mode flash.
[Xperia Arc Q&A, Help & Troubleshooting] Someguyfromhell:
Unbricking cannot be done in fastboot mode.

To OP: redownload the file, seems like the FTF is corrupted.

Sent from LT18i with custom firmware by myself.
[Xperia Arc Q&A, Help & Troubleshooting] Tilman:
Download the whole firmware, connect your device on flashmode, by keeping on pressed the back button and connect it, then flash the .ftf file.
[Xperia Arc Q&A, Help & Troubleshooting] Tilman:
I think that you've installed adb drivers only for arc/s, now that you've flashed Xperia pro firmware, so you need to install drivers for that and try again and report back.
[MDA II, XDA II, 2060 General] Kurupt10n:
Hi all,

I'm new to everything here and just had a few newbie questions.

I have an O2 Xda 2 but i want to remove everything O2 related from the phone. I am currently using a TIM sim-card but don't really want everything TIM related to be installed either. Is it possible to just have a default phone that simply uses the TIM part of things for calls n messages only?

Ringtones..... What file types are acceptable for use? And what can i use to convert mp3's to a decent length and size for use as such.

More if i think of them.

Thanks in advance