Related
Hello everybody.
I had some hard time rooting my tablet because of the broken links and outdated guides that didn't work if you had updated to stock ICS. After some hours of tinkering I managed to find the correct files for rooting it so here's and up to date guide for rooting the Galaxy Tab 10.1 with the latest ICS OTA update.
For the record my tablet is GT-P7500 with 3G. This guide should also work for GT-P7510 which is WiFi-only. Please leave a reply if it worked for your other model so I can include it here! Please also tell me if there are mistakes in the guide or you have a problem at some point.
If you follow these steps you will void your warranty.
The package can be downloaded from the signature, or in a single file here:
MIRROR - 1 (Down at the moment)
MIRROR - 2 (Mediafire)
The package ROOT-GT-P7500.rar includes:
A recent version of Odin (v3.07 - 2013)
Samsung USB drivers for Windows
Odin flashable TWRP recovery
TWRP flashable SuperSu
1 - Preparation
Extract the files to a place on your computer.
Make sure Kies isn't running on your PC. Look for its icon in the notification area.
Install "Samsung_USB_Driver_1.5.5.0.exe".
Move the file "Flashable_SuperUser.zip" to the root of your sdcard.
Open "Odin3 v3.07.exe" on your PC.
Press the "PDA" button and select "recovery-TWRP-P4-P7500.tar".
Leave Odin open on the PC.
2 - Download mode
Turn off your tablet.
Connect the USB cable.
Hold POWER + VOLUME DOWN until you see some Android images.
Press VOLUME UP, wait a moment until you get to another screen an press it again.
You should now be in "Download mode".
Open Odin and make sure that the first ID:COM column has a bluish colours and some text like "0:[COM4]". The ID:COM turns blue whever Odin has detected connection between your PC and the tablet. If it's still white/grey something is wrong with the USB connection or the Samsung USB-driver.
3 - The flashing
Now everything should be ready for Odin to flash you a new recovery. Don't change any of the default settings other than what's mentioned here.
Press "Start" in Odin to begin the flash, it should only take a few seconds. If your tabletreboots everything went fine!
If you have problems with Odin detecting your tablet, try rebooting your computer and your tablet, and using a different USB port. It's probably a driver problem.
Now turn off your tablet to enter the new TWRP recovery.
Hold POWER + VOLUME DOWN until you see some Android images.
Press VOLUME DOWN once and then VOLUME UP once to enter recovery.
Use TWRP to backup your current ROM in case something goes wrong or you want to return to stock ROM some time. Google "TWRP guide" if you don't know how to use it.
Once the backup is done, press "Install" in the TWRP main menu.
Locate the "Flashable_SuperUser.zip" and flash it.
If it flashed without errors, reboot your tablet and see if you now have SuperSu within your apps.
You should now have root access!
4 - Custom ROMs
If you want to install custom ROMs, find a flashable ZIP of your favourite ROM and put it on your SDCARD.
You might want to use a program like TitaniumBackup to back up all your apps so you can restore them later on your new ROM.
Follow the above steps from step 4 to enter recovery.
Backup your ROM again.
Press "Wipe" and then wipe cache, dalvik-cache, system and do the factory-reset.
Press "Install" and locate your ROM's ZIP-file.
Flash it and reboot!
That's about it. For long-time reliability I've included the file package in the signature in a split rar file (XDA doesn't allow big files). Download them all and then extract only one of them like any other rar file. If none of the mirrors aren't working and you have a problem downloading it from the sig, feel free to send me a PM.
If this helped you, please press thanks! :angel:
Thanks! But doesn't unlock root work?
Sent from my GT-I9000 with cm10.1
huskyT said:
Thanks! But doesn't unlock root work?
Sent from my GT-I9000 with cm10.1
Click to expand...
Click to collapse
I have never user UnlockRoot. This is the manual way of doing it. If UnlockRoot works then it's probably easier for beginners to use that method
What is this unlockroot you speak of
Sent from my GT-P7510 using xda app-developers app
Stark_raving_mad said:
What is this unlockroot you speak of
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
It's an automated tool that supposedly roots your device in a couple of steps. I don't know if it works but I know that a couple of users have successfully rooted their tablets usimg this guide.
Sent from my Nexus 4 using Tapatalk 4
THANK YOU
Jiia said:
It's an automated tool that supposedly roots your device in a couple of steps. I don't know if it works but I know that a couple of users have successfully rooted their tablets usimg this guide.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
it worked for me p4wifi-7510
Following this guide, I finally root my GT after so long. Thx, OP!
cyanogenmod
the cyanogenmod failed to install on my samsung tablet p7510, but I didn't backup the original rom and there is no system to reboot it now !! is there another way to transfer another mod to install it ??
windsguy said:
the cyanogenmod failed to install on my samsung tablet p7510, but I didn't backup the original rom and there is no system to reboot it now !! is there another way to transfer another mod to install it ??
Click to expand...
Click to collapse
Did you at least manage to install CWM or TWRP recovery? There should be a button called "Mount USB-storage". Press it and connect the tablet to your PC, it should show up as a storage device. If that doesn't work you can always use ADB PUSH on Windows to move files to your phone that is in recovery mode. There are several guides for that.
EDIT: Nvm, didn't notice you had fixed it already.
Hey man thanks for this guide. I've been flashing my sgs1900 here & there for a few years but just acquired a SG 10.1 tab so obviously I had to root it for flashing some custom roms later on. Anyway I can see things are more or less the same, but still just a little bit different enough to want to have a good guide at hand before I get all smug at myself later on for thinking I'm a rom king
Excellent guide & thank you for all the required files. KUDOS!
Sdcard
Sorry, I'm new to this. I understand everything except the part that says "Move the file "Flashable_SuperUser.zip" to the root of your sdcard." how do I do this? When I hook up the tablet to my pc, I do not see a sdcard folder.
Regards
Mestar_matt said:
Sorry, I'm new to this. I understand everything except the part that says "Move the file "Flashable_SuperUser.zip" to the root of your sdcard." how do I do this? When I hook up the tablet to my pc, I do not see a sdcard folder.
Regards
Click to expand...
Click to collapse
My apologies, that part really is a bit confusing. "The root of your sdcard" means that you don't put it in any folder. It's the upmost folder level that the user can access without root rights.
Sent from my Nexus 5 using Tapatalk
Will there be any issues running this from 64bit Win7?
I flashed the TWRP file using attached odin and recovery file.
No issues during flash, but when I goto TWRP the screen flickers.
Just like the refresh rate is not ok.
Someone ideas?
It is the P7500 Galaxy Tab 10.1
spannow said:
I flashed the TWRP file using attached odin and recovery file.
No issues during flash, but when I goto TWRP the screen flickers.
Just like the refresh rate is not ok.
Someone ideas?
It is the P7500 Galaxy Tab 10.1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
it's a known issue.
Flashed bootloader only using odin, And not TWRP but the old good ClockWorksMod CWM
spannow said:
I flashed the TWRP file using attached odin and recovery file.
No issues during flash, but when I goto TWRP the screen flickers.
Just like the refresh rate is not ok.
Someone ideas?
It is the P7500 Galaxy Tab 10.1
Click to expand...
Click to collapse
Use the TWRP2.6.30 from this thread.
iZLeeP said:
Use the TWRP2.6.30 from this thread.
Click to expand...
Click to collapse
Thanks :good:
Currently I succeeded by using the http://forum.xda-developers.com/showthread.php?t=2098429
and using the rom [ROM] [JB 4.3.1] CM10.2/SGT7 for P4WIFI and P4 [20140223] accordingly. It was a frightning night but we servived (me and my tablet).
Thanks again.
well.. I broke it
i've followed this instruction and forget to sweep content before rom instalation and my rom is broken.
I've been searching a way to transfer another rom data to my tab memory but somehow my laptop couldn't detect TWRP v4.2.2 version.
I'm still searching for another TWRP version that can be file pushing on to TWRP directly from my laptop.
is there any suggestion?
thank you
nantabr said:
i've followed this instruction and forget to sweep content before rom instalation and my rom is broken.
I've been searching a way to transfer another rom data to my tab memory but somehow my laptop couldn't detect TWRP v4.2.2 version.
I'm still searching for another TWRP version that can be file pushing on to TWRP directly from my laptop.
is there any suggestion?
thank you[/QUOTE
Use TWRP 2.6.3.0 explained in two post lower, then read http://forum.xda-developers.com/showthread.php?t=2304122
howto use adb to push a new rom to the tablet (zipfile to flash). Be patience, takes a long time.
Click to expand...
Click to collapse
FYI, I just used Towelroot to root my Galaxy Tab 10.1 with ICS. Easy 1-click solution.
So I just got my OTA for 4.4 and downloaded the update. So I hit the restart and install button. The installing process ran like it supposed to be until the end part of it. The screen showed the word "error" with the android logo laying down. Then the phone just stayed like that and the screen not changing. So I decided to turn off the phone. Then I booted up the phone again, the google screen shows normally, but after that it shows the screen showing "no command" and I am stuck with that screen now and cannot go in. So I researched about it and find out I need to go to recovery mode. Then I hit the vol up and power button, then hit the recovery mode. But still, it shows the no command screen again.
Please help me... Thanks
Same issue here. Nexus 4 (rooted) OTA update from 4.3 to 4.4 failed. "No command" error. Please help
It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13
eksasol said:
It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13
Click to expand...
Click to collapse
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?
GIANTLIZARDMAN said:
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?
Click to expand...
Click to collapse
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410
eksasol said:
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410
Click to expand...
Click to collapse
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.
eksasol said:
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.
Click to expand...
Click to collapse
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.
GIANTLIZARDMAN said:
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.
Click to expand...
Click to collapse
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.
I got it with the method in your sig. Flash factory image without wiping data (a different method) (short, if bootloader already unlocked). Thanks!
eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
tippingvan said:
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.
Click to expand...
Click to collapse
GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
I'm having the same problem.
I had 4.2 stock (JOP40C).
I used NRT to unlock and root.
I then got an OTA update for 4.3 (JWR66Y, I believe) and lost root.
I was going to re-root, but received another OTA for 4.4, so I figured I'd install it before re-rooting.
Unfortuntately, I didn't re-enable USB debugging, which may be my current issue.
The install encountered an error (Android on his back and little red triangle).
Now I can't get past Recovery.
I tried installing 4.4 from JWR66Ymanually via adb using methods described here and get the status 7 message shown above.
If I try installing 4.4 from KRT160 I get an error indicating my device has the wrong keys (seems to imply not the right starting version for the upgrade).
I've also tried flashing the factory JWR66Y ROM from the Google site using adb. When I do that, I get a "signature verification failed" message.
It looks like there may be a way around this if a flash a different recovery. Can I do that with adb?
I can't connect with NRT anymore. I ahve some backups I made with NRT, but am not sure how to load them without using NRT.
I can sideload with adb, but can't do much else. "fastboot devices" doesn't return anything.
Help!
Thanks!
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
brownbullet said:
Hi out there looking for help with my G2 (D803) . I am new to all this rooting and TWRP stuff but been trying to learn and figure this out. I accepted some update after which the phone only boots into TWRP recovery project v2.6.3.2 now. Looks like I lost everything else (at least that is what I think has happened).
So I have been reading on the forums and learned about using ADB devices and getting the right rom from xda-developers (I am with Telus in Canada) - used http://forum.xda-developers.com/showthread.php?t=2432476 - downloaded LG support tool and flash tool and drivers for phone and installed them all on the computer.
I first had trouble pushing the rom on to my phone (using ADB devices and ADB push commands) because the phone would just turn off while transferring and I could only regain access when the battery is fully drained (happens really fast now?) and I recharge (which seems to take forever now?).
I took the phone to a store and they did some tweaking (says SIMULATING ACTIONS on the title now below TWRP and version number) after which I could push the ROM (I did rename it on the computer) successfully on to the phone using "ADB push" in command prompt.
I proceeded to install the rom and it says successful but clearly it did not work. What I see is:
Finished running boot script.
E:storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
simulation actions ...
updating partition details ...
but then I reboot and it goes back into TWRP.
I tried going through flashtool as well and followed the steps to install the kdz file but it seems like the computer is not connecting to the phone. But if i go to device manager the device shows and says working properly (i installed the drivers already) and you also hear the beep when plugging in the USB cable into the phone. again it also seems to connect through command prompt because i can push a file successfully.
I am getting worried that I am out of luck with this phone . Can anyone help or provide suggestions as to what I am doing wrong? Would really appreciate it. Thanks.
Click to expand...
Click to collapse
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Download the whole Rom and flash it
Sent from my LG-D802 using XDA Premium 4 mobile app
brownbullet said:
Thanks for the reply. It definitely did something because the installation process moves forward now. Now I get:
Zip signature verification failed: 1
Error flashing zip '/sdcard/telus.zip
also when i unclick zip file verification in setting i also see:
checking for MD5 file...
skipping MD5 check: no MD5 file found
So problem with the zip file? I downloaded it off xda-developers but I renamed the file to Telus.zip and pushed it on to the phone in the sdcard directory.
Click to expand...
Click to collapse
you are a fxxxing genius thnx you so much
im going through the same thing
bigpappapuff said:
you are a fxxxing genius thnx you so much
Click to expand...
Click to collapse
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Chris2312 said:
Can you help me out? The same thing with my G2 and i have no idea how to fix it.
Click to expand...
Click to collapse
More info please.
bender_007 said:
More info please.
Click to expand...
Click to collapse
my g2 was was rooted and got an over the air update so now its just stuck in twrp and all of the memory got wiped so i dont know if its possible to fix it or if i have to get a new phone.
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
bender_007 said:
There are a lot of threads for your issue. Will search for one when I'm on lap.
Sent from my LG-D802 using Tapatalk
EDIT: There you go
Click to expand...
Click to collapse
Thank you
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
Hi,
Was stuck with my HTC Butterfly x920d with the same. Thanks for your guidance, was able to recover.
Foolishly, I had SIMULATE option checked in the recovery settings. Though was able to boot into system but no account, no google & reset stuck into recovery.
Thanks a ton
(I was trying to reset this device for my father)
flutterguy317 said:
I'm not entirely sure, but it sounds like everything in TWRP is being simulated, which would mean that no files are actually written. Try going into Settings in TWRP, uncheck the "Simulate actions" checkbox, and run the rom installation again.
Click to expand...
Click to collapse
How do you get into settings when it goes straight to simulating actions?
Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks
Join the club. No one has the VZW one for the flat s7 either....
Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be
billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man
Footer and verification error so far
Same here
Sent from my SM-G930P using XDA-Developers mobile app
dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.
Whenever i tried to follow the link it asked me for a security key ????
footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.
TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?