How to flash a factory image | Return to stock | Unroot your Nexus 6P
Hello Nexus 6P Users!
This tutorial will show you how to reset/unroot/save your Nexus 6P by flashing the Google Factory Images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC and Linux users: simply follow these instructions:
http://forum.xda-developers.com/showthread.php?t=2638673
Off-topic: installing ADB and Fastboot so easily, what a time to be alive!
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#angler
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already). Only follow step 1 from this thread:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Flashing the factory images
There is more than one way to flash these images. Each give the same results, but the first is for lazy (or smart) users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case first one does not work)
★Extract the image-angler-xxxxxx.zip from the previously extracted folder somewhere easy to access (On C:\images for example. Make it easy to type). You will have the following files:
★In the new folder, from the original archive/folder, extract "bootloader-angler-angler-XX.XX.img" (rename it to bootloader.img) and "radio-angler-angler-XX.XX" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:/images/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/images/radio.img
fastboot reboot-bootloader
fastboot flash system C:/images/system.img
fastboot flash vendor C:/images/vendor.img
fastboot flash userdata C:/images/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/images/boot.img
fastboot flash recovery C:/images/recovery.img
fastboot erase cache
fastboot flash cache C:/images/cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
And now you have a brand new Nexus 6P (software wise, at least). Congratulations!
Credits and Thanks:
@Mr hOaX
Got some fastboot command "updates" from you
@Heisenberg
Really cool root tutorial
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
abaaaabbbb63 said:
Credits and Thanks:
Mr hOaX
Got some fastboot command "updates" from you
Heisenberg
Really cool root tutorial
Click to expand...
Click to collapse
Nice to see you here bro
Good job
This guy's tutorial will really save your nexus for sure
gd6noob said:
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
Click to expand...
Click to collapse
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
abaaaabbbb63 said:
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
Click to expand...
Click to collapse
Followed the instructions and im getting an error cant find the files
joeyac02 said:
Followed the instructions and im getting an error cant find the files
Click to expand...
Click to collapse
Can you describe what exactly did you do?
At which point did you encounter the error?
When I download the images it doesn't contains Angler-bootloader and Radio.img. It only contains one file with the boot.img, etc... I tried downloading all the 6.0.0 link and it's all the same . I don't understand.
Thank you for the post. Hope I don't need to use it tho. :good:
I cannot make phone calls through the phone app?
I followed directions step by step but every time I get to the dead android guy and hold vol up + pow. I do not get the "stock" recovery where I could choose to data/factory reset, I just get the little dead android guy again.
Any help?
Nice guide
Sent from my Nexus 6P using Tapatalk
From Heisenberg post says that
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have.
Click to expand...
Click to collapse
And I have 64gb of storage. should I wipe or flash?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
You can do both. Just in case, your storage spaces shows reductions after flashing (Like my 64GB variant shows 32 GB), you can fix it by wiping data from stock recovery.
If you're not willing to remove the data on your internal storage, you can skip flashing userdata.img.
tried to go back to stock but stuck on google logo..what to do?
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you flash the the correct vendor.img, corresponding to your factory image?
DJBhardwaj said:
Did you flash the the correct vendor.img, corresponding to your factory image?
Click to expand...
Click to collapse
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
jordy787 said:
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
Click to expand...
Click to collapse
Vendor.img is already included in the factory image. If you used flash-all.bat script, it must have been flashed. What commands did you precisely use to flash the factory image?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
Don't ever flash it. It has no benefit and only causes problems. If you need to wipe your storage use this command:
Code:
fastboot format userdata
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Heisenberg said:
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Click to expand...
Click to collapse
I used the wug tool kit and it worked
Related
Hey im new to all this but i wanted to have the pure Android on my one x+.
I have rooted the phone etc etc and i went to install this kernal and rom: http://forum.xda-developers.com/showthread.php?t=2057920
After the reboot it just gets stuck on a screen saying "INITIATING SWAGGER" as shown below. I have no idea what to do from here how to restore it or install a working rom?
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for the help
Still not working, help please??? :/
LynchyY said:
Still not working, help please??? :/
Click to expand...
Click to collapse
You need to flash Gapps (20121212) as well.
Or you can wrote down your step, then more easier to known your problem.
xdacalvien said:
You need to flash Gapps (20121212) as well.
Or you can wrote down your step, then more easier to known your problem.
Click to expand...
Click to collapse
I am on the screen at the moment saying "Android is upgrading..." "Starting apps."
It has been on this screen now for about half an hour.
I have flashed gapps already although i may have done the wrong one but how can i get the one you just linked me onto my phone when its not even booting properly?
Thanks.
LynchyY said:
I am on the screen at the moment saying "Android is upgrading..." "Starting apps."
It has been on this screen now for about half an hour.
I have flashed gapps already although i may have done the wrong one but how can i get the one you just linked me onto my phone when its not even booting properly?
Thanks.
Click to expand...
Click to collapse
You need to go back the Recovery mode and flash the gapps..
Turn off your phone, Hold down the Volume Key (-) and press Power button to boot into bootloader.
This is quick step for you:
Installation:
install kernel
full wipe
flash rom
flash gapps
reboot into rom
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel
xdacalvien said:
You need to go back the Recovery mode and flash the gapps..
Turn off your phone, Hold down the Volume Key (-) and press Power button to boot into bootloader.
This is quick step for you:
Installation:
install kernel
full wipe
flash rom
flash gapps
reboot into rom
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel
Click to expand...
Click to collapse
Hey, thanks for the reply, can you give me a link to where i can find/download the kernel i need to flash?
Thanks
LynchyY said:
Hey, thanks for the reply, can you give me a link to where i can find/download the kernel i need to flash?
Thanks
Click to expand...
Click to collapse
Your need to go back ur ROM.zip file, and extract the boot.img. That is your boot.img... Any ROM got own boot.img.
So you not flash yet your BOOT.IMG.
xdacalvien said:
Your need to go back ur ROM.zip file, and extract the boot.img. That is your boot.img... Any ROM got own boot.img.
So you not flash yet your BOOT.IMG.
Click to expand...
Click to collapse
Yes but how do I install the kernel? what kernel do i install?
LynchyY said:
Yes but how do I install the kernel? what kernel do i install?
Click to expand...
Click to collapse
The Kernel here is means boot.img.
LynchyY said:
Yes but how do I install the kernel? what kernel do i install?
Click to expand...
Click to collapse
You'll need to open the zip file of the ROM you've flashed and find the boot.img contained within. Then use Hasoon's AIO Toolkit for HOX+ to flash the kernel (the bottom left option).
For some more information, the boot.img contains the kernel and the ramdisk for the device and is flashed to the boot partition of the device. Because the HOX+ is still S-OFF, we cannot flash the ROM and kernel together. We must flash the kernel (boot.img) separately using a utility called fastboot; the toolkit automates this process.
xdacalvien said:
The Kernel here is means boot.img.
Click to expand...
Click to collapse
Ok but how do i install the kernel if my pc is not even recognizing my phone?
Sorry for being a noob but i really don't want to break up my phone more than it already is.
Thanks.
LynchyY said:
Ok but how do i install the kernel if my pc is not even recognizing my phone?
Sorry for being a noob but i really dont want to **** up my phone more than it already is.
Thanks.
Click to expand...
Click to collapse
check the post #10, go to use the Hasson's AIO Kit to flash is more easier.
you need to install HTCDriver.exe from Hasson's AIO Kit.
xdacalvien said:
check the post #10, go to use the Hasson's AIO Kit to flash is more easier.
you need to install HTCDriver.exe from Hasson's AIO Kit.
Click to expand...
Click to collapse
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
LynchyY said:
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
Click to expand...
Click to collapse
Try to re-plug in the USB and test.
LynchyY said:
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
Click to expand...
Click to collapse
If the toolkit is not working, you'll need to do it manually I suppose.
1. Find the folder in the toolkit that contains fastboot.exe and navigate to that folder in a command prompt.
2. Hold the power and volume down buttons until your phone reboots into a white screen.
3. Connect it by USB if it isn't already and type "fastboot devices" and ensure that your device is listed (will just be a string of letters and numbers).
4. Once that works, type "fastboot flash boot path/to/boot.img" (I would recommend putting the boot.img in the same folder as fastboot.exe to make things easier on yourself).
5. If that command is executed successfully, run "fastboot reboot" if your device hasn't already rebooted.
xdacalvien said:
Try to re-plug in the USB and test.
Click to expand...
Click to collapse
Done that and nothing, my pc never recognizes the phone unless it is booted into android.At this point i can only get into the bootloader and recovery mode.
NasaGeek said:
If the toolkit is not working, you'll need to do it manually I suppose.
1. Find the folder in the toolkit that contains fastboot.exe and navigate to that folder in a command prompt.
2. Hold the power and volume down buttons until your phone reboots into a white screen.
3. Connect it by USB if it isn't already and type "fastboot devices" and ensure that your device is listed (will just be a string of letters and numbers).
4. Once that works, type "fastboot flash boot path/to/boot.img" (I would recommend putting the boot.img in the same folder as fastboot.exe to make things easier on yourself).
5. If that command is executed successfully, run "fastboot reboot" if your device hasn't already rebooted.
Click to expand...
Click to collapse
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
LynchyY said:
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
Click to expand...
Click to collapse
try" fastboot erase cache "
then " fastboot flash boot boot.img " again.
Remember, the boot.img is extract from the ROM.zip and put to the path same as fasboot.exe
LynchyY said:
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
Click to expand...
Click to collapse
ahh after this i tried again and the error was Low Battery so I will retry after charging my phone for a while.
Thanks again. I will let you know how it goes.
LynchyY said:
ahh after this i tried again and the error was Low Battery so I will retry after charging my phone for a while.
Thanks again. I will let you know how it goes.
Click to expand...
Click to collapse
After you haved success, you will become Member at this forum. FTW ~~~
How is now with your phone ?
Dell has updated their open source site with the developer files for the Lollipop update for the Venue 8 7840:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
This includes the kernel source, a guide Doc, and a "blankphone" image which will re-partition the device and leave it in the fastboot interface OS and wait for a system image to be flashed. It does not erase or provision a system image or boot image. The documentation mentions a separate "fastboot" image paired with the "blankphone" image, and traditionally (based on files posted by other OEMs) the "fastboot" zip is what contains the OS images. So hopefully (maybe?) they will be posting that at some point. We should be able to get images pulled off working devices for people to flash.
This "blankphone" zip should function as an "unbrick" and put a mis-flashed device back into a functioning (flashable) state, but you may end up without an OS. (This is why I called it "partial" unbrick, because you won't have a brick but you won't necessarily have a booting-to-Android device either.)
ALSO A WARNING: This should be all fine and good but proceed with caution.
I have flashed the IFWI-only.xml and successfully booted back to Android.
The zip file can be flashed with Phone Flash Tool Lite, available here from Intel for Windows and Linux.
There is a "Flash file" selector in Phone Flash Tool.
To unbrick and format, use the file: flash-DDO_BB.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To just flash the unlocked bootloader firmware, use the file: flash-IFWI-only.xml
DO NOT use the EraseFactory xml; I'm not certain but I think there are DRM keys in the /factory partition, and you could permanently break things like Netflix if you erase it.
Since mine is currently useless, I may as well try this. Will the image you uploaded here work?
Don't have access to the tablet at the moment but I'll try when I get in (couple of hours).
I know @wirebook tried on the older bootloader and failed but not harm in trying with this new stuff I suppose...
That system.img doesn't flash I think... Though it sounds like it's just an issue of repacking it somehow.
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
wonglynn2004 said:
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
Click to expand...
Click to collapse
Windows is unlikely, as it would require additional drivers and a custom bootloader OS to be created, among other issues. Linux may be possible though.
I've managed to unbrick my device, but I'm honestly not sure how.
So using the intel flash tool, I used the option flash-DDO_BB.xml, understanding that it would wipe the device (erase system, repartion, etc). I then had access to fastboot. From fastboot I attempted to flash the system.img @xBIGREDDx uploaded, obviously that failed with the sparse image header issue.
Next I converted the system.dat.new in the OTA to a system.img, attempted to flash that from fastboot, no go.
I decided it might be a good idea to flash the boot.img from the OTA, so I did that. Ended up on the original Dell/Intel boot animation (progress?). This seemed to infinitely bootloop (however maybe I was just impatient?).
I then booted CWM using the temp. recovery method (T4), wasn't able to do much at all, most directories were empty and nothing was mountable. Rebooted the tablet once more, went to get a drink and it's booted into Lollipop!?
I'm both confused and pleased... Can anyone shed any light?
anggusss said:
I'm both confused and pleased... Can anyone shed any light?
Click to expand...
Click to collapse
Hahaha not sure, maybe the reboot caused it to process the update again? The OTA may have been in the cache still.
Update: I have looked at the xml files and it turns out they are not erasing the boot or system partitions after all. That has been the standard procedure in the past so I didn't think to check. They are, however, wiping the data partition, and they wipe the cache twice. Maybe they've been reading XDA too much?
Ah I see. So if my system was never wiped, I assume flashing the new boot.img from fastboot is what kicked it into life.
I probably should have posted somewhere that I wrote a second query to Dell and heard back from someone in Legal six days ago stating that they were going to go bug the team and get the images posted online. They promised to follow up- never did- but looks like the rest of you were a lot more diligent in checking out the open source repository.
Anyway, the tablet I was working on belonged to a family member now living in a different city. Seems like we've figured out more or less how to unbrick this thing, so that's fantastic! I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
wonglynn2004 said:
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
Click to expand...
Click to collapse
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
anggusss said:
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
Click to expand...
Click to collapse
Yes, it was the developer unlock firmware that broke the OTA, not rooting. With the new Lollipop boot firmware, I think even if it's the unlocked firmware we should be good moving forward.
If you still want to unroot, there should be a menu option in SuperSU, it's like "cleanup" or something.
wirebook said:
I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
Click to expand...
Click to collapse
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
xBIGREDDx said:
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
Click to expand...
Click to collapse
Thank you so much for posting that! I'll attempt to walk my father through the process this weekend.
Stuff wasn't quite working right for me, the screen was turning on randomly, reboots took a ridiculously long time, and a few other things. Decided that it may be better to start with a fresh system partition.
Tried converting both the system.img from @xBIGREDDx and the one from the lollipop OTA to sparse imgs and flashing, however I'm getting
FAILED (remote: flash_cmds error!
When I try to flash system, during the write stage. I'd like to think they're correct sparse images since fastboot reads and sends them to the device.
If I look at the tablet screen during the flash, it complains of an "Unknown chunk type" before failing.
I can get to the default recovery and fastboot, I just don't seem to be able to flash something to my now empty system partition from fastboot...
EDIT: Managed to flash system through the tethered recovery, but I'm still met with a black screen on regular boot.
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
anggusss said:
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Click to expand...
Click to collapse
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
wirebook said:
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
Click to expand...
Click to collapse
Sorry, I could have been clearer.
The steps I performed:
First, booted to fastboot
Trigger the tethered recovery (T4)
Once in the recovery, I then formatted /system using the graphical menu. (Probably not necessary since we're DDing the img directly?)
I had a microsd card in the device which was EXT4 formatted, so I pushed the system.img to that after mounting it by hand.
Code:
mount -t ext4 /external_sd /dev/block/mmcblk1p1
Then from the PC side
Code:
adb push system /external_sd/system.img
You could probably push to the data partition if you can get it mounted in the event you don't have a microsd.
Once you have the system.img on the device, you can dd it onto the system partition
Make sure /system is unmounted
Code:
umount /system
dd if=/external_sd/system.img of=/dev/block/by-name/system
NOTE: /dev/block/by-name/system may be wrong, I'm going from memory. I'll correct it when I get in from work.
After flashing system, reboot to fastboot again
Code:
adb reboot fastboot
And finally flash the boot.img from the OTA zip I uploaded
Code:
fastboot flash boot boot.img
Perform a normal boot, and it should be working. First boot takes a while, 3-4 minutes.
anggusss said:
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
Click to expand...
Click to collapse
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
xBIGREDDx said:
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
Click to expand...
Click to collapse
I did try that quite a few times but no luck. I just seem completely unable to boot straight into fastboot. I either have to reboot to it using ADB or use the flashtool. Not necessarily a problem, just an inconvenience.
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition.
The new Twrp is out now 3.0.0-1 HERE
Let me know if this helps guys and gals.
jerflash said:
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition. This never happened to me before so it must be something in the new bootloader image or boot image that is causing this.
Does anyone else see this? I was going to test downgrading the bootloader later on today to see if the block is gone but it looks like the "default password" for encryption may have changed.
Let me know guys.
Click to expand...
Click to collapse
New TWRP test builds already out there that take care of the issue.
rebretz000 said:
New TWRP test builds already out there that take care of the issue.
Click to expand...
Click to collapse
yes i see that and i am going to flash it now. i had to read through that whole thread though. i will post it above for others.
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Awesome test build! It works like a charm
havanahjoe said:
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Click to expand...
Click to collapse
this happens because you booted into Android before flashing SuperSu or disabling the recovery-from-boot
when you flash the last item, in my case it was vendor.img, i clicked volume down on my phone, and went into recovery. i then selected SuperSu2.68 and flashed that. Then rebooted.
chaco81 said:
this happens because you booted into Android before flashing SuperSu
Click to expand...
Click to collapse
That would explain it. I didn't know SuperSu took care of this. Thank you
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Yes. I use the same version.
allen099 said:
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Click to expand...
Click to collapse
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
mickyw1980 said:
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
This allows you to keep encryption?
jerflash said:
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
floepie said:
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
Click to expand...
Click to collapse
That may be true but if you don't know to do that it will wipe everything. Just always been safer to do it individually.
Sent from my Nexus 6P using Tapatalk
gts24 said:
This allows you to keep encryption?
Click to expand...
Click to collapse
Looks like it does. Is there another way to tell?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using Tapatalk
I always flash system, boot, vendor through fastboot. Sometimes I also update the bootloader and the radio if there is a newer version available. All other IMG files are not necessary. It´s true that flashing the stuff one by one gives you more control ( and a dirty flash is also great for lazy guys like me who want to keep all their Apps, settings etc. ).
johnny2678 said:
Looks like it does. Is there another way to tell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just followed your flow chart , worked here as far as I can tell as well. (proper thanks button clicked )
When I flashed this morning and entered TWRP recovery it must of tripped something as the yellow "cannot check for corruption" warning changed to a red "Your device is corrupt" message. It still only shows for a few seconds before booting like normal. I can't really try anything until I get home, but will flashing the patched TWRP and booting into it be enough to change that back to the old yellow warning? Or do I need to reflash the system/boot packages again?
Hi all,
For those who don't know, I'm known for rooting HMD Nokia Android Phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So after few hours testing, I finally found out how to root it.
Note, I've only dumped stock ROM from Verizon Wireless Variant as it's the only variant I've obtained so far. For non-operator variant and AT&T variant, I need your help for firmware dumping in case you want to restore your phone back to factory original state or OTA update if possible.
Known working build: H1A1000.010ho.01.01.01r.109
Procedure is pretty regular.
Step 1: Unlock the bootloader
Unlike HMD Nokia Android Phones, bootloader unlock is straight forward.
Just enable OEM unlocking in developer options, reboot your phone to Fastboot mode and unlock the bootloader with following command:
Code:
fastboot flashing unlock
Then confirm unlock on the phone.
As I've always recommended for HMD Nokia Phones, you should do critical unlock as well:
Code:
fastboot flashing unlock_critical
Then confirm unlock on the phone.
Strange enough, this phone doesn't have unlock warning after unlocked. Not sure about open market release or AT&T Variant.
Step 2: Install Magisk Manager and allow storage permission
You can download it from Magisk release topic or https://github.com/topjohnwu/magisk/releases
Step 3: Reboot to fastboot mode and flash patched boot image
You can download required patched boot image and representative stock boot image from here: https://www.androidfilehost.com/?w=files&flid=297410
For Verizon Variant that available with build "H1A1000.010ho.01.01.01r.109" so far, download "H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img". You can check software version yourself if correct.
The command is straight forward too:
Code:
fastboot flash boot /path/to/H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img
If you use Platform tools from Google officially, you needn't to care about your current slot actually.
Now reboot your phone:
Code:
fastboot reboot
Step 4: Restore stock boot image and reinstall Magisk (For OTA update ability although no update for months)
After your phone booted, enable USB debugging and copy the file "H1A1000.010ho.01.01.01r.109-boot.img" you downloaded along with patched boot image. I would assume you copied it to root directory of internal storage.
So execute following ADB commands:
Code:
$ su
(Confirm Root permission on the phone)
# getprop ro.boot.slot_suffix
If it returns a, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_a
If it returns b, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_b
Then open Magisk Manager on your phone, tap no thanks if it asks for extra modules, then tap "Install" at the right of Magisk version, choose "Direct Install", and wait for the procedure complete.
If installed successfully, you can reboot your phone on Magisk Manager now.
That's it!
At least this phone will work with Treble GSI build, so you should have idea about how could I dump the phone.
For Treble GSI report, read this: https://github.com/phhusson/treble_experimentations/wiki/Red-Hydrogen-One
For those who want to know how I dumped the phone:
Well, I found the phone could support Treble GSI and received update before.
So if your current slot is B, you definitely want to give it a try.
1. Unlock the bootloader
2. Download AOSP 8.1 Treble GSI from @phhusson 's repo:
https://github.com/phhusson/treble_experimentations/releases
In my case I chose system-arm64-ab-gapps-su.img.xz one
3. Enter fastboot mode and flash the image
Please check current slot as well
Code:
fastboot getvar current-slot
I would assume your current slot is B in this case.
Code:
fastboot flash system /path/to/system-arm64-ab-gapps-su.img
fastboot erase frp
4. Use volume key to choose "Reboot to recovery" then press power key to confirm
Press power key and volume up key to get the menu if "No command" appears, then choose "Wipe data/factory reset" to erase userdata storage.
Then reboot the phone.
5. After the phone booted, finish Setup Wizard.
6. Dump the boot image
Code:
adb shell
$ su
(Confirm root permission on the phone)
# dd if=/dev/block/bootdevice/by-name/boot_b of=/storage/emulated/0/stock_boot.img
# exit
$ exit
adb pull /storage/emulated/0/stock_boot.img
adb reboot bootloader
7. Switch to previous version, do factory reset
Code:
fastboot --set-active=a
Reboot to recovery and perform factory reset.
8. Reboot to normal OS and accept OTA update.
9. Use Magisk to patch the boot image you dumped, then root it with your patched boot image, or you can upload it if possible.
10. You can dump other partitions as well if you want.
Reserved 2
How to unlock the titanium alloy version?
great man! but H1T1000 ？How to unlock the titanium alloy version? Which one does boot. img use?
mavitz said:
great man! but H1T1000 ？How to unlock the titanium alloy version? Which one does boot. img use?
Click to expand...
Click to collapse
For Titanium variant H1T1000, I don't have the phone right away.
If you can assist me, I'd like to help you for H1T1000 firmware dumping and rooting.
你好，你也是中国人呀？能加一下QQ吗？我的QQ361212944 ，我进开发者里面OEM锁打勾了，然后进fastboot模式，输入那两个命令，都提示出错。希望你能帮帮忙。谢谢。
Well Sir
Just performed this procedure on my VZW black aluminum model and yup got ROOT! Everything works and is stable so far. 4view is working, camera is shooting 3D just fine. Not a single error, stopped app, like I said everything is chugging along. So sweet! Thanks man. I almost tried this exact procedure on my own but discussions in the h4vuser.net forums swayed me away. Just happy to have root access on my H1!
the H1 open market needs unlock code
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
SynxSynx said:
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
joeyw007 said:
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
Click to expand...
Click to collapse
Thank you so so much dude.
SynxSynx said:
Thank you so so much dude.
Click to expand...
Click to collapse
your welcome, hope it helps.
joeyw007 said:
your welcome, hope it helps.
Click to expand...
Click to collapse
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
SynxSynx said:
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
Click to expand...
Click to collapse
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
joeyw007 said:
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
Click to expand...
Click to collapse
Right for sure, but the thing is I think I messed up at the point where I ended up not being able to get it to boot after removing the stock facebook apps (Lord knows why) but I did get t successfully rooted. Once it hit that point I kind of panicked and ended up
c:\adb>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system_b'...
OKAY [ 0.354s]
finished. total time: 0.356s
That was my dun goofed point.
At this point it's now flashing to a boot_a slot where it used to be flashing to boot_b slot. I am able to get it to start loading the OS but I'm not sure why it's not actually booting. It makes it to the Verizon boot screen, but then just hangs there.
My request from you earlier to see if you could dump your system.img (Which should still be bone stock and doesn't contain user data) was to see if I flashed the system from fastboot it would work.
I think bootloader wise it's totally fine, it's just I can't get the system to boot.
So I'm not really looking for a rom-per-se I just want to see if I can get the system.img from someones (now rooted) device to see if loading it through fastboot will make it so I don't have to send it in and wait for 5 days to get my phone back
Yeah it's completely hosed. If anyone who's rooted can do the following steps for me, I would really appreciate it because I have no phone at the moment.
adb shell
su
ls -al /dev/block/platform/*/by-name
read the Partition Management Table and find something that looks like
system ---> /dev/block/mmcblk07
dd if=/dev/block/mmcblk07 of=/sdcard/system.img
then upload the ~3gb file
It's basically the only thing that will save me right now.
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
SynxSynx said:
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
Click to expand...
Click to collapse
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
hikari_calyx said:
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
Click to expand...
Click to collapse
Dude thank you so much.
edit, read your profile, donation link secured
To subscribers of this topic:
raw dump of H1A1000 for Verizon uploaded. Note, system and vendor images are raw ext4 images, use img2simg to process them if you want to use fastboot to flash it.
https://www.androidfilehost.com/?fid=1899786940962611843
I was trying to use twrp in my device to install a custom ROM, but when after flashing it i cant boot into it, i used sp flash tool and it does not recognise my device.
when booting through cmd i get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the error that i get, i have unlocked bootloader
this might be useful to you guys i guess:
so please help me guys.
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
aIecxs said:
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
Click to expand...
Click to collapse
it doesnt works, held volume up just after i typed the command and brought me back to boot modes. there are 3 modes there: recovery mode, fastboot mode and normal mode.
selecting recovery mode would just show a android robot saying no command.
recovery mode is the right option. the no command screen is half way to stock recovery, flash twrp again. on the no command screen, press Power + Volume Up again to continue into recovery
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
so i keep flashing until it happens?
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
but it doesnt even boot into recovery now just boots into normal mode when selecting recovery mode. (only when connected to pc) but when removed from pc it boots into recovery mode and doesnt connect back to pc so fastboot command shows waiting for device.
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
aIecxs said:
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
Click to expand...
Click to collapse
ok, now i understood about the recovery menu, so to access the twrp recovery i would need to delete stock recovery i guess, but it would in turn brick my device so that just means i cant root my device, still going into root checker it says root availability is yes but it is hard to do it. so now im stuck on a roadblock...
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
aIecxs said:
(if you accidentially boot into android, twrp is gone, reflash and try again)
Click to expand...
Click to collapse
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
aIecxs said:
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
Click to expand...
Click to collapse
THERE ARE 3 METHODS!!!?? so ill just do the thing and see what happens.
VoxPlays08 said:
so ill just do the thing and see what happens.
Click to expand...
Click to collapse
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
aIecxs said:
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
Click to expand...
Click to collapse
Ok I'll reply if anything happens
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
aIecxs said:
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
Click to expand...
Click to collapse
checksum matches exactly
so flash it from fastboot and keep holding Volume Up while rebooting, select recovery mode
Im at the exact same spot, I can do the "fastboot flash recovery" but when rebooting, no matter what I press (when reboot) it always go to fastboot or normal boot..
the fastboot says its flashed ok in recovery, but I guess its overwritten when booting..
Stuck here..
If I choose recovery in fastboot using the Lenovo recovery and from there trying to flash with adb and 18.1 it erros out after 40% isch
I can use it but.. old.. and work wifi blocks me cuzzits old.