Related
Hello, I need some help trying to install the 1.9 ROM. I just purchased a Dell streak coming from an Iphone. Because of a deteriorating eye condition the big screen is a blessing. I bought it used on ebay. It originally had stock 1.6 which i upgraded to stock 2.2 (340) by downloading and running the pkg file. It was very easy to do. Im an att customer this is the relevant information regarding my version of 2.2 .
Version 2.2
Baseband GAUSB1A134031-US
Kernel 2.6.32.9
Build 14844
I have read through these forums extensively particularly the "how to" forums for days. After reading all the various variations for upgrading the rom (my phone lags and i want to see if the rom upgrade will fix this) I developed what I though was the proper procedure for installing 1.9. These are the steps i followed:
1. Install Android Drivers
2. Enter Fastboot mode
3. Installed Clockword Mod Recvery
4. Loaded the install txt file and 1.9 zip file on root of sd card.
5. Flashed the Clockword Mode Recovery IMG using fastboot. Fastboot said recovery was "done"
6. Rebooted.
7. Went into recovery mode by pressing Volume UP and Down and power button
8. Chose option 2 upgrade from SD card.
now its my understanding that doing so was supposed to take me to the clockmod recovery screen which would then give me the option of upgrading from the zip file. Instead I get a message in light blue which says in part
"Android System recovery utility GAUSb1a134031
To perform emergency software recovery you will need to insert SD card"
I then pull the battery and reboot and it boots up fine into the stock 2.2.
Now the question is what am i doing wrong. Im thinking that maybe its the baseband? and that I need to flash a new baseband. If anyone can help it with some guidance it would be much appreciated.
3.
Once you flash Clockwork you cannot let it boot. The OS will over-rite Clockwork. As soon as you flash Clockwork, hold both volume buttons down while it is rebooting. Selet option 2 and you should get the Clockwork menu.
Thank you i will give that a try
Didnt work. I do the fastboot recovery flash which it indicates is done. I then give the flashboot reboot command As soon as it starts rebooting i hit the volume up and down and power buttons but it still reboots into stock 2.2. I don't even get the recovery screen
Fuigured it out i only needed tto hold the volume buttons. Now im there thanks again
Hmm, you should be getting a recovery menu either way. The only thing I can think of is to try and hold both volume and power buttons down at the same time. This is how I normally access the recovery menu when not flashing the reboot comand. If thats not it, may be an issue with the recovery image. Have you considered StreakMod Recovery?
mdb4403 said:
Fuigured it out i only needed tto hold the volume buttons. Now im there thanks again
Click to expand...
Click to collapse
Ok, Cool!
I am trying to put Clockwork Recovery on the Vibrant and when I first boot it I need to manually select "reinstall packages". I usually have to do this two times in a row and then it boots into the cw recovery. But when I reboot into the recovery it boots back into the samsung recovery and I have to select "reinstall packages" again to get into cw. This isn't normal correct? I saw that I should only have to do this once and then it should boot into cw recovery everytime with no problems. The phone came with 2.2 stock.
In my experience with stock roms, i have to hit re-install packages twice to go to clockwork recovery.
Well what I am wondering is do you have to do that everytime you want to go into the recovery? Also could that possibly affect the phone to where I would not be able to restore it back to factory if something were to go wrong if I flashed a new ROM?
i assume you have rom manager right? You can do select reboot into recovery so that it will bring you straight to clockwork mod recovery. Also there's an app called "quick boot", that can make you go to recovery or download mode faster.
And no that won't affect anything when you want to flash another rom.
Your fine. Recovery will not effect going to back to stock because odin overrides all. Like the other guy said when your using a stock rooted rom you almost always have to hit it twice. Flash a custom rom and it will always go into recovery with out a hitch.
Sent from premium app
rom:trigger 2.9.3
kernel;overstock 1.4.3
theme:custom mash of all orange/tangerine
Ok, thank you for your help. I didn't know if it was having a problem or something.
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Tbry said:
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Click to expand...
Click to collapse
This should help you out.
Thanks for the link. I decided it is probably a better idea just to get a new kernal. My vibrant has andriod 2.1.1 right now. I read elsewhere that custom kernals come with clockwork recovery, plus that would eliminate any problems with my current kernal and the 2.2.1 ROM I am about to flash... Right?
Just need a guide for it.
Edit: I'm trying this. How long is it supposed to take?
Edit2: it failed when it trys to stop the adb server.
When first installed mik's CM7 on my LG P500, it comes with the standard Android System Recovery. I can reach this from holding down the POWER key, and it gives me an option from the drop down menu for (Reboot, Recovery etc.). When you choose Recovery, you get booted to the Android System Recovery menu.
Now, if you launch ROM Manager, and install CWM into your device, you have to launch the CWM recovery from within the ROM Manager app itself. Else, if you use the POWER key, and choose Recovery, you get stuck on the LG logo. There is no way out that I know of. I tried removing the battery etc. but to no avail.
So, I tried the only scenario I know, I booted into EMERGENCY MODE, and recovered the device using KDZ with a Telus firmware load for the LG P500, and gingerbreak the device again, and then re-wiped it and put back mik's CM7 OS on it again.
It was a weird scenario. Anyways, I now only use the ROM Manager and access the CWM recovery from the ROM Manager only.
When holding down the POWER button, I still have the Recovery option shown, but I have not tried to see what happens if I choose it. I did not feel like re-installing all the apps all over etc. Now I have backups just in case.
luckydog2006 said:
When first installed mik's CM7 on my LG P500, it comes with the standard Android System Recovery. I can reach this from holding down the POWER key, and it gives me an option from the drop down menu for (Reboot, Recovery etc.). When you choose Recovery, you get booted to the Android System Recovery menu.
Now, if you launch ROM Manager, and install CWM into your device, you have to launch the CWM recovery from within the ROM Manager app itself. Else, if you use the POWER key, and choose Recovery, you get stuck on the LG logo. There is no way out that I know of. I tried removing the battery etc. but to no avail.
So, I tried the only scenario I know, I booted into EMERGENCY MODE, and recovered the device using KDZ with a Telus firmware load for the LG P500, and gingerbreak the device again, and then re-wiped it and put back mik's CM7 OS on it again.
It was a weird scenario. Anyways, I now only use the ROM Manager and access the CWM recovery from the ROM Manager only.
When holding down the POWER button, I still have the Recovery option shown, but I have not tried to see what happens if I choose it. I did not feel like re-installing all the apps all over etc. Now I have backups just in case.
Click to expand...
Click to collapse
Many people, including me, have faced issues with ROM manager. Some times when booting into recovery or taking a NAND backup, it performs a full wipe of the phone and it has been reported many times on this forum.
Are you saying that you installed Mik's CM for the first time through the Android recovery? The general procedure is to root -> install CWM recovery(either through ROM manager or through the android recovery) -> install the ROM through the CWM recovery. After this, whenever the 'Power' button is held, the 'boot into recovery' option would directly lead to CWM.
I installed CWM through ROM manager. It successfully installed CWM but wiped the phone completely. Stopped using ROM manager from then onwards.
No. I installed it as you mentioned below
-> The general procedure is to root -> install CWM recovery(either through ROM manager or through the android recovery) -> install the ROM through the CWM recovery.
But when I hold down the 'Power' button, instead of 'boot into recovery' option which I thought would directly lead to CWM, it hanged at the LG Logo. I have not tried it since. I now only go into CWM recovery from the ROM Manager.
luckydog2006 said:
No. I installed it as you mentioned below
-> The general procedure is to root -> install CWM recovery(either through ROM manager or through the android recovery) -> install the ROM through the CWM recovery.
But when I hold down the 'Power' button, instead of 'boot into recovery' option which I thought would directly lead to CWM, it hanged at the LG Logo. I have not tried it since. I now only go into CWM recovery from the ROM Manager.
Click to expand...
Click to collapse
If ROM manager works fine for you, then go ahead. It is the easier way to take backup/boot into recovery, but it does not work for me
it is safer to use CWM Recovery than Rom Manager installed on Cm7
Ok, what is the difference? Its the same thing isn't it? I am using CWM recovery but to get to CWM recovery, I am launching ROM Manager and choosing the option to boot to CWM recovery. I am not using the POWER button method option to get to the recovery. I am not certain the POWER button won't work but the last time I did that, I was hit with the stuck on LG Logo.
I did not notice that by holding down the POWER button, I have three options:
- reboot
- recovery
- bootloader
Not sure what the bootloader option does.
Ok
1. Booting to recovery through rom manager sucks because rom manager support for our phone is not correct.
2. Booting to recovery through power menu sucks because reboot in power menu causes an unclean shutdown which can screw with your filesystems.
So, in conclusion, don't use either of these methods, turn off the phone and use the button combination.
Sent from my LG-P500 using XDA App
mihir287 said:
Ok
1. Booting to recovery through rom manager sucks because rom manager support for our phone is not correct.
2. Booting to recovery through power menu sucks because reboot in power menu causes an unclean shutdown which can screw with your filesystems.
So, in conclusion, don't use either of these methods, turn off the phone and use the button combination.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Ok. Interesting. Did not know that. I will use the button combination to get into the recovery. It does work for me from the ROM Manager, but who knows how long that might work for if its inconsistent for you guys with the same phone as well?
Thanks guys.
It doesn't seem real common, but I seem to have permabricked my nook. I can't connect to it via adb, can't boot to recovery from sd or the emmc, and can't seem to get it to recover via sdcard. I've tried Adam's Unbuntu Unbrick, copying the recovery to the sdcard, and trying to recover to 1.4.2 via the sdcard.
How I broke it:
I installed Goomanager and installed TWRP, and then flashed to CM9 with the 3.0 kernel. The recovery and CM9 were working as well as could be expected, but CM9 had too many Sleep of Death issues so I decided I wanted to roll back to a nandroid backup of CM7. TWRP couldn't see my backups, so I decided I'd flash the recovery back to CWM via indirect's nookrecoveryflasher.apk. This was the end.
The symptoms:
I rebooted after using the nookrecoveryflasher flashing back to CWM, and now it just displays the n with the copyright info. It then flashes white briefly, then a slightly bigger n is displayed, it gets brighter, then dimmer, then a black screen (still backlit). The charger goes from red-orange to green after the screen goes black, and charging appears to be halted. If I hold down the power button for 8 secs, the backlight goes off and the charger light turns back to red-orange and it seems to charge. ADB lists no devices.
Are there any suggestions for things I should try that I haven't already? I thought this was pretty much unbrickable but something went really badly, and this should have been a relatively "safe" operation.
Update:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Did you try removing and inserting the sdcard back in while in twrp?
I stayed with cwm and I was able to flash both kernel versions of cm9 just fine. Since u already tried the 1.4.2 revert to stock, your situation seems quite troublesome indeed
Sent from my Nook Tablet using xda premium
I can't get into either TWRP or CWM now.
Hm sounds like your recovery is screwed up...
Sent from my Nook Tablet using xda premium
Do you know what kind of bootloader you are using? Is it cyanoboot?
Sent from my Nook Tablet using xda premium
Cyanoboot was installed when I installed CM9, but after trying to flash back to TWRP, it doesn't seem to be coming up any more.
Wow that's unfortunate. I was thinking if u were using cyanoboot you would be able to hold the n button to choose where to boot from...
Sent from my Nook Tablet using xda premium
Have you tried burning a clockworkmod recovery image to an sdcard and booting into cwm via said sdcard? If you can get this to work, you can flash the internal cwm recovery zip to overwrite the internal recovery partition.
Also try the 8 failed boots method. Each time you see the gray n logo dissapear when powering on, pressand hold both the n button and the power button until your nook tablet shuts off. Repeat this 8 times and your tablet should be forced to boot into recovery mode. Good luck!
Sent from my Nook Tablet using xda premium
I don't think that will work, as it sounds as though the recovery partition was broken with indirect's app (it happens and I think there is a thread he made with 1 method of fixing broken partitions but it requires you to have drivers set up properly for it).
I had this same thing happen to me when indirect pushed his new app that supports the 8GB and 16gb models out. I got the big N and I ended up flashing cwm via sdcard cwm and then flashing cm9 again via the newly flashed internal cwm.
Yes I've tried putting CWM on the sdcard but the same thing happens. I've also tried 3 different sdcards 2,8,16Gb. I've tried meghd00t's repart.img and it all behaves the same. It's as if the code that gets called to read the sdcard is broken now.
It sounds like after that white flash is when CMW should load but instead I get a bit bigger n, and then it goes black.
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
comat0se said:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Click to expand...
Click to collapse
try locating the stock 1.4.2 rom in the development section and flash that. see if it works.
In general if you are in CWM you have adb access at that time. The world is at your wish when adb works. Push stock recovery, etc., etc. Instead of trying to flash (which continues to fail) use adb to recover by of the many methods available. I would begin with pushing stock recovery and boot recovery (by command or power + N).
Good Luck.
Lars for tobdaryl
Did you flash TWRP using the .zip from the 1st-2nd page? That TWRP .zip is bugged so as not to recognize an external sd. I had a problem like this until I used a recovery sd (ill put a link in here in a sec)
I had a terrible 13 hour run of trying to fix it before I finally got it to boot, then I opened up my gmail inbox and found out that I had won a Transformer Pad 300 from Phandroid.com, needless to say after 13 hours I was nearly hysteric when I found this out, hope your issue gets resolved.
I also couldnt mount sd, couldnt adb, couldnt fastboot, couldnt get sd to show up in TWRP so maybe this method will work:
http://forum.xda-developers.com/showthread.php?t=1640958
Sent from my Transformer Prime TF300T using XDA Premium HD app
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.