So up until a week ago I was running CM11, but for the past month I was having battery issues so I decided to revert back to stock to test if it was the battery or the ROM. So I flash my phone back to stock and update to 4.4.2 knowing that I still had all the tools still available in case I wanted to flash back to CM11. Now today I wanted to flash back to CM11, but I wanted to make sure the methods were still correct to flash back to CM most concerning the bootloader, and to my dismay I found out that everything changed for the worse. On the bright side I was able to root my phone but unfortunately I flashed CWM recovery so now I can't get into recovery, but I can still access my phone so its not hard bricked to the point I have to JTAG, but my first question is how do I revert back to system recovery, I made a nandroid backup before I flashed the recovery but would that still work? And my second question is are there any ROMS you can install that allow you to run a custom recovery or allow you to flash back to 4.1.2? Either way, I'm glad I decided to double checks facts before proceeding or I would've had a bricked phone.
Flameancer said:
So up until a week ago I was running CM11, but for the past month I was having battery issues so I decided to revert back to stock to test if it was the battery or the ROM. So I flash my phone back to stock and update to 4.4.2 knowing that I still had all the tools still available in case I wanted to flash back to CM11. Now today I wanted to flash back to CM11, but I wanted to make sure the methods were still correct to flash back to CM most concerning the bootloader, and to my dismay I found out that everything changed for the worse. On the bright side I was able to root my phone but unfortunately I flashed CWM recovery so now I can't get into recovery, but I can still access my phone so its not hard bricked to the point I have to JTAG, but my first question is how do I revert back to system recovery, I made a nandroid backup before I flashed the recovery but would that still work? And my second question is are there any ROMS you can install that allow you to run a custom recovery or allow you to flash back to 4.1.2? Either way, I'm glad I decided to double checks facts before proceeding or I would've had a bricked phone.
Click to expand...
Click to collapse
No custom recovery and no flashing back to 4.1.2. It is safestrap only and 4.4.2 touchwiz ROMs only, of which there is only one right now. Unless you are willing to send your phone to mobile tech videos and pay them $50. They are apparently ale to revert you're phone to 4.1.2.
You should have done a little more reading of all the warnings available in the forums before going back to stock and taking the update to 4.4.2.
Sent from the Shark Tank using XDA Premium 4 mobile app
landshark68 said:
No custom recovery and no flashing back to 4.1.2. It is safestrap only and 4.4.2 touchwiz ROMs only, of which there is only one right now. Unless you are willing to send your phone to mobile tech videos and pay them $50. They are apparently ale to revert you're phone to 4.1.2.
You should have done a little more reading of all the warnings available in the forums before going back to stock and taking the update to 4.4.2.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, that answers my second question, but is there anyways to reflash the stock recovery for 4.4.2?
Flameancer said:
Ok, that answers my second question, but is there anyways to reflash the stock recovery for 4.4.2?
Click to expand...
Click to collapse
There is if you can find one, but I don't think it's posted anywhere. Your best bet is to just Odin flash a stock 4.4.2 rom and start over again.
Sent from my HTC6525LVW using Tapatalk
Related
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
marclabrosse said:
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
Click to expand...
Click to collapse
no, u need to flash su, gb or ics its still the same process, maybe w/oneclick but i never tried that method
but whats the problem using cwm, its very safe todo and its y we can do so many things with our phones, and if need b u can always flash back to stock ics w/sammobile.com firmware files
afraid to say you'll have to have a cumstom recovery. SuperOneClick wont work. It actuallt will only work on GB 2.3.5. 2.3.6 wont. And I'm pretty certain ICS wont either.
Thanks guys, yeah I tried GB methods or rooting without CWM Recovery before posting, no go...should have rooted before upgrading her phone via Kies...
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store.
I've had mine running CWM recovery from day one, but I can restore it to stock without a problem, she's not technical at all... its her "Facebook" phone...
I guess CWM recovery will be going on there shortly...
marclabrosse said:
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store...I guess CWM recovery will be going on there shortly...
Click to expand...
Click to collapse
You can flash back to 3e recovery without losing root. Unrooting is covered in post #10 here: http://forum.xda-developers.com/showthread.php?t=1726445
I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!
Will I need to flash the stock kernel back on my phone to take the OTA or will it work with Imo's kernel? I tried to reflash the boot.img from my nandroid and wifi was not working, so I reflashed Imo's kernel and wifi works again and I am sitting in a holding pattern. I'd rather not have to ODIN back to full stock because I only have access to PC's at work and don't really have time in the day at work to be doing stuff like that while there.
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
What exactly makes you want the update? If it's the radio (which imo is the only reason to consider the OTA) then just get the radio and flash it in CWM.
i already have the radios flashed but I've had this weird issue that seems to only happen after flashing the kernel but has only happened on a few occasions mainly on the weekends at my daughter's 2 soccer games to be exact. Camera and video have acted weird, first was video controls were upside down, had to reboot a few times for it to fix and just yesterday everything I shot shows fine in gallery but when I go to import into Instagram the pics are all rotated 90 degrees.
I can't afford to have data issues which is the reason I haven't installed a custom ROM since I use my phone for work quite a bit. Figured go back to stock kernel, take OTA to clean out any weird issues that would linger and wait for either official JB or for ROMs to get solid on data issues.
mav3rick478 said:
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
Click to expand...
Click to collapse
Yes, but remember if you don't already have the OTA notification nothing with come just because you removed the custom recovery. If you've already received that notification then disregard this post.
Sent from my SCH-I535 using xda app-developers app
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
mav3rick478 said:
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
Click to expand...
Click to collapse
No problem. If you still notice weird issues then Odin to an older firmware and accept the OTA from there.
Sent from my SCH-I535 using xda app-developers app
Hi all,
I am using OMNIROM 4.4.4 bigpart in my old EU Wingray XOOM 32GB but I have lots of performance and stability issues (browser crashes, apps freezing, very slow system....). After reinstalling it I still have problems and I want to check if it's due to the device itself...
To test that, I would like to go back to the stock Android 4.0.4 ICS that I was using in my European xoom before the jump to EOS, CM and OMNI.
Could anybody help me on how to go back to stock? Where to download the stock rom? how to remove bigpart? Is it really required to remove bigpart to install the stock rom?
Thanks for any help given.
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
valent|n0 said:
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
Click to expand...
Click to collapse
Thanks a lot for answering.
So... I have to download the original Honeycomb software, "reflash it" and update until I get 4.0.4 or 4.1.2 ...
My doubt is ... do I have to "undo" the "bigpart"? Or will the stock firmware install perfectly in my "bigpart" xoom?
Thanks!
the bigpart issue I am not to sure of
Of course you need to undo BigPart. It's well document in Xoom Android development section of this forum.
You need to flash the non-big-part TWRP (2.8.0 or other), wipe everything, reboot intot TWRP, format Data, wipe everything again, reboot into TWRP again. Then you can flash original image using fastboot.
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
machina77 said:
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
Click to expand...
Click to collapse
... Sorry
jkd said:
... Sorry
Click to expand...
Click to collapse
Eh?
I didn't find anything in forum, could somebody help me how can i go back from bigpart to stock partition?
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
nomadman said:
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
Click to expand...
Click to collapse
I just flashed mine from omni bigpart back to stock 3.1 cause my 1yr old daughter can't keep her hands off my phone...was time consuming researching how to do it. But it works perfectly...I wound up running some script somebody wrote and it pretty much did everything for me... not in front of my PC at the moment but if you are still fighting it PM me and I'll give ya everything you need...