Related
I have had many android devices and almost all of them i have turned to this site to either make them better or give them renewed life. The nexus 7 is my first tablet and due to previous experience i came straight here to us and upgrade to the kernals and firmwares off the perfectionists i have come to know! (thank you all for the many years of making my devices as great and if not better than more recent mobile devices!)
Today i got my nexus seven and i downloaded: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH MORE
This i belive allowed me to unlock my boot loadeder and root my device (althoug i have no way to confirm rooting!).
After unlocking bootloader and rooting i attempted to install a custom rom (Smooth rom 4.3) using given instructions to use JRomflasher from there page. Only problem is, jrom does not find zipped or unzipped rom leaving me without an os! Could one of you nice guys help me out! I had a wifi 4.2.1 tab if that could help! kind regards, Alex!
Re: Please help a girl in need!
Download a kernel onto your computer as well as a ROM. Open a command prompt shift +right click. Plug the n7 in to the computer. Type "fastboot reboot recovery" without the quotations and press enter. Your device should boot into Cwm/twrp or whatever recovery in installed. Using windows explorer, Drag the ROM and kernel to your n7. First flash the kernel, then the ROM, then reboot. I know cause this happened to me too.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Cheers for advice but my device still refuses to acknowledge an updates there! in rar/zip or unzipped format! it just loops me back to start screen and i fail to do it all over again! Through experience i believe its my version of clockwork mod gone wrong as it gives me the option to install zip from sd card but continuoslly fails! what am i doing wrong?
In the future please use a title that is indicative of your actual problem and will be found and possibly help someone with a similar issue who does a search before posting. Also, people in here are helpful to all, regardless of gender. Thanks.
frap129 said:
Download a kernel onto your computer as well as a ROM. Open a command prompt shift +right click. Plug the n7 in to the computer. Type "fastboot reboot recovery" without the quotations and press enter. Your device should boot into Cwm/twrp or whatever recovery in installed. Using windows explorer, Drag the ROM and kernel to your n7. First flash the kernel, then the ROM, then reboot. I know cause this happened to me too.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Click to expand...
Click to collapse
Flashing a kernel before you flash a ROM would have no effect at all because nearly all ROMs generally overwrite the boot partition. (I dunno, maybe there are Aroura installers that avoid installing boot partitions). I think you meant to say "Flash ROM, then flash kernel".
@OP Use the toolkit to restore the stock rom, and then immediately
- use the recovery to make a backup and
- copy the backup to your PC
after you have done that, only then you should start considering custom ROMs and kernels. You might even want to rehearse a couple of disaster scenarios so that you are familiar with the custom recovery you have installed.
Because of the lack of an external SD card, there are plenty of folks who - due to unfamiliarity with how things work - not only screwed up an installation, but also deleted all their backups on the *emulated* SD card.
good luck
also do what the above poster said, and I find using either goo manager or rom manager probably the easiest way for a noob to flash some roms
so use your tool kit to "return to stock" ( hopefully it has that option) then root it, then install goo manager or rom manager to automate rom installs for you
Miami_Son said:
In the future please use a title that is indicative of your actual problem and will be found and possibly help someone with a similar issue who does a search before posting. Also, people in here are helpful to all, regardless of gender. Thanks.
Click to expand...
Click to collapse
ok sorry! do you have any input though because atm i have a TABLET THAT ONLY SAYS GOOGLE!, SORRY TO SOUND TROLL!
Re: Please help a girl in need!
bftb0 said:
Flashing a kernel before you flash a ROM would have no effect at all because nearly all ROMs generally overwrite the boot partition. (I dunno, maybe there are Aroura installers that avoid installing boot partitions). I think you meant to say "Flash ROM, then flash kernel".
Click to expand...
Click to collapse
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
frap129 said:
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
Click to expand...
Click to collapse
A million different things could have caused that.
You don't need to take my word for it though - just open up the installer scripts for each and note the erasing of the boot partition. It is impossible that you can flash a kernel to the boot partition, and then erase that partition, and then flash something else there (the boot image from the ROM), and have the original kernel survive.
I suppose that certain Aroura ROMs (or multi-ROM) installers could behave differently as they may allow mix-n-match ROM/kernel combinations.
But in general, standalone ROMs always overflash the boot partition (that's where the kernel & ramdisk image goes), so installing them 2nd would certainly overflash any prior "kernel flash". (Moreover, many of the kernel flashes drop stuff into /system/etc and elsewhere - so those things would get trashed too).
@OP : If the Google (black and white screen) shows a little open padlock at the bottom, then your bootloader is unlocked.
read this thread to figure out how to get into the bootloader/fastboot mode:
[REF] Nexus 7 Button Combinations
frap129 said:
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Click to expand...
Click to collapse
You r equate correlation with causation and have doled out bad advice based upon that flawed logic. The simple fact is that the kernel is overwritten when the rom is flashed.
Sent from my Nexus 7 using Tapatalk HD
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
amangupta53 said:
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
Click to expand...
Click to collapse
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks Ged.
Seems like I missed CF-Auto Root Method in my list. But I guess it's essentially the automated format of option 1 I listed above. I've already switched to SlimROM 0.8 F2FS which included the M-Kernel and thus easy to root. (A friend pointed it out to me, I took the plunge for F2FS)
Thanks again for the detailed solution. I'm sure it'll be useful for anyone looking to root Stock Lollipop with Stock Kernel.
Cheers!
Hello
I have a brand new Samsumg Galaxy S4 but I hate TouchWiz. I want to have the purest Android experience.
I'm a bit new with this phone and haven't used Android in two years now so I'm a bit lost.
What is the latest official Google Play Edition available for my S4? It doesn't have to be Lollipop (although that'd be nice), it can be on KitKat. As long as it's official and untouched (if such a thing exists)
Thank you for your time and help!
I use this rom
It's mostly stock but with a few features added. It has an aroma installer from which you can choose what to install. E.g if you want stock kernel or custom kernel.
GDReaper said:
I use this rom
It's mostly stock but with a few features added. It has an aroma installer from which you can choose what to install. E.g if you want stock kernel or custom kernel.
Click to expand...
Click to collapse
Thanks! I'll definitely try it. The only thing is I tried to install TWRP yesterday but the phone started to load it and then stopped. There was a tiny tiny progress color but when I just restarted the phone without completing the process, it worked fine which shows that it didn't even start.
I flashed TWRP using Nandroid manager (from google play) and the img file you get from the twrp site.
That's the only method that worked for me.
TWRP Image
Nandroid Manager
If you're on stock rom, nandroid manager will prompt you to install busybox app from google play (since stock roms don't have busybox). Just download it and install busybox using that app.
Then you can use Nandroid manager to flash that twrp recovery image. Then boot into recovery to make sure it works
Thank you! I've installed TWRP now. I'll continue the tutorial and keep you posted!
Alright it worked! Thanks a bunch!
No problem
I recently upgraded to ? and was disappointed to say the least so after looking around there are number of ways but all seem complicated so here is the easiest way which works for me
Flash at your own risk
My version P1640
1. Flash twrp recovery with flashtool or adb
2. Do a nandroid backup
3. Flash this http://rootjunkysdl.com/?device=Tegra Note 7&folder=Rom Stock 4.4.2-2.5
4.wipe dalvic etc then reboot
This rom is not compiled by me but is rooted
Lollipop is good but you need to tweak it to get it back to earth.
* Make sure your tablet is OEM unlocked. Then flash a sophisticated recover image version like TWRP. This will allow root-mode enabling via a patch.
* Put the tablet into fastboot mode and flash RootJunky's shared Lollipop restore image instead of the upgrade over the air (OTA). Good idea to erase particular partition before flashing.
* Boot to the recovery stage. Install latest zip SuperSu.zip using sideloader or having it already on a SD. This will enable root mode.
* Start system. Remove Apps from system partition unneeded, or that can be moved or installed to user directory instead. This frees up vital space. Example Lollipop only leaves a few megabytes left in the system partition after installation. Consider using Link2SD. Example get Google+, Google Play, Google Magazine, etc into the user partition and any other big App off your system parition. The system partition should only have important apps needed to be retained if a factory wipe is enacted.
* Then go through all your system settings make sure you tweak them to suit both power saving and your own desires.
* Use a startup tool like ES Task Manager to remove apps starting that don't need to be running from system boot.
* Install all Google Apps wanted. This can help to configure the system how it's meant to be.
* The system should now run smooth and use little battery.
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
With a bit of manipulation I replace the Launcher to Google's Now one.
e8hffff said:
Lollipop is good but you need to tweak it to get it back to earth.
* Make sure your tablet is OEM unlocked. Then flash a sophisticated recover image version like TWRP. This will allow root-mode enabling via a patch.
* Put the tablet into fastboot mode and flash RootJunky's shared Lollipop restore image instead of the upgrade over the air (OTA). Good idea to erase particular partition before flashing.
* Boot to the recovery stage. Install latest zip SuperSu.zip using sideloader or having it already on a SD. This will enable root mode.
* Start system. Remove Apps from system partition unneeded, or that can be moved or installed to user directory instead. This frees up vital space. Example Lollipop only leaves a few megabytes left in the system partition after installation. Consider using Link2SD. Example get Google+, Google Play, Google Magazine, etc into the user partition and any other big App off your system parition. The system partition should only have important apps needed to be retained if a factory wipe is enacted.
* Then go through all your system settings make sure you tweak them to suit both power saving and your own desires.
* Use a startup tool like ES Task Manager to remove apps starting that don't need to be running from system boot.
* Install all Google Apps wanted. This can help to configure the system how it's meant to be.
* The system should now run smooth and use little battery.
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
With a bit of manipulation I replace the Launcher to Google's Now one.
Click to expand...
Click to collapse
heads up just finished the lollipop stock rom here
1eyedmonster said:
I recently upgraded to and was disappointed to say the least so after looking around there are number of ways but all seem complicated so here is the easiest way which works for me
Flash at your own risk
My version P1640
1. Flash twrp recovery with flashtool or adb
2. Do a nandroid backup
3. Flash this http://rootjunkysdl.com/?device=Tegra Note 7&folder=Rom Stock 4.4.2-2.5
4.wipe dalvic etc then reboot
This rom is not compiled by me but is rooted
Click to expand...
Click to collapse
Thanks a lot!
LP 5.1 was a waste of time and resources. Apps freeze randomly (even after factory reset etc) and there are just better UI options in KK for now.
1eyedmonster said:
I recently upgraded to and was disappointed to say the least so after looking around there are number of ways but all seem complicated so here is the easiest way which works for me
Flash at your own risk
My version P1640
1. Flash twrp recovery with flashtool or adb
2. Do a nandroid backup
3. Flash this http://rootjunkysdl.com/?device=Tegra Note 7&folder=Rom Stock 4.4.2-2.5
4.wipe dalvic etc then reboot
This rom is not compiled by me but is rooted
Click to expand...
Click to collapse
Oh man! I flashed this on top of 5.1 LP as your instructions but now its in boot animation from ~11 minutes now! Any other formats had you done after flashing this over LP like factory reset from TWRP?
Fk me! I cant even get into recovery by poweroff+volume up!! It just switches off then boots back on and goes into the bootlogo powered by tegra. How do i atleast switch it off until something is figured out? Its just getting hotter and stuck on bootloop
How do I flash it back to 4.4?
nakulp said:
Oh man! I flashed this on top of 5.1 LP as your instructions but now its in boot animation from ~11 minutes now! Any other formats had you done after flashing this over LP like factory reset from TWRP?
Fk me! I cant even get into recovery by poweroff+volume up!! It just switches off then boots back on and goes into the bootlogo powered by tegra. How do i atleast switch it off until something is figured out? Its just getting hotter and stuck on bootloop
How do I flash it back to 4.4?
Click to expand...
Click to collapse
Last night I went into TWRP to fix permission since seemed like something was wrong with Lollipop and my TN7 went into a bootloop also. Couldn't get into recovery so I let the battery drain, recharged, and was finally able to get into TWRP. Flashed Tomsgt's 5.1.3 but before rebooting from TWRP it stated "No OS Installed! Are you sure you wish to reboot?" Of course I rebooted anyway and now the tablet is on but it's a blank screen. I hold the power button and the message "Power Off Device" does show up, so that's odd. Ended up flashing Stock-4.4.2-2.5 and it's finally back!!
Loved this tablet initially when it didn't stutter/lag so much, and I know the hardware is supposed to be more capable (other than the 1GB of ram). I don't game on it and don't do anything intensive. Don't understand why it would lag so much...
is this super-tool works with only evga tegra note???????
I have xolo play tegra note 7. I want to know that is this supertool will work with my xolo play tegra note 7 model p1640.. because this tool is for evga tegra note 7 so if anyone tried it then please help me...............
And i also want to know that my model is on lollipop and i want to downgrade this to kitkat... then can i use this tool( IF COMPATIBLE ) ?????????
All brands are the same
rahulsingla said:
I have xolo play tegra note 7. I want to know that is this supertool will work with my xolo play tegra note 7 model p1640.. because this tool is for evga tegra note 7 so if anyone tried it then please help me...............
And i also want to know that my model is on lollipop and i want to downgrade this to kitkat... then can i use this tool( IF COMPATIBLE ) ?????????
Click to expand...
Click to collapse
There are no differences between the brands, The only difference is the boot image and the name of the brand behind the device. the supertool will work with any brand (i think so) and if you use supertool to downgrade there should'nt be any issues (i think so i am not sure:angel
.
.
.
a message to all users reading the post there is a group on facebook named Nvidia Tegra Note so if you have any issues you can join that group everyone will try to answer that {Leave a Thanks if this Helped}
cant use this method
I'm having a little problem in here so can you please tell me which other methods can be use?
Thank you
Worked perfect
Please help how to remove Lollipop and install Kitkat in Xolo Tegra Note 7, just bought week back and really not happy with it so far.
Thanks for rply
First of all thanks for rply and i wanna tell you bro that after comment on xda i try to take risk and flash and downgrade with supertool and you know what supertool has xolo brand images cracked so nothing changed in my note after flash with supertool......
try to download and it says "You Shall Not Pass" and forces me back to the home page.
Can i flash this on my nvidia tegra note (xolo)
i want to downgrade my device
i want to downgrade my xolo p1640 ( tegra note tablet ) to android 4.4 , please someone help me. I am getting confused with several posts. please someone help me with steps so that i can downgrade my device. currently i have android 5.1 on it and not rooted .
Okay boys Just got this phone like a week ago. Used it to replace my Samsung that was acting up. Convinced my wife I needed it and then proceeded to toy with it.
I unlocked the bootloader, flashed custom recovery (TWRP latest), and rooted (Magisk latest) to stick recovery. I was running full stock 8.1.0 no custom ROM yet I was doing reading before I wan
ted to flash. Got to feeling comfortable so I got everything ready files downloaded USB hooked up and decided to be safe and make one more back up.
So thats what I did, I made a full TWRP backup, every single partition onto an external USB. So I am safe, right? Best to be safe... But that's when I rebooted from TWRP it boot looped.
So now I am currently stuck at boot. I get the warning screen about the unlocked bootloader then "Google" logo boot screen then a black screen and back to the start again. I knew that wasn't right, so I booted into fastboot with Power + Volume Down, cycled to recovery and selected it then... boot loop. No recovery. Hmmm... That's not good. But keep calm... did some research and found a few things. So i did this...
Heisenberg said:
FAQ can be found in post #3!
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
Click to expand...
Click to collapse
and that didnt work either so next I tried this
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
And that didn't work either. To be clear I left my bootloader unlocked. Each process works as far as flashing all the files via fastboot. But if I try to reboot or boot recovery, stock or custom, I boot loop. I have been looking everywhere and I dont see a solution and was hoping to get some help.
edit: Now I have also tried this... Doesnt seem to be the bootloop of death.
XCnathan32 said:
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 8/22: Android O is working with 4 Cores now! Big thank you to @xls654 for finding out how to get Android O to work.
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/25 - EX kernel for Android O added.
8/22 - Android O DPR6 boot.img and source added.
8/16 - Started making this fix open-source, source code section added in OP. Also uploaded modified Franco and Flash kernel & source.
8/10 - Added PA 7.2.2 and DarkROM boot images.
8/08, 2nd change - Uploaded modified boot.img for firmware 48C.
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img that only uses 1 core. Someone suggested I make a boot.img that only uses 1 core, just to see if it works for devices that didn't work with the 4 Core fix.
7/30 - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/29, 2nd change - Added Pure Nexus and PA dev version boot images, modified to use 4 cores, and utilize all 4.
7/29 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP.
7/21 - Fix created, stock boot.img, TWRP image, and EX kernel modified to use 4 cores.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 6P with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: With the new EX zip, you shouldn't need to flash the boot.img anymore, you can just flash twrp, and then flash EX in twrp.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from stock 6.17, 8.0 firmware: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. It also disables forced encryption as a bonus. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 48B, 7.1.2 firmware: Download |Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03: Download | Mirror. EX kernel 5.03 works with android 8.0.0. This zip applies the 4 cores patch, but you will need to flash it over an already modified boot.img to work.
Elemental X kernel version 4.12, universal zip: Download | Mirror. This zip is EX kernel, modified to use only 4 cores. Update: I modified it to apply the CPU utilization patch too, so now this is a universal zip, flash it over almost any ROM, and you should now have the BIG cores disabled fix, and the little core utilization fix.
Flash kernel version 2.5: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
Franco kernel r55: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
You will most likely not need these images. It will be much easier, and much more universal to flash one of the custom kernel zips above ^^^
PA boot.img from PA version 7.2.2, build 8/10: Download | Mirror. Uses only 4 cores, and has core utilization patch.
PA boot.img from PA version 7.2.1: Download | Mirror. Boot.img from PA dev preview 7.2.1, uses only 4 cores, and is modified to utilize 4 cores more effectively. Flash it after you flash the PA zip, either with fastboot, or TWRP image flash.
Pure Nexus boot.img from Pure Nexus 7/25 build Download | Mirror. This image is modified to use only 4 cores, and it has a tweak to utilize the 4 cores more effectively. Flash it after you flash Pure Nexus, either with fastboot, or TWRP image flash.
DarkROM boot.img from 7/21 build: Download | Mirror. This image is modified to use only 4 cores, and has the utilization patch.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Edit: seems not to help unfortunately. Here it is: Download | Mirror
Unfortunately, I have not been able to get Android O working yet, but I am working on it right now.
If you have a favorite custom ROM or kernel you want to ported over to use 4 cores, let me know, and I'll put it up.
*Source code:
Flash kernel: source | Flash ramdisk/AK2: source.
Franco kernel: source | Franco ramdisk/AK2: source.
Android O boot.img: source.
p-0000000000000000000000000000007 (sorry that was my kitten)
*Tested custom ROMS/kernels
I have used Pure Nexus by flashing the modified EX zip over it, it has notably better performance than the stock ROM, and very good battery life. It's a clean, stable ROM, with plenty of good features that are actually useful.
I have also used Paranoid android dev preview, very good performance, definitely my favorite as of now. Battery life leaves something to be desired, but I have not tried a custom kernel yet. Also, 7.2.1 seemed smoother to me than 7.2.2.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as I test more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
Turn resolution down to 1080p. On a small screen, the difference in between 1080p and 1440p is not very noticable. To do this, first get root access, then download a terminal emulator. In the terminal, type "su" and grant it root access, then type "wm size 1080x1920", and finally, change the density "wm density 400". Personally, I like my density at 400, but you can expieriment with it. Lower density=Smaller items and text, Higher density=Bigger items and text. Also @Adithya FRK mentioned that you also want to put density in build.prop so apps display correctly. Change ro.sf.lcd_density=560 to your density, if you changed it.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@tr1gg3r.man, He made the the PA kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@BeansTown106, He made the Pure Nexus kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@Dark_Eyes_, He made the DarkROM kernel, I just added a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@[U][COLOR="Purple"]The Flash[/COLOR][/U], He made The Flash kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work. His posts have also helped me a lot with learning how to build a kernel from source, understanding how to use git more, etc. I recommend you check them out if you are interested in getting started with android development.
@[B]franciscofranco[/B], He made Franco kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@xls654, He found out how to get Android O working with 4 cores.
FAQs
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are your device may have a different problem.
Does EX kernel have the new speed fix? - Yep, you can flash this over just about any ROM, and it should patch it to use only 4 cores, and use them well.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Click to expand...
Click to collapse
Please anybody if your willing to take a swing at helping me I would really appreciate it!
Thanks in advance!
Anybody have any insight?
Were you successful at returning to stock?
If not, I'm afraid you're suffering from the bootloop issue :'(
No i was not, but the standard 4 core fix isn't working for me either so I don't know what else to do.
I did something similar. Tried to update to latest may patch from custom rom. No sim found...so tried some radios..nothing. Thought I better get back to full stock. Similar to you tried the individual flashes and then the OTA as a whole. During that process I locked the bootloader. Now I get the yellow screen text says software isn't standard...then google logo...then the red text says os is corupt possibly...then google logo, forever. No loops it seems but just doesn't boot.
Anyone with thoughts?
i am on my 2nd 6p with the same problem after installing twrp. the first one i got operational by sideloading via twrp a factory img. to get the sideload to work i had to go back to android 6, 7 and 8 would not work. right now the google firmware site is not working, it has been out for a few days, so i have not been able to try it on the second 6p.
edit; now that i recall the factory img would not load after installing. i then went back to fastboot recovery and got the distress robot, twrp was of course gone. from there i did a factory reset which got me back to go and the long climb back to oreo.