I am pretty sure I know the answer to this, but I am just asking to be sure. I was looking at installing the "Tiamat Xoom Rom 2.2.1 - Moray", and I noticed that it said if I was not upgrading from Hammerhead, I needed to do a factory reset prior to flashing the ROM. I am not coming from Hammerhead, so I looked up the instructions on it, and it say "Factory Reset". So it looks like I am going to have to do a factory reset either way. True?
Can I ask why the need for the factory reset? I am sure there is a simple answer I am just not seeing, but it the ROM is going to overwrite my existing setup anyway, why the need for the Reset?
Krpto1973 said:
I am pretty sure I know the answer to this, but I am just asking to be sure. I was looking at installing the "Tiamat Xoom Rom 2.2.1 - Moray", and I noticed that it said if I was not upgrading from Hammerhead, I needed to do a factory reset prior to flashing the ROM. I am not coming from Hammerhead, so I looked up the instructions on it, and it say "Factory Reset". So it looks like I am going to have to do a factory reset either way. True?
Can I ask why the need for the factory reset? I am sure there is a simple answer I am just not seeing, but it the ROM is going to overwrite my existing setup anyway, why the need for the Reset?
Click to expand...
Click to collapse
If you have any changes to critical files (different from pure stock or the related Hammerhead rom), the Moray rom won't boot properly. It's worthwhile to just do the wipe data/factory reset than to try not to do it and end up looping.
Guess I didn't finish reading the instructions. It says that due to some bug fixes, a factory rest is required. Answers that question.
Opps, didn't see your post okantomi, but you said the same thing.
Next, it says powered by the Tiamat 2.1.0 Stock GPU Kernel. If I have the gpuOC already installed, to I need to switxh that first, or does that also happen with the ROM flash?
Krpto1973 said:
Guess I didn't finish reading the instructions. It says that due to some bug fixes, a factory rest is required. Answers that question.
Opps, didn't see your post okantomi, but you said the same thing.
Next, it says powered by the Tiamat 2.1.0 Stock GPU Kernel. If I have the gpuOC already installed, to I need to switxh that first, or does that also happen with the ROM flash?
Click to expand...
Click to collapse
I just flashed the oc gpu kernel over the Moray 2.2.1 rom update. Seems to work fine.
So... I went ahead and switched to the Stock GPU Kernel, have performed my Titanium and Nandroid Backups, and am ready to Wipe and Flash the ROM.
I am going to do the wipe in CWM, can I then install the ROM immediatly after from within CWM with the Install from Zip option?
Thanks
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
Too late. I got too excited and the ROM is unpacking now. Hope it works!
---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------
HAHAHAHA, it worked. It Rebooted and it is now restoring my data!!!!
Eyes Wide Open!!!!
---------- Post added at 10:17 PM ---------- Previous post was at 10:03 PM ----------
So everything came up perfect. I love it, but I do have a question that has nothing to do with the ROM, if anyone doesn't mind.
Since I had to factory rest it before applying the ROM, it is attempting to download all my apps from Google. If I go into the market they all show they are waiting to download, but none has started yet. I have always noticed this on my Xoom, that unlike my X which starts downloads right away, the Xoom takes weird random amounts of time to start the downloads, even if its just one app.
Any idea why?
Krpto1973 said:
So... I went ahead and switched to the Stock GPU Kernel, have performed my Titanium and Nandroid Backups, and am ready to Wipe and Flash the ROM.
I am going to do the wipe in CWM, can I then install the ROM immediatly after from within CWM with the Install from Zip option?
Thanks
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
Too late. I got too excited and the ROM is unpacking now. Hope it works!
---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------
HAHAHAHA, it worked. It Rebooted and it is now restoring my data!!!!
Eyes Wide Open!!!!
---------- Post added at 10:17 PM ---------- Previous post was at 10:03 PM ----------
So everything came up perfect. I love it, but I do have a question that has nothing to do with the ROM, if anyone doesn't mind.
Since I had to factory rest it before applying the ROM, it is attempting to download all my apps from Google. If I go into the market they all show they are waiting to download, but none has started yet. I have always noticed this on my Xoom, that unlike my X which starts downloads right away, the Xoom takes weird random amounts of time to start the downloads, even if its just one app.
Any idea why?
Click to expand...
Click to collapse
Here's a tip...since you backed up with Titanium, go into it and from batch, just choose restore MISSING APPS AND DATA. Don't restore system apps and/or data.
Hmmm, I think that would have required some fore thought, like putting the APK for Titanium into the the install_on_first_boot folder, cause after it rebooted, Titanium wasn't installed, and niether was a File Manger in order for me to install it, until it downloaded from the Market
Hindsight, huh!
Hello:
I had a 1.0.0 NST successfully rooted TouchNooter 1.6.24.
Following instructions from this forum, I updated it to 1.0.1:
Using the NST power button, I did a Factory Restore
Then, I applied TouchNooter 1.6.24 using this thread instructions.
Even though it booted properly rooted, and on 1.0.1 B&N NST software, I didn't pass trough the step:
"13. Enable Location Services when given the option."
Also, I even though I am able to connect to Wi-Fi, when I tried to activate:
"14.[...] launch Youtube from Go Launcher's App Drawer"
the YouTube app didn't respond.
However, I am able to open Gmail and sync it properly... but when I open the Market I can't seem to connect to my apps, nor to install new ones.
So here goes the questions ;-)
1) Is there a way to repair this?
2) If not or if is too much of a hassle to do so, how can I unroot my NST back to factory (1.0.0) state? With a Factory / hard reset like this or otherwise?
I don't mind loosing data, since almost all of my books are on a SD Card.
3) After unrooting, registering the 1.0.0 device in B&N and updating it to 1.0.1, will I be able to apply TouchNooter 1.6.24 succesfully again?
Awaiting your kind replies,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware. This method, however, does. (Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with it unless you were prescient enough to make a backup of your Nook's internal drives .)
1. Turn off your N2E completely.
2. Turn it on again by holding down power, and then,
3. as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
4. Click the home key twice, and you should be on your way.
Note that this absolutely destroys your shelves, notes, and other information, and you will be asked to register your Nook with BN again.
Hope this is helpful for people; it took a while for me to come across.
LastSilmaril said:
Hope this is helpful for people; it took a while for me to come across.
Click to expand...
Click to collapse
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
sarmasm said:
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Click to expand...
Click to collapse
I already sent you a PM with the link to backup/restore, but I guess it's worth reposting it here.
http://forum.xda-developers.com/showthread.php?t=1142983
From what I understand, yes, the nook should be factory-fresh afterward.
I do not know of a way to backup shelves separate than the general backup method, which of course, if you are making a backup of a rooted system, will not give you an unrooted system on reboot.
LastSilmaril said:
For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware.
Click to expand...
Click to collapse
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
LastSilmaril said:
(Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with
Click to expand...
Click to collapse
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
Ros:
Will any of the above methods unroot my NST?
If not, how may I unroot it: with nookRestore, otherwise, or not at all?
Awaiting your kind reply,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
ros87 said:
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots, my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs. What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here? This explains why when I did the L+R reset to 1.1 why I still didn't have WiFi though (I didn't know it was still 1.1; just shut it off and restored my 1.0.0 image, which I now understand to be compromise).
Now that I'm on 1.0.0, is there any advantage to using nookRestore again (ADB doesn't work, either by WiFi or USB) to try to get things to work? Or is there no solution to unrooting, whatsoever, unless/until you or someone else releases some sort of customized installer?
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
And I am sorry for misinforming you, sarmasm
-e
---------- Post added at 09:49 AM ---------- Previous post was at 09:39 AM ----------
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here?
Click to expand...
Click to collapse
No, I see what happened. I ran nookRestore, and this got me back to 1.0.0 (I didn't check the version number afterward, so I didn't know it changed) but didn't get rid of the Android launcher and such. THEN I did the L+R reset, and it *appeared* to be unrooted because the uRamdisk was replaced (...right? from your pm), but any modifications elsewhere would still remain.
So again, is there no hope? Running nookRestore again won't do anything, right? I do not know which files touchNooter modified outside of /data and /system (which at this point have both been wiped, since I have already ran nookRestore and L+R Reset)...
Ah, this is frustrating...
LastSilmaril said:
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots
Click to expand...
Click to collapse
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
LastSilmaril said:
my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs.
Click to expand...
Click to collapse
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher
Click to expand...
Click to collapse
Yes because /data/app is wiped by Factory Reset (L+R)
LastSilmaril said:
Now that I'm on 1.0.0, is there any advantage to using nookRestore again
Click to expand...
Click to collapse
Unless you have something that's not working properly, then no.
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
LastSilmaril said:
And I am sorry for misinforming you, sarmasm
Click to expand...
Click to collapse
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
[...]the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Click to expand...
Click to collapse
So, just to be clear and avoid any confusion whatsoever: using nookRestore (or a Factory restore i.e. 8 interrupted boot attempts) will remove the touchnooter 1.6.24 from my 1.0.1 rooted NST and result in a (as close as possible, user data issues appart) 1.0.0 stock NST, yes?
Awaiting your kind reply,
sarmasm said:
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!
Click to expand...
Click to collapse
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting
ros87 said:
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Click to expand...
Click to collapse
Thanks!
BTW, why the Reset after the Restore?
ros87 said:
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.
Click to expand...
Click to collapse
I hear you: I've been following some threads on the matter and it does seems an unstable issue, for the time being.
Very gratefully yours,
ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Yes because /data/app is wiped by Factory Reset (L+R)
Unless you have something that's not working properly, then no.
Click to expand...
Click to collapse
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.
LastSilmaril said:
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.
Click to expand...
Click to collapse
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.
ros87 said:
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.
Click to expand...
Click to collapse
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
---------- Post added at 07:01 PM ---------- Previous post was at 06:35 PM ----------
LastSilmaril said:
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
Click to expand...
Click to collapse
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Hard to say, but I have had similar issues earlier where my NST suddenly would not obtain an IP from a known router, but still work on other routers.
Didn't care to look into it back then and the problem went away on itself.
LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Before I give this a try, I wanted to check: do you have ADB working over WiFi after applying the noogie ramDisk root to the 1.1.0 firmware?
Thanks!
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24 Problem Solved!
Hello:
I've been waiting to see how the TouchNooter situation was resolved for the NST 1.1 update so I hadn't reseted my NST 1.0.1 just yet.
The thing his, yesterday I activated the wi-fi access at home, and just for the heck of it I used the GApp Android Market...
...and it worked just fine: I was able to download and update stuff (Go Launcher, Opera Mini) just as I expected (and wasn't able to) right after the 1.0.1 update and TouchNooter 1.6.24 re installation.
What happened in between? Other that booting normally a few times, which I always had been able to since the 1.0.1 update and TouchNooter 1.6.24 re installation, I sincerely don't know
Go figure... but thank you all for your kind advice and patience.
I'll be now watching closely the 1.1 update + TouchNooter 1.11.11 installation and see if and when will it be GApps (Market) compatible, specially so for those of us which are not very good or at least not dangerous at slicing root folders and files manually
Very gratefully yours,
rooting problem
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore
Nookguy32 said:
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore
Click to expand...
Click to collapse
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Don't use TouchNooter with FW older than 1.1.x
You can get the 1.1 update from here
https://code.google.com/p/nst-recovery/downloads/list
(use CWM to upload it to your NST)
Read first, act later etc..
Hi, so i put the rom zip file on my card and went into clockwordmod and wiped system cache etc.. So when i went to install from sd card there is no zip file, and i dont know what to do now. Please help
Someone please help my phone just stays at the motorola boot screen, and i needed to take out my battery to get my card out to put my backup nandroid on it. How would i go about restoring it?
Ugh no one can help!? I am pulling hair, i am so fustrated, i have no phone now
First of all ...patience young grasshoper...
Dx is nearly a legacy forum.
So you made a nandroid great.
Heres what i suggest.
Redownload and do a md5 checksum and make sure thevfilevis intact.
I always recommend chrome for dls.
Lets just assume your phone is bricked.
Novworries thanks to guys like sdshadow youre gonna be able to save your phone.
Heres a link to help you sbf your phone, because if your bootlooping its sbf time.
Heres his link Sd , I hope this is cool to repost.
https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/mobilebasic?pli=1
Now on a side note. You say you have cwm, but did you instal bootstrap first?
I will assume so since you said you have a nsndroid.
Also after you sbf, dont forget to reformat your sd card WITH YOUR PHONE.
This is an important step that many do not do. True not all cards have issues, but for some reason sd cards play a lot nicer when formated by current phone/manufacturer. Example: I have been able to use my gs3 32gb card in my n2 no prob.
But when I went from one xl to gs3 I nearly lost most files. I reformated on pc
After saving kept habing issues.
I used the phone, never happened again.
Lmk ill try n help best I can but keep 8t in the thread please.
---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------
One last thing NEVER EVER use TiBu to restore !!! Never!
Apps sure, but system data or using it as a nandroid is a no no.
:thumbup:
Made my list to share
Think this was solved over @ http://www.droidxforums.com
Sent from my Clear using xda premium
I have rooted and unlocked bootloader. I was running a rom just fine i flashed a kernel and getting boot loop. when i mount the phone to reload rom. windows 10 is having a hard time accessing the hard drive. I mean i see the htc 10 from windows explorer i open the hard drive of phone but won't open... is there a secret to mounting this phone?
how do i mount this phone and access the internal storage without issue on windows 10?
belovedson said:
I have rooted and unlocked bootloader. I was running a rom just fine i flashed a kernel and getting boot loop. when i mount the phone to reload rom. windows 10 is having a hard time accessing the hard drive. I mean i see the htc 10 from windows explorer i open the hard drive of phone but won't open... is there a secret to mounting this phone?
how do i mount this phone and access the internal storage without issue on windows 10?
Click to expand...
Click to collapse
You try and sideload rom using twrp?
You may also be able to access internal/external storage while in twrp
andybones said:
You try and sideload rom using twrp?
You may also be able to access internal/external storage while in twrp
Click to expand...
Click to collapse
tried it doesnt work
Almost sounds like you flashed an incorrect or corrupt kernel .. I had this happen once before and fixed it by re-flashing a stock, rooted RRU back to the phone and starting over
---------- Post added at 01:21 AM ---------- Previous post was at 01:07 AM ----------
Take a look at this link: https://forum.xda-developers.com/htc-10/help/soft-bricked-im-dumb-t3378838
I've bricked my phone more than once.. You can also try booting into TWRP, erasing EVERYTHING, and reinstalling everything through your SD card (You must copy the ROM to your SD card after formatting the data and reboot your phone back to TWRP again) which has also worked for me. Honestly your best bet is to search around on here and do your homework before taking a swing at trying to fix the problem. You don't want to brick it to the point of no return which is possible, but honestly I've been modifying and flashing phones before Androids even hit the market and I've never had a permanent brick. There's always a way
TNPaparazzi said:
Almost sounds like you flashed an incorrect or corrupt kernel .. I had this happen once before and fixed it by re-flashing a stock, rooted RRU back to the phone and starting over
---------- Post added at 01:21 AM ---------- Previous post was at 01:07 AM ----------
Take a look at this link: https://forum.xda-developers.com/htc-10/help/soft-bricked-im-dumb-t3378838
I've bricked my phone more than once.. You can also try booting into TWRP, erasing EVERYTHING, and reinstalling everything through your SD card (You must copy the ROM to your SD card after formatting the data and reboot your phone back to TWRP again) which has also worked for me. Honestly your best bet is to search around on here and do your homework before taking a swing at trying to fix the problem. You don't want to brick it to the point of no return which is possible, but honestly I've been modifying and flashing phones before Androids even hit the market and I've never had a permanent brick. There's always a way
Click to expand...
Click to collapse
ugh i will try that next. if this damn phone continues to have issues i will only stick to nexus and pixel devices.
I used the Moto G5 toolkit I found on here to root my phone (it's been forever since I last rooted, and it seemed like a simple, fast method), and I backed up my phone via the android backup option. It saved as a .ab file, is it possible to restore my phone to what it was before restoring/rooting last night (pre-root)? Skimming around, it's looking unlikely. Is there any way to get my phone somewhat back to what it was before? Unfortunately my grandma was signed into my account on an old tablet I gave her, and her stuff backed up via google, so I'm out of luck in that department.. Any advice is greatly appreciated!
bump
never take the easy way out unless have n idea what it does, adb restore backup.ab
i assume that backup is only apps n data doh so if don"t work would need flash a stock rom from here
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
https://www.youtube.com/watch?v=qjbU72RH_Rk&feature=youtu.be
krison01 said:
never take the easy way out unless have n idea what it does, adb restore backup.ab
i assume that backup is only apps n data doh so if don"t work would need flash a stock rom from here
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
https://www.youtube.com/watch?v=qjbU72RH_Rk&feature=youtu.be
Click to expand...
Click to collapse
is it possible to flash over my current rom without messing it up? i have a feeling the answer is no lol. at this point i've kind of started over, but if i can get at least my texts, photos, etc. back, it would be awesome. just not sure, the backup file is only 83mb. i didn't have a lot of pictures, but something tells me that's not what it has on it.
Braxton343 said:
is it possible to flash over my current rom without messing it up? i have a feeling the answer is no lol. at this point i've kind of started over, but if i can get at least my texts, photos, etc. back, it would be awesome. just not sure, the backup file is only 83mb. i didn't have a lot of pictures, but something tells me that's not what it has on it.
Click to expand...
Click to collapse
hmm u have twrp installed? if so can boot into it mount internal to usb n copy files if not then pray backup u made has it
krison01 said:
hmm u have twrp installed? if so can boot into it mount internal to usb n copy files if not then pray backup u made has it
Click to expand...
Click to collapse
boot into it with my phone?
Braxton343 said:
boot into it with my phone?
Click to expand...
Click to collapse
by that answer i can assume u don't have twrp install, so just follow the youtube video