Related
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
mazdaspeed6 said:
I just upgraded my E4GT Sprint from GB to ICS using the oneclick installer. I am trying to install the CODENAME rom from CWM but havng issues getting CWM installed. I used the the E4GT auto but FE16 isnt listed so i tried FE15 but it wont load into CWM. So i tried this link "http://forum.xda-developers.com/showthread.php?t=1390393" and flashed from ODIN and it goes into CWM but before it boots it says my phone is a gt-i9100 and has a ! on the bottom. It appears to boot though so i booted back into CWM and tried to flash the ZIP for CODENAME and the gapps file and it jsut gets stuck at the boot screen with the transformer logo. I cant get into CWM after that point and have to ODIN back to ICS. I am on ICS now and its working fine. Does anyone have any instructions on getting CWM installed and the codename rom from a fresh odin ICS install?
Click to expand...
Click to collapse
You really should read more before hopping around like that without checking. Real risk for a brick here.
-Flash EL26 stock CWM kernel via the PDA option in ODIN/Mobile ODIN
-When phone begins reboot, Hold Power + Volume up until boots into recovery.
-Wipe data/factory, cache and dalvik cache
-Flash ROM
-Flash Gapps
-Reboot
Those are the instructions right from the developer's thread. This is an AOSP rom and it sounds like you're trying to install TW kernels.
http://forum.xda-developers.com/showthread.php?t=1662295
This is the kernel repository. It links to each kernel where you can read further and find out if they are safe for flashing things.
Seems like you've done a bunch of stuff. But you really should do a whole bunch of reading first or you will brick your phone.
My suggestion would be to use sfhub's one-click http://forum.xda-developers.com/showthread.php?t=1705730 to get to a fully stock rooted device. Then use his autoroot package http://forum.xda-developers.com/showthread.php?t=1342728 to add CWM (the lates in the package is FF11+CWM Agat I believe) then you can add Agat's latest kernel with CWM http://forum.xda-developers.com/showthread.php?t=1721065
But I would be very careful when flashing ANY ROM; use the developers prefered method. Some recommend using EL26 CWM. Some a different recovery or procedure. Be especially careful with CM9 and AOKP builds to follow the directions there.
Good luck
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
mazdaspeed6 said:
So while i was waiting for a response i just went back to the stock GB using the one click install. I then used the autoroot package to install CWM and then restored my nandroid backup before i made in the very beginning. So my phone is back to a perfect state with GB and CWM installed. Can i just flash the ROM from CWM as is then? For some reason i thought it had to be "converted" to ICS and thats what started this whole mess. Things have changed since my old Evo
I just noticed that im running EL29 not 26...does that matter? When i try to flash that CMW EL26 stock root is when it gave me that gt-i9100 on boot and the ! at the bottom. Using the autoroot and choosing the EL29 Rogue is the only way i got it installed.
Click to expand...
Click to collapse
My friend some good suggestions above your post. Give yourself a day or two and do some reading prior to flashing. This way you may not end up at Sprint making up stories about why your phone wont boot up.
Let me just echo what everybody else has said, you're gotta read more. A lot more! If you're one goal is to get CNA in your phone I would recommend reading all of the very first post on that thread. They give step by step instructions.
If you need CWM there are several options to get it on your phone. Both sfhub and I have put together several one-click and automated options to get it on your phone.
One thing that hasn't been suggested yet but I would strongly encourage you to do is to read the "How Not To Brick Your E4GT" thread. It's sticked in the General section.
Good luck!
Two more things.
1) If you're going to ask for help give it a few minutes before trying something new. It takes people a minute to reply. Sometimes waiting that extra minute or two is all you need to be saved from bricking.
2) Don't be afraid to hit your thanks button for everyone who has offered advice already. I got them once for you but it might not hurt to do it again.
So i did the ULVH1 update through ODIN, followed the instructions. Once i was on ODIN picked the file for it. Ran it at firt it said Boot! Then Pass! So phone trys to reset but i get stuck on the reboot screen! Did i just brick the phone? Im rooted and using a custom rom (jedi mind trick v7). I need help on this.
Oh onre more thing. When i was stuck on the reboot. I tried getting into CWM and it got me through. Aren't i suppose to be unrooted already once this update occured?
Reboot loop? If you can get into CWM, you can always wipe, flash, wipe cache to fix things. If you can get into CWM you're still ok.
Now the thing about unroot and recovery, there's sort of different things. You can be unrooted, but still have CWM. CWM just lets you flash new ROMs that aren't manufacturer certified, I believe. I forget the details. So booting into ICS you could be unrooted, but the recovery is still CWM/TWRP
You are much better off using TWRP then CWM.
premiatul said:
You are much better off using TWRP then CWM.
Click to expand...
Click to collapse
Would you still use TWRP to flash roms that the OP recommends using CWM or CWM Touch?
I also understand NAND backups you made with CWM won't be restored successfully by TWRP?
So I got it to work. Im a noob on this stuff, so i wasnt sure if the file that XDA had was bad or not. I used a diff. one from phandroid.com. Went through ODIN and it went through with no problem. Lost root and CWM. Basically im back to stock. I eventually rooted again and CWM. But the funny part about it is that why do i still have my pics on the gallery? I thought this deletes everything? Like i said. Im a noob! lol. Everything seems working fine. Screen shots (went back the old way, instead of Power and Volume down.) Also, ISIS is that on google play? :good:
No flashing back to stock does not erase your internal storage.
Sent from my SGH-T989 using xda app-developers app
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
So, I have flashed CWM Recovery and CWM Touch Recovery onto my Epic 4G Touch. Rom Manager says both are installed. However, when I boot into recovery, I get the stock recovery. I've searched and searched and all I have found are people who aren't pushing the right buttons and others with junk answers that are no help at all, like instructions on how to flash the recovery.
Even if I reflash using Rom Manager or any other recovery installer, it boots to the stock recovery. It's as if any changes to the file system are being completely ignored.
The weird thing is, if I flash StockCWM-EL26 or rogue_ET-recovery-1.2.2-FB27-rc0 using Odin/Mobile Odin and get to whichever one I flashed once, then either the phone won't boot at all or subsequent reboots result in the stock recovery once again.
To reiterate, I have *no* problem booting the phone and I have *no* problem getting to recovery... it's the wrong recovery, but still.
Oh, and I'm using HyDrA ROM.
Wrong forum. Report your post & ask mods to move your thread here.
MistahBungle said:
Wrong forum. Report your post & ask mods to move your thread here.
Click to expand...
Click to collapse
That forum is for the Epic 4G. My phone is not the Epic 4G, it is the Epic 4G Touch.
Try here then (doesn't belong here regardless).
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
^^^^^ this been there done that
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
As I said, it either works once and never again or never at all no matter what I use to flash it.
Venum's Hydra rom? Wow, talk about a flash back..
Anyway, have you tried the el26 kernel one click?
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Would you mind listing the steps of flashing and items being flashed?
Only reason a custom won't stick is that you're flashing something behind it. In my mind at least..
First Time
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Wipe.
Flash HyDrA twice as per instructions.
Flash GApps.
Flash Multi-DPI Play Market while I'm at it.
Reboot.
Setup ROM.
Attempt to get to Recovery - got stock recovery.
Decided to try again without wiping. Same results.
Decided to try something:
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Made a NAND backup of /system and /data.
Flash HyDrA twice as per instructions.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Restore the NAND backups.
Reboot.
Attempt to get to Recovery - got stock recovery.
Another thing:
<Download Mode>
Flash Rogue recovery.
Reboot.
Attempt to get to Recovery - got Rogue recovery - So far so good.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Reboot.
Attempt to get to Recovery - got Rogue recovery - Interesting, but I can only access the external SD card from Recovery.
Flashed back to EL26.
Reinstalled HyDrA.
Restored the NAND backups.
(The Touch Recovery version is 5.8.1.5).
ROM Manager
Attempt to flash either CWM Recovery or CWM Touch Recovery.
Reboot.
Attempt to get to Recovery - got stock recovery.
Here is a list of my apps if you want that, too.
https://www.dropbox.com/s/k67l6mb294ruyug/apps-list.txt
I'm hesitant on trying anything else because it's a pain to restore it if I can't boot to the OS.
Just went back to Venums thread.
:edit: Briefly reading the thread, you'll need to have and AOSP kernel to run the Rom, so no, EL26 will not work.
:2d edit: This is out of the second post in that thread. - *If you are restoring a nandroid that you backed up via the above process, you will need to wipe cache and dalvik, then flash an AOSP ICS kernel or the ROM wont boot because it is backed up with the EL26 kernel. Then reboot.
Hydra comes with FD26 kernel. As per the OP.
I don't know, and haven't tested, if Hydra will run with EL26 cwm. But you need to add that to the last step.
But that's why you're going back to stock. It's part of the package.
Please, please, please; STOP using Rom Manager to flash a recovery.
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
egingell said:
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Click to expand...
Click to collapse
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
MoHoGalore said:
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
Click to expand...
Click to collapse
I downloaded one, I haven't tried it.
I take it back, I did try it, but it wouldn't install. FF18 Rev2, for the record.
MoHoGalore said:
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
Click to expand...
Click to collapse
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
egingell said:
I downloaded one, I haven't tried it.
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
Click to expand...
Click to collapse
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
MoHoGalore said:
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
Click to expand...
Click to collapse
Odin wouldn't install it, if that makes a difference. It's not that the install failed and I had to start over, again.
Well, since my touch isn't my daily use phone at the moment, I'll test that setup tonight.
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
egingell said:
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
Click to expand...
Click to collapse
My apologies on not getting back with you on this last night.
But the SD issue is also seen on the repacks with JB. Depending on when and how FF18 v2 was built (without source at the time?) could be similar to the issues with current repacks.
I'd have to refer those issues/questions to Agat or Garwynn..
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739
what recovery are you currently sitting on?
Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739
here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted
Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still
I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.
Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.
now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]
Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.