Hi, I would like to get a verification that the following procedure would work on the GPAD GPE V-510 to return back to Stock if ever needed. I am used to Nexus devices and using Factory images with Fastboot when needed and would like to have the same ability on the GPAD.
1st step was I made a TWRP backup when the device was pretty much stock (no root, standard recovery and kernel) and copied the files back to my PC.
Since then I have flashed custom recovery (TWRP) and Kernel (SleekAI)
Now if I enter Bootloader / Fastboot mode (Vol-Down + Power), would it be possible commands to return back to this state if for some reason TWRP recovery was no longer available and I wanted to restore back this image:
Check Tablet is visible in Fastboot mode:
fastboot devices
Restore Backups using Fastboot:
fastboot flash recovery recovery.emmc.win
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot flash userdata data.ext4.win
fastboot erase cache
fastboot reboot
Also do we need to restore / flash userdata or could we just issue the following command to format (erase) the data and it would return to its original state?
fastboot format userdata
If someone can confirm that this would work it would be appreciated, also do you think the backup images from 1 device could be used on other v-510 devices? If so I could post them and this procedure for anyone else needed to use this to return to Stock.
Thank you for your help,
Shaun
Related
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Zepius said:
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Click to expand...
Click to collapse
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Marc. said:
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
if something happens in the middle of you doing it the way in the link i mentioned, its easier to figure out how to fix items when you're on a certain step.
the toolkit is easier, but if something messes up, its hard to tell where since you have no idea what it is doing
the only other step is once everything is booted back up on yakju and is working properly, go back to fastboot and relock the bootloader with fastboot oem lock
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
Yes, if they check build.prop (unlikely that they will if you relock bootloader), they will be able to see the yakju fingerprint.
Marc. said:
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Click to expand...
Click to collapse
Why don't you download yakju factory image from Google? It has a bash script that can flash everything for you, in the right order. If you edit flash-all.sh, you'll see the fastboot commands it runs. That's the order you need to run them.
Sent from my i9250
I rooted my KFHD8.9 LTE and first installed CM10.2 and then CM11.0 using the following guides.
http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/
http://forum.xda-developers.com/showthread.php?t=2128175
http://forum.xda-developers.com/showthread.php?t=2128175
Worked great!! Thanks to all developers!!
I did not know the LTE option does not work with CM10/11. (The LTE versions available are unreliable, I tried them). I would like the tablet it back to Stock.
I made a TWRP backup of my original kindle stock. I have tried to restore that version in many ways with out any success. Most of the time the tablet boots back to TWRP recovery. I really don't know the reason.
I did make boot/recovery/system image back-ups as shown in the above guides. Can I issue the following commands in the fastboot mode to return the tablet to stock (ver 8.4.6)?
Is there any other steps I need to take to ensure proper return to stock? What about partition image? Do I have to restore it? I don't remember making a back-up of that.
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 reboot
PLEASE HELP!!
I am a noob and mostly worried about loosing TRWP recovery and bricking the tablet.
If you came from cm 10.2 or higher then restoring a backup in twrp might not work, I don't know what version of twrp you have but I am not familiar if the older backups would wipe out selinux xattribs on the data partition when restoring, if you know how to push and pull over adb and backup the backups to your PC first you could attempt a internal storage wipe if you wanted and then push the backups back to the device. Technically you can restore your backups with the commands you mentioned (though those arent exactly the the right files to flash mentioned in thencommands)but here's the one problem with that method, if that boot.img is from before you flashed 2nd bootloader and such then you will lose twrp, think its the same with system. So if you restore stock images you will have to reinstall twrp + and bootloader. I think kindle fire first aid can restore it for you with stock rooted but I am unaware of the jemlte model used the same bootimg and exact same system image as a normal jem model, so not positive if kffa helps or not.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
If you came from cm 10.2 or higher then restoring a backup in twrp might not work, I don't know what version of twrp you have but I am not familiar if the older backups would wipe out selinux xattribs on the data partition when restoring, if you know how to push and pull over adb and backup the backups to your PC first you could attempt a internal storage wipe if you wanted and then push the backups back to the device. Technically you can restore your backups with the commands you mentioned (though those arent exactly the the right files to flash mentioned in thencommands)but here's the one problem with that method, if that boot.img is from before you flashed 2nd bootloader and such then you will lose twrp, think its the same with system. So if you restore stock images you will have to reinstall twrp + and bootloader. I think kindle fire first aid can restore it for you with stock rooted but I am unaware of the jemlte model used the same bootimg and exact same system image as a normal jem model, so not positive if kffa helps or not.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thanks stunts513. I was using twrp 2.7.0.0, but even tried with 2.6.0.0. Deleted and formatted all internal storage, pushed backup using adb - still it does not work. I do not have any hope of restoring with twrp.
I copied the incorrect commands above. I meant these commands to restore.
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 reboot
I will try these commands, if it does not work I will have to use first aid tool.
Back to stock!!!
Here is what I did...
1) Booted into TWRP recovery and wiped everything (cache, boot, system, internal storage). Also format internal storage (Need to type "yes" to confirm)
2) Booted into Bootloader/fastboot from TWRP. (I think I restored su, not sure though)
3) Connected to PC and issued following commands - in the exact same order.
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 reboot
erase user data took a long time (2300seconds or so). I flashed boot and recovery second time because I found 2 different set of instructions as when to erase cache and userdata.
KFHD booted couple of times.. Voila I am in stock (rooted with SU). I think I can unroot with KindleFireHD89Root.zip (see link below, step10, option x)
http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/
Thanks to all developers!!
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue
Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause
Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.
If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.
Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.
Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.
same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.
Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.
philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?
I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.