THIS IS A SPRINT INTERCEPT!!!!
So I loaded UB droid onto my intercept now for whatever reason it decided to load stock recovery and hang at UB load screen. Now the phone wont boot to android and is stuck and bootloops. Heres what i have at my disposal.....
1. A copy of SW Update, but its the copy for the moment......I tried to connect to my intercept but it searches and cant find it.
2. The ability to get to stock recovery and download mode.....So its a soft brick if i had a signed update pack that worked i could load that over it. or a way to turn of the check for signed zips? I tried loading the update.zip file that they gave us when the first one bricked our phones but it didnt work said (status 7)????
3. A computer with ADB fully loaded...if i need to i can use that to help unbrick the phone.
4. I also have the following files DLO5 completely stock.zip (unsigned), UB4, the update.zip file for the intercept (signed), the mr which is in a tar.md5 file.
Heres what ive tried....
1. Using SWupdate to load the ship MR:
Problem with this method is that the SWupdate cant find my phone..and the intercept is coming up as a unknown device.
2. Loading a stock update.zip file... Comes back with installation aborted....see above.
Any suggestions?
http://intercept-root.googlecode.com/files/interceptRoot.apk this is how i did it over the phone to a friend i had him download and install the intercept root and cmwflsher then install the almost stock rom" then just wipe davic and install ud6 then the super kernal package it works well and has support for teathering ! should be set!
unlocked bootloader att. atrix. honeycomb rom. faux oc kernal
The same thing happened to me, and this was the perfect solution. Just download the almost stock, apply it in CM01, then after that wipe EVERYTHING!!
But unless you can charge your phone every couple hours, i wouldnt suggest UB6. It destroyed my battery life... I redid that almost stock and my phone hasnt needed to be charged for almost 2 days... UB6 is a battery raper, but its a sweet ROM
I ended up getting in download and flashed a stock image from there I rooted it loaded recovery etc.
Sent from my MB855
i screwed my phone too cuz im a noob ofcourse. i tried rooting my phone using inxane0381intercept.tar with SWUpgrade and then i put a custom recovery on it, and it wont boot
i can get into the custom recovery and the SWU download mode.
please help me
its all good if no one feels like helpin, i shoulda never messed around
Related
Ok, I installed Clockwork a while ago, then removed it and unrooted (I no longer needed root access, and I'm not doing any image flashing or anything that requires it). But after removing clockwork, it still boots to that first when I reboot my phone. In case if I ever have to take my phone in to VZ or something, how do I stop it from booting to that? I'm guessing it's not just a normal app, since I've reset to factory since then to try to resolve another issue, and it's still appearing, so I'm guessing it installed itself into the ROM.
I basically rooted my phone originally to install Titanium Backup before doing the factory reset, then I was thinking of trying some custom ROM's, but I decided not to (other than a performance increase, there's nothing else I really care about right now that custom ROM's would provide). So I installed Clockwork Mod and everything else RLM703 listed (http://forum.xda-developers.com/showthread.php?t=814299&highlight=guide), then removed everything after I decided not to mod it.
I can understand your concern on the not flashing, however if you do not flash i think you also still have the Superuser app (even ifyou dont have root rights) that itself would also void your warranty. The easiest, fastest, and safest way is to Flash it using the Method below.
Go To (droid-life .com /2010/09/21/how-to-return-droid-x-back-to-android-2-1/)
((**As a new user i cant post outside links so delete the spaces after life com in order to get the proper working link.))
**
You will download 2 things. The SBF for 2.1 (Which afterwards you can use OTA to reupdate to 2.2).
RSD Lite: This program is used by Motorola to flash phones so its not some unstable application that will mess up.
After you install the drivers, THEN install RSD Lite. You must Run RSD Lite as an administrator. Shift Click RSD Lite and choose Run as Administrator (Even if you are on an administrative account). Afterwards you just navigate from RSD lite to where you have your SBF Saved, Boot your phone into bootloader, then press start. Takes about 5 minutes and you are back to a brand new Droid X.
Like i said i understand your concern on this, and im deeply sorry if you get a rare case and it does decide to mess up, but i just flashed my phone 3 times yesterday using this method and never had a problem.
Hope this helps!
Ok, I know I created a backup through ROM Manager before I stalled Clockword Mod Recovery, but now I can't find it... However, I've been having some minor issues with my phone ever since I updated to 2.2, so maybe I'll just find a stock SBF and flash back to that... That link I posted has a droid x guide, with a link to a stock 2.2 SBF, so I can just grab that and flash it tonight or something. Or even just download it at home and keep it in case if I need it down the road...
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
What version of CWM did you flash?
Pm me and we will use a chat service (aim, yahoo messenger) and I will walk u through it.
My suggestion of what I would do is this. Find a windows computer somehow. Go to the development section and look for the sticky about rooting the ns4g. Look for the link to flash the d720 back to stock. Download all those files to a flash drive. Take the drive to the windows computer and set things up then flash the phone back to out of the box stock.
Then you can go back to the Mac and do the root and 3024 cwm recovery and rename the sh file that puts stock recovery back in at boot time. After all this you can do what you want but I would suggest staying with the stock experience. This might be extreme to fix this but in my opinion, I wouldn't waste time trying to fix it, especially since you are new to this. It's like computers, yeah you could try to fix it but you could be opening a can of worms. It might take less wasted time putting it back to complete stock instead of f-ing around trying to figure out what happened and how to fix it. You could take hours trying to fix an install of windows that keeps falling on it's face, or you could format and install windows fresh and new in maybe thirty minutes. Which is easier?
CM7 will not work at the moment because it still uses 2.3.3, go find instructions for a 2.3.4 Nandroid. if you want though,i heard that supeaosp works on a ns4g.
Sent from my Nexus S using XDA App
westinl said:
Let me first start off by saying that I am on a Mac.
I used these directions to get my phone unlocked and get ClockworkMod Recovery or whatever running on my Nexus S 4G.
I then loaded Cynogen onto my SD card, booted into Clockwork, wiped my phone, then tried to install Cynogen. It failed- it couldn't install boot.img or something.
Now, when I try to boot up my phone, it just shows the Google logo with the unlocked icon below it. It never successfully boots. I can still get into Clockwork Recovery, but below every menu section over the logo, it always shows some error like
Code:
E: failed to something something /cache
Can you guys please, PLEASE instruct me on how to get my phone working normally? I don't need it unlocked, just running the stock OS.
Anyone who can successfully help me do this on a Mac will receive a nice PayPal donation if they wish.
Thank you so much in advance.
And yeah, I know I shouldn't have been attempting this because I am such a n00b.
Click to expand...
Click to collapse
Dude, you can't flash regular Nexus S ROMs on the Nexus S 4G.
Reflash the latest clockwork recovery.
Use fastboot flash recovery recovery.img
then...
Go to recovery, mount the USB storage, and put this zip on the usb storage:ROM
Go to recovery and flash that zip
here's the recovery that works. cwm and stock. How many times is this going to happen with new people and this phone in this forum section before a new subsection is made? We are going to be putting out a lot of these unnecessary fires with people making first time mistakes until something is done so as to not confuse them. Some don't realize that there are different versions of the same phone that aren't necessarily compatible with each other.
The way things are set up now, it isn't making this problem go away. I think that a different method should be tried if the current one isn't working too well. I'm flogging a dead horse now......
I'm looking to root my new NS4G as well -- and do it right the first time. On a Mac as well.
If the similarly-suited OP had issues I'm a bit more skeptical about my effort.
A separate forum might be necessary so people with the D720 hardware don't have near-brick experiences.
Sent from my PC36100 using XDA Premium App
soooo....did the op ever get it running again? i wonder if anyone ever took up on his paypal offer
Hello everyone, First off I would like to thank all of those that have posted on this site and contribute to it.
Now to my problem. Let me share a little history of how everything started.
I first rooted my MT4G about a year ago, Tried to use IcedGlacier but it was not loading properly so I used cyanogenmod 6 I believe? I wanted to try IcedGlacier but It still was not loading properly. Then when I tried to restore it would not restore properly. At this point it appeared to be bricked but bootloader still worked but the PD15img file was not found. So after some researched I downloaded it and it restored my phone back to factory condition. Now I want to try other roms again because I'm getting bored of stock and attempting to load different kernels but this is where my issues are beginning.
As you can see in the attached photo that is what the bootloader looks like. I thought it was weird that next to hboot it says "HBOOT-0.85.2007 (PD1510000)".
(I tried to post the image but since I'm a noob I and unable. If you want to see the screen shot of my bootloader just message me.
I was thinking maybe this is a reason as to why now No other rom but the stock one will load. Also what is weird is that when it goes into bootloader it still says PD15img is not found but the phone will start up fine with the stock rom.
The phone remains rooted but No Rom or Kernel will Load and fully install.
When It loads roms it goes to install it shuts off and reboots into stock rom.
I tried to Use the PD15IMG.zip on the SD card to see maybe if it didn't load properly but it will begin to load with the blue bar in the corner but then after it goes all the way up nothing else happens.
I have been trying to look for answers but haven't found any real answers that help me fix my problem.
So if someone can help me I would greatly appreciate it.
The "no PD15IMG.zip" message is supposed to appear. When the bootloader loads, it checks the root of your SD for that file, and if it's not there, you'll get that message. Nothing wrong with that.
Since you're perm-rooted and running the engineering boatloader, you just need to make sure your recovery image is good. If you haven't already, download ROM Manager from the Market and use that to install a fresh copy of ClockworkMod recovery. From there you should be good to flash any ROM you want.
Thanks, I did what you said plus I realized when I was downloading the roms using a Mac and my Mac would unzip the file automatically and trying to compress it back to a zip doesn't work at all. But thanks alot for the help!
If the PD15IMG.zip doesnt work you probably dont have the part7-xxxxxxxxxx.zip file on your sdcard
Sent from my HTC Glacier using XDA Premium App
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
Hey guys!
My friend just got the G900F and I wanted to help him root it and install custom recovery + custom rom.
1. I installed custom recovery
2. I rooted the phone with towelroot
- Everything seemed to work perfectly, I used apps that required root and had no problems.
3. I made a backup of the phone's original software
4. I made a backup of the phone's EFS
5. I updated the modem+bootloader to Lollipop latest versions for G900F (I did this when I had 4.4.2 installed on the phone)
6. I booted into TWRP and made a total wipe
7. I Installed XtreStoLite INTL 2.2 - I choose Ktoonsez's kernel and NEE as I am from Sweden.
8. I rebooted the phone and now the phone is in an endless bootloop - says Set Warranty Bit: Kernel and the Samsung Logo, then it reboots and vibrates 2 times.
I've tried to reinstall TWRP via latest ODIN v.3.10 - it works to install but I cannot go into recovery as it just restarts and the same bootloop as step 8 happends.
I've tried to reinstall CF-Auto-Root via latest ODIN to restore the original Recovery - it works to install it, I can see on the phone that it is recovering original recovery et.c but after that it ends in a bootloop as step 8.
I have no problems getting into download mode, KNOX is 0x1.
I don't know what to do and I seem to lack the knowledge how-to search correctly to find an answer for this model(?) How can I either get back to stock or make a total clean adb fastboot?
I'm guessing its semi or hard bricked? I don't understand why as I followed the steps 100% from this guide http://forum.xda-developers.com/showthread.php?t=2699648
then I used the guidelines edgarf28 gives when installing the XtreStoLite rom and updating the modem/bootloader.
Help is very very appreciated.
Probably the Kernel not playing nice with the ROM
Install Samsung drivers on PC (KIES3 installs them, or grab from samsung.com)
Boot the phone into download mode (Volume Down, Home & Power)
Flash a stock ROM using ODIN 3.10.6 from sammobile dot com, or from the link in my Sig (United Kingdom G900F ROMS)
Great! Thanks. Exactly what I was looking for, I'm not the best on the search function. I did actually try to find the version needed to totally reboot via ODIN but didn't find it. I made the process and the phone works again, I will try to reproduce the steps but I guess I should skip Ktoonsez's kernel? Any idea why it doesn't work with it? As it is baked into the rom's aroma installer I thought it was compatible.
The kernel being the problem is just a guess, could have been something else, but from what you said, the only step I can see that might have bricked it was an incompatible Kernel, or maybe it didn't flash correctly and corrupted something
You can try flashing it again now you know how to recover the phone, see if it was just bad luck - best to reboot after each step to make sure it's working up to that step, then if it fails to boot after doing something else, you know exactly which step went wrong and can avoid it next time
Alright, made the exact same steps as before and it booted after every step. Last step was installing the ROM and it worked fine, after it says the same thing but this time I do not end up in a bootloop. Waiting for the phone to start for the first time, usually takes awhile.. I have seriously no idea what went wrong, only thing I could think of is that the phone was on 4.4.2 on the first try and the second I used your 5.0.. so.. conclusion is that.. that was the problem.
These things happen, I flashed back to KK to give it a try a few weeks ago, first flash ended in a bootloop, so I flashed the exact same KK ROM again, exact same process, second time it booted fine
It's what makes things like this fun & interesting I suppose, always something to learn
You're right! I'm happy that you helped me! Works perfect now, I'll continue to tweak things to give my friend the best experience... so nice to remove all the bloatware! What a beast compared to original.....