[SOLVED]
Verizon Developer Edition. I just did a complete reset to 4.4, stock recovery and all. Booted up, got the 4.4.2 update, installed that. Flashed custom boot logo, then flashed TWRP again. Went to go wipe data/cache and accidentally wiped system. Now I've got no OS.
What do I do now? I've updated to 4.4.2 from 4.4 and can't revert back.
You'll need a good friend who can make a backup in TWRP of just the System partition. This friend probably should have an identical phone, in my case, we both have Verizon Developer Editions. He also needs to be giving you a TWRP system backup that matches what you most recently had flashed. In my case, I had just taken the 4.4.2 update. Luckily he had too already. A TWRP backup of the system partition from someone on 4.4 or 4.2.2 would, I'd guess, brick you. So best to find someone with an identical phone to you and matching software, otherwise I don't know what'd happen. There should be 3 files, a recovery.log, system.ext4.win, and system.win.md5. This is about 1GB so it'll take time to transfer/download/upload around the place.
I had downloaded the adb tools a while back from step 1 here: http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
You need adb and all the drivers and crap working for this
Put the 3 files in that folder, where adb is.
Next, boot into TWRP on your phone with no OS and make a backup of everything, should go quick as there's no system and I'd guess data is probably pretty empty...
Next, go back to TWRP main page and go to mounts, then mount the /Data partition.
Shift and right click in Windows Explorer where adb is and open command prompt, type in adb shell and you should get a prompt. Type ls and hit enter, should see contents of the /Data partition
Type cd sdcard/TWRP/BACKUPS and hit enter, then type ls and hit enter, you should see another folder named T something, this is the phone's serial number. Type "cd serial" where serial is the name of that T folder and hit enter again.
Type ls again and you should see a folder starting with 2014- or whatever year you may be reading this in... that's the folder that has the backup files you just made.
Type mkdir A and hit enter followed by typing ls again, now you should see that 2014- folder and another folder named A
Type exit to get out of shell. Now type adb push recovery.log /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .005s or something.
You can type adb shell again, enter, and navigate to the directory to make sure there's a recovery.log file in the A folder. If there is, good. If not, no good, you did something wrong. Don't forget to type exit to get out of shell and back into Windows command.
Now do the same for the next small file, so type adb push system.ext4.win.md5 /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .007s or something.
Finally, the big file. Don't panic like I did, it'll take some time, like 4 minutes maybe. Type adb push system.ext4.win /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like 380s or something.
So, now you should have your TWRP system partition backup files in the A folder in the proper folder hierarchy. Now on the phone, just back out of mounts (hit middle button) and shut phone down and it'll warn you about there not being an OS.
Reboot recovery, Restore, you should now see the folder named A as an option. Hit that, and it should auto select System and nothing else. I did md5 check option. Slide to restore. Wait. Wait. Wait. Reboot.
If you're lucky, you'll see the boot animation and hopefully boot back into Android. It'll take a while the first go too so be patient.
Or, I have a buddy with a Verizon Dev Edition in close proximity... can he just make a backup in TWRP and then I could restore it?
Or is there a way to pull the System.img from his device and flash to mine?
Or how about the system.img from T-mobile? Could I flash that? Or... that wouldn't help would it...
CartlandSmith said:
according to this thread, you can:
[Q] Can you restore a nandroid backup on a different device?
But he needs to be on 4.4.2.
Click to expand...
Click to collapse
Yeah, he's on 4.4.2 already as well. He's making a TWRP backup of just System. So I guess I need to figure out how to get the folder hierarchy and the TWRP backup files onto my device. I assume through ADB somehow?
Also, I did grab the 4.4.2 OTA zip file before doing all this, so I have the update zip, but I don't think that helps me either does it?
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Just realized only 4.4 images are posted.
fml
yeah, I realized I could just make a TWRP backup of my empty partitions to get the folder hierarchy made. So now all I should need to do is figure out how to either:
A. Push a folder and sub-folders/files via ADB or
B. Create folders in ADB then push the files to the folders
Sounding good?
GloryUprising said:
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
From all I've read and understand, once you upgrade to 4.4.2, the bootloader also gets updated, and the new bootloader isn't backwards compatible, so you can't flash any images older than 4.4.2 else you'll brick somehow.
Just out of curiosity, anyone know how long it takes for factory images to be posted? I assume a metric &#@$ tonne of crap has to be done to get the files and poo from Verizon to Motorola to host.
Yeah. I'm pretty sure TWRP has already made the folder hierarchy for me. I think I just need to get my buddy's TWRP files and then push that folder to the device via ADB with "adb push /TWRP/BACKUPS /mnt/sdcard/TWRP/BACKUPS"
Yeah, I think maybe it's a folder with the device's serial number? T-something?
Okay so can you post the hierarchy I need to make? TWRP>BACKUPS>SERIAL#>BACKUPNAME>Backup Files?
Okay, I've got his TWRP backup of just system downloaded, 3 files. I booted into TWRP recovery and in the mounts sections, I mounted data. Now I can navigate the data folders via ADB shell. I've created a new backup folder "B". Now I think I just need to push the 3 backup files into that folder. Backup folder "A" was the one I made to get TWRP to auto-make the folder hierarchy.
How do I unmount now that I've pushed files?
Not that I can find.
I've got all the files/folders pushed and made. My phone is connected via USB and is in TWRP recovery. If I hit a volume button I get a gray screen with just "Updating partition details... Full SELinux support is present." I don't know what to do from here. I can still do "adb shell" and see my data partition in my command window...
Haven't tried, afraid to lose what I've done so far. If I back out to Restore in TWRP, the directories/backups don't show. I think it's cause my /data is mounted and being used by my PC so TWRP can't see the partition?
Believe it or not, I did this exact something, not paying attention and boom system wiped. I have been a lurker on XDA for years and years and never needed an account because I have never made a stupid mistake like this in the past.
I contacted Moto to see if they would bail me out, but if not I will just wait out the factory image its a tough lesson.
I have reverted back to my my old AOKPs3 until i can get this all figured out.
*I will be watching this to see if you figure it out, and if so maybe you can help me.
GL.
Fingers crossed. Backed out to main TWRP home screen, powered off. Booted back into recovery, Restore tab, my folder showed up with the System backup in there, restoring now...
Success!!!
CartlandSmith said:
there should be a popup warning saying when you wipe your system you run the risk of losing your OS or whatever something shorter, but enough of a warning that it would cause people to stop and think if this was what they intended to do.
Click to expand...
Click to collapse
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Mike7143 said:
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Click to expand...
Click to collapse
Me either.
Mike, Could you send me the file? Im in the same boat as you "were"
Related
I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk
Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.
Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.
Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.
Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk
Double post.
Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk
I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
voltage88 said:
I had the SD card issue where it wasn't seeing all my files. Recovery mode would see files I could not locate within the os.
What I did:
Backed up my contents. Always have a nandroid backup!
Downloaded and md5sum checked Trickdroid 8.0.0
Booted into recovery, wiped phone. Formatted all partitions.
My next plan of action was to adb push trickdroid. This failed, its not seeing my sdcard partion. I have attempted to format /sdcard. It returns no errors. I got to mount /sdcard, It fails to find the directory.
When I boot into fastboot (Thinking at the very worst I could relock my device nad flash an RUU)
It does not see any devices. I have verified multiple times that I am using the correct driver. I have removed all drivers from the system, attempted to use htc sync, uninstalled that, used the Naked Drivers, uninstalled those (still no device in fastboot), installed the ADB Driver installer (found using the search button). Still, no devices in fastboot.
If someone could point me in the right direction I would greatly appreciate it. I have been using adb and flashing devices for a number of years and have not yet encountered a problem like this.
-Erik
Click to expand...
Click to collapse
I fixed it!!! Anyone that has a similiar issue. This is what I did.
In a previous thread, I saw that 4.2 will redo the sd card structure. After some research, it was recommended to change the path to /data/media/0. I was then attempting to do the command as follows 'adb push Trickdroid_8.0.0.zip /data/media/0' (without tick marks)
The file was pushing as it should (no progress bar) however, it would fail at the very end saying it was unable to locate the directory.
After seeing adb fail in that manner, I knew my sdcard was not mapped to the above path. What I did was boot into recovery, go to mounts and storage, mount my sdcard. Go back to the first menu now.....From here, select advance, and view log. It will tell you where your sdcard is being mapped to. Simply push your zip file to this directory and success! I have a working phone again.
Fastboot still doesn't recognize my device however. I'd be more then happy to be educated as to what I may have done wrong.
I have flashed gpt.bin file of Potter and I am unable to downgrade or move back to sanders in my Moto G5s Plus (Sander). Help Please!!
khatrimann said:
I have flashed gpt.bin file of Potter and I am unable to downgrade or move back to sanders in my Moto G5s Plus (Sander). Help Please!!
Click to expand...
Click to collapse
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Hyde1234 said:
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Click to expand...
Click to collapse
Thanks for your help. I'll give it a shot and will revert back to you ASAP
PS: the google link isn't working
Corrupted google link
Hyde1234 said:
I was assited with a dev on here named pizzaboy192
He had me for load oem.img through the terminal commands.
He uploaded the oem.zip and he has a special recovery.img file to use to do a proper oem backup.
Here is a quote of our converstation.
After all that i am still not perfect. I used a twrp backup of oreo I found. It is the only way I can load anything on my phone is though a backup/restore.
I can't flash anything, and I can't adbside load anything either.
You can download the twrprecovery file from his post.
"Visit my XDA profile (I'm on mobile right now) and find my post about TWRP for stock. It's a special version I threw together to backup the OEM partition properly since TWRP normally doesn't.
What we're going to do is fastboot boot TWRP (not flash it) and then restore a backup of the Oreo OEM partition using TWRP.
Then fastboot flash all other Oreo partitions. Any Oreo ROM will work just to get you running, and it should take otas too."
next message:
"OK we're going to force OEM onto it.
https://drive.google.com/file/d/1WUw...ew?usp=sharing
That is the OEM partition but compressed. It should extract to a 768MB file (roughly that size)
copy it somewhere on the phone (TWRP should allow you to mount the internal storage as a USB drive, if that doesn't work, try ADB Push and push it to somewhere like \tmp
Then you will need to use adb to do the following (TWRP is broken for ADB and the stuff it spits out to your computer is garbled. I wasn't ever able to fix it.)
type adb shell and it should dump you down into some garbled mess
hit enter a few times to make sure you're at the shell (it's a root user)
load up notepad, paste the following into it and edit it so it shows the right path for the extracted .img file on your phone
dd if=/tmp/oemoreoaug.img of=/dev/block/bootdevice/by-name/oem
Copy that string and paste it into the adb window on your computer and hit enter. It will take a while to process it and then return an error about it running out of space before you hit the end of the file. that is OK (since your partition is too small)
Once it's finished, copy that result and send it to me just so I can have a clear idea what is going on.
Reboot into fastboot, reflash the oreo firmware but skip the line for OEM (it's kinda global, but not 100% but since moto hasn't released any updates since the oreo one and they don't seem to care, who cares as long as it works, right?) and then see if it boots. "
so if you get that to work,
then I was only able to do a restore using this file
MotoG5sPlus_Sanders_Android8.1Oreficial(ByYoungRockTech).rar
after that I did a full backup using Pizzaboys recovery, and now I am able to restore it at anytime.
Click to expand...
Click to collapse
Could you send the link again? For the same is corrupted
I did the same thing, flashed potter firmware on my sanders, and now ican't revert. Please help, also, the google link isn't working.