yashsingh1/xdaforums huggingface dataset:
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Morice69:
Hi, i first backup

Then format all

Then put old aos file in tablette

It will update from o.o.o to 3.x.x
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] alt36:
When i do that, it makes me "failed code 221". All old firmware have the same issue.

when i put the honeycomb rooted firmware(3.2.80 or any 3.xxx) it boot looping. But when i put ics rooted firmware(ics@blue or clean_slim&fast) everything works fine. I don't no what i do wrong and why honeycomb doesn't work.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] 55mls:
The way the older Honeycomb and later ICS roote firmware works is confusing and complicated.

In general, due to the differences between Honeycomb and any later firmware you end up having to do an Android Reset somewhere along the line. It's been a while, but I believe to go back to Honeycomb you need to do something like this:

Have SDE installed, go into Recovery and do a full reformat, then install whatever the last 'official" Archos firmware your device had.

Then, copy the 'rooted' Honeycomb firmware to the device (depends, but could be a squahfs or .ext file). Then shut down.

Restart into Recovery/SDE and bounce around to do the following:

Format => Reset Android

Remove Android Kernel

Flash the correct kernel files for the rooted Honeycomb firmware you had copied over earlier.

Been a while (since I see no logical reason to go back to Honeycomb on my end), but maybe the Reset Android and Remove Android Kernel need to be done in reverse order.

Also, one of the kernel files has to be renamed to work right (.gz has to be .lzo).

In other words, it IS possible to go back to a 'rooted' Honeycomb version, but I honestly don't know why anyone would really want to. The ICS 4.0.xx 'rooted' firmware is actually easier to install (don't need to do weird things like Reset or rename file names usually except for certain "custom" ROMS).

---------- Post added at 04:18 AM ---------- Previous post was at 04:07 AM ----------

I have no idea what you are trying to say because you CAN NOT install any older 'official' Archos firmware below whatever you had last installed.

In other words, if the last 'official' Archos firmware you had installed was 3.2.80 you can not install 3.2.79. If the last you had installed was 4.0.7 you can not install 3.2.80. If the last you had installed was 4.0.26 you can not install 4.0.7.

Except for one certain situation during the faulty 4.0.x ICS firmware releases where Archos actually did provide a certain combination of 4.0.x (test) firmware and a special 3.2.80 firmware release you can not ever install any previous (or older) stock 'official' Archos firmware. Only way to go back ends up having to install SDE and 'rooted' versions.

---------- Post added at 04:32 AM ---------- Previous post was at 04:18 AM ----------

Hate to say it,but the problems you seem to keep having are totally due to the way you are doing things! Results depend on if you actually did a full clean install of things on the tablet, which OS you are running on your computer, and whether or not you turned off USB Debugging on the tablet, disconnected the USB cable and did and total shut down and re-start of BOTH the tablet and computer.

Not to mention that trying to go back to 3.2.80 is actually far more complicated and confusing... not to mention bouncing around between different firmwares totally confusing all kinds of things... well... all I can say is that you are creating your own problems that have NOTHING to do with any of the various firmware ROM's if installed correctly.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] pthang:
Another question

can i downgrade from 4.0.28 back to 4.0.7?
[AT&T Samsung Galaxy Note II] suilobo:
I'm a android noob. AT&T Galaxy note 2 is my first android phone. Running 4.1.2

I was getting superb battery life before rooting. Easily 6-7 hours on screen time with close to 15 hours of standby, with everything turned on. Brand new phone used it for a week.

Decided to root so i can use apps like gl2sd. But after rooting using All-in-one tool kit, I'm getting horrible battery life. My top part of the phone feels warm to the touch all the time now, with battery draining 10% every hour. All I installed was twrp custom recovery and supersu root. Did not install any custom roms.

Android system seems to be the biggest drainer. I researched and tried all the suggestions, factory resetting, disabling all the AT&T bloatware, even disabling s voice, etc.

I even put my phone in airplane mode and it still drains at the 10% per hour rate.

Can someone guide me in the correct direction on what could've gone wrong.

Thanks in advance!
[AT&T Samsung Galaxy Note II] mrevankyle:
Just the act of rooting will do absolutely nothing to your battery life. It is muuuch more likely that it was an app you installed after rooting that is doing the damage or keeping it wakelocked
[AT&T Samsung Galaxy Note II] suilobo:
All I installed and used was titanium backup, and gl2sd as root apps. Nothing else really.

What is wakelocked? How do I get it out of it?

Thanks!
[AT&T Samsung Galaxy Note II] spawn50ak49:
Install GSam battery monitor it will show you what is wake locking your phone. A simplistic answer to what wake lock is is background application's or processes that are using CPU time. not letting the phone deep sleep. Example gmail syncing while the screen is off. You get the notification but the screen doesn't turn on.
[AT&T Samsung Galaxy Note II] d.cortez:
another option: uninstall gl2sd to see if that's causing the drain. are there other apps you've restored via Titanium Backup?
[AT&T Samsung Galaxy Note II] suilobo:
I just installed GSam battery monitor. Will start checking with that.

What do I do when I find the culprit. I have a feeling it has something to do with is android system thing. It's showing it taking that most battery. More than my screen! Is there anyway to stop it? It was fine before I rooted it.

Thanks In advanced!
[AT&T Samsung Galaxy Note II] suilobo:
I uninstalled gl2sd already. I didn't even bother putting titanium back on after the factory reset. I did not restore any apps from titanium.

What is the difference btw the factory reset in the settings menu and factory reset in the twrp recovery? Will it be better if I did a reset from the twrp recovery? I did the reset only from the settings menu so far.

Thanks again!
[AT&T Samsung Galaxy Note II] Astom22:
Have you fully charged it since rooting? Mine did that at first, but once I gave it to full charge, it went away. Just a thought.

Sent using Galaxy Note 2 w/ CleanROM 4.0.5
[AT&T Samsung Galaxy Note II] suilobo:
Thanks for the idea, but yeah, I have been constantly charging this. I had it run down to 12% last night before charging it back up.

Crazy thing is even in airplane mode, the battery continues to drain.
[AT&T Samsung Galaxy Note II] suilobo:
I have GSam installed. Top one on the list is Android System. 32.1% battery consumed. viewing number of times waking device, 73 times in 3 hours on battery. CPU minutes used is 6mins 18s.

Kernel (Android system) is number 2 on the list with 18.9% battery consumed. CPU minutes is 3m 42s.

What can be done to fix this?
[AT&T Samsung Galaxy Note II] mar.ioo:
Let it turn off by it self. Then charge back to 100%. Battery cycles, open Settings>Battery and see whats causing you to lose that much battery! :)
[AT&T Samsung Galaxy Note II] suilobo:
After installing GSam, I checked the android system, it is showing 115 wakelock in 30 minutes time. How do I fix this?
[AT&T Samsung Galaxy Note II] spawn50ak49:
Here's one idea. Save all the things you want to save from internal storage to your PC. Make sure you have a full charge. Reboot into twrp. Go to wipe menu and select factory reset, system, cash, delvic cash and data. That way you have a very clean slate.

Install your ROM. Boot into system and let it sit for 10 min. Set up your Google account only. Download and install gsam battery monitor and a screen shot app. Use your phone with the base system until battery is like around 10% charge.

Go to the gsam battery app and check apps that are using battery. Select the one that is using the most. Another screen should show up and should have a list of processes that are using the battery. Take a screen shot and post it. In fact take a screen shot of the graph and the app list. I'm interested in what it shows :)
[AT&T Samsung Galaxy Note II] suilobo:
I just in fact tried wiping my phone. But I didn't know I needed full battery. My phone was stuck at the Samsung logo. I pulled the battery and now won't turn back on. When I plug in the charger, all I get is the gray empty battery picture with a circle in the middle.

Any suggestions to get it back? Can't go into download mode or recovery mode. Here is a picture of it.

Thanks!

View attachment 1688306
[AT&T Samsung Galaxy Note II] GR8CDNPumpkin:
If the battery was exhausted completely it will do this. Let it charge for a while.
[AT&T Samsung Galaxy Note II] suilobo:
Ic.. Thxs. I will try to let it charge overnight. Hope it comes back!

Thanks!
[AT&T Samsung Galaxy Note II] suilobo:
Charged the phone overnight. It is still doing the same, will not boot up.

Any experts can give me some tips on what to do?

Thanks!
[AT&T Samsung Galaxy Note II] spawn50ak49:
Can you get into recovery? Hold down volume up, home key and power. If you can get into recovery you can flash your ROM. If no recovery can you boot into download mode. Volume down, home key and power. If you can get to download mode you can reinstall recovery with odine. Follow the rooting guide to the letter.
[AT&T Samsung Galaxy Note II] suilobo:
I couldn't get into anything. What I did was bring it to att store and acted stupid. They gave me a brand new phone. Lol. Lucky me.

No more rooting for me. Too much hassle. Lol

Thanks to all who tried to help me!

Greatly appreciate this great community!
[AT&T Samsung Galaxy Note II] livingaboard:
The rooting is fine. I don't know about this all in one kit or chain fire rooting...blah blah blah. I can do a little on my phone and I try to keep it simple. I used odin on Windows to install one tar file on my phone. Phone was rooted and superuser installed at the same time. Then I went to goo manager in the Google store and installed that. I used that to install TWRP. I then went into recovery and flashed my rom, basically.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] abhijitro:
Guys plz tell... which is the best download manager to download huge size files....
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] menewtoroot:
Nd now ..

Do i see same post again.??:eek::sly:

What the hell do u want....

** rooting is new for me,

nd i am a noob to root....:D:D**
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
There's no such thing as a best rom app or toasted sandwich

Try them for yourself

Thread reported
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Jonny:
Thread closed, read 1 post above to find why.
[Nexus 7 Q&A, Help & Troubleshooting] duckredbeard:
Too many spontaneous reboots, wife not happy with it. Wiping, resetting any taking it back today. Never even rooted it. Shame, I had my hopes up.

You can't know your limits until you exceed them.
[Nexus 7 Q&A, Help & Troubleshooting] icase81:
There must be something hardware wise wrong with it if its rebooting spontaneously. I haven't had a single spontaneous reboot on mine since purchase 3 months ago and I've done plenty of hacking around
[Nexus 7 Q&A, Help & Troubleshooting] tvdang7:
Mine locks up occasionally and reboots too. Mostly because of Netflix or hulu.
[Nexus 7 Q&A, Help & Troubleshooting] davisac:
The only time mine was rebooting was when I underclocked it too much. SOmethings wrong with your tablet .
[Nexus 7 Q&A, Help & Troubleshooting] najaboy:
Odds are it is not hardware related, nor is it caused by third party apps such as Netflix or Hulu. Random reboots are a known issue since 4.2 and are caused by the operating system itself.
[HTC One X] brayman:
Hiya,

My phone is a work phone and I've rooted it and installed Cyanogen rom on it, however encryption doesn't work as part of that rom. For me to be able to use the phone as a work device I need to encrypt it. If I tell it to encrypt the phone it never seems to do anything, I get the green android appear and that's it I have left it overnight before and it never seems to complete or give me any kind of progress bar. Any ideas how I can fix this please ?

Regards,

Martin
[HTC One X] DeeZZ_NuuZZ:
if you want to know something then ask in the rom thread....but where do you tried to encypt it? in the settings or where? and which encrypt do you mean? it should work nicely
[HTC One X] navalynt:
I'm assuming here you are trying to add an account as either Exchange or a Google Apps domain controlled by your employer and thus you are getting the security pop-ups telling you to add a PIN and encrypt the storage. What you'll find that really sucks is that once encrypted you can't flash updates to CM through the recovery anymore.

Try this app: Enhanced Email $9.99.

It will let you sync without needing to enable all of the security features on your device. I highly recommend you stick with a PIN code though!
[HTC One X] pabx:
Sorry for the self-advertisement: but encryption does work in my 4.2 AOSP ROM: http://xdaforums.com/showthread.php?t=2013506

Note that you should switch to the 'bigdata' layout in order to avoid any data leakage by an unencrypted sdcard.
[HTC One X] brayman:
I thought I did, ok. Yes if I go to settings and encrypt on the phone that way and it doesn't work.
[HTC One X] brayman:
Yes that's exactly It, Our work email is on Google now so its the Google apps problem. I don't mind if I cant flash updates as I haven't found any problems with the latest nightlies for a long time. I may try that if there is no other solutions dont really wanna spend my own money getting my work email working ;).
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] streetu:
Anybody can convert or make walkman like old walkman 4.0 from Hazel/Elm/Zylo ?

Something like this:
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
Hey Gang,

I have an old Dinc that I am trying to get setup for a friend to use on Cricket or Pageplus. This is not the issue though.

The phone is using:

hboot .92

S-Off

CMW recovery 5.0.2.0

The phone was on Touch of Blue 2.0 and having wifi issues, so i decided to wipe it and install ToB2.2

In looking for new mods for the dinc, I ran across Convert2EXT4

I flashed "Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip" and proceeded to install ToB.

All seemed fine, but upon initial boot it never gets past the bootanimation.

After 30 minutes of waiting I decided to re-wipe everything manually.

THIS IS WHERE THE PROBLEM CAME IN

I get an error when wiping /data & /cache

I flashed "Convert2Ext4_no_data_limit_dalvik_moved_Revert.v2.0.zip" to try to revert the change. It went fine, but i still get the error when wiping.

I have also tried to fix things using "fix_datadata.v2.0.zip" & "wipe_dalvik.v2.0.zip"

Nothing seems to fix the problem.

Now I can't flash anything.

When I flash a stock ROM via RUU or PB31IMG.zip I get a bootloop.

I believe the phone is not wiping the /data or /cache partitions because it can't find them.

Any help getting the partitions back to stock?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Try a factory reset from hboot? It will wipe emmc as a warning.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
tired that and every other form of wiping.

I have deduced that the phone has messed up partitions and needs to be re-setup.

I am currently following this thread ( http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/ ) to correct the problem. I'll post my success/failure in a bit :silly:
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
part of my problem is that i can't unmount /dev/block/mmcblk0 partition 1

The CACHE partition.

when I "print" ,or view, the partitions using "parted" i get this

Model: MMC SEM08G (sd/mmc)

Disk /dev/block/mmcblk0: 7911MB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File System Flags

1 8192B 797MB 797MB primary ext4

2 797MB 1007MB 210MB primary ext3

3 1007MB 7944MB 6937MB primary fat32 lba

I wish i had a nandroid backup to revert to.... but i don't

Oh well. This thing might be bricked for now until i figure out how to remove and re-create the internal partitions.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
i need some help understanding this 'parted' stuff.

I have tried to re-create the partitions but I get errors that i need to run "e2fsck" to fix them.

I am completely lost and need the help of a pro =)

TINY... where are you when I need you =)
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
At work. I haven't exactly had the chance to look. I wish I knew the thread where I tried to help before. Perhaps that could come in handy at least as a starting point.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
No rush!

Let me know what files or screenshots you need to even think about it =)

Who knows.... this could lead to the UlTiMaTE WiPE & FOrMaT script to rule them all :silly: :good:
[Droid Incredible Q&A, Help & Troubleshooting] cmlusco:
Ok so just to be clear you were on 2.0, then without wiping you flashed the ext4 dalvik moved mod. Then without wiping you flashed 2.2? After you flashed the ext4 dalvik moved mod, did you reboot before flashing 2.2, or just flash it right after the ext4 mod?

Fyi all versions of tob have the ext4 normal dalvik mod already built in. This may be where the issue came up. That is why i want to know exactly how you flashed the files.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
No. Here is what i did.

looked for new version of the ROM and downloaded it.

while it was downloading, I ran across the Convert2EXT4 mod and downloaded all of the files.

moved all my downloaded files to the SD card (ROM & mods)

factory wipe, then wiped system, datadata, data, cache, emmc, sd-ext.

flashed the rom ToB2.2

flashed the ext4 dalvik moved mod.

reboot

*** this is when i noticed something wrong because the phone sat on the splash screen for 30 minutes.

At this point I decided to un-do the mod and move things back to the way they were.

I flashed the mod to revert the change. The flash went fine with no reported errors.

Next, I wanted to start fresh so I format everything again. This is where my problem was evident.

/data & /cache could not be formatted. I rebooted and tried formatting again. No dice.

I moved forward with flashing the ToB2.2 ROM once again. No joy. It still won't boot.

This is where I am now.

I researched online and found "parted" . I believe this may be the solution but for some reason /cache will not unmount so i can format it.

I need a way to completely remove all partitions from the internal memory of the phone and re-create them.

Otherwise, I am semi-bricked :eek:

I hope this info clears up any questions :good:
[Droid Incredible Q&A, Help & Troubleshooting] cmlusco:
Ok that wasnt the problem then. Im not sure what causes this, but i have seen it several times before on different roms. Its always cache and data that seem to mess up. Any luck with parted? That thread is the only one i see where someone actually got it working right again. My only other sugestion would be to unlock your bootloader with htcdev, and then fastboot flash a misc img from froyo. Then run the froyo ruu thru hboot. I belive this is where the partition info is stored.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Check post #7 on this thread below:

http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/

Fortunately, parted is loaded on recoveries now so it doesn't need to be pushed over so run these from adb shell in recovery.

Quoted below:

Prior to trying to change anything, what is the output if you run parted /dev/block/mmcblk0 then type print as shown in post #11 from that thread?

Here is mine below:

~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext3
3 1007MB 8095MB 7088MB primary fat32 lba
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
I have been round and round with parted (post#4). It seems my '/cache' partition will not unmount :crying:

I hope we can figure this out :highfive:

Here is my 'print'

C:\Program Files (x86)\Android\android-sdk\platform-tools\DINC>adb devices
List of devices attached
HT132HJ00898 recovery

C:\Program Files (x86)\Android\android-sdk\platform-tools\DINC>adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B][COLOR="Blue"]print[/COLOR][/B]
print
print
[B][COLOR="DarkOrange"]Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext4
2 797MB 1007MB 210MB primary ext3
3 1007MB 7944MB 6937MB primary fat32 lba[/COLOR][/B]

(parted) [B][COLOR="Blue"]mkfs[/COLOR][/B]
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? [B][COLOR="blue"]y[/COLOR][/B]
y
y
Partition number? [B][COLOR="blue"]1[/COLOR][/B]
1
1
File system type? [ext2]? [B][COLOR="blue"]ext2[/COLOR][/B]
ext2
ext2
[B][COLOR="Red"]Error: File system was not cleanly unmounted! You should run e2fsck. Modifying

an unclean file system could cause severe corruption.[/COLOR][/B]
Ignore/Cancel?[B][COLOR="Blue"] i[/COLOR][/B]
i
i
Error: File system has an incompatible feature enabled. Compatible features are

has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Error: SEGV_MAPERR (Address not mapped to object)
Aborted