I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).
Related
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
So I attempted to get my phone from Paranoid to back to stock but I completely messed up. I basically restored my phone to CM 10, then I tried to relock my phone from there. So I used this video:
youtube.com/watch?v=5yS7yy4XVA4
and now I have fastboot with no rom and no recovery (also everytime i reboot from fastboot, it goes straight back to it). If anyone could help, what should my next step be? it would greatly be appreciated.
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
om4 said:
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
Click to expand...
Click to collapse
I have noticed a lot of poeple have this same problem coming from cm10/aosp/aokp thier OS and recovery disappear
Some people are just wiping system by mistake
om4 said:
Some people are just wiping system by mistake
Click to expand...
Click to collapse
It happened to a friend of mine and now this is maybe the 10th time I have seen this
Yeah, I'll agree it's happening too often but all aosp ROMs are still in pretty early development despite working as well as they do
I actually got it back unlocked (manually) but to get back to sense, what would you suggest?
You still need to flash twrp if you haven't done so and for a bare stock rom there's stock with goodies and there is another one with out
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
are you referring the the stock rom offered by mycomputerdoctor? If so, the flashing does fail, but your phone will still work. From what I understand the only problem is the error in TWRP and you wont have root anymore.
My phone does indeed still work, but I wiped /system before trying to flash so I don't have a ROM installed currently and therefore cannot boot past the splash screen.
http://forum.xda-developers.com/showthread.php?t=1999962
docnok63 said:
http://forum.xda-developers.com/showthread.php?t=1999962
Click to expand...
Click to collapse
Unfortunately, that is an RUU, which does not work for me. Thanks, though.
install the rom, even if it says fails, it should still boot. you could also just adb push the updated rom on to your sd card.
Thrillhouse847 said:
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
Click to expand...
Click to collapse
Im in the same boat :/ stuck in recovery and have no rom to flash. going to try to adb the latest version and see how that goes.
I was afraid of something like this. We shouldn't be messing with our phones without a back to factory state.
I'm actually all set now. I flashed the updated stock, debloated ROM and made a back up so I'm good to go.
Sent from my HTC6435LVW using Tapatalk 2
Long story short. Im using Infinix Hot 11s X6812 V728, wanting to root it with little to none knowledge. Flashed wrong boot.img, gets me to bootloop. Tries to flash stock rom but V728 firmware is not yet available. Flash stock rom of later version, now doesn't bootloop but after logo ot goes straight fastboot.
Installed TWRP and found in reboot/system options No OS Installed.
Tries to flash the later version again which is V723. Twrp is gone, stock recovery is in, only to found out the build version of my device is V586-V573 something like that. Tried to manually flash boot.omg, nothing happen. Thought to take it to carlcare but orange state. So tried to lock oem. Now logo bootloop with red state line. Does carlcare will know if you play with bootloader? Do i have another options?
IllustriousKage said:
Long story short. Im using Infinix Hot 11s X6812 V728, wanting to root it with little to none knowledge. Flashed wrong boot.img, gets me to bootloop. Tries to flash stock rom but V728 firmware is not yet available. Flash stock rom of later version, now doesn't bootloop but after logo ot goes straight fastboot.
Installed TWRP and found in reboot/system options No OS Installed.
Tries to flash the later version again which is V723. Twrp is gone, stock recovery is in, only to found out the build version of my device is V586-V573 something like that. Tried to manually flash boot.omg, nothing happen. Thought to take it to carlcare but orange state. So tried to lock oem. Now logo bootloop with red state line. Does carlcare will know if you play with bootloader? Do i have another options?
Click to expand...
Click to collapse
Some rules of thumb:
0. If you don't have a solid grasp on what you're doing, and how to fix it if something goes wrong, don't try.
1. Don't try to mess with anything without an unlocked bootloader.
2. NEVER attempt to lock the bootloader unless your device is running bone stock firmware, and successfully boots.
3. Don't expect warranty repair of any kind if you screw up the firmware. This may not be the answer you want, but what you did to your device is your fault.
They will probably fix it for you, but you will likely have to pay for the repair.