Related
For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:
I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app
@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium
U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app
Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell
EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse
ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium
A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks
Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?
one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please
After struggling with this phone T959V for 3 days I finally got the ROM installed.
It seems as you read these forums you're not sure if what you're reading is accurate and how much of this still relevant to your issue.
I did everything on a 32-bit system as this seems to matter as I couldn't do this on my 64-bit Win7, but that was following the heimdall oneclick methods, but I could only go so far with that. I got all the way to the cannot mount SD Card...
Being that this is my 2nd phone to root, this is the harder of the lot (my other was HTC)
But enough about myself here's some tips if you're still having issues with this guide that helped me out which wasn't posted.
Do yourself a favor and just get a 2nd SDCard. Stop crying about the cost and just get one. I had 2 8GBs so I didn't care if anything happened.
I made sure I copied all the data over to the hard drive and then formatted the blank one and put the files back. So now if I blew this one up while in rooting mode, I didn't care, because I knew I had one sitting ready to go.
You may want to get the latest Samsung USB drivers as mine was 32-bit and after rebooting it was able to see the phone.
If you stick your phone in downloading mode, just leave it there and make sure odin can see your phone. If its not showing up then something else is wrong (usb, cable, port...etc) many times ODIN couldn't see my phone and I had to download reinstall drivers reboot etc...but my phone was still hanging in download mode, so dont sweat it...
I was able to follow the directions and was very happy I got to step 10.
You may want to get the QuickBoot.apk as this is better than going to CWM once you're in the phone.
But now enter the ROM and I get the blasted "Cannot mount sdcard".
And I cannot make a backup, which is an indication that something is not reading right.
I read through the forums and they talked about creating a partition. Since I didn't care about the SDCard info I just said create a partition thinking that it would create a separate partition on the card...nope..it will wipe everything from the card as if you formatted it. I chose the 1024 and 0 cache and away it went.
After a quick reboot, I was able to make a backup and finally load a ROM and install.
I didn't realize that it was such a big deal with the formatting, but again as they say follow all directions.
I didn't do the #12, but did hear the Linda and all is great!
I'm happy to report that my Samsung Galaxy S T959V is finally rooted and Valhalla Black Edition installed.
I figured I should contribute my headaches as someone might be going through them as well.
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
sqlandy said:
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
Click to expand...
Click to collapse
1. You don't really need the busybox installer, but it's recommended since there are a few apps and tweaks out there that need busybox. If I recall correctly, I threw in busybox into my edition of VB, but I'm not sure if Raver threw it into his.
2. Yeah you can format it directly from the phone but the repartitioning is necessary, it'll work just after a format.
I tried to port a couple of ROMs from GSII and from Nexus S to our device using the following thread
But I'm always getting a status 7 error while flashing it.
This error is related to the updater script and I tried few changes here and there but without success.
Used Adam's CM10 as base and in the updater script the following lines seemed extra from the others ROMs' updater scripts.
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
tried with and without these lines and still got status 7 error.
The original thread is filled with questions for their own devices and hardly any useful answer from the author.
I'm guessing many of you would have tried this guide before and so wanted to discuss here within ourselves.
I could have PMed our great devs here, but thy are all busy in "actual dev" work and so do not want to disturb them.
They might post here when they have time.
So guys, please give suggestions and your hiccups when you tried this method. Let us try to "port" some ROMs
Take a look to the recovery log
Just replace the update script from CM 10 and try it should work...
Grarak said:
Take a look to the recovery log
Click to expand...
Click to collapse
umm.. i should have thought this. thanks Garak.
mj.vikram said:
Just replace the update script from CM 10 and try it should work...
Click to expand...
Click to collapse
ok, let me try the original update script from our cm10 build.
as soon as i get the mobile back from my dad.
All the Best Buddy :good:, Waiting for some Good ROM from you ....
I do not have my Galaxy R with me and so am trying this method on GNex for now to see if im able to boot the ported ROM.
I left the updater-script untouched and the CWM flash went through without the status 7 error.
but gets stuck after boot animation forever and never moves ahead.
In what way I should go about troubleshooting this issue, I mean what kind of log would help for this "stuck in boot anim issue"
sarun_biotech said:
I do not have my Galaxy R with me and so am trying this method on GNex for now to see if im able to boot the ported ROM.
I left the updater-script untouched and the CWM flash went through without the status 7 error.
but gets stuck after boot animation forever and never moves ahead.
In what way I should go about troubleshooting this issue, I mean what kind of log would help for this "stuck in boot anim issue"
Click to expand...
Click to collapse
Copy the libandroid_runtime.so, libandroid_servers.so and libmedia_jni.so from Ported ROM to Base ROM and see if solves the issue. Try taking a adb logcat to check what's causing the issue.
selva.simple said:
Copy the libandroid_runtime.so, libandroid_servers.so and libmedia_jni.so from Ported ROM to Base ROM and see if solves the issue. Try taking a adb logcat to check what's causing the issue.
Click to expand...
Click to collapse
yes. did that too Selva. still stuck at boot anim.
actually, when should i take the logcat. coz, during the boot anim phase, i cant connect using adb from pc and if i restore to old rom, the logcat is only for the new one.
correct me if im worng.
EDIT : connected to usb in cwm mode and i was able to run adb commands. but after the flash and reboot, the command always says waiting for device. even during the boot anim time.
sarun_biotech said:
yes. did that too Selva. still stuck at boot anim.
actually, when should i take the logcat. coz, during the boot anim phase, i cant connect using adb from pc and if i restore to old rom, the logcat is only for the new one.
correct me if im worng.
Click to expand...
Click to collapse
Switch off ur mobile...connect to pc...give adb logcat..it will wait for the device to show up...now switch on ur pc..it will rec ur device and start preparing the logcat....now chk the log
You cannot normally get an adb connection from a device that hasn't even booted up, because from ICS (or HC), this method was changed. Fortunately, this can be bypassed quite easily. Unpack the boot.img with Adi_Pat's tools or dsixda's kitchen, find 'service adbd' in init.rc and remove the option 'disabled'. You will get adb connection.
Regarding replacing native binaries and libraries: Always know what you do! Native code not supportes by our CPU will just spam the logcat with SIGILL errors.
Sent from my CM10-powered GT-I9103
selva.simple said:
Switch off ur mobile...connect to pc...give adb logcat..it will wait for the device to show up...now switch on ur pc..it will rec ur device and start preparing the logcat....now chk the log
Click to expand...
Click to collapse
didnt work out bro.
Adam77Root said:
You cannot normally get an adb connection from a device that hasn't even booted up, because from ICS (or HC), this method was changed. Fortunately, this can be bypassed quite easily. Unpack the boot.img with Adi_Pat's tools or dsixda's kitchen, find 'service adbd' in init.rc and remove the option 'disabled'. You will get adb connection.
Regarding replacing native binaries and libraries: Always know what you do! Native code not supportes by our CPU will just spam the logcat with SIGILL errors.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
thanks Adam. will try tmrw. and thanks for the heads up regdng libs. will study more.
Please make a nandroid backup first!!!
GT-P6200 ONLY
Warning: This seems to interfere with root (permissions?), you will most likely need to re-root. pretty much painless took me approx. 1 minute. Worth it.
ALSO: I did a complete uninstall/removal of Xposed before this, just in case.. and would highly recommend everyone do the same.
So I managed to de-odex /system/framework, system/app and /preload/symlink/system/app.
I used dsixda's kitchen, it automatically knew we had more apk's in hidden.img
with JellyBean Samsung has moved some .apk's to /preload/symlink/system/app and left a symbolic link in /system/app, likely to save space on /system.
Flash in CWM recovery that is compatible with jellybean.( 6.0.2.7)
This update.zip will wipe your /cache and /data/dalvik-cache and /preload/symlink/system/app's automagically.
Keep calm as it is extracting and be patient on reboot and enjoy...
Oh and it is true stock, nothing removed so file size is beefy at 402MB.
Try to go easy on my hosting sites so they don't get suspended, I may host it at another if I need to.
Should anything go wrong, simply advanced restore /system only.
Dropbox
PutLocker
---4shared---
reserved for future use.
Thank You.
Thank you so much but unfortunately i cant download 400 mb (SLOWEST INTERNET CONNECTION IN THE WORLD) so i was wondering if you could be kind enough as to giving me your edify_defs for the P6200 or at least the updater-script file
As for the Tablet UI I found this and it works fine on my Galaxy Tab 7+ (even with an odexed rom :laugh
http://forum.xda-developers.com/showthread.php?t=2095929
Hope it helps!!
MaxiTheMan said:
Thank you so much but unfortunately i cant download 400 mb (SLOWEST INTERNET CONNECTION IN THE WORLD) so i was wondering if you could be kind enough as to giving me your edify_defs for the P6200 or at least the updater-script file
As for the Tablet UI I found this and it works fine on my Galaxy Tab 7+ (even with an odexed rom :laugh
http://forum.xda-developers.com/showthread.php?t=2095929
Hope it helps!!
Click to expand...
Click to collapse
Really I thought I tried this, I use Xposed for a few apps. I would rather not have to go to 133 dpi If we could help it, could you please share a few screenshots? Thanks..
Yes, I can share my update-script shortly..
These are the screenshots:
https://drive.google.com/folderview?id=0BzKet174g1VAaTZvX0JCUFYySEk&usp=sharing
As you can see there is still a few bugs like the volume slider but nothing major..
welp, just got TabUI. Thanks to a few .smali edits, pretty excited.
Enjoy. cheers.
Anyone can confirm if this is working properly? And has it made a slight difference performance wise/batter wise?
seems snappier to me, and I havent deleted a single app yet.
Could you please share how you got the Tablet UI
And I'm still waiting on that script file too
I will post info later today, I promise.
Dropbox suspended... I will also try to upload to one more site tonight.
chrisrotolo said:
welp, just got TabUI. Thanks to a few .smali edits, pretty excited.
Enjoy. cheers.
Click to expand...
Click to collapse
Edit: sorry, unnecessary post...
Script-->
Code:
ui_print(" ");
ui_print("Deodexed Apps and Framework for GT-P6200 MMXC3.");
# unmount anything that will be mounted later
unmount("/preload");
unmount("/data");
unmount("/cache");
unmount("/system");
# wipe the dalvik cache
ui_print("Wiping the dalvik cache.");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/data");
delete_recursive("/data/dalvik-cache");
unmount("/data");
# actually format the /cache partition (cleaner than any other method)
ui_print("Formatting cache.");
format("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
show_progress(0.500000, 80);
# mount /preload
mount("ext4", "EMMC", "dev/block/mmcblk0p11", "/preload");
# mount /system
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
# delete /system/app and /system/framework
ui_print("Removing preload apks, framework and /system/apps......");
delete_recursive("/system/app");
delete_recursive("/system/framework");
delete_recursive("/preload/symlink/system/app");
ui_print("Extracting files...Keep Calm...");
package_extract_dir("preload", "/preload");
package_extract_dir("system", "/system");
ui_print("Setting permissions.");
set_perm_recursive(0, 0, 0755, 0644, "/system/framework");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/preload/symlink/system/app");
ui_print("Creating symlinks...");
symlink("/preload/symlink/system/app/AccuweatherDaemon.apk","/system/app/AccuweatherDaemon.apk");
symlink("/preload/symlink/system/app/Aurora.apk","/system/app/Aurora.apk");
symlink("/preload/symlink/system/app/Bluesea.apk","/system/app/Bluesea.apk");
symlink("/preload/symlink/system/app/Dropbox","/system/app/Dropbox.apk");
symlink("/preload/symlink/system/app/FaceLock.apk","/system/app/FaceLock.apk");
symlink("/preload/symlink/system/app/Flipboard.apk","/system/app/Flipboard.apk");
symlink("/preload/symlink/system/app/Gmail.apk","/system/app/Gmail.apk");
symlink("/preload/symlink/system/app/GoogleTTS.apk","/system/app/GoogleTTS.apk");
symlink("/preload/symlink/system/app/GroupCast.apk","/system/app/GroupCast.apk");
symlink("/preload/symlink/system/app/HoloSpiralmr.apk","/system/app/HoloSpiralmr.apk");
symlink("/preload/symlink/system/app/ICS_Herowidget_Tablet.apk","/system/app/ICS_Herowidget_Tablet.apk");
symlink("/preload/symlink/system/app/ICS_Herowidget_Tablet_Main.apk","/system/app/ICS_Herowidget_Tablet_Main.apk");
symlink("/preload/symlink/system/app/ICS_YahooNews_Tablet","/system/app/ICS_YahooNews_Tablet.apk");
symlink("/preload/symlink/system/app/ICS_YahooStock_Tablet.apk","/system/app/ICS_YahooStock_Tablet.apk");
symlink("/preload/symlink/system/app/Kies.apk","/system/app/Kies.apk");
symlink("/preload/symlink/system/app/kieswifi.apk","/system/app/kieswifi.apk");
symlink("/preload/symlink/system/app/Kobo_Tablet.apk","/system/app/Kobo_Tablet.apk");
symlink("/preload/symlink/system/app/Phonesky.apk","/system/app/Phonesky.apk");
symlink("/preload/symlink/system/app/PickUpTutorial.apk","/system/app/PickUpTutorial.apk");
symlink("/preload/symlink/system/app/PlusOne.apk","/system/app/PlusOne.apk");
symlink("/preload/symlink/system/app/PolarisOfficeTablet.apk","/system/app/PolarisOfficeTablet.apk");
symlink("/preload/symlink/system/app/PressReader_Tablet.apk","/system/app/PressReader_Tablet.apk");
symlink("/preload/symlink/system/app/Pulse.apk","/system/app/Pulse.apk");
symlink("/preload/symlink/system/app/SamsungApps_Tablet.apk","/system/app/SamsungApps_Tablet.apk");
symlink("/preload/symlink/system/app/SamsungAppsUNA3.apk","/system/app/SamsungAppsUNA3.apk");
symlink("/preload/symlink/system/app/SamsungCamera_Tablet.apk","/system/app/SamsungCamera_Tablet.apk");
symlink("/preload/symlink/system/app/SamsungIME.apk","/system/app/SamsungIME.apk");
symlink("/preload/symlink/system/app/Samsungservice.apk","/system/app/Samsungservice.apk");
symlink("/preload/symlink/system/app/SecPhone.apk","/system/app/SecPhone.apk");
symlink("/preload/symlink/system/app/SecSettings.apk","/system/app/SecSettings.apk");
symlink("/preload/symlink/system/app/SecTabletAlarmClock.apk","/system/app/SecTabletAlarmClock.apk");
symlink("/preload/symlink/system/app/SecTabletDualClockAnalog.apk","/system/app/SecTabletDualClockAnalog.apk");
symlink("/preload/symlink/system/app/SecTabletDualClockDigital.apk","/system/app/SecTabletDualClockDigital.apk");
symlink("/preload/symlink/system/app/SecTabletMusicPlayer.apk","/system/app/SecTabletMusicPlayer.apk");
symlink("/preload/symlink/system/app/SecTabletVideoPlayer.apk","/system/app/SecTabletVideoPlayer.apk");
symlink("/preload/symlink/system/app/SecTabletWorldClock.apk","/system/app/SecTabletWorldClock.apk");
symlink("/preload/symlink/system/app/SecWallpaperChooser.apk","/system/app/SecWallpaperChooser.apk");
symlink("/preload/symlink/system/app/SlideShow.apk","/system/app/SlideShow.apk");
symlink("/preload/symlink/system/app/Velvet.apk","/system/app/Velvet.apk");
symlink("/preload/symlink/system/app/YahoonewsDaemon.apk","/system/app/YahoonewsDaemon.apk");
symlink("/preload/symlink/system/app/YahoostockDaemon.apk","/system/app/YahoostockDaemon.apk");
symlink("/preload/symlink/system/app/YouTube.apk","/system/app/YouTube.apk");
symlink("/preload/symlink/system/app/Zinio.apk","/system/app/Zinio.apk");
ui_print("Unmounting...");
unmount("/system");
unmount("/preload");
ui_print(" ");
ui_print("All Done.");
ui_print("The first reboot after installation will take a few minutes.");
Credit for Tablet UI .smali edits: Here
Battery
hello chrisrotolo, but there is no 'possobilità' to see the percentage of batgteria cme in the original rom?
in the system settings when I go to check battery% nothing happens!
thank you and if you know how to fix send me a private message
hmm, strange. idk. Thats weird. reboot and try wiping /cache dalvik-cache and maybe fix permissions.
If you really need it you could get a small widget.
you try my tablet mode mod, it's there on the quick panel by default.
I didnt notice this because I don use it.
Thanks for the heads up.
hey chris,
after reboot it keeps showing the android logo for more than 10 mins..so i guess thats a bootloop
any idea?
btw im coming from PA 2.50
Not working for me, using stock rooted MC3 (CSC ITV).
After some minutes working to update apps on boot, locked on Samsung logo..
Wipe cache + Delvik not usefull , at last refreshed with JB MC3 Stock firmware with Odin ...
Any idea?!
Inviato dal mio GT-P6200 con Tapatalk 2
My CSC is P6200XAMC3
So did it say it was updating apps then rebooted and got stuck on samsung logo?
If you made a backup, you could likely just restore, however Im not sure if CWM backs up / preload.
We need a new CWM with this option I think.
Im sorry if you lost anything. You said you were rooted, did you have any root apps that may have been the culprit?
Have you tried flashing from fresh stock after Odin?
Thanks.
tzacapaca said:
hey chris,
after reboot it keeps showing the android logo for more than 10 mins..so i guess thats a bootloop
any idea?
btw im coming from PA 2.50
Click to expand...
Click to collapse
Android logo? Were you on stock when you flashed this?
chrisrotolo said:
My CSC is P6200XAMC3
So did it say it was updating apps then rebooted and got stuck on samsung logo?
If you made a backup, you could likely just restore, however Im not sure if CWM backs up / preload.
We need a new CWM with this option I think.
Im sorry if you lost anything. You said you were rooted, did you have any root apps that may have been the culprit?
Have you tried flashing from fresh stock after Odin?
Thanks.
Click to expand...
Click to collapse
Thanks for replay.
Yes CSC it's the same, I want to specify you that this ROM it's multiCSC and was applied the ITV = ITALY for my country (some third party apps are country releated).
Titanium Backup Pro installed root with SuperUser (last version) and CWM 6.0.XX installed.
Jelly Bean stock was installed after a FULL-WIPE from ICS LQ8 Vodafone (ITALY) ROM.
Your package take some time to install and at first boot recount my installed apps (over 230 !), than (if I remember correct ...) the system reboots and after boot animation stuck on Samsung Logo. I notice that boot animation have no sound after your mod .....
Download mode and CWM working after your mod though the system was unable to boot ...
Reflashed Stock JB firmware from ODIN PC with no problem, no app or data lost, my system it's working again.
What a pity, I was interested in TableUI mod on an deodexed ROM.
yes thank you I see that is multi-csc. well if you flash stock Italian Language is there. As far as the Vodafone/Italy .apks, there is usually a way to extract those and install seperately.
The only .apk I see in ITV is videos.apk
There also many people that claim you can change CSC without fac. reset. Search here on XDA.
Official:
Unique ECHOE-ROM Flashing-Guide
since v5 to v37 and up, still the best guide!
Always have a NANDROID Backup before changing anything on your device!
Please make a backup of your APP´s with e.g. Titanium-Backup to restore them after flashing!
Also it is advisable to make a backup of your contacts!
Note: You might have ROOT before getting custom recovery (CWM, TWRP, PhilZ) to work!
Flash MGA based Pre-Rooted ROM from DjeMBeY or ROOT your Phone to get it!
Users with NEW Bootloader simply flash a MI8 or higher pre-rooted ROM!
You have to build your System completely new to get a 100% working ECHOE ROM!
No "dirty flash" without wipe! Make it like I describe now or leave this Guide immediately!
You need the following for your Galaxy S4 I9505:
Device fully charged! =D--._.-----
Samsung USB connection cable to connect phone to PC
Micro SD-Card Reader for your PC (only if you have a micro-SD Card in the phone)
Samsung USB driver for PC Click here!
Latest Philz Touch Recovery Click here!
Odin (latest) ........................ Click here!
ECHOE ROM ....................... Click here!
Modem Collection .............. Click here!
Perhaps CSC Changer App Click here!
DOWNLOAD MODE:
(for Odin operations (.tar.md5 Files))
NOTE: You might have to extract downloaded .RAR file to get the inserted .tar .md5 file!
From switched OFF phone push the power button until the S4 vibrates, IMMEDIATELY push "volume DOWN" to enter download mode.
Push volume UP when you be asked!
Connect the Phone to PC with USB connection cable!
RECOVERY MODE:
(for Recovery operations (.zip Files)):
From switched OFF phone push the power button until the S4 vibrates, IMMEDIATELY push "volume UP" to enter recovery mode.
Process:
Prepare Phone:
1: ROOT YOUR PHONE like described above (if it´s not already rooted)!
2: Flash Philz Touch Recovery with Odin (as "PDA" or new Odin as "AP") or SGS4 flasher APP!
... Look at the above line "RECOVERY MODE" in this Guide how to start!
... If Philz Recovery asks you to fix ROOT (after you choose Reboot Now) choose NO !!!
Prepare SD-Card:
If you don´t have a Micro-SD Card just copy the downloaded EchoeRom ZIP to the internal SD!
3.: Switch OFF your phone and take out the micro SD-Card
4.: Put the micro SD-Card in a card reader and delete the folder ".android_secure"
.... It might work without deleting the ".android_secure" if you come from older ECHOE ROM Version (not tested by me)
5.: Copy the downloaded EchoeRom ZIP to the micro SD-Card
6.: Put the micro SD-Card back into the phone (DONT BOOT UP THE PHONE WITH INSERTED micro SD-Card, ".android_secure" is written again)!
Cleaning Phone:
7.: To completely clean your S4 and get rid of all older remaining´s you now start into Recovery Mode
... Look at the above line "RECOVERY MODE" in this Guide how to start!
8.: In the Settings of Philz Recovery choose:
8a: Advanced: Wipe Dalvic Cache
8b: Wipe Cache Partition
8c: Wipe Data/Factory Reset / Factory Reset
8d: Wipe Data/Factory Reset / "Clean before flash new ROM"
... Note: You have to flash a new ROM after doing point 8d !!!
... Stay into the Philz Recovery and read ahead!
Flashing ECHOE ROM:
9.: Because you stay into Philz Recovery hit the option "Install ZIP" then hit "choose zip from/storage/sdcard1" or internal SD and choose the EchoeRom ZIP
10.: After the flashing process finished go back to main menu and choose "Reboot System Now"
..... If Philz Recovery asks you to fix ROOT (after you choose Reboot Now) choose NO !!!
First Start:
11.: The first time the phone boot up take about 3-4 minutes
12.: After the phone has started do furthermore NOTHING for about 5 minutes (let the system set up in calm)
13.: Switch OFF the phone with the power-button
Flashing another Modem for your Echoe ROM Version (if the included modem is not working properly):
14.: Boot device into Download-Mode from switched off device (important)!
15.: Connect Phone to PC with the Samsung USB Cable!
16.: In Odin remove the "Auto Reboot" hook
17.: In Odin click on PHONE or newer Odin click on CP, load your Modem and press START
18.: Wait 3-4 minutes till there is a message: All threads completed. (succeed 1 / failed 0)
19.: Hold Power-Button for 10 seconds till phone resets (you feel the vibration)
Ready for take off!!! :laugh:
Phuuu... that was a ride... everything clean and new now!
Enjoy this famous ECHOE ROM!
Hit the :good:THANX Button if you enjoy!
.
Great guide and should help a lot of people out! Thanks for this!!
Sent from my GT-I9505 using XDA Premium 4 mobile app
I can't find an .android_secure folder anywhere on my SD card.
Just checked and the checksum is correct:
MD5 (/Users/Hate/Downloads/Echoe Illusion Rom v6_28Oct.zip) = 0fba4efafe95457a934cb50946bf552e
Same one as listed at http://d-h.st/AX5 the download link.
Prehaps the upload is corrupt?
Can anyone provide me with an alternative link? I don't want the themed version.
I'm trying downloading it with a different browser however I really cant see chrome being any problem at all?
Please someone help, I'm stuck with an expensive brick currently Well semi-brick :'(
I'd ideally like to fix it as its my only alarm clock!
Thanks
Hmmmmmm.
Just downloaded the themed version,
Wiped everything as instucted ( noticed it said Formatting external_sd/.android_secure despite me checking many time before and its not there, not even a hidden file or folder )
Getting the exact same error Can't open... bad...Can anyone help this is driving me crazy!
All the md5 hashes match
Thanks
Hey I cant seem to get my phone to stop losing signal when the screen is off. I have flashed the modem that the firmware checker says is good for my phone but its still not working any ideas.
HollowVegitoRay said:
Hey I cant seem to get my phone to stop losing signal when the screen is off. I have flashed the modem that the firmware checker says is good for my phone but its still not working any ideas.
Click to expand...
Click to collapse
Did flashed the ROM like described above?
Did you use the inbuilt Faux Kernel?
Have you flashed the Modem like described in Point #18 ?
What is your Bootloader (old or new (with or without Knox)?
This works flawless! Many people have confirmed! :good:
This flashing method is beyond any doubt, it MUST work if you dont have made thinks wrong!
philipkroberts said:
I can't find an .android_secure folder anywhere on my SD card.
Just checked and the checksum is correct:
MD5 (/Users/Hate/Downloads/Echoe Illusion Rom v6_28Oct.zip) = 0fba4efafe95457a934cb50946bf552e
Same one as listed at http://d-h.st/AX5 the download link.
Click to expand...
Click to collapse
Never mind, this folder is written from the System itself (after first booting up).
Whats the problem with your downloaded ROM?
Prehaps the upload is corrupt?
Can anyone provide me with an alternative link? I don't want the themed version.
I'm trying downloading it with a different browser however I really cant see chrome being any problem at all?
Please someone help, I'm stuck with an expensive brick currently Well semi-brick :'(
I'd ideally like to fix it as its my only alarm clock!
Thanks
Click to expand...
Click to collapse
Flash a stock ROM with Odin first and then go ahead!
For new Bootloader you have to flash stock .tar.md5 XXUEMJ5 Firmware with ODIN.
For old Bootloader you have to fllash stock .tar.md5 XXUEMGA Firmware with ODIN.
Flash stock ROM with my Guide here: http://forum.xda-developers.com/showthread.php?p=46399517#post46399517
So you should have a starting point to continue with the ECHOE ROM Flashing guide!
fAiLOfax said:
Did flashed the ROM like described above?
Did you use the inbuilt Faux Kernel?
Have you flashed the Modem like described in Point #18 ?
What is your Bootloader (old or new (with or without Knox)?
This works flawless! Many people have confirmed! :good:
This flashing method is beyond any doubt, it MUST work if you dont have made thinks wrong!
Click to expand...
Click to collapse
I flashed like described in point 18. I don't know what bootloader I have and I'm not sure about the kernel.
HollowVegitoRay said:
I flashed like described in point 18. I don't know what bootloader I have and I'm not sure about the kernel.
Click to expand...
Click to collapse
Did you ever flashed a ROM higher than MGA or MH1 you have the NEW Bootloader!
Flash a stock ROM with Odin first and then go ahead!
For new Bootloader you have to flash stock .tar.md5 XXUEMJ5 Firmware with ODIN.
For old Bootloader you have to fllash stock .tar.md5 XXUEMGA Firmware with ODIN.
Flash it like I described in my Best ROM Flashing Guide (in my Sig)!
Then continue with this ECHOE ROM Flashing Guide!
Hi, really like your threads and just discovered this one.
I have a android.secure folder on my external sd card but am wondering, why I can't just delete that one, boot into recovery, wipe and flash the new ROM. In your steps you recommend to take out the card, put it into a card reader, delete the folder, put ROM on external sd card, put card in phone and boot into recovery. Wouldn't that be the same as if I delete it on my phone with a file Explorer and booting into recovery?
Or is this folder recreated while shutting the phone down?
Also, could you explain a bit why this particular folder can make problems?
Thanks in advance!!
---------------------------------------------
If you like Techhouse you can listen to my tracks here:
www.facebook.com/mister.adl
adl said:
Hi, really like your threads and just discovered this one.
I have a android.secure folder on my external sd card but am wondering, why I can't just delete that one, boot into recovery, wipe and flash the new ROM. In your steps you recommend to take out the card, put it into a card reader, delete the folder, put ROM on external sd card, put card in phone and boot into recovery. Wouldn't that be the same as if I delete it on my phone with a file Explorer and booting into recovery?
Or is this folder recreated while shutting the phone down?
Also, could you explain a bit why this particular folder can make problems?
Thanks in advance!!
---------------------------------------------
If you like Techhouse you can listen to my tracks here:
www.facebook.com/mister.adl
Click to expand...
Click to collapse
I know mate!
I couldn´t delete the .android.secure folder from phone within! I think its used from System and should not be deleted while the system is runnig.
I don´t know what errors/problems this folder could make, I always removed it first.
I think friedrich420 has written that it should be deleted because of making problems when switching from stock ROM to e.g. ECHOE ROM!
SLIM - Yes, Full - No
Hi!
Huge Fan of Echoe Rom. I have a very weird issue with the echoe celstial voices goint to echoe illusion v7. Flashed celestial voices and worked like a charm. Then Illusion V6 Full came up. So downloaded and flashed it. Again worked like a charm. Then I tried the slim version and from there, something weird happened. echoe illusion v6 slim with no kitchen worked out fine, but game me random resets and freeze. So i tried goin back to full. But I cant flash the full version. But can go back to slim without a problem. tried it 20 times now but still getting stucked at boot logo. then v7 came out and still same results.
Cant post to echoerom thread directly due to restrictions. Please advice as to what should i do. Thanks in advance.
fAiLOfax said:
I know mate!
I couldn´t delete the .android.secure folder from phone within! I think its used from System and should not be deleted while the system is runnig.
I don´t know what errors/problems this folder could make, I always removed it first.
I think friedrich420 has written that it should be deleted because of making problems when switching from stock ROM to e.g. ECHOE ROM!
Click to expand...
Click to collapse
Thanx mate!
Will try your way for Echoe 7, even i never encountered any trouble. :fingers-crossed:
adl said:
Thanx mate!
Will try your way for Echoe 7, even i never encountered any trouble. :fingers-crossed:
Click to expand...
Click to collapse
:laugh:
BTW: i like to get "thanx" if I could help you!
cut
Sorry, me with another question regarding external sd + android_secure.folder:
I should take out the external sd, delete the folder and put the ROM on the external sd card. Now when i boot right into revovery will the folder be created again? Cause then it would make more sense to leave external sd card out and put the ROM on internal sd card and flash from there.
As I usually do a fullwipe, including formating internal sd card the ROM would be formated as well. So the ROM needs to be on the external sd card, but then again the android_secure folder might be created while booting up in recovery...i hope you understand my dilemma. :silly:
adl said:
Sorry, me with another question regarding external sd + android_secure.folder:
I should take out the external sd, delete the folder and put the ROM on the external sd card. Now when i boot right into revovery will the folder be created again? Cause then it would make more sense to leave external sd card out and put the ROM on internal sd card and flash from there.
As I usually do a fullwipe, including formating internal sd card the ROM would be formated as well. So the ROM needs to be on the external sd card, but then again the android_secure folder might be created while booting up in recovery...i hope you understand my dilemma. :silly:
Click to expand...
Click to collapse
Man! The folder is created from the Android System not from recovery!
Make it like I said in the Guide and that's it!
fAiLOfax said:
Man! The folder is created from the Android System not from recovery!
Make it like I said in the Guide and that's it!
Click to expand...
Click to collapse
DUUUUDE!!
Thanks so much for the hint with android_secure folder! #
I had this weird issue that after flashing Echoe ROM Slim Version 3-6 that while booting up for the first time after flashing 4 apps where installed which where totally bloat stuff (such as "mytaxi" and some other shi*t)
I have a "free" Phone, so i always wondered what is happening as this couldn´t come from any "carrier" service. I also formated my external sd card but the problem was still there when i installed Slim V6.
With your methoed this time NO bloat App was installed after the reboot!
Thank you so much, i finally figured out what was causing this! :good:
adl said:
DUUUUDE!!
Click to expand...
Click to collapse
Thanks so much for the hint with android_secure folder! #
I had this weird issue that after flashing Echoe ROM Slim Version 3-6 that while booting up for the first time after flashing 4 apps where installed which where totally bloat stuff (such as "mytaxi" and some other shi*t)
I have a "free" Phone, so i always wondered what is happening as this couldn´t come from any "carrier" service. I also formated my external sd card but the problem was still there when i installed Slim V6.
With your methoed this time NO bloat App was installed after the reboot!
Thank you so much, i finally figured out what was causing this! :good:
Click to expand...
Click to collapse
Nice mate!
That makes me happy! :good:
I have this modem installed now, can i update to this rom without having to update modem? Or still needed? And can i TB everything back?
And will this modem break my sounds? Since ive seen some comments of users breaking there sound ...
Sent from my GT-I9505 using app: XDA Premium and rom: CarbonRom