Related
I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.
I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..
Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app
joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.
sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2
mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!
The phone will not install a Verizon update with a custom recovery installed.
So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us
Ok so Huawei Ascend XT H1611 ATT. Rooted just fine. Unlock just fine. ATT sends update OTA. Supposed to go from B150 to B160. I tried to avoid it. Started and then froze on reboot. I can run recovery. Can flash recovery. Used every method I can find in the forums. All it will do is run either stock or custom recoveries but no matter how many backups or stock roms I have tried it just hangs on boot. I'm not too new to custom roms and rooting and unlocking, I just would like to know if I should just give up on it. It is not like it's the end of the world, I would just like a second opinion on the matter. Thanks for any advice.
MotoBlack said:
Ok so Huawei Ascend XT H1611 ATT. Rooted just fine. Unlock just fine. ATT sends update OTA. Supposed to go from B150 to B160. I tried to avoid it. Started and then froze on reboot. I can run recovery. Can flash recovery. Used every method I can find in the forums. All it will do is run either stock or custom recoveries but no matter how many backups or stock roms I have tried it just hangs on boot. I'm not too new to custom roms and rooting and unlocking, I just would like to know if I should just give up on it. It is not like it's the end of the world, I would just like a second opinion on the matter. Thanks for any advice.
Click to expand...
Click to collapse
When you flash recovery, have you tried factory resetting and wiping cache in recovery then rebooting?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
When you flash recovery, have you tried factory resetting and wiping cache in recovery then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes. That has been common practice for my other phones. This is the first phone that has had issues like this. Everything was fine until ATT it's update started.
MotoBlack said:
Yes. That has been common practice for my other phones. This is the first phone that has had issues like this. Everything was fine until ATT it's update started.
Click to expand...
Click to collapse
It's best to unroot a device before applying stock updates on most devices. Stock updates usually require you to have stock recovery and an unmodified system partition.
If there is a rooting method for the update then you can try reflashing your stock firmware to get a clean start then apply the update again, then try rooting again after the update is applied.
Sent from my SM-S903VL using Tapatalk