Related
EDIT: Ok, this isn't the I can't boot into WG-Slide thread =P
I want to make it more clear that there is absolutely no point in flashing the Engineering NBH
All it does is downgrade your radio, recovery, boot, and system images
The only image that mattered with the Engineering nbh doesn't get downgraded
I repeat something here... Using the Engineering nbh is NOT what gets you adb in recovery / clockwork / etc
Repeat again.. it is NOT what gets you that
Final Note: Keep in mind downgrading your radio isn't that safe... (anyone end up with one of those bricked G1's and had to get an exchange or even worse do a JTag?!) That could possibly happen if they changed the SPL version to a higher version than the radio compensates for - be careful!
Just wanted to let everyone know that flashing the ENG build is unnecessary and now found to be harmful...
Using the ENG build does NOT replace the SPL - which controls the ability to use fastboot or the ability to flash a recovery.img outside of an nbh file (thus we are unable to get ClockWork recovery to stick after reboot)
[This is the current theory, but using the ENG build then trying to flash any ROM that uses the majority of the /system like WG-Slide will not boot]
Using the ENG build does replace the recovery.img which is still stock recovery (unable to flash test signed update.zip files) but with an older kernel which is causing problems
Normal version of ClockWork recovery contain it's own kernel in the recovery.img - with our rooting situation...
When doing the root process to get into ClockWork recovery it maintains the kernel from the recovery.img already on the phone and just pushes is in the ClockWork binary, images, and scripts
It seems as if the older recovery.img has incorrect knowledge on the partition sizes with the SPL on the stock phones such that the /system partition is a smaller size than it really is
Which is why, you can flash Eugene's with no problem because he keeps the system partition size down in his builds and in the latest uses deodex'ed apps
In WG-Slide, after flashing there is only around ~7mb to spare (which is ok because you never write to the /system after flashing a ROM)
So for anyone wanting to try WG-Slide or ROMs coming out in the future that do use the full system partition size, you will have to revert to the original NBH at: http://bit.ly/wesaspin#280
You can do this:
Flash the production NBH from above
Redo the root process (only to the point where you get into ClockWork recovery (if using Eugene's)) and do a nandroid restore (this will only flash your boot.img, system.img, userdata.img (aka your data)
recovery.img will not be flashed via the nandroid process (because of the locks on the SPL)
wesgarner said:
...
Click to expand...
Click to collapse
Wes, awesome! Thank you for tracking down this issue. It is much appreciated.
After placing the downloaded ESPRIMG onto the root of your sdcard
1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again..
OH, delete ESPRIMG after otherwise it will load each time you boot into bootloader....lol...just happen to me....
so those of us that are rooted should go and UN-root and then re-do everything this way?
tubaking182 said:
so those of us that are rooted should go and UN-root and then re-do everything this way?
Click to expand...
Click to collapse
Well, to flash any ROM you have to go through the process to get to a usable recovery...
so really you are just putting the nbh on there then going back through the recovery process (as you would if you wanted to flash a diff rom from where you are now), and flashing your current data and ROM back to the phone (using nandroid)
here.david said:
1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again..
Click to expand...
Click to collapse
Oo yea I forgot those steps lol
plus... forgot to mention to put the nbh on your sdcard - but it's all good lol
Thanks for the more important details past the blah blah blah I posted lol
Just when I think I'm getting the hang of things... If anyone can help I would much appreciate.
These steps:
"1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again.."
Are how to get back to stock Slide status correct? Does that mean it will be unrooted?
I never did the eng-release flash because I have yet to flash more than one ROM. Is there another method to flash the ClockWork recovery that ISN't using the loop exploit?
Thanks for the hassle
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
You need time the battery placement with holding the volume down power button. Hold the buttons and then place the battery in while still holding the buttons. That should get you where you need to be.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Alright so if WE DID flash the Eng-Build before, we:
1. Flash production
2. Re-root
3. Flash new ROMs
HebrewToYou said:
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
Click to expand...
Click to collapse
Have the lower volume button pressed already while putting the battery back in.
Oakley44 said:
Have the lower volume button pressed already while putting the battery back in.
Click to expand...
Click to collapse
Tried it. No luck.
EDIT: Left the battery out for a few minutes. Didn't auto-boot upon putting the battery back in. Was able to pop into fastboot and access recovery. Trying to sort out my giant error...
HebrewToYou said:
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
Click to expand...
Click to collapse
Man... that sucks! Hmmm..... it looks like you bricked it. Remove the battery and unplug it from any usb or power cord and wait a while. Then put the battery back in....
Make sure your USB is unplugged! If you don't the phone will autoboot and get stuck in the loop.
sino8r said:
Man... that sucks! Hmmm..... it looks like you bricked it. Remove the battery and unplug it from any usb or power cord and wait a while. Then put the battery back in....
Click to expand...
Click to collapse
This worked, thankfully. Meh...
So, at some point I went from having to spoof the update.zip signature to not having to do that to get into clockwork.
What allowed that?
Will the update.zip sig have to be spoofed every time I want to get into Clockwork Recovery if I reverted?
Sent from my T-Mobile myTouch 3G Slide using XDA App
So the problem appears to be that after rooting and booting into ClockworkMod, I'm getting MD5 checksum errors when trying to nandroid restore. I try rebooting recovery and flashing update.zip and I get a signature verification failed error.
This never happened when I flashed the eng nbh after rooting. I can't get this **** to stick. Any thoughts on what I'm missing?
Jeebus, this is driving me nuts. Not only do I have to do the adb devices loop spam trick to get clockwork to boot up into the custom recovery now, I can't frickin get my Nandroid restore to pass MD5 checksum.
Any insight?
Until this issue is resolved I must firmly recommend that nobody else try this as it doesn't appear to work -- unless I'm missing something very important.
Without flashing the eng build you...
Can't boot into ClockworkMod from the stock recovery without repeating the root process
Can't restore your nandroid backup
Not only that, attempting to flash wesblend 1.0.2 after following these instructions caused the worst bootloop I have yet to experience.
HebrewToYou said:
Until this issue is resolved I must firmly recommend that nobody else try this as it doesn't appear to work -- unless I'm missing something very important.
Without flashing the eng build you...
Can't boot into ClockworkMod from the stock recovery without repeating the root process
Can't restore your nandroid backup
Not only that, attempting to flash wesblend 1.0.2 after following these instructions caused the worst bootloop I have yet to experience.
Click to expand...
Click to collapse
Yikes! Well, I think this throws Wes's theory out the window, lol! Back to the drawing board...
Hello. Right now, I am in the process of installing a custom ROM on an HTC Evo 4G LTE. I unlocked the boot loader, put TWRP on it, copied Paranoid Android on it with Gapps, and installed the zip. The phone is still in s-on mode and is stuck at the Paranoid Android screen. I have no idea what to do. I have to get it fixed ASAP. Please, help.
well for whatever reason paranoid android is not loading .. so ..go back into twrp a press reboot>system.. and you phone should reboot back into your previous rom...or you can press restore and choose the rom listed there.. and follow prompts from there.... that will get you back to square one.. you can figure out why the new rom wont load from there... make sense?... hopefully you DID make a backup of your old rom!!!
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
oh ya to get back into twrp .. hold down the power button and the vol down button at the same time .. that will take you to the boot loader screen .. scroll down with vol. button and choose "recovery" .. that will get you back into twrp.. easy cheesy
jceccoli said:
Hello. Right now, I am in the process of installing a custom ROM on an HTC Evo 4G LTE. I unlocked the boot loader, put TWRP on it, copied Paranoid Android on it with Gapps, and installed the zip. The phone is still in s-on mode and is stuck at the Paranoid Android screen. I have no idea what to do. I have to get it fixed ASAP. Please, help.
Click to expand...
Click to collapse
Sounds like you didn't fast boot the kernel
heliguide62 said:
well for whatever reason paranoid android is not loading .. so ..go back into twrp a press reboot>system.. and you phone should reboot back into your previous rom...or you can press restore and choose the rom listed there.. and follow prompts from there.... that will get you back to square one.. you can figure out why the new rom wont load from there... make sense?... hopefully you DID make a backup of your old rom!!!
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
oh ya to get back into twrp .. hold down the power button and the vol down button at the same time .. that will take you to the boot loader screen .. scroll down with vol. button and choose "recovery" .. that will get you back into twrp.. easy cheesy
Click to expand...
Click to collapse
Well, I never made a backup of the original stock ROM. I tried everything I could, but then realized I was in S-On mode, and HBOOT is 1.19. Therefore, I think there is no way around it. I just did "locked" the boot loader and ran the RUU. That has gotten it back to stock. Worst part is, I convinced my friend to do this because I had rooted my One S, now, he's never going to want to root again. He didn't back anything up to his computer, just his SD card, which was wiped. Damn. Thanks for the reply.
no prob .. well the the upside is .. you were able to get it back .. and you didn't brick the thing
Like om4 said, all you needed to do was flash the boot image. That is one of the known limitations with your hboot version.
http://forum.xda-developers.com/showthread.php?p=31102864
Sent from my EVO LTE
With s-on you may flash any Rom with a custom recovery. Just not (kernel,bootimg,radio) so what you can do is
HTC dev unlock,root stock rom
download flash image gui.apk
download the Rom and gapps
Open flash image gui
Flash the paranoid rom from FIGUI
Reboot into recovery and flash again
Now you should have a working boot image and rom.
Sent from my EVO using xda premium
Similar issues
Hey all, noob here.
This is as similar to the issue I am having now as I can find. So here's what up as far as brass tacks.
HTC EVO 4G LTE "Jewel"
TWRP loaded and functional
Rooted, (tampered) had SuperUser
Nothing in the internal SD card (explain momentarily)
No OS. Yeah, no.
S-ON due to 3.17.
Lost my Nandroid
Don't know much else cause if I take it out of recovery I have to suffer through a bootloop, but I will get more info once I get an idea of whats happening.
Down and Dirty:
So I have rooted several devices, My old Evo 4G's, a couple SIII and S4's and I thought I could do this in one morning. So I got it rooted, using WinDroids help, but skipped S-Off as 3.17 was too new for the software in the toolkit. Did some reading, read multiple times that S-ON was cool to just a ROM which is what I wanted, So I DL'd the ROM, loaded to internal memory, loaded up TWRP from recovery, ran it.
Failed.That's ok, I have the nandroid, I suffered a boot loop until I learned how to escape, Recovered, and I tried again with a fresh DL. Same. So I nandroided and was looking everything over. Then I butter fingered everything. I factory reset the phone, dumping my nandroid and my OS out the window. No I have a phone with no OS and my only access to it is through USB mount in TWRP. How can I either
A) get it back to stock ROM or
B) install the AOSP ROM I was going for. Any more information required I will be more than obliged to give.
I appreciate everything I get I promise!
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
slowfncar said:
With s-on you may flash any Rom with a custom recovery. Just not (kernel,bootimg,radio) so what you can do is
HTC dev unlock,root stock rom
download flash image gui.apk
download the Rom and gapps
Open flash image gui
Flash the paranoid rom from FIGUI
Reboot into recovery and flash again
Now you should have a working boot image and rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is what I think happened to me, by the way. How would I do a ROM without a Kernel? Just yank the kernel folder out? I doubt it. I used to know but I'll be honest, I have only dabbled recently, it's been a while since I kept up with the science precisely.
(No asking poster, Asking in general)
Read this and also this.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Read my Hboot guide in my sig, and also check out the guide on how to fix your phone after a system wipe. I think you'll find what you're looking for.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
JukeRedlin said:
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
Click to expand...
Click to collapse
You got it:good:
Anything else, just ask.
JukeRedlin said:
Ah, I read your guide before, I misread some in trying it, I'll give it another go now I re-read it.
[EDIT:] Read first one, not the second. I shouldn't have any issues, I'm pretty techie, Just need the right reading material. Appreciate it mate!
Click to expand...
Click to collapse
Up and Running on Mean Bean, should be able to get anywhere I need from here. Thanks Fin, and all who helped before~
Not a problem.
Sent from my HTC EVO 4G LTE
Hello there,
i have been searching for hours in the net but i can't find any help!!!!!
So,here's the case:
i rooted my x10 mini so i can install custom firmware.After that i installed xrecovery via root explorer.Until here everything was working perfectly.After that i installed flashtool and unlocked the bootloader.I restarted the phone and got into recovery menu by pressing "back" several times when the 'White logo came". In recovery menu i made a factory reset and wiped cache.Then i choose to install a custom firmware from zip file but an error came "install failed" or something like that.After rebooting the phone nothing happens.The phone does not vibrate,no green light the comes,i can't go in flash mode and if i press "home and power" nothing happens and of course not detected from the pc.The phone seems to bee 100% dead!!!Is there a way to recove it??????
Please i NEEEEDD YOUR HEEEEEELPPPP!!!!!!!!!!
disconnect the battery and rstaret phone
Sent from my E10i using xda app-developers app
i have already done this but nothing happens
Somethings wrong. Tell me, what are you FIRST trying to achieve?
a rooted stock firmware(2.1-update1) with unlocked bootloader?
or a custom ROM working on top of a custom Kernel?
i firstly tryied to achieve a rooted phone with custom firmware and now i am trying to get it turn on!!!
petran_gr said:
i firstly tryied to achieve a rooted phone with custom firmware and now i am trying to get it turn on!!!
Click to expand...
Click to collapse
Put it on the wall-charger for an hour or so, see if something happens.
custom firmware? what is that? do you mean custom rom and a custom kernel. If you are trying to have one of this roms:MiniCM7/8/9,GingerDX,MiniCM7pro,ArcMiniNXT™,etc which is commonly working on top of the nAa kernel. I think you should flash the kernel first to have a CWM recovery not an Xrecovery then flash properly a ROM.
i can't go into flash mode,the phone does nothing!Is there another way to recover it back to stock???
Find/Search,google it and ask others on this forum on how you can get an Stock Firmware. It's worth 224mb. everyone should have one for this will be the back to stock restore point.
you can use it by flashing it to Flashtool. afterwards you are back on stock. not rooted, and got it's warranties back.
---------- Post added at 10:44 PM ---------- Previous post was at 10:41 PM ----------
you can go to flashmode with a trick, so you can flash your stock firmware.
power off, remove the battery. attach usb cable, hold back button, then insert the battery. It will be on flashmode. =') chiiiiiiiing. your x10mini is back.
---------- Post added at 10:47 PM ---------- Previous post was at 10:44 PM ----------
I found it.
SmG67 said:
for unlocked bootloader: download
for locked bootloader: download
They're about 210mb, although the site may indicate differently... just wait till the download is done. Put it in the firmwares folder and flash...
Click to expand...
Click to collapse
i tried the trick with the battery removal but it does not connect.I also put it in wallcharger for about an our but nothing happens.it is completely bricked
I still don't believe you are in a HARD BRICK.
I never had one. The LED doesn't turn on? It should turn green. and should be connected in flashmode.
no the led is also dead,
i thing it is the bootloader that bricked the phone.i read something about the week of construction but am not sure what it is.Mine is 10w22 if it's any help.
petran_gr said:
no the led is also dead,
i thing it is the bootloader that bricked the phone.i read something about the week of construction but am not sure what it is.Mine is 10w22 if it's any help.
Click to expand...
Click to collapse
After unlocking the bootloader you could still get into recovery, so that didn't brick your phone. Which Firmware were you trying to install when it failed?
SmG67 said:
After unlocking the bootloader you could still get into recovery, so that didn't brick your phone. Which Firmware were you trying to install when it failed?
Click to expand...
Click to collapse
see? base on what he said, theres nothing to cause a Hard brick on his device. He's even on to x10mini not x10mp(that has some more issues because of the flex)
---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------
I really don't believe you are in HARD BRICK.
if you can only go to flashmode you can have it back. think of any way to go to flashmode. or try and try again to do what I told you to enter Flashmode. you should open the flashtool then try my trick.
i tried to install this rom:
http://forum.xda-developers.com/showthread.php?t=2054144
petran_gr said:
i tried to install this rom:
http://forum.xda-developers.com/showthread.php?t=2054144
Click to expand...
Click to collapse
ooooh the sevenbean. there should be another requirement, the CWM recovery. not the Xrecovery. things you should have done are the following:
1. Root
2. Unlock the bootloader
3. Install the nAa-JB-03 kernel
4. Enter CWM recovery
5. Full wipe(wipe data factory reset, Wipe cache, Wipe Dalvik, Format Data, Format System)
6. Flash the SevenBean Rom.
and what about now??is there another way to get back to stock without flash mode?For example by copying files to the sdcard??
I don't think there is. If only you could enter the flashmode.
PS can you enter Xrecovery?
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------
how to flash KERNEL on xperia x8/x10 mini
no,i can's enter xrecovery mode because it does not even turn on
Your only hope is entering the flashmode. can you do an offline charging?
I have no idea what happened to my GNote, but the problem is when I reboot to ROM and unlock the screen the screen turns black, keys lit and that's it 'till I reboot and it happens all over again.
I'm looking for a fix or guide to completly wipe the phone and start over. Luckily I have my current ROM backed up.
Thanks in advance.
Are you flashing a kernel?
Once I flashed my favorite kernel with a new rom. It booted, but then I had infinite blackness. To fix it I booted into recovery, performed a factory reset, installed only a rom and was fine.
440bro said:
Are you flashing a kernel?
Once I flashed my favorite kernel with a new rom. It booted, but then I had infinite blackness. To fix it I booted into recovery, performed a factory reset, installed only a rom and was fine.
Click to expand...
Click to collapse
Nope, just a custom ROM, flashed 8 before this one and never had any issues. When my phone was working, I noticed something odd in root browser; some folders and files have their date set to 12/31/1969?????
I can still access TWRP and download mode.
youngunix said:
I have no idea what happened to my GNote, but the problem is when I reboot to ROM and unlock the screen the screen turns black, keys lit and that's it 'till I reboot and it happens all over again.
I'm looking for a fix or guide to completly wipe the phone and start over. Luckily I have my current ROM backed up.
Thanks in advance.
Click to expand...
Click to collapse
Put the phone in download mode, open Kies, plug phone into usb, in Kies select tools, firmware upgrade and initialization. Have your phones serial number handy (Can be found under the battery). Enter model number using all caps (SGH-I717) and follow the prompts. This will put the phone back to stock 4.1.2. You will loose root and recovery, but will be back to complete stock. By far the easiest, safest method to completely wipe and start over.
youngunix said:
Nope, just a custom ROM, flashed 8 before this one and never had any issues. When my phone was working, I noticed something odd in root browser; some folders and files have their date set to 12/31/1969?????
I can still access TWRP and download mode.
Click to expand...
Click to collapse
What rom are you flashing, and where did you get it from? If it's from a reliable source, and you're certain it's for your device, you might have a corrupt file. You can try re-downloading it and flashing again. If it happens again notify the developer and try a different rom.
rsfinsrq said:
Put the phone in download mode, open Kies, plug phone into usb, in Kies select tools, firmware upgrade and initialization. Have your phones serial number handy (Can be found under the battery). Enter model number using all caps (SGH-I717) and follow the prompts. This will put the phone back to stock 4.1.2. You will loose root and recovery, but will be back to complete stock. By far the easiest, safest method to completely wipe and start over.
Click to expand...
Click to collapse
WOW! Small little detail, huge difference. No wonder it wouldn't work, I typed all in caps except the {i}.
Thank you
440bro said:
What rom are you flashing, and where did you get it from? If it's from a reliable source, and you're certain it's for your device, you might have a corrupt file. You can try re-downloading it and flashing again. If it happens again notify the developer and try a different rom.
Click to expand...
Click to collapse
It wasn't the ROM, I've probably deleted one of them folders/files and f'ed up the system.
youngunix said:
It wasn't the ROM, I've probably deleted one of them folders/files and f'ed up the system.
Click to expand...
Click to collapse
I hate when that happens!
If you want to just fix what you've got you can reflash the SAME rom right on top of what you've got.
If you want a fresh start, in recovery perform a factory reset, install the rom of your choice, and enjoy!
After spending all night working on restoring the phone, at least the main issue is solved, I'm back on a custom ROM.
But I still see the same folders and files with date last modified: 12/31/1969. Can't believe I'm the only one with this issue.
KIES for me does not have the selection firmware upgrade and initialization under tools...I have Emergency Firmware Recovery and Firmware Upgrade Settings, which locks the program up (I'm on a Mac)...what happened is that I tried to do a upgrade that T-Mo was passing on, and can't boot past the screen that has the gray battery, or if I'm lucky, the Samsung Galaxy Note 4G Android 4G screen prior to the T-Mo jingle...phone has been wiped twice, at least...
And where do you see these files? Most likely they were on the usb storage and it didn't get wiped during ROM install.
What if I put all of the ROMs, etc., on the SD card, and attempt to restore that way?
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
Agoattamer said:
And where do you see these files? Most likely they were on the usb storage and it didn't get wiped during ROM install.
Click to expand...
Click to collapse
What files are you speaking of?
lildaddym said:
What if I put all of the ROMs, etc., on the SD card, and attempt to restore that way?
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
What files are you speaking of?
Click to expand...
Click to collapse
My response was meant for the OP.
Hey all i accidentally hit the OTA update "OK" button when it popped up on my screen. I've been deferring it for the past few months but my finger slipped and hit the "OK" instead of the "defer" and choosing a date to ask again.
I have a looping "Teamwin" logo and it keeps looping.. Cant seem to do anything. I've taken out the battery and then start it up but it still does the same thing.
Any advice, step by step to get out of this loop?
Thanks!
David
you can not OTA update with a custom recovery...time for a date with Odin.
Historical coodsen
droidstyle said:
you can not OTA update with a custom recovery...time for a date with Odin.
Click to expand...
Click to collapse
Would you care to give me a link to do this with a note 2, droidstyle?
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
Whats the key combo to see if i can boot into recovery and ill try it
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
stealthrt said:
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
Click to expand...
Click to collapse
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
droidstyle said:
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
Click to expand...
Click to collapse
Well i just started flashing in odin.... will update when its done.
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
And doing the volume down+home+power sends me to the same screen (WARNING!!!... custom os.. etc etc)
Any other advice?
stealthrt said:
Any other advice?
Click to expand...
Click to collapse
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
B_I_N_G_E said:
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
Click to expand...
Click to collapse
Yeah it still does the same teamwin loop doing it that way.
What else can i try?
stealthrt said:
Yeah it still does the same teamwin loop doing it that way.
I tried again to flash and it still is at the loop after a restart...
and also...
What else can i try?
Click to expand...
Click to collapse
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
B_I_N_G_E said:
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
Click to expand...
Click to collapse
ive only tried the root66 rom.
stealthrt said:
ive only tried the root66 rom.
Click to expand...
Click to collapse
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
Alright i flashed the bootloader and all seems to be fine. I got 2 tutorials mixed up so i though one was using bootloader as the ROM.
All is good now thanks droidstyle and B_I_N_G_E.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
root66 works on all devices with the current firmware since it does not contain a bootloader, recovery, or wipe data. Sometimes it will cause a bootloop which all that is needed is to wipe data in recovery.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
you need to boot into recovery and wipe data...if you can get into recovery the a full odin package will need to be flashed such as stock VRAMC3. However it looks like you figured it out.