Related
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..
Ok so yesterday I received a cappy from someone on here that I told them I would try and fix. I am not charging them anything and am actually paying shipping back to them. When I received it and turned it on it was stuck at the end of the cornkernel bootlogo. I thought hey this will be easy and flashed the heimdall version of I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click. Phone rebooted and is now stuck at the att logo. So I flash cornkernel, its stuck at the end of cornkernel bootup. So I decided on a whim to try and flash this kernel Devil3_1.1.3_HB_cappy_CFS_BLN_VC_20120807, luckily that got me into recovery, so I did a full backup of all the stuff on his internal storage and completely wiped the phone, wipe data/factory reset, wipe dalvik cache, format boot, format system, format sdcard, format cache, format data, format datadata (yes I know I wiped some things twice) . Then I flashed my rom, it just reboots to recovery after the flash, still reboots after a reflash of the rom. I then wiped everything again and tried flashing CM9's latest nightly to see if I could get it to boot up. Still reboots to recovery. So far all together I have flashed I897UCJI6-OCD-REV02-Low-designgears, i897uckk4 Odin One Click CONTAINS Bootloaders, Re-partition, Full Wipe, I897UCKF1_withBL,SGH-I897_I897UCKJ3, KK4-SE-One-Click, JF6 With Bootloaders, SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click Followed By I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click both are heimdall. All of those either left it stuck at att or kernel screen after I flashed a kernel. Anyone got any ideas? I am almost to my wits end.
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Try the Odin version of this... Stock KK4 one click...it will do ya a full wipe and repartition for sure.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already have that is my go to file actually and I tried that before going the heimdall route. Thanks Anyways.
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
-SGA- said:
You should try the Rogers stock gingerbread with boot loaders. Worked for me when I was using the AT&T and not getting past recovery...
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for the idea. It didn't work tho. I am still at the same spot, phone keeps rebooting to recovery.
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
stayintwisted said:
have to wonder,,has the phone had the EU bug? might try flashing the rom with datadata ( I believe thats it) on the external sd
Click to expand...
Click to collapse
Not that I know of, It isn't my phone so I do not know the history other than him saying it didn't boot past the kernel screen and receiving it and seeing that and then what I have done. Normally the sd card data from what I have seen is wiped when the eu bug happens from what I have read, maybe I am wrong, but since I backed up his data off the sdcard that is why I do not believe it has had the eu bug.
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
cbalt said:
Anyone have any more ideas, I tried the EU Bug Instructions @ http://forum.xda-developers.com/showthread.php?t=1447303&page=85 Replacing the vold.fstab in the rom and also flashing it with CWM without luck. I am still stuck with it rebooting to recovery. I am still waiting on him to tell me his address again so I can mail it back to him since at this point I am lost. I told him MobileTechVideos would more than likely be his best shot at getting it fixed though.
Click to expand...
Click to collapse
Long story short, recovery is iffy at best for me. I went through something similar to this when trying to go from CM10 back to CM9 for the first time. Ever since then recovery has not been right.
What I did was
Install a stock one-click with bootloaders, used odin to flash speedmod kernel and then used that recovery to flash CM9 in three successions wiping everything each time. Somehow it took, and now I am no longer a crack flasher because I have the same kernel splash screen problem every time.
So,
Use this http://www.mediafire.com/?5rcofbzusoor6mv
PDA button in Odin3 1.7: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Boot into recovery.
Flash your ROM
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Wipe /system, /data, and dalvik.
reboot recovery.
Flash again.
Try to boot normally.
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
There is a place that has rogers stock roms
cbalt said:
Thanks for the idea, but it's a no go, Phone just stops at Galaxy S SGH-I897 Kernel Screen. I can't even get to recovery. Only way I have got to recovery with this phone was flashing an ICS kernel.
Click to expand...
Click to collapse
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
sunfirestorm said:
There is a place that has rogers stock Roms the one click Odin's back to 2.2 is my go to for all problems the i can't get to recovery. I know you said you tried rogers stock roms but try the one-clicks for some reason they have always saved me. It will re-install everything and you will be on stock recovery if it works but from there its easy to get CWM and your on your way
Click to expand...
Click to collapse
I have already tried all three of the Rogers One Clicks with none of them actually doing anything more than the Captivate One Clicks, It still doesn't boot past the first screen. Thanks for the input though.
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
fohdeesha said:
You've been using a one click with 2.3.3 bootloaders, they're are 2.3.5 bootloaders available that have solved certain peoples sleepdeath issues, including mine. I've done this procedure on several captivates to take them from mangled and non-bootable to latest bootloaders and working recovery to flash whatever rom I need to from there on.
Use this one click that includes the 2.3.5 bootloaders - http://fohdeesha.com/data/other/android/i897uckk4 with latest BL.zip
After that goes through and you have stock gingerbead, use this odin package to flash the included devil kernel package, that will give you the latest CWM recovery
http://fohdeesha.com/data/other/android/uckk4 CWM recovery.zip
After that, if you still can't boot into recovery, you have a hardware issue
edit: looks like you already did this more or less.......try it once more in this order? Then once you do this and boot into recovery, flash a rom and see if it will work
Click to expand...
Click to collapse
I'm going to do your steps again which is more or less what I have already done. I am waiting to hear back from the person so I can ship him the phone back and he can send it to MTV or someone or just junk it, its his phone and his choice. At this point I would say it needs Jtag or Unbrickable mod + repair. Although I am still trying ideas of mine and anyone elses lol.
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Well if the one clicks are successfully writing primary and secondary bootloaders and it's still not working, a jtag isn't going to do anything else. It almost sounds like the memory has a few corrupt blocks, but I can't say until you flash 2.3.5 BL's and see what happens
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
cbalt said:
EDIT: Still A No Go. Doesn't Boot Past ATT Screen After Flashing The Odin 1 Click, After Flashing Kernel then wiping and flashing rom, it just reboots to recovery
Click to expand...
Click to collapse
Oh jeez looks like the memory is failing then
Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart.
Okay so these are the steps that I followed:
-Used the KGS Utility and chose "s-off"
-Followed all the prompts everything worked out fine.
-Following that I used it to install a custom recovery.
-Followed the prompts everything worked fine.
-Then I used Revolutionary CWM to flash SuperUser.
-App was there on reboot.
-Then I downloaded the AOKP "Initiate Your Swagger"[4.1.2] Rom
-Put it on my SD card and flashed it (after wiping and backing up)
-When the phone boots the setup wizard starts.
-I follow the prompt and when it gets to "Just a sec" the phone freezes then restarts.
Don't know what the problem is here.
I get the same problem when trying to flash CM10. The phone will boot, but then after 20-30 seconds will reboot.
kojimin said:
Hello, long time reader, first time poster. I know about rooting, and installing roms and all that good stuff (had a galaxy s2 but odin bricked it). So I'm new to the sensation, and it's quite different from my previous device. My problem is that when I install a custom rom, the phone will boot and all about after about 30 seconds will freeze and restart. I also noticed that there is no signal in custom roms either. Don't know what I'm doing wrong here. I used an all in one tool to do s-off, and install a custom recovery. Then I rooted it. Then I started trying to install custom roms but they don't seem to work. What am I doing wrong?
Click to expand...
Click to collapse
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.
Skipjacks said:
Be VERY specific and give a step by step detail of what you are doing to install. Give WAY more detail than you have. And put the detail in a list, not a giant paragraph.
Then we'll look at it and see what's missing.
Click to expand...
Click to collapse
Sorry about that. Edited my first post. I hope that is enough.
When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.
Skipjacks said:
When you say it boots for 20 seconds, what exaclty for you mean.
Does it just replay the boot animation over and over? Or does it actually bring you to a home screen with the status bar and everything for 20 seconds before the reboot? That's a very important difference in diagnosing this one.
Also try installing 4EXT recovery. CWM has been known to cause weirdness with AOSP roms. Plus you may have an older version of CWM thatcan't properly install the newer roms. If you used a .zip in bootloader to flash CWM yuou probably had an older version. I have a special place in my heart for CWM too, but 4EXT is just so much better for the Sensation. (Different recoveries ar ebetter or worse on different devices.)
If you properly installed superuser on your stock rom that you have a nandroid backup for, installing 4EXT is super easy. Just restore the nandroid, which should boot up without problems, download the 4EXT app from the play store, and use the app to install teh latest version of the recovery. No need for ADB or flashing in bootloader. Then try a full wipe and fresh install of AOKP from 4EXT.
Click to expand...
Click to collapse
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.
kojimin said:
It boots up to the homescreen (with no signal) then it reboots.
I will try 4EXT and post my results. Thanks for your help thus far!
EDIT: Tryed installing 4EXT now when I try to boot into recovery it shows the HTC spash screen, then it reboots back the homescreen. So I think my recovery is gone.
EDIT 2: So I got the 4EXT recovery installed. But the ROMs are giving me the same issues (no change). I also noticed as before, when the custom roms boot there isn't any cellular signal.
Click to expand...
Click to collapse
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Update the firmware.. You are on gingerbread firmware (revolutionary soff worked for you means you are on GB) and it won't work on ics/jb roms
Check the firmware thread by kohr-ah in sensation development section and flash universal 3.33 firmware
It will solve your rom problems
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
it was the firmware! I just updated to 3.33, and 4.1.2 "Initiate your swagger" booted up completely. Thanks for your help :good:
Awesome reply mate :
Sent from my HTC Sensation XE with Beats Audio using xda premium
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
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
krusty_da said:
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
Click to expand...
Click to collapse
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
lj50036 said:
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
Click to expand...
Click to collapse
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
dgcruzing said:
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
Click to expand...
Click to collapse
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
Yes, dont worry too much as I was in the same boat.. lost the recovery a few times.. and or couldn't get recovery to mount any partitions..
If you have still got ADB connection then use Busters wipe... multiple times.. as it cleaned mine out..
Then I used the easyflasher to flash the CWM kitkat Version and used this to flash Tims Kitkat off the external SDcard..
booted in to Kitkat with out loading Gapps.. let it settle then booted in to the recovery then booted to Bootloader..
and reflashed TWRP 2.8.. flashed Gapps with this and its all settled in..
One thing that I made sure off was to boot the device after flashing a recovery.. somewhere in all the instructions it says to to this.. So I made sure I did it..
otherwise I kept getting that password screen in TWRP...and if i got that then I knew it was not mounting anything..
K.. keep at it.. if there is will there is a way and as said if you have an unlocked bootloader and ADB you are half way there already..
Good luck..
lj50036 said:
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
Click to expand...
Click to collapse
Thanks! I'm loading Lollipop for the fisrt time now!
I found a tutorial here to change the bootloader:
http://forum.xda-developers.com/showthread.php?t=2187982
And downloaded the latest firmware from here:
http://www.service.asus.com/#!downloads/c1wax
Thanks again