Database Users

Samsung Galaxy S GT i9000m Recovery

Ok Fellas! just got my phone last night, rooted it installed the stock froyo JK4.
I come from htc desire so my recovery was bit different installed rom manager & got cloworkmod 2.5.1.2.
Downloaded a rom on phone, rebooted into recovery, but this recovery has purplish text instead of green & there is no install from SD. I cant think of any thing at the moment can some one please help, I wanna install some other rom, other than the stock froyo. PLEASE HELP.

You need to install clockwork revory if you go to the rom manager application there will be an option to flash clock recovery right at the top when you open the application hope this claers things up

yep i did sir, but still there is no option to install from sd, it only allows me to install as update.

from teh rom manager im selecting Galaxy S I9000 for clockwork recovery and it successfully downloads and when i press reboot into recovery its still takes me to the purple screen....i think this means that im not able to get into clockwork recovery any help.??

you have to select 'install update.zip' the first time, this will install clockworkmod and then you can proceed.

The problem is your using 3e recovery and cwm will not work with 3e.
To get 2e recovery you will have to use odin and flash a kernel that has 2e recovery, I suggest hardcores kernal as it comes with cwm already , from there you can install what ever custom rom you want using.the update.zip or installing zip from sd.
Sent from my GT-I9000M using XDA App

FuryriderX said:
you have to select 'install update.zip' the first time, this will install clockworkmod and then you can proceed.
Click to expand...
Click to collapse
Hey man as per your instructions i got the clockwork dome thru rom manager and rebooted into recovery. I pressed update and i ran for a bit but then gave an error about the signature of the package and installation aborted. Pls help.
Sent from my GT-I9000M using XDA App

Samdroid_G_S said:
The problem is your using 3e recovery and cwm will not work with 3e.
To get 2e recovery you will have to use odin and flash a kernel that has 2e recovery, I suggest hardcores kernal as it comes with cwm already , from there you can install what ever custom rom you want using.the update.zip or installing zip from sd.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Hey man you sound pretty helpful would you direct me in a direction for those recovery files ur talking about and some sorta guide. Much appreciated eh.
Sent from my GT-I9000M using XDA App

the best way to get clockwork working on i9000m (personally i believe)
is to flash the kernel for Speedmod... you should see it in development forum... just flash that kernel with odin
and your recovery will work fine

danial.aw said:
the best way to get clockwork working on i9000m (personally i believe)
is to flash the kernel for Speedmod... you should see it in development forum... just flash that kernel with odin
and your recovery will work fine
Click to expand...
Click to collapse
Hey man thanks alot, do you mind pasting a link here. If you kindly can please and thanks again.
Sent from my GT-I9000M using XDA App

There are a few things i could suggest.
1. Keep your flashing to a minimum if you have the i9000m. There is a high probability that your phone's memory card is defective and you'll ruin it by accessing it more often. Froyo broke lots of bell phones, and being a rom junky means more flash activity. I am on my second phone, but some people are up to their fifth. Flash a good stable rom and dont go too crazy flashing after that
2. download ODIN, and most 3rd party kernels have 2e i think (http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html) - pretty sure speedmod does. voodoo also does, all kernels can be found in the dev section easily
Just make sure you download the ODIN version of the kernel and not the CWM file, because since you dont have CWM already, you'll not be able to use it.
There is a problem with USB mounting your sd cards on your pc without patching, since you are running a stock 2.2, so you would need the patch unless you go to a 2.2.1 rom
3. 2.2.1 runs nicer than 2.2, but i havent flashed to a JPY because i am paranoid about my second i9000m dying before i get a backup phone . You may want to flash a jpy mod (like doc rambone's, or darky's), but if you have battery life problems flash a different modem, like the JK4 modem used in bell's latest official rom

junooni.1980 said:
Hey man thanks alot, do you mind pasting a link here. If you kindly can please and thanks again.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
You can find the thread here http://forum.xda-developers.com/showthread.php?t=822756
You can find the instructions here for ODIN http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
Just read through that all the answers your looking for are there ;p.

pervert said:
There are a few things i could suggest.
1. Keep your flashing to a minimum if you have the i9000m. There is a high probability that your phone's memory card is defective and you'll ruin it by accessing it more often. Froyo broke lots of bell phones, and being a rom junky means more flash activity. I am on my second phone, but some people are up to their fifth. Flash a good stable rom and dont go too crazy flashing after that
2. download ODIN, and most 3rd party kernels have 2e i think (http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html) - pretty sure speedmod does. voodoo also does, all kernels can be found in the dev section easily
Just make sure you download the ODIN version of the kernel and not the CWM file, because since you dont have CWM already, you'll not be able to use it.
There is a problem with USB mounting your sd cards on your pc without patching, since you are running a stock 2.2, so you would need the patch unless you go to a 2.2.1 rom
3. 2.2.1 runs nicer than 2.2, but i havent flashed to a JPY because i am paranoid about my second i9000m dying before i get a backup phone . You may want to flash a jpy mod (like doc rambone's, or darky's), but if you have battery life problems flash a different modem, like the JK4 modem used in bell's latest official rom
Click to expand...
Click to collapse
Oh crap! really, i think imma sell this phone rite away then, cus coming fro desire im a rom junky. I guess this aint the rite phone from me.

Yeah, there are massive known problems with internal memory on these phones. I'm already on my second, and if i have more issues, i'll be buying the international i9000 from ncix.com. same phone, no internal memory problems.

HELP!!

So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?

You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...

Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App

Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.

ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..

I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.

Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.

Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.

UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.

BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.

@Mardenator
your screenshot a looke liek from my adwluncher from my tab...

Lol I'm using ADW Ex.

ok i dont untersant waht you with them post, sorry.

Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

Softbrick caused by LPY - How did you recover your phone?

There have been few more cases of Superbrick since Chasmodo's and now I'm worried that there would be more of such cases when people start flashing custom LPY ROMs, LPY mods and use Stock and Clockwork recovery functions.
I have created this thread specially for those people to share their methods/experience - when the softbrick happened to them and how they managed to recover their phone (symptoms such as nand write failure, factoryfs failure etc).
So if more of such incidents happen, possible solutions would be at one place.
Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.
Do not post solutions if you have not successfully tried it yourself.
Regards.

fixed my superbrick by sending it back to india to get sent in for new motherboard

JamieD81 said:
fixed my superbrick by sending it back to india to get sent in for new motherboard
Click to expand...
Click to collapse
Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.

Boy124 said:
Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.
Click to expand...
Click to collapse
if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..

JamieD81 said:
if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..
Click to expand...
Click to collapse
Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.

Boy124 said:
Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.
Click to expand...
Click to collapse
If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.

wildestpixel said:
If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.
Click to expand...
Click to collapse
+1 perfect reply

Entropy was refering to Epic 4G Touch forum so I searched there and found useful info there. Credit goes to xST4T1K
How to Avoid Brick
-If you are on ICS with an ICS kernel, DO NOT WIPE! this has the potential to brick your device (until source arrives, just have patience)
-Using a bad USB cable to ODIN back to GB from ICS
-Rom Manager
-Touch recovery
-Avoid flashing any custom rom in stock ICS recovery
-Avoid restoring a GB backup when running an ICS leak
-Avoid restoring a ICS backup when running a GB rom
-Always use PC odin to return GB - Do flash custom GB kernel on non-GB rom to flash GB firmware

Boy124 said:
....................
So if more of such incidents happen, possible solutions would be at one place.
Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.
Do not post solutions if you have not successfully tried it yourself.
Regards.
Click to expand...
Click to collapse
Your post in itself is tantamount to trolling.

wildestpixel said:
Your post in itself is tantamount to trolling.
Click to expand...
Click to collapse
If you do not have anything useful to say, better stay away from this thread.
I am not offering you the job.
And you don't seem to have much knowledge than proving
superbrick != softbrick

You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.
Everything else is a soft brick.

chasmodo said:
You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.
Everything else is a soft brick.
Click to expand...
Click to collapse
100% accurate
nothing about superbrick is anything to do with softbricking a device.

Thanks Chas.
People won't contribute but will waste time on what is what and what's not.

I had to use a combination of many things:
- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick
- CWM refused to restore any backup or wipe anything (FREAKED OUT)
- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)
- Used Redpill restore my backup
- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.
Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo
hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.

tazzix said:
I had to use a combination of many things:
- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick
- CWM refused to restore any backup or wipe anything (FREAKED OUT)
- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)
- Used Redpill restore my backup
- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.
Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo
hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.
Click to expand...
Click to collapse
So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)

eitama said:
So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)
Click to expand...
Click to collapse
I would guess so, and wish I knew that earlier, it was supposed to be able to UPGRADE without wipe, otherwise if I would have gone the standard way of backup, titanium backup, wipe, flash; I would not have goten any damage for sure.

For me it has been to Flash a wipe rom.
Skickat från min GT-N7000 via Tapatalk 2

Installed LPY w/ root via mobileOdin pro without issue, but was having many issues with FC's. I was thinking of doing a full wipe, but decided to see if it was safe considering the issues with the previous leaked ICS roms, checked xda where I saw the warning about LPY.
Decided to go back to GB by flashing AbyssNote kernel 4.2, then restoring backup.
The most recent backup gave me an error, so I went to the back before that. Everything seemed to go fine but on reboot I got stuck at the Samsung logo.
Was able to still get in cwm so I reflashed AbyssNote kernel, then flashed Cassie Xtralite rom, which is the gb rom that I had been on before flashing ICS.
Everything booted up so I went through the procedure to get Cassies rom up and running and everything has been fine since.
Will try ICS again at some point but will wait a little bit longer until things seem more sorted.

I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)

bmcsfuze said:
I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)
Click to expand...
Click to collapse
In a Factory Reset you only lose your apps, contacts, gmail settings etc.. i.e. what you have in the system.

[GUIDE] On ICS LPY ROM [DO's & DONT)

From the Moderator... Please read my Caution in post #27-thanks
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Edit: Shorty66 just posted he bricked his note by doing factory reset from within the os. So far he's the only one at the moment. But numerous members reported bricking their device using CWM recovery & stock recovery. Just to be safe, use the os factory reset rather than recovery. Me myself have used the os factory reset at least 6-7 times as we speak without any issue for the time being.

Nice guide, perhaps you could also add the steps to safely go to a 'safe' kernel/rom if one is already using LPY?
Sent from my GT-N7000 using xda premium

+1
Would also like to know the go back to b/cm9 etc steps
Sent from my GT-N7000 using xda premium

Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there to get to any custom roms or rooted gb.

Ashren81 said:
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there get to any custom roms or rooted gb.
Click to expand...
Click to collapse
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2

MamaSaidWhat? said:
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
Click to expand...
Click to collapse
flash using pc odin or heimdall. get to recovery and flash/wipe or install gb backup from there. but i advise u to get back to stock gb to get a clean start and move from there.

Ashren81 said:
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Click to expand...
Click to collapse
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex

sehooo said:
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
Click to expand...
Click to collapse
apex launcher FTW!

nice guide!

Ashren81 said:
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Click to expand...
Click to collapse
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
The post I referenced: http://forum.xda-developers.com/showthread.php?p=26086599#post26086599

k1ng617 said:
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
Click to expand...
Click to collapse
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.

Ashren81 said:
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Click to expand...
Click to collapse
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.

hgberry said:
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
Click to expand...
Click to collapse
yes that should be the way like i've post earlier. just use the safe-kernel of ur choice. but dont restore nandroid backup from any previous ics, nandroid from previous gb is fine. nice to see ur note safely back on gb. /thumbsup

I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium

Goodm7sn said:
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.

I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.
to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
You might just be in the lucky position to have a phone which doesn't have the error.
But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...
I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.
Do you still know your flash history?

Hi Shorty66,
Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it.
Sent from my GT-N7000 using xda premium

Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
Sent from my GT-N7000 using xda premium

[Q] How can I remove custom recovery? Ran into some problems and want to "start over"

[Q] How can I remove custom recovery? Ran into some problems and want to "start over"
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.

_tyler_ said:
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.
Click to expand...
Click to collapse
how'd you root your phone first? through what?

MuzakaTheBeast said:
how'd you root your phone first? through what?
Click to expand...
Click to collapse
I followed the IORoot22 instructions along with clarification from wyrdtrtle on IRC

Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk

spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Oh, right, I remember reading that Loki bypasses locked Bootloaders (which somehow led me to think only CWM had Loki support and would work when TWRP didn't). I'm gonna try this now.

spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Didn't work. Still get an error saying it failed

_tyler_ said:
Didn't work. Still get an error saying it failed
Click to expand...
Click to collapse
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying

spinninbsod said:
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying
Click to expand...
Click to collapse
apparently the 10.2 rom i was trying to flash wasn't compatible with my phone (not too sure on the specifics) but I tried the latest nightly for cm11 and I've been running it since last night.