Somewhere along the line i messed up and deleted the whole os through twrp. I Don't know how it happened but it did. I found a forum that lead me to a sprint recovery which I needed so I flashed that not thinking anything of it. It flashed Android 4.4.4 and now my WiFi Doesn't work. Maybe i should have done more research but is there anyway to fix this? I am rooted but S-ON
Tkelley11 said:
Somewhere along the line i messed up and deleted the whole os through twrp. I Don't know how it happened but it did. I found a forum that lead me to a sprint recovery which I needed so I flashed that not thinking anything of it. It flashed Android 4.4.4 and now my WiFi Doesn't work. Maybe i should have done more research but is there anyway to fix this? I am rooted but S-ON
Click to expand...
Click to collapse
Definitely do more research before you blow away things on your phone, yes
Anyway, depending on which "Android 4.4.4" you flashed it probably requires a new firmware, which you can't flash because you're S-On. Flash an earlier ROM (or backup) that supports your firmware.
Where can I find the correct stock Sprint Rom for my phone?
Sent from my 831C using XDA Free mobile app
Tkelley11 said:
Where can I find the correct stock Sprint Rom for my phone?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Google "stock rooted ROM/backup for sprint HTC one m8" in your browser
Tkelley11 said:
Somewhere along the line i messed up and deleted the whole os through twrp. I Don't know how it happened but it did. I found a forum that lead me to a sprint recovery which I needed so I flashed that not thinking anything of it. It flashed Android 4.4.4 and now my WiFi Doesn't work. Maybe i should have done more research but is there anyway to fix this? I am rooted but S-ON
Click to expand...
Click to collapse
You could restore the backup you saved to your extSD.
Didn't I help you in another thread you started that said basically the same thing and I linked you to @Mr. Hofs' stock backup collection?
Just sayin....
Well if you have a backup on your external sdcard than yes restore it from there
jball said:
Well if you have a backup on your external sdcard than yes restore it from there
Click to expand...
Click to collapse
He doesn't. Hence the wink. He "didn't think to make one" if I recall correctly, but that could have been someone else.
xunholyx said:
He doesn't. Hence the wink. He "didn't think to make one" if I recall correctly, but that could have been someone else.
Click to expand...
Click to collapse
You must have went in and edited wile I was posting cause all I seen was "restore from your external sdcard" [emoji8]
jball said:
You must have went in and edited wile I was posting cause all I seen was "restore from your external sdcard" [emoji8]
Click to expand...
Click to collapse
Nope, I added the wink right away and had a chuckle to myself.
Like I said, he was told about the stock backups yesterday, and on another thread, he OPed the almost exact same thing. I told him there to go back to stock, I believe as well. He obviously doesn't want to take the time to do some reading and searching to help himself. I'm not willing to spoon feed him. It's time he just followed the advice that was given.
Related
How to extract stock Rom? The case is that I haven't done backup of my stock Rom branded by era provider.
Now some guy told me that he just bought desire z from era and his Rom is identical to RUU_Vision_HTC_WWE_1.72.405.2_R_Radio_12.28e.60.14 0f_26.04.02.17_M2_SF_release (available on this forum)
except radio code which is ending with fU instead f.
So if I would like to get Rom which is flashed on his device, to have exactly what was on mine on the beginning what and how it should be done?
Sent from my HTC Vision using XDA Premium App
Searching XDA found this: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#RUU_Flashing
I think it's just connect phone, run RUU*.exe
tan-ce said:
Searching XDA found this: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#RUU_Flashing
I think it's just connect phone, run RUU*.exe
Click to expand...
Click to collapse
Ok thanks it is for sure usefully guide but I'd like to know how to retrieve or backup stock Rom from the phone with original stock?
Sent from my HTC Vision using XDA Premium App
Ok, if I understand you right, you currently have a phone with stock ROM, and you want to take a backup of that phone, correct?
If that's the case, I think you'll still need to root the phone in order to install Clockwork recovery. Once you have Clockwork, then you can take a nandroid backup of your phone. So I don't think you can grab a backup of stock ROM before it was rooted.
tan-ce said:
Ok, if I understand you right, you currently have a phone with stock ROM, and you want to take a backup of that phone, correct?
If that's the case, I think you'll still need to root the phone in order to install Clockwork recovery. Once you have Clockwork, then you can take a nandroid backup of your phone. So I don't think you can grab a backup of stock ROM before it was rooted.
Click to expand...
Click to collapse
Yeah so this a problem. During rooting it is necessary to downgrade your soft to 1.34 what automatically force you to loose your stock Rom. :/
Sent from my HTC Vision using XDA Premium App
Oh right, now I remember. I think if you can't find the exact RUU, you're out of luck. What do you want that backup for anyway?
tan-ce said:
Oh right, now I remember. I think if you can't find the exact RUU, you're out of luck. What do you want that backup for anyway?
Click to expand...
Click to collapse
No no I wanted only to have a possibility to back to the stock Rom if my phone will have to be sent to service on warranty.
I know one guy from Poland who also bought a phone from the same telcom operator - era.
He gave me info that the stock Rom on his phone is:
12.28e.60.140fU_26.04.02.17_M2
While on the forum can be find the same but with one difference in radio code - only f instead fU
12.28e.60.140f_26.04.02.17_M2 and can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=879384
But what does it mean this difference mentioned above and if it is negligible or not?
Sent from my HTC Vision using XDA Premium App
Well, unless you've flashed a custom radio, another option could be to extract everything from that RUU you found in the forum and flashing everything except the radio.
Although if you want to send your phone for warranty you'll probably have to do a bit more work to get s-on again...
tan-ce said:
Well, unless you've flashed a custom radio, another option could be to extract everything from that RUU you found in the forum and flashing everything except the radio.
Although if you want to send your phone for warranty you'll probably have to do a bit more work to get s-on again...
Click to expand...
Click to collapse
I've flashed two ROMs first one was CM7-R2 and then I've decided to use Virtuous 1.0.1. I don't know if during that process also radio was flashed :/ Was it? I am new Android so I don't know some things yet.
Sent from my HTC Vision using XDA Premium App
Btonh ohyj uiibf hgv
meXdroid Ghost Chilli
Sebalos said:
I've flashed two ROMs first one was CM7-R2 and then I've decided to use Virtuous 1.0.1. I don't know if during that process also radio was flashed :/ Was it? I am new Android so I don't know some things yet.
Click to expand...
Click to collapse
I'm quite sure that flashing those ROMs do not change your radio. So if you need to send for warranty, I think you'll just need to flash the ROM part of the RUU (should be able to find a post somewhere which tells you how to extract just certain parts of the RUU) and then reflash partition 7 to get S-OFF. If you used gfree, it would have made a backup of that partition before it gave you S-OFF. Hopefully you still have it.
Actually, have you taken a look at this?
bought it 4/9/11 deleted calender by mistake been trying for 3 days put back in someone here taught me how to put it in but files wont work set permission at read write everything!!! maybe calender.apk wrong
pqc200 said:
bought it 4/9/11 deleted calender by mistake been trying for 3 days put back in someone here taught me how to put it in but files wont work set permission at read write everything!!! maybe calender.apk wrong
Click to expand...
Click to collapse
You could always just run a RUU and reroot.
If that is easier for you.
http://forum.xda-developers.com/showthread.php?t=884060
mattykinsx said:
You could always just run a RUU and reroot.
If that is easier for you.
http://forum.xda-developers.com/showthread.php?t=884060
Click to expand...
Click to collapse
Or just flash the rooted stock OTA.
http://forum.xda-developers.com/showthread.php?t=874251
matt2053 said:
Or just flash the rooted stock OTA.
http://forum.xda-developers.com/showthread.php?t=874251
Click to expand...
Click to collapse
I read his post as he bought the Evo rooted.
I believe in a fresh install.
mattykinsx said:
I read his post as he bought the Evo rooted.
I believe in a fresh install.
Click to expand...
Click to collapse
That's what I suggested. You also suggested the added step of unrooting and rooting again though I think that's completely unnecessary and would be a huge PITB just to get the calendar back. There's no need to throw unrooting into the mix. He should just flash the (rooted) stock ROM.
Sent from my PC36100 using XDA App
matt2053 said:
That's what I suggested. You also suggested the added step of unrooting and rooting again though I think that's completely unnecessary and would be a huge PITB just to get the calendar back. There's no need to throw unrooting into the mix. He should just flash the (rooted) stock ROM.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Eh it just brings everything to stock, updates the radio and so forth, just gets it all done.
That's why I suggested it.
mattykinsx said:
Eh it just brings everything to stock, updates the radio and so forth, just gets it all done.
That's why I suggested it.
Click to expand...
Click to collapse
Actually he didn't mention if he flashed a custom recovery or not so he might have to run RUU if he can't flash the stock ROM. I didn't think about that.
OP, did you flash either ClockworkMod or Among RA recovery?
Sent from my PC36100 using XDA App
pqc200 said:
bought it 4/9/11 deleted calender by mistake been trying for 3 days put back in someone here taught me how to put it in but files wont work set permission at read write everything!!! maybe calender.apk wrong
Click to expand...
Click to collapse
If you have the calendar.apk, is the option to install non-market apps checked under settings-applications-development?
mrufino1 said:
If you have the calendar.apk, is the option to install non-market apps checked under settings-applications-development?
Click to expand...
Click to collapse
You can't just install calendar.apk because its a system app.
You would have to push it to /system/app then run fix permissions.
Flashing the stock ROM through recovery would be easiest.
Sent from my PC36100 using XDA App
Assuming it's a sense rom, I would just download any sense rom, then push it via adb to the /system/app folder, chmod 0744 {filename.ext}. Done.
If it's AOSP, then same instructions, but grab an AOSP rom.
I would just reflash the rom you flashed originally. Wipe Dalvik/Cache and you should be good to go.
It says he's on stock ROM right in the thread title!
Sent from my PC36100 using XDA App
matt2053 said:
It says he's on stock ROM right in the thread title!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok, it's been a while since I rooted, but, when I did you had some form of a development rom and had to flash a different one right away. There were several "stock roms" to choose from.
It may be different now, so maybe I'm wrong. If so, get over it.
OP you have tons of options to correct your situation.. the thread police can surely help you out.
Batman58 said:
Ok, it's been a while since I rooted, but, when I did you had some form of a development rom and had to flash a different one right away. There were several "stock roms" to choose from.
It may be different now, so maybe I'm wrong. If so, get over it.
OP you have tons of options to correct your situation.. the thread police can surely help you out.
Click to expand...
Click to collapse
I was referring to the post above yours.
Sent from my PC36100 using XDA App
I have the same issue I installed a lock ring color and for some reason it kicked out the calender widget so I'm looking just for the calender widget if anyone has it. I truly dont want to have to reinstall this rom to get it back its just takes so long to restore my data.
danya247 said:
I have the same issue I installed a lock ring color and for some reason it kicked out the calender widget so I'm looking just for the calender widget if anyone has it. I truly dont want to have to reinstall this rom to get it back its just takes so long to restore my data.
Click to expand...
Click to collapse
My friend all you have to do is get the calendar widget apk from the rom you flashed and adb push it back over
Ok so i need to send my inc 2 in for a refurb. I am currently running AOKP build 37 with aeroevans v9ics kernel and an unlocked BL. How do i return to complete stock unrooted?
i've seached all over the forum and can't find anything. It was easy with my droid x2 because you could just run the SBF with RSD Lite.
I also have the new software version 6.1 if thats any help.
Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.
blazingwolf said:
Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.
Click to expand...
Click to collapse
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.
dets34 said:
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.
Click to expand...
Click to collapse
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.
blazingwolf said:
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.
Click to expand...
Click to collapse
hmm never thought about it like that. I guess ill give it a try and see how wise you truly are.
Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU
dets34 said:
Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU
Click to expand...
Click to collapse
Hmm. What did it say as it went through the process?
It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time
dets34 said:
It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time
Click to expand...
Click to collapse
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.
blazingwolf said:
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.
Click to expand...
Click to collapse
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.
dets34 said:
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.
Click to expand...
Click to collapse
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.
blazingwolf said:
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.
Click to expand...
Click to collapse
Thank heavens for my overly cautious brain
Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.
blazingwolf said:
Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.
Click to expand...
Click to collapse
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?
dets34 said:
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?
Click to expand...
Click to collapse
Did you clear dalvik cache?
blazingwolf said:
Did you clear dalvik cache?
Click to expand...
Click to collapse
cleared everything. i just tried flashing the andybonestock or whatever rom, and im getting the same thing. stuck at the droid eye.
nvm i take that back. the andybonestock rom flashed, just took a little while to load
dets34 said:
nvm i take that back. the andybonestock rom flashed, just took a little while to load
Click to expand...
Click to collapse
Cool. That one should work for you as well.
blazingwolf said:
Cool. That one should work for you as well.
Click to expand...
Click to collapse
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.
dets34 said:
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.
Click to expand...
Click to collapse
The app I listed above.
SuperUser can also just be deleted but the modified su will still be there.
Hello,
I bought a broken screen T989 from ebay. I needed the motherboard from the device. However, upon receiving device, i swapped motherboards no problem. However, i have an "Unknown" imei and baseband number.
I know there is a way to restore the IMEI from scratch on my galaxy S III (T999) but i am not sure if that method will work on the SII (Also quite afraid to as it most likely may brick it)
Does anyone know the manual method for restoring it?
Also, google lead to a bunch of promissing looking threads about the I9100 (International version) but from what i have read the T989 uses a different partition for the EFS stuff.
Thanks everyone!!
Do you know the imei number by any chance?
Don't type it btw just answer yes or no lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wolfygang said:
Do you know the imei number by any chance?
Don't type it btw just answer yes or no lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
yes i do know the IMEI number. Its on the sticker of the case.
THis is urgent...
elesbb said:
THis is urgent...
Click to expand...
Click to collapse
Another bump.. Seriously NOBODY has ANY clue?
elesbb said:
Another bump.. Seriously NOBODY has ANY clue?
Click to expand...
Click to collapse
Please don't do this...
elesbb said:
THis is urgent...
Click to expand...
Click to collapse
Seriously...
Sent from my SAMSUNG-SGH-T989 using xda premium
ArianaGrande said:
Please don't do this...
Seriously...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Lol I have too. I miss feeling like a n00b.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
flash the zip from my thread here:
http://forum.xda-developers.com/showthread.php?t=1611796
and flash a different radio that is supported by android version u are using
icenight89 said:
flash the zip from my thread here:
http://forum.xda-developers.com/showthread.php?t=1611796
and flash a different radio that is supported by android version u are using
Click to expand...
Click to collapse
No way. So I just flash the efsfix.zip and then a radio?! Sex. If this works I'll love you forever I also cannot use Odin cause the seller failed to mention the USB port doesn't work except for charging. -.- ugh fml
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Yeah this was a no go...
elesbb said:
Yeah this was a no go...
Click to expand...
Click to collapse
Did you ever fix it? If so do share please.
the-Mike_D said:
Did you ever fix it? If so do share please.
Click to expand...
Click to collapse
Nope i never did. Everything i ever found lead to using a Jtag box. Which costs about 100 bucks xD And i don't know anyone who has one.
elesbb said:
Nope i never did. Everything i ever found lead to using a Jtag box. Which costs about 100 bucks xD And i don't know anyone who has one.
Click to expand...
Click to collapse
I got my T-989 fixed about 30 minutes after posting my question to you. I'm just not sure which one of the steps I took was the actual bullet. But I'll post what I did here in the same order.
1. Downloaded and put onto the phone's sd card these files for future flashing back to back. They are. the "efsfix.zip" file from here http://forum.xda-developers.com/showthread.php?t=1611796. Also, this rom which comes with it's own modem. http://forum.xda-developers.com/showthread.php?t=1818305. That's it. Now maybe the trick is in the steps though?
So what I did was boot into clockworkmod recovery "latest one for this phone." Used the factory reset option. Next went to mount the phone to usb option so I could access the internal memory card's files and deleted them all. I had a suspicion that maybe there's something corrupt in the data files or whatever. Really this might be silly but whatever, I did it. I still had my 2 files from before on the external sd card so no worries. Next I unmounted and disconnected from the pc. Then cleared cache again, then cleared dalvic again (I do these two steps a lot when flashing stuff back to back). Then flashed the efsfix.zip. Then clear cach, dalvic again. Then flashed the rom shown above which installed everything in one swoop like kernel, modem, system files, ect. After that finished I cleared cache, dalvic one last time. Then let it reboot.
So, it boots normally but upon the first "What is your name" screen it loads with a funky keyboard. It's a lol factor. Apparently a goof of the rom that happens sometimes. Just skip it all or figure out how to choose the T9 by using the menu key. Anyway, after changing my keyboard from inside the working settings menu to the samsung one I realized that I was so distracted by the keyboard issue that I I was just now noticing that I had a working baseband and it was connected to the network (T-Mobile) again as usual. Problem solved. Now as a last precautionary step I reboot into recovery (clockwordmod) again and use the option to backup efs folder to external sd card just for good measure. Then finally make nandroid backup of the whole working rom as well. You could probably flash any rom you want after this though. Anyway, something in there made it work so I hope it might work for you too.
I had a backup of stock before root but when i tried to back up to it today it gave me a md5 mismatch so i couldnt back up to it. From what I seen in beaups thread that I need to be on a stock rom and stock kernal for his s-off method to work. Is there a stock rom that I could flash to use the s-off method?
I'd like this answered as well. I think andy's stock rom near the bottom of the page works, but I haven't had a confirmation yet. Also wondering if odex versus deodexed versions matter.
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Aggies1288 said:
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Click to expand...
Click to collapse
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
cstrife999 said:
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
Click to expand...
Click to collapse
Just tried v1.0a..... No dice.
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
cstrife999 said:
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
Click to expand...
Click to collapse
Im downloading 1.1 now. Ill get back with y'all on how it went.
Aggies1288 said:
Im downloading 1.1 now. Ill get back with y'all on how it went.
Click to expand...
Click to collapse
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
mcampos7 said:
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
Click to expand...
Click to collapse
This is what I've been on since launch day. Curious if this will work.
m4rk0358 said:
This is what I've been on since launch day. Curious if this will work.
Click to expand...
Click to collapse
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
mcampos7 said:
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
Click to expand...
Click to collapse
Yea i got made fun of when using that lol...
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
I HAVE NEVER USED TWRP FOR BACKUPS. IT IS A MERE SUGGESTION THAT THIS METHOD WILL WORK WITH SIMILAR RESULTS. I HAVE NEVER BROWSED A BACKUP FOR TWRP. ANY ATTEMPT YOU MAKE USING A TWRP BACKUP IS OF YOUR OWN COGNIZANCE. YOU HAVE BEEN WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
IIRC: If you have an md5 mismatch while trying to restore in a recovery, try this process:
IF YOU HAVE A BACKUP I HIGHLY SUGGEST STORING THE BACKUP FILE ON YOUR DESKTOP JUST IN CASE!!!!
Boot into whatever ROM you're on ATM.
Browse to your ClockworkMod (or TWRP backup must have an accessible folder for it's backups) using a Root file explorer, which I happen to use "Root Explorer" and open the backup file you just made.
Inside of that will be a nandroid.md5.
Delete that file and reboot into recovery, and try restoring again.
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
This method did work for me several times on several backups, but root and S-Off being so new, I cannot attest that it works for the One. YOU ARE WARNED**!!
cstrife999 said:
Yea i got made fun of when using that lol...
Click to expand...
Click to collapse
For using what? Linux? NOS?
mcampos7 said:
For using what? Linux? NOS?
Click to expand...
Click to collapse
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
cstrife999 said:
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
Click to expand...
Click to collapse
Looks like we may have to flash the boot.img that they are talking about in the s-off thread anybody have a guide for doing that?
I take it nobody tried deleting the nandroid.md5?
rmaccamr said:
I take it nobody tried deleting the nandroid.md5?
Click to expand...
Click to collapse
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Aggies1288 said:
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Click to expand...
Click to collapse
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
I tried the odex stock rom, but it won't flash... Anybody have this issue?
santod040 said:
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Ok i found it it was under /data/media/clockworkmod/backup but i dont see any files inside of that that are a md5 file im going to look in the data.ext4.tar file and the system.ext4.tar.a. Does any of those ring a bell? i see the boot.img, data.ext4.tar.a, recovery.img, system.ext4.tar.a, and system.ext4.tar.b. Thats all the files inside the backup i made before i rooted.