ClockworkMod Recovery for Samsung Galaxy S2 HD LTE (SGH-I757M)
Bell Canada released the Galaxy S2 HD LTE (SGH-I757M), which is a slight upgrade from its original Galaxy S2 GT-I9100M released the summer before, with now a bigger display and HD resolution. I have ported ClockworkMod (CWM) Recovery to the SGH-I757M, which allows you to make backups/restores of your device and also to flash custom ROMs and ZIPs.
(If you still don't know what ClockWorkMod Recovery or a custom recovery menu is, Google it or search XDA.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
WARNING! Do not flash this to a different device model from the one it's meant for - YOU MAY BRICK YOUR PHONE IF YOU DO. It will not work with the other Galaxy S2 iterations like the I9100, so don't try it with the Bell Galaxy S2 I9100M (non-HD). DO NOT flash it on the Asian variant of the GS2 HD (SHV-E120) either, as it uses slightly different internal hardware - the ROM will be unstable and the phone component will not work. If you are sure you have the CANADIAN Bell Galaxy S2 HD LTE (SGH-I757M), then click on the button below:
(For questions about ClockworkMod for the SHV-E120, contact skysbird on Twitter or GitHub. I will not discuss that device in my thread, it's not compatible with this ClockworkMod.)
NOTE FROM dsixda:
I SOLD MY SGH-I757M IN SEPTEMBER 2012. PLEASE DO NOT MESSAGE ME FOR TECH SUPPORT. DIRECT YOUR QUESTIONS TO THIS THREAD ONLY. STOCK FIRMWARE AND MORE ARE IN POST #3.
DOWNLOAD HERE
Go to the Dev-Host link above and navigate to the "Bell SGS2 HD LTE" folder, and then the "clockworkmod" sub-folder to access the files required for the following steps. Please read the installation instructions carefully.
Support my work:
DONATE / FOLLOW ME
To install CWM Recovery:
If you don't already have Odin, download it from the link above, and extract the zipped file to a folder. Ensure both the .EXE and .INI file have been extracted.
Download the TAR file for ClockWorkMod Recovery (e.g. cwm_recovery_xxxx.tar, or if you want the version that uses finger touch input: cwm_touch_recovery_xxxx.tar). Do not extract the file out of it, keep the TAR file as it is.
Turn off the phone
Put it into Download mode by pressing Power and Volume Down at the same time. The device will vibrate and soon you will see a Warning screen, where you will need to press Volume Up to enter Download mode. (NOTE: You can also use the Galaxy S2 USB Jig to go straight to Download mode. I recommend you get one from eBay just in case.)
While in Download mode, start up Odin and connect your phone to the PC via USB. You should see a status message in Odin saying your device was "added".
In Odin, press the BOOTLOADER button and select the CWM TAR file you just downloaded.
In Odin, press Start. Your custom recovery should be flashed completely in a span of a few seconds, and then it should say "PASS" in Odin. If it doesn't finish and is stuck, then your file was either corrupted during the download or there was an MD5 mismatch (this is not a regular TAR file, it has an MD5 signature).
IMPORTANT: If you downloaded the "Touch" version of CWM, *avoid* using the "Reboot to Recovery" option in the ROM or apps like Quick Boot to boot into recovery. I have found that using such apps with Touch Recovery causes every subsequent reboot to go back into recovery rather than to the system. If you are stuck in this state, re-flash the recovery image so that it boots back to the system. Next time, if you want to get into recovery, use the button combination mentioned in the steps below instead. If you have the non-touch (normal) version of CWM, this issue won't happen.
To enter CWM Recovery:
Turn off the phone
Hold down the Power button to turn the phone on, and then immediately hold down Volume Up + Volume Down at the same time.
The device will then show the word "Samsung". Let go of the buttons at the exact moment you see this.
If you did it on time, you will enter CWM Recovery. Use the Volume keys to move up and down, and press Power to select. The capacitive buttons do this: Menu = DOWN, Back = BACK to main menu, Search = SELECT
NOTE: If you had flashed CWM but are still seeing the stock recovery image, then click here for a solution.
Make sure you make a Nandroid backup of everything the first time you use custom recovery. The backup will be stored under the 'clockworkmod' folder of your SD card.
UPDATE: I sold off my device back in September 2012, so please do not message me for tech support. Use this thread instead, which is its intended purpose. Thanks!
To root your device through CWM:
This step is only if you want to root the stock firmware that is currently on your device. If you are going to flash a ROM like CyanogenMod, then you can skip this section, since most custom ROMs already have root installed.
You need to first download root_sgs2hdbell.zip from the Dev-Host site linked above. Copy it to your device's internal or external SD card.
Then go back into CWM and flash the ZIP. You should now be rooted, you don't need to do anything else to your stock ROM.
Factory/stock firmware images, custom ROMs, change log, source code, acknowledgements, etc.:
See next two posts!
.
Change Log
Version 6.0.1.1 (the first Touch version for SGH-I757; August 16, 2012)
Built using ClockworkMod Recovery Builder (also required hex-edit of ramdisk load address)
Version 6.0.1.1 (Non-Touch version - August 15, 2012)
Latest version of CWM, updated from CyanogenMod sources
Version 5.5.0.4b (July 3, 2012)
In kernel, enabled CONFIG_MMC_BLOCK_BOUNCE which helps with SD read/write performance (may fix SD card flashing issues)
Version 5.5.0.4a (June 22, 2012)
Using ICS kernel based off MSM 8660 sources
Fixed issue where if someone uses an app to reboot into recovery, the device will never be able to reboot back into system (would always boot into recovery unless you re-flash recovery image). "Boot to recovery" apps will now work.
Contains proper device name info (SGH-I757M, not full_galaxys2hdbell)
Version 5.5.0.4 (June 12, 2012)
First build based off stock Gingerbread kernel
Custom ROMs:
There is already development undergoing for this device:
If you only want a rooted stock Gingerbread or ICS ROM with all the Bell apps removed, see the Dev-Host link in post #1, under the SGS2 HD LTE / Other Custom ROMs folder.
markdexter's DexROM - strips down the above ROM even more and adds a theme
Try my CyanogenMod 9 - this is stock Android 4.0 (Ice Cream Sandwich). It is good enough to use every day.
Try my CyanogenMod 10 - this is stock Android 4.1 (Jelly Bean).
Copy the ROM to your SD card and then go back into CWM and flash the ZIP.
Factory images and related files:
If you want to reset the flash counter found in Download Mode so that it doesn't mention a custom ROM was flashed or was flashed multiple times, then try this mod, courtesy of mangelok: Flash counter reset
For the original stock 2.3.6 and 4.0.4 firmware for SGH-I757M, see the Dev-Host link in post #1 - under the "SGS2 HD LTE / factory images" folder. You can flash this in Odin to restore your phone to original state. Just do a factory reset of your phone, then open Odin and place the tar.md5 file in the PDA slot and then start the flash. This also flashes the stock recovery image.
If you just want the Bell ICS modem (MUGLH2), it is found in the 'factory images' folder. You need to flash this under CWM.
There is also a stock 2.3.6 firmware + stock recovery, which has Superuser (root) files injected in it, so it's already rooted (but without CWM). It's at the Dev-Host link in post #1 (rooted_I757MUGLCA_I757MOYCLCA_I757MUGLCA_HOME .tar)
If you just want to go back to stock recovery, download the stock recovery image (stock_gb_recovery.tar) at the Dev-Host link and repeat the steps in post #1 for installing the recovery image (but this time use stock recovery instead of custom recovery).
More discussion:
Participate in the Bell Samsung Galaxy SII HD LTE user group on xda-developers
Other useful links:
Mount points and other info for this device
Original Discussion on rooting this device
All my source files for this device at GitHub, including those for ClockworkMod, ICS kernel, and CM9 device tree ("celoxhd").
Android Kitchen by dsixda - SGH-I757M is now supported
Article about this recovery image on the XDA portal - by willverduzco
Acknowledgements:
Thanks to Koush (for ClockworkMod), Cyanogen, Chainfire (inspiration), rxulan (link to rooted stock firmware), adlx.xda (for the custom graphics help), testers (you know who you are) and my awesome Twitter followers (continual help and encouragement).
One more
Link to Modded Bell Rom Thread: http://forum.xda-developers.com/showthread.php?p=27331138#post27331138
Android 4.0?
Is it possible that you could make an android 4.0 Rom for this device since bell seems to take their sweet time rolling out ICS to phones. Also thanks for porting CWM to my phone I've been looking everywhere for it.
B.Moreira said:
Is it possible that you could make an android 4.0 Rom for this device since bell seems to take their sweet time rolling out ICS to phones. Also thanks for porting CWM to my phone I've been looking everywhere for it.
Click to expand...
Click to collapse
Bell will likely release it at the end of the month, I'm probably not able to do any work on CM9 due to health and family reasons.
dsixda said:
Bell will likely release it at the end of the month, I'm probably not able to do any work on CM9 due to health and family reasons.
Click to expand...
Click to collapse
Alright, that's ok. Ill just make a thread for custom roms for this phone.
B.Moreira said:
Alright, that's ok. Ill just make a thread for custom roms for this phone.
Click to expand...
Click to collapse
You probably won't get a stable ICS custom rom until Samsung releases the sources for the phone. Also you should ask that question in the Q&A section of the forum not in General device section.
Thanks! love this =D
Will flashing the recovery menu to my bell s2 help me root and unlock it easily like superclick or would i still have to flash my russian rom? Thank you for the work though.
singh99 said:
Will flashing the recovery menu to my bell s2 help me root and unlock it easily like superclick or would i still have to flash my russian rom? Thank you for the work though.
Click to expand...
Click to collapse
Make sure you read the section in post #1 for rooting the S2 HD. Just flash the ZIP, you don't need the Russian ROM. Do not flash this to the old Bell S2, this is for the HD LTE variant.
Hi dsixda, can I use this CWM recovery for SII HD LTE model E120L (korea version)
theanh6 said:
Hi dsixda, can I use this CWM recovery for SII HD LTE model E120L (korea version)
Click to expand...
Click to collapse
Refer to the big warning on page 1 directly above the download link...
I have no idea what will happen.
If someone here as the Bell SGH-I757M update for Android 4.0 (from Kies or stock), please get in touch with me via PM or Twitter. There is a test ROM floating around.
has it been released??
Yes if u have a dev unit the Kies will detect it and show update to 4.0
Oh, pretty sure mine isnt a dev unit
Dsixda not too sure if you seen this!!
http://www.xda-developers.com/tag/samsung-galaxy-s-ii-hd-lte/
markdexter said:
Dsixda not too sure if you seen this!!
http://www.xda-developers.com/tag/samsung-galaxy-s-ii-hd-lte/
Click to expand...
Click to collapse
Someone's been living under a rock..
It's already linked on post #1
Related
Perka´s And flip360´s Clean Install Guide And Package.
Warning!
If you do not follow the guide exactly you might brick your phone!
This guide is only for Samsung Galaxy S GT-I9000
If you do not know what 3 button combo or recovery is, read this please.
If you have Captivate Here you have a guide.
We are not responsible for bricking anybody’s phone!
If it happens we will try to help you, but remember we are doing this for free!
You do not have to do all Sections, please read what each Section is for.
IMPORTANT! – You need to read the guide before doing it, and use the files provided.
Section A If you have 2.1, 2.2, 2.2.1
Section B is for flashing stock 2.1, to get a fresh clean install.
Section C is for flashing our update.zip from 2:e recovery (It is a renamed Kitchen Rom) Log here.
Section D Another way to get to Kitchen Rom from stock 2.1 with 2e recovery, does not work with Stock Froyo 2.2 or 2.2.1.
Section E is a guide to Magical Rom Kitchen.
Section F is a How to CWM update.zip guide, (to get CWM, only works in 2e recovery 2.1 Eclair)
Before you begin with the flashing process, make sure that you:
Samsung drivers installed on your computer.
Have backups.(When you restore your backups, DO NOT restore system settings.)
Do not have any lag fix applied.(If you are going to flash stock with pit, no need to disable lag fix)
Phone battery is fully charged.
You don´t have Kies running.
We strongly urge you to read through the whole guide first before attempting any of this,
and sticking to our reference, here is the files that you will need before attempting to flash your Samsung Galaxy S GT-I9000.
Download Section.
Odin v 1.3
Samsung USB Drivers.
Driver x64
Driver x86
For Section A
Speedmod Kernel K13b
For Section B
GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM_Odin_Csc_Pit.512.zip
or
GT-I9000_I9000XWJM9_I9000XXJM4_CODE-MODEM_Odin_Csc_Pit.512.zip
For Section C
The renamed Kitchen Rom (update.zip) Log file This is used if you get stuck on GT screen.
For Section D
Z4Root
Sgs Kernel Flasher
Speedmod Kernel choose the CWM.
Qr codes in Post 2
For Section E
Cook your favourite Kitchen Rom in Magical ROM Kitchen
For Section F
ClockWorkMode update.zip
Preparations
To begin with, download and extract all these files mentioned above to a convenient location, preferably on your desktop. Once you have all the files in place, launch Odin as administrator. On your device end, make sure that you have disabled any lag fix, if applied earlier.
Ensure that the drivers for your SGS are installed on your computer.
If you have Kies already installed on your machine, the drivers are already in place. If Kies is running shut it down.
Power off your phone.
Put your Galaxy S in download mode by pressing and holding the Volume Down + Home + Power keys at the same time.
You will see a yellow symbol and the words ‘Downloading’ once the phone has gone into download mode. That’s it, we’re ready to begin the flashing sequence.
Section A
Before flashing the Speedmod Kernel, put your Kitchen Rom on your internal sd card.
Flashing a Speedmod Kernel Guide here.
When flashing on 2.1, you get stuck on GT-screen, dont worry its normal, just pull battery and enter recovery.
Now go to Section E
Section B
Flashing stock firmware
Make sure you don´t have Kies running, and your phone is off, do not connect it now.
1.Start Odin
2.In PIT, load the 512.PIT file.
3.For PDA, select the CODE file.
4.For PHONE, select the MODEM file.
5.For CSC select the CSC file.
6.Make sure that the Re-partition box is checked.
7.Put your phone in download mode. (Volume down + power button + home button )
8.Connect your phone to your PC via the USB cable. It will install the drivers, or if they are already installed, you will see ‘Added’ in Odin’s message box . A COM port will also become visible.
9.Again make sure that all the selections in Odin’s interface are correct. Press the Start button when verified.
The flashing sequence will begin, and you will see several messages in Odin. Make sure that the phone does not disconnect during this time, as it may brick your device permanently. Once the flashing sequence has completed, Odin will give a ‘Completed’ message in the Message box, and a green PASS will appear on top.
Your device will automatically reboot at this point.
Congratulations! You have successfully completed stage one of the process, and now you’re running the XWJM8 or JM9 2.1 Éclair firmware.
Section A is useful if you just want to revert back to factory stock 2.1 (warranty, repairs, etc.)
Now you can do Section A ,D or F
Section C
Flashing the update.zip, this is used if you have problems installing your Kitchen Rom
Copy the update.zip (it is a renamed Kitchen Rom Log) to your Internal Sd card.
Shut off the phone and reboot to recovery (Volume UP + Home + Power) and do a FACTORY RESET.
Then choose Install update.zip from the recovery, let it install and reboot. When the phone has booted, shut the phone off and enter recovery (Volume UP + Home + Power) and then choose Install update.zip from the recovery, let it install and reboot.
It´s not a typo you need to do it twice.
All done! Now you have a basic Kitchen Rom containing CWM and all you need to flash a custom ROM.
If you want to stay with this Rom, you can enter the Magical ROM Kitchen and make a update.zip with the apps you want to add, and flash it in cwm. If you want to uninstall something you can do it with Titanium.
Now you can go to Section E
Section D
Another way to get to Kitchen Rom from stock 2.1 with 2e recovery, does not work with Stock Froyo 2.2 or 2.2.1.
When you have the apps and the Kernel needed for this Section,
1.Install the apps.
2.Cook your Kitchen Rom and put it on your internal sd card. (see section E how to do that)
3.If you did not download the kernel with your phone,(qr codes in post 2) put it on your internal sd card.
4.Root with Z4Root.
5.Flash the Speedmod Kernel with Sgs Kernel Flasher (only v1.5.9 or newer)(Atm you will get stuck on GT screen due to mismatch between kernel/firmware versions if you try normal booting)
6.Enter recovery
7.Factory reset
8.Install zip from sd card
9.Choose zip from sd card
10.Install the Kitchen Rom
11.Reboot
Section E
Flashing a Kitchen Rom if/when you have clockworkmode
Here you have a app guide made by marcedli Xda
And here you have a nice Kitchen walk-trough with screens: Link.
This is the steps you need to do.
1.Place Kitchen Rom on internal sd card
2.Enter recovery
3.Factory reset (if you install new base Rom OR the previous Rom had a voodoo kernel AND you want to wipe)
4.Install zip from sd card
5.Choose zip from sd card
6.Install the Kitchen Rom
7.Reboot
Section F
How to get CWM with CWM update.zip (only works in 2e recovery 2.1 Eclair)
1.Place your Kitchen Rom on your internal sd card, that you generated in the Kitchen
2.Place the CWM update.zip on your internal sd card that you downloaded from download Section
3.Power down your phone and enter recovery (Volume up + power button + home button )
4.Choose apply sdcard:update.zip, now you will end up in recovery again, so choose apply sdcard:update.zip and you will have CWM.
5. Now go to Section E step nr 3.
If you still have any questions please log in to Kitchen`s Irc support channel. (in irc type !help)
Webchat!
Please rate or comment.
This guide was made and tested by,
flip360 Xda
Perka Xda
Beerfund
Links and QR codes.
Do you need a file? Perka´s File Stash!
Black Android Theme by Pele78 (imo the best out there!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need help with modem, csc, and other stuff, please go to Doc´s Irc channel and type !help and you will find what you are looking for, Click this text.
Guide in PDF
Perka´s File Stash
Adobe Reader
Z4Root
Sgs Kernel Flasher
Speedmod Kernel
Credit Goes To The Doc Team!
Do you want free dropbox cloud space? Use this link to sign up and you get 2gig + 250mb space for free (and I get 250mb) Thx.
gday.. just to clarify...does this suggest therefore to flash back to jm8 2.1 prior to flashing to a Doc Rom??
i have asked this in another post, but say for example you are already running another ROM that comes with all the bells & whistles (eg cwm, optional lagfix, root, sgs tools themes etc)..
would the user need to go back to jm8?
cheers
skuzy said:
gday.. just to clarify...does this suggest therefore to flash back to jm8 2.1 prior to flashing to a Doc Rom??
i have asked this in another post, but say for example you are already running another ROM that comes with all the bells & whistles (eg cwm, optional lagfix, root, sgs tools themes etc)..
would the user need to go back to jm8?
cheers
Click to expand...
Click to collapse
If you have problems flashing, use this guide, if you already have cwm recovery and can flash custom roms you dont need to do this guide.
thanks for confirming.!
Can this be used to flash all modded CWM ROMs? I think so. You can check & modify the topic accordingly.
ragin said:
Can this be used to flash all modded CWM ROMs? I think so. You can check & modify the topic accordingly.
Click to expand...
Click to collapse
i think so. We will test this out and give feedback
flip360 said:
i think so. We will test this out and give feedback
Click to expand...
Click to collapse
You mention 502 pit. Did you mean 512 or 503?
ragin said:
You mention 502 pit. Did you mean 512 or 503?
Click to expand...
Click to collapse
yes 512pit file. sorry typo
Huh? Isn't Doc's rom a CWM Rom? You can't flash those as a update.zip can you?
snapper.fishes said:
Huh? Isn't Doc's rom a CWM Rom? You can't flash those as a update.zip can you?
Click to expand...
Click to collapse
Yes Doc`s rom is coupled with CWM yes, but stock 2.1 also. try it
There´s an update coming to you soon from me and flip360
Teaser
http://www.swedroid.se/forum/showthread.php?p=428217#post428217
Updated enjoy.
Sorry, but to quote DocRambone's words:
"Wrong Section to post".
Edit: Thread reported.
Nice guide, thanks!
Is it also valid if you want to upgrade from an older Froyo rom like Doc 6.0 ?
If you start directly from stage 2 beeing on a stock rom, you have recovery 3e which won't let you flash unsigned packages (like the renamed DocRom "update.zip".
Or as I missing something ?
-Loom- said:
Nice guide, thanks!
Is it also valid if you want to upgrade from an older 2.1 rom like Doc 6.0 ?
In Docs own installation guide he stated to install a clean JP9 base before, do the usual CWM install through update.zip etc ..
And if you start directly from stage 2 beeing on a stock rom, you have recovery 3e which won't let you flash unsigned packages (like the renamed DocRom "update.zip".
Or as I missing something ?
Click to expand...
Click to collapse
If you are on a Doc rom do stage 3.
2.1 has 2:e recovery so it can flash unsigned zips.
Does not work if you have 3e recovery.
Doc advised to install a clean JM9 base rom before upgrading to a romkitchen rom.
But in stage 3 you wrote to just install the kitchen rom from CWM. Regardless what DocRom was in use before ?
-Loom- said:
Doc advised to install a clean JM9 base rom before upgrading to a romkitchen rom.
But in stage 3 you wrote to just install the kitchen rom from CWM. Regardless what DocRom was in use before ?
Click to expand...
Click to collapse
yes my good man
flip360 said:
[FONT=Book Antiqua, serif]For Stage 2[/FONT]
[FONT=Book Antiqua, serif]The renamed Doc Rom [/FONT][FONT=Book Antiqua, serif](update.zip) [/FONT][FONT=Book Antiqua, serif]Log file[/FONT]
[FONT=Book Antiqua, serif]Samsung USB Drivers.[/FONT]
[FONT=Book Antiqua, serif]Driver x64[/FONT]
[FONT=Book Antiqua, serif]Driver x86[/FONT]
Click to expand...
Click to collapse
Got these drivers package ... But which one is used for my SGS on W7 x64 please ? It doesn't find it by istself ?
Wendigogo said:
Got these drivers package ... But which one is used for my SGS on W7 x64 please ? It doesn't find it by istself ?
Click to expand...
Click to collapse
the x64 one, i think it does throught win driver management.
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
sfetaz said:
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Click to expand...
Click to collapse
I hope there is program like that
Backwardsblade said:
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think so.
I try but don't find the device
frederuco said:
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
Click to expand...
Click to collapse
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
1090t said:
I hope there is program like that
I don't think so.
I try but don't find the device
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
Click to expand...
Click to collapse
unzip first. inside another zip file.
goodintentions said:
unzip first. inside another zip file.
Click to expand...
Click to collapse
Yah, i do that
.........................
why is the only rom i can install and work is the: Android Revolution HD ?!
1090t said:
why is the only rom i can install and work is the: Android Revolution HD ?!
Click to expand...
Click to collapse
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
1090t said:
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
Click to expand...
Click to collapse
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
goodintentions said:
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
Click to expand...
Click to collapse
it doesn't work i just wait there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is that right why to boot in to rom (from cold-boot) ?
horndroid said:
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
Click to expand...
Click to collapse
I try many time with these the Recovery still same
even with the old version ..nothing
1090t said:
it doesn't work i just wait there
is that right why to boot in to rom (from cold-boot) ?
I try many time with these the Recovery still same
even with the old version ..nothing
Click to expand...
Click to collapse
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
feisty_noodle said:
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
Click to expand...
Click to collapse
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
The op's problem is very similar to this one http://forum.xda-developers.com/showthread.php?t=1549062 which has been resolved.
goodintentions said:
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
Click to expand...
Click to collapse
You are right, I may have misinterpreted the OP.
Still, I think the solution is the same.
When the device boots into recovery and can be cold-booted into ROM, the most likely culprit is the 'boot-recovery' flag which is set in the /misc partition. When the system sees that upon boot, it goes straight into recovery.
It should be the recovery's job to blank out that flag at some point, but CWM 5.5.0.4 (and, perhaps this recovery the OP is using) does not do this.
So, the solution is to reset it with the 'echo ...' command (or blanking out the first few bytes of /dev/block/mmcblk0p3) in shell.
My suggestion is very conservative.
I'll gave try and let u know
when i connect to the computer nothing shows up
even the Asus sync don't found it
I'll gave try on Linux
any help
How to upgrade from Gingerbread WF07 to a Jelly Bean ROM on the SHW M110S
Basic Considerations that will help you to restore your current ROM
First make a Backup of your current ROM, such that you can return to it, IF the Jelly Bean ROM is not what you expected it to be. How?
a) When Using a tegrak Kernel on the M110S , you can get this done on the bootup screen , by entering it and making a system and also a dbdata/data backup of your phone, which can be restored by using the terak kernel again IF WF07 ROM is what suits you best.
Your backup will be placed in the Tegrak Folder in the Internal SD card...so save this to your PC or external SD card for safe keeping.
b) When using a Speedmod kernel, you need to enter recovery first to make a nandroid backup of your system and data
Your Backup will be placed in the ClockWorkMod Folder of your SD card. Which can be restored by using the speedMod kernel again IF WF07 ROM is what you desire.
None of these Kernels can be used for Jelly Bean ROM, and you need to use a Version 5 CWM (ClockWorkMOD) recovery, to flash the Jelly Bean or ICS ROM direct from your SD card...as such the first thing you need to do is change the Recovery on your M110S to a version 5 ClockWorkMOD.
Second Backup your efs folder, why? read this. How? read this
What you should know about this Jelly Bean ROM on the M110S
a) It may take from 3 to five minutes for the ROM you flashed to stabilze, so try to be patient or you will have a non responsive phone in your hands, even when the ROM is stable.
b) When ever certain functions do not seem to work initially...like unable to connect to your WIFI, network etc just reboot phone.
c) Poor response may be due to settings or permissions that need to be fixed, which can be done on your settings menu or in the advanced menu of your recovery ...so you must have ample knowledge of the numerous features the Jelly Bean settings menu has.
The Jelly Bean ROM's for Korean Galaxy S (SHW M110S) that have little to NO issues at the moment are
Common Issue in Jelly Bean being having NO Ringtone only vibration
Typhoonoid aokp verion 2.1.2 or here
Typhoonoid paranoid version 1.1
CM 10 All Fixed
Provisionmod All Fixed
JBean 4.2 under construction here only for testers to verify bugs
Reminder, What you do with your Phone is your own responsibility, so do it at your own risk. Always ensure your Battery is fully Charged prior to flashing any phone
This is the basic procedure for Jelly Bean upgrade
1) Download the CWM Recovery.tar ( Attached below), the ROM's come in .zip format ( it can be as many as you wish, for you to test them out, one after the other) and Place them in a Folder (create and name it as you wish) on your SD Card Also Download the Gapps.zip (Google apps) File that need to be flashed after flashing the ROM. ( So it will always be two packages to flash, in order to get your phone functioning)
Download:-
a) CWM Version 5.0 Recovery attached below
b) Rom of your choosing from here or here or here Zip file includes ROM & Kernel (do not unzip)
c) Gapps Here (do not unzip)
d) Ringtone Fix here (Tested not working on M110S)
e) New 4.1.2 Kernel use Odin to flash when using older ROM
2) Flash the version 5 and up CWM recovery on your Phone, How?
Put your phone into download mode, Fireup Odin3 on your PC, connect to Odin3 with USB cable, select CWM Ver.5.0 recovery.tar under PDA and Flash it. Ensure you do not reboot the phone by "UNTICK" reboot in Odin3 such that it will not power ON after Flashing, in case it does power ON, just pull out Battery , press power button for 30 seconds and insert battery again
3) After flashing recovery with Odin, You can enter " Recovery Mode" by press VolumedownKey+PowerKey+HomeKey. You do this every-time you want to switch to a JellyBean or iCS ROM or to utilize the many features this recovery has, like Backup/restore/fix permissions and mostly to do the full wipes (NEEDED to be done every time you want to SWITCH ROMS) etc
4) Once in CWM Recovery you do the Full wipes (use your volume keys to move up or down in the recovery menu to select and the power key to execute that command).
The undermentioned wipes need to be done and will constitute a FULL Wipe of your Phone but your SD card will not be fully formatted as such your Images and other non system files will remain as is.
a) Wipe data / Factory reset
b) Wipe cache
c) Enter advanced and wipe dalvic Cache
Once the full wipes are done,
5) You now choose the ROM you placed in your SD card by selecting "Install zip from sdcard" which will lead you to "choose zip from sdcard", which will take you to all the folders you have on your SD Card..scroll down to where you placed the downloaded files and select it
Once selected the ROM will be Flashed on to your phone, so wait till it says "install completed" Now you do the same selection process again (Step 5) to select the Gapps file and wait till it says "Install completed"
6) That's it, Now select "Reboot system Now".
Now the ROM has been installed on your phone, so let it boot up and you can repeat this procedure to switch again and again till you have the best ROM of your choosing.
Solutions to solve problems, if any
In the event that it fails to boot-up or you placed a wrong ROM that caused a boot loop or any other problem, just look in My Android Solutions , IF you cannot enter Recovery mode to flash another ROM.
or
You can also use Odin3 to Flash a Gingerbread ROM in Download mode and use your First backup ( made by Tegrak or speedMod) to return your phone to its original state.
Ringtone Codec from this post unfortunately it seems to fail in fixing the Ringtone issue but no harm done in installing this codec
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on any device.
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
Final Advice
IF you like the ROM you had just installed and after doing all the tweaks and adjustments you would like to try another ROM, just get back into your CWM recovery , scroll down to "backup and restore" and back it up. Such that you can restore it, if your next selection is below expectations. or you wish to tweak it further at some other time. You can have many ROM's backed up and restored whenever you like...just remember on what date you backed it up.
You , YES! you are an " Android ".
You Must watch this documentary concerning your privacy Terms & Conditions we agree to
If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Screen Shots of Typhoonoid aokp
Screen Shots of Paranoid
Typhoonoid by ODIN? Tegrek after Typhoonoid?
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?
md11980 said:
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?
Click to expand...
Click to collapse
Nope, you MUST use the Version 5 CWM recovery to flash ICS or Jellybean ROM's and Nope you cannot use tegrak anymore, and lag fix (sort of ) can be done with seeder app already included in the ROM
soft bricked
xsenman said:
Screen Shots of Paranoid
Click to expand...
Click to collapse
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?
asukaragnaboy said:
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?
Click to expand...
Click to collapse
means still in download mode and needs a full flash of ROM or Kernel or recovery you had earlier attempted to flash
upgrade screenshot http://forum.xda-developers.com/attachment.php?attachmentid=2147778&d=1374970741
On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Sent from my GT-I9070 using xda app-developers app
shaikhsumair99 said:
On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Click to expand...
Click to collapse
Not too sure, the others can achieve swap support, but give it a try, it pretty easy to change ROMS and test out, which can do what lidroid screen shots may be on their website here http://bbs.lidroid.com/forum.php?mod=viewthread&tid=110092&highlight=lidroid+wc13
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app
shaikhsumair99 said:
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete
xsenman said:
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete
Click to expand...
Click to collapse
Sorry for asking again but i want a cm 7.2
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Is this cm 7.2 is this rom has bugs
Please tell the bugs.
Thanks for helping bro.
Sent from my GT-I9070 using xda app-developers app
shaikhsumair99 said:
Is this cm 7.2 is this rom has bugs
Click to expand...
Click to collapse
NO. its ver 4.1, meaning Jelly Bean, CM 7.2 is gingerbread/ICS combo, try looking in the links given in OP, you need to go into their parent directory and it will clearly state CM 7.2. CM 9 would be ICS , CM 10 would be Jelly Bean.
unfortunately I Have not tested them , so unable to tell you the bugs in each of them.
Oops i am sorry posted wrong link.
I know that that cm 10 is jb and 9 ics
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/Sayanogen/M110S CM7.2(TOUCHWIZ4.0).tar
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Sent from my GT-I9070 using xda app-developers app
shaikhsumair99 said:
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Click to expand...
Click to collapse
like i said earlier , have little knowledge about its current development or bugs, as far as I know, they stopped short of fixing bugs when CM 10 came into the picture. So best you test it out.
visit PIT STOP for 7.2 version 3 plus guide (click on original post to see screenshots and latest info) and 7.2 perfect version download from here
It means there are no bugs in 7.2cm sms fixed.zip
And there is swap support.
Sent from my GT-I9070 using xda app-developers app
shaikhsumair99 said:
It means there are no bugs in 7.2cm sms fixed.zip And there is swap support.
Click to expand...
Click to collapse
I hope so, that's what perfect should mean but may mean different in Korea so check it out.
xsenman said:
I hope so, that's what perfect should mean but may mean different in Korea so check it out.
Click to expand...
Click to collapse
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Sent from my GT-I9070 using xda app-developers app
hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?
shaikhsumair99 said:
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Click to expand...
Click to collapse
looks like provision made a new kernel even for Jellybean, so it can flashed using odin3 after flashing ROM & gapps. oc means its an overclocked version
swiftcity1305 said:
hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?
Click to expand...
Click to collapse
you use the one that is included in the ROM package. and can be updated with new version of that kernel later, you cannot use gingerbread kernels like (tegrak or speedmod)
[GUIDE] Flash Official JB 4.1.2 Firmware on P6810 Wi-Fi Device
Sick and tired of Samsung ignoring the official JB 4.1.2 update for our much maligned and forgotten device?
Well, you’re in luck, this guide will effectively turn your P6800 Wi-Fi device into a P6800-GSM/3G model. We do this by changing the device partition layout and then flashing P6800 firmware with Odin.
Of course, due to hardware differences, you won’t have a working radio/modem. Also, some unneeded system apk's will need to be removed and the UI will also need some cosmetic changes etc, but it's a start.
WARNING & DISCLAIMER: I am not responsible, YOU are! You can probably forget about your warranty. This will wipe everything and increase your flash counter too !
PRE-FLASH REQUIREMENTS
1. Internal sdcard contents backed up off device
2. Any apps & data (is you wish) backed up off device
DOWNLOAD REQUIREMENTS
1. P6810 Wi-Fi model with a FULL battery
2. Windows PC
3. P6800_3G_16G.pit
4. Download P6800 JB 4.1.2 DXMD3 firmware from:
a) Samsung-updates.com
b) sammobile.com5. Odin 3.07
6. Samsung drivers
METHOD
1. Extract P6800_3G_16G.pit & P6800 firmware so you just have .pit & .tar files
2. Drivers
a) Uninstall or disable KIES
b) Install Samsung drivers & reboot PC3. Run Odin 3.07 & install
[PIT] = P6800_3G_16G.pit
[PDA] = P6800 official JB 4.1.2 firmware .tar file4. Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue5. Connect device to PC via USB cable
6. ID:COM should change colour in Odin 3.07
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Click [START] and watch the magic
8. If you get a screen message with button [Reset perangkat] (Reset device), just tap it
NEW PARTITION LAYOUT
FURTHER RECOMMENDATIONS
*. Flash TWRP 2.6.1 in Odin [PDA]
*. Flash P6800 JB 4.1.2 SkyHigh kernel
MY P6810 RUNNING EROBOT ROM + SKYHIGH KERNEL
GUIDE: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4 IN POST #2
.
[guide] downgrade p6810 (wifi) from official jb 4.1.2 to ics 4.0.4
[GUIDE] DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4
WARNING & DISCLAIMER: I am not responsible, YOU are! You can probably forget about your warranty. This will wipe everything and increase your flash counter too !
PRE-FLASH REQUIREMENTS
1. Internal sdcard contents backed up off device
2. Any apps & data (is you wish) backed up off device
DOWNLOAD REQUIREMENTS
1. P6810 Wi-Fi model with a FULL battery
2. Windows PC
3. P6810_WIFI_16G.pit
4. Download P6810 ICS 4.0.4 firmware from:
a) Samsung-updates.com
b) sammobile.com5. Odin 3.07
6. Samsung drivers
7. P6810 TWRP Recovery
METHOD
1. Extract P6100_WIFI_16G.pit & P6100 firmware so you just have .pit & .tar (or .tar.md5) files
2. Drivers
a) Uninstall or disable KIES
b) Install Samsung drivers & reboot PC3. Run Odin 3.07 & load
[PIT] = P6810_WIFI_16G.pit
[PDA] = P6810 official ICS 4.0.4 firmware .tar file
Uncheck [AUTO REBOOT]
[/IMG]
4. Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue5. Connect device to PC via USB cable
6. Odin ID:COM should change colour
7. Click [START]
8. Success = “RESET”
* Factory Reset is required for boot
- ICS device is known the be affected by SuperBrick (aka Brick-Bug)
- Those trolls that want to debate this can debate themselves out of this thread !
- Instead, we do this the "SAFE" way by using a custom recovery9. Disconnect USB cable
10. Reboot into Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue11. Click [RESET] button in Odin and load
[PDA] = P6810 TWRP Recovery.tar
Uncheck [Auto restart]12. Connect device to PC via USB cable
13. Odin ID:COM should change colour
14. Click [START]
15. Success = “RESET”
16. Enter Recovery Mode
a) Disconnect USB cable
b) Hold volume UP + Power until enter TWRP menu (release only when in recovery)
c) If unsuccessful first time, release buttons & try again
d) TWRP Recovery may give message “unable to mount ‘/data’” & auto reboot17. Enter Recovery Mode again
a) Wipe – format data (type “yes”)
b) ignore message " 'unable to mount ‘/data' "
c) Reboot System
d) Tap [Do Not Install] SuperSU18. Device will boot – wait about 5 mins
* Setup ROM and enjoy
* Your device & partitions are now restored to original P6810 ICS 4.0.4
.
You are a genius!
I'll give it a try as soon as I can!
Thanks!
furius said:
You are a genius!
I'll give it a try as soon as I can!
Thanks!
Click to expand...
Click to collapse
Let me know how you go. You should be fine as long as you meet all the requirements and follow the steps.
Sent from my GT-I9500 using XDA Premium 4 mobile app
UpInTheAir said:
Let me know how you go. You should be fine as long as you meet all the requirements and follow the steps.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do we need to flash p6800 recovery? Due to different layout partition? So if we need to go back to p6810 (through restore from backup) we need to flash p6810 recovery first?
Inviato dal mio HTC One X utilizzando Tapatalk
furius said:
Why do we need to flash p6800 recovery? Due to different layout partition? So if we need to go back to p6810 (through restore from backup) we need to flash p6810 recovery first?
Inviato dal mio HTC One X utilizzando Tapatalk
Click to expand...
Click to collapse
After flash the P6800 firmware, you don't need to flash any custom recovery. It's just a recommendation and also reminder to flash stuff for P6800. You need it if you wish to flash eRobot ROM.
TO RETURN TO P6810 PARTITIONS & FIRMWARE
Follow the above steps but substitute Step #3
A - P6810_WIFI_16G.pit + bodivas P6810 JB ROM .tar file + then flash P6810 CWM/TWRP Recovery & FULL nandroid restore
To be clearer: If you need to go back,
1. Flash P6810 PIT + bodivas ROM in Odin
2. Let ROM boot
3. Flash P6810 CWM/TWRP Recovery in Odin and then FULL restore the ICS Nandroid
Don't forget to keep the Nandroid backup on your external sdcard, internal will get wiped !
Sent from my GT-I9500 using XDA Premium 4 mobile app
Is it completely impossible to flash back to stock using Mobile odin from bodivas ROM?
Sent from my GT-P6810 using XDA Premium HD app
karlsbug said:
Is it completely impossible to flash back to stock using Mobile odin from bodivas ROM?
Sent from my GT-P6810 using XDA Premium HD app
Click to expand...
Click to collapse
I don't know, but haven't found a way with PC Odin yet. Still a few things to try later on using old ICS 4.0.4 bootloader etc.
The only successful method so far is the Nandroid way.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Cheers UITA, btw usb otg is now working with your your latest kernel. Excellent!
Karlsbug.
Sent from my E330 using xda app-developers app
Update. It seems I have wifi issues with v1.6.0. I unpacked the kernel from bodivas rom, reflashed, seems OK, now. Wifi would only work if I turned it off and on again. No usb otg now:crying:
karlsbug said:
Cheers UITA, btw usb otg is now working with your your latest kernel. Excellent!
Karlsbug.
Sent from my E330 using xda app-developers app
Click to expand...
Click to collapse
karlsbug1971 said:
Update. It seems I have wifi issues with v1.6.0. I unpacked the kernel from bodivas rom, reflashed, seems OK, now. Wifi would only work if I turned it off and on again. No usb otg now:crying:
Click to expand...
Click to collapse
I think you're in the wrong thread.......
Anyway, I tested all OK on bodivas stock ROM. Had no issues the past day. Backup your data and save off device. Reflash his stock ROM (no multi-windows) and try again.
BTW, I have managed to revert to ICS 4.0.4 without using nandroid. :highfive:
I'll post the method here later today. I have some business today.
From now on, I'll be using eRobot, but must make a flashable script to uninstall some non-related feartures and apk's etc. I'll even attempt later on to modify some apks to get rid of some unneeded options in settings menu.
Guide: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4
Full Guide: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4 in Post #2.
I don't use Mobile Odin, but don't think it's possible.....
Now enjoy your JB "P6800" or ICS P6810
Cheers,
UITA
Edit: Nearly forgot, thanks bodivas for suggesting Factory Reset.
I know its the wrong thread but i cant post inthe ROM sorry.
Atb
Sent from my GT-P6810 using XDA Premium HD app
After flashing JB, I don't think flashing CWM or TWRP is working properly. I get successful flash of P6800 TWRP, but fails to boot into recovery volume up + power. Flashing the P6810 TWRP recovery partly works, but does not show the internal sdcard. Maybe something to do with bootloader still showing P6810 ?
Will take a look later.
Sent from my GT-I9500 using XDA Premium 4 mobile app
BUG - Can't quite get any custom recovery flashed properly on JB
Edit: Just flash TWRP 2.6.1.0 in Odin [PDA]. Done
In TWRP recovery:
Internal sdcard = emmc
External sdcard = sdcard
My P6810 IS NOW running eRobot ROM + SkyHigh kernel :
EDIT : STILL A FLAW IN THE "RECOVBERY PROCESS". SOME RECOVERIES STILL FAIL TO FLASH AND OTHERS DON'T MOUNT /RECOGNISE ALL PARTITONS. THE TWRP 6.1.0 DOES NOT BACK UP THE PRELOAD PARTTION, WHICH IS A REQUIREMENT TO RESTORE CORRECTLY.
Running erobot rom and skyhigh kernel on my P6810 too!
I followed your instruction and all was fine! All is working well, I'll report more feedback in the next days ...
Thanks UpInTheAir
One more thing: from your screen shot you are using tablet UI while erobot has phablet UI ... I tried to switch to tablet UI changing lcd density but touchwiz continues to crash ... how did you get it working?
And again ... is there the possibility to have the multi window feature as in bodivas rom?
furius said:
One more thing: from your screen shot you are using tablet UI while erobot has phablet UI ... I tried to switch to tablet UI changing lcd density but touchwiz continues to crash ... how did you get it working?
And again ... is there the possibility to have the multi window feature as in bodivas rom?
Click to expand...
Click to collapse
I was running eRobot v1 , Phablet is v2.3P. I really do suggest a full wipe immediately prior to flash (if ROM doesn't automatically). I haven't flashed v2.3P yet, but have a read through the eRobot thread on the development section. Please let me know what you find out. Edit: jhust flashed it, working ok
http://erobotrom.blogspot.com/p/erobot-rom-for-g-tab-77.html?m=1
I have permission from eRobot to modify and release his ROM at XDA. I was going to do tablet UI, but now doing Phablet instead. I am working on a Aroma installer version to flash in custom recovery. As per my previous post, custom recoveries aren't working 100% with preload not being able to backup or restored. We need this for 4.1.2.
Although the guide works flawlessly, the end useability is not quite there with custom recovery not quite working as expected.
If I can't get this working easily for user simplicity, the eRobot ROM will be built/modded for P6810 partitions instead. So the only requirement will be flashing bodivas base ROM and custom P6810 recovery from daniel_hk TWRP 6.0.0.0. I have some family time today, but hopefully have something out for "P6800" partitioned or original P6810 partition device soon.
Edit: Just Flashed "version 1" of eRobot 2.3P SkyHigh Edition with new Aroma 2.70RC2 installer. Just got to config for a lot more Aroma options before first release. Flashing and testing takes time, just one little error can give a big headache ! Just look out in the development thread for a "new" ROM for the P6810 in a few days time. If a FULL wipe is done (preload, system, data, dalvik), there are no flash issues. Maybe I'll look at adding a few more system mods (time permitting) later on, wait and see.......
Sent from my GT-I9500 using XDA Premium 4 mobile app
This appeared to work well for me. Then I got to the screen where there is the, "Reset perangkat" dialog button (and a back button on the bottom left). I've tried over and over to tap either button, but my touchscreen is apparently non-responsive (and the screen times out and goes to sleep as you're touching it - so apparently it's not detecting any input). I tried reflashing again, and there was no change. The screen orientation automatically rotates, the volume buttons work, the power button works - it's just that the touch screen is non responsive. I am going to try downloading a different 4.1.2 ROM from SamMobile (but their servers are slow so it'll be awhile).
Any other ideas?
gat0rjay said:
This appeared to work well for me. Then I got to the screen where there is the, "Reset perangkat" dialog button (and a back button on the bottom left). I've tried over and over to tap either button, but my touchscreen is apparently non-responsive (and the screen times out and goes to sleep as you're touching it - so apparently it's not detecting any input). I tried reflashing again, and there was no change. The screen orientation automatically rotates, the volume buttons work, the power button works - it's just that the touch screen is non responsive. I am going to try downloading a different 4.1.2 ROM from SamMobile (but their servers are slow so it'll be awhile).
Any other ideas?
Click to expand...
Click to collapse
Quite strange, I've lost count the times I've used this method and not come across this.
If you get stuck at the reset screen again, maybe you could try:
1. Disconnect USB cable
2. Enter stock recovery: factory reset (hold volume UP + power until enter recovery)
3. Reboot and wait 5-10 mins for first boot
If still not working, try flash again same full firmware package (same CSC), because it won't/shouldn't ask for the reset if already flashed (didn't ask again for me anyway)
Sent from my GT-I9500 using XDA Premium 4 mobile app
Hi,
I found a link for Liquid Smooth unofficial build for our note on their google+ community.
http://dl.niimdroid.com/LiquidSmooth/n7000/
I just want to share. [emoji6]
Greetings from Germany
scoute-dich
really smooth perhaps the best I have tried (and I've tried many rom) thanks
wow that's awesome! are you the one building these?? I am going to try this asap
thank you very much for the link
REVENGE SOLVES EVERYTHING
tysonraylee said:
wow that's awesome! are you the one building these?? I am going to try this asap
thank you very much for the link
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
No, I didn't build it, I just found the link. But I also think that this is a good rom. I didn't found a xda-thread, so I posted it here...
Greetings from Germany
scoute-dich
flahsed the 18-10-2014 release
multi-user works
hover is included
seems very stable
Theme engine needs some updating but i guess should be included in the future updates
what else can i ask for
thank you very very much
Hope there would be an official thread for this
scoute-dich said:
No, I didn't build it, I just found the link. But I also think that this is a good rom. I didn't found a xda-thread, so I posted it here...
Greetings from Germany
scoute-dich
Click to expand...
Click to collapse
Its being made by the Great dev for the asylum omni "Bosko Trkulja" aka chasmodo
follow the link here...by the way,these are the blind builds of his,,,
https://plus.google.com/103683575509787472991/posts/GBdaA3FuKDp?cfem=1
DrNinjaa said:
Its being made by the Great dev for the asylum omni "Bosko Trkulja" aka chasmodo
follow the link here...by the way,these are the blind builds of his,,,
https://plus.google.com/103683575509787472991/posts/GBdaA3FuKDp?cfem=1
Click to expand...
Click to collapse
wow!!! chas is the man an awesome and talented dev indeed
REVENGE SOLVES EVERYTHING
Hi mates,
I've not seen any instructions about installing that ROM. With only 170GB probably it is not a full rom.
I haven't seen the kernel in it and also SecPhone.apk; SecContacts.apk; SecSetings.apk etc. . . . . even SystemUI.apk
Could somebody post any guidelines about installation, which kernel should be used etc. :fingers-crossed:
Should SNote apps etc. from Note3 works on it without any changes?
Thanks.
Avitohol said:
Hi mates,
I've not seen any instructions about installing that ROM. With only 170GB probably it is not a full rom.
I haven't seen the kernel in it and also SecPhone.apk; SecContacts.apk; SecSetings.apk etc. . . . . even SystemUI.apk
Could somebody post any guidelines about installation, which kernel should be used etc. :fingers-crossed:
Should SNote apps etc. from Note3 works on it without any changes?
Thanks.
Click to expand...
Click to collapse
This is an AOSP rom which is like a Google stock firmware found in nexus devices that's why the size is 170-200mb and yes this is a full rom though you have to download gapps separately
The firmware you are thinking about is the Samsung bloated firmware filled with unnecessary junk making it around 1 - 1.5GB and so we call it Crapsung
Sorry I despise Samsung firmware, never used it and never will
Also note since this is not a Samsung firmware you will not able to use Snote or any Samsung related application as they are not compatible with AOSP framework
The instructions to flash this firmware are as follows
1) download ROM (the kernel is included in the ROM itself )
2) download PA Gapps
3) make sure your device is ROOTED and if not rooted already, please ROOT your device. (This is a mandatory and important step)
4) download RAW kernel for KK ROMs. (we have to use this kernel as KK ROMs require SE Linux compatible recovery otherwise you will not be able to flash it)
Note : raw kernel doesn't becomes your device kernel. The kernel is bundled with the ROM which will get flashed along with it
5) move all downloaded files to internal or external SD.
6) Now on a ROOTED device, reboot it to recovery by pressing home key + power key + volume up key simultaneously.
7) Since you are already rooted I expect might also have flashed a custom recovery. If so take a nandroid backup with that recovery [ DO NOT SKIP THIS STEP ]
7) Once nandroid backup is done do the following
-wipe data factory reset
-wipe cache
-go to mounts and storage and format system
-go to advance and wipe dalvik cache
8) back to the main menu choose install zip and first install RAW kernel and once done navigate to advance and select "reboot recovery" [ do not skip this step]
9) assuming that everything went correctly you should now be booted into TWRP recovery. You could do a factory reset here too if you want
10)Now choose install and select the ROM file first and queue the Gapps file too and flash
11) once the process is complete reboot and setup your device accordingly
12) and if not already Welcome to real world of android (Aosp/cm11)
Simple right
Raw kernel can found in the development section of N7000 forum with a simple search make sure to download the one for KK ROMs.
As for Gapps just go to Google and type pa gapps and the first link will take you to PA Gapps xda thread. Choose your pick from there
hope that helps
thank you very much
REVENGE SOLVES EVERYTHING
tysonraylee said:
This is an AOSP rom which is like a Google stock firmware found in nexus devices that's why the size is 170-200mb and yes this is a full rom though you have to download gapps separately
The firmware you are thinking about is the Samsung bloated firmware filled with unnecessary junk making it around 1 - 1.5GB and so we call it Crapsung
Sorry I despise Samsung firmware, never used it and never will
Also note since this is not a Samsung firmware you will not able to use Snote or any Samsung related application as they are not compatible with AOSP framework
The instructions to flash this firmware are as follows
1) download ROM (the kernel is included in the ROM itself )
2) download PA Gapps
3) make sure your device is ROOTED and if not rooted already, please ROOT your device. (This is a mandatory and important step)
4) download RAW kernel for KK ROMs. (we have to use this kernel as KK ROMs require SE Linux compatible recovery otherwise you will not be able to flash it)
Note : raw kernel doesn't becomes your device kernel. The kernel is bundled with the ROM which will get flashed along with it
5) move all downloaded files to internal or external SD.
6) Now on a ROOTED device, reboot it to recovery by pressing home key + power key + volume up key simultaneously.
7) Since you are already rooted I expect might also have flashed a custom recovery. If so take a nandroid backup with that recovery [ DO NOT SKIP THIS STEP ]
7) Once nandroid backup is done do the following
-wipe data factory reset
-wipe cache
-go to mounts and storage and format system
-go to advance and wipe dalvik cache
8) back to the main menu choose install zip and first install RAW kernel and once done navigate to advance and select "reboot recovery" [ do not skip this step]
9) assuming that everything went correctly you should now be booted into TWRP recovery. You could do a factory reset here too if you want
10) Now choose install and select the ROM file first and queue the Gapps file too and flash
11) once the process is complete reboot and setup your device accordingly
12) and if not already Welcome to real world of android (Aosp/cm11)
Simple right
Raw kernel can found in the development section of N7000 forum with a simple search make sure to download the one for KK ROMs.
As for Gapps just go to Google and type pa gapps and the first link will take you to PA Gapps xda thread. Choose your pick from there
hope that helps
thank you very much
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thanks. This is fully thorough instruction. Thanks :good:
My Liquid Smooth with Bauner Kernel, really fast! Thanks mythical chasmodo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7000 using Tapatalk
panamera2011 said:
My Liquid Smooth with Bauner Kernel, really fast! Thanks mythical chasmodo
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Made the switch to LS and Bauner kernel, very good combo ?
Ls 20142024
https://plus.google.com/103683575509787472991/posts/bRVf12Uec8Z
chasmodo said:
https://plus.google.com/103683575509787472991/posts/bRVf12Uec8Z
Click to expand...
Click to collapse
awesome!! will flash this when I get home
thank you very much
REVENGE SOLVES EVERYTHING
I am getting the error "unfortunately ui system process has stopped"
I have tried full wipe and also without gapps but still the same error.
is it just me or is anybody else getting it too??
REVENGE SOLVES EVERYTHING
Hi bro try with clean install there is no problem here....
yes the build is fine works perfectly
its my sim that was causing the FC's changing my sim solved the problem
REVENGE SOLVES EVERYTHING
Is that normal or battery draining could someone guide me what is causing my battery drain fast..
Ls 20141026
https://plus.google.com/103683575509787472991/posts/a7sBzu6JQJy
LS-KK-v3.2-2014-10-26-n7000 [emoji4]