I apologize if this has been covered before, but several searches haven't turned it up.
I'm trying to upgrade my Galaxy Tab Pro 8.4 to Android 7.1 and I'm running into a roadblock in the recovery mode. I have options for Wipe data/factory reset and Wipe cache partition, but there's no Advanced option, so I can't wipe the Dalvik cache.
The tablet is rooted -- I checked it after running Odin, and even ran Odin once more to be sure -- and I had Debugging checked under Developer Options, so I think I should be seeing the Advanced option, but it's not there.
I tried installing the new OS anyway, but I got failure messages, and then the tablet rebooted itself to 4.4.2, still rooted. I've restarted Developer Options and re-checked Debugging.
I must be missing something, but I can't see it. Thanks in advance.
This is driving me insane. Every time I think I'm making progress I run into a roadblock. At this point I'm just trying to load/install TWRP recovery so I can do a thorough wipe, including the Dalvik cache, but although I can find the flash file in my file manager, TWRP doesn't see it.
On the tablet's own storage TWRP starts its search at emulated/0, but I can't find folders in the file manager called emulated or 0. It will also look in sdcard, but even though I've copied the file there, TWRP doesn't see it, although it seems to be looking for "extsdcard." It also doesn't see zip files I've downloaded to the sd card, if that matters. It seems that TWRP can only find folders, not files.
I uninstalled and reinstalled TWRP, but it's the same. So I uninstalled TWRP again and tried to go with CWM, but it's not compatible with my tablet.
Part of me knows there must be a solution somewhere, but this has just about reached the point of "life's too short." If anyone can offer any help, it would be greatly appreciated.
I've finally had some success! I found instructions for installing TWRP with Odin, and they worked. And so, I expect, did the TWRP backup of the tablet's OS. All I need now is a Nougat 7.1 download that works; the one I have now:
Galaxy Tab Pro 8.4 Lineage OS 14.1 [mondrianwifi] [Android 7.1.1 Nougat]
...isn't working. TWRP attempted the zips I downloaded (OS and GAPPS?) but the verification failed. So at this point I can only boot to TWRP. If I just start the tablet normally, it hangs at the Samsung logo screen, and while I can turn it off, it starts itself again after 10 seconds or so, requiring a boot to TWRP and shut down from there.
I'm hopeful I'll find downloads that work, but some of the links I've found appear to have expired. I should be able to go back to 4.4.2 from the backup, but since I've gotten this far I'd like to follow through. It looks like I have more searching ahead of me.
More success! I found the following link to the OS and downloaded the Pico GAPPS as that author suggested, and it worked! My thanks to Marc0601!
https://forum.xda-developers.com/ga...m-resurrection-remix-5-8-5n-02-09-18-t3837764
Related
So just as the title says i decided to root my n7. Everything seemed to go smooth until my nexus 7 was stuck on the boot animation screen for about 20 minutes. I tried doing a factory reset in TWRP and it said wipe failed. I decided to flash CWM instead and do a factory reset but i couldn't. It said error mounting /data. I'm not sure what to do googling around didn't seem to work.
TWRP gave me a message saying SU is not installed after i installed the recovery so i clicked instal SU. I'm not sure if that contributed to my problem or not. Any help would be greatly appreciated.
Ok so i figured this out.
So for anyone who ever gets into an endless bootloop with the inability to wipe data you need to do the following.
1. Download the latest Factory image from google.
2. Exctract the files into your platform-tools folder an run the "flash-all" command this video illustrates it perfectly http://www.youtube.com/watch?v=bsss9e71bKo
3. And you're done! hopefully this helps someone out
Hello everyone,
I hope there is somebody out there who can help my Nexus7 -2013 to operate again.
My nightmare started after upgrading Android os to 5.0.2. The tablet started to shutdown from time to time, so i searched for downgrading to an older version but could not find such option on the menu.
Therefore, i followed a youtube video -not knowing what i was doing- and setup TWRP 2.6..0.0 on my tablet. When i opened it again, OS was working but google play and keyboard were not working.
So, i tried to backup, no success. Then i tried all options on TWRP menu (wipe, factory reset etc.) and it got worse.
Currently, when i open the tablet, it takes me to Google logo with a lock, no desktop or OS works. (see picture 1). If i wait long, it takes me to TWRP menu. see pic2)
For the last one week, i tried everything; adb sideload, install, mount etc, nothing solves the problem.
There is no place to run flash commands etc. I connected to computer but only adb sideload works and it does not help me use any other commands.
I had a flash disk with 5.0.2 and 5.0.1 factory images, but it did not setup those two files (and does not see them on flashdisk anymore i do not know why)
I also downloaded twrp 2.6.0.0 and 2.8.5.0 MD5 img's and tried to use but no success, changed file extensions to zip also not worked etc. (see pic3)
Anyway, finally i downloaded alternate rom (CleanROM-5.1.0) and UPDATE-SuperSU-v2.46.
I am trying to setup any of these, just to operate the device.
I install SuperSU (zip1) and CleanRom(zip2) together from install menu and setup was complete (see pic4). CleanRom was setup successfully.
However, when i reboot from TWRP after install it says "root permission appear to be lost..." (see pic4). Whatwer i do, it opens with Google logo and the only place it takes me back is TWRP recovery page.
Your support on this is greatly appreciated.
Thank you
Follow the instructions here. You can transfer installation files in recovery using adb commands or you should be able to copy using Windows Explorer.
http://wiki.cyanogenmod.org/w/Install_CM_for_flo
Or go back to stock using the Nexus images.
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .
Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?
I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.