This is the System, Boot and recovery image from the
KVT49L: XNPH19O firmware (newer than the update zip I posted)
Recovery: http://www.androidfilehost.com/?fid=23487008491963229
Boot: http://www.androidfilehost.com/?fid=23487008491963228
System: http://www.androidfilehost.com/?fid=23487008491963261
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
Can you post up a picture of the recovery? I would like to see which it is.
Harfainx said:
Can you post up a picture of the recovery? I would like to see which it is.
Click to expand...
Click to collapse
It's the oppo esque one lol
We already got twrp working.. Hehe Dees_Troy said the recovery had references to oppo all in it (not surprising)
Sent from my One using Tapatalk
graffixnyc said:
It's the oppo esque one lol
We already got twrp working.. Hehe Dees_Troy said the recovery had references to oppo all in it (not surprising)
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Let's start calling it what it really is:
The Find 7 OnePlus Edition, aka find7op
Updated the OP with the System.img
That's quick guys.. Thanks!
What would happen if i would flash it on my oppo7? I will try...
Gesendet von meinem X9006 mit Tapatalk
Entropy512 said:
Let's start calling it what it really is:
The Find 7 OnePlus Edition, aka find7op
Click to expand...
Click to collapse
Will you work on the OnePlus? TIA
Inviato dal mio Nexus 4 utilizzando Tapatalk
m3dd0g said:
What would happen if i would flash it on my oppo7? I will try...
Gesendet von meinem X9006 mit Tapatalk
Click to expand...
Click to collapse
So I take it you didn't have much luck, since you didn't post "ZOMG, it works!!! I got it working on my oppo 7!!!"???
How to enter system recovery
graffixnyc said:
This is the System, Boot and recovery image from the
KVT49L: XNPH19O firmware (newer than the update zip I posted)
Recovery: http://www.androidfilehost.com/?fid=23487008491963229
Boot: http://www.androidfilehost.com/?fid=23487008491963228
System: http://www.androidfilehost.com/?fid=23487008491963261
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
Click to expand...
Click to collapse
The zip is flash? The equipment is suppose root, right. How to enter system recovery? You have to install a custom recovery? Have the option to install from the internal memory zip files? Wipe cache is needed?
I'm on the official Portuguese forum Opo, we have two facilities in Portugal and start by yourself these questions. I'm noob and would like to know to pass information. obg
Manholas said:
The zip is flash? The equipment is suppose root, right. How to enter system recovery? You have to install a custom recovery? Have the option to install from the internal memory zip files? Wipe cache is needed?
I'm on the official Portuguese forum Opo, we have two facilities in Portugal and start by yourself these questions. I'm noob and would like to know to pass information. obg
Click to expand...
Click to collapse
Hi,do you have dump files for 64G ? I flash the dump file on your pose my 64G OPO becomes 16G OPO...
pls del
ailai55 said:
Hi,do you have dump files for 64G ? I flash the dump file on your pose my 64G OPO becomes 16G OPO...
Click to expand...
Click to collapse
I'm not sure how the partitions are set up with this device, but I assume since there is no SD card, it SHOULD be similar to a nexus. That being ASSUMED maybe this thread will shed some light for you. I have this issue on my nexus 4 all the time, and we also have variants based on storage size. The only difference among them is the storage partition's size, and all factory images are identical...meaning we don't have an 8gb factory image and a 16gb factory image. So I'm assuming this is the same case here....that would mean whatever happened isn't as a result of the images themselves, but rather an issue with the device just like with a Nexus 4. So this method may actually work for you. I'd strongly recommend using caution about the method involving deleting partitions via terminal, however...pay attention to the one that details using stock recovery. (with nexus devices, doing a factory reset with stock recovery will wipe the ENTIRE device, including the internal storage partition...FYI )
http://forum.xda-developers.com/nexus-4/general/how-to-fix-internal-storage-16gb-8gb-t2033692
hp420 said:
I'm not sure how the partitions are set up with this device, but I assume since there is no SD card, it SHOULD be similar to a nexus. That being ASSUMED maybe this thread will shed some light for you. I have this issue on my nexus 4 all the time, and we also have variants based on storage size. The only difference among them is the storage partition's size, and all factory images are identical...meaning we don't have an 8gb factory image and a 16gb factory image. So I'm assuming this is the same case here....that would mean whatever happened isn't as a result of the images themselves, but rather an issue with the device just like with a Nexus 4. So this method may actually work for you. I'd strongly recommend using caution about the method involving deleting partitions via terminal, however...pay attention to the one that details using stock recovery. (with nexus devices, doing a factory reset with stock recovery will wipe the ENTIRE device, including the internal storage partition...FYI )
http://forum.xda-developers.com/nexus-4/general/how-to-fix-internal-storage-16gb-8gb-t2033692
Click to expand...
Click to collapse
Thank you for your detailed instruction. I'm afraid I would just stay for 16G for now and wait for the OTA from Cyanogen. Hope it will resolve this issue.
btw,do you have your OPO already?
ailai55 said:
Thank you for your detailed instruction. I'm afraid I would just stay for 16G for now and wait for the OTA from Cyanogen. Hope it will resolve this issue.
btw,do you have your OPO already?
Click to expand...
Click to collapse
No, I wish!!
No partition
hp420 said:
I'm not sure how the partitions are set up with this device, but I assume since there is no SD card, it SHOULD be similar to a nexus. That being ASSUMED maybe this thread will shed some light for you. I have this issue on my nexus 4 all the time, and we also have variants based on storage size. The only difference among them is the storage partition's size, and all factory images are identical...meaning we don't have an 8gb factory image and a 16gb factory image. So I'm assuming this is the same case here....that would mean whatever happened isn't as a result of the images themselves, but rather an issue with the device just like with a Nexus 4. So this method may actually work for you. I'd strongly recommend using caution about the method involving deleting partitions via terminal, however...pay attention to the one that details using stock recovery. (with nexus devices, doing a factory reset with stock recovery will wipe the ENTIRE device, including the internal storage partition...FYI )
http://forum.xda-developers.com/nexus-4/general/how-to-fix-internal-storage-16gb-8gb-t2033692
Click to expand...
Click to collapse
The total storage capacity of the opo is the primary partition. Let's have a primary partition of 64GB. There are no divisions partitions.:good:
How can i install this files ?
sebfar said:
How can i install this files ?
Click to expand...
Click to collapse
Use fastboot commands:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
When i flash system.img, i have error : data too large
Envoyé de mon A0001 en utilisant Tapatalk
sebfar said:
When i flash system.img, i have error : data too large
Envoyé de mon A0001 en utilisant Tapatalk
Click to expand...
Click to collapse
Size limit for flashable files? Did you resolved this? Also how to put one into fastboot mode??
Related
As the Topic Suggest is there any guide someone made for noobs like me
who wanna upgrade there NEXUS 7 to 4.2.2 having Custom kernel without loosing data ?
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you don't have to wipe anything. Just flash and go!
scream4cheese said:
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you won't have to wipe anything. Just flash and go!
Click to expand...
Click to collapse
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
1) make a full nandroid (cwm/twrp) backup
2) flash a 4.2.2 stock-derived ROM on top of existing ROM - no wipe
2.5) flash a minimal root kit (SuperSU or Superuser) if not in ROM in step 2 - no wipe
3) flash the same kernel you used previously - no wipe
4) profit!
No workie? Restore backup from step # 1 and try something else.
pleasant said:
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
There's no need to do that. But in spite of it, I can tell you that you can just create the nandroid backup and leave it in your device. Don't pull it out. Just flash the download in my previous post and if anything goes wrong. Enter recovery mode and restore your system. Even if you did pull the nandriod backup file from the N7 and the device fails to boot up, you cant just put the file back in to restore it that way. It won't mount so you can access the internal storage system.
P.S i don't know how to make the backup show up but i think there are a few thread here that some people have found a solution to it.
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Click to expand...
Click to collapse
I have had TWRP behave the same way - sometimes it will put backups in
/data/media/TWRP/...
and sometimes in
/data/media/0/TWRP/...
It is a bit of a mystery what causes this to happen. Strangely, when there is a folder in the first location, TWRP (2.4.1.0) will not find the second one. But, if I manually move the files from the first location (/data/media/TWRP) to the second location (/data/media/0/TWRP) using a file manager, then TWRP will find the backups no problem.
well, the "sdcard" mount point ( == /data/media/0/ ) is the thing that shows up on the PC via MTP mode, so I would just move the files to the second location. I'm not sure if CWM behaves the same way, but you will certainly be able to copy them from the N7 to the PC at that point.
good luck.
pleasant said:
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
Click to expand...
Click to collapse
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
scream4cheese said:
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
Click to expand...
Click to collapse
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
pleasant said:
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
Click to expand...
Click to collapse
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
boot(basically kernel) and system are usually what people mean 'custom ROM'. So if you just manually flash these two things(and usually need to be done together), none of your 'data' would be lost.
So just find these two images (usually .img) in whatever custom ROM you want and flash it.
This is the unix convention for a long long while and android is just linux
scream4cheese said:
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
Click to expand...
Click to collapse
So if there is a flashable zip available that would be great
Sent from my Nexus 7 using Tapatalk HD
you don't really need to flash bootloader
chimpanzeexda said:
you don't really need to flash bootloader
Click to expand...
Click to collapse
Yeah, I told him that.
Sent from my Nexus 7 using Tapatalk HD
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hi bro can you provide me the similar flashable zip for android 4.3 for nexus 7 wifi
Sent from my Nexus 7 using Tapatalk HD
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Soundtallica said:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Click to expand...
Click to collapse
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Soundtallica said:
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Click to expand...
Click to collapse
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's easier to just flash all of the images (except userdata) top to update, rather than flashing two and then messing around with OTA.
So is there anyway to flash the update without losing my data/apps??
Thanks!
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you very much!
Enviado de meu Nexus 6P usando Tapatalk
Step 9, right @Heisenberg ?
joooe said:
Step 9, right @Heisenberg ?
Click to expand...
Click to collapse
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
mystertom said:
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
Click to expand...
Click to collapse
Can you provide a screenshot of your attemp to flash the recovery? Also you might want to try opening the command prompt as administrator, right click on the command window in start menu and select open as administrator.
Heisenberg said:
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
Click to expand...
Click to collapse
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
joooe said:
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
Click to expand...
Click to collapse
Where did you say that? I know that wiping data will remove apps, but it's the right way to go about it to ensure no problems occur.
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
It all went after this post.
But no problem.
joooe said:
It all went after this post.
But no problem.
Click to expand...
Click to collapse
Surely you were aware that wiping data was going to remove your apps? So all you needed to do was back them up first and restore them after you flashed. Apologies if I should have made that clear in my previous posts.
No problem. It was my stupid mistake.:good:
fastboot flash bootloader bootloader-angler-angler-02.45.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
sleep 5
fastboot update image-angler-mmb29v.zip
Normally in the last line there is an option "-w" this wipes the data.
Don't do that and modify the script so the option is gone, like I did.
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Soundtallica said:
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Click to expand...
Click to collapse
Don't install it, it'll fail, you must flash the factory images. Each command is entered individually (press enter key to send the command), wait for flash to finish then enter the next command.
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
I recently, yesterday, flashed a 7.1 from to my phone. Actually both that at available, and both times I am getting this error message on boot. I'm not sure what I'm doing wrong. Phone seems to run well though. Help? Thanks!
It's in the attachment
I'd be curious to know aswell..
Sent from my ONE A2003 using Tapatalk
I had this same issue awhile back but somebody told me what to do and it went away..
For the life of me I can't remember what it was .
I'm thinking it had something to do with Vendor but can't remember
Sent from my Pixel XL using Tapatalk
Did you update the vendor image after flashing the ROM?
wwe9112 said:
I recently, yesterday, flashed a 7.1 from to my phone. Actually both that at available, and both times I am getting this error message on boot. I'm not sure what I'm doing wrong. Phone seems to run well though. Help? Thanks!
It's in the attachment
Click to expand...
Click to collapse
Just flash the vendor image to the corresponding build. Ex: build NBD90X needs the NBD90X vendor image and so on. Should resolve the issue.
BIGSAMDA1ST said:
Just flash the vendor image to the corresponding build. Ex: build NBD90X needs the NBD90X vendor image and so on. Should resolve the issue.
Click to expand...
Click to collapse
Now I'm stuck elsewhere, I decided to do a full flash -_-. I formatted everything not thinking and now I have no rom on my device. I think I am stuck. Is there a way to transfer a rom to my device? I used TWRP to format my device.
Boot into fastboot mode, unlock the bootloader, and flash the latest factory image...
https://developers.google.com/android/images?hl=en
redduc900 said:
Boot into fastboot mode, unlock the bootloader, and flash the latest factory image...
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Fastboot just says to connect a USB Cable but it's connected. I have drivers installed. I don't have a rom obviously to enable USB debugging -_-.
If u have TWRP just boot to recovery then plug in the phone to computer and a window will pop up showing Internal Storage and jus copy a ROM/Gapps/Vendor to Internal Storage and then select Install and flash away.
Sent from my Pixel XL using Tapatalk
scoot0073 said:
If u have TWRP just boot to recovery then plug in the phone to computer and a window will pop up showing Internal Storage and jus copy a ROM/Gapps/Vendor to Internal Storage and then select Install and flash away.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I got it! I had to use another pc for some reason; my main pc wasn't recognizing it but my laptop did -_-. Anyway, where do I find the vendor image? Also how do I flash that, I remember a while back I found one and went to flash it and there was several radio buttons on where to flash it. I don't want to screw this up lol.
Thank you so much.
Post#2 on first page
(How to install a ROM)
Read it more easier than me typing it all out..haha
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Pixel XL using Tapatalk
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards
demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!
hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.
goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.
zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse