Related
Ok before everyone starts thinking I repeating questions that have already been repeated. You must know what I'm dealing with.
I am not that great with android yet, but I know enough.
I have a vibrant that I rooted with Super One Click, and then found out about the clockwork issues with 3e. So then proceeded to do the 3e recovery fix that i downloaded from xda.
It worked for every one that i have seen a thread about it for, but for me, when I go to flash clockwork, then reboot into recovery. I reinstall packages, and it briefly says that it is "switching to ClockworkMod recovery", reboots but goes right back into 3e, doesn't give any error messages or anything. weird right
Anyone had this problem? can't find anyone that has. Thanks
Running vibrant 2.2 with root, and attempting to use clockwork recovery 2.5.1.2
Simplest answer is to odin to jfd, reboot into recovery and reinstall packages. This should put you in cwm recovery. From there flash a custom rom and enjoy...i recommend bi-winning. Its mostly stockish and is very smooth.
Sent from my SGH-T959 using XDA Premium App
ajster1989 said:
Ok before everyone starts thinking I repeating questions that have already been repeated. You must know what I'm dealing with.
I am not that great with android yet, but I know enough.
I have a vibrant that I rooted with Super One Click, and then found out about the clockwork issues with 3e. So then proceeded to do the 3e recovery fix that i downloaded from xda.
It worked for every one that i have seen a thread about it for, but for me, when I go to flash clockwork, then reboot into recovery. I reinstall packages, and it briefly says that it is "switching to ClockworkMod recovery", reboots but goes right back into 3e, doesn't give any error messages or anything. weird right
Anyone had this problem? can't find anyone that has. Thanks
Running vibrant 2.2 with root, and attempting to use clockwork recovery 2.5.1.2
Click to expand...
Click to collapse
As said go back to stock and redo it. The toolbox works wonders
http://forum.xda-developers.com/showthread.php?t=954509
toolbox
I will try the tool box, let's see what happens...
Thanks
I had that problem, all I did was put the update.zip in the internal sd and the external sd too. After that it should work
Sent from my GT-I9000 using XDA Premium App
Toolbox worked
So yeah the tool box worked, whoever came up with that really did a good job, thanks
Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.
Hello! I have searched the forums already, but to no avail. I have a bricked G Tablet UPC300-2.2 and I am trying to find the stock files and instructions on how I can get this tablet up and running again. Can someone point me in the right direction? Thanks!
Sent from my seksi SGS3 using Tapatalk 2
Anyone?
Sent from my seksi SGS3 using Tapatalk 2
haoleflip said:
Anyone?
Sent from my seksi SGS3 using Tapatalk 2
Click to expand...
Click to collapse
Try this site and learn how to nvflash, then download the bootloader 1.2 stock rom and reset your tablet. Good luck.
http://viewsonic-gtablet-for-dummies.webs.com
Also looking for help. I got the nvflash to work but after the reboot it hangs on the "n" after TnT. When I reboot with "vol +" I see the kernel try to load and then it goes to the black Android screen and !. Any ideas were to look?
iskshoj appointed
BacDoc said:
Also looking for help. I got the nvflash to work but after the reboot it hangs on the "n" after TnT. When I reboot with "vol +" I see the kernel try to load and then it goes to the black Android screen and !. Any ideas were to look?
Click to expand...
Click to collapse
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
PHP:
BacDoc said:
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
Click to expand...
Click to collapse
You might want to try using just the stock 1.1 nvflash with stock recovery first before jumping straight to 1.2 with touch recovery. Granted NVflash was designed to write the stock IMG to you device but best to restore to a complete stock 1.1 go through setup and except the OTA update. This should put you through a better course and update both stock firmware and bootloader. Then as long as everything sticks you can update the recovery IMG using the NVflash package available for what ever ROM you decide to update to. Good luck.
BacDoc said:
Well I got Team DRH's CWMR Touch to boot now and I got my stock gTab back for about 10 mins. After wiping everything clear I was able to return to stock but after maybe the second reload I got nothing. Seems I lose the the stock ROM and have to start the NVFlash process again to get it to load. Any ideas on how I can get a stable stock ROM?
Click to expand...
Click to collapse
I would try nvflashing again and make sure your repartition and do all the wipe caches n factory reset before and after you nvflash and hopfully that will clear things up. Might go ahead and try the Smooth Bean Rom. U wont regret it. Blazzing speed.
Thanks guys, I did get it up and running but its not stable. When I update to the firmware it crashes and won't load. After a few restarts sometimes it works some times I have to NVF to restore it again. Should I try the NVF 1.1?
At this point I have/had CWM with no rooted ROM, only stock trim.
---------- Post added at 10:26 PM ---------- Previous post was at 09:43 PM ----------
1.1 seems to allow the OTA update. Getting some forced close apps now.
Do I need to wipe everything now?
Well I found what appears to be a stable stock setup now.
I can't get into CWM now and Rom Manager won't install, neither will Google Play.
BacDoc said:
Well I found what appears to be a stable stock setup now.
I can't get into CWM now and Rom Manager won't install, neither will Google Play.
Click to expand...
Click to collapse
First off using ROM manager for you Gtab is just asking for trouble. Don't use it.
As far as Google play how are you trying to install it and what on?
Sent from The Darkside via me....
G tablet stuck "booting recovery kernel image"
I tried to restore to TnT using the zip file up date. Rebooted and the only think I get is the View Sonic logo and in the upper left hand corner "booting recovery kernel image" Also also can not access through the USB from my PC. I tried putting the recovery files on a micro sd card but the tablet does not recognize it. Is there any way I can get access from my pc? Any suggestions are greatly appreciated.
Mark
ultracorp said:
I tried to restore to TnT using the zip file up date. Rebooted and the only think I get is the View Sonic logo and in the upper left hand corner "booting recovery kernel image" Also also can not access through the USB from my PC. I tried putting the recovery files on a micro sd card but the tablet does not recognize it. Is there any way I can get access from my pc? Any suggestions are greatly appreciated.
Mark
Click to expand...
Click to collapse
At this point the only thing that would advise to do is NVflash to stock with the CWM recovery image pre-installed so that everything would be correct. When NVflash is complete boot into recovery and perform a wipe data factory reset and reboot into system.
Sent from The Darkside via me....
Hello all, I want to install Clockworkmod on my Samsung Vibrant T959 so I can install a custom ICS ROM. I ran into some problems along the way. I can not seem to install CWM correctly. I had the phone under Froyo 2.2, kernel version 2.6.32.9, and build number froyo.uvkb5. After flashing the recovery by ROM Manager, I would still be stuck at the stock recovery. I have the correct files to download:update.zip. After clicking on "reinstall packages", the recovery said "replacing stock recovery with Clockworkmod recovery". The problem is that after that message, the phone restarts into the stock recovery. I tried it 4 times in a row, but I'm still stuck at the stock recovery. The system keeps saying that it will replace the stock recovery with the CWM recovery, but that did not happen with me. I would keep getting the same message when I click on "re install package". What am I missing that does not allow me to do this? Thanks all.
Are you on 2.1 eclair or 2.2 froyo?
I'm pretty sure you need to be on 2.1 but don't quote me.
Also, I believe there is an issue with the newer versions of ROM manager, recovery mismatch. (Again don't quote)
I haven't had to mess with that stuff in a long time. Either way I'm posting a link that will help you along. If you have any more questions just shoot.
http://forum.xda-developers.com/showthread.php?p=9375927
Paranoid, sitting in a deep sweat...
Thanks for the reply. Like I said in my last post, I am running at Froyo 2.2. I already bricked my phone for failing to downgrade to 2.1. I already rooted my phone, my problem is that I could not install CWM correctly by the stock rom. After the message states that it is replacing the stock rom, my phone goes back to stock with no changes.
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Your positive you dont have a 4g?
Sugartibbs said:
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Click to expand...
Click to collapse
You do not understand, I am having the problem that CWM could not install properly. When I chose "install packages" the steps went by and ended with "Replacing stock recovery with CWM recovery". Usually, that would jump straight into CWM recovery after it's installed. That did not happen to me, After installation, my phone restarted and booted back into stock recovery. I tried installing again but I always go back to stock recovery and not Clockworkmod recovery as I planned.
Ive never seen that error message, I know its frustrating, but the t959v 4g comes loaded with Froyo 2.2,the a 2.1 eclair odin will brick it.Just trying to help.
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
Paranoid, sitting in a deep sweat...
---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------
In the link I sent is the AIO toolbox download. There is a guide how to use it in this link. The DL links are dead in this one so get from previous.
Paranoid, sitting in a deep sweat...
IIRC the update.zip method does not work in Stock 2.2 because of the 2e and 3e recovery mismatch. If you to go to 2.1 Eclair, then you can use the update.zip method and then flash your ROM of choice after that. If you decide to stay on 2.2, you'll have to get the 3e method. It is in the Development section, so you'll just have to search 3e and it should come right up.
All this is provided you have a T959 (3g) and not a T959v (4g). Sorry but lately there have been many 4g users flashing our ROMs and then freaking out.
You can also find a bunch of files in my Repo thread stickied in the Dev section.
samsgun357 said:
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Maybe you'll get it now.
Good luck.
@Woody, thanks buddy.
I linked your repo thread in my previous post.
Edit: well the link isn't in my posts, must not have sent??? But here it is
http://forum.xda-developers.com/showthread.php?p=31279153
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
nfkod said:
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
^^ this is not true.
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
naturallight said:
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I have no idea what you are talking about?????
Paranoid, sitting in a deep sweat...
If you have the proper xda version of update zip on your sd...,, theres no need for a kernel flash.
I have the same exact issue as the original poster. 2.2 froyo and all. I even replaced my stock 3e recovery with the modded one, but I get the same issue. Says its flashing CW recovery but it always reboots and comes back with the stock recovery. What exactly are we doing wrong?
Follow steps in this guide, update.zip b is probably best but you need to Odin back to stock first.
http://forum.xda-developers.com/showthread.php?p=9375927
Alright so I managed to get CWM on my 2.2 Stock Vibrant and even got it permanently. What I did was download SGS Kernel Flasher and install it. Then I went the Samsung Vibrant Kernel Bible and found the stock kernel with Voodoo lagfix included that matched my phone (because the kernel has CWM built in) downloaded it, and placed it on the root of my card. Launched the app, backed up my current kernel and then flashed the new one. Everything went smooth and then my phone rebooted and was stuck on the Vibrant screen for 20 minutes. I was pretty sure I messed my phone up. Also it was talking to me which I didn't realize at first, because I was expecting my phone to be talking to me! Finally made out what it said and it said something along the lines of not enough space on the partition, closing... It was hard to understand because it was in a robotic voice. It eventually rebooted and loaded up like normal. Checked the about phone but saw nothing different. So I decided to reboot to recovery just to check and sure enough, CWM 2.5.1.3 comes up, and comes up every time Finally, now to figure out what to do to get on a jellybean ROM
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
samsgun357 said:
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
Click to expand...
Click to collapse
QFT. Just yesterday I ran into the same problem as reported by the OP and a few others. I HAD to downgrade to 2.1 via JFD Odin. Then flash the update.zip. I then just downloaded ROM Manager to get CWM working. However, I did see in some instructions that sometimes even though you know you have CWM installed, it will still default to stock recover. I simply applied the update.zip again and it eventually fixed itself. Not sure what that was about, but I did see it in some instructions, and I experienced it as well.
nfkod said:
the first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
great help dude.i fixed finaly."""""thanks"""""
HELP!!!!
I'm a semi-amateur at rooting, and I'm worried I bricked my wife's Droid Razr MAXX. Here's what happened:
A year ago, I rooted her Razr and installed safestrap, which came with its TWRP interface. It had been running slow, so yesterday I said I'd put her on a new ROM. I installed CM 10.1.3 and everything seemed to go smoothly. After I'd finished the install of the ROM, using safestrap and TWRP, I reinstalled all her apps and everything.
Then I reinstalled SuperSU, VooDoo OTA Rootkeeper, and Safestrap v2.11. I ran safestrap and noticed it said it didn't have custom recovery installed, even though I knew it did. I don't know why, but I hit the button to install custom recovery.
Well, her phone was being screwy so she reset it at work. It then began to bootloop, and she turned it off (power + vol up + vol down). I turned it on, the safestrap splash screen showed, and I hit "menu" to boot into recovery.
Instead of TWRP, I am getting the green and black stock recovery screen. Uh oh, right? So I don't know what to do now. I wiped cache and dalvik to see if it'd reboot, but still, it bootloops.
Do I hit "Disable Safestrap (if stuck in recovery)"? I'm afraid to do anything at this point, out of fear of bricking her device. Any help would be greatly appreciated!!!
Download RSD Lite 5.7 and download the 4.1.2 firmware here
http://sbf.droid-developers.org/cdma_spyder/list.php make sure you have a good charge on the phone, (it won't charge in fastboot) then open the firmware in RSDlite extract, put your phone in fastboot mode (Vol+ Vol- power select fastboot) plug the phone into your computer using your micro USB that came with the phone. Wait for files to extract then flash. Hope this helps. Any further questions you can send me an IM at [email protected]
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------
This will bring you back to stock but you can easily re root.
Sent from my DROID RAZR HD using xda app-developers app
eolsgaard said:
HELP!!!!
I'm a semi-amateur at rooting, and I'm worried I bricked my wife's Droid Razr MAXX. Here's what happened:
A year ago, I rooted her Razr and installed safestrap, which came with its TWRP interface. It had been running slow, so yesterday I said I'd put her on a new ROM. I installed CM 10.1.3 and everything seemed to go smoothly. After I'd finished the install of the ROM, using safestrap and TWRP, I reinstalled all her apps and everything.
Then I reinstalled SuperSU, VooDoo OTA Rootkeeper, and Safestrap v2.11. I ran safestrap and noticed it said it didn't have custom recovery installed, even though I knew it did. I don't know why, but I hit the button to install custom recovery.
Well, her phone was being screwy so she reset it at work. It then began to bootloop, and she turned it off (power + vol up + vol down). I turned it on, the safestrap splash screen showed, and I hit "menu" to boot into recovery.
Instead of TWRP, I am getting the green and black stock recovery screen. Uh oh, right? So I don't know what to do now. I wiped cache and dalvik to see if it'd reboot, but still, it bootloops.
Do I hit "Disable Safestrap (if stuck in recovery)"? I'm afraid to do anything at this point, out of fear of bricking her device. Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Did you try to install SS from within CM? SS is intended to be installed and managed on stock. Did you install CM on a new slot in recovery?
Also, the latest SS version is 3.60.
For future reference, your actions should've been these:
1. Uninstall custom recovery using whatever SS you have installed on stock.
2. Uninstall SS and install newest SS version.
3. Install custom recovery using the newly installed SS.
4. Reboot into TWRP, create NEW slot and flash ROM.
Right now, I'd recommend what nickmoogo said above - start fresh, and do everything in order this time around, good luck!
CruxHumanus said:
Did you try to install SS from within CM? SS is intended to be installed and managed on stock. Did you install CM on a new slot in recovery?
Also, the latest SS version is 3.60.
For future reference, your actions should've been these:
1. Uninstall custom recovery using whatever SS you have installed on stock.
2. Uninstall SS and install newest SS version.
3. Install custom recovery using the newly installed SS.
4. Reboot into TWRP, create NEW slot and flash ROM.
Right now, I'd recommend what nickmoogo said above - start fresh, and do everything in order this time around, good luck!
Click to expand...
Click to collapse
That's exactly what I did. I have no idea why I did it either. Since I was on v2.11, clearly it's been a while since I touched her phone. So there's no way other than starting over from stock firmware, huh? If I could just get back to the TWRP interface I'd be much more comfortable, but I know SS's version of TWRP is unique. If starting fresh is the safest bet, that's what I'll do. Thanks guys!
eolsgaard said:
That's exactly what I did. I have no idea why I did it either. Since I was on v2.11, clearly it's been a while since I touched her phone. So there's no way other than starting over from stock firmware, huh? If I could just get back to the TWRP interface I'd be much more comfortable, but I know SS's version of TWRP is unique. If starting fresh is the safest bet, that's what I'll do. Thanks guys!
Click to expand...
Click to collapse
Someone more knowledgeable than myself could maybe advise more in this case. Start fresh is what *I* would've done.
Flashing stock is not that hard of a procedure, and after installing some roms and finding the one that works the best for you, you won't be seeing much of stock anyways, I know I don't.
dead link
nickmoogo said:
Download RSD Lite 5.7 and download the 4.1.2 firmware here
http://sbf.droid-developers.org/cdma_spyder/list.php make sure you have a good charge on the phone, (it won't charge in fastboot) then open the firmware in RSDlite extract, put your phone in fastboot mode (Vol+ Vol- power select fastboot) plug the phone into your computer using your micro USB that came with the phone. Wait for files to extract then flash. Hope this helps. Any further questions you can send me an IM at [email protected]
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------
This will bring you back to stock but you can easily re root.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
i know that post is 2years old but am in the same mess here. can i get a working link
SwayMontana said:
i know that post is 2years old but am in the same mess here. can i get a working link
Click to expand...
Click to collapse
Links in the index, but you need to use correct version
Bootloader version must match, or at least it cannot be downgraded.
http://forum.xda-developers.com/showthread.php?t=3023837
[INDEX] Motorola Droid Razr Development (2015)
Sent from my XT912 using Tapatalk