Related
Hello,
I get my nook simple touch rooted using the minimal touch nooter.
But it seems I have some problems. Superuser is install, but when I install an application that require root, it states that, it is not possible with my device (something like that).
I want to install it back perhaps i did soemthing wrong at the beginning when I was testing the function.
Could you please tell me how I can do, to I have to make some wipe ? go back to factory ? doing the whole process from the beginning ?
thanks in advance,
You could try rerooting with minimal touch nooter.
It sounds like you may have picked a wrong default for superuser when the dialog was first presented asking if you wanted to grant root access with the choices being allow, deny and a tickbox for remember.
I have a vague memory of accidentally hitting "deny" with "remember" ticked on a device the first time the dialog presented itself and ultimately deciding to reset to stock and re-root the device.
So, if reapplying the root doesn't work, yes, you should boot from noogie and restore your backup or failing that force a device reset using the 8 failed boots method. There is also a method for resetting that I've had mixed luck with on the NST that uses the lower left and lower right buttons held down at power on.
Eded's got tools for making the device wipe process much simpler, though, posted at
http://forum.xda-developers.com/showthread.php?t=1475613
The 'old' tool is a really good one to know about as long as your device is largely intact
http://nooter.googlecode.com/files/Alpha-FormatTouch.zip
It doesn't include a replacement OS but assumes that you have not formatted your partitins - as long as that's true (as it is in your case) the tool makes one change to your device and then uses the onboard recovery process.
That's great, because it means that tool supports both the NST and the glowworm.
roustabout said:
You could try rerooting with minimal touch nooter.
It sounds like you may have picked a wrong default for superuser when the dialog was first presented asking if you wanted to grant root access with the choices being allow, deny and a tickbox for remember.
I have a vague memory of accidentally hitting "deny" with "remember" ticked on a device the first time the dialog presented itself and ultimately deciding to reset to stock and re-root the device.
So, if reapplying the root doesn't work, yes, you should boot from noogie and restore your backup or failing that force a device reset using the 8 failed boots method. There is also a method for resetting that I've had mixed luck with on the NST that uses the lower left and lower right buttons held down at power on.
Eded's got tools for making the device wipe process much simpler, though, posted at
http://forum.xda-developers.com/showthread.php?t=1475613
The 'old' tool is a really good one to know about as long as your device is largely intact
http://nooter.googlecode.com/files/Alpha-FormatTouch.zip
It doesn't include a replacement OS but assumes that you have not formatted your partitins - as long as that's true (as it is in your case) the tool makes one change to your device and then uses the onboard recovery process.
That's great, because it means that tool supports both the NST and the glowworm.
Click to expand...
Click to collapse
thanks for your reply. I don't understand everything you wrote, i forgot to explain that I am a NOOB with capital letters....
So, I need to try first with minimal touch as describe , as it is the first time I do it (i use this to root my nook first). If it doesn't work, i go back to factory and root it again ? no wipe cache, data, to do ? when I put a new rom I my defy I have to wipe either data or at least cache depending of what I install, this is why I ask
you'll need to wipe /system and /data. The tools Eded provides do that for you.
On your NST is a hidden file that restores your system. Eded's tool leverages that file.
- boot from clockwork
- install his zip
- remove the clockwork disk
- hit reboot.
Once your device restores, stop trying to root it.
Read up on making a backup. There are a couple of threads about backing up your NST. One of the great things about the NST is that you can easily make a complete backup of it.
I prefer to use a disk called noogie to make my backups.
Verify that your noogie backup is 1.8 gig. Folks sometimes try to restore from partial backups and that's a big headache.
Now that you've got a backup, try rooting again -- if it fails, you can either use the reset tool or restore from your backup.
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
electron73 said:
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
Click to expand...
Click to collapse
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
I'll check my laptop at home tonight. I believe I kept my heimdall backup before flashing cwm
Sent from my DROID BIONIC using Tapatalk 2
Just checked, mightve deleted it. Sorry man
aximtreo said:
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
Click to expand...
Click to collapse
Oh that would be awesome! Are you rooted? Let me find the commands in the meantime, I read somewhere it's a simple one command in terminal to extract the recovery partition into a file on sd card...
WHAT AN ORDEAL !!!!
But in the end: SUCCESS!
I managed to get my tab updated with the Verizon OTA update.
The problem is definitely CWM !!! A rude awakening is in store for everyone with the P6800 CWM installed, because it a) fails to verify the checksum of OTA files correctly on the i815, b) it thinks the tablet is a P6800, so the OTA file fails to run if it assert checks for "SCH-i815" hardware AND lastly c) modem updates don't work because the device /dev/cdma_update doesn't exist, so the modem.bin firmware_update call fails !!!
In short, I had to fumble the OTA file apart and do the update manually in two runs:
First file, kick the checksum, hardware check and modem update out, then manually run the ZIP through CWM. The zip subsequently (LUCKILY) updated the stock recovery and overwrote CWM with a new fresh stock recovery.
Second file had everything kicked out BUT the modem udpate and LTE patch, so with the STOCK recovery this file ran through just fine, updated the modem and then applied the LTE delta patch.
Phew!!!
Of course I had to manually restore root after the update, had backed up with voodoo, auto restore failed, so terminal and hacking it was...
Now I have the tab running on clean stock FD01, baseband and LTE FD01, rooted and stock recovery.
No more CWM, no more "hacking" with the ROM until some dev finally releases a "correct" CWM and at least ANY factory ODIN image is available to bring the tab back to stock if needed!!!
Kinda sick of the non-support for this tab. So much going on for the Galaxy Note and pretty much every other device. I'm starting to regret having bought this "special" Verizon version
Awesome find and great to know for whenever ics does come out. Could you please post the recovery img you got?
Sent from my DROID BIONIC using Tapatalk 2
OK after getting so many responses I decided to just post everything here in hopes that it will help others, too:
All files are here:
http://www.mywo.org:88/XDA/sch-i815/index.php
Step by step procedure to update the Verizon Tab from ..FA02 to ..FD01 build IF YOU ARE stuck with CWM installed on your tab and the original OTA fails with errors:
Upload the SCH-I815_FA02c_To_FD01.1.zip to the INTERNAL(!) SD card. This is important because CWM contains a bug that will only allow you to install from ZIPs stored on the INTERNAL SD storage.
Upload the SCH-I815_FA02c_To_FD01.2.zip to the EXTERNAL(!) (micro SD) card. This is important, because after the factory recovery is restored, it will correctly (and only) look for ZIPs on the EXTERNAL card.
Best way just copy both files to both locations
Fire up CWM and do "install from ZIP" and select SCH-I815_FA02c_To_FD01.1.zip
It should run (takes a while) and eventually tell you all is done. BOOT the tab. It should boot fine but in system it will show the new Android build FD01 but the baseband (radio) will still be the "old" one.
Now press and hold power and vol up again until you see the default Samsung recovery menu. Choose install from ZIP and select SCH-I815_FA02c_To_FD01.2.zip. This will now upgrade the baseband only. When done, reboot and enjoy being back on the "factory upgrade path" with the tab.
I hope someone more savvy than me can "fix" CWM to work properly with VZW tabs (accept the checksum, not fail the check for "SCH-i815" and provide the correct /dev file links for radio upgrades). Until then, I recommend just leaving the tab as-is and not tinkering with the ROM. Not that there is any custom ROM available anyway :-(
I also pulled the NEW factory recovery image FD01_recovery.img with the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/FD01_recovery.img bs=4096
So in case anyone with a botched recovery wants to restore factory (Samsung 3e) recovery. This was actually the reason I had to go through all this... There is NO factory recovery image ANYWHERE to be found. I can't believe that I should be the first one ever to post one?? Anyway, hope it will help
I'm still quite new here, so I do really appreciate every click on that "thanks" button
P.S. for tinkerers and devs I also uploaded the original, untouched OTA file (0559c0e4e08e.update_SCH-I815_FA02c_To_FD01.bin) as it came from Samsung or Verizon or whatever and ended up in the /cache partition.
THANK YOU!
Electron,
You sir, are a BOSS! Thank you so very much for doing the work, and sharing it. You just made things one hell of a lot easier on me, and anyone else that follows.
Regards,
-Rob
Also want to say thanks. You rock, dude. I wouldn't have known how to revert **** on my own.
Also, I feel like we need a sticky or something for sch-i815 owners to go to for device specific stuffs, especially since there is little knowledge/info out for this device.
Sent from my Galaxy Nexus using xda premium
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
phigmeta said:
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
Click to expand...
Click to collapse
You're in luck! You don't need to go through the whole ordeal because you do NOT have CWM! You can just update the regular intended way. Go into settings, about phone and then click check for system updates. If it presents you the OTA update, just do it the regular way.
My complicated "hack" is only necessary if you DO HAVE CWM installed.
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
phigmeta said:
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
Click to expand...
Click to collapse
Hey
OK unless someone can tell us how to "make" an ODIN flashable ROM for you, here is what I would do (and please don't get scared because it sounds a bit convoluted).
First, you need to be rooted. This is obviously the case.
IMPORTANT since you don't have CWM installed yet, SAVE your factory restore.img before proceeding, this saves you a lot of hassle later!
Open the android terminal, type su (accept the prompt) and then type (or copy/paste)
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/factory_recovery.img bs=4096
Check that you have a "factory_recovery.img" file on your sd card now it should be about 8M big.
Now you're safe to install CWM from the forum, look for the other thread(s) where this is being discussed and follow the instructions for the P6800 "international" version with 3G. CWM Thread here:
http://forum.xda-developers.com/showthread.php?t=1613638&highlight=cwm&page=3
Then (thanks to nicduim!) there is a full factory (rooted) CWM image floating around on the forums here:
http://forum.xda-developers.com/showthread.php?t=1613638&page=6
Which I used to restore my tab to "almost factory" with the missing bloat apps back in place.
I have a copy on my server here: http://ww.mywo.org:88/XDA/sch-i815/ it's the "2012-05-06.22.48.58.ZIP"
unzip that and put the contents on your INTERNAL SD card in the folder clockwordmod. So on your internal SD you should have /clockworkmod/2012-05-06.22.48.58 and inside there the files boot.img, recovery.img etc.
Use CWM recovery to restore this backup. If you never used CWM before. Press power button and volume up and hold both until you see the menu screen with text. You can go up/down with the volume buttons (go slow, it's very laggy) and with the power button you "select" an option. Select the "restore from backup" option and point it to the only folder being offered, the 2012-05-06.22.48.58.
The restore takes a while, then reboot the tab. Now you're back to stock! Last thing you need to do is get rid of CWM again because in the end it's still a bit buggy and will prevent the OTA update from running properly.
Since you luckily have a backup of the factory recovery in form of that factory_recovery.img file, just install and open terminal again, type su and then type (or copy)
dd if=/mnt/sdcard/factory_recovery.img of=/dev/block/mmcblk0p6 bs=4096
This overwrites CWM with your original Samsung Android recovery.
Now you just reboot as usual, connect to the internet and wait until the popup message shows up that a system update is ready, accept it and enjoy
If you don't want to wait for the automatic OTA, you can also stop before killing CWM and use my convoluted 2-step manual update which will get you to the exact same condition as the official OTA.
Hope all this makes sense
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
AlpineMan said:
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
Click to expand...
Click to collapse
Oh wait, so you are saying that in "About device" your Android is 3.2
Baseband i815.04 V.FD01 I815FD01
and your Build number is already at HTJ85B.I815FD01.SCH-I815.I815FD01 ?
That would mean you are already updated. In this case, it should be pretty easy to fix your problem. Which apps did you delete with Titanium? I can back them up from my system and make them available for you. All you'd need to do is drop the backup files into your Titanium backups folder and then fire up titanium and restore them!
The /dev/cdma_update node is only required WITHIN CWM recovery, so that is nothing for you to worry about. The zip files above won't help you because they are incremental updates requiring your system to be at FA02, not FD01 !
Yes... I'm already in the latest update. I already backed up the bloatware using Titanium Backup before uninstalling. So I just need to restore them back in order to receive and apply OTA updates in the future?
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
Please Help
Hi. I'm rooted and removed all sorts of bloatware with Titanium. I did this a long time ago and did not back anything up because I'm used to running hardware with custom ROMs available, and not relying on OTA updates.
Since there aren't any custom ROMs for the i815, I'd like to get ready for the upcoming ICS update. To do so, I want to get FD01 loaded onto my device, but I can't update because I've apparently removed too much of the required bloatware.
Does anyone know WHAT pieces of bloatware I'd need to reinstall in order for the OTA update to apply? I'd assume I can restore them and then apply the update and re-root.
If anyone can help pinpoint what missing APKs might help, I'll give them a shot. And, to the extent I figure anything out, I'll repost here in the hopes that it helps someone else.
electron,
Your instructions worked ... thank you so much
@jkrell... the failed attempt at installing the update should return an error message(s). You just have to read through them until you find the culprit(s). Apparently I uninstalled a few odexed files that were needed. I couldn't update until i hunted them down and restored them.
I guess we all jumped at the opportunity to install the cwm recovery image, that we didn't even think about cmda updates....ooops. So far i had to do a complete factory restore after the update. I was getting soft bricked to the point where I had no choice. Good thing I sent all titanium backups to actual sd card, i was able to salvage 97% f my data..... with the exception of a few downloads i forgot to move.
Gamecih doesn't work anymore (either version). No more automative data hacks I'm not sure what's going on. I uninstalled adfree..used titanium backup to uninstall both versions and reinstalled both several times. Oh well.
It really sucks not having nandroid backups but it's not worth the trouble of having to do this everytime an OTA modem update gets pushed to my tab. Needless to say, I won't be odining the cwm based recovery image again.
I'm with the O.P. I wish i hadn't wasted my money on this tab. No true cwm for this tab, so no dev will ever waste thier time with this tab. The sch i815 will soon be forgotten about and some other tablet will be all the hype before summer ends....that's just how it is. 21 months left on my contract.... [email protected]#k my life. Lol
Thanks Smitty.
When I try to update, I just see the "!" logo and then the device reboots. Is there a log file somewhere I can look at to see what the errors are?
I hear ya on the gloom and doom, but this device has only been out for just over 3 months now. I'd expect a recovery and some custom ROMs to come eventually. I doubt I'll go the custom ROM route unless CyanogenMod is supported, because I have no complaints about the tablet's performance thus far. It's speedy, smooth and the battery lasts forever.
In my book, this is a great tablet and I'm satisfied with the purchase.
Hey everyone,
I'm having trouble getting my Nexus 7 to update to 4.2.2. My device is rooted, I recently performed a factory reset.
The update has never appeared in my "System updates" menu, so I looked around and saw that if you force stop "Google Services Framework" and clear its data, the update will appear in "System updates."
It did, but when it finishes downloading, it says "Verification failed."
I tried another factory reset, and I had to again force stop and clear data on "Google Services Framework" to get the update to appear, but again it downloads and say "Verification failed."
I'm stumped now. Do I have to unroot and reroot? Do I have to keep waiting for this update? Do anything with the bootloader? (I really hope not...)
Thanks everyone!
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
Is flashing the stock 4.2.1 rom the same thing as doing a factory reset to 4.2.1?
If it isn't, would flashing the 4.2.1 rom wipe my tablet?
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
If he is trying to do an OTA to 4.2.2, would it not be more straightforward to just flash the 4.2.2 factory image? The OP has already done a factory reset, so it doesn't look like he/she is particularly attached to his current setup.
Also - the language he used was vague - it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
But it doesn't matter - newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images. It's just too detailed a process to describe compactly.
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC. Yes, all of it. You can throw it away later if you find you didn't need it. But if you follow the instructions for the Google (factory) images install, everything gets wiped off of /data including your pseudo - SD card.
At a minimum, that will allow you to follow the SBS instructions for installing the 4.2.2 factory images, or - you can simply install a 4.2.2 Stock ROM from over in the dev forum.
Whatever you do, start getting in the habit of making backups - and at least occasionally also getting copies of those off of the tablet.
Oh boy, lot of information to digest here....and a lot of questions
it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
Click to expand...
Click to collapse
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images.
Click to expand...
Click to collapse
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC.
Click to expand...
Click to collapse
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Horadrius said:
Oh boy, lot of information to digest here....and a lot of questions
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
Sounds like your download is bad if it fails at this stage. I believe it is saying the checksum of the download file doesn't match whatever is downloaded.
PS. not related to N7, why XDA use the re-captcha which I need to refresh several times to get something I can read
Horadrius said:
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
Click to expand...
Click to collapse
No. It means that for some strange reason, running a checksum program on the downloaded OTA file failed to produce the expected checksum. The most likely way this can happen is that the file is truncated - the download stopped short of the full file. Don't know why this is happening, but there you go. There could be other failure causes that are more rare, but it doesn't mean you are not "supposed" to have the OTA. It means that the download process is failing.
The *stock* recovery does a number of even more sophisticated checking than this; but it appears from your description that the recovery never even gets booted.
Horadrius said:
So, no updating the device from System Menu because I'm rooted/unlocked bootloader?
Click to expand...
Click to collapse
Yes and No. An unlocked bootloader causes no problems at all. ANY of the following CAN or WILL cause problems:
- attempting to run an OTA with a custom recovery installed instead of the stock recovery.
- having a modified boot partition (e.g. non-stock kernel, or slightly modified boot partition)
- having altered (or removed!) files in the /system partition that are targeted for patching.
- permissions changes performed by the installer script can cause root functionality to disappear
Horadrius said:
I'll have to flash everything as it comes out?
Click to expand...
Click to collapse
Not sure what you are asking here, but the basic answer is that if you stay on stock you can certainly apply OTAs easily. If you start altering things, you might or might not be able to apply an OTA; there are simply no guarantees.
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD. While it is possible that an OTA could succeed, it is unreasonable to have the expectation that it will do so.[/size]
Horadrius said:
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
Click to expand...
Click to collapse
I presume you are talking about the future here, as you said that you already did a factory reset at least twice. If you have subsequently added stuff back in, then I suppose you might be talking about the present tense.
But, yes - either TiBu or the Carbon app can be used along with a strategy where you simply back up the apps & data you are interested in, (plus any "flashable zips" that you used to customize your device in the first place), and you simply start from scratch with a factory install followed by re-rooting, and then restore your apps & data (using TiBu or Carbon).
One other thing you can do which is EASY is this: simply wait until a developer/ROM cook publishes a "Stock" flashable ROM based on the release that the OTA is upgrading to. Don't worry about the OTA, just wait a little bit. (These ROMs are already out for the WiFi-only model, BTW).
1) Take a backup as the first thing you do. It's easy and gives you some insurance.
2) Don't wipe (no "factory reset") - just install the Stock ROM over the top of your existing ROM.
that's it. If you were using a custom kernel, re-install it.
Horadrius said:
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD.[/size]
Interpret that as you desire. It is unreasonable for you to expect that you can diddle with your phone any way you please, and a patch install upgrade methodology will be robust in the faces of arbitrary changes on your part. You are the person creating the maze, not Google.
Moreover, it is your choice to take an upgrade - it's not mandatory. My guess is your tablet was quite pleasing to you before any OTAs started rolling out. Nobody is forcing you to do anything.
OK, one last thing. It is still possible that a manual OTA can succeed on your phone if it is lightly rooted - but there are no guarantees. The procedure does not require you to wait around until an OTA arrives on your phone, but it is not for the faint-hearted:
1) Download the appropriate Stock OTA File.
2) Re-install the stock recovery onto your tablet. You will have to dig it out of the Google full factory image for the version of the OS you are currently running. (available here)
Code:
fastboot flash recovery factory-4.2.1-recovery.img
3) Soft-boot into a custom recovery, e.g.
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
5) Using the command line and adb to communicate with the soft-booted recovery, create a recovery command file:
Code:
C:\myPCsux> adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /cache/update.zip
C:\myPCsux> adb shell
# cd /cache/recovery
# cat > command
--update_package=/cache/update.zip
^D # ( that is a Control-D character )
# sync
# reboot recovery
This will either succeed or fail. Based on your comments though, you might just want to overflash a Stock-derived ROM over the top of your existing ROM (a "no-wipe" install).
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13) <-- NOTE for WiFi (nakasi/grouper) ONLY
good luck with your tab.
Someone once said "Rooting is a lifestyle". There's some truth to that; it eats up your time. Perhaps it is not for you.
Thanks, bftb0.
Looking through your list of reasons for why my OTA might not work, none of them applied to me.
I didn't install any custom recovery (didn't install Clockwork Mod recovery specifically to avoid dealing with flashing roms) or kernels or modify any partitions, nor to my knowledge changed any files in the /system section.
I think I'm going to give this update a week or so to pop up on my update menu before I start tinkering again.
Don't get me wrong - I enjoy this kind of tinkering, and all the perks of rooting, but my knowledge is extremely limited, which is what makes it frustrating trying to find information. The only thing I've done before this is install Cyanogen on my HP Touchpad.
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
chimpanzeexda said:
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
Click to expand...
Click to collapse
That's all I've done, root and unlock bootloader. The download only showed up when I cleared data and force stopped the "Google Services Framework" process. I reboot the system, and check for the update and nothing is there.
well, sounds like you have to flash it manually using fastboot then.
That said, I myself have no intention of doing the update any time soon as I don't find any specific problem with 4.2.1 and there isn't any specific feature i want in 4.2.2
Horadrius said:
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
Click to expand...
Click to collapse
TL;DR Yes and No.
People that use toolkits seem to use hard-flashed installs of custom recoveries, as they don't really understand what goes on under the hood, even if the toolkit offers them a means to soft-boot any image the toolkit operator downloads. (I assume that the toolkits probably allow this; as I don't use them I don't know for sure.)
What I am saying is that the answer depends on your knowledge. So long as you have an unlocked bootloader, you can soft-boot any boot image you like - including custom recoveries.. (This also pre-supposes correctly-functioning device drivers, but that is a Windows/user training issue, it has nothing to do with Android).
When I say soft-boot, I mean that the image is transferred to the tablet, which then hands over control and starts executing that image - but it is not "flashed" to Flash memory, so the next time a boot occurs, the same boot images are still stored in either "boot" or "recovery".
In this configuration, the phone should be much more likely to complete an OTA as it will have the stock recovery present most of the time, and only temporarily present when you attach to your PC and kick things off with a custom recovery.
The OTA could still fail, but it probably would succeed for a very lightly rooted stock configuration (other than problems with losing root).
The only downside to this arrangement is that you can't be flashing roms or making nandroid backups or other forms of rooter activities when you are away from the PC.
For the IT-OCD or obsessive ROM hopper, that could be a good thing.
good luck... the rest is up to you.
Ok, I installed Clockwork Mod from a toolkit because going into fastboot and choosing "Recovery mode" led me to a picture of the Android guy with a red triangle on his back saying "No Command."
I'm just going to install 4.2.2 myself now. Question regarding that link - odex/deodexed - I looked up the difference but can't tell which one is appropriate for me - I'm guessing it's odex because that seems to be closer to stock.
Edit: It worked! Thanks for your assistance, everyone!
IMO, google should not ship odex image now that we have fast enough hardware. odex is just a form of 'pre-compilation' which only benefit first time load(or when the cache is cleared). Too little gain for such a complicated setup.
I installed TWRP and tried to flash SuperSU according to the guide by ashyx here: https://forum.xda-developers.com/showthread.php?t=3475381
So, from what I can tell by reading this thread: https://forum.xda-developers.com/galaxy-tab-a/help/samsung-galaxy-tab-10-1-mount-data-t3544561, the problem is that my device was encrypted. I tried restoring the full image that I made using TWRP, before trying to flash the boot. Stuck on Samsung logo now. I should have seen this coming when I was getting "failed to mount /data" errors.
So I suppose I need to flash that zip https://www.androidfilehost.com/?fid=24591000424951049, but I thought I better ask specifically about my device and situation before blindly flashing yet another zip.
What steps do I need to take now?
thanx
update :: it sounds like my last resort option is to flash the stock ROM (can I do this in Odin?)
BUT I noticed that SuperSU saved a "stock_boot_*.img.gz" file, which I copied to SD root and also to my PC. Now I imagine that if I flash this, I might be able to regain access to the OS... that would be the best at this time. Then I can do more research and try root again later.
Is this true, and how should I flash the stock_root file?
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
trefrog said:
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
Click to expand...
Click to collapse
It doesn't really decrypt it, it does a full format using either no encryption or new encryption. I'm sorry, but the files are gone. To answer your question though, I believe the encryption is full-disk.
Going forward, check out TitaniumMediaSync. You can mirror your internal storage to a computer via FTP, so when these things happen (and they do happen), you won't lose anything. I'm sorry you lost your files in this.
actually I didn't lose my files! I was able to restore the backed up boot partition that twrp made and tucked into a folder.
happy af :laugh:
... so are you saying that the decrypt function in the Android settings just wipes everything? Then why is it even there, if it's basically a factory reset?
hmm associated with Titanium Backup? I have a license for that, and as soon as I root this, I'll be installing it. Currently, all my important stuff (just photos), are backed up to my PC via QuicPic's cloud backup feature.
I think i have found myself in the same situation as you. I dont have any files or data to lose. managed to do first step in using odin to install twrp. tried to follow additional steps of installing super su, then padded boot. now the tablet wont load past the first screen. I can still get into twrp. how can i get this fixed, rooted and a custom image installed? any help in the right direction would be appreciated.
find that "stock_boot_*.img.gz" using the twrp file browser thing. copy it to the root of your SD for safe keeping (even if the SD is encrypted, it seems that it does so only at the file level, rather than partition/disk level, so it will be written unencrypted). if ur plugged to PC, you can copy it across for even safer keeping
then... I don't recall how I found it, but it's in twrp. a way to flash that file. worked for me, because as far as I made it, only the boot partition was affected
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)