Alright, here's the problem,when the official jb 4.1.2 update came out a few days ago I decided to re-root and try a custom rom (tried on ICS but never was successful, also never bricked). I rooted fine and updated to safestrap 3.11, found a cm 10.1 rom online, went through all the steps but never wiped the stock system so every time I tried to boot it would try to dual boot and not work. I finally realized that i was wiping the rom system and not the stock which was why it would never work. So, wiped both caches, factory reset, and system wiped as per instructed and after that I installed the cm 10.1 in rom slot 1. Rom booted great worked fairly well but was a bit buggy for the first day, installed gapps no problem. After messing with it for a day I decided to switch back to stock system because i had all my contacts on backup assistant which wasnt available on the cm rom. when i tried to restore stock, I realize that somehow my backup got erased or something because all it is is an empty folder and took no time at all to restore, also wont boot. Any suggestions?
Phone specs (idk if it matters): XT912 CDMA Droid RAZR 4.1.2 (or was anyway)
PS. sorry for the super long post, i was kinda venting
http://www.droidrzr.com/index.php/topic/12777-droid-razr-utility-xt912-jellybean-windows-mac-linux-all-in-one/page__pid__227369#entry227369You can try to use this utility to take you back to stock JB:
Wouldn't that just root me and not take me back to OTA JB? I used the same program to re-root after the update from ICS to JB a few days ago.
Matt's Utility also has a "flash back to stock" option.
Alright, I got my phone back on track without needing a factory cable which was the route everything was going until I found a post about a work around by outfieldslayer on droid forums, anyone else who has this problem, just search "HELP battery died during flash!". Thanks to shobon and Gus194 for pointing me in the right direction and special thanks to mattlgroff for his work on the Razr utility!
I want to make sure I have the proper partitioning and such for the newer ROMs since I had not done the OTA, I just flashed the JB rom when it first came out.
So I just spent the last hour using LGNPST a few times.
Here is what happened. This was my first time using LGNPST.
Putting the phone in download mode was simple. I selected the .dll and then the 20j.bin
It got to 67% and the phone restarted. Then it gave the message at 85%.
I look at the phone and nothing seems to have changes, my wallpaper is the same and it looks like everything is there. I figured this would clear everything and I would be starting fresh.
So I tried it a couple more times with the same result. I even restated my PC and made sure nothing else was running.
I thought I might as well go back to 10o then. I selected it, again at 67% the phone restarts, but now it's got the old splash screen and hangs at the end of it. I let it sit and sit, restart it a few times all the same, it hangs after the splash.
So I do it one more time back to the 20j. 67% and it restarts. Now it boots there is a screen that said updating apps. Now it seems I am back to the stock JB I had before w/ my custom wallpaper and apps all there.
How do I check and see if it worked and I have the proper partitioning to try out the 4.2.2 ROMS?
Well looks like it must have worked.
All the AT&T apps I had frozen with TiBu are back, and when i open TiBu it can not find root.
I still thought that using LGNPST would wipe it clean. Guess I was mistaken.
Re=rooted w/ the new universal root and running FreeGee now.
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive:
Hey there.
To preface, I'm not new to flashing, just new to Samsung and Odin. (former CrackFlasher from the original D1 and Bionic/Razr days)
I got my S4 a couple months ago, rooted it and installed TWRP immediately and it had been running great ever since. I'm still on MDK and have not taken the ME7 update.
Got the bug again and decided to give Hyperdrive RL7 a shot. Downloaded it, rebooted into TWRP, flashed it, rebooted and let it sit for a few hours last night.
Opened it up this morning, everything worked GREAT! I know how these things work - new ROM, coming from stock, so I started from a clean slate and didn't use my TiBu backup to restore, I literally went and redownloaded every single app I use direct from Google Play Store.
I have to say the ROM was perfect - fast, smooth and awesome functionality and even some customization that gives previous Razr AOKP a run!
That's where the fun ends though - I rebooted the phone and ended up on the Samsung Unlocked with an unlocked padlock, and it wouldn't budge.
So, no problem, boot into TWRP, wipe and install Hyperdrive again.
NOPE. So I read that some people were having problems with TWRP, so I decided to give the older 2.5 version a try - Odin'd it to the phone and FAIL.
So someone else had mentioned they had luck with OUDHS. Odin'd it to the phone, but it wouldn't take it, so I found a download for OUDHS that's flashable from within "recovery" and flashed it from within TWRP, fully believing that's what it was meant for. THAT was a horrible idea that resulted in a boot that shows yellow text that states that there is software that isn't Verizon verified and to take my phone into the local Verizon store.
I had a feeling about flashing a new recovery from within a recovery, but I also thought it was pretty straightforward to flash back to stock... that's not been the case so far - the VRUAMDK_No Wipe file doesn't want to do anything because it's a .tar inside a .zip, opening the .zip in WinRAR, 7Zip and even WinZip doesn't open anything... so I can't even flash to stock.
Now I have NO recovery (no TWRP), and everything I've tried to push to the phone via Odin fails - with the exception of \SCH-I545_MD2_423399_Kernel.tar.tar which is what was used to root the phone to being with, and that only gets me back to the Samsung Custom unlocked padlock screen.
PLEASE HELP!
(thanks in advance for all input)
***EDIT:
I redownloaded the VRUAMDK_No flash 2 more times and got one that opened with WinRAR (still wouldn't open with 7z or WinZip, and after pushing it with Odin 4 times, the last time it finally went through.
I know a bad download was part of the first problem with not being able to open the original zip file to extract the md5 from within, but there was NO difference whatsoever in the 4 times I kept poking it with Odin when it finally took.
I successfully booted to stock, then rooted, then flashed TWRP 2.5, then installed Hyperdrive RLS8 successfully.
For anyone that's reading this that may have the same or similar problem, first try to download the ROM again and again (and again if necessary) - until you can open it with 7z or WinRAR, you don't have a valid, good download of it.
Second, keep poking it with Odin. It was my 4th try when it finally worked. --literally no changes in between, nothing changed at all, it just worked out of random on the 4th try.
/thread
Hope that helps someone. Glad I wasn't in more of a hurry!
Psychlone said:
Hey there.
To preface, I'm not new to flashing, just new to Samsung and Odin. (former CrackFlasher from the original D1 and Bionic/Razr days)
I got my S4 a couple months ago, rooted it and installed TWRP immediately and it had been running great ever since. I'm still on MDK and have not taken the ME7 update.
Got the bug again and decided to give Hyperdrive RL7 a shot. Downloaded it, rebooted into TWRP, flashed it, rebooted and let it sit for a few hours last night.
Opened it up this morning, everything worked GREAT! I know how these things work - new ROM, coming from stock, so I started from a clean slate and didn't use my TiBu backup to restore, I literally went and redownloaded every single app I use direct from Google Play Store.
I have to say the ROM was perfect - fast, smooth and awesome functionality and even some customization that gives previous Razr AOKP a run!
That's where the fun ends though - I rebooted the phone and ended up on the Samsung Unlocked with an unlocked padlock, and it wouldn't budge.
So, no problem, boot into TWRP, wipe and install Hyperdrive again.
NOPE. So I read that some people were having problems with TWRP, so I decided to give the older 2.5 version a try - Odin'd it to the phone and FAIL.
So someone else had mentioned they had luck with OUDHS. Odin'd it to the phone, but it wouldn't take it, so I found a download for OUDHS that's flashable from within "recovery" and flashed it from within TWRP, fully believing that's what it was meant for. THAT was a horrible idea that resulted in a boot that shows yellow text that states that there is software that isn't Verizon verified and to take my phone into the local Verizon store.
I had a feeling about flashing a new recovery from within a recovery, but I also thought it was pretty straightforward to flash back to stock... that's not been the case so far - the VRUAMDK_No Wipe file doesn't want to do anything because it's a .tar inside a .zip, opening the .zip in WinRAR, 7Zip and even WinZip doesn't open anything... so I can't even flash to stock.
Now I have NO recovery (no TWRP), and everything I've tried to push to the phone via Odin fails - with the exception of \SCH-I545_MD2_423399_Kernel.tar.tar which is what was used to root the phone to being with, and that only gets me back to the Samsung Custom unlocked padlock screen.
PLEASE HELP!
(thanks in advance for all input)
***EDIT:
I redownloaded the VRUAMDK_No flash 2 more times and got one that opened with WinRAR (still wouldn't open with 7z or WinZip, and after pushing it with Odin 4 times, the last time it finally went through.
I know a bad download was part of the first problem with not being able to open the original zip file to extract the md5 from within, but there was NO difference whatsoever in the 4 times I kept poking it with Odin when it finally took.
I successfully booted to stock, then rooted, then flashed TWRP 2.5, then installed Hyperdrive RLS8 successfully.
For anyone that's reading this that may have the same or similar problem, first try to download the ROM again and again (and again if necessary) - until you can open it with 7z or WinRAR, you don't have a valid, good download of it.
Second, keep poking it with Odin. It was my 4th try when it finally worked. --literally no changes in between, nothing changed at all, it just worked out of random on the 4th try.
/thread
Hope that helps someone. Glad I wasn't in more of a hurry!
Click to expand...
Click to collapse
Hyperdrive for me was fast and good and all, but i found it to be a tad unstable, just like you experienced. Beans and Bonestock are very stable tho.