Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?
Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?
Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!
Related
I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?
bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.
pretty self explanatory. I used safestrap, unistalled it, when i try to get to the stock recovery i pick it from the fastboot menu using the up vol key and then the phone just boots like normal, never goes to the recovery. any ideas would be hugely appreciated.
zeer.row said:
pretty self explanatory. I used safestrap, unistalled it, when i try to get to the stock recovery i pick it from the fastboot menu using the up vol key and then the phone just boots like normal, never goes to the recovery. any ideas would be hugely appreciated.
Click to expand...
Click to collapse
Are you still rooted? After rooting with any of jcase's methods (i don't know about the 4.4 one), rebooting to recovery just launches the rom without write protect. I'm not 100% sure, but I think you'd have to flash back to stock to recover stock recovery.
Why exactly do you want stock recovery back? Maybe we can work around it to get the results you want.
Also, you should post things like this in the Q&A forum.
JetOhmNet said:
Are you still rooted? After rooting with any of jcase's methods (i don't know about the 4.4 one), rebooting to recovery just launches the rom without write protect. I'm not 100% sure, but I think you'd have to flash back to stock to recover stock recovery.
Why exactly do you want stock recovery back? Maybe we can work around it to get the results you want.
Also, you should post things like this in the Q&A forum.
Click to expand...
Click to collapse
well im worse off now. wiped my system. no rom. no recovery. think im royally screwed.
Yup, safestrap replaces your recovery, and since you nixed safestrap, your phone has nothing to fall back to. You're phone will be fine, I did the same thing when I unrooted and tried to install the 4.4 update. You just need to flash the stock recovery files in RSDLite. Will you loose your data? Sure (or you can save what you want on your computer), but your phone will be fine. Let me know if you get messed up trying to do this.
I have Safestrap 3.7.2 and Lollipop rooted installed. I've googled and googled and can't find an answer to this. I booted into Safestrap to try to figure out how to delete an old NC1 backup I made. I hit the reboot/recovery button once. What a mistake. The phone booted into stock recovery. Now when the phone boots, I get a message saying Safestrap is disabled with the options of recovery or continue. Continue does nothing but gives me a blank screen. Recovery takes me into Safestrap, and I can't get the phone to boot back into Lollipop. If I hit reboot/system, I get the same Safestrap disabled screen. If I hit reboot/recovery, I end up in the stock recovery. It says to wait 10 seconds and it will boot, but all I get is a blank screen. I have Lollipop in the stock ROM slot with no other ROMs loaded. HELP!
Well the only thing I could figure to do was to ODIN back to NC2, use Towelroot to get root, install Busybox and Safestrap 3.75, install the OC1 rooted ROM, and reinstall everything via Titanium Backup. This time once I get the phone set up the way I want I will make sure to make a Safestrap backup. What a pain.
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
voigts said:
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
Click to expand...
Click to collapse
Since you're on Lollipop did you flash the OC1 kernel before leaving Safestrap? http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
voigts said:
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
Click to expand...
Click to collapse
Only thing I can think of is something in your Titanium backup is messing things up. If you happen to flash all that again (not saying to do) but if you do, I would boot into Safestrap (once you install Lollipop) and flash the OC1 kernel to see if it boots ok. (Before you do the Titanium Backup).
Thank you for the replies. I failed to realize that I needed to extract the lollipop file and then flash the SM-N900A_OC1_Kernel_Safestrap_Installer.zip file contained within AFTER flashing the lollipop file. Yes, I get the stupid award for the day. Duh....
I extracted the file, copied to MicroSD card, and then booted into Safestrap and flashed it. Hopefully things will work correctly now. I feel pretty stupid.
I need help myself.. Every time I try to flash any type of zip I get stuck in safestrap disabled
All,
I was rooted and installed twrp with PopRock rom. I decided I will return this phone via JUMP and wanted to unroot. I followed directions from:
http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
using odim 3.09 and firmware SM-N910T - N910TUVU1COD6 from: http://forum.xda-developers.com/note-4-tmobile/general/untouched-lollipop-firmware-t3098187
Everything looked like it is working accordingly BUT after the firmware install and reboot, all of my data/apps/even my fingerprint unlock is still there.
Did I do something wrong? I thought by installing a firmware like I did automatically wipes the phone. Is there something I can do to check to make sure I am in fact back to unroot status? I check the 'about phone' and everything looks right, I went into recovery 'volume up/power/home button' and went into stock recovery and not twrp. Just perplexed that after the firmware install, my data/apps is still intact.
Also, when I return the phone back to T-Mobile, what do they check?
Thanks!
thats what odin does it doesnt wipe internal you have to do it in stock recovery and all they check is everything on the outside works. @Nutzzer
Simplyeduardo said:
thats what odin does it doesnt wipe internal you have to do it in stock recovery and all they check is everything on the outside works. @Nutzzer
Click to expand...
Click to collapse
Ahhhh...did not know that. Ok, so all I have to do is wipe the phone via recovery and I should be good to go.
Thanks again!
So I had root on 4.4.2 with busybox and safestrap. I attempted to flash the OC1 file which is the stock 5.0 rooted lollipop, but it failed. Now my phone boots and shows the paddle lock boot screen, but bypasses safe strap and goes into an Android system recovery withe the android guy. Ive tried to target my original backup, but it fails. I'm going into the twrp directory on my external storage that has the stock backup, but when i click it, it opens and shows 4 md5 files.
data.ext4.win000.md5
data.ext4.win001.md5
system.ext4.win000.md5
system.ext4.win001.md5
Is there a way to get the phone to boot? I've just tried to wipe data as well but it connects to odin for a few seconds, then goes into removed status when it goes into Android System Recovery <3e>.
Have u flashed the twrp recovery?
Sent from my A0001 using XDA Free mobile app
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
lesd777 said:
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
Click to expand...
Click to collapse
Did you make sure to flash the lollipop kernel in safestrap before rebooting? You can't use regular twrp on our locked bootloader, so safestrap and flashfire are the only options. But safestrap doesn't work out the door with L, so you have to use flashfire or the safestrap workaround. Make sure you read, read, and read some more to get where you're trying to go. Good luck.